At 9:01 PM -0500 2002-10-03, Puneet Kishor wrote: >I have Golive 5, but didn't invest in 6 because I discovered it >didn't do anything for Perl. Is the SDK GL6 specific? I have no idea >what knowledge it >On Thursday, October 3, 2002, at 01:18 PM, Troy Davis wrote: >> I use GoLive to create websites. But I use BBEdit to work with >>perl. The two can co-exist, but you're right in that they're not >>very good roommates. >> I'd love to see a module to replace the php dynamic database stuff >>with perl... >>Puneet: >>> The reason I need something like Dreamweaver or Golive is because >>>I don't want to use my finite braincells remembering syntax for >>>silly html for making tables, frames, hex colors, and other such >>>stupidities. Doing that nonsense visually makes developing web >>>apps tolerable. Even more so when you have to go back and edit >>>some convoluted frames and/or tables code.
Perhaps because I taught HTML for five years in the early days, and insisted that my students work without visual HTML composers (which were terrible, besides), I never adopted GL, DW, etc into my own workflow. When my projects have web output, all the HTML is generated by my software, i.e., Perl. Maybe this doesn't get at the problem you're trying to solve, but with a modest investment of time you could equip yourself with Perl tools to do everything you need, including eliminating the tedium of composing in raw HTML. There are several versatile HTML-generating modules on the CPAN, and most use some form of templating. I've built my own templating and output module, so I can't make a recommendation, but others on this list would happily. A complete "web application" development library could be assembled from a set of well-maintained Perl modules from CPAN. Your module would 'use' or 'require' DBI.pm, CGI.pm, File::Spec, etc, collecting these powers together to be harnessed in your own methods. That wisdom aside, Puneet's posts suggest interest in a programming challenge to learn from, which was the impulse I followed... For my projects, I have to be able to send output in many formats, often not HTML, not even network-related (database, spreadsheet, page layout, postscript). So I wrote a templating module that can dispatch methods from external libraries in response to whatever string of tokens it's fed. For HTML output, I have a module whose methods dress up the data they're passed in the HTML format evoked by the token; if an output method fails, the token is output as an HTML comment. Thus the only place in my programs that any HTML appears is in the methods (subroutines) specifically employed to produce output in this format. Program control, state transitions, database operations, math, date-time calcs, image generation, and so on, have none. This is where I see the dividing line between logic and presentation. It's a thinko to look at the code and the template as representing that distinction. Speaking of templates, I have HTML templates of all types and sizes: one-line dynamic input widgets; whole 'pages' with headers n' everything; standard input forms; sub-templates nested within master templates; dynamic style sheets... The output from my html-generating methods is also beautiful :-) That is, it's just the way I like it: correct HTML usage, easy to scan if I view source, follows my prefs for indentation, capitalization, etc. I also have templates for use during development, e.g., to throw the necessary data and control buttons onscreen, but without the ultimate art and typography. Sometimes all it takes is a style sheet to spruce it up. Forgive me for going on if you know all this, but let me add one more thing about Perl-generated HTML: it has two distinct uses: direct dynamic output, which the web server returns to the client; and output to file, for web resources that update on a time period or upon some event other than an http request. The latter is, in effect, what the visual editors do: output to a file to be used as static HTML. Why not build your own? 1; -- - Bruce __bruce_van_allen__santa_cruz_ca__
