xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] [Proposal][Standard][UX] Forms

by Ecaterina Valica

I've made some additions to our Forms Standard page: http://incubator.myxwiki.org/xwiki/bin/view/Standards/Forms The standard is very similar to what we have for the WYSIWYG editor: - vertical alignment - display of labels (we have uppercase text for Colibri style consistency) - display of hints/error messages - primary/secondary buttons I made a proposal to integrate this standards inside the platform: http://incubator.myxwiki.org/xwiki/bin/view/Standards/FormsProposal - administration - object editor - user profile - Create Space/Page - Copy/Rename Page Any feedback is welcomed, Caty

14 years, 6 months

[xwiki-devs] Fwd: [ANN] Maven Release Plugin 2.1 Released

by Vincent Massol

fyi -Vincent Begin forwarded message: > From: Brett Porter <brett(a)apache.org> > Date: October 8, 2010 7:03:48 PM GMT+02:00 > To: announce(a)maven.apache.org, Maven Users List <users(a)maven.apache.org> > Cc: Maven Developers List <dev(a)maven.apache.org> > Subject: [ANN] Maven Release Plugin 2.1 Released > Reply-To: users(a)maven.apache.org > > The Maven team is pleased to announce the release of the Maven Release Plugin, version 2.1 > > This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. > > http://maven.apache.org/plugins/maven-release-plugin/ > > You should specify the version in your project's plugin configuration: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-release-plugin</artifactId> > <version>2.1</version> > </plugin> > > Release Notes - Maven Release Plugin - Version 2.1 > > ** Bug > * [MRELEASE-128] - SCM properties being replaced during release:perform > * [MRELEASE-317] - release:prepare should fail if any pom depends on SNAPSHOT parent > * [MRELEASE-318] - Release plugin throws NullPointerException when using version range for dependency > * [MRELEASE-350] - Option '0' for "specify the selection number ( 0:All 1:Project Dependencies 2:Plugins 3:Reports 4:Extensions ):" is broken > * [MRELEASE-370] - release:prepare is not updating inter-modules dependencies to the next version snapshot identifier correctly (-DdryRun=true). > * [MRELEASE-458] - Branch Does Not Honor updateWorkingCopyVersions Setting > * [MRELEASE-524] - command line versions don't seem to work on release:branch for specific format > * [MRELEASE-536] - CommonBasedir Calculation fails on windows > * [MRELEASE-546] - regression introduced in MRELEASE-261 > * [MRELEASE-551] - Unable to release with maven 3 when having no $HOME/.m2/settings.xml > * [MRELEASE-563] - help strings need help, they are not helpful out of context > * [MRELEASE-586] - release:perform - The temporary file "pom.xml.branch" should be ignored as "pom.xml.next" and "pom.xml.tag" are ignored > * [MRELEASE-589] - Resolved dependencies overwritten when multiple subprojects with SNAPSHOT dependencies are released > > ** Improvement > * [MRELEASE-497] - Don't overwrite SVN auth cache > * [MRELEASE-530] - Git provider does 'git push' during 'mvn release:prepare' which causes unwanted problems (scm 1.4 upgrade) > * [MRELEASE-554] - Allow custom files to be modified before doing a prepare or branch... > * [MRELEASE-583] - Better Snapshot Dependency Handling > > Enjoy, > -The Maven team > > -- > Brett Porter > brett(a)apache.org > http://brettporter.wordpress.com/ > > > >

14 years, 6 months

[xwiki-devs] [discussion] Synchronizing version numbers of applications, plugins, and core.

by Caleb James DeLisle

I have been observing problems with the versioning scheme which we are using. Because applications are not branched along with core, when a bugfix version of a stable branch is released, new versions of applications are typically pulled in. This means that `experimental' code is being introduced into a `stable' branch in a bugfix version. This is not the path I would choose but more importantly we can't honestly say that our code goes through a milestone/release candidate verification process if some of the code is allowed to bypass it. This situation has caused me to make a mistake which I was able to correct during the release without major issue, I think the same issue is behind the release of 2 bogus versions (2.4.1 and 2.4.2) There is another issue, users who want to mix and match applications to build their own wiki are faced with a set of version numbers and no way to know what is compatible with what. A user who I spoke with last night had this very problem. We could publish a compatibility matrix but if we were to show all the versions a given application is compatible with, that would require testing each application version against each core version and I think we need to concentrate on testing what gets released in XE. Both of these problems would be fixed if version numbers were synchronized and everything was branched for a release. Relevant questions which come to mind are "do we need the capability to release applications at separate times?" and "is there no way to do that with synchronized version numbers?" Am I missing any other reasons? Should this not become a proposal? Caleb

14 years, 6 months

[xwiki-devs] UniqueIdentificationNumber component

by Stefan abageru

Hello Devs ! I built a component to handle unique generation of document names. The documents must be instantiations of a specified class and the generation is done taking into consideration the currently existing documents and all the values used before. It retrieves the maximum value currently used, increments It is configurable in xwiki.properties. More info cand be found here http://code.xwiki.org/xwiki/bin/view/Plugins/UniqueIdentificationNumberPlug… . Thanks, Stefan Abageru !

14 years, 6 months

[xwiki-devs] [proposal] Deprecate com.xpn.xwiki.api.Context#getUtil()

by Caleb James DeLisle

Hi, I would like to hard deprecate com.xpn.xwiki.api.Context#getUtil(). It exposes functions to the user which are not optimized for scripting and some of which are security vulnerabilities. This class is not in the api package and it appears that it was never intended to be exposed to the user. +1 @Deprecated. Caleb

14 years, 6 months

[xwiki-devs] [Proposal] Merge Link and Image as Reference in Rendering module

by Vincent Massol

Hi, This is a technical refactoring but I'm posting it here since it means changing our rendering API quite significantly. Basically we currently have 2 notions: Image and Link. I'd like to make them one (called Reference) since we need/want to handle similarly and this would remove lots of duplicated code. Since we've already broken quite a lot of Rendering APIs in XE 2.5M1/M2 I feel it's a good time to be brave and go the full monty... ;) I've started the work already but wanted to keep you posted in case someone disagrees. For the record this is about implementing: - http://jira.xwiki.org/jira/browse/XWIKI-5549 - http://jira.xwiki.org/jira/browse/XWIKI-5554 Thanks -Vincent

14 years, 6 months

Re: [xwiki-devs] [xwiki-notifications] r31632 - platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode

by Sergiu Dumitriu

On 10/05/2010 10:55 AM, Ecaterina Valica wrote: > .annotationAvatar img { > + max-width: 50px; > + max-height: 50px; > +} > > the initial proposal contained #smallUserAvatar (30px) instead of > #mediumUserAvatar (50px) > > http://incubator.myxwiki.org/xwiki/bin/Improvements/AvatarsProposalAnnotati… Yes, I noticed that. However, IMO it's not really needed as a small image, since the medium size also fits well. > > On Tue, Oct 5, 2010 at 01:39, sdumitriu > <platform-notifications(a)xwiki.org > <mailto:platform-notifications@xwiki.org>> wrote: > > Author: sdumitriu > Date: 2010-10-05 00:39:24 +0200 (Tue, 05 Oct 2010) > New Revision: 31632 > > Modified: > > platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Macros.xml > > platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Style.xml > Log: > XAANNOTATIONS-34: Display user avatars on annotations > Done. > + minor layout changes to make the UI more consistent with the > comments tab. > > Modified: > platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Macros.xml > =================================================================== > --- > platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Macros.xml > 2010-10-04 22:38:42 UTC (rev 31631) > +++ > platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Macros.xml > 2010-10-04 22:39:24 UTC (rev 31632) > @@ -134,6 +134,7 @@ > #set($mode = 'view') > #end > <div class="annotation $!{ann.state}" > id="annotation_${mode}_$!{ann.id <http://ann.id>}"> > + <div > class="annotationAvatar">#mediumUserAvatar($ann.author)</div> > <div class="annotationHeader"> > #displayAnnotationTitle($ann) > #displayAnnotationToolbox($ann $mode $docWiki $docSpace $docPage) > @@ -213,6 +214,18 @@ > ## Fake object that allows to use the API to generate the display > #set($fakeObj = $doc.newObject($annotationClassDocName)) > #set($properties = $annotationClass.properties) > + #if ($properties.size() == $hiddenProperties.size() + 1) > + ## Do not show property labels if there's only one property to > display > + #set($prop = $annotationClass.get('annotation')) > + #set($discard = $fakeObj.set($prop.name <http://prop.name>, > "$!{ann.get($prop.name <http://prop.name>)}")) > + <div class="annotationText"> > + #if($mode == 'edit' || $mode == 'create') > + $doc.displayEdit($prop, '', $fakeObj) > + #else > + $doc.displayView($prop, '', $fakeObj) > + #end > + </div> > + #else > <dl> > #foreach($prop in $properties) > #if (!$listtool.contains($hiddenProperties, $prop.name > <http://prop.name>)) > @@ -226,6 +239,7 @@ > #end > #end > </dl> > + #end > #end > {{/velocity}}</content> > </xwikidoc> > > Modified: > platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Style.xml > =================================================================== > --- > platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Style.xml > 2010-10-04 22:38:42 UTC (rev 31631) > +++ > platform/xwiki-applications/trunk/annotations/src/main/resources/AnnotationCode/Style.xml > 2010-10-04 22:39:24 UTC (rev 31632) > @@ -241,7 +241,7 @@ > } > > .annotation-box { > - padding: 2px 12px 4px 6px; > + padding: 6px 12px; > } > > .annotation-bubble .loading { > @@ -252,6 +252,29 @@ > width: 99%; > } > > +.annotationAvatar { > + float: left; > + width: 55px; > + text-align: left; > +} > +.annotationAvatar img { > + max-width: 50px; > + max-height: 50px; > +} > +* html .annotationAvatar img { > + width: 50px; > +} > + > +#allAnnotations .annotationAvatar { > + padding-top: 5px; > +} > + > +#allAnnotations .annotationHeader, #allAnnotations .annotationContent { > + margin-left: 55px; > +} > +#allAnnotations .annotationTitle * { > + line-height: 1.4em; > +} > .annotation-box .annotationAuthor { > border-bottom: 1px dotted $theme.borderColor; > display: block; > @@ -264,30 +287,10 @@ > margin-right: 51px; > display: block; > } > -.annotationContent { > +.annotation-bubble .annotationContent { > clear: both; > } > > -## In velocity comment: settings for using the larger images from silk > -.annotation-box .annotation { > - ##padding: 0 0 0 18px; > - ##background: transparent #imgURL('note') left top no-repeat; > - padding: 0 0 0 14px; > - background: transparent #attImgURL('notesmall') left 4px no-repeat; > -} > -.annotation-box .buttons { > - ##padding: 0 0 0 18px; > - padding: 0 0 0 14px; > -} > - > -/* Make room for the large note_add icon */ > -.annotation-box-create .annotation, .annotation-box-create .buttons { > - padding-left: 18px !important; > -} > -.annotation-box-create .annotation { > - background: transparent #imgURL('note_add') left top no-repeat > !important; > -} > - > .annotation-box .links { > float: right; > font-size: 80%; > @@ -298,20 +301,20 @@ > background-image: #imgURL('note_add'); > } > > -/* Annotations list (extra-tab)*/ > -## In velocity comment: settings for using the larger images from silk > +/* Annotations list (extra-tab) */ > #allAnnotations .annotation { > - margin: 8px 0; > - ##padding: 0 0 0 18px; > - ##background: transparent #imgURL('note') left top no-repeat; > - padding: 0 0 0 14px; > + margin: 0 0 8px; > +} > +#allAnnotations .annotation .annotationText { > + padding: 0 36px 0 14px; > background: transparent #attImgURL('notesmall') left 4px no-repeat; > + text-align: justify; > } > -#allAnnotations .UPDATED, #xwikicontent .UPDATED, > .annotation-bubble .UPDATED { > +#allAnnotations .UPDATED .annotationText, #xwikicontent .UPDATED { > ##background-image: #imgURL('note_error'); > background-image: #attImgURL('notesmallorange'); > } > -#allAnnotations .ALTERED, #xwikicontent .ALTERED, > .annotation-bubble .ALTERED { > +#allAnnotations .ALTERED annotationText, #xwikicontent .ALTERED { > ##background-image: #imgURL('note_delete'); > background-image: #attImgURL('notesmallred'); > } > @@ -331,7 +334,6 @@ > display: block; > float: right; > margin-top: -1.2em; > - margin-right: -2px; > } > .annotationTools a { > background: transparent none no-repeat left top; > @@ -372,6 +374,9 @@ > } > .annotationContent dd, .annotationContent blockquote { > margin-bottom: 10px; > +} > +.annotationContent blockquote { > + padding-left: 12px; > }</code> > </property> > <property> -- Sergiu Dumitriu http://purl.org/net/sergiu/

14 years, 6 months

[xwiki-devs] Open World Forum Demo Cup 2010 award for XWiki SAS

by Emilie Ogez

Hi all, On Friday, October 1rst, XWiki SAS (http://www.xwiki.com) made a demo of the XWiki open source solution, as a finalist og the Demo Cup. It is one of the lucky winners! The Demo Cup is an opportunity to show innovative and promising open source solutions, selected very strictly. We are proud to announce that XWiki SAS received *one of five awards*, given by the jury composed of international experts from the field of open source. It rewards the work and commitment of a team and of the XWiki open source community. *So thank you to all of you! * The other winners are Bluegriffon, Obeo, Jaspersoft and Talend. About the Demo Cup: http://www.openworldforum.org/connect/awards Regards, Emilie ---- XWiki SAS Marketing & Communication Manager Web site: http://www.xwiki.com To subscribe to our newsletter: - http://www.xwiki.com/xwiki/bin/view/News/Newsletter Join our community on Facebook: - http://www.facebook.com/xwiki Follow us on Twitter: - http://www.twitter.com/xwiki

14 years, 6 months

[xwiki-devs] [Announcement] XWiki Enterprise 2.5 Milestone 2 Released

by Sergiu Dumitriu

The XWiki development team is pleased to announce the release of XWiki Enterprise 2.5 Milestone 2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download Main changes since XWiki Enterprise 2.5 Milestone 1: * Support for viewing attached office documents in the wiki * Experimental Extension Manager * New User Directory * Further improvements to the edit UI * More consistent use of user avatars * More image manipulation settings * Better handling of attachment versions when rolling back documents * Preliminary optional accessibility stylesheet * Experimental xwiki/2.1 wiki syntax * Interwiki links * Various Security improvements For more information see the Release notes at http://www.xwiki.org/xwiki/bin/Main/ReleaseNotesXWikiEnterprise25M2 Thanks -The XWiki dev team

14 years, 6 months

[xwiki-devs] [vote] Implement macros for the Main.Dashboard components for 2.5 RC

by Anca Luca

Hi guys, The Main.Dashboard revamping was supposed to be done in 2.5M2, but I didn't manage to. I would like to implement issues XE-719, XE-720, XE-721 and XE-722 during the RC phase, to have them for 2.5 final. Here's my +1, WDYT? If we do, the risk is that there would be issues, and the issues would be in the main page of the wiki, if we don't (and create the 2.6 branch and develop there), then we will be farther away with the implementation of the dashboard in the 2.5 release (basically only the macro to display columned content will be released in the final). Additionally, I might not be able to have everything done by RC time, but at least some of the macros should be implemented (the order is the one of the list above). Thanks, Anca

14 years, 6 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs