On Oct 12, 2004, at 6:52 PM, Matthew Weier O'Phinney wrote:
I haven't had much luck with PHP books when it comes to efficient
coding
techniques and site/application architecture. It's a niche that needs
to
be filled.
Another thing you might want to research is the MVC pattern
(Model-View-Control
* Greg Donald <[EMAIL PROTECTED]>:
> > why use one template, or many - why use different pages rather than
> > relying on variables.
>
> I scoff at template engines like Smarty and frameworks like Mojavi.
> But that's just me. I work with both of those technologies everyday
> but would never incl
* Lists <[EMAIL PROTECTED]>:
> This is helpful, thanks. But I understand most of the pieces. I'm
> interested in efficient and organizational factors to consider in using
> them. But after sending this, I thought, maybe my question is more of
> a general structural web design question rather
It'll make a small project seem huge in no time flat, but that's the
price you pay for 'organization' and stuff.
But frameworks can also make a huge project seem medium which is the
advantage of organization. Also, it's quite often the case that a small
project grows and slowly becomes a big projec
On Tue, 2004-10-12 at 18:18, Greg Donald wrote:
> We use Mojavi, and it works very well:
>
> http://mojavi.org
> http://www.peterrobins.co.uk/it/mojavi/tutorial.htm
>
> It's way more than just templates, it's display and logic seperation,
> modularization, filter chains, the works. In fact we us
On Tue, 12 Oct 2004 14:38:21 -0700, lists <[EMAIL PROTECTED]> wrote:
> This is helpful, thanks. But I understand most of the pieces. I'm
> interested in efficient and organizational factors to consider in using
> them. But after sending this, I thought, maybe my question is more of
> a general s
This is helpful, thanks. But I understand most of the pieces. I'm
interested in efficient and organizational factors to consider in using
them. But after sending this, I thought, maybe my question is more of
a general structural web design question rather than PHP.
I've checked google, (I'm
On Tue, 12 Oct 2004 13:19:37 -0700, lists <[EMAIL PROTECTED]> wrote:
> I"m wondering what factors are at play in deciding to use "require",
> "include",
This dictates the level of error reporting you desire when pulling in
a file. On failure, include() won't stop your script execution, while
requ
On Tue, 2004-10-12 at 16:19, lists wrote:
> Hi List,
>
> I"m wondering what factors are at play in deciding to use "require",
> "include", "file_get_contents" and such when laying out a site. Like
require() generates a fatal error if the target file doesn't exist. This
means your script will no
Hi List,
I"m wondering what factors are at play in deciding to use "require",
"include", "file_get_contents" and such when laying out a site. Like
why use one template, or many - why use different pages rather than
relying on variables. I'm also wondering about how I see "{content}"
type stuf
10 matches
Mail list logo
