Thanks, Andreas. I'm quite enjoying the look and feel of qx.mobile; just not how close I need to get to html and css. I'll keep working with it. The flow layout portion is just a small part of my needs (albeit, an important need). I'm quite sure I'll find some appropriate solution.
If I come up with a generalized solution for a Flow layout for qx.mobile, I'll provide a pull request. Otherwise, I'll just do something specific to my app. Cheers, Derrell On Fri, Oct 30, 2015 at 10:11 AM Andreas Ecker <andreas.ec...@1und1.de> wrote: > Hi Derrell, > > as you’ve been using (and contributing to) qx.Desktop exclusively, it’s > clear you would need to get accustomed to qx.Mobile. ;-) It’s an > alternative GUI toolkit specifically targeting mobile or somewhat limited > devices. As such it’s also closer to the underlying HTML and CSS, allowing > to code closer to the native capabilities. > > Despite being closer to native, qx.Mobile still is quite an abstract GUI > toolkit (don’t know of more abstract ones for mobile). There’s no > reasonable way to just merge the two GUI toolkits without losing much of > the desktop features. If you still want 100% abstraction in the mobile GUI > layer, you'd have to stick to qx.Desktop. On most touch devices it should > be an ok solution, particularly with the input-device independent event > layer since qooxdoo 4.0 (or reduced DOM elements since qooxdoo 3.0). Much > depends on your app’s actual needs, a simplified UI design and proper > custom theming. > > If you want to go with qx.Mobile, you could look into CSS flexbox to come > up with a solution for your flow layout requirements. At least one specific > to your app. Only newer browsers eventually include a sufficient flexbox > implementation, which still might lack features or have bugs. See flex-wrap > for features you’d expect from a typical flow layout. Life on mobile ain’t > easy ... > > HTH, > > Andreas > > > I'm finding that I don't enjoy working with mobile nearly as much as > desktop, because there's too much I need to do in pure html because the > widget set won't do it for me. Labels, for example, have very few > properties, requiring creating html to do things. That means that, in the > style of more than a decade ago, I'm required again to deal with browser > differences and such, which was my reason for wanting qooxdoo 0.1 back in > the day. > > I still haven't figured out how to get a Flow layout in mobile. Can > someone help me? > > I'm definitely finding that I'm agreeing with whomever it was who > proposed, a month or so ago (Phyo, was that you?), that mobile and desktop > should be merged, to provide a single framework that can present > appropriately on both environments. Although I want the presentation that > qx.mobile provides for the mobile enviornment, qx.mobile seems to have lost > much of the benefit that qooxdoo has traditionally provided. Sigh. > > Derrell > > >
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
