Hi Wolfgang,
On Wed, 2010-03-10 at 13:13 +0100, Wolfgang Stradner E wrote:
Hi Teus,
Thinking of building Bibledit from scretch, perhaps the following dream
could fit in:
Low Power Computing List:
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Hi,
Thinking of a Scripture processing tool for Balsa (Basic affordable
language software applicance), why not dreaming about something? And why
not dreaming big?
What about a tool which
- looks very much the same as Paratext (=PT): PT is actually the most
used Scripture processing tool for Bible translators. I remember that
(at least earlier versions of PT tried to be similar to MS-Word (which
many people used for Scripture processing at this time) in order to make
it easier to learn to use PT,
The way of of doing things on the web differs a lot from how things are
done in a desktop application. There's a lot of clicking on the web, and
going to other pages, which means that the layout of the "program" keeps
changing all the time. Desktop applications such as Paratext usually
keep their well-known layout. For that reason it won't look like
Paratext. But this would not be a problem, since people once use to the
web should intuitively understand how to navigate in bibledit-web.
- does a good job in Linux as Bibledit (Bibledit was built for Linux and
is working there successfully since many years) and
Sure, it should do a good job there.
- has the capacity to connect to Fieldworks (in a way the Translation
Editor does)
I am not sure what this is for at the moment.
and allowing to switch on/off features so that can be used in a very
simple way (working with and without cloud computing) ...
The services offered are going to be diverse, since the bibledit-web
would have administrators, managers, translators, consultants, members,
and finally, visitors who are not logged in. Each of the groups of
people mentioned above will have appropriate capabilities. Visitors have
the least options, members a bit more, and so on.
Teus.
wolfgang_stradner.vcf