3 ms·
With all due respect, I don't think this is a strong enough reason against Sencha. Just because jQuery Mobile lets you use HTML, it doesn't mean that it's easy
by solutionyogi 15y ago
With all due respect, I don't think this is a strong enough reason against Sencha.
Just because jQuery Mobile lets you use HTML, it doesn't mean that it's easy to swap it with some other library. I think jQuery Mobile will dictate how your HTML looks like to a certain degree. If you ever decide to change the library, I think you will have to re-do the whole UI anyway just like Sencha.
I am not saying that there can not be other reasons to not use Sencha, but in my opinion, this one is not.
- untog 15y agoI think jQuery Mobile will dictate how your HTML looks like to a certain degree. Oh, absolutely. But it uses standard elements a lot- so a textbox is an <input>, a dropdown is a <select>, and so on. It depends how much you depend on their UI defaults, but in my case I've found it a very simple process to bring the UI over. It needs some CSS tweaks to look pretty again, but the rest "just works".
- wvenable 15y agoI quickly build a mobile web app using jQuery Mobile and re-used a lot of code and functionality from our desktop web app. I had to disable some jQuery Mobile functionality but I had something working in less than a week. This wouldn't have been possible if jQuery mobile isn't just a wrapper over HTML and JavaScript.