[dev] horde blocks

[Marcus I. Ryan]

Something I've learned on this project - better to be wordy and
perfectly clear than shortcut to make programming easier at the cost
of readability.

--
Marcus I. Ryan, marcus at horde.org
-----------------------------------------------------------------------
 "Love is a snowmobile racing across the tundra and then suddenly it
 flips over, pinning you underneath.  At night, the ice weasels come."
                 -- Matt Groening
-----------------------------------------------------------------------


Quoting Marko Djukic <marko at oblo.com>:

> Quoting Chuck Hagenbuch <chuck at horde.org>:
>
> > Quoting Marko Djukic <marko at oblo.com>:
> >
> > > some of the block code from portal i'd like to put into a
> separate
> > > Horde_Blocks class to deal with blocks as a collection, and
> then
> > > Horde_Block (or maybe Horde_BlockObject?) to deal with
> individual blocks?
> > > so both portal and giapeto could access the same code?
> >
> > We already have Horde_Block; how would you see Horde_BlockObject
> being
> > different? Horde_Blocks (or maybe Horde_BlockCollection, to be
> more
> > explicit?) sounds like a good idea to me.
>
> Horde_BlockObject - i was just following the naming in
> Horde_Category...
> Horde_BlockCollection sounds a bit wordy but i supppose is fine.
> Just wanted to
> avoid having Horde_Block and Horde_Blocks... too similar.
>
> marko
>
> --
> Horde developers mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>
>