🚀 go-pugleaf

In article <13725@well.UUCP> svc@well.UUCP (Leonard Rosenthol) writes:

>	If the fact that the program resaves TEXT with a different creator
>and kills the resource fork is so '<<effeely>> unusuable' then do tell
>what you use for a word processor??  Since all of the major WP's for the Mac
>all have this deficiency (and I do agree that it is one!), then I guess you 
>don't use any of them, eh???

        Right you are, I don't use any of the existing WP:s save for an
        occassional post-edit in WriteNow 2.0 or Word 3.0.1.  Originally
        I used *only and exclusively* the word-processor inside the MS
        Works, which I find a fairly good job as far as simple writing
        tools go... and it ain't that simple (ie, primitive) either.
        However, for serious writing-cum-programming and editing of
        downloaded text-files (of which I have plenty) I exclusively
        use the McSink/ Vantage text processing DA.  I found that both
        your own Sigma-Edit and a french product "Joli Write" would give
        me similar functions (though McSink has more of it incl. a limited
        macro-language).  Simply put I distinguish between the text creation/
        writing stage (when I wouldn't play with multiple fonts and sizes
        anyway) and the editing/ formatting stage during which I might add
        some formatting commands that are not available from within McSink
        (that, being a "text", not "word", processor is limited to one font
        & size per window, although it can handle 16 open windows simulta-
        neuosly).  Apart from a nice set of built-in programming-related
        functions it is also *very fast*, especially when jumping in steps,
        works nicely without a mouse and coexists happily with other appli-
        cations.  It's not perfect but then, neither am I... ;-)


>	As to your question about where Paragon sees Nisus in relation to
>MSWord, that's a good question.

        Obviously, they are trying to go after both the MSWORD-market and
        to provide the programmer community with a successor to the QUED.
        The will was there, allright, although the execution leaves a lot
        to desire.  I must admit that Nisus is admirably inspiring in some
        parts (the DFLT resource in every doc; configurability of user
        interface, even the non-standard option-scrolling (=instantenous
        reverse-direction scrolling)) and, clearly, with a lot of oomph.
        In most other respects however, mainly due to its slow jumping and
        menu-decoding speed, it is a disaster.


>	According to the 'Nisus Quick Reference' card sitting next to my
>Mac (I keep it there for GREP reference), there are indeed way to do all the
>movement that you requested (jump to beg/end of doc, etc.) from the keyboard

        Jump to beg/ end of doc keybord-shortcuts merely call the interpre-
        ted macro functions.  This is *progress*?


>	As to the speed of the Macro Language, I agree that it is far from
>fast (and far from perfect  by any stretch of the imagination), but remember
>that it is the ONLY WP with a builtin Macro language

        Oh, I don't mind the macro-language being slow - it is always
        faster than hand-keyed-process alternatives.  I merely object
        to having strictly *primary* jumping functions implemented as
        macros instead of being hard-coded (which is NOT the same thing 
        as being hard-wired to a particular (command-)<key>)


>	(I will agree with you that there are a number of 'not-quite-well-
>designed features though...)


>    product support where it really
>>   counts.... which should be right here, on usenet, and _not_ primarily
>>   available only by telephone within the geographics limits of US of A.
>>   Geography and user-support don't mix!
>>
>	That is such a wonderful idea, but since not EVERYONE in the world can
>get, or wants to get an account on a machine with USENET/Internet

        True, but, aren't we here the *CUTTING EDGE* of the _global_
        Macintosh community?  If not us, then who?  If not here then where?
        Paragon, if they are serious, should at least care about being
        visible here, question of support notwithstanding.

        So, it looks like it is TXXT next for me... 
-- 
----
------ ianf@nada.kth.se/ @sekth.bitnet/ uunet!nada.kth.se!ianf
----
--