Fabrizio Lanza wrote:
Hi,
yes, I was referring to the Sword gui front-end. But I saw that there
are installation files for Linux also. Thus I thought it was not using
win32 specific components (riched32.dll, etc.). I did not have a
chance to try Sword under Linux. Do you perhaps know how the issue was
solved there?
I can give a partial answer:
The C++ Sword API is ported to various platforms (Window, Mac, Linux)
and this is used on those platforms to create a front end. That is the
code for each front end is platform specific.
There are some efforts currently underway to use cross platform widgets
to create a front end. When that is completed, it may be possible to use
the same frontend code on Win, Mac and Linux.
Each of these frontends may have their own strategy for rendering the
text to the user.
JSword is a Java implementation of the Sword API and BibleDesktop the
gui built with it runs on all platforms on which Java runs. This
implementation does not use RTF at all. Rather it converts the modules
to OSIS and then that to HTML. The HTML is then displayed by a Java
widget that can display HTML.
Kindest regards,
Fabrizio Lanza
2006/2/11, L.Allan-pbio <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>:
I suppose you are asking about The SWORD Project's gui
application, which is
BibleCS (also known as "The SWORD Project for Windows" and aka
sword.exe).
The sword-api (aka the sword engine) is a C++ library with no gui
component.
BibleCS uses the sword-api to access modules such as Bibles,
commentaries,
etc. and is a "front-end" to display them (along with searching
and other
functionality, but that is a quick summary).
These are my understandings:
* BibleCS was developed in Borland C++ Builder 5 (BCB-5),
* ongoing development can be done with BCB-6.
* BCB provides a wrapper around the Microsoft rtf rich edit
For the development I've one on a CrossWire front-end, I've been
generally
satisfied with rtf. However, one issue about choosing RTF is how
concerned
you are about compatability with Win9x and WinMe. They came with older
versions of riched32.dll and riched20.dll, and my experience is
that you
spend quite a bit of time fussing with the differences. On Win2000 and
WinXp, I found the rich-edit control to be very capable and more than
acceptable to work with. The headache was Win9x support.
My 2ยข worth.
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
<mailto:sword-devel@crosswire.org>
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
------------------------------------------------------------------------
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://www.crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
