- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] [Proposal] Components Annotations
by Vincent Massol 26 Mar '09

26 Mar '09

Hi, To start with I propose to model against the plexus annotations but more simple: * Component * Requirement * Configuration /** * Marks a class as a XWiki component. */ @Documented @Retention(RUNTIME) @Target(TYPE) @Inherited public @interface Component { Class<?> role(); String hint() default ""; String instantiationStrategy() default ""; } /** * Configures a requirement. */ @Documented @Retention(RUNTIME) @Target({ FIELD, METHOD }) @Inherited public @interface Requirement { Class<?> role() default Object.class; String hint() default ""; // // HACK: This is here to support component requirement lists, which can take a list of hints // String[] hints() default {}; } Note: not sure yet why plexus says it's a hack. /** * Marks a field as a configuration element with a default value. */ @Documented @Retention(RUNTIME) @Target(FIELD) @Inherited public @interface Configuration { String name() default ""; String value(); } So for example in the code you'd have: @Component(role=Parser.class) public class WikiModelXWikiParser implements Parser... { @Requirement private LinkParser linkParser; .... wdyt? I'm still researching. Thanks -Vincent

2 2

[xwiki-devs] [VOTE] Release date and roadmap for 1.8.1
by Vincent Massol 26 Mar '09

26 Mar '09

Hi, I'm proposing that we release XE 1.8.1 on the 6th of April. It would have been 3 weeks since the release of 1.8 and we'll have plenty of important fixes and improvements for our users. Note that 1.8.1 is mainly for rendering/wysiwyg improvements. The roadmap is currently defined in jira: - For wysiwyg http://tinyurl.com/d75olg - For rendering http://tinyurl.com/cwpchk Note that more issues will be put for rendering and other domain. The idea is to time box this for the 6th of April. Here's my +1 Thanks -Vincent

5 4

Re: [xwiki-devs] [xwiki-notifications] r18027 - in platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg: client/plugin/macro/exec client/widget/rta/internal server server/cleaner/internal server/converter/internal
by Vincent Massol 26 Mar '09

26 Mar '09

Hi Marius, On Mar 26, 2009, at 12:26 AM, mflorea (SVN) wrote: > Author: mflorea > Date: 2009-03-26 00:26:55 +0100 (Thu, 26 Mar 2009) > New Revision: 18027 > > Modified: > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > client/plugin/macro/exec/RefreshExecutable.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > client/widget/rta/internal/IEBehaviorAdjuster.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > server/DefaultWysiwygService.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > server/cleaner/internal/DefaultHTMLCleaner.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > server/cleaner/internal/WysiwygCleaningFilter.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > server/converter/internal/EventsHTMLConverter.java > platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ > server/converter/internal/XWikiHTMLConverter.java > Log: > Updated the WYSIWYG code due to: > * XWIKI-3456: Provide way to control the HTML cleaning filters > executed by the HTML Cleaner > * XWIKI-3457: XHTML parser shouldn't run the HTML Cleaner > Also some minor IE fixes. [snip] > import com.xpn.xwiki.web.Utils; > import com.xpn.xwiki.wysiwyg.server.cleaner.HTMLCleaner; > @@ -49,8 +53,12 @@ > { > org.xwiki.xml.html.HTMLCleaner cleaner = > (org.xwiki.xml.html.HTMLCleaner) > Utils.getComponent(org.xwiki.xml.html.HTMLCleaner.ROLE); > - Document document = cleaner.clean(new > StringReader(dirtyHTML)); > - filter.filter(document); > + HTMLCleanerConfiguration config = > cleaner.getDefaultConfiguration(); > + List<HTMLFilter> filters = new ArrayList<HTMLFilter>(); > + filters.add(filter); I think it would be good to add a good comment here explaining why you have to run your filter first. > > + filters.addAll(config.getFilters()); > + config.setFilters(filters); > + Document document = cleaner.clean(new > StringReader(dirtyHTML), config); > return XMLUtils.toString(document); > } > } [snip] Thanks -Vincent

2 1

[xwiki-devs] [Proposal] Find out active XE installations
by Vincent Massol 26 Mar '09

26 Mar '09

Hi devs, I think it would be interesting for us to know how many people install and use our software. Of course we'd need to do this in a non intrusive manner that adds value for the user. Here's an idea Ludovic and I have discussed: * In the administration page add a blog panel by default (replacing the create page panel for ex which IMO isn't needed there) showing the last 5 RSS feeds from xwiki.org -> This is useful for the admin users since they need to know the latest versions and news about the software they use -> They can remove the panel easily if they don't want to see news -> We can generate a unique id based on the user's system (http://johannburkard.de/blog/programming/java/Java-UUID-generators-compared… ) so that we can identify active installs We could then define what we call an active install (say a ping at least once every month for ex) and we can find: - how many new installs per day/month/year - how many users stop using xwiki after some time and what the average time it's used actively Obviously we won't get perfect data (people will remove the panel, others won't be connected to the internet, etc) that but it seems to me it would a good guess. Once we get this data we could display it on xwiki.org (we could even display it in the stats space with the other data). WDYT? Thanks -Vincent

3 5

[xwiki-devs] GSOC 2009 : Google Docs Integration in XWIKI
by Arun Reddy 26 Mar '09

26 Mar '09

Hello devs, I am interested in the idea of "Google Docs Integration in XWIKI ". This idea is an extension to the existing Google Docs Plugin : http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/Google+Docs+Integrat… I have successfully installed that plugin with the help of sergiu and ludovic. Learnt how it works. Looking out how to integrate various google documents ( docs,spreasheets,. powerpoint) into xwiki. I will be happy if you can post few of your ideas on what all features can be included and considered for extending this feature. -- Best Regards, Arun Reddy

2 2

[xwiki-devs] status of "Social Networking via OpenID support in Xwiki?" for GSOC?
by Niels Mayer 26 Mar '09

26 Mar '09

I've noted some more comments about widget integration in general, but nothing as specific or useful (IMHO) as a project to integrate http://www.google.com/friendconnect/ ( http://www.youtube.com/v/N94s7ix0JPo&hl=en&autoplay=1 ) with Xwiki. That way people with the appropriate ID/credentials compatible w/ google friendconnect's OpenID would be able to login and leave authenticated comments on a wiki. A while back Thilina Buddhika ( http://www.mail-archive.com/[email protected]/msg07563.html ) expressed interest in this subject on this list; I was wondering if that interest continues, or if others might find this an interesting pursuit for GSOC 2009. The user experience should be that those w/ openID credentials should get an automatic login into Xwiki, and that the same authentication would also drive the friendconnect "widgets." I think the widgets themselves could easily be integrated into Xwiki's existing panel system. Therefore, the main work would be in creating a smoothly-integrated OpenID-based auth system giving appropriately credentialed users an automatic "authenticated guest" login. This login allows authenticated comments and registration, making commenting much easier and straightforward in Xwiki. Also, registration could always associated with a real user and not a spam account at mail.ru... Although the construction of widget "panels" itself might be simple, some of the authorization issues might be thorny. For example, do you publicly display your friends-list-widget-panel to all unauthenticated users and search engines, or do only logged-in users get access? Likewise, when "friends" log in or view your site, they might automatically receive special privilege based on their authenticated-friend status, e.g. view-access to a private part of the wiki, for example. This might require extension of the Rights system in Xwiki with extra roles alongside "unathenticated user", such as "openid authenticated user" and "openid authenticated friend." ... Here's the original messages and a summary of replies: On 02 Feb 2009, Thilina Buddhika wrote: [xwiki-devs] Possible project ideas for XWiki in GSoC 2009 I have a growing interest on XWiki and willing to take part in its development. I am also planning to apply for GSoC 2009 (yet to be announced) and I have realised that XWiki is a challenging and promising open source project for GSoC 2009. When watching the developer list, I found this mail by Niels Mayer with the subject,* "Social Networking via OpenID support in Xwiki?"*. And It looks like an intersting idea. I also found that there was a GSoC 2008 project related to this idea [1]. So is it possible to continue this project further? Other than the above idea, I would like to know the other possible project ideas for GSoC 2009. If it is too early I am posting about this, then lets leave it for the next couple of weeks. Anyway I am trying to get familiarized with Xwiki until the GSoC 2009 is announced. [1] - http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SSOAndOpenIDSupport ................................... from: Niels For some strange reason, I think this is an excellent idea :-) > > Of these, which has the easiest to integrate: > http://www.google.com/friendconnect/ > http://developers.facebook.com/connect.php > > http://developer.myspace.com/Community/blogs/devteam/archive/2008/12/09/int… > > Friendconnect has always looked most interesting of the lot, since it will > give you a variety of customizable friendconnect "widgets" . Once you > request and customize a particular instance, google generates the code and > presents it in a scrollable textarea. > > Reusing the framework of one of Xwiki's existing panels is a good way to > wrap Google Friendconnect socialnetworking into an Xwiki site. You'd > basically take the code and paste it into the panel document. Then layout > one or more of the google panels into the "sidebars" in Xwiki. This permits > xwiki to layout the friendconnect panels as if they were :"one of it's > own." > > Probably the easiest first-experiment would be to take an existing panel > that you probably don't use, like /xwiki/bin/inline/Panels/Welcome; as > 'Admin' click "edit" and then paste in the google code between > #panelheader("Welcome") and #panelfooter(). Later, create more via > http://nielsmayer.com/xwiki/bin/view/Panels/CreatePanel ... > > This video shows what happens on the google-side: > http://www.youtube.com/v/N94s7ix0JPo&hl=en&autoplay=1 > > I haven't looked at friendconnect's OpenID implementation so I don't know > how it would coexist or overlap w/ Xwiki's auth. > I'd assume you'd create an implementation per > > http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-core/src/main/… > follow instructions in > > http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication#HCustomA… > > You mentioned GSOC 2008 and > http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/SSOAndOpenIDSupport > ... > what is the status of any code completed to date? > ............................... Vincent Massol: I'm pretty sure we'll all want to have widget integration as a GSOC > 2009 project (open social, etc). > ............................... Thomas Mortagne: > The OpenId authenticator and provider already works pretty well based > in the current not very clean authentication api with some hack > > because Markus did not had choice to do this otherwise. I just did not > had time to integrate it yet in the trunk but Raffaello Pelagalli > started do to some test with it to integrate between > http://l10n.xwiki.org and xwiki.org farms (l10n is on its own instance > > of XWiki). > > See http://jira.xwiki.org/jira/browse/XWIKI-2630 , > http://jira.xwiki.org/jira/browse/XWIKI-2588 and > http://jira.xwiki.org/jira/browse/XSALBATROSS-34 > > .................................. Markus Lanthaler: > Right. The implementation is complete but I guess the tests are still > missing (kind of difficult to write meaningful tests for it). > > The implementation supports both, RP and server. XWiki can accept OpenIDs > from other sites as well as issue OpenIDs to be used on other sites > supporting OpenID. That way you can use your XWiki account all over the web > > (well at least on sites that support OpenID). > > Niels http://nielsmayer.com

1 0

Re: [xwiki-devs] [xwiki-notifications] r17994 - in platform/core/branches/xwiki-core-1.8: xwiki-core/src/main/java/com/xpn/xwiki/doc xwiki-core/src/test/java/com/xpn/xwiki/doc xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/bloc
by Thomas Mortagne 25 Mar '09

25 Mar '09

On Wed, Mar 25, 2009 at 15:51, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: > tmortagne (SVN) wrote: >> + if (header.getLevel().getAsInt() <= HeaderLevel.LEVEL2.getAsInt()) { > > Couldn't the level be Comparable? Actually, as an enum, it already is. Improving the code by using it. Thanks Sergiu > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Thomas Mortagne

1 0

[xwiki-devs] [Proposal] XE 1.9 + XE 2.0 + Roadmap for XE 1.9
by Vincent Massol 25 Mar '09

25 Mar '09

Hi devs, XE 2.0 ===== We've had discussion about XE 2.0 in the past. I think now is the right time to release it and we should prepare to do so. Two reasons; 1) We've had a lot of new features (new rendering, new wysiwyg, webdav, REST, office import, usability improvements, etc) added recently in 1.8 and this alone warrants calling it 2.0. The new rendering and new wysiwyg could be set as default in XE 2.0. 2) XE 1.0 marked a stability level. XE 2.0 will mark another stability level (I'm thinking about the old wysiwyg editor which could be said to be stable...) 3) It's been almost exactly 2 years since we released XE 1.0, it's high time for a major release. However since we still have a bit of work to fully finish the new rendering and new wysiwyg and since we want user feedback from 1.8 to ensure we get a rock solid 2.0 release I propose to have a XE 1.9 release before the XE 2.0 (which would be a promotion of XE 1.9 final with the config change to have new syntax/wysiwyg as defaults). The other advantage of releasing XE 2.0 is that we want to start the maintenance period for the old rendering/old wysiwyg as early as possible to get new people to use the new system. Once 2.0 is released we'll continue releasing bugfix versions of 1.9.x from time to time but we'll advise people to switch to 2.x. I propose we keep support for the old 1.0 syntax (either using the old code or using the 1.0 --> 2.0 syntax converter) for 1 year. This is the time we have to make our existing users switch to the new syntax. Note that with the automatic converters it shouldn't be something too difficult. Roadmap for XE 1.9 ================ General:It's a stabilization release meaning we must resist putting new things in it and fix what doesn't work well enough. Content proposal: * Finish/stabilize/document new rendering - Thomas/Vincent * Finish/stabilize/document new wysiwyg editor - Marius/Anca * Finish/stabilize/document office importer + doc splitter/management - Asiri * Finish/stabilize/document webdav - Asiri * Finish/stabilize/document REST support - Fabio * Finish/stabilize/document new blog application - Sergiu/Guillaume * Continue UI improvements (ex: new treeview, new search interface, full list to be defined) - JV/Ecaterina/Guillaume * Fix search using lucene plugin - ???? * Finish XE French translations - JV/Guillaume * Fix other bugs (watchlist, page names with special chars, etc) - All * Refactoring of apps to use more of SSX - Jerome? Note: I don't think we can commit to have a new skin system or a new skin in place for the 1.9 timeframe. Proposed Dates: * 1.9M1: 6 April * 1.9M2: 4 May * 1.9RC1: 18 May * 1.9RC2/Final: 1 June * 2.0: 15 June WDYT? Thanks -Vincent

11 20

Re: [xwiki-devs] [xwiki-notifications] r17994 - in platform/core/branches/xwiki-core-1.8: xwiki-core/src/main/java/com/xpn/xwiki/doc xwiki-core/src/test/java/com/xpn/xwiki/doc xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/block xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/internal/renderer xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/internal/renderer/chaining xwiki-rendering/xwiki-rendering-api/src/main/java/org/xwiki/rendering/liste
by Sergiu Dumitriu 25 Mar '09

25 Mar '09

tmortagne (SVN) wrote: > + if (header.getLevel().getAsInt() <= HeaderLevel.LEVEL2.getAsInt()) { Couldn't the level be Comparable? -- Sergiu Dumitriu http://purl.org/net/sergiu/

1 0

[xwiki-devs] [Proposal] New Search Interface
by Ecaterina Valica 25 Mar '09

25 Mar '09

Hi devs, This week I've been working on making a new UI proposal for the existing XWiki search interface. I would really apreciate your feedback on my proposal mockups that can be found at http://incubator.myxwiki.org/xwiki/bin/view/Mockups/Search+Interface#propos… If you're interested in more information, other mockups variation and analysis can be found on the same page. Thank you, Ecaterina Valica

5 10