Re: yet another template
| From: | Alex Black | Date: | Thu, 08 Nov 2001 18:53:07 +0000 |
| Subject: | Re: yet another template | ||
| References: | 1 2 3 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-2664@lists.php.net to get a copy of this message | ||
In article <4.2.0.58.20011107183616.00d18cf0@pop.freesurf.fr>,
jm.poure@freesurf.fr (Jean-Michel Poure) wrote:
> > $tpl['value'] = $string;
> >and for a block/section/whatever-its-called
> >you only need to say
> > $tpl['blockname']['value'] = $string;
>
> I like the idea of an object/xml compatible structure.
>
> How would you integrate the template system with databases?
> Keeping key/value pairs in a text file is rather old-fashioned...
>
> Any idea?
> /Jean-Michel POURE
hi jean,
all of that thinking has happened with binarycloud, we have functioning
code.
we have en Entitymanager which accepts xml definitions of fieldsets with
a bunch of metadata, and we autogenerate sel commands for basic
operations. we also automatically generate db independent schemas from
those entity definitions.
soon, we're going to start on a set of builder classes which will
automatically generate forms, lists, calendars, etc base on entity
definitions and local configuration.
I encourgae you not to duplicate this work, as we have invested a _huge_
amount of effort to do it properly.
Also if that work were to take place separately, that places PEAR firmly
in the framework space, which I think is precisely what Stig wants to
avoid?
in any case, we should maintain open communication on this because this
concept is pretty much the core of binarycloud.
best,
-alex