well... On Thursday, October 3, 2002, at 09:17 PM, Sherm Pendley wrote:
> On Thursday, October 3, 2002, at 10:01 PM, Puneet Kishor wrote: > >> I have Golive 5, but didn't invest in 6 because I discovered it >> didn't do anything for Perl. > > 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. > > Furthermore, your HTML code shouldn't be in the same file as your Perl > code anyway - good programming practice dictates putting it in an > external template. There are literally a dozen or more CPAN modules > for "filling in the blanks" when using such templates - my own > favorite is Text::Template, but your mileage may vary. > that, seriously, is a matter of choice. *shouldn't* is a strong word... unless I am developing a text-oriented, blogging kinda tool, or a template driven "news site", 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.). Of all the applications I have worked on to-date, I really can't think of a single one where I could have successfully separated the logic from the presentation, programming from the html-ing, no matter how good a practice it is supposed to be. pk/
