RE: INTRO

> dialogs we are getting. Other issues include; the footprint and the
> speed of the app.

By footprint, do you mean its size on disk, the number of dependencies, how
much RAM it uses when running, etc?

It is in our interest to reduce all of the above (via optional build-time
features). I would also add to this; less CPU intensive. We have AbiWord
'working' on the device but it;

A. crashs - presumably due to lack of memory (32 meg in this case)
B. is very sluggish - even just typing text
C. dialogs do not scale down to our limited screen res

> All we need is the basic functionality of AbiWord.

I don't know what you mean by that. Care to explain?

Well - stuff like;

A. type text with; normal, bold, italics, underline
B. use a variety of fonts (even a small set would be fine)
C. the usual page and paragraph formatting such as; justification
D. embed images

> I gather that some folks did a Nokia 770 port and perhaps I can build
> on that?

Yeah. All of their modifications are in our source tree, if you want to look
at them. It includes some code changes to better integrate with their
"Hildon"
framework, some code changes to strip out unecessary features (like
printing), and some modified dialogs, for their constrained screen size and
modified feature set. All of this is documented in the mailing list
archives.
  
Yes; I think this is a good start for our work and I will be looking at them
asap.

> Would my work be of interest to the general community or should I just
> hack the code for our specific purposes?

It might be. I don't think that you've said enough about what modifications
you'll make or how you plan to achieve them for us to answer your question.

Generally, I'd rather do development in our tree.
There's always the chance that what you do will be useful for someone else
in the future, provided it doesn't disrupt the rest of the application too
badly (and is maintainable).

Understood - thanks!

Peter
Received on Wed Feb 15 23:56:34 2006