Hi,
While moving Event classes I've noticed that we have various naming schemes for them. I'm proposing to standardize on one only.
Right now we have the generic form <type><qualifier>Event with 3 different qualifier strategies:
* ApplicationStartedEvent --> preterit form
* ScriptEvaluationStartsEvent --> present form
* AnnotationAddEvent --> nominal form
I'm proposing that we use the form: <type><qualifier>Event where <qualifier> is of the preterit form, e.g:
* ApplicationStartedEvent
* ScriptEvaluationStartedEvent
* AnnotationAddedEvent
And for Event about actions that have not yet been executed to use the present progressive form, e.g.:
* ApplicationStartingEvent
* ScriptEvaluationStartingEvent
* AnnotationAddingEvent
WDYT?
Thanks
-Vincent
We can remove the 2.4 branch in hudson now (I have removed it in SVN yesterday).
Thanks
-Vincent
On Nov 9, 2010, at 4:05 AM, Caleb James DeLisle wrote:
> Trying out a new test reporter, tell me what you think.
>
>
> Statistics Report:
> 1 tests stopped failing, yay :)
> 17 tests failed out of a total of 2044
> The total time taken to run the tests was 845.61536 seconds,
> and the average time taken by a test was 0.41370615 seconds.
> The fastest test ran in 0.0 seconds,a record held by
> http://hudson.xwiki.org/job/xwiki-platform-core-2.4/org.xwiki.platform$xwik…
> The slowest test ran in 73.998 seconds,and that one was
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
> -------------------------------------------------------------------------------
> Detailed Failure Report:
> 8 Regressions,
> 0 Tests are Probably Flickering,
> 9 Failures
> -------------------------------------------------------------------------------
>
> Regressions:
> These tests have failed for the first time in stored history.
>
> Name: testDocumentCacheSync
> Details: null expected:<[modified ]content> but was:<[]content>
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Name: testDocumentCacheSyncForAttachments
> Details: Name: PUT URI:
> http://localhost:8081/xwiki/rest/wikis/xwiki/spaces/Test/pages/AttachementC…
> Status code: 404 Status text: Not Found Response: <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>
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Name: Validating XHTML validity for: space=XWiki, page=DeletedDocuments executed with credentials
> Admin:admin
> Details: Validation errors in space=XWiki, page=DeletedDocuments FATAL: The reference to entity "id"
> must end with the ';' delimiter. at line [353] column [68]
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Name: Validating XHTML validity for: /xwiki/bin/view/Main/AllDocs?view=deletedDocs executed with
> credentials Admin:admin
> Details: Validation errors in /xwiki/bin/view/Main/AllDocs?view=deletedDocs FATAL: The reference to
> entity "id" must end with the ';' delimiter. at line [363] column [68]
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Name: Validating Dutch Web Guidelines validity for: space=XWiki, page=DeletedDocuments executed with
> credentials Admin:admin
> Details: Validation errors in space=XWiki, page=DeletedDocuments FATAL: The reference to entity "id"
> must end with the ';' delimiter. at line [353] column [68]
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Name: Validating Dutch Web Guidelines validity for: /xwiki/bin/view/Main/AllDocs?view=deletedDocs
> executed with credentials Admin:admin
> Details: Validation errors in /xwiki/bin/view/Main/AllDocs?view=deletedDocs FATAL: The reference to
> entity "id" must end with the ';' delimiter. at line [363] column [68]
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Name: Validating XWiki validity for: space=XWiki, page=DeletedDocuments executed with credentials
> Admin:admin
> Details: Validation errors in space=XWiki, page=DeletedDocuments FATAL: The reference to entity "id"
> must end with the ';' delimiter. at line [353] column [68]
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Name: Validating XWiki validity for: /xwiki/bin/view/Main/AllDocs?view=deletedDocs executed with
> credentials Admin:admin
> Details: Validation errors in /xwiki/bin/view/Main/AllDocs?view=deletedDocs FATAL: The reference to
> entity "id" must end with the ';' delimiter. at line [363] column [68]
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
> -------------------------------------------------------------------------------
>
> Failures:
> These tests have failed multiple times in a row.
>
> Failing for the past 2 builds.
> Name: Validating Dutch Web Guidelines validity for: space=Main, page=WebHome executed with
> credentials Admin:admin
> Details: Validation errors in space=Main, page=WebHome ERROR: At least one style attribute has been
> found on the page.
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-manager-tests-2.4/com.…
>
> Failing for the past 2 builds.
> Name: Validating Dutch Web Guidelines validity for: space=WikiManager, page=CreateNewWiki executed
> with credentials Admin:admin
> Details: Validation errors in space=WikiManager, page=CreateNewWiki ERROR: An input field has been
> found with no label association.
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-manager-tests-2.4/com.…
>
> Failing for the past 2 builds.
> Name: Validating Dutch Web Guidelines validity for: space=Main, page=WebHome executed with
> credentials Admin:admin
> Details: Validation errors in space=Main, page=WebHome ERROR: At least one style attribute has been
> found on the page.
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-manager-tests-2.4/com.…
>
> Failing for the past 2 builds.
> Name: Validating Dutch Web Guidelines validity for: space=Main, page=WebHome executed with
> credentials Admin:admin
> Details: Validation errors in space=Main, page=WebHome ERROR: At least one style attribute has been
> found on the page.
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-manager-tests-2.4/com.…
>
> Failing for the past 131 builds.
> Name: junit.framework.TestSuite@1f920cf
> Details: Could not start Selenium session: Failed to start new browser session: Error while
> launching browser
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Failing for the past 131 builds.
> Name: junit.framework.TestSuite@10f11b8
> Details: Could not start Selenium session: Failed to start new browser session: Error while
> launching browser
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Failing for the past 131 builds.
> Name: org.xwiki.it.ui.AllTests
> Details: Failed to connect to binary FirefoxBinary(/home/hudsonagent/firefox/firefox) on port 7055;
> process output follows: Error: cannot open display: :1.0 ÿError: cannot open display: :1.0 ÿ System
> info: os.name: 'Linux', os.arch: 'i386', os.version: '2.6.27.10-grsec-xxxx-grs-ipv4-64',
> java.version: '1.5.0_15' Driver info: driver.version: firefox
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Failing for the past 131 builds.
> Name: org.xwiki.it.ui.AllTests
> Details: Failed to connect to binary FirefoxBinary(/home/hudsonagent/firefox/firefox) on port 7055;
> process output follows: Error: cannot open display: :1.0 ÿError: cannot open display: :1.0 ÿ System
> info: os.name: 'Linux', os.arch: 'i386', os.version: '2.6.27.10-grsec-xxxx-grs-ipv4-64',
> java.version: '1.5.0_15' Driver info: driver.version: firefox
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
>
> Failing for the past 131 builds.
> Name: WYSIWYG Selenium Tests
> Details: Could not start Selenium session: Failed to start new browser session: Error while
> launching browser
> Link:
> http://hudson.xwiki.org/job/xwiki-product-enterprise-tests-2.4/com.xpn.xwik…
Hi,
We have created a mess we need to fix ASAP since event classes are public. Here's a proposal:
* Move Documents events (and all model events in general: classes, objects, etc) to the Model module in an event package (org.xwiki.model.event).
* Move Action events to xwiki-core for now (in a com.xpn.xwiki.event package)
* Move Annotations events to the annotation-core module in org.xwiki.annotation.event package
* Move script events to the xwiki-script module (in org.xwiki.script.event package)
* Move Attachments events to xwiki-core for now (in a com.xpn.xwiki.event package)
* Move Application started/stopped events to xwiki-container-api (in a org.xwiki.container.event package)
+1 from me
Thanks
-Vincent
Hi everybody!
I changed somethings in our XWiki source and now I want to make a
component or something like it to share with all of you, possibly
including it in the official source code.
This is the modifications I made:
* Store every attachment (including its revisions) in the filesystem,
not in the database (able to customize the storage folder in
xwiki.cfg).
* Set a "default group" to XWikiLDAPAuthServiceImpl, where all users
logged through Active Directory is automatically added to this group.
This is a workaround for the "Default Group" problem on Windows, where
the users belongs to the group in Active Directory but the "memberOf"
property comes empty.
My problem is I could not find an up-to-date tutorial about writing
components. I also could not find a simple explanation about how to
tell XWiki not to use XWikiHibernateAttachmentStore and
HibernateAttachmentVersioningStore, using my classes instead.
By the way, I'm not an advanced Java programmer, so I need the things
well explained! ;) Anybody can help?
Best regards!
Felipe Giotto
Hi devs,
Good job with the recent activity implementation!
I've noticed that when you build XE from trunk and run it, you see all the pages with an author of XWikiGuest. I would have expected to see them with an author of Administrator. Is that a bug? Maybe it's not related to the recent activity implementation but it doesn't sound right anyway.
Also if I click on XWikiGuest it goes to a non existing page (since XWikiGuest user doesn't exist). I think we shouldn't make XWikiGuest clickable.
Thanks
-Vincent
Good morning,
My name is Gregory GUENEAU and i am actually helping XWiki SAS for its marketing.
I am 39 years old and my all career, since 1992, have been in the numeric business. I first produced CD-ROM applications such as games, cultural applications, softwares for sales or training, etc. I progressively involved more and more in the internet business. I runned more than 250 projects for many companies like l'Oreal, Orange, Disney, Danone, etc. My main experiences were as Production Director and "image" business production co-Management in a very famous event company : "Le Public System". I also runned my own company : Avane, where i invented Chronopolys as a new project management system that got some awards thanks to the collaboration with XWiki.
I am also a professor and research director in "Gobelins, l'ecole de l'image" where i still teach project management. In this school i created a master degree training course, and had also the occasion to write a book published by Eyrolles "Conduite de Projets en Creation Numerique".
I can bring a lot of knowledge about user expectation in the community discussions, i hope you will appreciate.
Best
Gregory
On Nov 6, 2010, at 6:56 PM, Ludovic Dubost wrote:
> Le 06/11/10 13:33, Vincent Massol a écrit :
>> Hi,
>>
>> Just a notice that I'll remove the following branches from jira since we (open source xwiki developers) only support 2 branches (trunk + latest stable):
>>
>> • xwiki-core-1.5-curriki/
> 1.5-curriki is still needed for curriki. This core is still active.
Moved to http://svn.xwiki.org/svnroot/xwiki/curriki/branches/xwiki-core-1.5-curriki/
Thanks
-Vincent
>
>> • xwiki-core-1.8/
>> • xwiki-core-1.9/
>> • xwiki-core-2.1/
>> • xwiki-core-2.2/
>> • xwiki-core-2.3/
>> • xwiki-core-2.4/
>>
>> Please shout quickly if you have a good reason to keep one of these (also note that they'll always be in the svn history).
>>
>> Thanks
>> -Vincent
Hi all,
Ludovic suggested that I register an account on http://incubator.myxwiki.org/ so that we can work on a Balsamiq mockup.
I registered on this mailing list, but gather that the incubator is a different thing.
Could someone please set me up with this?
Thanks, Jim
On Nov 7, 2010, at 11:50 AM, sdumitriu (SVN) wrote:
> Author: sdumitriu
> Date: 2010-11-07 11:50:04 +0100 (Sun, 07 Nov 2010)
> New Revision: 32582
>
> Modified:
> platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/XWikiDocument.java
> Log:
> XWIKI-4726: Forward links are not refactored on rename causing broken links on rename to different space.
> Fixed.
> Patch from Stefan Abageru applied with some cleanup.
>
> Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/XWikiDocument.java
> ===================================================================
> --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/XWikiDocument.java 2010-11-06 21:41:04 UTC (rev 32581)
> +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/XWikiDocument.java 2010-11-07 10:50:04 UTC (rev 32582)
> @@ -5670,12 +5670,48 @@
> xwiki.saveDocument(backlinkDocument, saveMessage, true, context);
> }
>
> - // Step 4: Delete the old document
> + // Step 4: Refactor the links contained in the document
> + XWikiDocument newDocument = xwiki.getDocument(newDocumentReference, context);
> + XDOM newDocumentXDOM = newDocument.getXDOM();
> + List<LinkBlock> linkBlockList = newDocumentXDOM.getChildrenByType(LinkBlock.class, true);
> + XWikiDocument currentContextDoc = context.getDoc();
> +
> + try {
> + boolean modified = false;
> + for (LinkBlock linkBlock : linkBlockList) {
> + ResourceReference linkReference = linkBlock.getReference();
> + if (linkReference.getType().equals(ResourceType.DOCUMENT)) {
> + context.setDoc(this);
> + DocumentReference currentLinkReference =
> + this.currentDocumentReferenceResolver.resolve(linkReference.getReference());
> +
> + context.setDoc(newDocument);
> + DocumentReference newLinkReference =
> + this.currentDocumentReferenceResolver.resolve(linkReference.getReference());
> +
> + if (!newLinkReference.equals(currentLinkReference)) {
> + modified = true;
> + linkReference.setReference(this.compactWikiEntityReferenceSerializer
> + .serialize(currentLinkReference));
> + }
> + }
> + }
> + // Set new content and save document if needed
> + if (modified) {
> + newDocument.setContent(newDocumentXDOM);
> + xwiki.saveDocument(newDocument, context);
> + }
> + } finally {
> + // Restore original context
> + context.setDoc(currentContextDoc);
> + }
cool thanks stefan and sergiu. IMO we would benefit to introduce some private methods (or not so private if it has a general purpose) to perform this step (or other steps, I don't remember the existing code). checktyle wouldn't probably pass on this method as it is now.
BTW we have a refactoring module and I think it would be a good place to move the rename implementation to this new module... when someone has the time and energy to do so...
Thanks
-Vincent
> +
> + // Step 5: Delete the old document
> xwiki.deleteDocument(this, context);
>
> - // Step 5: The current document needs to point to the renamed document as otherwise it's pointing to an
> + // Step 6: The current document needs to point to the renamed document as otherwise it's pointing to an
> // invalid XWikiDocument object as it's been deleted...
> - clone(xwiki.getDocument(newDocumentReference, context));
> + clone(newDocument);
> }
>
> /**
The XWiki development team is pleased to announce the release of XWiki
Enterprise 2.5.1 and XWiki Enterprise Manager 2.5.1. These are bugfix
releases on the 2.5 branch.
The highlights of this release are: fixed and improved the PDF export,
fixed broken images from the office importer, fixed a severe performance
problem with many blog categories, and fixed broken scheduler functionality.
For more information, see the full release notes at:
- http://www.xwiki.org/xwiki/bin/Main/ReleaseNotesXWikiEnterprise251.
- http://www.xwiki.org/xwiki/bin/Main/ReleaseNotesXEM251.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi Caty,
On 11/03/2010 01:59 PM, evalica (SVN) wrote:
> Author: evalica
> Date: 2010-11-03 13:59:32 +0100 (Wed, 03 Nov 2010)
> New Revision: 32351
>
> Modified:
> platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Script.xml
> Log:
> XSCOLIBRI-243: Change page header shortcuts separator to a more simple one that assures readability
I can see that this commit is actually fixing XAANNOTATIONS-37. As all
the commits should have the issue they fix in the commit log (or the
multiple issues they fix), and I will assume that XAANNOTATIONS-37 was
created after this commit was done, you should edit the commit message
to reflect this (this will help me find the code that was committed for
that issue in the jira subversion tab).
See here instructions about how to do that:
http://subversion.apache.org/faq.html#change-log-msg , knowing that our
SVN allows revision property modifications.
Thanks,
Anca
> - Changed separator situated after #annotationsshortcut
>
> Modified: platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Script.xml
> ===================================================================
> --- platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Script.xml 2010-11-03 12:58:40 UTC (rev 32350)
> +++ platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Script.xml 2010-11-03 12:59:32 UTC (rev 32351)
> @@ -665,7 +665,7 @@
> var shortcutsContainer = $('commentsshortcut').up();
> var annShortcut = new Element('span', {'id' : 'annotationsshortcut'}).update('<a href="#' + this.annTabname + '">$msg.get("annotations.title")</a> ');
> shortcutsContainer.insert({top: annShortcut});
> - var separator = new Element('span', {'class' : 'separator'}).update('|');
> + var separator = new Element('span', {'class' : 'separator'}).update('·');
> annShortcut.insert({after : separator});
>
> annShortcut.observe('click', XWiki.displayDocExtra.bind(XWiki, this.annTabname, 'annotationsinline.vm', true));
>
> _______________________________________________
> notifications mailing list
> notifications(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/notifications
Hi guys,
If you can please test XE 2.6 RC1:
http://maven.xwiki.org/releases/org/xwiki/enterprise/
Once I get a few confirmations that it works well, I'll finish the release and publish it.
Thanks for your help!
-Vincent
Acting Release Manager for XE 2.6 RC1
Hello again,
Following my previous email, here is a first draft proposition about
the visual redesign of the suggest widget.
Currently the widget style is pretty off the colibri skin. A bit
better with toucan, but not really ideal either.
I propose we move to a simpler, lighter design, that make uses of
Color Themes. You can find a first proposal with two variants (that
you can test live) on the incubator :
http://incubator.myxwiki.org/xwiki/bin/view/Improvements/SuggestRedesignPro…
Note that this mail concerns only the first part of the document for
now : suggest with items without description (items with description
are not supported yet, I'll propose them later on).
Let me know what you think, and if you agree with the overall
direction. Then we can discuss the tiny bits.
Jerome.
Hi devs,
It's been two weeks since the release of 2.5, and there have been some
critical and not so critical bugfixes since. Most notably:
- images no longer appear in documents imported from office documents
- PDF styling was completely broken, now it has been greatly improved
See the full list of fixed issues here:
http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=p…
Does anybody want to commit something else?
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
Hi everyone,
Sergiu started mentioning the idea of a XE 3.0 when we defined the XE 2.6 roadmap. We need a more general agreement that we want a XE 3.0 and how to reach it.
As Sergiu I believe we need a XE 3.0 ASAP for the following reasons:
- it's been a bit more than 1 year since the XE 2.0 release and I feel it's good to have one major release every year
- we've added **lots** of features since XE 2.0. Check http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotes to get a feeling
- it's good for open source marketing
Before being able to release XE 3.0 I think:
- XE 2.6 is already planned for the 18th of November (with "mail this page" and "recent activity" features + icon/emoticon and wikiword support that was sneaked in surreptitiously)
- We should have a XE 2.7 release (1 month duration, ie leading us to the 18th of December) to finish started stuff:
-- Finish the Gadget integration since it's been started already and it's important. That said I'd actually be ok to not finish it if we think it's too much to release XE 3.0 quickly according to the dates below. Anca to tell us if it's possible in the timeframe.
-- First working extension manager that can be used to install XARs (replaces the old Packager on the back end side). Thomas to tell us if it's possible in the timeframe.
-- Recent Activity with apps sending events (XE 2.6 will already have a good part of it)
-- UI finishing touches
-- Some additional Security and Performance improvements if possible
-- etc (add what you'd like to see absolutely here - it should be work already started as much as possible and no new stuff)
- Release XE 3.0 one month after the XE 2.7 release, ie around 18th of January - ie end of January 2011)
Very important: XE 3.0 should be a maturation/conclusion release, i.e. concluding all the work started in the 2.x series (same as what we did for XE 2.0). It shouldn't be seen as revolutionary stuff that we should add from now on since it'll take a year more before those can be fully stabilized and we would loose the window of opportunity of doing a major release now.
Note: We shouldn't try to cram too much things in since that'll extend the lead time to release XE 3.0 and we'll loose the stabilization effect.
WDYT?
Thanks
-Vincent
Hi,
I'm summarizing some idea I've had about some tools to help the release process:
Idea 1: Create a semi-automated Release Plan page on xwiki.org
===================================================
* Read the POM from http://svn.xwiki.org/svnroot/xwiki/enterprise/trunk/distribution/jetty/hsql… (using aether)
* Find all transitive dependencies (using aether)
* For each dep:
** Read its POM
** Read the version from the pom, remove the SNAPSHOT part
** Read the JIRA URL from the pom
** Find the list of issues in jira with a fixfor equal to the read version
** If there are not closed issue display a warning message
** Display the list of issues found
** Read the SVN info from the POM to find the svn tag URL (using svnkit for example)
** With the version build a full URL
** Get the svn revision number of the last commit for that URL
** Do a svn log on trunk/ to find all commits since the last release
** Display them
This should give a Release Plan Dashboard allowing the releaser to see at a glance what should be released, saving him the work to:
- find all deps
- find which modules have been modified and needs to be released
Idea 2: Create a Release application on dev.xwiki.org
==========================================
* A very simple application with a home listing all past releases that have been done already + a create new release button
* When you press that create button it creates a new release page, copying a template page which has the release steps
* Use the todo macro/application to list all the steps to be performed in the release, allowing the release to tick them visually as he progresses through the release (it's important to be able to tick a task in view mode - if we don't have this feature in an existing todo/task macro then develop it).
WDYT? Would that help the release process? Any other ideas.?
Thanks
-Vincent
Hi,
To be discussed but I'd rather we call the macro "activity" for several reasons:
- it's shorter and easier to use (same reasoning as "avatar" vs "uservatar" macro)
- it's more generic
- we could want to add a parameter in the future that gives the time span (and it doesn't have specifically to be recent)
Thanks
-Vincent
On Nov 2, 2010, at 6:13 PM, evalica (SVN) wrote:
> Author: evalica
> Date: 2010-11-02 18:13:48 +0100 (Tue, 02 Nov 2010)
> New Revision: 32334
>
> Modified:
> enterprise/trunk/wiki/src/main/resources/Main/Dashboard.xml
> enterprise/trunk/wiki/src/main/resources/Main/RecentActivity.xml
> Log:
> XE-736: Rename Main.RecentChanges to Main.RecentActivity to reflect the new implementation
> - Changed macro name from recentchanges to recentactivity
>
> Modified: enterprise/trunk/wiki/src/main/resources/Main/Dashboard.xml
> ===================================================================
> --- enterprise/trunk/wiki/src/main/resources/Main/Dashboard.xml 2010-11-02 17:02:56 UTC (rev 32333)
> +++ enterprise/trunk/wiki/src/main/resources/Main/Dashboard.xml 2010-11-02 17:13:48 UTC (rev 32334)
> @@ -217,12 +217,12 @@
> = $msg.get("xe.dashboard.wiki.recentactivity") =
> #else
> = $msg.get("xe.dashboard.space.recentactivity", [$doc.space]) =
> - ## Set variables to limit recent changes to the current space and 15 items.
> + ## Set variables to limit recent activity to the current space and 15 items.
> #set ($rcSpace = $doc.space)
> #set ($rcChangesNb = 15)
> #end
>
> - {{recentchanges space="$!rcSpace" changesNb="$!rcChangesNb" /}}
> + {{recentactivity space="$!rcSpace" changesNb="$!rcChangesNb" /}}
>
> )))
> )))
>
> Modified: enterprise/trunk/wiki/src/main/resources/Main/RecentActivity.xml
> ===================================================================
> --- enterprise/trunk/wiki/src/main/resources/Main/RecentActivity.xml 2010-11-02 17:02:56 UTC (rev 32333)
> +++ enterprise/trunk/wiki/src/main/resources/Main/RecentActivity.xml 2010-11-02 17:13:48 UTC (rev 32334)
> @@ -1184,13 +1184,13 @@
> <defaultCategory>Content</defaultCategory>
> </property>
> <property>
> -<description>Displays the recent changes in this wiki or in the passed space, if any.</description>
> +<description>Displays the recent activity in this wiki or in the passed space, if any.</description>
> </property>
> <property>
> -<id>recentchanges</id>
> +<id>recentactivity</id>
> </property>
> <property>
> -<name>Recent Changes</name>
> +<name>Recent Activity</name>
> </property>
> <property>
> <supportsInlineMode>0</supportsInlineMode>
> @@ -1322,7 +1322,7 @@
> <defaultValue>true</defaultValue>
> </property>
> <property>
> -<description>Whether to show differences for the items in the changes list or not.</description>
> +<description>Whether to show differences for the items in the activity list or not.</description>
> </property>
> <property>
> <mandatory>0</mandatory>
> @@ -1388,7 +1388,7 @@
> <defaultValue>true</defaultValue>
> </property>
> <property>
> -<description>Whether to show changes rss links or not.</description>
> +<description>Whether to show activity rss links or not.</description>
> </property>
> <property>
> <mandatory>0</mandatory>
> @@ -1454,7 +1454,7 @@
> <defaultValue>30</defaultValue>
> </property>
> <property>
> -<description>Number of changes to show.</description>
> +<description>Number of activity to show.</description>
> </property>
> <property>
> <mandatory>0</mandatory>
> @@ -1520,7 +1520,7 @@
> <defaultValue></defaultValue>
> </property>
> <property>
> -<description>Comma separated list of tags to display changes for.</description>
> +<description>Comma separated list of tags to display activity for.</description>
> </property>
> <property>
> <mandatory>0</mandatory>
> @@ -1586,7 +1586,7 @@
> <defaultValue></defaultValue>
> </property>
> <property>
> -<description>Comma separated list of spaces to display the recent changes for.</description>
> +<description>Comma separated list of spaces to display the recent activity for.</description>
> </property>
> <property>
> <mandatory>0</mandatory>
> @@ -1663,7 +1663,7 @@
> </object>
> <content>{{velocity}}
> ##
> -## Recent changes.
> +## Recent Activity
> ##
> ## Optional parameters :
> ##
> @@ -1671,9 +1671,9 @@
> ## Note that HTTP parameters supercede velocity set variables.
> ##
> ## - rcShowRss (String set to "true" or "false"): show RSS at the bottom of the list.
> -## - rcSpace (List of string[s]): restrict recent changes retrieval to pages within the given space.
> -## - rcTag (List of string[s]): restrict recent changes retrieval to pages with the given tag.
> -## - rcAuthor (List of string[s]): restrict recent changes retrieval to pages with the given author.
> +## - rcSpace (List of string[s]): restrict recent activity retrieval to pages within the given space.
> +## - rcTag (List of string[s]): restrict recent activity retrieval to pages with the given tag.
> +## - rcAuthor (List of string[s]): restrict recent activity retrieval to pages with the given author.
> ## - rcChangesNb (String set to a numerical value): number of pages to display recent activity.
> ## - rcPagercPageEventsNo (String set to a numerical value): number of activity events displayed for each page.
> ##
> @@ -1705,7 +1705,7 @@
> #end
> #end
> ## pass the variables from the velocity context
> -{{recentchanges #if($rcShowRss) showRss="$rcShowRss" #end
> +{{recentactivity #if($rcShowRss) showRss="$rcShowRss" #end
> #if($rcChangesNb) changesNb="$rcChangesNb" #end
> #if($rcPagercPageEventsNb) changesNb="$rcPagercPageEventsNb" #end
> #if($rcSpaceString) space="$rcSpaceString" #end
Hi devs,
I've been working on http://jira.xwiki.org/jira/browse/XE-721 and it's
done on my local. This is the recent changes macro based on the current
implementation (not the activity stream one), but the idea is that we'll
rewrite it to display recent activity in the future. I will commit it
for the moment, in the 2.6 trunk, as is, but I would like to discuss
here the name of the macro and its parameters:
Macro name:
recentchanges, changes, activity, recentactivity
Parameters:
* rss link should be shown at the bottom of the changes table (boolean):
showRss, rss
* minor changes are shown or not (boolean, default false): showMinor, minor
* shows "see modifications" link next to entries (boolean, default
true): showDiff, showDifferences, diff, differences
* number of changes to show (number, 0 means "all", defaults to 30):
changesNb, changesCount, number, count, limit
* tags of documents to show chages for (comma separated list): tag, tags
* spaces of documents to show changes for (comma separated list): space,
spaces
* authors of documents to show changes for (comma separated list):
author, authors
Note that the types cannot be enforced since it's a wiki macro, I put
them there just for orientation.
I'd go for
activity rss minor diff count tags spaces authors .
WDYT?
Thanks,
Anca
Hi,
I'd like to include xwiki/2.1 in the list of available syntaxes by default for 2.6RC1.
Of course the default syntax remains xwiki/2.0.
The rationale is:
* Get people to know it exist and try it out as early as possible to provide feedback
Note that it's marked (experimental) in the syntax combo box list so it should be enough to let people know about its status.
Here's my +1
WDYT?
Thanks
-Vincent
Hello everyone,
As I said in my answer to Vincent's mail about our roadmap leading to
XWiki 3.0, I would like to include in this path some improvements to
the Ajax Suggest widget, as well as a new high level feature : the
"livesearch" (or whatever we will end up calling it) that provides
dynamically search results "as you type" in the search box - and that
uses those suggest widget improvements.
I've started a design document at
http://dev.xwiki.org/xwiki/bin/view/Design/SuggestImprovmentsAndDynamicSear…
It includes some more details about the livesearch thing, including a
breakdown plan with releases targets.
Here is how I see it :
* Redesign of the Ajax Suggest widget : 2.6 RC 2 (Note : this will be
mostly a visual re-design for a start, I'm not planning on rewriting
the widget from scratch - though some refactoring will be needed).
* Capability for the suggest to display multiple groups of typed items
(with icon and description) 2.6 RC 2
* Dynamic search (the "live search") : in the 2.7 cycle. I think it is
too early to break this feature down in the releases of the 2.7 cycle.
My +1 to have this new feature in 3.0, and to start the suggest widget
improvements in 2.6.
WDYT ?
Note, I have started working with Caty on a suggest widget redesign
proposal, I will send a mail about it very soon.
Cheers,
Jerome.