[sword-devel] frontend features, their applicability -- consistency?

[jonathon]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Karl Kleinpaste wrote:

> It *cannot* do what a laptop or desktop does, 

The typical smartphone sold today, has the same amount of RAM as the
typical desktop of five years ago, and the same amount of storage as the
typical desktop of a decade ago.

The biggest limit on what one can do, is inflicted by the locking down
of the OS by the cell carrier/device vendor.

> fond fantasies to the contrary notwithstanding.

You might not be able to get an iPhone, or Android to do what a laptop
or desktop does, but that does not mean that it is a fantasy to do so.

I wouldn't want to use a smartphone for writing a novel, or calculating
Mersenne primes, or calculating the graphs that are constructed by the
application of Catastrophe Theory. But those are done, and in the first
instance, is a genre of Japanese literature.

>but it is not and never will be a general study app.

Olive Tree did a partial presentation on an iPhone at the SBL Bible
Software Shootout. The biggest obstacles were the lack of resources, and
 that the specific functionality was not yet working in the iPhone
version. Screen estate, or lack thereof was not an issue.

I won't be surprised if, by BibleTech 2012, the only difference between
Olive Tree and Logos (both mobile and desktop apps, for both
organizations) are in the resources that are available.

Personally, I think that the biggest issue with using mobile devices is
 the lack of storage. The small screen estate is a secondary issue. One
that can be, and has programmed around. (Yes, that means that you can
have a commentary follow a verse, and a dictionary follow the word, and
each be visible to the user.)

jonathon
- --
Non-list email sent to this email address is forwarded to Dave Null, unread.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkvSJbAACgkQVyQBHg3MfvR5dQCfXTBP28rWC2xfiEZFluXPZ2gq
o00AniEEdWvPLm6McooTzAXeifxJtL6M
=+GOc
-----END PGP SIGNATURE-----