October 2011 - xwiki-devs@xwiki.org

[xwiki-devs] XWiki logo around
by coldserenity 20 Nov '11

20 Nov '11

Hi, I remember once there was a contest for new XWiki logo but due to elections fail (there would have been too many unsatisfied people if any of newly suggested logos had been approved) the process has gracefully ended (which, in my opinion, was a good decision) I also think that it would be worthless to conduct another competition/election amongst users because as the saying goes - tastes differ. The only thing users can contribute are their ideas (which might be accepted or might not which is fair) regarding shapes and symbols to use. Decision about visual design should be made within very very small circle of visual designers probably with one or two people involved in the project to chill down designers' burning imagination :) Having all of the above said, I would suggest to collect a set of shapes and symbols for new XWiki logo each supplied with description of underlying meaning. And then (having revised all of the comments in some of the former posts regarding what new logo should be: symmetric/asymmetric, complex/simple, round/firm) provide all that to a designer to draw several sketches. And then by internal vote (at maximum the development team members involved) choose the new logo. This thread is for storing all of the ideas on the new XWiki logo. At least that's what I (as a user) will be using it for may any ideas to come. Join :) Regards, Roman -- View this message in context: http://xwiki.475771.n2.nabble.com/XWiki-logo-around-tp6074956p6074956.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

1 2

[xwiki-devs] [VOTE] Adding notions of Locale and Version in EntityReference
by Vincent Massol 16 Nov '11

16 Nov '11

Hi devs, After much brainstorming with Thomas and with the implementation of the new model I'm doing, we've come to the conclusion that it would be better to add the notions of Locale and Version in EntityReference. The main reasons are: * otherwise we need to introduce a notion of UniqueEntityReference in the model and it makes it very awkward at an API level (user need to constuct a UniqueEntityReference from an EntityReference depending on the APIs used) * it makes APIs more complex than what they could be. For example: - getDocument(EntityReference) - getDocument(EntityReference, Locale) - getDocument(EntityReference, Version) - getDocument(EntityReference, Locale, Version) vs - getDocument(EntityReference) (subnote: this is why I introduced UniqueEntityReference in the model) * It'll mean that anywhere we use an entity reference we'll be able to reference a specific version of that entity and/or a specific language. Some example: including a specific version of a page, referencing a specific version of an attachment in wiki syntax, etc. In a first version I'd like to only introduce a generic get/setAttributes (to allow extensibility) in EntityReference + get/setLocale/Version (for easiness of access). ATM I'm not planning to define a textual syntax for attributes (but it could something like: wiki:space.page[name1=value1, … nameN=valueN]). I'm not asking to vote on this. Here's my +1 Thanks -Vincent

6 20

[xwiki-devs] How to use RESTFUL API to insert Objects on Pages
by Mark Wallace 16 Nov '11

16 Nov '11

Hi all. Short version of my question: Can anyone point me to an example of adding object of a custom class to a page via the ReSTful API? And now for the long version of my question: I can successfully create a page using REST, but can't add an object. Here is the problem step by step. 1) Using this XML definition in a file called AlinaPage.xml: <?xml version="1.0" encoding="UTF-8"?> <xwiki:page xmlns:xwiki="http://www.xwiki.org" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.xwiki.org C:\Users\mwallace\ Desktop\xwiki_rest_model.xsd"> <xwiki:link href="http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Main/pages/Alina+Frey/o…" rel="http://www.xwiki.org/rel/o bject"></xwiki:link> <xwiki:id/> <xwiki:fullName/> <xwiki:wiki/> <xwiki:space>Main</xwiki:space> <xwiki:name>Alina Frey</xwiki:name> <xwiki:title/> <xwiki:parent/> <xwiki:parentId/> <xwiki:xwikiRelativeUrl/> <xwiki:xwikiAbsoluteUrl/> <xwiki:translations/> <xwiki:syntax/> <xwiki:language/> <xwiki:version/> <xwiki:majorVersion>1</xwiki:majorVersion> <xwiki:minorVersion>0</xwiki:minorVersion> <xwiki:created>2011-07-02T12:32:00-04:00</xwiki:created> <xwiki:creator>XWiki.mwallace</xwiki:creator> <xwiki:modified>2011-07-02T12:32:00-04:00</xwiki:modified> <xwiki:modifier/> <xwiki:content>{{include document="XWiki.PersonSheet"/}}</xwiki:content> </xwiki:page> 2) I do the following command, which adds the page successfully: C> curl -u mwallace:password -X PUT --data-binary "@AlinaPage.xml" -H "Content-Type: application/xml" http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Main/pages/Alina+Frey 3) The resulting page from a HTTP GET is: <?xml version="1.0" encoding="UTF-8"?> <page xmlns="http://www.xwiki.org"> <link href="http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Main" rel="http://www.xwiki.org/rel/space"/> <link href="http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Main/pages/Alina%20Frey…" rel="http://www.xwiki.org/rel/history"/> <link href="http://localhost:8080/xwiki/rest/syntaxes" rel="http://www.xwiki.org/rel/syntaxes"/> <link href="http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Main/pages/Alina+Frey" rel="self"/> <link href="http://localhost:8080/xwiki/rest/wikis/xwiki/classes/Main.Alina%20Frey" rel="http://www.xwiki.org/rel/class"/> <id>xwiki:Main.Alina Frey</id> <fullName>Main.Alina Frey</fullName> <wiki>xwiki</wiki> <space>Main</space> <name>Alina Frey</name> <title>Alina Frey</title> <parent/> <parentId/> <xwikiRelativeUrl>http://localhost:8080/xwiki/bin/view/Main/Alina+Frey</xwikiRelativeUrl> <xwikiAbsoluteUrl>http://localhost:8080/xwiki/bin/view/Main/Alina+Frey</xwikiAbsoluteUrl> <translations/> <syntax>xwiki/2.0</syntax> <language/> <version>4.1</version> <majorVersion>4</majorVersion> <minorVersion>1</minorVersion> <created>2011-07-02T12:45:12-04:00</created> <creator>XWiki.mwallace</creator> <modified>2011-07-02T21:33:48-04:00</modified> <modifier>XWiki.mwallace</modifier> <content>{{include document="XWiki.PersonSheet"/}}</content> </page> 4) But then, using this definition of an object in file AlenaObject.xml: <?xml version="1.0" encoding="UTF-8"?> <xwiki:object xmlns:xwiki="http://www.xwiki.org" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.xwiki.org C:\Users\mwallac e\Desktop\xwiki_rest_model.xsd"> <xwiki:id/> <xwiki:guid/> <xwiki:pageId>Main.Alina Frey</xwiki:pageId> <xwiki:wiki/> <xwiki:space>Main</xwiki:space> <xwiki:pageName>Alina Frey</xwiki:pageName> <xwiki:className>XWiki.PersonClass</xwiki:className> <xwiki:number>0</xwiki:number> <xwiki:headline/> <xwiki:property name="_knows"> <xwiki:value>Main.Alena</xwiki:value> </xwiki:property> <xwiki:property name="_knows"> <xwiki:value>Main.Judi Wallace</xwiki:value> </xwiki:property> <xwiki:property name="name"> <xwiki:value>Alina Frey</xwiki:value> </xwiki:property> </xwiki:object> 5) I try the following command, which does NOT insert the object properly: C> curl -u mwallace:password -X PUT --data-binary "@AlinaObject.xml" -H "Content-Type: application/xml" http://localhost:8080/xwiki/rest/wikis/xwiki/spaces/Main/pages/Alina+Frey/o… 6) Rather, I get this error message: <html> <head> <title>Status page</title> </head> <body> <h3>The server has not found anything matching the request URI</h3><p>You can get technical details <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.5">here</a>.<br> Please continue your visit at our <a href="/">home page</a>. </p> </body> </html> What am I doing wrong? -- Mark Wallace Principal Engineer, Semantic Applications Modus Operandi, Melbourne, FL, USA

2 1

[xwiki-devs] [VOTE] Should "delete" rights be considered at the document level?
by Sergiu Dumitriu 02 Nov '11

02 Nov '11

Rights have different scopes in XWiki. Administration rights can only be set on a space or wiki level, and any "admin" right set on a document alone will be silently ignored. Programming rights are only considered when set on the xwiki:XWiki.XWikiPreferences document, being ignored in any other virtual wiki and at the space or document level. Delete rights are a bit special as well. By default, the creator of a document has delete rights on that document. Unlike the other rights which default to true when no right is set, this one defaults to false. So, by default, when no "delete" rights are set on the document/space/wiki, only the creator of a document and administrators are allowed to delete it. Should we allow setting the delete right at the document level? Personally, I'd say no, since it's a rare requirement for a non-creator to be able to delete just one document. Space-level rights should be enough, IMO. -- Sergiu Dumitriu http://purl.org/net/sergiu/

3 4

[xwiki-devs] Technical name for "Application Within Minutes"
by Marius Dumitru Florea 02 Nov '11

02 Nov '11

Hi devs, We need to decide on a technical name for the "Application Within Minutes", i.e. the name of the platform module and the name of the space that will hold the Application Within Minutes pages. For now I committed my code in xwiki-platform-applicationWithinMinutes and I used the "ApplicationWithinMinutes" space name but this is not consistent with the way we named modules and spaces so far. Do you have any suggestions? We could use simply xwiki-platform-application, but it collides with xwiki-platform-application-manager, and I don't think it's a good idea to merge them. Is application manager still used? Is it going to be replaced by the extension manager? Thanks, Marius

4 6

[xwiki-devs] Google Apps Integration with XWiki
by Ludovic Dubost 31 Oct '11

31 Oct '11

Hi, A little week-end fun which can turn out quite useful. I've coded a Google Apps Integration module. It allows to: - search for a document in your Google Docs instance and upload it to an XWiki page. - to click on an "edit link" (like webdav) to open an attachment in Google Docs, then edit it (in another tab), and then in one click retrieve it to resave it in XWiki. - the latest feature supports overwriting a document with the same name in your Google Docs instance or to create a new separate file. The extension is here and the code in GitHub: http://extensions.xwiki.org/xwiki/bin/view/Extension/GoogleAppsIntegration It's only using a XAR + Groovy and does not need any templates modification (the attachment zone is enhanced by a JSX). Some stuff that could be added: - automatically give more rights for others to edit - send a Wiki content or a Wiki table to Google Docs and resave in the Wiki page (I leave that to XWiki rendering specialists :)) - additional UI feature to possibly use a Lightbox to launch the editing and the edit screen Ludovic -- Ludovic Dubost Founder and CEO Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

1 0

[xwiki-devs] [Proposal] New FAQ Application and new FAQ strategy
by Vincent Massol 31 Oct '11

31 Oct '11

Hi devs, I've created a new FAQ application. It's currently available from http://www.xwiki.org/xwiki/bin/view/FAQ/WebHomeNew (it's linked from the old one: http://www.xwiki.org/xwiki/bin/view/FAQ/WebHome) The reason I rewrote it is because I think FAQs are important and that we're not using it enough Here's how I think it could work out: * If a user has a question he/she should verify if it's already in the FAQ. If not then he/she should post a message for the XWiki Mailing List/Forum. * The strategy is then for people who know the answer to create a new FAQ entry about the question and reply in the mail with the link to the new FAQ Entry In this manner we will quickly enrich this FAQ database. Of course the FAQ answers should be as short as possible and point to existing docs (if those docs don't exist they should be updated/created). Basically I see FAQ as entry points to our documentation, from the point of view of someone asking questions of the type "how do I….". Thus there can be several FAQ entries all having the same link to the documentation. WDYT? Thanks -Vincent PS: As you can see I have only 4 entries right now since we need to migrate exisitng FAQ entries: - use a good page name - rewrite them in XWiki Syntax 2.0 - verify their accuracy - update docs where needed Maybe we should have a FAQ day to work on that?

3 3

[xwiki-devs] [Contrib] xwiki-extension-mantis
by Jérémie 30 Oct '11

30 Oct '11

Hi all, I would add my extension in xwiki-contrib. This allows to use the mantis soap client in a macro. My first code https://github.com/jerr/xwiki-extension-mantis seems to work (my github account is jerr). According to my understanding of http://contrib.xwiki.org/xwiki/bin/view/Main/WebHome this email is the first step. Tell me if you need more information. Regards, Jeremie.

2 1

[xwiki-devs] [Proposal] Supported Browser Strategy
by Sorin Burjan 28 Oct '11

28 Oct '11

Hello, There are a lot of browsers out there and supporting them all in all versions is just too hard to be done in a quality manner with the number of committers we have. In addition we should try to explicitly list the level of support we have for each browser on xwiki.org so that users know what to expect, on a release by release basis. Thus I believe that we need a strategy and a general agreement about what browsers we want to support. I propose that by "supporting" we mean: - issues created for these browsers in jira are not closed as won't fix and we make a best effort to fix them - we include these browsers in our tests (be them automated or manual) - when we create new features or modify existing features we make a best effort to verify that they work on the supported list of browsers So here's a proposal: * Drop IE6 support - Dropping IE6 will provide a lot of benefits: 1) allow us to use newer technologies which are more useful, 2) remove lots of hacks we've accumulated over the years and 3) have more time to work on more relevant browser versions. A lot of products have now dropped support for IE6 and it's time we do it too. * Drop IE7 support - Currently, IE7's market share is similar to the one of IE6. They are both considered obsolete browsers for the same reasons as IE6 * Support IE8 - currently IE8 has the largest market share of all IEs and it is widely used in enterprise environments. * Support IE9 starting with 3.3 release - IE9 is slowly getting ground in front of IE8 * Support Mozilla Firefox 3.6 - even with the new release stragtegy of Mozilla, Firefox 3.6 still has aprox. 50% of all Mozilla browsers. This browser is still supported officially by Mozilla * Support Mozilla Firefox 4 and newer - The proposal is to support only the latest stable Firefox release since FF4+ have automatic upgrades. * Support Google Chrome 13 an newer - support the latest stable version of Chrome released as with FF4+ * Support Safari 5 in XWiki 3.3 and newer. * Don't officially support Opera - This means that we don't test against it all the time, we don't ensure that new feature work on it but if someone raises an issue in jira and it's easy to fix (or if someone provides a patch) then we fix it. * For all other non mentioned browsers - We don't officially support them (same strategy as for Opera above) I also propose that in the Release notes for each version of XWiki we mention the list of browsers we have tested against and that we "support". Best regards, Sorin B.

10 10

Re: [xwiki-devs] [VOTE] Make org.xwiki.rendering.internal.macro.MacroContentParser public (summary)
by Thomas Mortagne 27 Oct '11

27 Oct '11

Done On Wed, Oct 26, 2011 at 7:09 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com> wrote: > Hi devs, > > Right now it's not very easy for a macro to properly deal with content > parsing especially the way to find which syntax to use to parse the > content. > > There is a very useful tool that we are using internally but its not > public so contribution macros can't use that. > > I propose to move > org.xwiki.rendering.internal.macro.MacroContentParser to > org.xwiki.rendering.macro.MacroContentParser. > > WDYT ? > > Here is my +1 > > -- > Thomas Mortagne > -- Thomas Mortagne

1 0