Looking ahead - as a module maker rather than a developer.
Do we have a roadmap / planning page to discuss what should be done in SWORD
v1.8 ?
One thing concerns me which immediately springs to mind.
* Require support for all the new custom OSIS elements and attributes that
can be output by Chri
days) so tools are equal in importance to the engine
itself
> Date: Fri, 14 Jun 2013 01:24:20 -0700
> From: dfh...@googlemail.com
> To: sword-devel@crosswire.org
> Subject: [sword-devel] After SWORD v1.7 gets released?
>
> Looking ahead - as a module maker rather than a dev
Office Filter we have made 3 genbooks in one week at
church (will submit them within days) so tools are equal in importance
to the engine itself
> Date: Fri, 14 Jun 2013 01:24:20 -0700
> From: dfh...@googlemail.com
> To: sword-devel@crosswire.org
> Subject: [sword-devel] After SWO
On 14 Jun 2013, at 15:49, Dan Blake wrote:
> +1 for module creation tool (with GUI).
>
> On 6/14/2013 9:03 AM, Pola Edward wrote:
>> I think we also need to focus in module creation tool (with GUI) to
>> encourage more people to create modules
>> Also some more documentations and tutorials will
Better module creation tools (although desirable) are "off topic" for this
thread.
My question was about what should be in the development roadmap for the
SWORD engine (API) as new/enhanced features for subsequent releases.
David
--
View this message in context:
http://sword-dev.350566.n4.nab
On 14 Jun 2013, at 18:18, David Haslam wrote:
> Better module creation tools (although desirable) are "off topic" for this
> thread.
>
> My question was about what should be in the development roadmap for the
> SWORD engine (API) as new/enhanced features for subsequent releases.
Except your que
I think David mentioned the Python script, because currently the Sword
engine doesn't support the full OSIS spec that the Python script outputs.
The Python script produces stuff that the Sword Engine can't parse
(presumably?)
On 14 June 2013 18:24, Trevor Jenkins wrote:
> On 14 Jun 2013, at 18:
Could therefore be argued that module creation tools with a GUI interface would
also exploit markup features that the API doesn't support at the present so
they'd be in the discussion too.
On 14 Jun 2013, at 18:28, Chris Burrell wrote:
> I think David mentioned the Python script, because curre
Sorry, but isn't Bibledit a graphical module editing tool?
It is freely available in most GNU/Linux repositories not sure about
windows, though... Though, a GTK application very well might work in
windows...
On 06/14/2013 12:32 PM, Trevor Jenkins wrote:
Could therefore be argued that modu
Bibledit can already export to OSIS - but further conversion is required to
make a module.
It can call the latest version usfm2osis.py (with options to use alternative
scripts).
It's checked every 24 hours for any available updates.
And (in the context of Pola's reply) Bibledit is for Bibles, not
ditor (.net) but still
thinking in how to make it more generic to support more osis elements over time
> Date: Sun, 16 Jun 2013 01:59:25 -0700
> From: dfh...@googlemail.com
> To: sword-devel@crosswire.org
> Subject: Re: [sword-devel] After SWORD v1.7 gets released?
>
> Bibledit can
or are willing to
spend considerable time on learning usfm
Sent from my HTC
- Reply message -
From: "Pola Edward" <5...@hotmail.com>
To: "SWORD Developers' Collaboration Forum"
Subject: [sword-devel] After SWORD v1.7 gets released?
Date: Sun, Jun 16, 2013
12 matches
Mail list logo
