And why can't you do the same with the CGI module? $page_o_html = hidden(-name => 'crap', -value => $crap); would be the same thing.
You lost me on that... plus if you really need to, I have ADDED the CGI at a later point to a pre-existing script and only change the portions that I really wanted to use CGI.pm (cause it's better) and left the rest of the code as is (cause it was too cumbersome to change it all). But then the code starts looking ugly, at some point it needed a re-write (2 months later). I don't use the CGI or HTML modules for tables, I prefer to write those myself, but never had problems with throwing in my own html code in with the CGI stuff. > -----Original Message----- > From: drieux [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 12, 2002 12:18 PM > To: [EMAIL PROTECTED] > Subject: Re: Preview data > > Also, while I like Nikola's generalized solution - I have > decided that the general idea of > > $page_o_html .= <things that add onto it> > > allows me to be more flexible so that I can 'dump out' the > page at different stages as I try to figure out what this > or that Module gives me as 'features' for doing CGI/mod_perl > stuff.... > > > > > ciao > drieux ---------------------------------------------------------------------------- -------------------- The views and opinions expressed in this email message are the sender's own, and do not necessarily represent the views and opinions of Summit Systems Inc. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
