> From: Stefan Matthias Aust <sma at 3plus4.de>
>
> I don't think that Squeak is really capable of doing word processing. 

While I don't think that is 100% true even now, what we should  
really do is fix it, righ?!

[..]
> - Just one font per document

As far as I can tell, this isn't true.  At least it sure looked like  
I had to map more than one font to Postscript when outputting "Back  
to the Future" in tests.

> - No printing other than creating a bitmap (GIF, JPEG) or a postscript 
> version of a morph.  And the latter wouldn't support other fonts  
but Times
> I think.

The Postscript support should be easily adaptable to other formats,  
such as PDF or maybe even WMF.  It definitely supports more than one  
font!  In fact, there is a multi-level approach to mapping the fonts  
used in the document to something that will hopefully be available on  
the target printer.

> - No tables

TableMorph anyone?  Haven't checked, but I am sure there is  
something that could be adapted (or whipped up quick enough -> too  
bad I am not proficient with Morphic yet, just had a go at the  
plumbing so far...)

> - No easy to use support for indentation and tabulators (I think, the 
> paragraph objects alrady have some basic support for this but probably 
> again only for the whole document and there's no GUI yet)

AFAIK, it's a per-paragraph setting.  Paragraphs are fairly  
flexible.  Actually a little too flexible in some respects because  
attributes are handled via a call-back mechanism, making it fairly  
difficult to statically analyze the style settings (for output or  
interchange).

> - No support for long documents.  A workspace for example becomes  
dead-slow
> if you want to edit 1MB or more.  Winword is still very fast.  Even my 
> little faithful NotGNU editor can handle this without problems.

I think some of the algorithms used need fixing.

Marcel