[ansel] Ansel::listGalleries()

[Ben Chavet]

> I'd think that this would be easier if Ansel were using the true
> parent->child relationship, right?  If so, it's another incentive for
> working on the datatree driver to futher optimize it.

Galleries & sub-galleries do use a true parent->child relationship.  
Galleries &
Images do not.  The only issue I see here is if you move a Gallery, you 
have to
update all of the images in the gallery to reflect the new location, which
could get messy.

>> I gotta admit, that interface is pretty sweet.  I especially like the drop
>> shadows.
>>
> I do like the interface, it's just nasty code (all nested tables).  I'd
> like it to be XHTML/CSS with W3C conformance.  But maybe that's asking
> too much.

It's not asking too much if you supply a patch ;)  Seriously, though, I 
agree on
the XHTML/CSS conformance.

> If we are tracking the uploaded date for an image, this should be really
> easy to pull off.  A simple query like SELECT FROM <> WHERE
> Attriubute="Date Uploaded" AND Value>=<Date - 7days>.  If we aren't
> tracking that, we should add it as it is a piece of information that
> does seem to be relevant and would be useful down the road (say I wanted
> to do a search of my images and display all images uploaded between
> certain dates).  The random image should be possible now.

We already store a date on the images.  I don't remember right off if 
it is used
as the date upload or the date modified.  This should probably be expanded.

> One other question that you might know the answer to.  What are the
> reasons that uploaded images are stored with random filenames and not
> the uploaded image name?  I can guess that it was due to: 1) desire to
> avoid possible collisions, 2) get around naming convention issues
> between windows and unix.  Was there any other reason?

I didn't design that part (At least, I don't think I did...is that 
bad?), but I
would speculate that the points you stated are probably the reason.

--Ben