At 3:48 pm +0000 02/02/01, John Delacour wrote:
>At 4:25 pm +0100 2/2/01, Andreas Marcel Riechert wrote:
>
>| Even if we won't get a new text editor in the next release, it seems to
>| be a good idea to think about the features, the next editor should have.
>| I think -- because Perl is moving more and more in the Unicode
>direction --
>| a minimum requirement should be Unicode awareness.
>| Therefore, at the moment I see two possible text-engines as a base:
>|
>| Waste >= 2.0 ... still Beta. ( http://www.merzwaren.com/waste/ )
>| or
>| The Multilingual Text Editor (MLTE)
>
>| Unfortunately MLTE seems to require MacOS 8.6 or higher.
>| So both engines do not seem to be "the best choice".
The WASTE web site gives a table summarising the main features of
TextEdit, MLTE and WASTE as follows:
TextEdit MLTE WASTE 2.0
Underlying Rendering Layer QuickDraw Text ATSUI QuickDraw Text
Minimum System Requirement 6.0.5 9.0 7.1
68K Support * *
Carbon Support * * *
>32K text * *
Double-byte Script Support * * *
Bidirectional Script Support * * *
Inline Input * (with TSMTE) * *
Character Formatting (Styles) * * *
Paragraph Formatting (Rulers) *
Full Justification * *
Tabs * * (with WETabs)
Undo/Redo * *
Drag & Drop Editing * *
Embedded Objects * *
Unicode Support * *
At 2:09 pm +0000 05/02/01, John Delacour wrote:
>I'm way out of my depth here but I have a feeling it might be easier
>than you fear. It would probably be worth dropping a line to Tom
>Bender, the author of Tex-Edit Plus, who was one of the first to use
>WASTE and has, since his original Tex-Edit, always grabbed the
>latest and nicest text engine for the program. He might even be
>prepared to some work on it -- so might Marco Piovanelli himself.
>
>Just a thought.
You couldn't possibly be as far out of your depth as I am, but I very
much like the thought of writing to Marco Piovanelli and will follow
that up in the first instance.
At a first and very superficial look at WASTE the calls are closely
similar to TE so it might not be such a huge undertaking to replace
the one with the other in the MacPerl source files. However TE calls
occur all over the place in MacPerl so it certainly isn't going to be
that easy either.
Can anyone give a complete list of all the '.c' files involved in the
editor? And has anyone any idea how to separate them off for
experimental purposes so that the editor might be developed without
having to build the whole of MacPerl every time?
AF
