RE: [binarycloud-dev] BCTagParser.php

[Andreas A. <a.a...@th...>]

Hey Alex,

>> Hmm regex is another option. This could be a part of the the
>> TemplateManager. So we can do stuff like <bc:tmpl
>> var="something" /> that
>> would make into <?=$TemplateManager->handle["something"]?>
>> or something similar.

> That's a possibility, but I think in most cases the <bc:
> tags will be interpreted into either static html, or
> (in the case of the <bc:module> tag, a call to Page)
Ok, I don't want the <bc:*> tags parsed at runtime.


> TemplateManager will be a simple generalized set of methods
> for applying templates to data using xslt, smarty, native
> php, whatever people want.
Got it. Cool.

> I view the <bc:> tags more as a function of the make
> system than a runtime thing.
100% agree. Transforming them at run-time would be lame.
I never ever thought of that. I thought of bc:tag that makes
into a php echo ing something. That was 'caus I misunderstood
template manager as the actual template engine.


> Also, I'd like the flexibility to use xslt if I want,
> or just be lazy and use native php. :)
I see the point.

>> I know if we use that it's enforcing policy. But in the process of
>> standardizing things it's a logical step. And for what are
>> standards? They force something so that everybody that knows the
>> standard can use it ;-)

> I agree, but I would prefer to use standards that come from
> wc3, not create my own production standards.
Uh, don't misunderstand. With "standard" I tought of official standards like
the w3c recommendations not something own.


> I have a certain way of doing things: some
> people like that way and others I'm sure do not.
> I would far prefer that binarycloud be flexible enough
> for people to configure it and use it to suit their
> particular needs.
Agreed.

[xhtml]
> That's true. So we really may want to consider it.
> But I can see other problems with it:
>
> -what do you do with embedded "native" php in templates
> that is parsed as a processing instruction?
That's a problem, alright.

> -we would be forced to build _some_ kind of debugging
> support during make that would point syntax errors
> during make, or I can see peole going crazy trying to
> find problems.

good point.


> I think for the moment that regex is preferable because the
> tag syntax isn't complex. also, you can rely on the fact
> that the tags are valid xml within their own scope, so you
> could pass them to a parser in little chunks and get
> arrays back :)
Hmm, ok I see It's better for now I guess. The additional overhead (debug,
embedding native php) and the somehow limited flexiblity does not sacrifice
using this standards (now) that may become "common" in some years.


Andi