RE: XML Templates...

I guess we are thinking web application more than web sites, but in the
Internet of tomorrow if your site is not an application you are dead in the
water anyway.  I understand the point of presentation logic layers.  Which
can still be had in Jadeke.  I guess a good example would be how many shops
hire VB programmers to write GUI and then have C++ connect the dots so to
speak.  This would be similar.  

Basically this is not complete reinvention of PHP.  This is Rapid
Application Develompent PHP.  Only you still have the ability to get to core
php underneath if you want to get your hands dirty.  At this point I think
the template approach is actually targeting more of the static web site
format not ones that want applications.  Which is fine, but not how most see
the future of the web.

Thanks,

Derek Neighbors
Administrative Technology Center
Lead Client Server Programmer/Analyst
Phone: 602-506-2273
Pager: 602-310-2428
Email: [email protected]


> -----Original Message-----
> From:	Andrei Zmievski [SMTP:[email protected]]
> Sent:	Tuesday, February 15, 2000 11:37 AM
> To:	Jade Meskill
> Cc:	php-template
> Subject:	Re: XML Templates...
> 
> On Tue, 15 Feb 2000, Jade Meskill wrote:
> > so the HTML designer creates a vanilla HTML document awaiting ties to
> the
> > database...
> > 
> > See before.html (attached)
> > 
> > Then the developer comes in behind the designer and adds the database
> > functionality to it...  this saves the designer and the developer from
> > having to learn unfamiliar syntax (as far as the current template sytem
> > looks) to be included in the template (and is much more standardized
> IMHO).
> > 
> > See after.xml (attached)
> > 
> > We are really talking about the same thing, just a different approach...
> > Thanks for your time. :)
> 
> It is a different approach. In most cases we have the templates going
> back and forth between developer and designer, so having XML code might
> be a tad confusing. Secondly, my personal opinion is that templates
> should not have any sort of database access in them. By the time you put
> DB calls, while loops, etc. you're back to reimplementing PHP.
> 
> -Andrei
> * A feature is a bug with seniority. *