Posted by Stephen Kay on 04/03/06 04:10

in article X-WdneyyYJ_QpLLZnZ2dnUVZ_smdnZ2d@comcast.com, Jerry Stuckle at
jstucklex@attglobal.net wrote on 4/1/06 10:37 PM:

>> I assume this is a no-no, but what are the problems with just leaving it
>> this way? It seems to be working anyway. Otherwise, I assume the options are
>> to rewrite every single page to remove this stuff, or to try and remove it
>> procedurally after reading it into the $content variable.
>>
>> Thanks,
>
> Other than:
>
> 1. It may or may not work in all current browsers,
> 2. It may or may not work in next generation browsers,
> 3. One look at the source (in any browser) shows you are lousy webmaster.
>
> Any questions?


Well, #1 & #2 make sense. #3 I guess might be important for those people
who have their self-worth tied up in things like that. I mean, that's the
first thing I do when I go to a site: look at the source and evaluated the
skill of the programmers. ;-)


> And btw - I would never code something like this in the first pace. Virtually
> impossible to maintain!

Which part are you talking about? Having a php template with a header, a
navbar, and a footer, and then being able to include content somewhere in
the page?

Or reading pre-existing HTML pages for the content part?

I wouldn't structure it like this either, except the site already exists,
has probably a hundred existing pages, and used to use a godawful frame set
arrangement. I'm trying to improve it without rewriting the whole thing or
cleaning up every single page. But maybe that's the way to go, anyway.

--
Stephen Kay
Karma-Lab sk@karma-lab.NOSPAM.com
^^^^^^^

[Back to original message]