[sword-devel] Future MacSword
Troy A. Griffitts
scribe at crosswire.org
Tue Mar 11 12:14:31 MST 2008
I think your ideas are exciting. My only thoughts (which you've likely
already considered) are that it would be nice to package an official
bundle of the beta at sourceforge. This would allow pre-Leopard users
to have something usable with our latest modules. It might be nice to
also include your module installer in that bundle if it's not too much
work. But I don't think making Leopard a requirement moving forward is
a bad idea, as long as we have some fallback mechanism for less
fortunate users. Thanks for all your work. I realize I haven't given
any time to assist your work, so my comments here are merely my
thoughts, for whatever they're worth.
Manfred Bergmann wrote:
> Although MacSword is quite old and it would be more than time for
> something new I found that it will still take a good amount of time
> until something usable is there that can replace MacSword.
> I'm the only one developing in this area ATM and was quite busy with
> my daily work the last months/weeks, so it hasn't gotten as far as I
> would have liked it.
> I have put many hours of work into refactoring the Sword Objective-C
> Backend (coming from MacSword) and in a module installer that is now
> in Eloquent (btw: a new version has been released with some
> My thinking was that until something new is there I would branch
> MacSword and backport the backend and the module installer into
> MacSword. The UI would stay the same and it would be a Leopard only
> IIRC the majority of users that had questions about MacSword actually
> were using Leopard.
> Altough the UI of MacSword is hardly usable in iPhone, having
> something Leopard compatible or Leopard only would ease the port to
> iPhone tremendously.
> What are your thoughts about this?
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel