-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.
Th
Ahoi.
I don't actually care so much about bookmark consistency. And if so then mainly
between PS and MS because Mac users maybe will have an iPhone and want to sync
their bookmarks. But I haven't heard of such feature requests.
Generally though for the sake of features it would be great to be ab
Somewhat related: when talking about syncing user-created content, I found
Craig Rairdin's BibleTech:2008 talk "Beyond Mobility: Synchronizing
User-Created Data Between Platforms, Readers, and Vendors"
interesting (though I'm not sure that it solves all of the problems, because
some of them fundame
On 04/14/2010 01:41 PM, Karl Kleinpaste wrote:
Anyhow, I fear the discussion is reaching far afield from my original
questions, which revolved around the question of consistent baseline
user experience and what we ought to require (in some fuzzy sense) of
Sword app teams' development.
What does
Hi All!
Jesus, help us to find right solution.
Simply I think every new frontend should use much of existing source code
and existing standards. If there would be bookmark framework in Sword i
used it.
Karl Kleinpaste:
Xiphos has implicitly extended the semantic of that bookmark format,
simply
Hi All!
Jesus, help us to find right solution.
Simply I think every new frontend should use much of existing source code
and existing standards. If there would be bookmark framework in Sword i
used it.
Karl Kleinpaste:
Xiphos has implicitly extended the semantic of that bookmark format,
simply
Karl,
Great thoughts.
Regarding real users asking for cross-application compatibility for
Bible Desktop, we've only ever had a couple. The biggest is that an
installed base of modules can be used. This typically is of the form:
"I've given up on windows and have a some modules that are no long
Am 14.04.2010 um 18:41 schrieb Karl Kleinpaste:
>
>> ps: I reckon that bookmarks sync between PS and a desktop would be a
>> manual process (in that you need to hit a button to do it, rather than
>> it all being automagic cloud-based syncing), so it would be something
>> you could opt out of, fo
Nic Carter writes:
> But perhaps this is the time for me to say I'm considering cutting
> support for the GenBook format? The iPhone has the kindle app, has a
> very cool CCEL app & is about to get the iBooks app (from Apple), so I
> can't see much point.
That would be unwise. The availability o
Karl Kleinpaste wrote:
>
> Nobody real cares. Real, in the sense of being a general user of our
> software, as opposed to us, who are stuck on features for features'
> sake.
I think you are probably right there. Unless we move a whole way further
and allow a explicitly partial import and export
On 04/14/2010 12:50 PM, Nic Carter wrote:
> But perhaps this is the time for me to say I'm considering cutting
> support for the GenBook format? The iPhone has the kindle app, has a
> very cool CCEL app & is about to get the iBooks app (from Apple), so I
> can't see much point.
I would be very sad
Peter von Kaehne writes:
> Part of the reason is probably general direction of user mobility.
> People move Windows->Apple or Windows-> Linux, but after a bit of
> messing around, few move Gnome->KDE or vice versa.
Perhaps. But if, as you suggest, ...
>> Xiphos uses the exact same bookmark stor
Nic Carter wrote:
> But perhaps this is the time for me to say I'm considering cutting
> support for the GenBook format? The iPhone has the kindle app, has a
> very cool CCEL app & is about to get the iBooks app (from Apple), so I
> can't see much point.
Only that GenBook is a format which does no
Ok, I'll keep this brief cause it's 2:30am & I'm on my phone, but I
pretty much agree with Karl.
Re: bookmarks: PocketSword has a 2 min worth of effort implementation
in there atm. This WILL change soon, as with loads of other features.
I get to play catchup with all you big boys, cause I've
Thanks Karl, this is brilliant!
Karl Kleinpaste wrote:
> This brings a couple problems. First, we have the necessity of the
> interaction: Does the user allow this to occur? If the user declines --
> for now, or forever -- then we are left with an application that still
> must provide bookmark s
Karl,
This is a superb essay. I love it when programmers extensively philosophize
like this.
And yet, is a mailing list the best place to communicate deep and detailed
thoughts such as these?
It's not the kind of material for a wiki page either.
IMHO, This sort of excellent content is really be
I've had some philosophical meanderings about frontends over the last
several weeks.
One of the best things about The Sword Project is that a whole herd of
applications has been able to grow up around the core engine. Support
constructs based on platform capability, workflow ideals, toolkit
provi
17 matches
Mail list logo
