[kdewebdev-site] Local test bench and defined variables
Eric Laffoon
eric at kdewebdev.org
Thu Mar 10 13:05:41 EST 2005
On Thursday 10 March 2005 12:12 pm, Andras Mantia wrote:
> On Thursday 10 March 2005 21:43, Eric Laffoon wrote:
> > The inclusion of applib.php is not an assumption. It is a rule!
>
> I don't think we need to argue further more, but I took out this part of
> your mail to point out what is the difference between my thinking and
> yours. ;-)
I would defer to you in coding decisions regarding application design because
you have more experience. ;-)
> What I say is valid in general, but what you say is valid for the
> special case called kdewebdev.org.
Right. PHP is not as rich a language as C++ and so concessions sometimes need
to be made.
> Now we can argue till death about what it better for us, and until I
> run into serious troubles with parameters in PHP you cannot convince me
> that I'm not right. :-)
>
> Andras
It will be more apparent as the site progresses. applib.php addresses several
issues from my years of experience with web design. Central to this is that
having one file to do some important things can save a lot of grief. Those
are"
1) manage paths for local test and site - this can become a lot more critical
if you want to add security measures
2) insure required include files can be centrally managed
3) deal with order of precedence issues centrally - for instance with cookies
or sessions certain things must happen before other things and doing them in
the wrong order can cause serious problems
I really should let you build a site with all these things without the simple
looking central include file so you can experience hair pulling agony first
and appreciate why I would make including this file mandatory. I just don't
want to have to watch. ;-)
--
Eric Laffoon
Project Lead - kdewebdev module
More information about the kdewebdev-site
mailing list