xwiki-devs March 2011

xwiki-devs@xwiki.org

53 participants
121 discussions

[xwiki-devs] XE 3.0M3 released on maven.xwiki.org

by Marius Dumitru Florea

Hi devs, XWiki Enterprise 3.0 milestone 3 has been released on maven.xwiki.org. It would be good if some of you can test it ( http://maven.xwiki.org/releases/org/xwiki/enterprise/xwiki-enterprise-jetty… ) before we publish it on the download page. Thanks, Marius

13 years, 9 months

[xwiki-devs] REST API usage

by Fabio Mancinelli

Hi everybody, I was wondering in which XWiki subsystems the REST API is used in a direct way. I know that it is used in different place but I don't have a clear vision. Could you please tell me where are you using it? Thanks, Fabio

13 years, 9 months

[xwiki-devs] Back to the future of XWiki !

by Ludovic Dubost

Hi all, As many of you may know, 7 years ago, I created the XWiki Open-Source software. A few years ago, especially when Vincent arrived, I took a step back from development of the XWiki product to focus on developping XWiki SAS which allows to support the XWiki development. I've particularly spent my time making sure that the deployments of XWiki our Customers have been doing are successfull. I've left the product development work to committers who under the lead of Vincent have done amazing work in the last few years. We have provided some product marketing in addition through Guillaume's and lately Gregory's work which allowed to bring some feedback from users and customers and also bring a different less technical perspective to the XWiki Product development. Cati also joined the team and allowed us to make huge steps forward in product usability and design. Now, as XWiki SAS's project implementation team is doing great work on it's own, I've decided to involve myself more in the future of XWiki's product. I'm now the new XWiki SAS 'Product Marketing' head which means I will involve myself in community discussions about the product features actively developped, investigated for future development as well as in general discussions about the XWiki Software's future. I will try to bring the knowledge that XWiki SAS's customer, project managers, support team bring us from using XWiki in production environments to the community so that we make better decisions, more focused on developments that will allow to increase XWiki's success with end users. At XWiki SAS we have already done a lot of work to organize this feedback so that we know more things that XWiki SAS's developers and the XWiki community should work on. In the next few weeks you will therefore see me work on the investigations of future features as well as work more closely with developers whenever they feel the need on the features they implement actively. I will also manage the different surveys we have done in the past to gather feedback from our community. These surveys have still been running on the xwiki.org web site although they are now quite outdated. I will propose to review them and launch them again. If users or developers have any feedback about XWiki, about what we should work on in priority, please do send that feedback on the list (preferably). Although we have a much bigger list of great ideas than what we currently can achieve, you can help us on helping us select the most important ones that will make a difference. I would like to use this occasion to thank our great community of developers and users who help the committers every day to make XWiki better. We could not do this without all the suggestions, ideas, patches that our community provides. Thanks Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

13 years, 9 months

[xwiki-devs] WYSIWYG editor macro support changes

by Marius Dumitru Florea

Hi guys, In order to fix http://jira.xwiki.org/jira/browse/XWIKI-5691 and a few related bugs I had to refactor the way macros are displayed inside the rich text area of the WYSIWYG content editor. Along with this I introduced a few improvements in the way the user interacts with macros. Here's a list of changes: * macros are displayed now 100% like in view mode * macros that have output are emphasized only when hovered or selected * you can navigate the macro output with the arrow keys * you can copy content from the macro output * press Enter to edit macro * press Space to toggle between collapsed and expanded state * Ctrl+Shift+R reloads the macros * Ctrl+Shift+E expands all/selected macros * Ctrl+Shift+C collapses all/selected macros * Ctrl+Shift+M to open the insert macro wizard Known issues that I'd like to fix for 3.0 final: * you can cut text from macro output * you can drag text into/from macro output * placing the caret before/after a macro is still tricky Please take a look and let me know what you think. Thanks, Marius

13 years, 9 months

Re: [xwiki-devs] [xwiki-notifications] r35297 - platform/xwiki-plugins/trunk/activitystream/src/main/java/com/xpn/xwiki/plugin/activitystream/eventstreambridge

by Vincent Massol

On Mar 8, 2011, at 6:23 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2011-03-08 06:23:16 +0100 (Tue, 08 Mar 2011) > New Revision: 35297 > > Modified: > platform/xwiki-plugins/trunk/activitystream/src/main/java/com/xpn/xwiki/plugin/activitystream/eventstreambridge/BridgeEventStream.java > Log: > XPAS-38: Implement the new API method to delete an Event from the EventStream > Done. > > Modified: platform/xwiki-plugins/trunk/activitystream/src/main/java/com/xpn/xwiki/plugin/activitystream/eventstreambridge/BridgeEventStream.java > =================================================================== > --- platform/xwiki-plugins/trunk/activitystream/src/main/java/com/xpn/xwiki/plugin/activitystream/eventstreambridge/BridgeEventStream.java 2011-03-08 05:21:21 UTC (rev 35296) > +++ platform/xwiki-plugins/trunk/activitystream/src/main/java/com/xpn/xwiki/plugin/activitystream/eventstreambridge/BridgeEventStream.java 2011-03-08 05:23:16 UTC (rev 35297) > @@ -103,6 +103,22 @@ > /** > * {@inheritDoc} > * > + * @see EventStream#deleteEvent(Event) > + */ > + public void deleteEvent(Event e) > + { > + try { > + XWikiContext context = getXWikiContext(); > + ActivityStreamPlugin plugin = getPlugin(context); > + plugin.getActivityStream().deleteActivityEvent(convertEventToActivity(e), context); > + } catch (ActivityStreamException ex) { > + // Unlikely; nothing we can do Well should log it at least as an error. Thanks -Vincent > + } > + } > + > + /** > + * {@inheritDoc} > + * > * @see EventStream#getRelatedEvents(Event) > */ > public EventGroup getRelatedEvents(Event e)

13 years, 9 months

[xwiki-devs] XWiki.WatchListMessage doesn't have a creator set

by Marius Dumitru Florea

Hi devs, OrphanedPageTest from xmlrpc-tests fails for XWiki.WatchListMessage page from the watchlist application because it doesn't have a creator set. Was the creator field left unset on purpose? See http://hudson.xwiki.org/view/Functional%20Tests/job/xwiki-product-enterpris… Thanks, Marius

13 years, 9 months

[xwiki-devs] [Proposal] Optional Contact Form in the download page

by Vincent Massol

Hi devs and everyone, Emilie has proposed the following content to be added to the Download page (http://www.xwiki.org/xwiki/bin/view/Main/Download): http://dev.xwiki.org/xwiki/bin/view/Drafts/TextDownload The idea is twofold: 1) to get feedback about what people think about our software. 2) some people who download the XWiki software from xwiki.org don't know that XWiki SAS has a commercial offerings and could be interested by it The pros for the community are: 1) XWiki SAS will publish back the result of the feedback it receives from the download form which will allow us to fine tune and improve the software 2) XWiki SAS could get more business (from people who want to buy support, dev work, hosting, etc) which will mean accrued budget for paying developers and resources to work on the XWiki project Note 1: the form would be of course optional Note 2: in the future I'd like to see a not for profit foundation to handle xwiki.org, the xwiki open source project, donations, etc. When this happens we could elect from member for the foundation and have the feedback form sent to that foundation for example, with members of the foundation having access to the data (for example). WDYT? Thanks -Vincent Massol, acting as both CTO of XWiki SAS and XWiki open source developer

13 years, 9 months

[xwiki-devs] [VOTE] Move web modue packages/groupid to org.xwiki instead of com.xpn

by Vincent Massol

Hi, Since we're starting the 3.0 cycle I think it's time to move the web modules to use the org.xwiki groupId and package names. It's not really normal for an open source project such as our to use the package of a company (and that of a company that doesn't exist anymore... xpertnet has been replaced by XWiki SAS a few years ago) and I don't think moving web modules to that package/groupid is going to cause any important problems to anyone. Here's my +1 Thanks -Vincent

13 years, 9 months

[xwiki-devs] XWiki.CopyDocument and copy.vm

by Marius Dumitru Florea

Hi devs, I just noticed that we have two forms for copying a document: Space/Page?xpage=copy and XWiki/CopyDocument?sourcedoc=Space.Page copy.vm has been recently updated to follow the vertical form layout standard and its code was also cleaned. XWiki.CopyDocument wasn't updated and I find its code a bit buggy. Maintaining both of them is wrong so I propose to remove XWiki.CopyDocument from the XE xar and update LiveTableResultsMacros to use xpage=copy for the copy link in the action column (I couldn't find any other usages). I'd like to do this asap. Thanks, Marius

13 years, 9 months

[xwiki-devs] [proposal] tracking status of major features in the current version in development

by Ludovic Dubost

Hi, I took the liberty to update a bit the roadmap page http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap to add links to the Design page or the JIRA page when they existed. I also added the Investigations with links in the page. I would like to propose that we increase a bit the visibility on the development of the features. What I would like to suggest is that: All major feature in development or investigations gets a "Design" page and these pages are linked from the Roadmap page. The Design page should include at least: - the use cases that are being implemented - a link to the JIRA issue if it exists. - a link to the UI design proposal. I would also like to suggest that the UI design proposal are moved from myxwiki.org to xwiki.org either on their own wiki or on the dev wiki. - a design document which explains the objetives and implementation strategy (this should be reviewed by the community through the mailing list) - and most importantly an action plan with priorities and status on each element of the action plan (it can list the use cases that are first being implemented or other actions necessary to implement) - the action plan should be updated after each Milestone release. - we should also update the Roadmap page when we know a feature is at risk of not making the final release. We already have a lot of that sometimes a bit disorganized. The objective and design is often in a mail thread. It would be better if the last status is on the Wiki. But more importantly what is more missing is the implementation strategy, the action plan with the priorities and the current status. In order to help out prioritizing development based on what we feel the users more need we need the splitting of priorities and the status. This is particularly important for large features that have a big impact and a lot of potential user interactions (extension manager, dashboards, workspaces) Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

13 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs March 2011