Il 23 aprile 2012 15:39, Massimo Di Pierro <massimo.dipie...@gmail.com> ha scritto: > To me the issue is not flexibility vs ease of use. > > To me the issue is storing layout info (html) or storing a more abstract > representation (wiki syntax). > > In both cases one can embed higher level components. In the former case it > is easier for users (wysiwyg) and it can made it work with any theme, but > changing theme a posteriori becomes difficult. In the letter case it easy to > change theme but building themes requires technical expertise.
Wysiwyg with wiki syntax cannot be done? The problem is the editor or the way content is stored? The html syntax is not simpler than wiki so in any case the user that does wysiwyg does not care what is below he trusts the visual editor. For a more advanced user IMHO wiki syntax (or any proper syntax) can enforce the component reuse by having more readable shortcuts to components. Having an intermediate language has the advantage of easier themig also, i.e. the theme can act on the final conversion to html of the rendered object. If thought that way the theme would become a filter besides simply adding presentation directives (i.e. css). Some have done the above using XSLT. Personally I would like to avoid XSLT. mic
