[sword-devel] php bindings
kirkley at kirkley.com
Sun Feb 25 18:26:25 MST 2007
Hey, that 'Bible Tool' is pretty cool, I didn't see any way to jump to a
specific point in the bible though just word searches. If I wanted to tell
a newbie to start reading the book of Mark or from Mark 1-3 or something ..
is there another interface that I missed?
This is much closer to what I was talking about. Adding functionality to
this tool would probably be what I'm looking for as its similar. Is the
Troy A. Griffitts wrote:
> Have you seen our web-based software:
> Brent Kirkley wrote:
>> Yeah, I see what your saying. However at Sun when we are rebuilding
>> software, at a certain point we look at completely rebuilding from the
>> ground up with an entire new standard .. we do this just to shed the
>> and work arounds of the older architecture. So where I was going with
>> if the php client if you will was written in such a way to only
>> the newer adopted xml texts, granted it doesn't make everyone happy.. but
>> would in time help motivate folks to port the old texts to the new
>> formats or build import/export tools ..etc.
>> It doesn't really matter to me, just looking for easier ways to make
>> the Word of God out there quicker so more people can get at it where ever
>> they are. With the current move to the web all over the world, its on
>> phones, and pda's, dumb terms, pc's, even on TV's now. Can you imagine a
>> missionary in some foreign country sharing the bible with some guy living
>> a mountain somewhere over a satalite web phone looking at a web version
>> the Sword texts?? Cool huh!
>> Jonathan Morgan wrote:
>>> On 2/24/07, Brent Kirkley <kirkley at kirkley.com> wrote:
>>>> I'm interested in participating in a php version of the sword software.
>>>> According to the Osis docs the bible texts aren't too var removed from
>>>> regular xml docs so parsing them out shouldn't be that bad. Also, I
>>>> thinking.. instead of trying to incorporate all of these C libs into
>>>> build stack.. why not recreate them as php module/libs or even objects.
>>>> Granted the effort is duplicated but at least the build is completely
>>>> separate from the build tree.
>>> The Sword library contains a large amount of functionality, which it
>>> would be difficult to duplicate in any given language, and it would
>>> require adding support for anything as Sword added support for it, to
>>> keep it current. Even the JSword project, which has had a large
>>> amount of effort put into it, is not very close to the Sword library.
>>> If you use a binding to the existing library, then you get all the
>>> functionality already there very nearly for free.
>>> In addition, the issue isn't just OSIS. A large number of Sword
>>> modules are in the ThML or GBF formats. Unless you wish to support
>>> all of these, you lessen your chances of dealing with any Sword module
>>> properly. Sword supports all these module types already.
>>> sword-devel mailing list: sword-devel at crosswire.org
>>> Instructions to unsubscribe/change your settings at above page
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
View this message in context: http://www.nabble.com/php-bindings-tf3175267.html#a9152121
Sent from the SWORD Dev mailing list archive at Nabble.com.
More information about the sword-devel