[nycphp-talk] <script language="php">
nyphp at enobrev.com
Fri Feb 7 12:49:56 EST 2003
I've seen tutorials and such on xml / xsl, and I've seen it live at
trip.com which impressed me as that was implemented at least 6 months
ago. I just spent 4 days on a basic xml class (yes I know they're out
there, but that's no good for learning ;) ) Have any of you had
experience creating entire sites with xml / xsl. I've been incredibly
interested in the solution for a while, but I'm worried about how it
works on browsers and general dev experience..
Any stories, comments or recommendations about it?
From: Ian Forsyth [mailto:ian at plusfour.org]
Sent: Friday, February 07, 2003 12:11 PM
To: NYPHP Talk
Subject: Re: [nycphp-talk] <script language="php">
Shouldn't there be a move towards xsl, xml, xslt type templating..
more options for media delivery... all data gets outputted at xml,
then the data gets transformed.. but if data is xml, its a lot easier
to syndicate, and if your a store, its easier to have your products get
sucked up into sites like dealtime.com, and you could also just release
your products, and give people dealerids, something like what amazon
does, then you have more exposure of your product..
Didn't websap make a soap class for amazon?
down with html templating systems.. march towards the future!
On Thursday, February 6, 2003, at 07:35 PM, Sterling Hughes wrote:
> On Thu, 2003-02-06 at 22:18, Jon Baer wrote:
>>> Like I said, maybe I'm reading into this too much. But please
>>> If there are other ways than the previous to display PHP variables
>>> HTML than let me know. Thank you.
>> Well you got my point ... the fact that you need to apply things
>> <?= $foo["bar"] ?> is a little wierd when an engine like Smarty
>> exists, kinda wierd its not part of the language itself for doing DB
>> (any plans on this?). Like I said probably just out of place since I
>> from using ATG Dynamo and the concept of droplets I thought was a
>> good form
>> factor for building web apps with good clean syntax.
> Its not - using a templating engine on top of PHP itself is inane,
> unless you have certain specialized cases. Separating logic from
> content is always good - but don't get overzealous, you can right your
> backend logic *and* your frontend logic in PHP and still keep them
> "First they ignore you, then they laugh at you,
> then they fight you, then you win."
> - Gandhi
--- Unsubscribe at http://nyphp.org/list/ ---
More information about the talk