jonmmorgan at gmail.com
Fri Mar 20 02:54:20 MST 2015
>From the point of view of an outsider to the decision making process, I'm
concerned that you are preventing access by the many for the benefit of the
Of course, I don't know the exact time-frames we're talking here. If it's
a case of an extra few months on top of a process which has lasted years it
would be reasonable.
If it ends up much longer, then I think the cost to users of other
frontends is much greater than the benefit of this policy.
This particularly applies as (as I understand it) the NASB will be a "for
sale" module which could have a clear disclaimer "this will not work
properly with BibleDesktop" and probably won't be immediately available for
sale the day you sign off on it (I find Greg's "the next step in the
process" comment ominous).
On Fri, Mar 20, 2015 at 8:31 AM, Greg Hellings <greg.hellings at gmail.com>
> I'm waiting on DM to release the new version of BibleDesktop which has
> several style handling improvements utilized by the NASB. Troy has
> mandated that the module appear properly in the main desktop
> applications, and that's the last one to come into line.
> Once that's done, then we can move on to the next step in the process.
> On Thu, Mar 19, 2015 at 7:28 AM, David Haslam <dfhmch at googlemail.com>
> > Greg Hellings took up the NASB project.
> > David
> > --
> > View this message in context:
> > Sent from the SWORD Dev mailing list archive at Nabble.com.
> > _______________________________________________
> > sword-devel mailing list: sword-devel at crosswire.org
> > http://www.crosswire.org/mailman/listinfo/sword-devel
> > 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
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the sword-devel