Re: Treeview "See all" button
Evelyn McLellan
I've inserted some comments below:
Hi Evelyn,
I did some modifications in the treeview behavior so "See all" button
should appear now only when necessary.
Actually, today I came back to this issue after some days off and I
felt that the code got dirty and my solution was not very good.
I feel like the behavior is difficult to explain and probably not the
best, so I would like you tell me your opinion.
- Treeview items are limited when you open a page, but not when you
expand a node manually.
Agreed
- When some items were hidden (because of different reasons) the "See
all" button should always appear.
"See all" button should only appear when the treeview items are hidden because there are more than 10 (or whatever the set number is)
- If we have a fond with two subfonds, all of them are shown and the
"See all" button won't appear.
Agreed
- But if we have a fond with 20 subfonds, only will be shown 10 or the
value set in the settings page.
Agreed - then the "See all" button appears
- If the current node is an archival description which is not a root,
its ancestors will be shown but ancestors's siblings will be hidden,
Agreed
but the "See all" button will appear.
No, the "See all" button should only appear when there are more than 10 child levels of the information object you are currently viewing
Moreover, descendants of this
node will appear but the number is limited to the value set in the
settings page by the user...
Agreed.
In addition, the "See all" button needs to turn into something else after it has been clicked and all the child levels are showing. Maybe "See first 10" ? And when that happens, the button needs to remain where the user can easily click it - i.e. not at the end of a list of 200 descendents.
I hope this is workable. Sometimes it's hard to picture how something works until you actually have it in front of you.
Going to bed!
Regards,
--
Jesús García Crespo
David Juhasz
On 9-Apr-10, at 10:53 AM, Evelyn McLellan wrote:
>
> In addition, the "See all" button needs to turn into something else
> after it has been clicked and all the child levels are showing.
> Maybe "See first 10" ? And when that happens, the button needs to
> remain where the user can easily click it - i.e. not at the end of a
> list of 200 descendents.
I think "Hide" is kind of the de-facto standard out there. I agree
that it would be *nice* not to have to scroll down to the bottom of
the list of 200 descendants, but the user did click the "See all"
button - I think they have been adequately forewarned that there's
going to be a big list.
I think even *better* than "See all" would be "See all XXX children".
David Juhasz,
Software Engineer, Artefactual Systems Inc.
http://www.artefactual.com | P: 604.527.2056 | F: 604.521.2059
Evelyn McLellan
Evelyn
--
You received this message because you are subscribed to the Google Groups "Qubit Toolkit Developers" group.
To post to this group, send email to qubi...@googlegroups.com.
To unsubscribe from this group, send email to qubit-dev+...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/qubit-dev?hl=en.
Peter Van Garderen
>
> I think "Hide" is kind of the de-facto standard out there. I agree
> that it would be *nice* not to have to scroll down to the bottom of
> the list of 200 descendants, but the user did click the "See all"
> button - I think they have been adequately forewarned that there's
> going to be a big list.
>
> I think even *better* than "See all" would be "See all XXX children".
I agree and "See all XXX children" would be a great way to give the user an
indication of what they're in for if they select "See all". One slight tweak on
that to avoid extra text would be: "See all (XXX)", then you can ignore the word
'children' which might confuse some users.
--peter
Evelyn McLellan
I'm adding some "See all" issues to the issues list. Could you please
have a look at them, especially http://code.google.com/p/qubit-toolkit/issues/detail?id=1415?
Thanks.
Evelyn
Evelyn McLellan
On Apr 13, 4:42 pm, Evelyn McLellan <epmclel...@gmail.com> wrote:
> Hi Jesús,
>
> I'm adding some "See all" issues to the issues list. Could you please
> have a look at them, especiallyhttp://code.google.com/p/qubit-toolkit/issues/detail?id=1415?
Evelyn McLellan
Sorry, it's taking me a while to figure out how treeview and "See all"
should work.
On Apr 13, 4:42 pm, Evelyn McLellan <epmclel...@gmail.com> wrote:
> Hi Jesús,
>
> I'm adding some "See all" issues to the issues list. Could you please
> have a look at them, especiallyhttp://code.google.com/p/qubit-toolkit/issues/detail?id=1415?