I agree that there should be a separation of logic and presentation elements, I do that as much as possible.
In GoLive's dynamic content examples, the php, jsp and vb code is merged within the html files. Not an ideal situation from my perspective. I don't know if this is necessary or not for new dynamic content formats. In any case, the GoLive SDK manual is pretty hefty, 400-some-odd pages. It would take some serious time investment to develop perl ports of the included examples (a calendar, shopping cart, etc.). If Adobe were paying me to port the examples to perl? Sure. But for free? I don't have that much time available. Perhaps a motivated student would, but ideally Adobe should throw some resources at the question, assuming enough people want the feature. Cheers, Troy >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. At 10:17 PM -0400 10/3/02, 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. > >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. -- _______________________ Troy Davis ACD Interactive Slipstream.com 205 W. 4th St. #1130 Cincinnati, OH 45202 USA Tel - 513.241.4444 x119 Fax - 513.241.1107
