xwiki-devs April 2014

xwiki-devs@xwiki.org

27 participants
54 discussions

[xwiki-devs] Inject Warning in Page when Macro in Space not exists

by Matthias Wegner

Hi All, i want to put a {{warning}} in the header of a page when a specific macro is not contained. How can i do that. I tried in a Listener when the needed Macro-Block is not contained with doc.getXDOM().getRoot().addChild(new WordBlock("{{warning}}Warning Text.{{/warning}}")); context.getWiki().saveDocument(doc, context); This not works. What is the correct way to manipulate the Document DOM on Load? Regards, Matthias -- View this message in context: http://xwiki.475771.n2.nabble.com/Inject-Warning-in-Page-when-Macro-in-Spac… Sent from the XWiki- Dev mailing list archive at Nabble.com.

9 years, 10 months

[xwiki-devs] Overwrite Method of Component in Velocity

by Matthias Wegner

Hi All, I want to create a component where i can overwrite a method of the component from velocity or groovy script inside a wiki page. Its also fine if i can "read" a groovy script to the component so i can use the defined logic. Maybe i have to use a own programmed macro for that. Is that possible? Do you use something similar somewhere? Regards, Matthias -- View this message in context: http://xwiki.475771.n2.nabble.com/Overwrite-Method-of-Component-in-Velocity… Sent from the XWiki- Dev mailing list archive at Nabble.com.

9 years, 10 months

[xwiki-devs] Questions about fixing getRenderedContent() bug

by Vincent Massol

Hi, Im trying to fix http://jira.xwiki.org/jira/browse/XWIKI-4274 Basically if you do $xwiki.getDocument("someDoc").getRenderedContent() it'll get executed in the context of the current doc which I believe is wrong especially since other signatures of getRenderedContent() execute in the target document's context. I have fixed this locally but found that admin.vm for example is assuming that getRenderedContent() will get executed in the context of the calling doc (i.e. XWiki.Import when doing an import for example). FYI the chain flow is admin.vm -- getRenderedContent() --> XWiki.AdminSheet --> XWiki.AdminImportSheet --> importinline.vm, which requires the current doc to be XWiki.Import (to get/put attachments from/to it). I can fix this easily using a new getRenderedContent signature I've introduced. However I'm wondering if we have other places that incorrectly use getRenderedContent() and assume it won't be rendered in the context of the target document. Is this change too dangerous to make? If not know, we'll need to it quickly (2.1M1?) since it's an important bug IMO. WDYT? Thanks -Vincent

9 years, 10 months

[xwiki-devs] [Contrib] Request repository for Recruitment Application

by Alexandru Chelariu

Hello, I would like to request a repository on xwiki-contrib for the Recruitment Application i am working on. I'd like the repo to be named application-recruitment and also jira component. My github username is chalx. Thank you, Alexandru Chelariu

10 years, 2 months

[xwiki-devs] idea front end

by Yacine Kebir

Hello, i have an idea concerning the icons of base skin colibri or others, we should integrate "Entypo" on the skin ans delete all image icons, the advantage is : 1- we win the chargement time of pages 2- reduce the number of code lines in the code. 3- we can add, edit , put color and change the sise of this icons 4- the skin of this icons are in flat design and we can put it in any form 5- its free for any users for more information http://www.entypo.com/ wordpress have just integrate this solution Yacine

10 years, 5 months

[xwiki-devs] Flamingo Application Bar

by Guillaume "Louis-Marie" Delhumeau

Hi guys, I have pushed a first version of flamingo in platform/XE, but it is only a prototype that need a LOT more do be ready for production. One of the new things brought by flamingo is the "Applications" left bar, which is not exactly the same thing as the Applications Panel we already have. We can see it more as a "dock" with a list of applications, and in the future, we could make it customizable by the user. Caty has written a proposal for this [1]. Right now, for the first implementation, I need to make some choices about the way we "populate" this bar. We can create new classes to describe the bar entries, or new UI Extensions (maybe not the good choice regarding the recent e-mails...), or by re-using the existing AddApplicationUIX... It is described on http://design.xwiki.org/xwiki/bin/view/Proposal/AppBar#HImplementationConsi…. Other thing: In my draft, I have created a new VM file on the filesystem for this concept. Maybe I should create it as an extension point stored in the database, but it means it won't appear on an empty wiki. WDYT? I let you make some comments about this. Thanks, Caty & Louis-Marie [1] http://design.xwiki.org/xwiki/bin/view/Proposal/AppBar

10 years, 5 months

[xwiki-devs] [ANN] 10 years of the XWiki open source project!

by Vincent Massol

Hi everyone, On the 15th of December (i.e. in a month's time), it will be **10 years** since the first commit on the XWiki open source project. Ludovic did the first commit in CVS on Sourceforge: " 15.12.2003 10:13:33, by ludovic Initial revision " (Can be seen at http://svnsearch.org/svnsearch/repos/XWIKI/search?from=20030101&to=20040101 ) 10 years is starting to be some respectable milestone! I invite everyone to join us in celebrating by adding your own story about your interaction with the XWiki community or the XWiki software at http://dev.xwiki.org/xwiki/bin/view/Drafts/TenYearsOfXWiki <XWiki SAS hat> Since I'm also the CTO of the XWiki SAS company, I'd like to officially invite all the members of this great community to join us in celebrating the 10 days of the XWiki project at the XWiki SAS office in Paris, France on the 12th of December 2013. Here's the invitation: http://www.xwiki.com/lang/en/News/XWiki+10th+Anniversary See you there! </XWiki SAS hat> Well done everyone! -Vincent Massol

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] [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] 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs April 2014