WebStar works! But it seems correct that FileMaker does not. But isnt
FileMaker really an Apple product? And they have no osx version yet?
The tango plugin seems to be a problem, but I havent tried very hard
yet. Tango acgi I havent used, but I guess I have to rebuild all the
files if I have to switch?
Hallvard
P� mandag, 30. september 2002, kl. 17:08, skrev John Schroeder:Hallvard,
>
> I've never tried it, but I read (when OSX first came out) that WebSTAR
> would not run under OSX Classic. I do not know if this is true or not.
> I believe that the acgi was able to run under OSX Classic, and I know
> that FileMaker does also run under classic. How OSX handles AppleEvents
> is unknown, since they changed it a bit in OSX.
>
> I would be curious to know your results.
>
> Regards,
>
> John Schroeder
> On Saturday, September 28, 2002, at 02:40 PM, Hallvard wrote:
>
>> Is there any experience out there with using the tango 3.5 plugin og
>> acgi to webstar 4.* under mac os X/classic?
>> I saw some questions about this in the list search, but with no
>> conclusion on it.
>> I would like it if I could make my taf-files and filemaker databases
>> work under os x, but I plan to migrate to apache, and then I suppose
>> I�ll have to redirect requests to these domains to webstar on a
>> non-standard port, and run it on classic mode.
>>
>> What about the tango 3.5 editor - is there anybody with any
>> experience in using it on osx?
>>
>> Hallvard, Norway
>>
>> ________________________________________________________________________
>> TO UNSUBSCRIBE: send a plain text/US ASCII email to
>> [EMAIL PROTECTED]
>> with unsubscribe witango-talk in the message body
>>
>
> ________________________________________________________________________
> TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
> with unsubscribe witango-talk in the message body
>
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
