Re: CDATA

Horatio;
    Obviously there has been a HUGH amount of mis-communication and behind
it all is that we come at the same thing differently - you from a GUI
environment and me from a console environment. What you are explaining I
already know, but the structure of Amaya to function primarily as a GUI
interface is not going to be useful to me at all - to many others,  'yes' it
will be useful. Best of luck in your development.
                                       - Mark

Mark Lee
Smithsonian Institution
Electronic HelpDesk & Software Distribution System Webmaster
mlee@sivm.si.edu

----- Original Message -----
From: "Horatio Davis" <horatio@qpsf.edu.au>
To: <www-amaya@w3.org>
Sent: Thursday, January 24, 2002 5:32 PM
Subject: Re: CDATA


>
> On Thu, 24 Jan 2002, Mark Lee wrote:
>
> >     A file, once it has been hauled into an editor, only represents a
> > suspended 'snapshot' of the currently active file. Until the file is
saved
> > neither it nor the script it contains are active.
>
> Looking at the original post, I had thought you originally asked why
scripts
> were not executing in Amaya - which Laurent answered by saying that wasn't
> implemented yet. Scripts are useful because they make documents
interactive
> - in other words, the state of the document changes over time. Editing a
> moving target is an awkward challenge, but some documents depend on their
> script components in order to present properly, so editing them without
> scripts active is awkward also.
>
> Did you only want Amaya to execute scripts when not in editing mode?
>
> >     Why Python? I am curious because I have only encountered comparisons
> > between Python and Java or C.
>
> Python is designed to be embedded in things, and I like the stuff.
>
> -- Horatio
>

Received on Thursday, 24 January 2002 17:53:27 UTC