Re: Re: better way to mix html and php code?
| From: | Dan Baker | Date: | Thu, 17 Nov 2005 21:03:41 +0000 |
| Subject: | Re: Re: better way to mix html and php code? | ||
| References: | 1 2 3 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-226008@lists.php.net to get a copy of this message | ||
"Robert Cummings" <robert@interjinn.com> wrote in message
news:1132257406.18353.24.camel@blobule.suds...
> On Thu, 2005-11-17 at 14:34, Dan Baker wrote:
>> <afan@afan.net> wrote in message
>> news:437B5A85.9010901@afan.net...
>> > Hi to all,
>> > always wondered what's better way to mix html and php code. Here are
>> > three
>> > "ways" of the same code. Which one you prefer? (And why, of caurse :))
>> (snip)
>> > I think third solution would be the best solution?
>>
>> IF you are doing a complex site, then the third option is almost
>> mandatory.
>> You typically do not know what code will be in the header, until you have
>> processed some of the page. Building the page as-you-go, allows for easy
>> alteration of previously built HTML code. Complex sites are extremely
>> difficult to create using the "template" approach, because of the variety
>> of
>> output.
>
> Ummm... bullturds :)
>
(snip)
>
> Now anywhere in the modules (which incidentally get loaded before the
> content), or anywhere else in a sub-template content can be accumulated
> in any of the above accumulator names. I have worked on plenty of
> complex sites, and my JavaScript and other content always goes EXACTLY
> where it's supposed to be, regardless of where the logic exists that
> determines it's need to exist. For instance to include on load
> javascript from any module:
Looks very good. I rescind my previous post. I haven't worked with
templates of this magnitude before.
DanB