Re: Album hierarchie

Hi Joe

> > My vacation
> > __New York
> > ____At the opera
> > __Quito
> > ____At the market
> 
> Suppose I share "My vaction" with the public. Should that setting
> apply to the pictures immediately in "My vaction" or should it apply
> to everything beneath "My vacation", including sub-albums. What if I
> had previously set __Quito to be private? 

There will always be some attribute issues with tree-like 
structures, as in any normal file system. Sometimes you want 
a setting to be applied on only one level, and sometimes it 
should propagate down into the whole tree. The important thing 
for the admin user is to have a reasonable amount of control
possibilities. 

One possible implementation would be to have something like 
the following attributes for each folder (or for each attribute
setting page):

"Attribute setting scope" (radio button values: "Only this 
level", "This level and below (except locked)" or "This level 
and ALL below")

"Attribute propagation lock" (radio button values: "Allow 
changes by parent", "Lock this level" and "Lock this level and 
all below")

The default values should be "Only this level" and "Allow changes 
by parent".

This way you have three possibilities when setting attributes: You 
can apply them to only the current level, you can set the 
complete tree (except folders/subtrees which are "Locked"), 
and finally, you can set the whole tree no matter if subtrees 
are locked or not.

There are of course a number of different ways this type of 
scheme can be implemented, so this is just one example. If you 
choose to implement something like this, then I think that it 
would be valuable to get some sort of warning message when you 
use "This level and below (except locked)" for those folders 
which are "Locked". Then you can check them individually and 
see if the lock is relevant or not.

By the way, I do not see this as relevant for the access parts 
only, but for ALL attributes possible to set for a folder
(image size, thumnail size, etc.)

One problem, though, might be that you sometimes want to change 
only one attribute (say the thumbnail size) and let it propagate 
through the tree. But you would like to keep the (possibly 
different) settings for the other attributes on that setting page.

If you want to handle this then you need to add a check-box for 
every attribute, so that when not checked this attribute is 
not changed. But you could perhaps leave this as a 
future to-maybe-never-be-implemented option... :-)

Despite the possible "propagation issues" with hierarchical 
structures I think that normally you will not change these 
attributes very often, so this "full control" possibility is 
not really the most important thing. If I get tree-structures
in Pixory I can live with some non-optimal attribute setting 
issues... 

/Gunnar





------------------------ Yahoo! Groups Sponsor --------------------~--> 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/EGnolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/pixory-beta/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/