xwiki-devs September 2015

xwiki-devs@xwiki.org

19 participants
51 discussions

[xwiki-devs] Export page with history as XAR which includes histories

by Ghosh, Amrita

Hi, I am trying to export page with its histories as XAR. I referred to this document: http://platform.xwiki.org/xwiki/bin/view/Features/Exports and used the following URL: https://SERVER/xwiki/bin/export/Space/Page?format=xar&pages=Main.testpage&h… , where SERVER is my server name and testpage is the page with history that I am tryin to export as XAR. This command did not work. I am seeing message "A problem occurred while trying to process your request. Please contact the webmaster if this happens again." on the page and status 304 (Not Modified) on the browser. Can someone please let me know how I can export a page with histories as XAR which includes all its history information? Thanks, Amrita

9 years, 2 months

[xwiki-devs] [VOTE] Retire XMLRPC

by vincent＠massol.net

Hi devs, I’d like that we retire the XMLRPC feature of XWiki. Rationale: * We now have a REST API * The XMLRPC API is pretty old now, doesn’t support Nested Spaces, see http://jira.xwiki.org/browse/XWIKI-1249 The idea would be to: * Step 1: Relocate the code in an optional module (in addition to or inside one of the existing xmlrpc modules). This means handling some code currently in oldcore + update web.xml * Step 2: Move the optional xmlrpc modules to the github contrib organization * Step 3: Update documentation on xwiki.org and add an entry on e.x.o (move doc from http://platform.xwiki.org/xwiki/bin/view/Features/XMLRPC in it). Note that this will mean that XOffice will require users to install XMLRPC first if they want to try using it. Not a problem IMO. It’s also possible that the same will apply to XEclipse (or not) as I don’t remember if we had moved the code to use REST or not. WDYT? Here’s my +1 Thanks -Vincent PS: FTR, first time this was discussed on the list: http://markmail.org/message/gnockgbhnbfroa75

9 years, 2 months

[xwiki-devs] [Proposal] Deprecate SpaceDocs Panel

by vincent＠massol.net

Hi devs, Right now the SpaceDocs Panel displays: https://www.evernote.com/l/AHfuNTzznTdGJrbaZQ3txJH0Lru06IzUbDM My proposal is to: * Deprecate this Panel and move it to an Extension on e.x.o (and possibly also in the git contrib organization) * Introduce a new ChildrenPanel replacement * Change the panel title to be "Children Pages" * Have the Panel display a tree using the documentTree macro, showing only the children pages under the current page Basically this would be a variation of the more general Navigation Panel. Example of how it would look like: https://www.evernote.com/l/AHcplN3IcxxIBKzSVOMF42MOpOlZGc0OfuQ WDYT? Thanks -Vincent

9 years, 3 months

[xwiki-devs] FW: Display link on xwiki page

by PATEL, ABDULKADAR

Vincent, once again thanks for your reply. If I add link using JS code, then that link will be lost once the page is refreshed. Thus I need to do something on server side. That's why I knowledge xwiki rendering comes into picture. Here I see two ways of achieving this : 1. Using annotations 2. Using comments Basically the question is : How can I update a page with comment/annotation from js code? Thanks & Regards, Abdulkadar Patel -----Original Message----- From: Vincent Massol [mailto:vmassol@gmail.com] On Behalf Of vincent(a)massol.net Sent: Monday, September 21, 2015 1:51 PM To: XWiki Users Cc: PATEL, ABDULKADAR Subject: RE: [xwiki-devs] Display link on xwiki page On 21 Sep 2015 at 10:16:00, PATEL, ABDULKADAR (abdulkadar.patel@capgemini.com(mailto:abdulkadar.patel@capgemini.com)) wrote: > > Hi Vincent, > > > > > > Thanks for your response. > > > I know it might be very trivial issue but as I am working on xwiki > first time, > > > I don’t know basic things and that’s why bugging all of you with my silly doubts. > > > > > > To achieve this use case, I have followed below steps : > > > > > > 1. Modified xwiki-min.js file to bind a javascript code which will > display a popup dialog on click of ctrl+shift+N You shouldn’t do that. You should use a Javascript Extension instead, see http://platform.xwiki.org/xwiki/bin/view/DevGuide/SkinExtensionsTutorial > 2. This dialog fetches projects and issue types from jira server and > displays as dropdown ok > 3. Once user clicks on submit, a jira issue is created ok > 4. Now I need to display a link near text selected by user in step 1 but don’t know how to do it. This is not really related to XWiki (unless you wish to reuse the Annotation code but then I don’t now this code enough to know if you can do this or not). In any case you could check the Annotation code to understand how it’s done there, basically how to find the location of some text in the content. I guess there are at least 2 ways: * Do that using JS and thus insert your link using JS * Do it on the server side using the Rendering engine (this is what Annotation is doing I think) and add some specific HTML marker so that by using JS you can easily insert the link. In any case what you wish to do is something complex and requires good knowledge of JS (and possibly of XWiki’s Rendering if you choose this solution). Thanks -Vincent > I have attached code I have added in xwiki-min.js > > > > > > You can also suggest if this is a right approach and if I can follow some other approach. > > > > > > Thanks & Regards, > > > Abdulkadar Patel > > > > > > > > > > P.S. I have not kept xwiki developers mail list since this mail becomes huge and will need approval from list moderator. > > > > > > > > > From: Vincent Massol [mailto:vmassol@gmail.com] On Behalf Of > vincent(a)massol.net > Sent: Monday, September 21, 2015 12:52 PM > To: XWiki Developers > Cc: PATEL, ABDULKADAR > Subject: Re: [xwiki-devs] Display link on xwiki page > > > > > > > > Hi there, > > > > > > > > > On 18 Sep 2015 at 15:25:44, PATEL, ABDULKADAR (abdulkadar.patel@capgemini.com(mailto:abdulkadar.patel@capgemini.com))(mailto:abdulkadar.patel@capgemini.com(mailto:abdulkadar.patel@capgemini.com))) wrote: > > > Hi all, > > > > Sorry to bug all of you again and again with the same requirement. > > But I am also helpless till I get it done. > > > > I have ebelow use case : > > > > 1. User selects some text on an xwiki page and hits some keyboard > > shortcut say Alt+ctrl+N > > > > 2. This opens a popup dialog like shown below : > > > > [file:///Users/vmassol/Library/Containers/it.bloop.airmail.beta11/Da > > ta/Library/Application > > Support/Airmail/General/Local/1442819908355112192/Attachments/image0 > > 04.jpg@01D0F242.DD794520(mailto:Support/Airmail/General/Local/144281 > > 9908355112192/Attachments/image004.jpg(a)01D0F242.DD794520)] > > > > > > > > 3. As you can see in the screenshot, it displays list of projects, issue types from JIRA server. > > > > Issue summary field is pre-populated with the selected text from xwiki page. > > > > 4. Once user submits this dialog, an issue is created in JIRA and a > > link will be created on xwiki page besides selected > > > > text. > > > > So far I have achieved 1,2 and 3 but not able to achieve 4 One > > option I thought of is to create an annotation for the selected text > > with text as a link to JIRA issue But I don't understand how to achive this from javascript code. > > I have written javascript code in > > webapps/xwiki/resources/js/xwiki/xwiki-min.js file > > > > Please suggest me an approach to achive point no 4. > > Also suggest me if there is a better and cleaner approach. > > > > > > > I’m not sure I understand the problem. Step 4 seems easy. You just need a form action which calls a wiki page (possibly the current page passing some parameter) and then using Velocity for example to create the JIRA issue using the JIRA REST API. > > > > > > > > Thanks > > > > -Vincent > > > > > > Thanks & Regards, > > ____________________________________________________________________ > > [file:///Users/vmassol/Library/Containers/it.bloop.airmail.beta11/Da > > ta/Library/Application > > Support/Airmail/General/Local/1442819908355112192/Attachments/image0 > > 01.gif@01D0F241.1B349010]Abdulkadar(mailto:Support/Airmail/General/L > > ocal/1442819908355112192/Attachments/image001.gif(a)01D0F241.1B349010% > > 5dAbdulkadar) Patel Consultant | GESBU > > > > > > > > This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

9 years, 3 months

[xwiki-devs] Future of Flamingo, Bootstrap and Less in XWiki

by Guillaume "Louis-Marie" Delhumeau

Hello everyone. The front-end world is evolving really fast, and it's very hard to pick the good JavaScript framework, the good CSS preprocessor, or the good CSS toolkit. It's so unpredictable that it has inspired a comic strip: http://www.commitstrip.com/en/2015/09/16/how-to-choose-the-right-javascript… :) Last year, we have chosen to use Bootstrap for our new Flamingo Skin. Quickly, I have discovered that we had to integrate a CSS preprocessor to be able to customize it [1]. The natural choice was Less, since Bootstrap and of lot themes of the web were using it. Now, the situation have changed. Bootstrap 4.0 will be released soon [2]. It have been entirely rewritten and some retro-incompatibilities have been made. But the most breaking change is that they don't use Less anymore, but Sass. By the past, they use a less-to-sass converter so they were able to propose both versions of the framework. But now, I doubt the opposite converter could be possible since Sass have more features than Less. Worse, it seems that Sass is becoming more popular than Less [3]. Note: the current Bootstrap version, 3.x, will be maintained during one year, so we have this time to adapt. If we want to upgrade to Bootstrap 4, we will need to integrate the Sass preprocessor. Fortunately, we can re-use a lot of the work that I've done for Less (the cache mechanism, etc...) that I can modify to be more generic. I don't have estimated the time it would take yet. If we want to upgrade Flamingo to Bootstrap 4, it will create some css breakage (and the ability to use LESS in SSX will be loose). And we will have to convert our Less code to Sass. We could also decide to keep Bootstrap 3.x in Flamingo and use Bootstrap 4 for our next skin. Thanks, [1]: http://design.xwiki.org/xwiki/bin/view/Proposal/ColorThemeforFlamingo#HImpl… [2]: Bootstrap 4 announcement: http://blog.getbootstrap.com/2015/08/19/bootstrap-4-alpha/ [3]: The State of Front-End Tooling – 2015: http://ashleynolan.co.uk/blog/frontend-tooling-survey-2015-results -- Guillaume Delhumeau (gdelhumeau(a)xwiki.com) Research & Development Engineer at XWiki SAS Committer on the XWiki.org project

9 years, 3 months

[xwiki-devs] Display link on xwiki page

by PATEL, ABDULKADAR

Hi all, Sorry to bug all of you again and again with the same requirement. But I am also helpless till I get it done. I have ebelow use case : 1. User selects some text on an xwiki page and hits some keyboard shortcut say Alt+ctrl+N 2. This opens a popup dialog like shown below : [cid:image004.jpg@01D0F242.DD794520] 3. As you can see in the screenshot, it displays list of projects, issue types from JIRA server. Issue summary field is pre-populated with the selected text from xwiki page. 4. Once user submits this dialog, an issue is created in JIRA and a link will be created on xwiki page besides selected text. So far I have achieved 1,2 and 3 but not able to achieve 4 One option I thought of is to create an annotation for the selected text with text as a link to JIRA issue But I don't understand how to achive this from javascript code. I have written javascript code in webapps/xwiki/resources/js/xwiki/xwiki-min.js file Please suggest me an approach to achive point no 4. Also suggest me if there is a better and cleaner approach. Thanks & Regards, ____________________________________________________________________ [cid:image001.gif@01D0F241.1B349010]Abdulkadar Patel Consultant | GESBU Capgemini India | Pune Tel.: +91 20 6631 1755 - Extn: 20 12530 Mob.: + 91 8087683419 Email: abdulkadar.patel(a)capgemini.com<mailto:abdulkadar.patel@capgemini.com> www.capgemini.com<http://www.capgemini.com/> People matter, results count. _______________________________________________________________________ 7 Switch off as you go |q Recycle always | P Print only if absolutely necessary This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message.

9 years, 3 months

[xwiki-devs] Special behavior of the "Main" space in XE 7.2?

by Guillaume Lerouge

Hi Devs, I started trying out XE 7.2 (SNAPSHOT from around 12:30 today) and I was very impressed, the changes look quite good! While playing with it, I had a question about how the "Main" space is handled. Here's what I did: from .../xwiki/bin/view/Main/, I clicked the "create" button and created a sub page, then a sub-sub page. Here's what I got: - .../xwiki/bin/view/SubPage/SubSubPage Although I was expecting this: - .../xwiki/bin/view/Main/SubPage/SubSubPage So I was wondering whether this was the expected behavior, and whether it had been discussed before? Congrats & Thanks, Guillaume

9 years, 3 months

[xwiki-devs] [Brainstorming] "Child/sibling/descendant page" vs "subpage"

by Eduard Moraru

With the introduction of Nested Spaces / Nested Documents, we find ourselves having to expand our terminology to accommodate the tree-like structure of spaces/documents that we are managing. IMO, we have started going in the wrong direction with using standard tree terminology directly in XWiki's UI, introducing new terms that simple users could be easily confused by or overwhelmed (this adding to the already existing ones). The specific issue I have in mind is how do we refer child entities for each concept (wiki, space, page) and how does this scale when the hierarchy increases. What I propose is that we Keep It SSimple (*™*) :) and just use the "sub" prefix for the concept at hand. Examples: * wiki -> subwiki (here we can continue using "wiki", as discussed previously [1], since we don`t actually support nested wikis yet, but if "subwiki" is used in a conversation it still makes perfect sense) * space -> subspace [2] * page -> subpage [3] The problem with the term "child", as pointed out by Marius in an offline chat, has indeed the issue that it can only be applied correctly for first level descendants, after which it becomes inaccurate, since starting with the second level the term "descendant" is more appropriate. All of this becomes unnecessarily complicated and, IMO, we should avoid dealing with it by using the "sub" prefix which is much easier to grasp and accept. On a similar note, I also find the term "nested" to be a bit unnecessarily complicated, specially for non-technical and non-english native users. WDYT? Thanks, Eduard ---------- [1] http://markmail.org/message/cehvpds5qmljq5f7 [2] https://en.wikipedia.org/wiki/Subspace [3] https://en.wikipedia.org/wiki/Subpage

9 years, 3 months

[xwiki-devs] [Proposal] Postpone (again) the 7.2 final release date to the 24th of Sep 2015

by vincent＠massol.net

Hi devs, The 7.2RC1 version is being released today (released started yesterday), and the 7.2 final is planned for next Monday (the 21st). Note that we have already pushed the 7.2 release date by one week (was planned for the 14th originally). However, I believe we won’t have enough time to provide a good quality release if we release in 3 days time so I’m proposing that we push the release to the 24th, ie giving us one week to fix last minute important bugs and last minute important polishings. In case a very important bug would occur we would still have time to push again the release by a few days without going beyond end of September (we need to leave time for 7.3 - 1.5 months - and 7.4 - 1.5 months too). WDYT? Thanks -Vincent

9 years, 3 months

[xwiki-devs] [ANN] XWiki 7.2 Release Candidate 1 released

by Eduard Moraru

The XWiki development team is proud to announce the availability of XWiki 7.2 Release Candidate 1. This release candidate brings many Flamingo skin improvements to better present Nested Documents on top of the Nested Spaces concept. Similar improvements were made in applications like Solr Search, AWM, FAQ, Activity Stream and the Skin editor in order to be compatible with Nested Spaces. On the developers side, a new Select widget and a document picker were added to allow richer UIs to be created. Last but not least, 41 bugs were fixed in this release on the road towards the coming final 7.2 release. You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download Make sure to review the release notes: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki72RC1 The following people have contributed code to this release: Denis Gervalle Ecaterina Moraru (Valica) Eduard Moraru Gabriela Smeria Guillaume Delhumeau Marius Dumitru Florea Sergiu Dumitriu Thomas Mortagne Vincent Massol Thanks for your support -The XWiki dev team

9 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 September 2015