Jesse Guardiani writes:

What I'd really like to do is move towards a system where all page
specific code is handled at the very top of the page, possibly by inserting
a tag similar(but unique for each page) to this:

[ ... ]

Unless there's some tangible benefit to all this, I don't care. Each time a change is introduced, there's a possibility of introducing a bug. Cutting things apart just to introduce a higher theological level of design purity will not result in any tangible benefit, and then you'll need to spend even more time fixing bugs that were introduced in step 1.

If I had all the time in the world, then maybe. But I don't have all the time in the world, and I'd rather spend what I do have on things that will actually result in something productive.

Then, as do_output_form_loop() works it's way down the page it will
encounter tags like this:

[#display_email_table#]

[#display_Next_Page_icon#]

etc...

Each of the 'display_...' tags would translate to a simple function in
do_output_form_loop() that would simply print the necessary data
stored in the data structure created by 'init_page_x'.

That's nice, except that in many instances this is not a fill-in-the-blanks type of deal. In many cases you need to remove entire sections of HTML, or generate new ones.

I don't have any particular need to win any design purity contexts. I'm not going to fix anything that's not broken.


Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to