[sword-devel] iPhone frontend alpha screenshots
iwagn973 at students.bju.edu
Mon Nov 24 07:20:12 MST 2008
I've had this suggestion given to me a few times now by friends and I
really like the idea behind it. I'm not entirely sure why everyone has
always done chapter by chapter, but it just seems to have been a
convention for a very long time. The SWORD API actually grabs by
verse, so it wouldn't make much difference in implementation. The
only difference might be a slightly longer load time. I believe that
the way the iPhone SDK's widgets work, I would have to load everything
before displaying it. I'll go play with that and see how much
difference it makes speed-wise.
As for the name, I think that could cause some confusion as to being a
PocketPC app. I would have preferred something like iSword, but that
name is already in use by someone developing an iPhone SWORD web
application (the project looks to be inactive though). If anyone has
any name suggestions let me know.
There's no place like 127.0.0.1
On Nov 24, 2008, at 9:04 AM, seb.sword at koocotte.org wrote:
> On Mon, Nov 24, 2008 at 07:05:28AM -0500, Ian Wagner wrote:
>> Please let me know any ideas/suggestions you have.
> Really nice !
> I have one suggestion you may find irrelevant: Don't cut on chapters
> but on
> I know that most (all?) sword frontend are displaying text chapter by
> chapter, and sword-API is probably build this way; but I think it's
> a very
> bad idea. Chapters and verses are a common and useful way to locate
> a text
> fragment, not a way to cut text. This create artificial separations.
> for Psalms, books are a more relevant separation, text was not
> written in small parts.
> This may requiere a more tricky usage of libsword, keeping 3 or 4
> at the same time to display text as if it was the full book.
> Seb, autocuiseur - La koocotte ® - 06 12 05 65 94
> sword-devel mailing list: sword-devel at crosswire.org
> Instructions to unsubscribe/change your settings at above page
More information about the sword-devel