Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Jimmie Houchin
Thanks for the info. I just subscribed to the jsword-devel list so I could find the cvs. Jimmie Houchin Joe Walker wrote: www.crosswire.org/jsword Troy - perhaps we should link to it from somewhere? Joe. Jimmie Houchin wrote: Hello, Is the JSword backend code available via download or cvs

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Chris Little
On Thu, 16 Jan 2003, Jimmie Houchin wrote: > I am not understanding the need of reading the binary indexes. If I can > read the text and produce the text appropriately for the frontend to > render to the user, then why do I need the indexes? Can't I create my > own indexes based off the text?

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Joe Walker
www.crosswire.org/jsword Troy - perhaps we should link to it from somewhere? Joe. Jimmie Houchin wrote: Hello, Is the JSword backend code available via download or cvs? I am not finding it at Crosswire. I am very liking missing it somewhere. Thanks. Jimmie Houchin Joe Walker wrote: Jim

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Jimmie Houchin
Hello, Is the JSword backend code available via download or cvs? I am not finding it at Crosswire. I am very liking missing it somewhere. Thanks. Jimmie Houchin Joe Walker wrote: Jimmie Houchin wrote: The Java frontend, does it use the Sword libraries or will there be Java code for reading

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Joe Walker
Jimmie Houchin wrote: The Java frontend, does it use the Sword libraries or will there be Java code for reading Sword modules? There *is* Java code for reading Sword modules. JSword is split between frontend and backend in a similar way to Sword, so there is a JSword backend that reads Swor

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Jimmie Houchin
[EMAIL PROTECTED] wrote: Similar to what others have suggested, you might think of just doing an OSIS reader and not try to read Sword modules. There are quite a few of them and you'll need to be quite familiar with C++ in order to understand the code that reads/writes them. Naive question aler

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Jimmie Houchin
Chris Little wrote: On Thu, 16 Jan 2003, Jimmie Houchin wrote: You mean I can't reverse engineer them from the text markup itself? You can try, but you will probably fail. It's not markup that poses a problem. The markup is just other people's standards that we make use of. The problem is

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread porton
> > Similar to what others have suggested, you might think of just doing an > > OSIS reader and not try to read Sword modules. There are quite a few of > > them and you'll need to be quite familiar with C++ in order to understand > > the code that reads/writes them. > > Naive question alert... >

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Patrick Narkinsky
Thus spake "Chris Little"> : > Like I proposed that we might do for Sword, he could consider building > indexes into the OSIS XML files. It would be relatively simple to build > an index that catalogues the start and end point of each identified > osisID, for example. This would mean you only ha

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Chris Little
On Thu, 16 Jan 2003, Jimmie Houchin wrote: > You mean I can't reverse engineer them from the text markup itself? You can try, but you will probably fail. It's not markup that poses a problem. The markup is just other people's standards that we make use of. The problem is reading the binary in

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread porton
> Thus spake "[EMAIL PROTECTED]"> : > > > Why we don't use a database library (db1/db2/db3, are to bloated and so I > > think not acceptable), but there are also several other similar formats? I > > recommend to switch to such a database in a future version of Sword instead of > > our own messed c

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Chris Little
On Thu, 16 Jan 2003 [EMAIL PROTECTED] wrote: > > On Thu, 16 Jan 2003 [EMAIL PROTECTED] wrote: > > > > Similar to what others have suggested, you might think of just doing an > > OSIS reader and not try to read Sword modules. There are quite a few of > > them and you'll need to be quite familiar

[sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Jimmie Houchin
If I am able I will write Squeak access to Sword Modules. If that is not successful or possibly even if it is, I can interface the Sword libraries as either a plugin or via FFI. The Squeak frontend I want. How I access the Sword Modules is flexible. Thanks. Jimmie Houchin [EMAIL PROTECTED] wro

[sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Jimmie Houchin
Chris Little wrote: On Thu, 16 Jan 2003 [EMAIL PROTECTED] wrote: It will be interesting to see if the Sword Module system stabilizes in light of OSIS. The above statement was actually mine. Sword will not be dropping any module formats as a result of OSIS. OSIS is being used as an import form

[sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Jimmie Houchin
[EMAIL PROTECTED] wrote: If the Sword project provided OSIS modules for all its text that would be fine. With OSIS there is a spec to go by. I could start there within Squeak. If I needed to interface the Sword libraries then I could. I would have to be willing to limit access to those platforms

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread porton
> On Thu, 16 Jan 2003 [EMAIL PROTECTED] wrote: > > Similar to what others have suggested, you might think of just doing an > OSIS reader and not try to read Sword modules. There are quite a few of > them and you'll need to be quite familiar with C++ in order to understand > the code that reads/wr

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Patrick Narkinsky
Thus spake "[EMAIL PROTECTED]"> : > Why we don't use a database library (db1/db2/db3, are to bloated and so I > think not acceptable), but there are also several other similar formats? I > recommend to switch to such a database in a future version of Sword instead of > our own messed code, which i

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-16 Thread Chris Little
On Thu, 16 Jan 2003 [EMAIL PROTECTED] wrote: > > It will be interesting to see if the Sword Module system stabilizes in > > light of OSIS. Sword will not be dropping any module formats as a result of OSIS. OSIS is being used as an import format at the moment. In the future, we might base addit

Re: [sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-15 Thread porton
> It will be interesting to see if the Sword Module system stabilizes in > light of OSIS. The problem is not what is format of entries (e.g. OSIS), but the format but a module (as a whole, the structure how it is split to entries). Why we don't use a database library (db1/db2/db3, are to bloate

[sword-devel] RE: [sword-devel]Squeak Sword UI

2003-01-15 Thread gprideau
> If the Sword project provided OSIS modules for all its text > that would > be fine. > > With OSIS there is a spec to go by. > > I could start there within Squeak. If I needed to interface the Sword > libraries then I could. I would have to be willing to limit access to > those platforms for which

[sword-devel] Re: [sword-devel]Squeak Sword UI

2003-01-15 Thread Jimmie Houchin
It will be interesting to see if the Sword Module system stabilizes in light of OSIS. If the Sword project provided OSIS modules for all its text that would be fine. With OSIS there is a spec to go by. I could start there within Squeak. If I needed to interface the Sword libraries then I coul