I mean... I've created some projects, each one with some milestones, and I created some different views for each milestones... working now, in to-do list, closed... you know...
My "problem" is that the list is going very big... so I beleive could be a very interesting feature to, for example, in the Main page, collapse the milestones and see only the clients, clicking in a button like ">", expand the list... so you only see the milestones list of the client you want...
In the same way, the Views list... adding, perhaps, some kind of "filter": "all the views", "views for client...".
I saw all the items are TRs, so we have only to include these TRs in a mother table for each client, with the style set to "disply: none" or "display: inline". right?
Well, i appreciate your dedication, and perhaps a job's collegue may be in "the teem" soon, and i'm sure he'll can give you some help if you want to. Bye.
Sure, something like that is doable. Just need to find an intuitive way to present it. It would also need to be saved off either in the database or in a cookie, so you don't have to expand/collapse the list every time.
Help is always welcome. I'm just me, and unfortunately I don't have unlimited time. =)
I'm sure he will be pleasure to help you making this bigger and better (and it's very very good just now, you know).
I would save the state of expanded/collapsed items in a cookie, althought my firefox delete all of them every time it closes... ;) but it's a personal preference that i can disable in my browser. I supose make an UPDATE every time a user expand or collapse a list in a window is to overload the database system and network in a non necessary task (my poor networks quality experiences here in Spain make think in that way...), and if the system and clients still go growing... the better option is allways to save the maximun amount of space in database and network bandwith, don't you think so?
The "list growing too big on the main page" problem could be solved (on the main page at least) in a different way which might be easier to implement (I don't know for sure). Please read my post here.
Nevertheless, the collapsible list idea is good and could be used on long lists anywhere in the program.
