Sorry, forgot to CC!
>
> > the jos package is for things that require native code and the like, so lets put
>it in org.jos.ui.core[.peers?]
>
> OK, but we will have to make an assumption at this point that the
> simplest peers, i.e. Component, Container,
> Window, etc. will not have calls to native libraries and will instead
> call some Java-abstracted graphics hardware device. I don't know if
> that part of the project has been finalized yet. Also, it would be
> useful to have some spec on the Shell interface. In trying to create a
> skeleton for the JOSToolkit, I realized that some of the functionality
> there should be things that could be accessible from any UI (e.g.
> beep()).
>
> Some thought should definitely go into the interface to graphics devices
> soon, because with a spec for the graphics device, we could create the
> Toolkit, peers, and everything in a matter of weeks. For now, we can
> settle with relegating the most fundamental component/graphics stuff to
> a default toolkit.
>
> Later,
>
> Sean Cribbs
_______________________________________________
UI maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui
