"Alex Black" ...
> the horse is back from the dead!
huh?
> > And aside from that, i don't have a one and only common_head.php ... i
have
> > a separate plain common head, in plain HTML... the real common_head.php
> > should look like (definitively not real PHP sintax):
>
> right, and though this is not directly related to templating:
>
> I thik you would benefit greatly by introducing some system design (i.e.
> separate "layers" doing separate tasks)
Why? If nested tables can do the work, i won't bother learning how layers
work...
> I don't like to do database connections when I've already output markup,
> what if something goes wrong, or I want to do a redirect, etc?
If something goes wrong -> It's the DBA fault. :-)
> I like to access functions in "DB Object" files - those functions return
> results in arrays which I can pass into markup.
>
> Makes the code a _helluvuh_ lot more maintainable.
I'm pretty comfortable programming directly with OCIwhatever() functions
directly in the main code, that's it.
In other words, i don't need to make my code more maintainable because i'm
comfortable with maintaining it right now.
> True, but why not just bitch at macromedia until they include support for
> PHP in ultradev?
(Well, i haven't purchased dreamweaver either)
> (plegh, visual authoring tools: a necessary evil)
Why, when you have notepad.exe and a couple of browsers to test that the
pages work properly?
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
