Printable View
Noticed the road map changed on friday - the 3.2 release no longer lists 'mobile' apps (as part of that release) - really interested to find out what direction ext.js is going in developing mobile apps (whether helping with iphone dev or other platforms)?
We are committed to using HTML, CSS and Javascript for building applications.Quote:
Originally Posted by franksmejk
thanks for the quick reply - using " CSS and Javascript for building applications." is definitely the approach...
I guess I was asking (more directly if that ok) - why there was something called 'mobile apps' on the release schedule, then that was removed?
And related to this thread it was remarked that a / the developer of jqtouch was now working with ext.js - so was thinking that there would be something similar developed for placing ext code into a container (of sorts) for the iphone...?
Hope these questions make sense
It was moved off the roadmap because mobile is separate from our desktop offering - no other reason.Quote:
Originally Posted by franksmejk
thanks (again for the quick reply) - have looked at several tools for helping in this regard, but since our web apps are in ext.js.... but was looking for some details (sorry if I'm not understanding your respones) - would prefer to just use the (mobile) browser, but my project is now geting requirement to add development time / resources for iphone 'local' usage (of our apps) -
So should we expect to not see mobile widgets as a part of extjs and that there will be ext.mobile product?
However it is called, "Mobile Apps" or "ext.mobile", I'd like to have something like this Ext-based so the question still remains: Shall we wait? This year? Or, should we go jQTouch way?
Sorry for being insistent but my main application is for managers who just expect "an iPhone interface" and they keep asking for it more and more often. I could perhaps calm them down for a couple of another months but then I have to make a decision.
The replies of aconran and edspencer are very confusing... This is not an answer to the question! I can only agree to what jsakalos and franksmejk wrote! Please be more detailed and do not let us stand in the rain. This will disappoint people a lot! You changed the Road Map without explaining anything! Please change your strategy and explain us what you have planned with the already announced mobile components.
I agree with You, but I think, that the general problem is that we have so many combinations of smartphone-browser.Quote:
Originally Posted by Bucs
Every single mobile browser acts different (events, rendering engine).
The same mobile browser acts different on various devices (SIC!).
There is bigger mess than in 'regular' browsers.
And so it's not so easy do port such a framework as Ext to all that devices, even to few ot them may be hard B)
You may know that:
http://video.yahoo.com/watch/4943143/13163203
http://quirksmode.org/m/touch.html
Browser in iPhone is WebKit based and acts very similar to his big brother :)
so I think it's easiest - the environment is well known.
I have searched some threads about building web apps with ext for mobiles, but cannot find any other information then what is in here, i.e. "ext.mobile" is being worked on.
Can the team release any information about goals and timelines?