Collection interfaces

[Topmind]

> "Topmind" <topmind at technologist.com> wrote in message
> news:MPG.15085517debf4b649896ca at news.earthlink.net...
> >
> > Well, my experience tells me that the "task axis"
> > is the most "business friendly" axis to build
> > along (being that multi-axis paradigms still need
> > a lot of work and thus we are forced to emphasize
> > one at the expense of others for now.)
> >
> We'll make an OOer of you yet.
> Psst. Less structural taxonomy and more task-oriented
> thought. You might even think of a little "agent" doing
> that task for you. Then, you'll dress that little agent up
> in some nice clothes, and presto, an object.
> 


If you can show a benefit of such wrapping.


> Or component. Perhaps you should just skip OO and
> go right to components. Just don't suggest components
> should be wrapped in tables.
> 

Sometimes the interfaces can.

> I vote YES for comp.top
> 

Only because you want to get rid of me.

-tmind-