xwiki-devs June 2011

xwiki-devs@xwiki.org

36 participants
61 discussions

[xwiki-devs] [Discussion] Defining Sheets

by Marius Dumitru Florea

Hi devs, A prerequisite for Application Within Minutes [1] is to be able to specify the sheet that will be used to display a document without touching the content of that document [2]. This can be done in multiple ways, depending on how we define the notion of a sheet. (1) Class sheets vs. document sheets A class sheet displays an object of a particular type and is specified in the definition of that type. This means that when you create or edit a class, i.e. a type of object, you can specify which sheet should be used to display the instances of that class. Pro: Documents don't have to specify a sheet. Con: We have to determine which sheet to use in case there are multiple objects attached to a document. A document sheet displays a document of a particular type and is specified at document level because the document type, unlike the xclass, does not exist actually. The document type is inferred from the type of objects the document has, or from its content, or, why not, from the type of attachments it has. Pro: Doesn't have the class sheet con. Con: Each document has to specify which sheet to use. Class sheets are enough for Application Within Minutes because the wizard will create a single class (with a sheet) and so the application items will have only one object that specifies a sheet. (2) Separate sheets per action? The current practice is to define a single (class) sheet which either checks for the current action in its code or uses doc.display method whose output is action specific. How often did you had the need to write separate sheets per action (e.g. create, view, edit, search, changes)? (3) Which actions require a sheet? If we're talking about class sheets then the list of actions that target an object and which require a sheet is limited. Currently we have "view" and "edit", but Ludovic proposed also "create", "search" and "changes". If we're talking about document sheets then we can have custom actions and so we need an extensible mechanism to map actions to sheets. (4) Sheet parameters? If we're talking about class sheets then they only need to specify how an object is displayed. Document sheets on the other hand may need to control elements like: * which tabs (comments, annotations, attachments, etc.), if any, are displayed * show title field in edit mode * the side panels * the form buttons WDYT? Thanks, Marius [1] http://dev.xwiki.org/xwiki/bin/view/Design/ApplicationWithinMinutes [2] http://dev.xwiki.org/xwiki/bin/view/Design/ApplicationWithinMinutesCoreChan…

13 years, 1 month

[xwiki-devs] [xeclipse] questions about LocalDataStorage and display of Page resources

by Jun Han

Dear All, I have some questions about the LocalDataStorage implementation and Page resources display. 1. The current LocalDataStorage implementation uses xmlrpc model and the cache structure looks like the following: index |-space |-page As the xmlrpc model is being replaced by org.xwiki.eclipse.model package, do we need to modify the local storage as well, e.g., adding a folder to store various wikis? I am not very clear about how local storage works. My rough understanding is like this: (1) When user accesses a page, local cache stores it. (2) Whenever user makes a change in the editor, store it in the local cache (3) when user performs a submission, synchronize the content 2. I have asked how to display page information before, the suggestion from Eduard is the following: ------ WebHome (PageSummary) -------- Attachments ---------- dog.png ---------- spreadsheet.xls -------- XWiki.XWikiComments ---------- 0 : Administrator ('author' property value) ---------- 1 : Guest ---------- 2 : Administrator -------- XWiki.MyClass ---------- 0 : etc. ---------- 1 : etc. However, I am not sure what else needs to be included? e.g, annotations, versions, history, translations? Once confirmed, I will start working on the page content. Best regards Jun Han

13 years, 1 month

[xwiki-devs] hibernate cache optimization?

by Paul Libbrecht

Hello XWiki-devs, maybe this forum is better than curriki-dev. In short: how can I boost the size of the cache of objects held by hibernate? thanks in advance paul > as you know curriki.org is somewhat of a fat server serving really many requests. > > One symptom we are seeing on the production machine only, almost, is: > xwiki.getPlugin("curriki").fetchUserGroups(). > that sometimes takes more than 1 minute and sometimes much less, all for the same user. > On the development machine it takes time with users with a lot of groups only when the hibernate cache is flushed. > > My interpretation is that this method is fetching the group and probably a lot more. My answer would be to go low-level. > > But another answer would be to ensure that the hibernate cache is big enough so that all these stay in memory. Making this possible would also speed up a huge amount of other things. > > Are we talking of the file ehcache.xml's attribute: > maxElementsInMemory="10000" > ? > I sure could raise this by a factor 10 if true. > > thanks in advance > > paul

13 years, 1 month

[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, 1 month

[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, 1 month

[xwiki-devs] [Proposal][UX] Improvements for the Add menu

by Ecaterina Moraru (Valica)

Hi, This is a proposal regarding the improvement of the Add menu in order to: - specify a template for the newly created entities (space/page); - specify also applications templates; - some improvements for the create page step: the ability to select an existing space or create a non-existing one + position changes. You can see the proposal at http://incubator.myxwiki.org/xwiki/bin/view/Improvements/CreateMenuProposal The "Add" menu could contain just the entries: - Page - Space - Application. In the usability interviews I had, no one used the other shortcuts ('Comment to page; Attachment to page'), but the interviewers were not beginners users, so if someone from the community is using those shortcuts please tell us if you want to keep them. The Create Space step relates to http://jira.xwiki.org/jira/browse/XWIKI-6684 The Create Page step relates to http://jira.xwiki.org/jira/browse/XE-897 For the application homepage http://incubator.myxwiki.org/xwiki/bin/download/Improvements/ApplicationWit… the create action will auto-generate the page name (according to the options) and will preserve the current space [1]. With this proposal we can benefit from the contextual actions (for applicationWithinMinutes inside the designated space) but we are not dependent completely of the space, being able to create application instances in an universal manner from the "Add" menu. Also, the existing behavior for the wiki pages will be preserved. The default option for the template + location will modify accordingly to the context where the "Add" menu was launched. Please provide feedback. Thanks, Caty [1] http://xwiki.markmail.org/thread/mac6a24us4ucmp3j

13 years, 2 months

[xwiki-devs] Second Commit for the plan of this week .GSoC-"Auto-completion in content editors"

by 许凌志(Jamesxu)

Hi, I have submit my second commit of the project, it contains four small commits: 1. Make patch for the suggestions given by review comments of Marius for my last commit. 2. Add some wiki editor(textarea) related utility functions for WikiEditor object, it is useful when intergate the suggestion box to the editor. 3. Codes for the second and third part of my plan this week: (a). 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 server. (b). Implement the function that displays the list of wiki pages where the caret is. But I use the suggestion box I have already implemented before this week, instead of writing a plain HTML list inside a DIV. 4. Make a patch for modifying the suggestion json format for link suggestion box Here I want to explain how I Implement the function that displays the list of wiki pages where the caret is. When the suggestor started, I add a mask which duplicate the same content with the same size, position and also same style of the textarea. When user types triggers, for example, type "[[" for link suggestion, the mask will be updated for two things: (1). update the content to syncronized with the values in textarea. And also surround the trigger with a "span" mark, for example, for "[[", it will be surrounded by <span id="suggestion_mark">[[</span>. It is useful for recorde the trigger and get its offset position which is the right place to show the suggestion box. (2). update the position of the mask include the scrollTop of the mask to syncronizied with the textarea. I use the LinkSuggestionBox which I have implemented last week to show the suggestion results, it can be shown in the right place now. But the navigation of the result item by up and down key does not work now, I have found the problem and I will refine it in next commits. -- 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, 2 months

[xwiki-devs] How to write xwiki servlet

by 许凌志(Jamesxu)

Hi, I want to write some server side codes for ajax response, anyone can tell me how to do it, is there any documents for that? Thank you very much -- 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, 2 months

[xwiki-devs] Status: GSOC Xwiki Android Client

by Chamika Weerasinghe

Hi, I modified navigator in xwiki-android-components so that it will communicate to XWiki instance via xwiki-android-rest. But it cannot be tested due to following problems. 1. After building xwiki-android-rest library it doesn't have GSON library. Therefore REST isn't working since GSON classes are not found withing the library. I searched a method to include gson (or any other) jar file to add to my custom library. It is said that if we use scope of the dependency of the maven configuration as "compile" it will include jar files in our build. But it doesn't work for me. 2. Since xwiki-android-component use xwiki-android-rest, I want to import rest library to the component. I've done this in eclipse. But cannot figure it out how should I do this in maven. Due to above issues current repository give build errors. I planned to develop object/class editor component in next few days since xwiki-navigator is almost finish. Eduard suggested, it should be an "open objects and classes (in a separate and configurable object/class editor widget) ". Can you describe about this widget further so that I can get a clear idea about it. Best Regards, Chamika Weerasinghe

13 years, 2 months

[xwiki-devs] Commit for the plan of this week .GSoC-"Auto-completion in content editors"

by 许凌志(Jamesxu)

In this commit, I Implemented the function that logs a message in the firebug console whenever the caret is after [[ (but just that, nothing more!). It contains two small commits, one if the codes for LinkSuggestor, and the other is the test codes for it. -- 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, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs June 2011