Re: [binarycloud-dev] BCTagParser.php

[Alex B. <en...@tu...>]

> Hi 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)

> How are your plans for the native TemplateManager. Will it be a xslt thing
> (as planed some months ago) or will it be more like smarty (replace) or
> completely make based with bc:style tags ?

Any and all of that:
    TemplateManager will be a simple generalized set of methods for applying
templates to data using xslt, smarty, native php, whatever people want.

I view the <bc:> tags more as a function of the make system than a runtime
thing.

> I'm still unsure about the xhtml/xml/xslt stuff. It would simple things up
> and also make the docs clear and usable by transformers.

I agree, though I see some problems with doing that - there really aren't
that many good xslt tools out there and people won't necessarily want to use
it.

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

> 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. 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.

> I mean, using standardized technology will make live easier, even if people
> are not used to close the <img> tag. In my opinion it's not a big deal to
> close them. To learn this it's a matter of an hour or so. The loose-xhtml
> standard is not much different from html.

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?
    -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.

etc.

> I think if we start using xml stuff (we already have in the configs) we
> should use it throughout the system. Ok, it would force xhtml on users - but
> bc is targeting professional users and big projects. So using xhmtl would
> not be a drawback in my mind.

I agree, but with the caveats above.

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 :)


_a

> 
> Andi
> 
> 
>> Or, because of the simplicity of the tags, we could probably
>> build a regex that would get 'em all.
>> 
>> _a
>> 
> 
> 
> _______________________________________________
> binarycloud-dev mailing list
> bin...@li...
> https://lists.sourceforge.net/lists/listinfo/binarycloud-dev
>