<DIV>Are you planning on building the new version of BibleDesktop based on the Eclipse Rich Client Platform? <A href="http://eclipse.org/rcp/">http://eclipse.org/rcp/</A></DIV>
<DIV> </DIV>
<DIV>I think that would be a great idea. I know that IBM built the new version of Lotus Notes based on the Eclipse Rich Client Platform, which is a very complicated client application. If that can be done, BibleDesktop should be efficiently built on top of the Eclipse Rich Client Platform also.</DIV>
<DIV> </DIV>
<DIV>Thanks,<BR>Mete<BR><BR><B><I>DM Smith <dmsmith555@yahoo.com></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid">Another difference is the license. SWT uses EPL (Eclipse Public License, <BR>see http://www.eclipse.org/legal/epl-v10.html for details).<BR>I think this raises the question of how compatible is it with the GPL. <BR>The EPL seems to allow us to distribute a program under the GPL,<BR>but does not allow for GPL to be viral. Since GPL is viral, it does not <BR>look like we can freely mix the two of them.<BR><BR>The Apache License has a similar bent (which is what Lucene is licensed <BR>under), but we use it purely as an API to a separate set of services.<BR>So our code is not a derived work of Lucene.<BR><BR>The SWT does not provide such a clean separation in our code. We will be <BR>blending SWT and our code in a significant manner. So our<BR>work will clearly be a derived work of SWT and GPL.<BR><BR>Any input? Can we go with SWT and if so how? (Let's go for Light and not <BR>for Heat
:)<BR><BR>DM Smith wrote:<BR><BR>> I am reading a book on SWT to see where the differences between it and <BR>> Swing are.<BR>> I'm not interested so much in the how, but the what. I expect that SWT <BR>> has a different way<BR>> of doing the same thing. Specifically, I want to figure out what SWT <BR>> does not do that Swing<BR>> does that we care about.<BR>><BR>> The first that I found is that SWT uses the class Decorations to do <BR>> something like MDI (JInternalFrame)<BR>> but according to the book, on resize (split pane or window) the <BR>> internal windows are layed out<BR>> all over again with their original positions and sizes. I think that <BR>> this is unacceptable.<BR>><BR>> Personally, I find that MDI is only of value to look at passages <BR>> side-by-side. If that is its only value<BR>> then I think that we can figure out how to provide that feature a <BR>> different way (e.g. parallel tab sets).<BR>><BR>>
Any other thoughts?<BR><BR>_______________________________________________<BR>jsword-devel mailing list<BR>jsword-devel@crosswire.org<BR>http://www.crosswire.org/mailman/listinfo/jsword-devel<BR></BLOCKQUOTE>