Re: Ansel::listGalleries()

Quoting "Heath S. Hendrickson" <[email protected]>:

> 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)?

No - you'd lose the ability to have multiple subgalleries with the same name,
which currently works (foo:bar and baz:bar can both exist with the DataTree
code).

Using the datatree_id, instead of the datatree_name, like I said 
earlier, would
be the better way to go.

-chuck

--
"Regard my poor demoralized mule!" - Juan Valdez
-- 
ansel mailing list - Join the hunt: http://horde.org/bounties/#ansel
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]