I think you mentioned scrollbars for that last level, but you didn't have any in the mockup. In theory you could have so many children in that last level that you run out of screen space showing them and then something needs to show scrollbars or indicate that there are things not visible. In the additional 10 minutes I spent thinking about this problem, I think I would just start hacking away at the layout code and teach it to wrap into additional columns.
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Amy Sent: Friday, August 01, 2008 5:03 AM To: [email protected] Subject: [flexcoders] Re: Eli Greenfield's Randomwalk --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Alex Harui" <[EMAIL PROTECTED]> wrote: > > Amy, make sure you want 90% of tilelist functionality, otherwise it > might be better rolling your own. Selection, virtualization, renderers, > dataproviders, etc. > > > > IIRC, there are stacks of renderers, so I would try to make the last > stack this special-case thing, whether tilelist or custom layout of > items. There will likely be challenges around proper measurement. How > will you decide how many of those last things to show? Well, ideally I'd show all of them, since this is for navigation in a program...anything that's not shown is something you can't get to directly. Thanks; Amy
