Primefaces supports both web and mobile version. There is some minor difference in coding the two version.
Is there anyway to use primefaces for both WEB and MOBILE version? I mean single code base which supports both MOBILE and WEB version using primefaces? (something similar to the applications built by bootstrap)
Primefaces mobile is built on jquery mobile which works on phone, tablet, or desktop. So if you stick with primefaces mobile it should work on all devices.
To make it clear, Primefaces created some PrimeFaces Premium Themes and Layouts like (Sentinel, Spark, Ronin and all other on http://www.primefaces.org/themes). In my opinion that's great (good looking / pixel perfect), those are responsive layouts but not all components are responsive. You can check responsive components on responsive.xhtml
Related
The scenario is a mobile page developed with JSF and Primeface Mobile. I want to navigate in the same xhtml page between multiple pages (have a look at: JSF Primefaces Mobile navigation). After upgrading PrimeFaces from version 6.1 to 7.0 org.primefaces.mobile.application.MobileNavigationHandler does NOT exist anymore. What do i need to use instead? The migration guide "6.2 to 7.0" (https://github.com/primefaces/primefaces/wiki/Migration-Guide) doesnt help me: "[...] Mobile has been removed in favor of responsive features. [...]"
There is NO migration path for you other than rewriting your code.
PrimeFaces Mobile was completely removed in 7.0
See this blog post from Primefaces: https://www.primefaces.org/primefaces-6-2-roadmap/
PF Mobile is a renderkit for the existing components however we’ve
just realized that we have to maintain two different sets at the same
time so decided to deprecate PF Mobile and focus on the responsiveness
of the standard renderkit. So in 6.2, mobile will be deprecated and
removed in 7.0.
Have a look at my migrated fork: https://github.com/djmj/primefaces-mobile.
I extracted the mobile components from PrimeFaces 6.1 and adapted them to PrimeFaces 7.0 as a separate library. I did testing with mobile showcase and will test it in our own application and production the next days.
Liferay screens is available for iOS and android allowing development of native apps using Liferay portal as backend - sort of. Is this supported in codenameone?
No.
Unlike Lifray with Codename One you only build the UI once to do that you need to use our GUI builder or API both of which would be incompatible with Lifray.
Onsen-ui 2.0 provides material and flat components. If we want to follow vendor design guidelines we should use material for android and flat for ios. How should I do without using full switch android or ios on my templates ?
With Onsen 2.0, they are enabling this exact feature. Onsen 2.0 will automatically detect the platform and switch between iOS and Material for you. Check out this blog post from yesterday that explains it all in detail: https://onsen.io/blog/what-is-material-design/
This is the relevant quote though from that link:
We have also gone one step further by adding automatic styles. What
this means is that an Onsen UI app will use the Material Design
components when running on the Android platform while it automatically
switches to the flat design when running on iOS.
I will be waiting for Beta 7 , Have you decided the date of release. Switch based on platform is going to be a fantastic feature.
Anyone have the idea of which Javascript framework is much supported by the cross platform
for PhoneGap App development.
I search on the web and find the JQuery Mobile framework but it is not much compatible with the android it shows problem with UI while it is much supported by the iPhone.
There is any JSframwork supported by the all max platform?
Please Help..
I personally use DataZombie's fork of jQTouch - https://github.com/DataZombies/jQTouch
The transitions and scrolling all work fine on Android unlike some of the others.
Android doesn't have a built-in theme for Android the way it does for iOS, but I was able to put one together for my app fairly easily (it's just CSS and a few images). When it is more complete I will probably release it, but you should be able to do your own or use the jet one (that looks fairly Android-ish).
None of the frameworks really looks like a proper native Android app out of the box as far as I have been able to tell. Nearly all of them seem to have a very iOS-centric navigation system (back buttons in nab bars, etc) that just don't exist in native Android apps. One of the first things I did in my theme was to get rid of any back buttons thus relying on the hardware back button for backward navigation (more like what Android users expect).
We are developing a J2ME application and sometimes we face constraints while working with the default lcdui library. Whenever we want some extra in the UI, the only option is to work with canvas which is not so easy. Now we are thinking to use LWUIT as UI library instead of ludui but having some question before starting -
Is LWUIT mature enough to be used in a enterprise J2ME application?
Can we mix LWUIT and LCDUI in same application ?
In my point of view. lwuit is mature enough to be used in enterprise applications. It's still in permanent development and it's progressing fast.
Yes you can mix both of them. If you use an lwuit form you can only add lwuit components and vice versa. It should be possible to implement and draw you own container objects (canvas style).
LWUIT is mature enough to be used as enterprise application and though J2ME has some limited classes when we talk about JDK but still its mature enough to build many applications