Hi everybody,
what about even more simplification of the plugin call?
Namely: allowing the ommission of inverted commas for arguments without space, e.g. {{{flexslider myselfies}}}
I got the idea from css font-family, where inverted commas are only required when the name of the font family contains spaces. The same could be done to plugin calls. The first word is always the name of the plugin, and further words are arguments. Only arguments containing a space would need to be delimited by inverted commas. For other arguments this is logically not really necessary.
Even now, when the argument is a number, inverted commas are not required, e.g. {{{year 2010}}}, why not allow this for strings also?
Additional simplyfication in plugin calls?
Re: Additional simplyfication in plugin calls?
IMHO all that simplifications are subject of confusing.
I think one -- and only one correct syntax is best practice.
I think one -- and only one correct syntax is best practice.
Re: Additional simplyfication in plugin calls?
I'm against this simplification, because it would introduce ambiguities. As it is now, the arguments are not parsed by CMSimple_XH, but are simply passed to PHP's eval. This allows rather complex argument lists; actually, arbitrary expression lists are permitted. The expressions may contain constants, which would not be distinguishable from unquoted strings.svasti wrote:what about even more simplification of the plugin call?
Namely: allowing the ommission of inverted commas for arguments without space, e.g. {{{flexslider myselfies}}}
Christoph M. Becker – Plugins for CMSimple_XH