Re: Ansel::listGalleries()

Ben Chavet wrote:

>> I thought of that right after I sent the email.  So, what has to happen
>> if I move a sub-gallery in the current design?  The gallery has to get a
>> new parent, but the images themselves don't need any changes, do they?
>> Aren't they just connected to the containing gallery?
>
>
> The images are connected to the galleries by having a field containing 
> the name
> of the gallery they are a member of.  If the gallery you move is a 
> sub-gallery
> of any other gallery, the name of that gallery will change from 
> parent1:gallery
> to parent2:gallery.  In this case, we would have to update every image 
> in the
> gallery to reflect the new location of the gallery.
>
> --Ben

Oh, so the gallery name isn't just the immediate gallery, but the full 
lineage of the containing gallery.  Was it done that way for a reason?  
I can see that it makes it easier when displaying the lineage on the 
gallery display page, but is it used for anything else?  What would 
break if you just stored the containing gallery of the image and not the 
full lineage?  Because if you did that, it would make it much easier to 
build the gallery move function.  Can't you still get the lineage from 
the gallery information (via getParent() or some similar call)?

h
-- 
ansel mailing list - Join the hunt: http://horde.org/bounties/#ansel
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]