Re: [cgiapp] FYI: CGI::Framework
On Jan 11, 2004, at 10:22 PM, Peter Chen wrote: On Jan 10, 2004, at 5:12 PM, John Lawton wrote: If you want to trap templates you can match _tmpl.html instead. C::A also has some design decisions that turn people off. (I like C::A) -john You are missing my point. To me, .html indicates that it is HTML. A template is not HTML. In my experience, a file name or a file extension should be indicative of the content and function of the file. If you are using HTML template the your file is probably html with a few template directives. For all practical purposes its HTML. This is something that I learned the hard way in the last 15 years. Then again, your mileage may vary. Two reasons that I wouldn't recommend your approach: If you are using professionals to design your pages their software may not know how to deal with your .tmpl files. If you keep it as HTML Both inDesign and DreamWeaver can handle the Template directives. When you have hierarchy of template that generate other template files you do not want to start coming up with a bunch arbitrary file extensions. I stopped doing this when I worked on a project that had templates that generated HTML templates. I didn't want to create an additional extension to differentiate the two template files. Your system doesn't scale very well with the complexity of the problem. One way to handle this is to add _tmpl1.html and _tmpl2.html to denote different template types. You can filter using a slightly different apache directive. You will not get burned if you do it this way For reviewing modules, and deciding whether they are worth the time and effort for further investigation, I find these small details revealing regarding the amount of effort and thought or the level of software engineering discipline that were put in. If you are concerned about the architecture of a module then look at its source. Personally as long as the module is useful and works properly I am not too concerned about how it is implemented, unless I am maintaining it. -john - Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiappr=1w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [cgiapp] FYI: CGI::Framework
On Jan 10, 2004, at 2:52 PM, Eric Frazier wrote: That seems like a pretty minor point to me. I use .cgi for mod_perl apps :) Eric I use .cgi for mod_perl apps as well. IMHO, .cgi indicates that the file is an executable used as a CGI. Whether it is run by an interpreter such as Perl or Python is irrelevant. Pete - Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiappr=1w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [cgiapp] FYI: CGI::Framework
If you want to trap templates you can match _tmpl.html instead. C::A also has some design decisions that turn people off. (I like C::A) -john On Jan 10, 2004, at 11:25 AM, Peter Chen wrote: On Jan 7, 2004, at 11:23 AM, Mark Stosberg wrote: I thought I would bring attention to CGI::Framework, a project which shares some goals with CGI::Application. ... http://search.cpan.org/perldoc?CGI::Framework I haven't tried it myself. Mark I took a brief look of it to get a feel for some of the decisions made by its author. Right away I saw the following sentence in the man page: Templates should have the .html extension. This strikes me as a rather poor decision, and turns me off. IMHO, it is a poor practice to use the same extension for two different purposes. For example, I may have Apache configured so that it will trap any attempt to directly access a template, which has the extension, .tmpl. Using .html for both static html pages and templates would make such a configuration impossible. Ok, maybe I am biased because I am sold on CGI::Application. :-) Pete - Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiappr=1w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiappr=1w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[cgiapp] FYI: CGI::Framework
Hello, I thought I would bring attention to CGI::Framework, a project which shares some goals with CGI::Application. It provides some specific features beyond CGI::Application including: - Session management with CGI::Session - an explicit API to help with form validation. http://search.cpan.org/perldoc?CGI::Framework I haven't tried it myself. Mark - Web Archive: http://www.mail-archive.com/[EMAIL PROTECTED]/ http://marc.theaimsgroup.com/?l=cgiappr=1w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
