How's this look for a start.  If we're going to start library development then we should have an architecture.

Is there any way we can host some sort of model on wiki or dsource or dm?

We need to work out the way fwd first.

In article <c68570$1lht$1@digitaldaemon.com>, Achilleas Margaritis says...
>
>
>Exactly. It's not what I plan to write, it is what it is needed to get D accepted by software houses.
>
>I think the following libs are needed:
>
>1) collections
>2) callbacks (signals and slots/events)
>3) sockets
>4) gui
>5) database
>6) filesystem
>7) compression
>8) xml
>
>The Java's APIs is a good start...

oops... Walter doesn't like you  anymore.
He prefers the python libs.

>Qt is also another good place to look for what
>core APIs need.
>

There use to be a much more complete list on wiki, can anybody find it? Who was it from?

Ant

> oops... Walter doesn't like you  anymore.
> He prefers the python libs.

Hey, I don't like Java either.

Does Walter like me now ? :-)

Scott Egan wrote:

> How's this look for a start.  If we're going to start library development
> then we should have an architecture.
> 
> Is there any way we can host some sort of model on wiki or dsource or dm?
> 
> We need to work out the way fwd first.
> 
> 
> 

I like it. At bottom layer, import libs of native apis. Above that, simple layer of objects. And above that, DFC (D Foundation Classes).