-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>JADE will probably interface directly to org.jos.core.*, does that
mean
>it /has/ to be in org.jos.ui.jade.*? 
>I wrote a program that used javax.swing.*, does that mean I have to
put
>it in javax.swing.myapp.*? JADE will be an integral part of JOS'es
>succes, but I think the ability for it to be /not/ part of JOS is
just
>as important. it is an application, an ambassador between the human
the
>computer, one that can change shape to best communicate. if JOS were
>running off the onboard of a small robot in someones basement it
wouldnt
>need JADE, JADE would be a hinderance, adding extra weight to its
>fragile alluminum legs. this same robot might have a remote
connection
>to jon q. hackers PC, which does have JADE and a small app for
sending
>data to the robot, that would be the best way to communicate in this
>case. Thats why we want JADE to be flexible, so we can have the best
way
>to communicate with JOS at all times, part of realizing that is
>realizing sometimes the best way is without JADE.

just my 2c:
JADE will be developed and maintained by the JOS-Project. Therefore
the classes should be located somewhere in the org.jos tree and the
appropiate subtree for it is ui.

Then there should be a subsection for all plafs that will be
implemented.

So I'd like to create the packages as follows:

org.jos.ui.plaf          - everything that has to implemented for all
l&fs 
                           (If there is something needed outside the 
                           java.swing and java.swing.plaf packages)
org.jos.ui.plaf.default  - a default JOS l&f 

org.jos.ui.jade          - like the p&f a package containing
everything for all UI-Managers
org.jos.ui.jade.default  - the default Application handler.

The used jade-package should always use the UI which is set as the
"System Look and Feel", this should be just an entry in the registry,
so it's easy to change. (Of course the jade-manager should be set in
the same manner)

With this, it's quite easy for everybody outside JOS to write and
install their own jades using some methods like
(JadeManager.installJade(packageName) ) and the JOS-System has some
default-values it can rely on...

Just some thoughts about it...

ThomasGelzhaeuser
-----BEGIN PGP SIGNATURE-----
Version: PGP for Personal Privacy 5.5.3

iQA/AwUBN5EPAz//GJB521UHEQL/8wCg2bllf0V+uO4jAOO6/FpDNBG93o4AoKAF
6XNbVxIM+Fpw/lZestbzzBtY
=wMe8
-----END PGP SIGNATURE-----


========================================================================
Thomas Gelzh�user    | Danziger Stra�e 153        | Tel: +49 30 42804927
Software Development | 10407 Berlin / Germany     | Fax: +49 30 44050819
                                                  | Mobile: +49 172 3927600

ICQ: 9428848         | E-Mail: [EMAIL PROTECTED] 
Website (under construction and german only): http://gelzhaeuser.webjump.com

Public Key available on request

_______________________________________________
UI maillist  -  [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/ui

Reply via email to