as i am beefing up some of the wikka actions i have noticed that instead of using the html attributes which are well known and widely used most of the actions use hard to remember and easy to confuse pseudo parameters/attributes like {{image}} using url instead of src.

in the new versions i make at least i am making the html standard attributes (like src= for image) an alias to the (for me) meaningless url= . i would like to see this enforced as a rule for html element related ({{table}}, {{image}}, etc) action development...

agreed - keeping in mind backward-compatibility though.

backward-compatibility is not a problem, except maybe for {{table}}.
i submitted a suggestion in the tracker for {{table}} but i have just discovered the ongoing discussion about it... shame on me, i'll search more before posting stuff.

i think there should be a file which contains all the action configuration (action.config.php) ... containing something like:

/* lastinfo */
define('DEFAULT_SHOW', '3');
define('DATE_FORMAT', 'D, d M Y');
define('TIME_FORMAT', 'H:i T');

and so on for all the actions. this file would be sourced from wikka.config.php so all the actions have access to it.

but perhaps with date and time, that would be specified only at one place, normally a site uses the same date/time form everywhere, doesn't it?

>but perhaps with date and time, that would be specified only at one place, normally a site uses the same date/time form everywhere, doesn't it?

the idea is to make it configurable for the user, see http://wikka.jsnx.com/UserSettingsPanel

MinusF, I'm not sure whether centralizing all the action options in a single config file would be a good idea. Unless we have a module for handling action installation/removal/configuration (see for instance http://wikka.jsnx.com/InstallableActions), this could result in inconsistencies and bugs as soon as single actions are hacked/upgraded. And once action settings can be modified through an wiki interface, it doesn't really matter whether they are stored in a central config file or in the action file itself, right?