<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">My RCP application takes up 14 MB. My plugins and the JSword plugin
take up ~800KB. JSword dependencies take up ~1MB. The rest is made up of RCP core
plugins or RCP ancillary plugins on which my plugins depend. <br>
<br>
RCP doesn't trim down very well (save the 3MB that Gabriel mentioned), but I think that's a fair price for the flexibility and functionality that it provides. <br><br><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">----- Original Message ----<br>From: Zhaojun Li <lzj369@gmail.com><br>To: J-Sword Developers Mailing List <jsword-devel@crosswire.org><br>Sent: Saturday, December 9, 2006 2:10:39 PM<br>Subject: Re: [jsword-devel] feather request: book downloading and index generating api<br><br>Peter, <br><br> I would say the final size would be 12 mb. Of course it may be able to be compressed a little bit.<br><br>I would suggest that No change for DB itself except that we provide a new plugin project for people who ever want to do RCP work. It will be like a jar file. This project is a nice to have one.
<br>I appreciate DM's offering for a place to collaborate . Like Apache, we can make it an incubator project. <br><br><br><br><br><div><span class="gmail_quote">On 12/9/06, <b class="gmail_sendername">Peter von Kaehne
</b> <<a rel="nofollow" target="_blank" href="mailto:refdoc@gmx.net">refdoc@gmx.net</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I can honestly say the discussion you juts had on this thread is way above my head.
<br><br>That said, may I please urge caution - a 9mb download requires a broadband connection, a lot of people though do not have these yet - particularly a lot of those Crosswire is aimed at.<br><br>Unless - and I do not understand this - there is a serious gain in functionality, is this a good way to go?
<br><br>Peter<br><br>-------- Original-Nachricht --------<br>Datum: Sat, 9 Dec 2006 12:32:21 -0500<br>Von: "Zhaojun Li" <<a rel="nofollow" target="_blank" href="mailto:lzj369@gmail.com">lzj369@gmail.com</a>><br>An: "J-Sword Developers Mailing List" <
<a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>><br>Betreff: Re: [jsword-devel] feather request: book downloading and index generating api<br><br>> For RCP, it will be a set of plugins,.For a library purpose for third
<br>> party<br>> to use, it should be a plugin project with jsword and common jar and<br>> expose<br>> all the packages to downstream plugin jars that use it.<br>><br>> We need to discuss it before nail it down.
<br>><br>> On 12/9/06, P. R. B. <<a rel="nofollow" target="_blank" href="mailto:dysbiote@yahoo.com">dysbiote@yahoo.com</a>> wrote:<br>> ><br>> > Do you mean in an Eclipse sense, like New -> Project... -> Java Project,<br>> > or conceptually? Eclipse-wise, the way that's worked best for me is to
<br>> have<br>> > several Java plug-in projects that compose the RCP application, similar<br>> to<br>> > how BibleDesktop is composed of projects bibledesktop, commons-swing,<br>> > commons, etc. I'm not sure if that helps answer your question or not.
<br>> ><br>> > ----- Original Message ----<br>> > From: DM Smith <<a rel="nofollow" target="_blank" href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.com</a>><br>> > To: J-Sword Developers Mailing List <<a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">
jsword-devel@crosswire.org</a>><br>> > Sent: Saturday, December 9, 2006 8:47:23 AM<br>> > Subject: Re: [jsword-devel] feather request: book downloading and index<br>> > generating api<br>> ><br>
> > One question, should it be a "java project" or a "java plugin project" ?<br>> > On Dec 9, 2006, at 8:41 AM, DM Smith wrote:<br>> ><br>> > I'll see about setting up a jsword-rcp Eclipse project and get the
<br>> > permissions wide open. We can use this to collaborate.<br>> > On Dec 9, 2006, at 1:44 AM, Zhaojun Li wrote:<br>> ><br>> > My last post before I fall asleep :)<br>> ><br>> > Let us do not worry code efficency or naming standard and such and such.
<br>> > At least we have a start point. We can always refactor and tune the apis<br>> > later.<br>> ><br>> > Right now, the most import thing is to get started.<br>> ><br>> > God Bless!
<br>> ><br>> > On 12/9/06, P. R. B. <<a rel="nofollow" target="_blank" href="mailto:dysbiote@yahoo.com">dysbiote@yahoo.com</a>> wrote:<br>> > ><br>> > > Hi Zhaojun,<br>> > ><br>> > > I'll work on making the jsword plugin available this weekend. In
<br>> > > general, I had two purposes when writing the plugin: to use RCP<br>> classes in<br>> > > place of JSword classes whenever I felt it was appropriate (e.g.<br>> > > preferring IProgressMonitor over JSword Job and RCP extension points
<br>> over<br>> > > properties files), and expose only the essential packages to the<br>> clients.<br>> > ><br>> > > Don't worry about me being burned out. =) Most of that had to do with<br>
> > > trying to write the thing myself in a short period of time through<br>> long<br>> > > nights, and making the project self-serving / ego-driven rather than<br>> > > God-serving. That's my confession. I think there's a lot we can do
<br>> with it<br>> > > together if we're patient.<br>> > ><br>> > > As to your previous e-mail: Having multiple GUIs may be a good idea.<br>> One<br>> > > of the strengths of BibleDesktop is its smaller footprint and
<br>> compatibility.<br>> > > The desktop application I wrote is focused on functionality /<br>> usability (<br>> > > e.g. listing the commentaries and dictionaries that reference a<br>> > > highlighted verse) at the cost of depending on the RCP framework and
<br>> being<br>> > > fairly CPU intensive for some operations. There'd be less concern<br>> about<br>> > > applications having overlapping functionality or overlapping target<br>> audience<br>> > > if we keep the GUIs in separate niches, yet we'd still be pushing to
<br>> keep<br>> > > the core flexible and simple.<br>> > ><br>> > > Be sure to keep all of this in your prayers. If we keep God at the<br>> > > center of this, I believe He'll lead us to something good.
<br>> > ><br>> > > Good night, all.<br>> > > -Phillip<br>> > ><br>> > ><br>> > > ----- Original Message ----<br>> > > From: Zhaojun Li < <a rel="nofollow" target="_blank" href="mailto:lzj369@gmail.com">
lzj369@gmail.com</a>><br>> > > To: J-Sword Developers Mailing List <<a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>><br>> > > Sent: Friday, December 8, 2006 11:51:59 PM
<br>> > > Subject: Re: [jsword-devel] feather request: book downloading and<br>> index<br>> > > generating api<br>> > ><br>> > > Philip,<br>> > ><br>> > > I don't konw OSGi good enough either. However, guys in the street tell
<br>> > > me it is cool.<br>> > ><br>> > > I think a standard ant build to create a plugin jar is good enough for<br>> > > now. With your effort, I think we are in a good position now. Since
<br>> you are<br>> > > burned out, :) , I can take over your GUI and maintain mine too. After<br>> all,<br>> > > it is not very hard for this part.<br>> > ><br>> > > Since you did the migration already, Could you share your changes? I
<br>> > > mean overview, why and how.<br>> > ><br>> > > On 12/9/06, P. R. B. < <a rel="nofollow" target="_blank" href="mailto:dysbiote@yahoo.com">dysbiote@yahoo.com</a>> wrote:<br>> > > ><br>> > > > Another thing to consider is to put the JSword and Common code into
<br>> a<br>> > > > basic OSGi bundle / RCP plugin jar and have BibleDesktop run an OSGi<br>> > > > framework implementation (something like Apache Felix). The<br>> Crosswire jars<br>> > > > would stay independent of RCP, yet RCP developers could treat the
<br>> jars as<br>> > > > standard plugins. Some abstraction classes would still need to be<br>> made to<br>> > > > the JSword/Common code for RCP'rs, to reduce the conflicts that<br>> Zhaojun and
<br>> > > > I ran into.<br>> > > ><br>> > > > I don't know enough about OSGi to say what other pros and cons there<br>> > > > are.<br>> > > ><br>> > > > As for making BibleDesktop a standard GUI RCP: Yes, you'd be
<br>> dependent<br>> > > > on SWT.<br>> > > ><br>> > > > Any other thoughts? It seems like we've got some good ideas floating<br>> > > > around.<br>> > > ><br>
> > > > ----- Original Message ----<br>> > > > From: David < <a rel="nofollow" target="_blank" href="mailto:lzj369@gmail.com">lzj369@gmail.com</a>><br>> > > > To: J-Sword Developers Mailing List <<a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">
jsword-devel@crosswire.org</a> ><br>> > > > Sent: Friday, December 8, 2006 10:50:14 PM<br>> > > > Subject: Re: [jsword-devel] feather request: book downloading and<br>> > > > index generating api
<br>> > > ><br>> > > > The main advantage for RCP that it hides the low level details from<br>> > > > business logic. A big plus is cross platform is piece of cake. We<br>> can click
<br>> > > > several times to make it run on almost every platform like linux,<br>> > > > windows,mac ,ppc, you name it. It is native code call from java<br>> layer, thus<br>> > > > very fast.
<br>> > > > The biggest challenge is the size.<br>> > > ><br>> > > > The default size is like 9mb.<br>> > > ><br>> > > > Another advantage is update: RCP has built-in update site support.
<br>> It<br>> > > > even supports anatomical update! even scheduled update!<br>> > > ><br>> > > > Plus, it is de facto standard for JAVA IDE now. and IBM is behind<br>> it.<br>> > > >
<br>> > > > as far as BD gui, it is hard to tell because it depends. My<br>> experince<br>> > > > tells me that it is very easy to mimic the current gui with two<br>> views.<br>> > > > Installation view can be done , I have it done already, it can be
<br>> shared.<br>> > > > The other part is main gui: it should be a Form base with a broswer<br>> GUI or<br>> > > > two.<br>> > > > The preference can be done by using RCP built-in preference api. It
<br>> is<br>> > > > very simple. I can share my code by providing a simple tutorial.<br>> > > ><br>> > > > BTW, all code are open sourced.<br>> > > ><br>> > > > I have different opinion about the classloader. Yes, jsword's class
<br>> > > > loader creates an issue for RCP. However, I do not think removing it<br>> is a<br>> > > > good idea. We can add addition classes or addition methods to jword<br>> (Jsword,<br>> > > > and common) to solve this issue. Maybe is is time to create an
<br>> standard<br>> > > > eclipse plugin. I can offer help on this one.<br>> > > > Next week I will release all the code to a place so everyone can<br>> share<br>> > > > and modify. The GUI like a clone of WEBSOWRD on
<a rel="nofollow" target="_blank" href="http://crosswire.com">crosswire.com</a><br>> > > ><br>> > > > In Christ,<br>> > > ><br>> > > > Zhaojun<br>> > > > On 12/8/06, DM Smith <<a rel="nofollow" target="_blank" href="mailto:dmsmith555@yahoo.com">
dmsmith555@yahoo.com</a>> wrote:<br>> > > > ><br>> > > > > Zhaojun and Phillip,<br>> > > > > I think there is enough interest that it would be good to meld all<br>> > > > > this into one effort.
<br>> > > > ><br>> > > > > Phillip, I'm sorry you have burned out. Perhaps if we had<br>> > > > > collaborated we could have shared the load.<br>> > > > > Please help me understand the advantages and disadvantages of
<br>> going<br>> > > > > to RCP for JSword and Common. And what impact it would have on the<br>> > > > > BibleDesktop GUI. How portable is RCP? Will it run on all<br>> platforms that<br>
> > > > > Java runs? Or is it limited like SWT?<br>> > > > ><br>> > > > > I've done a bunch of reading, but have been focusing on adding<br>> > > > > behavior to what we have. So I have not really experimented too
<br>> much.<br>> > > > ><br>> > > > > In Him<br>> > > > > DM<br>> > > > > On Dec 8, 2006, at 9:17 PM, P. R. B. wrote:<br>> > > > ><br>> > > > > Hi gang,
<br>> > > > ><br>> > > > > I ran into the same problem with RCP. I ultimately turned the core<br>> > > > > JSword libraries (common and jsword -- the parts I was after) into<br>
> an RCP<br>> > > > > plug-in that could accommodate the RCP Job class and use plug-ins<br>> to extend<br>> > > > > the installer, filter, and driver (RCP needs to manage class<br>> loaders itself,
<br>> > > > > so the class utilities and property files were removed). The key<br>> to changing<br>> > > > > the job code, for me, was to replace JSword-Job calls with<br>> IProgressMonitor
<br>> > > > > calls, and making all calls run in the caller's thread. The<br>> IProgressMonitor<br>> > > > > interface serves essentially the same purpose and the JSword Job<br>> class, so
<br>> > > > > the change was fairly straight-forward.<br>> > > > ><br>> > > > > I have an example of the changes that I made at the bottom of this<br>> > > > > e-mail.
<br>> > > > ><br>> > > > > Off-topic: I hit project burn-out with this endeavor a few weeks<br>> > > > > back and the fate of the code is undecided (I take project<br>> burn-out pretty
<br>> > > > > hard). The JSword plug-in is functional and the RCP application is<br>> 100%<br>> > > > > working. If anyone wants to play with it or is interested in<br>> helping me<br>> > > > > resurrect the thing back to life, please let me know.
<br>> > > > ><br>> > > > > Thanks,<br>> > > > > -Phillip<br>> > > > ><br>> > > > > --<br>> > > > ><br>> > > > > Example changes to convert JSword Job code to use IProgressMonitor
<br>> > > > > (for non-RCP'rs, IProgressMonitor and IStatus are part of the<br>> Eclipse/RCP<br>> > > > > core API):<br>> > > > ><br>> > > > > Installer interface:
<br>> > > > > IStatus install(IProgressMonitor monitor, Book book);<br>> > > > ><br>> > > > > HttpSwordInstaller class:<br>> > > > > public IStatus install(IProgressMonitor monitor, Book book){
<br>> > > > > // Is the book already installed? Then nothing to do.<br>> > > > > if (Books.installed().getBook(book.getName()) != null)<br>> > > > > {<br>
> > > > ><br>> monitor.beginTask(Msg.INSTALLING.toString(book.getName()),<br>> > > > > 1);<br>> > > > > monitor.worked(1);<br>> > > > >
monitor.done();<br>> > > > > return Status.OK_STATUS;<br>> > > > > }<br>> > > > ><br>> > > > > final SwordBookMetaData sbmd = (SwordBookMetaData)
<br>> > > > > book.getBookMetaData();<br>> > > > > try<br>> > > > > {<br>> > > > > // the task has as many steps to perform as there are
<br>> > > > > parts to the download<br>> > > > ><br>> monitor.beginTask(Msg.INSTALLING.toString(book.getName()),<br>> > > > > (getSize(book) / 4096) + 1);<br>> > > > >
monitor.subTask(Msg.JOB_INIT.toString());<br>> > > > ><br>> > > > > URL temp = NetUtil.getTemporaryURL("swd", ZIP_SUFFIX);<br>> > > > > //$NON-NLS-1$<br>> > > > >
<br>> > > > > // download the book. Each chunk downloaded<br>> contributes<br>> > > > > to the monitor's work.<br>> > > > > download(monitor, directory + '/' + PACKAGE_DIR,
<br>> > > > > sbmd.getInitials() + ZIP_SUFFIX, temp);<br>> > > > ><br>> > > > > // Once the unzipping is started, we need to continue<br>> > > > > File dldir =
SwordBookPath.getDownloadDir();<br>> > > > > if (!monitor.isCanceled())<br>> > > > > {<br>> > > > > monitor.subTask (Msg.JOB_CONFIG.toString
());<br>> > > > > IOUtil.unpackZip(NetUtil.getAsFile(temp), dldir);<br>> > > > > SwordBookDriver.registerNewBook(sbmd, dldir);<br>> > > > > }
<br>> > > > ><br>> > > > > }<br>> > > > > catch (Exception ex)<br>> > > > > {<br>> > > > > Reporter.informUser
(this, ex);<br>> > > > > return new Status(IStatus.ERROR,<br>> > > > > JswordActivator.PLUGIN_ID, 0, Msg.UNKNOWN_ERROR.toString(), ex);<br>> > > > > }<br>> > > > > finally
<br>> > > > > {<br>> > > > > monitor.done();<br>> > > > > }<br>> > > > ><br>> > > > > return Status.OK_STATUS;
<br>> > > > ><br>> > > > ><br>> > > > > ----- Original Message ----<br>> > > > > From: David < <a rel="nofollow" target="_blank" href="mailto:lzj369@gmail.com">lzj369@gmail.com</a>><br>> > > > > To: J-Sword Developers Mailing List <
<a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a>><br>> > > > > Sent: Friday, December 8, 2006 10:26:01 AM<br>> > > > > Subject: Re: [jsword-devel] feather request: book downloading and
<br>> > > > > index generating api<br>> > > > ><br>> > > > > Hi, DM,<br>> > > > > If you just want to migrate to SWT, I personally think it does not<br>> > > > > worth it. SWT just another set of API, like SWING. However, if
<br>> you want to<br>> > > > > migrate to NETBEAN RCP or Eclipse RCP, I will applause your<br>> effort. (The<br>> > > > > application size will be increased by 6-9MB). For Eclipse RCP,
<br>> the work is<br>> > > > > just create veiws and call jword api.<br>> > > > ><br>> > > > > The work I am doing is based on Eclipse RCP. Jsword is a base part<br>> > > > > of it. The plan is to build a p2p system that can enable blog ,
<br>> forum<br>> > > > > sharing, of course file sharing( JXTA.) next year. It will be a<br>> set of<br>> > > > > plugins.<br>> > > > ><br>> > > > > Right now, I am rewriting the system to look like exactly what is
<br>> on<br>> > > > > web sword interface. After all, people are familar with web<br>> interface. I ,<br>> > > > > however did a websword plugin with tomcat embedded(yes, a server<br>> on user's
<br>> > > > > desktop). It is cool. However, due to other considerations, I put<br>> it on<br>> > > > > hold.<br>> > > > ><br>> > > > > Since you are interest, I will put the source code to Google code
<br>> > > > > next week. I tried sourceforge, still does not get approved. An<br>> > > > > alternative is I put the code temporily into jwsord SVN, so you<br>> can look at<br>> > > > > it. Again, next week. :)
<br>> > > > ><br>> > > > ><br>> > > > ><br>> > > > > On 12/8/06, DM Smith < <a rel="nofollow" target="_blank" href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.com</a>> wrote:<br>> > > > > >
<br>> > > > > > We hope to migrate the UI to SWT. So I am very interested in<br>> your<br>> > > > > > RCP<br>> > > > > > work. Is there a place where I can see what you have done. If
<br>> > > > > > possible,<br>> > > > > > I'd like to minimize your pain of re-integrating the JSword as<br>> it<br>> > > > > > changes.<br>> > > > > >
<br>> > > > > > David wrote:<br>> > > > > > > Eclipse RCP platform has its own threading api. Use can choose<br>> > > > > > the job<br>> > > > > > > run on backgroud or foreground. I maybe need to double check
<br>> why<br>> > > > > > the<br>> > > > > > > process failed. (I believe it is because of threading)<br>> > > > > > > For book installation, I added two mirror methods to do
<br>> > > > > > downloading<br>> > > > > > > and copying. It works fine. The only issue is the api and<br>> > > > > > package<br>> > > > > > > keep changing and I have to compare every time there is a new
<br>> > > > > > release<br>> > > > > > > and merge the code.<br>> > > > > > ><br>> > > > > > > For indexing, I have not made it to work correctly. I will
<br>> > > > > > study the<br>> > > > > > > code next week. The basic idea is kick off a background job<br>> and<br>> > > > > > call<br>> > > > > > > jsword api to generate index. No thread for indexing itself is
<br>> > > > > > needed.<br>> > > > > > ><br>> > > > > > > For Web sword, the book installation is on server side. Never<br>> > > > > > mind.<br>
> > > > > > > It will not be used for end users. I put it on hold because I<br>> > > > > > have<br>> > > > > > > several othe plugins need to be done soon.<br>> > > > > > >
<br>> > > > > > > Zhaojun<br>> > > > > > ><br>> > > > > > > On 12/8/06, *DM Smith* < <a rel="nofollow" target="_blank" href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.com</a><br>> > > > > > > <mailto:
<a rel="nofollow" target="_blank" href="mailto:dmsmith555@yahoo.com">dmsmith555@yahoo.com</a>>> wrote:<br>> > > > > > ><br>> > > > > > > David wrote:<br>> > > > > > > > Hi, DM and fellow developers,
<br>> > > > > > > ><br>> > > > > > > > I am developing web sword(90% done, pure j2ee<br>> > > > > > implementation, will<br>> > > > > > > > help web hosting) and sword on eclipse RCP. Issues were
<br>> > > > > > raised up<br>> > > > > > > > when I try to integrate install book and generate<br>> indices.<br>> > > > > > The code<br>> > > > > > > > now has job api build in and also has the reporter to
<br>> > > > > > > communicate with<br>> > > > > > > > user UI.<br>> > > > > > > ><br>> > > > > > > > In order to accelerate the acceptance of jword
<br>> > > > > > library, the api for<br>> > > > > > > > downloading books and api for index processing need to<br>> > > > > > seperated<br>> > > > > > > from
<br>> > > > > > > > Job api.<br>> > > > > > > I'm not sure I understand the problem.<br>> > > > > > ><br>> > > > > > > The index api (
org.crosswire.jsword.index) is independent<br>> of<br>> > > > > > the<br>> > > > > > > Job and<br>> > > > > > > Reporter apis. The Lucene implementation is not.
<br>> > > > > > > Likewise for the install api ( org.crosswire.jsword.index<br>> )<br>> > > > > > and the<br>> > > > > > > sword<br>> > > > > > > implementation.
<br>> > > > > > ><br>> > > > > > > Both the Job api and the Reporter api are listener based.<br>> If<br>> > > > > > there<br>> > > > > > > is no
<br>> > > > > > > listener for Job events or Reporter events, then those are<br>> > > > > > not heard.<br>> > > > > > > Any listener of your choosing can be provided or not
<br>> > > > > > provided. It<br>> > > > > > > is up<br>> > > > > > > to you.<br>> > > > > > ><br>> > > > > > > The purpose of the Job and Reporter apis is to provide
<br>> > > > > > asynchronous<br>> > > > > > > communication of a potentially background task thread. For<br>> > > > > > > example, you<br>> > > > > > > will notice in BibleDesktop that you can download and/or
<br>> > > > > > index<br>> > > > > > > more than<br>> > > > > > > one Book at a time. Each download and index is on its own<br>> > > > > > thread
<br>> > > > > > > and it<br>> > > > > > > communicates back to BibleDesktop asynchronously of its<br>> > > > > > progress<br>> > > > > > > or any
<br>> > > > > > > problems that are encountered.<br>> > > > > > ><br>> > > > > > > In a web environment asynchronous communication of<br>> > > > > > long-lived
<br>> > > > > > > threads on<br>> > > > > > > the server may prove to be a challenge, but it should be<br>> > > > > > possible.<br>> > > > > > >
<br>> > > > > > ><br>> > > > > > > _______________________________________________<br>> > > > > > > jsword-devel mailing list<br>> > > > > > >
<a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> <mailto:<a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > > > > > ><br>> > > > > > >
<a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> > > > > > ><br>> > > > > > ><br>> > > > > > >
<br>> > > > > ><br>> ------------------------------------------------------------------------<br>> > > > > > ><br>> > > > > > > _______________________________________________
<br>> > > > > > > jsword-devel mailing list<br>> > > > > > > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > > > > > > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">
http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> > > > > > ><br>> > > > > ><br>> > > > > ><br>> > > > > > _______________________________________________
<br>> > > > > > jsword-devel mailing list<br>> > > > > > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > > > > > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">
http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> > > > > ><br>> > > > ><br>> > > > > _______________________________________________<br>> > > > > jsword-devel mailing list
<br>> > > > > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > > > > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel
</a><br>> > > > ><br>> > > > ><br>> > > > > ------------------------------<br>> > > > > Check out the all-new Yahoo! Mail<br>> beta<<a rel="nofollow" target="_blank" href="http://us.rd.yahoo.com/evt=43257/*http://advision.webevents.yahoo.com/mailbeta">
http://us.rd.yahoo.com/evt=43257/*http://advision.webevents.yahoo.com/mailbeta</a>>- Fire up a more<br>> powerful email and get things done faster.<br>> > > > > _______________________________________________
<br>> > > > > jsword-devel mailing list<br>> > > > > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > > > > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">
http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> > > > ><br>> > > > ><br>> > > > ><br>> > > > > _______________________________________________<br>
> > > > > jsword-devel mailing list<br>> > > > > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > > > > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">
http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> > > > ><br>> > > > ><br>> > > > ><br>> > > > _______________________________________________<br>> > > > jsword-devel mailing list
<br>> > > > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > > > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel
</a><br>> > > ><br>> > > ><br>> > > > ------------------------------<br>> > > > Access over 1 million songs - Yahoo! Music Unlimited.<br>> > > ><br>> <<a rel="nofollow" target="_blank" href="http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=36035/*http://music.yahoo.com/unlimited/">
http://pa.yahoo.com/*http://us.rd.yahoo.com/evt=36035/*http://music.yahoo.com/unlimited/</a>><br>> > > ><br>> > > > _______________________________________________<br>> > > > jsword-devel mailing list
<br>> > > > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > > > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel
</a><br>> > > ><br>> > > ><br>> > > ><br>> > > _______________________________________________<br>> > > jsword-devel mailing list<br>> > > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">
jsword-devel@crosswire.org</a><br>> > > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> > ><br>> > ><br>> > > ------------------------------
<br>> > > Any questions? Get answers on any topic at Yahoo!<br>> Answers<<a rel="nofollow" target="_blank" href="http://answers.yahoo.com/;_ylc=X3oDMTFvbGNhMGE3BF9TAzM5NjU0NTEwOARfcwMzOTY1NDUxMDMEc2VjA21haWxfdGFnbGluZQRzbGsDbWFpbF90YWcx">
http://answers.yahoo.com/;_ylc=X3oDMTFvbGNhMGE3BF9TAzM5NjU0NTEwOARfcwMzOTY1NDUxMDMEc2VjA21haWxfdGFnbGluZQRzbGsDbWFpbF90YWcx</a>>.<br>> > > Try it now.<br>> > ><br>> > > _______________________________________________
<br>> > > jsword-devel mailing list<br>> > > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">
http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> > ><br>> > ><br>> > ><br>> > _______________________________________________<br>> > jsword-devel mailing list<br>> >
<a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> >
<br>> ><br>> > _______________________________________________<br>> > jsword-devel mailing list<br>> > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">
http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> ><br>> ><br>> > _______________________________________________<br>> > jsword-devel mailing list<br>> > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">
jsword-devel@crosswire.org</a><br>> > <a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> ><br>> ><br>> > ------------------------------
<br>> > Everyone is raving about the all-new Yahoo! Mail<br>> beta.<<a rel="nofollow" target="_blank" href="http://us.rd.yahoo.com/evt=45083/*http://advision.webevents.yahoo.com/mailbeta">http://us.rd.yahoo.com/evt=45083/*http://advision.webevents.yahoo.com/mailbeta
</a>><br>> ><br>> > _______________________________________________<br>> > jsword-devel mailing list<br>> > <a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br>> >
<a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br>> ><br>> ><br>> ><br><br>--<br>"Ein Herz f�r Kinder" - Ihre Spende hilft! Aktion:
<a rel="nofollow" target="_blank" href="http://www.deutschlandsegelt.de">www.deutschlandsegelt.de</a><br>Unser Dankesch�n: Ihr Name auf dem Segel der 1. deutschen America's Cup-Yacht!<br><br>_______________________________________________<br>jsword-devel mailing list
<br><a rel="nofollow" target="_blank" href="mailto:jsword-devel@crosswire.org">jsword-devel@crosswire.org</a><br><a rel="nofollow" target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br></blockquote>
</div><br>
<div>_______________________________________________<br>jsword-devel mailing list<br>jsword-devel@crosswire.org<br><a target="_blank" href="http://www.crosswire.org/mailman/listinfo/jsword-devel">http://www.crosswire.org/mailman/listinfo/jsword-devel</a><br></div></div><br></div></div><br>
<hr size=1>Everyone is raving about <a href="http://us.rd.yahoo.com/evt=42297/*http://advision.webevents.yahoo.com/mailbeta">the all-new Yahoo! Mail beta.</a></body></html>