<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>I think we also need to focus in module creation tool (with GUI) to encourage more people to create modules<br>Also some more documentations and tutorials will help developers to make such GUI tools<br>Using the Open 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 <br><br><div>> Date: Fri, 14 Jun 2013 01:24:20 -0700<br>> From: dfhmch@googlemail.com<br>> To: sword-devel@crosswire.org<br>> Subject: [sword-devel] After SWORD v1.7 gets released?<br>> <br>> Looking ahead - as a module maker rather than a developer.<br>> <br>> Do we have a roadmap / planning page to discuss what should be done in SWORD<br>> v1.8 ?<br>> <br>> One thing concerns me which immediately springs to mind.<br>> <br>> * Require support for all the new custom OSIS elements and attributes that<br>> can be output by Chris's usfm2osis.py script.<br>> <br>> David<br>> <br>> <br>> <br>> --<br>> View this message in context: http://sword-dev.350566.n4.nabble.com/After-SWORD-v1-7-gets-released-tp4652548.html<br>> Sent from the SWORD Dev mailing list archive at Nabble.com.<br>> <br>> _______________________________________________<br>> sword-devel mailing list: sword-devel@crosswire.org<br>> http://www.crosswire.org/mailman/listinfo/sword-devel<br>> Instructions to unsubscribe/change your settings at above page<br></div> </div></body>
</html>