Dell Sala wrote:
In other words, build a php wrapper around your software package. Done
right, it won't know the difference, and you don't have to muck around
with httpd.conf.
This can be fun. It can be an easy way to improve the user
interface of commercial junkware web apps.
I did a presentation at a conference about a demo system I built
with an instruction librarian. With about 200 lines of PHP I was able
to put a wrapper over a library catalog that created an online
instruction unit that worked with the real catalog. It would display
popover <div>s that would give people instructions. The app monitored
their progress -- it would congradulate them if they found what they
were looking for and offer them help if they made certain common mistakes.
_______________________________________________
New York PHP Community Talk Mailing List
http://lists.nyphp.org/mailman/listinfo/talk
NYPHPCon 2006 Presentations Online
http://www.nyphpcon.com
Show Your Participation in New York PHP
http://www.nyphp.org/show_participation.php
