Hi Jerome,
Jerome Velociter wrote:
Hello all,
I think it would be nice to have the possibility to post-load some of
the JavaScript extensions, as a way to ease performance best practices
for developers. (See
http://developer.yahoo.com/performance/rules.html#postload for example).
It would also allow people to easily add hungry third party scripts
(like the google analytics tracker) in a non intrusive manner and not
sacrificing performance (no need to modify/override htmlfooter.vm for
example, a simple SX always-use will do).
I see different ways of doing that :
1) Either we say all document JSX are
post-loaded, and we move the hook
down the DOM just before the closing</body> tag.
This poses a problem in WYSIWYG editing mode. I'm currently loading the
JSX in edit mode in order for the page to look as in view mode. Placing
the hook inside the editable body is dangerous.
In the case of the WYSIWYG we could keep it in the header (I believe you
already are placing the hook yourself and do not use javascript.vm,
right ?).
BTW is it such a good idea to load extensions in edit mode?
I'm not very convinced, since some extensions could affect the content
of the edited DOM, leading to weird content. (Think about the addSizes
extension of the SX tutorial for example
).
Jerome.
Marius
2) Either we have 2 hooks and we leave it as an
option to be post-loaded.
My preference goes to 1), as I don't see any good use case where a
extension would need not to be post-loaded; and 2) is not so elegant to
implement with the current SX mecanism.
WDYT ?
(Note: I'm not talking about file-system extensions here (JSFX), though
the question could be asked for them as well - I need to give it more
thoughts)
Jerome.
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs