xwiki-devs June 2014

xwiki-devs@xwiki.org

26 participants
53 discussions

[xwiki-devs] [Proposal] Having the AppBar panel in the left side column by default.

by Guillaume "Louis-Marie" Delhumeau

Hi, In Flamingo, we have created the concept of Application Bar, that we have implemented as a Panel: http://jira.xwiki.org/browse/XWIKI-10254 I propose to put the Application Bar by default on the left column. Since we do not have a configuration system at the skin level, it would be present for both Colibri & Flamingo. I think it is not a problem because I have managed to make it look good for both (except for the size of the icons) : http://jira.xwiki.org/secure/attachment/27707/appbar.png WDYT? Thanks, Guillaume

10 years, 6 months

[xwiki-devs] [Brainstorm] Application Descriptor

by Ecaterina Moraru (Valica)

Hi, There have been some recently discussions about Application Descriptors and their utility when generating content for XWiki features, like taking the icon field from the descriptor in order to generate the application panel for the AppBar, etc. I've gathered some use cases / needs on this page: http://design.xwiki.org/xwiki/bin/view/Proposal/ApplicationDescriptor It would be nice to brainstorm a bit if we consider the 'Application Descriptor' concept to be needed in our future, especially since the Flamingo Skin is focused heavily on the Applications concept. I would be curious why this concept has been deprecated (Application Manager): * maybe the fields the descriptor contained are deprecated by the Extension Manager; * maybe a bad usage; * etc. And also very important is what fields you consider should be needed in the Application Descriptor and ways to make it easily extensible. Having an Application Descriptor would facilitate having an index containing all applications, called Application Index, in order to help the user navigate and manage the installed applications outside the Extension Manager (which is found in Administration). Thanks, Caty & Louis-Marie

10 years, 6 months

[xwiki-devs] Our first Extension! =)

by Danilo Amaral de Oliveira

Hello XWiki Dev, How are you? In my company, we have created an XWiki extension that allows use the sigmajs framework (sigmajs.org) and we would like to share the extension with the community. Our idea is create a github project and make it available through extension manager to the users however we don’t have idea how to create the github and after that link that with the extension, how can we do that? Thank you, Danilo Grupo Energisa Danilo Oliveira Analista Suporte Aplicacao TI - DPTO CORP. DE INFRAESTR. TI e-mail: danilo.oliveira(a)energisa.com.br | tel: (32) 3429-6342 | cel: (32) 8452-9478 Esta mensagem contém informação confidencial. Se você a recebeu por engano, não divulgue ou copie seu conteúdo. Por favor, avise ao remetente imediatamente e apague-a do computador. Privileged and confidential. If this message has been received by mistake, do not disclose or copy its contents. Please notify sender and delete immediately.

10 years, 6 months

[xwiki-devs] Override Preview behaviour in WYSIWYG

by walid yaich

Hello, When clicking on preview, I need to add some velocity code before rendring the page, please where can i find the code of preview button of the editor "WYSIWYG" ? Thanks in advance

10 years, 6 months

[xwiki-devs] [XWiki Day] PR Review Day #1

by vincent＠massol.net

Hi devs, We’re Thursday and Thursday is XWiki Day! :) I’d like to propose that we do our first PR Review Day today. The goal is to review all the JIRA issues that have patches or PRs in them (http://jira.xwiki.org/secure/IssueNavigator.jspa?reset=true&mode=hide&jqlQu…) and: - apply them if possible - comment on them if something is missing/not right - set the proper “Pull Request Status” field value: Awaiting Committer Feedback, Awaiting Contributor Feedback, None - ping the contributor if we’ve already asked for some info and we didn’t get it - if some PR are almost good then spend the extra time to finish them to allow applying the PR Process: - when you start reviewing a PR please assign it to yourself to set the lock on it - when you’re done, if the issue wasn’t closed, then unassign yourself Please record: - how many issues you’ve reviewed - how many PRs you’ve applied WDYT? Let’s do it! :) Thanks -Vincent

10 years, 6 months

[xwiki-devs] [Proposal] Cleaning our POM deps by explicitly listing used dependencies?

by Vincent Massol

Hi devs, Running mvn dependency:dependency-analyze produces interesting results. For example: [INFO] --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- [INFO] Building XWiki Commons - Properties 3.2-SNAPSHOT [INFO] --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- … [INFO] --- maven-dependency-plugin:2.3:analyze (default-cli) @ xwiki-commons-properties --- [WARNING] Used undeclared dependencies found: [WARNING] org.slf4j:slf4j-api:jar:1.6.1:compile [WARNING] javax.inject:javax.inject:jar:1:compile [WARNING] Unused declared dependencies found: [WARNING] org.xwiki.commons:xwiki-commons-component-api:jar:3.2-SNAPSHOT:compile [WARNING] org.xwiki.commons:xwiki-commons-test:jar:3.2-SNAPSHOT:test [WARNING] org.hibernate:hibernate-validator:jar:4.2.0.Final:test [WARNING] org.hamcrest:hamcrest-core:jar:1.1:test [WARNING] org.jmock:jmock:jar:2.5.1:test The question is (for this module but more generally for all others): * Should we add slf4j and javax.inject reps in the pom.xml for this module? (for ex today slf4j and javax.inject are found in the component-api dep) I think we should, wdyt? Note that the "Unused declared dependencies found:" doesn't always generate correct results as is the case here. This is mostly because it's a static byte code check so any dep used at runtime will be considered unused. See http://www.sonatype.com/books/mvnex-book/reference/optimizing-sect-dependen… Thanks -Vincent

10 years, 6 months

[xwiki-devs] Fw: CKEditor.com :: new comment on Where are the sources for CKBuilder?

by vincent＠massol.net

At last! Good news :) -Vincent On 4 Jun 2014 at 13:40:19, noreply(a)ckeditor.com (noreply@ckeditor.com(mailto:noreply@ckeditor.com)) wrote: > Hi vmassol, > > wiktor has commented on: "Where are the sources for CKBuilder?" > > ---- > Apologies for taking so long to publish it. We had a plan to rewrite > CKBuilder to node.js, but after realising that it would be a pretty > time-consuming task, we've decided to postpone it till CKEditor 5. After > cleaning up the code, documentation etc. the source files are finally > available: > > https://github.com/ckeditor/ckbuilder [1] > > Thanks for your patience! > > ---- > > You can view the comment at the following url > http://ckeditor.com/comment/132339#comment-132339

10 years, 6 months

[xwiki-devs] Users are in need of a reusable Tree view of pages, what can we do?

by vincent＠massol.net

Hi devs, I’ve noticed a recurring trend from our users: a lot of them seem to wish to display Tree views/navigation view of their wiki pages either in page content or in a panel. When they go to e.x.o, there’s a lot of extensions listed (showing that other users had this need previously) but none really work well: http://extensions.xwiki.org/xwiki/bin/view/Extension/WebHome#|t=extensions&… We do have a tree view in AllDocs but it’s not perfect and it’s not easily reusable. Thus I believe we need to find an official solution to this tree view issue. The easiest solution could be to create a wiki macro based on our current tree view so that it can be reused in wiki pages and more importantly in a panel. Having a “spaces” parameter to restrict the list of spaces to display would be nice too. WDYT? Any other idea? Thanks -Vincent

10 years, 6 months

[xwiki-devs] [Proposal] Color Theme Application for Flamingo

by Guillaume "Louis-Marie" Delhumeau

Good evening, We have discussed recently about the necessity of having a new Color Theme Editor for Flamingo. Some of you have suggested to try to integrate in XWiki an existing Bootstrap Customizer such as FancyBoot: http://fancyboot.designspebam.com/ After looking on Google and Github, I could not find any that matches this criterias: - Bootstrap 3 support - active - compatible with an XWiki integration That is why I propose to write our own, which could actually take some code from existing projects. On my side, I have written 2 prototypes and I have pushed them in a new github repository: https://github.com/xwiki-contrib/bootstrap-customizer-prototypes Prototype A ==== Demo: http://xwiki-contrib.github.io/bootstrap-customizer-prototypes/prototypeA/ (chrome users: please refresh the page if you do not see a color picker when you click on an input box) This prototype opens a real web page inside an iframe, and use the LESS browser compiler to update the CSS. Pros: - it uses LESS so it shows the **real** results - any wiki page can be seen in the preview frame - not so hard time to implement Cons: - it is quite slow, and sometimes the browser gets frozen for a few seconds. Prototype B ==== Demo: http://xwiki-contrib.github.io/bootstrap-customizer-prototypes/prototypeB/ This prototype emulates the behaviour of LESS when we change some variables. The results is displayed in a preview box, but it is a fake one. Pros: - The prototype runs quickly in the browser because there is no LESS compiler involved. Cons: - The preview box is not a real page and it cannot show all use-cases. - Will take more time to implement and to maintain because we have to manually emulate what LESS would do in the preview box. I'm +1 for Prototype A. What do you think? Thanks, Guillaume

10 years, 6 months

[xwiki-devs] Caused by: java.lang.RuntimeException: Assertion botch: negative time

by walid yaich

Hi Devs, I have a loop in which i add object to all documents under the space "Main", it crashes in the middle of the loop ... ##get all document in the Main space #set($docus = $xwiki.getSpaceDocsName("Main")) #foreach($docu in $docus) #set ($myDoc = $xwiki.getDocument("Main", $docu)) $myDoc.getFullName() ##Add object to the page #set($obj = $myDoc.newObject("Revision.RevisionClass")) $obj.set("approvedRev", $myDoc.getVersion()) ## Save the object in the page $myDoc.getDocument().setMetaDataDirty(false) $myDoc.getDocument().setContentDirty(false) $myDoc.save() #end Stack is attached Please any method to catch the exception and let it go in Velocity Thanks in advance :)

10 years, 6 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs June 2014