Re: [oxid-dev-general] Pimp my module-config

Alexander Kludt Fri, 24 May 2013 03:22:25 -0700

+1 for that solution

Manuel Reiß

Freitag, 24. Mai 2013 11:29

Hi again,
after messing around a little bit with the module-configuration, I think providing additional blocks in each If-statement and around the whole construct should provide enough flexibility and forget the custom metadata types from my previous post – they seem to be too huge too handle (since the whole configVar-handling relies on these types).

The module_config.tpl could look like this then:

[{block name=“admin_module_config_var_types“}]
[{if $var_type == 'bool'}]
    [{block name=“admin_module_config_var_type_bool“}]
    ...
    [{/block}]
[{elseif $var_type == 'num'}]
    [{block name=“admin_module_config_var_type_num“}]
    ...
    [{/block}]
...
[{/block}]

Greets,
Manuel

[email protected] | www.mediaopt.de

derksen mediaopt gmbh | elbestrasse 28/29 | 12045 berlin | +49 (30) 34 09 42-77 | fax-66 | Amtsgericht Charlottenburg | HRB 120935 B | ust.-id DE265886017 | geschäftsführer dipl.-ing. philipp derksen

Von: [email protected] [mailto:[email protected]] Im Auftrag von Manuel Reiß
Gesendet: Donnerstag, 23. Mai 2013 17:29
An: [email protected]
Betreff: [oxid-dev-general] Pimp my module-config

Hi list,
for module configuration OXID provides a module-config tab whose content is rendered by metadata‘s settings entries. Unfortunately those entries aren’t very powerfull IMHO – therefore my following suggestion:

define a new metadata „type“ entry = „include“ with a template-file as value :
'settings' => array(
        array('group' => 'my_module__config', 'name' => '', 'type' => 'include', 'value' => 'my_module__myAwesomeModuleConfigExtension.tpl'),
);

which will be then included in module_config.tpl:

[{elseif $var_type == 'include'}]
[{include file=$module_var }]

small change, big possibilities i guess.
Alternatively / additionally a block wrapping the whole IF-statements inside module_config.tpl would also provide more flexibility here – ppl could define their own types etc (e.g. type=“password“ ;) ).

Do think this might be a good idea ?

Greets,
Manuel

[email protected] | www.mediaopt.de

derksen mediaopt gmbh | elbestrasse 28/29 | 12045 berlin | +49 (30) 34 09 42-77 | fax-66 | Amtsgericht Charlottenburg | HRB 120935 B | ust.-id DE265886017 | geschäftsführer dipl.-ing. philipp derksen

_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Manuel Reiß

Donnerstag, 23. Mai 2013 17:28

Hi list,
for module configuration OXID provides a module-config tab whose content is rendered by metadata‘s settings entries. Unfortunately those entries aren’t very powerfull IMHO – therefore my following suggestion:

define a new metadata „type“ entry = „include“ with a template-file as value :
'settings' => array(
        array('group' => 'my_module__config', 'name' => '', 'type' => 'include', 'value' => 'my_module__myAwesomeModuleConfigExtension.tpl'),
);

which will be then included in module_config.tpl:

[{elseif $var_type == 'include'}]
[{include file=$module_var }]

small change, big possibilities i guess.
Alternatively / additionally a block wrapping the whole IF-statements inside module_config.tpl would also provide more flexibility here – ppl could define their own types etc (e.g. type=“password“ ;) ).

Do think this might be a good idea ?

Greets,
Manuel

[email protected] | www.mediaopt.de

derksen mediaopt gmbh | elbestrasse 28/29 | 12045 berlin | +49 (30) 34 09 42-77 | fax-66 | Amtsgericht Charlottenburg | HRB 120935 B | ust.-id DE265886017 | geschäftsführer dipl.-ing. philipp derksen

_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

<<attachment: coding.vcf>>

_______________________________________________
dev-general mailing list
[email protected]
http://dir.gmane.org/gmane.comp.php.oxid.general

Re: [oxid-dev-general] Pimp my module-config

Reply via email to