Sencha Touch or jQuery Mobile? – Read This Before You Make a Decision
Sencha Touch or jQuery Mobile? – Read This Before You Make a Decision.
If you ever need to choose between jQuery Mobile and Sencha Touch, you need to consider these factors before making your decision:
About jQuery Mobile
- It’s a UI-only library, which relies on jQuery and jQuery UI for DOM manipulation, Ajax and other utilities
- To create UI widgets, you generally need to hand-code their html, and the library enhances their look and feel
- As it works by enhancing the html you create, it allows you to re-use or re-purpose existing html
- Some simple applications can be created using only html, without having to write JavaScript code
- It has a relatively small object model, which makes it faster and easier to learn, specially if you are familiar with jQuery
- It does not impose a coding discipline or structure, which gives you flexibility, but can lead to applications that are difficult to maintain
- Easier to integrate with other frameworks
- Targets more devices than Sencha Touch
- Not tied to a particular vendor
About Sencha Touch
- It’s a library that tries to do it all: UI widgets, DOM manipulation, Ajax and other utilities
- Does not depend on other libraries
- Follows a JavaScript-centric approach, where you are required to write little html
- Has a large object model, which provides more features out of the box, but takes longer to learn
- Imposes a coding structure and discipline, which generally results in well-organized code
- Provides built-in server and local storage abstractions, which make it easier to perform CRUD operations on relational data
- Has built-in facilities for creating iOS and Android native packages
- Targets less devices than jQuery Mobile
V|Raptor – High productivity in Java web development
V|Raptor – High productivity in Java web development.
Anybody with experience on this, please comment
thnaks
Which is the Hottest Java Web Framework? Or Maybe Not Java?
Which is the Hottest Java Web Framework? Or Maybe Not Java?.
I haven’t sat down in a long time and actually tried to determine a trend in the Java web framework arena. The uncountable number of “easy to use” Java web frameworks that are out now adays is too many to even start to pay attention to.
Struts 1 came out at a perfect time in history… where your only choice was either hand-coding everything or Struts… and most people went with Struts.
Flash forward a few years later and now you are in a state where everyone has done, redone and re-redone Struts and the Model 2 style of web frameworks over and over and over, each one supposedly easier and faster than the previous one.
Some of the frameworks genuinely bring some pretty cool ideas to the table in new and interesting ways. Others of them accomplish basic tasks with the most convoluted/confusion syntax ever; requiring you to readjust your thinking that you’ve already spent years learning (sorta like Windows Vista did) and learn entirely new technology stacks from the ground up.
With so many choices for Java web frameworks out there, and most of them pretty decent from a technical level, the only thing causing the adoption of particular ones to grow are tools and tooling support.
