Hey guys,
have you read the blog post [1] we put online some time ago? We sure plan some
kind of mobile widget's. But i don't think that we can make the desktop widget
usable on every mobile device. That gap of power is just too big currently to
get that done. But I don't want to give a way too much details about it because
we have not jet decided how to release the whole mobil stuff at all. But be
sure there will be some public code in the near future!
Regards,
Martin
[1] http://news.qooxdoo.org/qooxdoo-mobile-prototype
<http://news.qooxdoo.org/qooxdoo-mobile-prototype>
Am 05.01.2011 um 16:35 schrieb Greg Hellings:
Reusing the same API is almost certainly the best route, as what is really
being discussed is primarily a themeing discussion plus an
architecture-of-the-app issue.
That way the user can even maintain most of the same widgets and bindings while
just altering which widgets and theme are used for the mobile version
(providing they had a well designed app).
--Greg
On Jan 5, 2011 9:29 AM, "Jean-Baptiste BRIAUD -- Novlog"
<[email protected]<mailto:[email protected]>> wrote:
> Should we have a separate widget set for mobile ?
> Or Should we reconfigure behavior of classical qooxdoo widget to react on
> touch event ?
>
> I'm wondering if the second proposition give more power and more code reuse
> between mobile and desktop version of the same app.
>
> Of course, I'm not saying a mobile app should be the exact same code since
> some differences can"t be hidden behind the resue of the same widget.
> For example, putting less widget on the screen will not and should not be
> addressed by qooxdoo API.
>
> I think I would prefer having one Table widget class for both touch and
> classical device rather than having 2 classes like Table and TouchTable.
> Otherwise, the risk is a bloated API.
>
> What do you think ?
>
> On 5 janv. 2011, at 14:39, Ilkka Oksanen wrote:
>
>> Hi,
>>
>> +1 for mobile widget set. For example things like lists with inertial
>> scrolling and navigation bars for switching UI views would be very nice
>> addition.
>>
>> I'm also in the process of porting my "desktop" Qooxdoo application for
>> mobile devices and would like at least partially re-use the existing source
>> code. I first thought that the Unify framework is right tool for this job
>> but soon realised that the new Unify UI elements are quite low level and not
>> compatible with the existing Qooxdoo elements. I also considered jQuery
>> Mobile but switching to that would probably mean that I need to start from
>> the scratch with the coding.
>>
>> In my opinion majority of smartphones are already now or soon capable of
>> running the whole Qooxdoo framework. Dual core mobile devices are coming
>> this year. Problem is then just the UI elements which should be optimised
>> for the finger use and 3-4 inch screens.
>>
>> -ilkka
>>
>> http://unify.github.com/unify/
>> http://jquerymobile.com/
>>
>> On Wed, Jan 5, 2011 at 12:52 PM, rikardo
>> <[email protected]<mailto:[email protected]>> wrote:
>>
>> Are there any plans to develop modern components like Sencha Touch?
>>
>> We have developed Web portal for citizens to receive digital electronic
>> invoices and other digitally signed document on their e-portal with qooxdoo.
>>
>> We are now planning to rewrite our document management system for entrprises
>> and we would like to cover all platforms (desktop, web, mobile), we also
>> plan to use modern toolkits like QML, but the problem is that with QML web
>> platform is not covered. The only web components we have found behaving like
>> QML is Sencha Touch framwork. But it is still very raw, requires a lot of
>> css knowledge, when some special components needs to be developed (like list
>> item delegate - it cannot be developed from other components, but one must
>> define html/css text stream). Qooxdoo is much superior platform in terms
>> clean object oriented paradigm, but lacks Touch web components. If there are
>> any short term or medium term plans we would like to know, since we are not
>> making decisions which way to go.
>>
>> Thanx
>>
>>
>> --
>> View this message in context:
>> http://qooxdoo.678.n2.nabble.com/Sencha-Touch-like-components-tp5891617p5891617.html
>> Sent from the qooxdoo mailing list archive at Nabble.com<http://Nabble.com>.
>>
>> ------------------------------------------------------------------------------
>> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
>> to consolidate database storage, standardize their database environment, and,
>> should the need arise, upgrade to a full multi-node Oracle RAC database
>> without downtime or disruption
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [email protected]<mailto:[email protected]>
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>>
>> --
>> http://iki.fi/iao/
>> +358 50 486 0721
>> ------------------------------------------------------------------------------
>> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
>> to consolidate database storage, standardize their database environment, and,
>> should the need arise, upgrade to a full multi-node Oracle RAC database
>> without downtime or disruption
>> http://p.sf.net/sfu/oracle-sfdevnl_______________________________________________
>> qooxdoo-devel mailing list
>> [email protected]<mailto:[email protected]>
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
<ATT00001..txt><ATT00002..txt>
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
