Re: [Jsynthlib-devel] Once again: Package structure

[Hiroo H. <hir...@co...>]

Hi,

Joachim> I think it's hard to keep track of the suggested
Joachim> changes in a mailing list.
I agree with you.  Does anyone have a good idea?

Joachim> So nobody read Dennis's mail or what?
Joachim> 
Joachim> I agree with Dennis that an org.jsynthlib.jsynthlib package
Joachim> is superfluous and I've never seen such a doubled structure
Joachim> somewhere else.

Rib answered to the mail.  (Both the original mail and the reply were
sent to old yahoo mailing list.)

--------------------------------------------------------------------
The reasoning was to have the package name be tld.domain.application. 
The OS X Preferences class expects this, which is why there's
currently the org.jsynthlib.jsynthlib.dummy class.

Packages under org.jsynthlib are meant to be standalone. For example,
EditorBuilder uses the widgets without running JSynthLib, and the
desktop classes could be used in any java project. Since core,
synthdrivers, and the xml driver don't really make sense outside of
the Editor/Librarian, they all go into an application package. 
Unfortunately org.jsynthlib.jsynthlib is confusing, but I couldn't
think of a better name.
--------------------------------------------------------------------

I agreed with Rib silently.

org.jsynthlib is for JSynthLib project which may release other programs.
org.jsynthlib.jsynthlib is for an application called 'JSynthLib'
released by JSynthLib project.
-- 
Hiroo Hayashi