Thanks for the hint Christopher,
My only concern with this alternative is that there is no global view of the
tree. For instance, in iOS mail, there is an mix of 1/ and 3/ when in the
master mailboxes view, i.e. accessing mail threads is 1/ but browsing the imap
tree is 3/. I’m going to try to play with the list renderer and let you know.
Thanks and regards,
Vincent
Le 14 déc. 2013 à 23:08, Christopher Zündorf <[email protected]> a
écrit :
> Hi Vincent,
>
> I would choose alternative 1.
> Because it is the most used solution for a hierarchical data view on a mobile
> device.
> You could also hide and show the children on tap of a parent item and indent
> the children.
>
> For this solution you only have to extend the existing List renderer for your
> purpose.
>
> Greetz Christopher
> Von: Vincent Vandenschrick [[email protected]]
> Gesendet: Samstag, 14. Dezember 2013 11:58
> An: [email protected]
> Betreff: [qooxdoo-devel] Mobile hierarchical data view
>
> Hi all,
> First, congratulations for the new release !
>
> I’ve just started to implement the mobile UI for the Jspresso framework, and
> I have a design issue regarding hierarchical data view. On a desktop UI, you
> would use a tree view to represent hierarchical data, whereas on mobile,
> there is no such widget available. I would definitely like to keep a
> hierarchical view for the master view of the mobile manager.
>
> As of now, I can think of 3 alternatives :
> Chain list widgets embedded in navigation pages. I can foresee 2 drawbacks to
> this approach : the user looses the global view of the hierarchical data, and
> splitting the view into several components will complicate the data binding
> compared to what’s available with the tree controller.
> Implement a dedicated list item renderer that is itself a list, and so on…
> Might solve the problems above, but I really don’t know if this has any
> chance to work.
> Flatten the hierarchical data structure, represent it as a list, and make a
> dedicated renderer that « indents » the list item representation based on the
> item level. Will solve the global view issue, but the data binding might
> still be a little more complicated although it sounds feasible.
>
> Any opinion on this ? Any option I missed ?
>
> Thank you for any hint !
>
> Vincent
>
>
>
> ------------------------------------------------------------------------------
> Rapidly troubleshoot problems before they affect your business. Most IT
> organizations don't have a clear picture of how application performance
> affects their revenue. With AppDynamics, you get 100% visibility into your
> Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
> http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk_______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
