dmsmith555 at yahoo.com
Thu Aug 17 21:46:32 MST 2006
I'm not really familiar with .NET as I develop in Java for its
The Sword C++ library, is also platform independent for all practical
Does the .NET platform all for linking C++? If so, I would suggest
Then you could focus on the UI as a starting point. Later, the core
could be ported if needed.
You asked on IRC whether JSword is a complete port of Sword.
Nope. For a couple of reasons:
1) It's not a port. The code has a lot of similarities but a
different design as
it leverages the strengths of Java and uses COTS as much as possible.
2) We have not had enough time to implement all the features of Sword.
At this time we don't support Raw GenBook. And we don't support module
writing. There are other things that we don't do, but those are the
3) Sword is a moving target. The only way to keep up is to not port it,
but use it directly. There are some pretty exciting things coming up in
the next year: alternate versifications, tagged papyrii, support for TEI
dictionaries. We will have a hard time implementing all of these and
add the missing features during the next year.
If you do decide to go the JSword port route, join the jsword-devel
and I'll help you with understanding the code.
In His Service,
On Aug 17, 2006, at 10:52 PM, veritosproject at gmail.com wrote:
> I have started to port Sword (actually JSword) to the .NET Framework.
> I have so far ported org.crosswire.common.history,
> o.cw.common.activate, and a couple files from o.cw.common.util.
> If anyone wants to help on this project, just email me.
> Currently Implementing: org.crosswire.common.util.*
> Already Implemented: Filter, URLFilter,
> Iterator is going to be a mess because the structures differ greatly
> between C# and Java. CollectionUtil is also kind of odd.
> I don't know the parallel with the .class structure in Java, so the
> o.cw.common.history stuff might be malimplemented. I'll post my code
More information about the sword-devel