Sencha Touch seems popular but looks complex to use with a node
framework so looking at JQTouch (I guess it's some sort of off-shoot
from Sencha). We want to keep things as simple as possible.
any experiences / suggestions ?
DHTMLX Touch
http://dhtmlx.com/touch/?mn
Haven't used these for a project, your mileage may vary
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
jl.z
On Mon, Apr 16, 2012 at 9:46 AM, David Whitten <whi...@worldvista.org> wrote:
> I understand that Rob Tweed has a system for making Sencha Touch much easier
> to use.
> http://www.mgateway.com/ for more details.
>
> Dave
>
> On Mon, Apr 16, 2012 at 9:28 AM, john.tiger <john.tig...@gmail.com>
> wrote:
>>
>>
>> we've tried using JQuery Mobile but it's way too buggy (and note all the
>> unanswered posts on the forum which is not a good sign)
>>
>> Sencha Touch seems popular but looks complex to use with a node framework
>> so looking at JQTouch (I guess it's some sort of off-shoot from Sencha). We
>> want to keep things as simple as possible.
>>
>> any experiences / suggestions ?
>>
>> --
>> Job Board: http://jobs.nodejs.org/
>> Posting guidelines:
>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
>> You received this message because you are subscribed to the Google
>> Groups "nodejs" group.
>> To post to this group, send email to nod...@googlegroups.com
>> To unsubscribe from this group, send email to
>> nodejs+un...@googlegroups.com
>> For more options, visit this group at
>> http://groups.google.com/group/nodejs?hl=en?hl=en
>
>
> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com
Also some popular frameworks are backbone.js and ember.js (aka sproutcore 2.0). Backbone has no ui widgets, and I ember doesn't have much.
There are *many* mobile frameworks these days.
On Mon, Apr 16, 2012 at 9:46 AM, David Whitten <whi...@worldvista.org> wrote:
I understand that Rob Tweed has a system for making Sencha Touch much easier to use.
http://www.mgateway.com/ for more details.
Dave
On Mon, Apr 16, 2012 at 9:28 AM, john.tiger <john.tig...@gmail.com> wrote:
we've tried using JQuery Mobile but it's way too buggy (and note all the unanswered posts on the forum which is not a good sign)
Sencha Touch seems popular but looks complex to use with a node framework so looking at JQTouch (I guess it's some sort of off-shoot from Sencha). We want to keep things as simple as possible.
any experiences / suggestions ?
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en
If you want to support a broad range of devices jQM is the way to go and the new v1.1.0 final release has a lot of bug fixes and improvements. I'm using jQM with backbone.js, and require.js on node, but would advice to use azicchetti's router https://github.com/azicchetti/jquerymobile-router instead of the backbone router.
images not sizing correctly
appreciate your insights -
our initial plan is to be agile - mostly server side template rendering
(node + mongodb) which we know well and can bang out fast to pass the
"fail fast" stage - then upgrade to more client side / native stuff in
version 2
so, in this approach does it make any sense to use the lower learning
curve jQTouch to get something out there asap, and migrate to Touch v2
later if warranted ?
ps: nice auto "folding" on your web site
> Just to be clear, I am independent of all the key framework
> development companies and what follows are my own opinions based on my
> own R&D and experience.
>
> I would class Sencha Touch (particularly the latest v2) as the current
> "Rolls Royce" of mobile web frameworks. Actually Sencha Touch was an
> offshoot of jQTouch - the original core developer of JQTouch was hired
> by Sencha and the ExtJS framework architecture was adapted to create
> Sencha Touch.
>
> I've not really been impressed by jQuery Mobile, but then I'm
> personally not a big fan of jQuery generally. The general view is
> that jQuery Mobile is focussed more on mobile web *sites*, while
> frameworks like Sencha Touch are all about emulating the Native App
> experience (both iOS and Android) via the capabilities of WebKit
> mobile browsers, HTML5& CSS3.
first, I appreciate all the input received.
re JQM - we found most of the showstopping bugs had to do with ui-grid /
blocks - we've totally eliminated using these and are otherwise finding
JQM to be the easiest/fastest way to get something out the door. ps: we
are also not using transitions.
after yahoo locked up my system - I wrote off anything YUI (I've never
felt their tools are that friendly w/ linux - but might just be our own
experience).
played a bit with dojo - a lot there, it just didn't seem to "flow" well
to me - this might just be personal or maybe needs better docs/tutorials
- I think it is worth looking more at.
haven't proceeded with JQTouch since what I've read seems most of effort
has passed to either JQM or Touch2
Touch2 looks very good but concerned about potential for license change
and we want to stay with totally free open source - also it is a
significant learning curve over JQM -
so our plan is: stay with JQM (without ui-grid, transitions) for
initial versions - maybe then migrate to dojo or Touch2 / phonegap
after passing fail-fast phase.
>
> Best regards,
>
> Filipe
>