- xwiki-devs@xwiki.org - lists.xwiki.org

[xwiki-devs] [Vote] Create component API for skinx
by Anca Luca 07 Jan '11

07 Jan '11

Hi devs, I wanted to create a component to define the interface for the skin extension mechanism: @ComponentRole public interface SkinExtension { public void use(String resource); public void use(String resource, Map<String, Object> parameters); } in a module in platform/core called xwiki-skinx-api or xwiki-skinx-bridge-api and then implement it with ssx, jsx, ssfx, jsfx, ssrx, jsrx hints in the skinx plugin. Basically the implementation will do nothing else but grab the XWikiContext from the Execution, grab XWiki from there, get the plugin api and call the use function on it. This will be useful to write code that needs the skin extensions but doesn't want to depend on the core (macros, for example) and it will serve as a bridge towards the future implementation of the skinx plugin as a component. My +1 for the proposed interface in xwiki-skinx-api and the implementation in the plugin. WDYT? Thanks, Anca

3 4

Re: [xwiki-devs] [xwiki-notifications] r33834 - platform/web/trunk/standard/src/main/webapp/templates
by Ecaterina Moraru (Valica) 06 Jan '11

06 Jan '11

thanks sergiu On Thu, Jan 6, 2011 at 06:54, sdumitriu <platform-notifications(a)xwiki.org>wrote: > Author: sdumitriu > Date: 2011-01-06 05:54:21 +0100 (Thu, 06 Jan 2011) > New Revision: 33834 > > Modified: > platform/web/trunk/standard/src/main/webapp/templates/createinline.vm > Log: > XWIKI-5855: Make create templates compliant with our vertical forms > standard > Revert a change which makes the HTML invalid (the <form> element accepts > only block level elements, and <input> are inline elements) > > Modified: > platform/web/trunk/standard/src/main/webapp/templates/createinline.vm > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/templates/createinline.vm > 2011-01-06 04:49:30 UTC (rev 33833) > +++ platform/web/trunk/standard/src/main/webapp/templates/createinline.vm > 2011-01-06 04:54:21 UTC (rev 33834) > @@ -175,6 +175,7 @@ > ## Display the form. > ## > --------------------------------------------------------------------------------------------------------- > <form action="$doc.getURL('create')" method="post" class="xform third"> > + <div> > <input type="hidden" name="tocreate" value="$tocreate"/> > #if($tocreate == 'page') > ## > --------------------------------------------------------------------------------------------------------- > @@ -310,4 +311,5 @@ > <input type="submit" class="button" value="$msg.get('create')"/> > </span> > </div> > + </div> > </form> > \ No newline at end of file > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications >

1 0

[xwiki-devs] Only XWiki 1.0 syntax is allowed after migration
by Valdis Vītoliņš 04 Jan '11

04 Jan '11

Hello! I'm migrating my Xwiki site from 2.1.1.25889 to 2.7.33656 and I cant catch why only Xwiki 1.0 syntax is allowed. On editing Page Syntax combo box shows only Xwiki 1.0 and rendering also looks bit wrong. E.g. some pages show {pre} tags. I tried to change ../WEB-INF/xwiki.cfg file without any success. Can anybody provide some hints? Thanks! Valdis

2 3

[xwiki-devs] [Proposal] Rendering refactoring: introduce the notion of original blocks to the core Block API
by Vincent Massol 03 Jan '11

03 Jan '11

Hi devs, This is a bit technical but after brainstorming with Thomas we came to the conclusion that in order to implement "generic marker" support the best solution would be to add the notion of original blocks to the Block interface itself. This will results in 2 things: * adding new begin/endOriginalBlocks events (in Listener.java) * adding a CollectionBlock that is a non content block used simply to group together one or several blocks. We'll need it in the following use case: when a single block is replaced with several blocks, we'll need to wrap the several blocks in a CollectionBlock that has an originalBlocks field set to the previous single block. It's also needed in some other use cases, for example when a block is replaced by a leaf block (non father block), we need a wrapper block to group together begin/endOriginal blocks and the new block events. In summary the idea is to not require a new generic marker block and instead set the notion of original block in the Block interface itself. WDYT? Thanks -Vincent

2 1

[xwiki-devs] [ANN] XOffice 1.1.2 Released
by Florin Ciubotaru 03 Jan '11

03 Jan '11

This is a small maintenance release that puts XOffice inline with newer XWiki versions. Check out XOffice at: http://xoffice.xwiki.org/xwiki/bin/view/Main/WebHome Release notes for v1.1.2: http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXOffice112 Thanks, The XWiki dev team.

1 0

[xwiki-devs] xwiki.org is down?
by Paul Libbrecht 02 Jan '11

02 Jan '11

Hello fellow developers, I can't reach http://www.xwiki.org/xwiki/bin/view/Main/WebHome while www.xwiki.org redirects properly (so the xwiki is down, not the apache). Something must be hanging wrong somewhere. That makes it that I can't commit it seems. Skol seems to be "working" since quite a while (more than an hour?). paul

2 1

Re: [xwiki-devs] [xwiki-notifications] r33714 - enterprise/trunk/wiki/src/main/resources/ColorThemes
by Sergiu Dumitriu 28 Dec '10

28 Dec '10

On 12/28/2010 01:22 PM, evalica (SVN) wrote: > Author: evalica > Date: 2010-12-28 13:22:42 +0100 (Tue, 28 Dec 2010) > New Revision: 33714 > > Modified: > enterprise/trunk/wiki/src/main/resources/ColorThemes/ColorThemeClass.xml > enterprise/trunk/wiki/src/main/resources/ColorThemes/ColorThemeSheet.xml > enterprise/trunk/wiki/src/main/resources/ColorThemes/ColorThemeTemplate.xml > enterprise/trunk/wiki/src/main/resources/ColorThemes/DefaultColorTheme.xml > enterprise/trunk/wiki/src/main/resources/ColorThemes/WizardPropertyMapping.xml > Log: > XE-796: Customizable "Add" menu entry from the Color Theme Wizard > > Modified: enterprise/trunk/wiki/src/main/resources/ColorThemes/ColorThemeSheet.xml > =================================================================== > --- enterprise/trunk/wiki/src/main/resources/ColorThemes/ColorThemeSheet.xml 2010-12-28 12:18:23 UTC (rev 33713) > +++ enterprise/trunk/wiki/src/main/resources/ColorThemes/ColorThemeSheet.xml 2010-12-28 12:22:42 UTC (rev 33714) > @@ -1431,6 +1434,7 @@ > <div #elementMetaData('mainmenu')> > <div> > $msg.get('xe.themes.colors.wizard.mainMenu') I think it would be better to use a different text for this one, since it's supposed to be used only for the Add entry: > +<span #elementMetaData('menuaddentry')>$msg.get('xe.themes.colors.wizard.menuEntry')#$msg.get('core.menu.create')</span> > <span #elementMetaData('menuentry')>$msg.get('xe.themes.colors.wizard.menuEntry')#1</span> > <span #elementMetaData('menuentry')>$msg.get('xe.themes.colors.wizard.menuEntry')#2</span> > </div> > -- Sergiu Dumitriu http://purl.org/net/sergiu/

2 2

[xwiki-devs] [Proposal] Make an UPDATE XAR of XWiki Enterprise standard XAR
by Ludovic Dubost 28 Dec '10

28 Dec '10

Hi, We have a general problem when upgrading XWiki which is to not forget to exclude certain files from the import. The manual exclusion is something that generates all sorts of problems especially when done by less experienced users. These files are: - preferences - all and admin group - admin user - invitation config file - anotation config file Either we make a FULL and an UPGRADE XAR or we make a CODE and CONFIG xar (initial install would need both xars to be imported). I'm more for the solution of one FULL and one UPGRADE xar. Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

2 1

[xwiki-devs] [Vote] [Standards] Forms: Usage + Documentation page to XWiki.org
by Ecaterina Moraru (Valica) 27 Dec '10

27 Dec '10

Hi devs, A. Usage: Some time ago I made a proposal about the form usage standard: http://markmail.org/thread/5ya4iozbpl2c2kf2 Since then, the standard has been used by: - Marta and Sergiu in "Send by email" feature http://incubator.myxwiki.org/xwiki/bin/download/Standards/Forms/ShareByEmai… - Marius in "WYSIWYG Configuration in Administration" http://incubator.myxwiki.org/xwiki/bin/download/Standards/Forms/WYSIWYGConf… - the original proposal also reflected possible usage of the places where the forms new style could be applied http://incubator.myxwiki.org/xwiki/bin/view/Standards/FormsProposal This is a vote mail to include the form standard CSS in colibri.css, in order to avoid duplication and to start using it the standard to all our forms elements. So here is my +1. B. Documentation: The documentation for the usage of the proposed form standard is at: http://incubator.myxwiki.org/xwiki/bin/view/Standards/FormVerticalUsage If you have something to add to it, please do, otherwise, after we will add the code in the platform, the documentation will also move to xwiki.orgat http://platform.xwiki.org/xwiki/bin/view/DevGuide/FrontendResources My +1. Thanks, Caty

12 13

[xwiki-devs] [VOTE] New committer: Raluca Stavro
by Sergiu Dumitriu 25 Dec '10

25 Dec '10

Hi devs, I'd like to propose Raluca as a committer. Raluca is one of the first employees of the of the Romanian branch of XWiki SAS, with more than three years experience developing applications on top of the XWiki platform. She didn't have time to contribute that much code to the platform, but she's been active on the mailing lists, she provided several patches, and she's the main developer behind the new Activity reimplementation of the old Recent Changes feature. I trust her to bring good value to the community, so here's my +1. -- Sergiu Dumitriu http://purl.org/net/sergiu/

10 10