une 27, 2002 7:40 AM
To: [EMAIL PROTECTED]
Subject: Re: [PHP] Seperating presentation from logic
John Holmes wrote:
> You really want a template system. Check out Smarty or patTemplate.
> Devshed.com has a nice two part tutorial on patTemplate and I like how
> it looks a little better than Smart
John Holmes wrote:
> You really want a template system. Check out Smarty or patTemplate.
> Devshed.com has a nice two part tutorial on patTemplate and I like how
> it looks a little better than Smarty right now. Might want to evaluate
> both and see which is faster or easier.
Great idea - except
Sent: June 27, 2002 12:39 AM
To: 'SP'; 'Jean-Christian Imbeault'; [EMAIL PROTECTED]
Subject: RE: [PHP] Seperating presentation from logic
> There are a ton of template systems. Look here for performance
> benchmarks:
> http://www.phpinsider.com/benchmarks_phemplate
&
> There are a ton of template systems. Look here for performance
> benchmarks:
> http://www.phpinsider.com/benchmarks_phemplate
>
> Unfortunately pattemplate isn't tested so I don't know how it rates.
I downloaded the scripts and added patTemplate to the mix. It's average,
rating in the middle
on 26/06/02 11:53 PM, Mark Gallagher ([EMAIL PROTECTED]) wrote:
> Theoretically this could still be done only with editing of the
> stylesheet. Of course, it's not that simple - Mozilla comes closest to
> decent browser support for that sort of radical change, and even it's
> not there yet.
wel
On 25 Jun 2002 at 17:40, Jean-Christian Imbeault wrote:
> Some of the "issues" are things like how to make it painless for both
> the designers and me if one day, out of the blue, a designers decides
> that the background colour should be changed, or the graphics changed.
> Or even worse the two
> >>Wouldn't you ultimately be better off moving most of this sort of
> > thing
> >>into style sheets and then have the designers play with the style
> > sheets instead?
> > What if your designer wants to change from a two column
> table to a four column table. Or change the menu from a v
On Wednesday, June 26, 2002, at 09:05 AM, John Holmes wrote:
> I disagree. Maybe I'm just not getting it, or understanding the "FULL
> POWER" of xml/xslt. It just seems like it's adding in an additional
> layer that you don't need. It seems so dependent on browser versions,
> and parser version
John Holmes wrote:
>>Wouldn't you ultimately be better off moving most of this sort of
>
> thing
>
>>into style sheets and then have the designers play with the style
>
> sheets
>
>>instead?
>
> Sure, if all they are doing is playing with fonts, colors, sizes, etc...
>
> What if your designe
> Wouldn't you ultimately be better off moving most of this sort of
thing
> into style sheets and then have the designers play with the style
sheets
> instead?
Sure, if all they are doing is playing with fonts, colors, sizes, etc...
What if your designer wants to change from a two column table t
> personnaly, I agree with you, and I would really like to see more PHP
> frameworks (or template systems) rely on XML/XSLT.
> you can have a look at :
> http://www.interakt.ro/products/Krysalis/
I disagree. Maybe I'm just not getting it, or understanding the "FULL
POWER" of xml/xslt. It just see
>
> $siteTitle
>
> $colBg = "#FF";
> $colText = "#FFCC99";
> $colLink = "#EE";
> $colComplimentary = "#CC6600";
>
>
> $fontHeading = " size=\"3\">";
Wouldn't you ultimately be better off moving most of this sort of thing
into style sheets and then have the designers play w
real project.
looks interesting ...
> -Original Message-
> From: Jerome Houston [mailto:[EMAIL PROTECTED]]
> Sent: mardi 25 juin 2002 20:51
> To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Subject: RE: [PHP] Seperating presentation from logic
>
>
> Is there a particular rea
Is there a particular reason everyone is skipping over the idea of using
XML/XSLT? What you're talking about is EXACTLY what XSLT was designed for.
You can write scripts that access the DB, and output XML. Then you just use
XSL files written by your designers to translate your XML into HTML.
2 12:02 PM
To: 'Jean-Christian Imbeault'; [EMAIL PROTECTED]
Subject: RE: [PHP] Seperating presentation from logic
You really want a template system. Check out Smarty or patTemplate.
Devshed.com has a nice two part tutorial on patTemplate and I like how
it looks a little better than Sma
cument???
---John Holmes...
> -Original Message-
> From: Jean-Christian Imbeault [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 25, 2002 3:50 AM
> To: [EMAIL PROTECTED]
> Subject: Re: [PHP] Seperating presentation from logic
>
> Thanks for the links. Hard to figure o
ginal Message-
From: Jean-Christian Imbeault [mailto:[EMAIL PROTECTED]]
Sent: June 25, 2002 1:00 AM
To: [EMAIL PROTECTED]
Subject: [PHP] Seperating presentation from logic
I'm just about to start a large PHP project in which I get to work with
professional designers/layout people. I want t
on 25/06/02 6:40 PM, Jean-Christian Imbeault ([EMAIL PROTECTED])
wrote:
> Some of the "issues" are things like how to make it painless for both
> the designers and me if one day, out of the blue, a designers decides
> that the background colour should be changed, or the graphics changed.
> Or eve
on 25/06/02 5:50 PM, Jean-Christian Imbeault ([EMAIL PROTECTED])
wrote:
> Maybe my message was too vague but what I meant is that my designers
> will come up with the site layout, colours, graphics etc ... I want them
> to be able to do all their work without thinking about any programming.
Why
Thanks! I'll visit and read all the links you gave.
Some of the "issues" are things like how to make it painless for both
the designers and me if one day, out of the blue, a designers decides
that the background colour should be changed, or the graphics changed.
Or even worse the two column la
I think the issues are VERY project specific. Luckily for me I'm the
DESIGNER and PROGRAMMER on many of my projects, but often I'm just one of
the two.
When I'm just designing, I obviously need to develop page templates, but
more and more of my time is spent developing style guides (often also c
Well... I still think that these tools can help.
For example PHPWebSite (which I use for our Intranet) has a set of
'themes'. A theme consists of a style sheet (.css), some image files
(logo's, backgrounds etc.) and a small set of PHP scripts that define
things like standard header, footers.
Thanks for the links. Hard to figure out what those things are just from
their web pages. They should work on making it easier to figure what the
projects are.
I'll have a look but ...
Maybe my message was too vague but what I meant is that my designers
will come up with the site layout, colo
You might want to start by looking (download, instal, try) at available
content managers like
PHPWebSite http://phpwebsite.appstate.edu/
PHPNukehttp://phpnuke.org/
They do exactly that; seperate content from programming logic. As an
admin you can assign certain users as beini
I'm just about to start a large PHP project in which I get to work with
professional designers/layout people. I want to separate all the
programming logic from the presentation but I am not sure how to do this.
Can anyone point me to resources (web tutorials/articles or books) that
would help
25 matches
Mail list logo
