At 9:42 PM -0500 10/3/2002, Puneet Kishor wrote:
>On Thursday, October 3, 2002, at 09:17  PM, Sherm Pendley wrote:
>>Why would you expect it to? Golive is a WYSIWYG HTML editor - the requirements for 
>which are a great deal different from those of a good Perl editor.
>
>so why does it offer support for coding php, asp, and other server side scripting 
>languages? the truth is that it is _primarily_ a wysiwig html editor... but if you 
>were to think of it as a web application development IDE... then it would make sense 
>to offer some basic scripting support (which it does, except not for perl), or a darn 
>good integration with a (or several) external editors.
>
>>[...]
>
>much of the time my html code itself is governed by some server-side logic... hence 
>perl (or any other scripting language) really becomes the generator of such code 
>(hence the existence of stuff like embperl and mason, etc.).

I think the crux of the issue is that, for the kind of support these wysiwyg editors 
provide and for the market they're targeting, plain-vanilla perl support doesn't make 
any sense at all. If they were to code for Perl, they would need to choose between any 
one of the Templating environments and support that - TT, Mason, embperl, etc. As far 
as I can tell, they are interested in documents that look like SGML and behave 
more-or-less similarly to HTML. And, in the intrinsic tmtowtdi nature of perl, there 
is no single canonical way to dress up an HTML document to include perl code.


-Charles
 Euonymic Solutions
 [EMAIL PROTECTED]

Reply via email to