Kino wrote:
>On Thursday, October 24, 2002, at 06:27 AM, Geoffrey Heard wrote:
>
>> At 12:15 AM +0900 24/10/02, Kino wrote:
>>>
>>> But at least perl is not so verbose and wordy as AppleScript. And
>>> perl is cross-platform, so much more worth trying than AS, I feel.
>>
>> I hope NW does have its own internal scripting language and that it
>> does work with an external, cross platform scripter.
>
>Me too, I hope so. With external scripting languages, it is almost
>impossible to manipulate style and formatting which are crucial when we
>use a word processor as a word processor. If an *intelligible* tagged
>text format will be adopted by NW X, perhaps it will not be so hard to
>control style/formatting with an external program though.
I to hope that the scripting language of NWX will be better than the scripting/macro
language NWClassic has... Because even today we can't control styling with help of the
macro language ;-) To do that, we need to use the menu command language. And the menu
command language is in principle noth different from AppleScript, which *is* and
external thing. Why is it not different from AppleScript? Well, just look at the
editor Style from www.merzwaren.com.
Style supports all scripting languages based on Apple's Open Scripting Architecture,
like Frontier. (Btw, doesn't also (Mac)Perl belong to those languages, all so?) Style
is scriptable, recordable and attachable; it has an easily customizable Script menu
and supports Frontier's menu sharing protocol.
For instance, just now I opened AppleScript's ScriptEditor and turned on recording and
recorded this script, within two secounds (and when I saved it I could activate it
from a menu withing Style):
tell application "Style"
activate
select contents of document 1
set size of selection to "72 pt"
set font of selection to "AvantGarde Bk BT"
end tell
I.e. and external language that control another editor to a greater extent that the
macrolanguage of NW. (Allthough in NW we can say that the way its three macro
languages works together creates a fourth meta language...)
But I cannot imagine that NWX would not support AppleScript? But will it support it to
the same deep extent as Style does? If it dit, that is: if it supports Apple's open
scripting architecture, even Frontier would be supported! Anyhow, if I can record and
NWX action with the same ease as I can do it with Style, then I will not care whether
the scripting language is external or internal. IN fact I would prefer that it was
external, so that the things I learn can be used in other programs as well.
>> In my view, to grow, Nisus needs to become cross platform. The
>> platform wars are hotting up, and NW running on Linux, for example,
>> might find a useful niche. Running on Windows is the other step, of
>> course, and again there could be a useful niche market.
>
>I'm afraid porting a Cocoa application to another platform is not easy.
>Many functionalities of a Cocoa app seem to depend on frameworks which
>are not be found in another platform.
I believe that depends on how you make your app... The just killed Pepper ran on Mac,
Windows, Linux.
--
leif
---------------------------------------------------
The Nisus Interactive List
[EMAIL PROTECTED]
Searchable archives:
http://www.mail-archive.com/nisus-interactive%40nisus.com/
To unsubscribe from this list please send a message with "unsubscribe
nisus-interactive" in the body of the email to [EMAIL PROTECTED]
