Re: Conf: argue !

> Solve it as (1):
>
> /smarty
> /smarty/options
> /smarty/options/plugins_dir
> /smarty/options/plugins_dir/0 =>(BC_PATH_BASE . '/smarty/libs/plugins')
> /smarty/options/plugins_dir/1 =>(BC_PATH_BASE . '/smarty-plugins')

nice because it clearly defines arrays...

>
> /smarty
> /smarty/options
> /smarty/options/plugins_dir  =>(BC_PATH_BASE . '/smarty/libs/plugins')
> /smarty/options/plugins_dir  =>(BC_PATH_BASE . '/smarty-plugins')
>
> (and have Conf group these into an array)

elegant but problematic (no path uniqueness, though XML certainly doesn't
guarantee that...)


> Or (3):
>
> /smarty
> /smarty/options
> /smarty/options/plugins_dir => array(
>        (BC_PATH_BASE .  '/smarty/libs/plugins'),
>        (BC_PATH_BASE . '/smarty-plugins') )
>
> (and allow for arrays in the value).

extremely yucky.

> (1) Yacc. Looks like hacking.

it's not _that_ bad :)

 (2) Elegant. Makes Path being non-unique (in the database only).

yeah, non unique I don't love.

> (3) Possible. Powerfull. Introduces customized data format in the
> database.

yeah, don't like it.

---

so in fact I think we have two choices:


1::
> /smarty
> /smarty/options
> /smarty/options/plugins_dir  =>(BC_PATH_BASE . '/smarty/libs/plugins')
> /smarty/options/plugins_dir  =>(BC_PATH_BASE . '/smarty-plugins')

this builds an array from like-pathed conf values, so an integer PK is
obviously required.

2::
or... we could make the above illegal and force naming on everything.


I vote #1, allow arrays to be built from non-unique paths.

Everyone else?

_a
_______________________________________________
dev mailing list
dev-PnctHDZWAvB/Cz2I37pSEPZ4XP/[email protected]
http://lists.binarycloud.com/mailman/listinfo/dev