Created Forum entry https://forum.xwiki.org/t/comparing-xwiki-to-mediawiki-and-confluence-on-xwiki-org/634
Thanks, Caty On Fri, Sep 22, 2017 at 7:11 PM, Ecaterina Moraru (Valica) < vali...@gmail.com> wrote: > Hi, > > I finally got the time to make another iteration for these comparison > pages. > > If anyone want to make modifications on the texts, they are available at: > - http://dev.xwiki.org/xwiki/bin/view/Drafts/Compare/ > - http://dev.xwiki.org/xwiki/bin/view/Drafts/Compare/XWiki-vs-Confluence/ > - http://dev.xwiki.org/xwiki/bin/view/Drafts/Compare/XWiki-vs-MediaWiki/ > > They should look like: > - Compare: http://design.xwiki.org/xwiki/bin/download/Proposal/ > XWikiOrg2017/preview_Compare.png > - XWiki vs. Confluence: http://design.xwiki.org/xwiki/ > bin/download/Proposal/XWikiOrg2017/preview_Confluence.png > - XWiki vs. MediaWiki: http://design.xwiki.org/xwiki/ > bin/download/Proposal/XWikiOrg2017/preview_MediaWiki.png > > I'm curious to know what you think about this version in terms of layout, > validate the content, maybe you have other points that we can compare the > solutions on, maybe I wrote something wrong for the solutions. > > Let me know, > Caty > > On Tue, May 17, 2016 at 11:17 PM, Bryn Jeffries < > bryn.jeffr...@sydney.edu.au> wrote: > >> Denis Gervalle said: >> > > Yes, we only maintain documentation for the latest version of XWiki on >> > > xwiki.org (not enough manpower to have decent doc for several >> versions >> > > ATM). >> > > >> > >> > However, for version 6.2.5 and later, you have a way to mitigate this >> > limitation. You can install the Scripting Documentation Application on >> your >> > own wiki (see >> > http://extensions.xwiki.org/xwiki/bin/view/Extension/Scripti >> ng+Documenta >> > tion+Application). >> >> Thanks, I did not know about this tool, which sounds excellent. >> >> > Unless you are using XWiki prior to 4.2 , using Wiki Component is >> definitely >> > the recommended way to writes Groovy components. Registering >> > components "by hand" from a groovy script has many drawbacks not only >> > the restart one, and you should avoid doing that. The best is of course >> to >> > write the components in Java, and install them as an extension. >> >> I've found the ability to write small Groovy scripts as components has >> been very handy and simpler than writing full extensions in Java. For >> utilities that I don't wish to make into public extensions the burden of a >> small Groovy script into a proper extension seems prohibitive (although >> that may just be that I haven't written one yet, and I'm just a walker at >> the bottom of a hill complaining about how high it looks...). Last time I >> asked there is was no simple way to install private extensions. Also, I >> didn't have much luck writing a proper component in Groovy, which I >> sometimes prefer to Java. >> _______________________________________________ >> users mailing list >> users@xwiki.org >> http://lists.xwiki.org/mailman/listinfo/users >> > >
