I am adapting my resolution switching work for Vidcaster on VideoJS into a plugin (see https://github.com/videojs/video.js/pull/233).
In VideoJS 3.2 the VideoJS controls were active on mobile platforms such as Android and iOS. Now when I boot up version 4 it appears the native controls take precedence. This means that features that require actions on control bar buttons such as tracks, etc are not accessible, correct?
We would like to continue to present a resolution switching button to our mobile users. Was the decision to defer to the native controls an intentional philosophical one? If so, where in the code does this decision happen? I have been digging for it for a while now.
Much appreciated.
According to the source the native controls are default on iOS and Android "until controls are more stable on those devices".
<video data-setup='{"customControlsOnMobile": true}' … would enable the video.js controls, but bear in mind they're disabled for a reason.
Update: This question and answer relate to video.js 4. For video.js 5 the equivalent is nativeControlsForTouch: false. Native controls are always used on iPhone and older versions of Android known to be problematic with custom controls.
Currently the option to initialize a video that will display videojs' custom controls and not the native controls (iOS, for example) is nativeControlsForTouch: false.
Can be found in the source here.
This option can be set as stated in the answer above through <video data-setup='{"nativeControlsForTouch": false}' … or through JavaScript: vjs('video_id', {nativeControlsForTouch: false});
Related
How can I design material design card view in cn1? It can be done pretty easily in android native and react native etc. But I'm confused how easily can it be done in cn1 with all those shadows and card radius etc. Is there any example on it? Plz see the design below.
Sure. You can use RoundRectBorder in the designer tool or through CSS. It includes support for the slight roundness of the corners as well as support for shadows. Just place containers with that styling in a BoxLayout Y.
Sencha Touch has 2 classes Ext.device.Notification and Ext.Msg to display messages.
As per documentation of Ext.device.Notification Notifications are used to show native dialog boxes. The Simulator implementation will use Ext.MessageBox for show and a simply animation when you call vibrate. In otherwords, while testing in simulator/chrome emulation, Notifications behaves like MessageBox. But on actual device, it launches native device notification.
So I was wondering why would we not always use Ext.device.Notification to show Notifications ? Is there a need to use Ext.Msg? Are there any performance issues of using Notification over Msg?
Haven't used Ext.device.Notification so far but it seems that you can not style this type of message as you could style Ext.Msg. So it should be easier to include Ext.Msg into your app theme and have a consistent look.
On the other hand (as you already mentioned) you can vibrate the device using Ext.device.Notification. This is not possible using Ext.Msg though.
That being said these two classes are not completely interchangeable.
I have been working on Foundation 4 framework.I just want to know whether off canvas layout system is required for this version or not. As per my knowledge its not required because they have added mobile support with 'Mobile First' theme.
Please correct if i am wrong.
Thanks,
Srinivas
Off Canvas Layouts is not required for Foundation 4 because it was written for version 3. But while it was written for V3 it can work with F4. I know, and not only by opinion, but as a matter of fact, as I have played with it already and have a proto using F4 with off canvas layout specifically with the sliding panel similar to this.
For better UI in small devices Off Canvas Layout is awesome. Like if You hit a button and a panel slides in from the left (or depending on how you look at it, the main panel slides out of the way). You should really use it. And Of course, if you have downloaded the latest release from github repo or via website it is already come with Zurb Foundation 4.
Does the WPF WebBrowser control always use Internet Explorer or does it use the default web browser on the system ?
Regards,
MadSeb
One issue the Web Browser Control has that it’s perpetually stuck in IE 7
rendering mode by default. Even though IE 8 and now 9 have
significantly upgraded the IE rendering engine to be more CSS and HTML
compliant by default the Web Browser control will have none of it. IE
9 in particular – with its much improved CSS support and basic HTML 5
support is a big improvement and even though the IE control uses some
of IE’s internal rendering technology it’s still stuck in the old IE 7
rendering by default.
This applies whether you’re using the Web Browser control in a WPF
application, a WinForms app, a FoxPro or VB classic application using
the ActiveX control. Behind the scenes all these UI platforms use the
COM interfaces and so you’re stuck by those same rules.
See this:
Web Browser Control – Specifying the IE Version
http://www.west-wind.com/weblog/posts/2011/May/21/Web-Browser-Control-Specifying-the-IE-Version
Internet Explorer, though there are "hacks" posted on the internet which allow you to use a workaround in order to launch any browser you like.
This thread seems to explain one of the possible solutions.
We have a standard business application written in Silverlight for which we need to use Windowless Mode. This "feature" to use a Telerik Silverlight component.
Using Google I have found lots of bad things that can go wrong with windowless mode with regards to mixing HTML content and animations. I am interested in knowing if bad things will happen if the silverlight app is the only content in the browser window.
Thanks in advance for sharing your experience.
Mike
Windowless actually improved the way Silverlight and html interact. Without windowless set, Silverlight is just painted on top of the html. Setting windowless is the only way to have html on top of silverlight or to have a transparent silverlight application.
The major downside to windowless is that it forces silverlight to be software rendered instead of hardware rendered. This means that the power of the GPU can't be utilized for things like animations.
If the silverlight app is the only thing in the browser window, the only real difference between windowless and not is the performance issue mentioned above.
An example of Windowless mode with lots of animations and mixed in HTML is the Office Labs Silverlight site. NOTE: You need to click the "Try in Silverlight" on the plain HTML version of the site to see the Silverlight version.
That site uses a floating iframe to display HTML inside of the Silverlight content. Most of the animations work just fine, however, you can't scale the HTML very easily so the HTML is hidden while some of the animations are performed.
Let me know if you have any other questions about the site.