Hey William -- > I think one mental problem I'm having is that I want to eliminate code > redundancy. However, it seems your philosophy would say that if there is > an admin interface to the data and a user interface, there should be two > separate CGI::App modules to implement these separate interfaces. That > seems like redundancy. The problem is that HTML doesn't allow you to just "layer" functionality. For instance, in the non-admin mode you might just display some text, but in the admin mode you might need a drop-down for that same text which also contains 40 other choices. You can start putting everything into if-else blocks, but that gets tired quick. In my apps, the admin interface accesses the same data, but might have a very different visual (HTML) representation. In that case separate CGI-App modules makes sense. OTOH, Brett describes a good system for minimizing redundancy. It takes a little work, but it is possible to encapsulate functionality into "model" methods so that admin and non-admin web applications share as much code as possible. > Thanks for a great > framework and for your continual efforts to help us use it most > effectively. I'm glad you find it useful! TTYL, -Jesse- -- Jesse Erlbaum The Erlbaum Group suppressed Phone: 212-684-6161 Fax: 212-684-6226 --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/suppressed/ To unsubscribe, e-mail: suppressed For additional commands, e-mail: suppressed
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.