xwiki-devs July 2011

xwiki-devs@xwiki.org

26 participants
50 discussions

[xwiki-devs] Copy page through Restful API

by xManish

Hi, In XWiki, we could copy a page from one space to another space. Is there any thoughts about making a copy of page through RestApi. While copying a page, all of the objects within that page should be copied over too. The only way I can see it can be done now is by getting all objects of that page, iterate through them and create them one by one. Is there a better solution to this? Thanks in advance Regards, Manish -- View this message in context: http://xwiki.475771.n2.nabble.com/Copy-page-through-Restful-API-tp6575262p6… Sent from the XWiki- Dev mailing list archive at Nabble.com.

13 years, 2 months

Re: [xwiki-devs] [xwiki-users] [Demo] Wiki3.0 project preview

by Eduard Moraru

Hi Marius, On Wed, Jul 20, 2011 at 8:49 AM, Marius Dumitru Florea < mariusdumitru.florea(a)xwiki.com> wrote: > Hi Eduard, > > On 07/19/2011 11:29 PM, Eduard Moraru wrote: > > Hi community, > > > > If anyone is curious, a demo installation of the current work on the > Wiki3.0 > > [1] research project is available at http://wiki30-demo.xwiki.com > > > > With the Workspaces feature, you can register a user and create > workspaces, > > invite/accept other users and generally manage your workspace. > > > > Interesting sections (or rather a list of features) are: > > > > = In the main wiki = > > > > - Create new Workspace (Add menu or homepage button) > > - Workspace Directory (Top menu, under 'Workspace') > > - 'Workspaces' section in user profile > > - User Directory improvements > > - Join/Leave/Request membership/Accept invitation to join a workspace > > (Workspace Directory or homepage of a workspace) > > - Workspace search suggestions (top-right search box) > > > > = In a workspace = > > > > - Dashboard > > - Workspace information panel (right panels) > > - Main wiki link (Top menu, under 'Workspace') > > - Delete workspace (Top menu, under Workspace, for owner) > > - Workspace Configuration section (Administration, 'Configuration' > category) > > - Workspace Users section; Accept membership requests or invite users > > (Administration, 'Users& Groups' category) > > - User registration redirecting to main wiki (Top-Right register link) > > - Removed local XWiki.Admin user > > > > > > Besides the Workspaces feature, the Real-Time editor is also available > for a > > quick test. You can access it by editing a page in "Real Time" edit mode. > > You can't miss it :) > > The real time editor is quite nice. I haven't tested it before. We > should definitely integrate the line number feature in the wiki edit mode. > > > For quick tests, you can edit the same page in 2 browser windows and see > > changes in one window triggering an update in the second one. It also > works > > with multiple users (obviously) and allows other to join in the editing > > session. > > > > For now it's working real time only for wiki code. Work on the WYSIWYG > > version has already started. > > > > > > Please feel free to report any bugs or suggestions here or (preferably) > at > > http://jira.xwiki.org/jira/browse/WIKITHREEDOTO and do be aware that > it's > > still work in progress. > > The list of users in the Workspace information panel is not right for a > newly created workspace. My user is listed twice and the first avatar in > the list points to the workspace home page. > Fixed. > Also, the Top Active Members section lists 3 users: > > Administrator -> global user (should be hidden IMO) > Admin -> local user, missing (again, should be hidden IMO) > Fixed. my user, but the link points to the corresponding local user which is > obviously missing > AFAIK, this is a bug http://jira.xwiki.org/jira/browse/XWIKI-6103 that has been fixed for XWiki 3.1. The problem is at wiki creation time, because I change the context database and the context user does not change accordingly, making Activity Stream to register the unchanged user, thus, resulting in a local user instead of global. When I will upgrate to 3.1, I hope that this will be fixed too. In practice, the 'ghost' user will disappear as fast as at least 5 users start editing pages :) > > Looks great otherwise. Well done! > Thanks :) and thanks for the feedback as well, Eduard > > Thanks, > Marius > > > > > Thanks, > > Eduard > > > > ----------------- > > References: > > [1] https://wiki30.xwikisas.com/ > > _______________________________________________ > > users mailing list > > users(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/users > _______________________________________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/users >

13 years, 2 months

[xwiki-devs] [PROPOSAL] Introduce begin/end events standard

by Thomas Mortagne

Hi devs, I would like to introduced a standardized (at observation API level) way to indicate that en event represent the beginning or the end of something. The idea is them to use it in things like activity stream to group events/whatever or in my case maintain a stack of states in the Execution context about the current action updated by listening to events. My immediate use case is to filter some modification in automatic watch feature (imported xar, crated wikis, etc.) but I feel that we need that information for a larger audience. In details my proposal is to introduce BeginEvent and EndEvent interface (feel free to suggest better names if you have some in mind). Then pushing the BeginEvent instance in the context in a stack of current events poped when receiving a EndEvent. Note that I don't not plan to put an id in Begin/EndEvent since it should not be needed if they are properly generated (some job can't finish if all it's sub jobs are not finished). WDYT ? -- Thomas Mortagne

13 years, 2 months

[xwiki-devs] XWiki Android Client

by Chamika Weerasinghe

Hi all, Thank you all for giving me help to develop xwiki-android-client and passing me in GSOC mid evaluation. Since I've finished most of the xwiki android navigation features now I'm working on adding other features which uses XWiki RESTful POST and PUT methods. There is really big problem here. Because until now I used json objects to communicate with XWiki REST. But REST doesn't support accepting json objects. Please correct me if I'm wrong. If REST doesn't accept "application/json", I have to modify almost all the classes in xwiki-android-rest to be worked with xml. Another drawback is still REST doesn't provide "links" of the elements in json but xml provides it. Fabio described it here ( http://blog.fabiomancinelli.org/2011/03/07/XWikis_RESTful_API.html) I selected json because it can be deserialized using gson which is the smallest json deserializing library specially designed for Android. But now I feel that moving from json to xml is the best option. A light weight xml serialization library named simple-xml ( http://simple.sourceforge.net/) would be a feasible library for Android. Should I proceed with xml using simple-xml or can you suggest me a better option which saves my time from modifying classes? Thank you, Best Regards, Chamika Weerasinghe

13 years, 3 months

[xwiki-devs] about documentation of adding a tag to a page via REST API

by Jun Han

Dear all, I am trying to add a tag/tags to a page. However, it seems to me that there is an inconsistency between XWiki REST API document and its implementation. http://platform.xwiki.org/xwiki/bin/view/Features/XWikiRESTfulAPI#HTagresou… The document indicates that PUT method can take <tag> element and will add a tag. However, the implementation only takes <tags> element (via xml/application) and PUT method replaces all the existing tags with the new tags included in the <tags> element. Is there a REST call that only adds a tag to the page without replacing all the existing ones? Best regards Jun Han

13 years, 3 months

[xwiki-devs] The plan of GSoC project "Auto-completion in content editors" (7.18 - 7.24)

by 许凌志(Jamesxu)

Hi, Last week I have done following things: 1. Fix most of the bugs Marius had found last week, there are still three left for further discussion with mentors 2. Refine the codes according to the last review by Marius 3. Read the documentation of writing REST service, and design the rest service for link auto-suggestions, I should talk with mentors about the implementation details. In this week, I am going to do the following things: 1. Implement Rest service for link suggestion 2. Implement the whole context for link suggestion, include "attach:", "@", "." and "||". 3. Consider to implement the ctrl+space to re-open the suggestion box according to the different contexts of link suggestion. -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

13 years, 3 months

[xwiki-devs] The plan of GSoC project "Auto-completion in content editors" (7.4 - 7.11)

by 许凌志(Jamesxu)

Hi, thanks for Marius' help ,last week, I have done the following work: (1). Implemented the function that logs a message in the firebug console whenever the caret is after [[ (2). Implement the function that requests the list of wiki pages matching some prefix user input. BUT, don't actually query the database, instead simply return a dummy list from the wiki page. (3). Implement the function that displays the list of wiki pages where the caret is, and integrated it with the SuggestionBox I have already implemented. Here is the plan for next week: I will focus on fixing bugs and improving what I have and to make suer by the end of the week the link suggest should work very good. Include (1). Display the suggestion box in right place and at the right time. (2). Close suggestion box in custom, and also when some other keys typed like "esc" "right" and "left" (3). Test to make sure the prototype for link suggestion runs very well. -- Best wishes, 许凌志(Jame Xu) MOE KLINNS Lab and SKLMS Lab, Xi'an Jiaotong University Department of Computer Science and Technology, Xi’an Jiaotong University

13 years, 3 months

[xwiki-devs] a successful integration of XWiki with Sakai

by Adam Hocek

Hello XWiki Developers, I wanted to let you know that we completed our first release of integration of XWiki with Sakai (sakaiproject.org). Sakai is an open source collaborative teaching and learning application used by many educational institutes worldwide. The integration replaces an older less supported wiki tool in Sakai. We presented the new tool at the recent Sakai 2011 conference in Los Angeles, CA, and are anticipating several schools to begin using the tool. I think this will be bring about greater exposure and have a positive impact for the respective open source communities. If anyone has any questions I'd be happy to try and answer them. We will probably be emailing to this list sometime soon with some specific questions and requests. Cheers, - Adam Adam Hocek Information Technology Marist College tel: 845-575-3948

13 years, 3 months

[xwiki-devs] Are there XWiki UI tests?

by Adam Hocek

Hello, Since we have integrated XWiki with Sakai and we are helping to develop test plans for the integration tool. I wanted ask if there are any UI tests available for XWiki? This would be helpful to our goal. Thank you, - Adam Adam Hocek Information Technology Marist College tel: 845-575-3948

13 years, 3 months

[xwiki-devs] [Proposal] XE 3.2 Roadmap

by Vincent Massol

Hi devs, Since we're getting close to XE 3.1 final release it's time for defining the roadmap for 3.2. After discussing offline with several XWiki devs (the ones from XWiki SAS) here's a list of items for 3.2 that we came up with. • Features • UI for extension manager + backend extension manager (continued, especially nice XAR upgrades) • Search improvements and especially scoring, French support and wildcard issues (continued from 3.1) • App Within Minutes • Jiras Priority 1 • XWIKI-6504 Convert Panels application into syntax 2.0 • XWIKI-6676 UI does not report failed delete actions of attachments; XWIKI-6623 Attachment upload failure gives no feedback to user • ORACLE fixes • Fixes for HTTPS support • XWIKI-6687 Be able to delete a space from the UI • Jiras Priority 2 • Stats module improvements (Commit code from client projects without changes) • LDAP Admin UI (commit Jerome work without changes) • Clustering bug • XWIKI-6684 Use a predefined Space Template like Dashboard, Livetable when creating a new space • XWIKI-6073 Change stylesheet and javascript extension filename when a modification is done on those • Investigations • Solr • Browser support (IE6, IE7, Safari) • XWiki in 5min • XEM/Workspace features This is of course a minimal list that we're proposing to implement. More could be implemented but we're proposing to guarantee the implementation of the items above. Now we need to put names against each of these items. Can you please volunteer and put your name next to issues you'd like to implement? Thanks -Vincent

13 years, 3 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs July 2011