On the FAQ page for Fluid Framework https://fluidframework.com/docs/faq/#what-browsers-are-supported it says that Fluid will only work on Safari for Mac. To me this means that it will not work on iOS or the iPadOS. I don't think I need to explain why this is a problem for adoption.
So, why won't Fluid Framework work on iOS or iPadOS and is there anything that can be done about it?
Fluid Framework does work on iOS and iPadOS, but the framework doesn't get significant test coverage on those browsers. I just tested a few examples on iOS and they worked (DraftJS, brainstorm.) That language in the FAQ should be changed to reflect that there is no automated testing for iOS, but the team intends for Fluid to work.
In fact, Fluid should work in any JavaScript engine. The requirement is that the JS runtime can load the client libraries (written in JS/TS), load the container, and make a connection to the service.
There are even some (fairly hidden) Node examples in the repo, although there isn't automated testing on those examples yet either.
Full Disclosure: I work on the Fluid team
Related
Trying to figure out if Unity's LWRP could run in AirConsole build.
Apparently LWRP is supported in WebGL2 builds, so the question is - does AirConsole themselves fully support it? If not fully - what features are and what are not supported?
I am not very familiar with Unity nor LWRP, but to clarify:
AirConsole and it's games always run in a browser (except on AndroidTV where it may run as a native game). In the end AirConsole is "just" a website or Javascript API. Consequently if the browser supports WebGL 2.0, then it also works with AirConsole.
However, Web GL 2 support seems to be missing on e.g. Safari, which is one of the platforms supported by AirConsole. A game should run on all major browsers.
https://caniuse.com/#feat=webgl2
I hope this explanation helps you.
In the Google Cast SDK Overview video published on YouTube by Google, the presenter says
There are design implications that are driven from the Design Checklist so in addition to the platform specific guidelines for Android, iOS and Chrome, it is important to do a thorough review of the Google Cast Design Checklist.
The sentence reads like legal-speak, but more importantly, it mentions existence of platform specific design guidelines for Chrome. I never knew that there is anything like that. I attempted googling around, I could find guidelines for Android, iOS, but nothing for Chrome. Does anybody know where the Chrome guidelines can be found?
The design checklist is here: https://developers.google.com/cast/docs/design_checklist
The starting point for Chromecast developer doc is here: https://developers.google.com/cast/
There is an unified design guide for both Android and Web Apps that was announced on June 25 2014 at the Google I/O keynote. It is available at the https://www.google.com/design/ site. Regarding Google endorsed UI frameworks, there are two. Polymer Paper and Google Web Starter Kit. Additionally, there are stylesheets on GitHub from various people that aim to replicate the look and feel of the Chrome Settings page as well as various widely-used opinionated Responsive CSS Frameworks that can provide design clues, most notably Twitter Bootstrap and Foundation.
Polymer Paper
Polymer Paper is a set of Polymer Web Components which implements the unified mobile and web UI concept called Material Design. Some of the distinctive characteristics is the use of drop shadows and animated transitions to hide latency and give feeling of responsiveness. The components are built with the Polymer framework on top of web components, so it works best in cutting edge browsers.
Google Web Starter Kit
Together with the Google Web Fundamentals developer guide the Starter Kit provides a starting point regarding look and feel for your web app (a style guide with UI elements, e.g. sandwich sidebar), as well as preconfigured selection of helper tools to better manage your CSS styles, minify resources, keep performance considerations in mind and so on. The Starter Kit employs production ready tools and procedures that can be used today.
There is nothing like that, the presenter probably just misspoke. The Thinking in Web Apps page on Google Developers could give you some hints, but it feels outdated in many aspects.ยจ
Just some more general advice on that:
People tend to gravitate towards Twitter Bootstrap these days, so base your design on that and you will play well with others.
Watch the trends and adopt what the big players are using. For example, the sliding drawer on the side seems to be big now.
Regarding the ongoing effort by Google to allow easy porting of Chrome Apps to mobile phones, looking at the Android and iOS guides may help. Most importantly try to optimize your app for touch, avoiding hover, right clicking and minimize the need to type.
I am creating a dashboard project for which i am using nvd3 but as we know svg is not supported in IE8 so it does not render graphs/charts in IE8..please suggest how i can make nvd3 work in IE8
I'm in the same situation and I think I may just ditch nvd3 (besides no ie8 support, I'm finding other bugs). I'm wondering, has anyone successfully used r2d3 with nvd3?
My concern is that r2d3 uses d3v3 now, which nvd3 is not presently supporting (currently d3v2... d3v3 support in the works as of writing this).
For an alternative to nvd3, I'm considering:
MorrisJS!
- Works on ie8 (Raphael-based), but a newer project and less flexibility/options with the charts comparatively.
Google Chart Engine!
- I think this may be the way to go (for my project), I don't like that its not open source, but I'm already working extensively with the Google Maps API and this solution is very stable and easy to use from my experiences thus far. In limited testing in ie8 it works very well.
Also, here's another stackoverflow question on this topic, [question]: nvd3.js rendering solution for Internet Explorer
...seems r2d3 was the accepted answer there, but no one really verified it.
The library r2d3 is "a customized build of D3 powered by RaphaelJS. The combination of D3 and Raphael enable developers to easily build data visualizations that work in IE7+ and all modern browsers." - it has its limitations (see the link for details), but it would be a good place to start
Google has taken up the implementation of WebRTC in Chrome very seriously as indicated by the frequent updates in the Canary and Beta channel of Chrome. Are there any other browsers who are upto implementing this?
Firefox/IE/Opera are working on it. No word from Apple/Safari or Microsoft/IE, although IE is unlikely at best, because they're working on their own standard unfortunately. Crazier things have happened, but I wouldn't count on it. Apple has been fairly mum on the subject.
If you want support for those other browsers, we built a solution for it # Frozen Mountain (I work there) using IceLink.
Opera Mobile does offer support to WebRTC. And according to this article, Mozilla isn't all that far behind either. Ericsson Labs has their own custom browser which supports WebRTC. But it runs only on Ubuntu as of now. WebRTC itself is still under development and I'm sure that we can see complete support from all major browsers in some time.
Mozilla is far along in implementing WebRTC, and we're leading the design and implementation of DataChannels within WebRTC, as well as Identity work. We're working on a project-specific repo right now (alder), but pieces have already moved over into mozilla-central, such as initial support for getUserMedia.
Hello recently I've been a bit curious and wanted to make a browser. I'd like to use an existing engine though such as Gecko or Webkit. Are there any resources on the web for how to get started and any examples? Language choice doesn't really matter(but no VB please. That was the only example code I found)
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all Internet users to experience the web. This site contains design documents, architecture overviews, testing information, and more to help you learn to build and work with the Chromium source code.
Or study some applications using Webkit for example. Chances are, these projects are not as complex as chromium.
I'd recommend you build a browser in Java with Swing or SWT. They have all the components you'll need, so you need to put them together and start figuring out the tougher problems. The documentation is good, and you may even find tutorials that get you most of the way there.
I recently downloaded the code for Firefox or Chrome, and this seems like a much more difficult place to start. There's lots of setup and overhead to get a build working on your machine compared with a Java app.