Maybe this can help: http://www.intorel.com/index.php?page=ActiveSiteCompiler-default_asp --- On Fri, 4/10/09, Paul M Foster <paulf@xxxxxxxxxxxxxxxxx> wrote: > From: Paul M Foster <paulf@xxxxxxxxxxxxxxxxx> > Subject: A Tool For Building PHP Web Apps > To: php-general@xxxxxxxxxxxxx > Date: Friday, April 10, 2009, 1:28 AM > Here's a hairbrained idea I was > kicking around. I object to the idea of > including 15 or 30 files in a PHP application just to > display one page > on the internet. It makes the coding faster, but it makes > the display > slower and seems silly to me. > > So what if you had a tool or a set of tools where you could > write code > snippets and such, and then hit a button or issue a > command, and > everything you specified got written into a single file? > You'd specify > that this page needs to read the config, set up a database > connection, > validate these fields, etc. When you were done, it would > write all this > code to a *single* file, which the user would invoke by > surfing to that > page. The resulting code would be *static*, not like what > results from > most templating systems. So rather than specify a specific > variable > value in the resulting file, it would embed the PHP code to > display the > variable, etc. > > What might be the liabilities of something like that? Would > there be > security issues? Would there be increased difficulty in > debugging? What > can you think of? > > Paul > > -- > Paul M. Foster > > -- > PHP General Mailing List (http://www.php.net/) > To unsubscribe, visit: http://www.php.net/unsub.php > > -- PHP General Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
