<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.6000.16441" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV>"We will very happily add your project to the list of sword applications on
<BR>our front page. Would you like to wait until you have decided on your
new <BR>name (per your previous email about conflicting names with other
software)?" <BR><BR><BR><BR>I see how BibleCS is codenamed (CS for CrossWire).
For lack of a better <BR>name, I will go with SWBible (where SW can stand for
SwordWarrior or simply <BR>Sword). I am completely open to suggestions :)
<BR><BR><BR><BR><BR><BR>"Yes, developing your software under the banner of
CrossWire Bible Society <BR>will save you from having to obtain your own
permission to use some of our <BR>modules." <BR><BR><BR><BR>Exactly. I see no
point in doing extra work and re-inventing the wheel :)
<BR><BR><BR><BR><BR>"Most of our applications have some distinction from our
other software <BR>which we point out so users have an idea why they would like
to choose one <BR>product <BR>over another. " <BR><BR><BR><BR>One thing that
prevents me from contributing to BibleCS is that I do not <BR>know Borland.
eBible uses Microsoft Visual C++ which also provides a <BR>"microsoft look" to
the end product. I can think of a few other differences <BR>in end user
interfaces. For example, the personal notes section in eBible is <BR>different,
the footnotes appear at the bottom of each chapter, the strong <BR>and
morphological tags require the user to click instead of a pop tooltip, <BR>the
format of bible text is verse-per-line, etc. <BR><BR><BR><BR><BR><BR>Have you
looked at adding InstallMgr support to your application? This is <BR>the
code we've been chattering about which we have been trying to debug for <BR>this
next release of the engine. It is a simple class interface which
<BR>allows you to have multiple module repositories and to query for new/updated
<BR>modules and will download and install those you select. We have a
<BR>standalone application that we ship with BibleCS (our current windows
<BR>software). You are welcome to bundle that with your application so
your <BR>users can download and install using this tool. <BR><BR><BR><BR>Yes,
that can be done and it makes a lot of sense to do, since now eBible <BR>will be
dealing with a lot of modules <BR><BR><BR><BR>"As an added note, BibleCS has
been fairly stagnant for quite some time. If <BR>there is any way we might
merge our efforts to advance free windows <BR>Biblesoftware, it might be a
blessing to everyone" <BR><BR><BR><BR>BibleCS has many features that eBible
lacks. e.g. install manager, parallel <BR>feature, creating a verse list, and
support for multiple languages. Now that <BR>both projects are under one roof of
Crosswire, our projects can freely copy <BR>and paste code from each other
without any restrictions (A true merger would <BR>be more difficult due to
differences in compilers) <BR><BR><BR><BR>Over the next few weeks, I will move
our eBible source code to the <BR>SourceForge website, and try to comment the
code extensively so as not to <BR>frustrate potential volunteers J
<BR></DIV></BODY></HTML>