On Jun 12, 2009, at 2:29 PM, Sergiu Dumitriu wrote: > Florin Ciubotaru wrote: >> Hi, >> >> XWiki has evolved a lot in the past year and new client apps were >> created. >> Our current Xml-Rpc API is aligned to the Confluence 1.0 API >> specification and hasn't been really enriched in a long time. >> >> Since we have some distinct features like 'polyglot wiki' I propose >> to >> create a new "xwiki2" method set to handle XWiki 2.0 method calls. >> The new handler will be added to the Apache Xml-Rpc servlet >> properties file. >> >> Proposed new xml-rpc methods(mostly needed for XEclipse, XOffice >> and XOO): >> - parseFromHtml(String html, String syntax) : String >> - render(String source, String syntaxId) : String >> - cleanHtml(String dirtyHtml) : String >> - add class ( http://jira.xwiki.org/jira/browse/XWIKI-3499 ) >> - getConfiguredSyntaxes > > getEnabledSyntaxes sounds better to me
He's using the same name as in the XWiki API which is good IMO. If we want getEnabledSyntaxes the we also need to change the API. Enabled or Active are better I agree since even though they are configured they can still be deactivated at runtime by unregistering a parser. Also it's possible to dynamically add a new parser even if it's not configured. +1 in general. Just make sure that the XWiki XMLRPC client continues to work for accessing Confluence instances. Thanks -Vincent >> - getVirtualWikisNames >> - getMacros, etc. >> >> Proposed Xml-Rpc model extensions: >> - Page >> - syntaxId; > > - defaultEditMode? > - editComment? > - hidden? > >> - ServerInfo/Wiki: >> - isMultiWiki >> - defaultSyntax >> - encoding >> >> WDYT? > > +1 > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
