Hi Devs, This is about the wiki-macro-bridge. According to our previous discussion, I was going to put document listening, macro creation and macro registration logic into xwiki-core-rendering-macro-wikibridge module. But as it seems the macro creation part is going to be highly dependant on bridges (DAB) and would require a couple of more methods on DAB. Since DAB is becomming heavy and poluted, I'm proposing that we split the wikimacrobridge as follows: * Keep document listening, macro registration and macro de-registration logic inside xwiki-core-rendering-macro-wikibridge module as it is. * Differ the macro instantiation logic into some component interface (WikiMacroGenerator). * Have the default WikiMacroGenerator in xwiki-core. (perhaps inside com.xpn.xwiki.doc? any other place?) Here is my +1.

Thanks. - Asiri _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs

Hi Devs, This is about the wiki-macro-bridge. According to our previous discussion, I was going to put document listening, macro creation and macro registration logic into xwiki-core-rendering-macro-wikibridge module. But as it seems the macro creation part is going to be highly dependant on bridges (DAB) and would require a couple of more methods on DAB. Since DAB is becomming heavy and poluted, I'm proposing that we split the wikimacrobridge as follows: * Keep document listening, macro registration and macro de-registration logic inside xwiki-core-rendering-macro-wikibridge module as it is. * Differ the macro instantiation logic into some component interface (WikiMacroGenerator). * Have the default WikiMacroGenerator in xwiki-core. (perhaps inside com.xpn.xwiki.doc? any other place?) Here is my +1. Thanks. - Asiri _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs