[dev] ansel backend

[Ben Chavet]

Sorry about being so vague, I was quite frustrated at the time :)

I just scrapped my last attempt because of complications, and here's where I'm
at now.  I'm planning on having a control structure, I'll probably stick with
$ansel_shares, which will extend Horde_Share and act as the root of the tree. 
Galleries will extend CategoryObject_Share, Images will extend CategoryObject. 
The control structure will be used to access different objects and will be able
to differentiate between galleries and images, as well as the parent/child
relationship between all of the objects (at least, that's what I hope it will
be able to do).

I just started this approach this morning and will probably not get back to it
until tomorrow or the next day.  It's not even a complete skeleton yet, so I'll
keep you updated on my progress as I go.

--Ben

PS, the class names listed above are from memory, might not be exact names, but
you get the idea...



Quoting Chuck Hagenbuch <chuck at horde.org>:

> Quoting Ben Chavet <ben at chavet.net>:
>
> > I'm out of ideas, so I thought I would call in some reinforcements.  These
> > are some of the problems I've been facing:
> >
> > - Which class should I extend & how should I do it?
> >
> > - How do I say "here is a gallery, which images are in it?"
> >
> > - How do I say "here is an image, what gallery does it belong to?"
> >
> > - If I use a control structure (like groups does), where do I store the vfs
> > info?
> >
> > Any ideas are *very* welcome!
>
> Oof. Do you have any notes/code/pseudo code to riff on? Those are pretty
> large
> questions...
>
> -chuck
>
> --
> Charles Hagenbuch, <chuck at horde.org>
> "I'm really... I'm not too fascinated by green food." - Average Joe
>
> --
> Horde developers mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>


----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.