At 11:48 -0600 3/22/06, Ralph Mitchell wrote:
>OK, I'm completely iggerant about Applescript and Safari, but why
>couldn't you use curl to telnet to the webserver and simply send that
>text?? It's not curl that needs to handle the javascript, it's the
>target system. Curl would just see characters to send, right??

You would need a login account at the webserver and that's unlikely.

The webserver would have to be Mac OS neXt and that's unlikely too.

Apple does allow AppleScripts to be executed remotely but the feature is turned off by default because of security risk.

The only thing I have ever needed JavaScript for with curl is to do some calculation required to present a challenge and response kind of thing as a cookie or POSTing as a part of a login process. So far it's always been possible to emulate the calculation in perl. In many cases it's simple enough to extract from an iCab log file (equivalent to LiveHTTPheaders). Changing the format of a date is common and perl makes that really simple.

Most JavaScript in pages is devoted to generation of fancy GUI thingies and system-dependent pull-down menus. Getting rid of dancing gerbils is what curl is all about anyway.

Content insertion using downloaded css-3 files is what really worries me for the future.

-- 
Applescript syntax is like English spelling:
Roughly, but not thoroughly, thought through.