[jsword-devel] splitting projects

[DM Smith]

Go for it.

I think common should be split into two parts, perhaps internally. One for 
swing stuff and one for everything else.

I think using Eclipse projects makes sense to manage units of development, 
which, once mature, has its own delivery schedule (e.g. 1.0, 1.1, 1.2, ...). 
This may facilitate using common for more than one project (e.g. FlashCard).

The only difficulty I can envision may be managing software changes during 
the transition.

Joe Walker writes:
>
>Hi,
>
>So I'm working on splitting jsword into:
>- jsword-web (the website)
>- bibledesktop (Swing gui)
>
>Is there a reason why we're not splitting out the following at the same 
>time?
>- common (utility stuff)
>- jsword-sword (sword like API on top of jsword)
>
>I think the original reason why I was nervous was a one-step-at-a-time sort 
>of reason, but the further I get into this the more I realize that this is 
>a fairly big change, so if splitting out the above 2 makes sense ever, then 
>now would be a good time to take the pain.
>
>I'm not going to be checking any of this in until I'm more sure that it 
>works a bit better than it does now!
>
>Joe.
>
>
>_______________________________________________
>jsword-devel mailing list
>jsword-devel@crosswire.org
>http://www.crosswire.org/mailman/listinfo/jsword-devel

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now! 
http://toolbar.msn.com/go/onm00200415ave/direct/01/