xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

by Sergiu Dumitriu

On 10/15/2009 12:05 PM, asiri (SVN) wrote: > Author: asiri > Date: 2009-10-15 12:05:22 +0200 (Thu, 15 Oct 2009) > New Revision: 24508 > > Modified: > Log: > [misc] Activated checkstyle for officeimporter code base. > > - Fixed 71/72 Checkstyles reported. > > - The remaining checkstyle issue (class fan-out ~ 22, max allowed is 20) is bit hard to fix without refactoring the officeimporter API a little. You can fix it by removing the readStream utility method, which can be replaced with something from commons-ioutils. This will remove all usages of ByteArrayOutputStream and IOException and add one class from ioutils. -- Sergiu Dumitriu http://purl.org/net/sergiu/

15 years, 3 months

[xwiki-devs] [VOTE] XE 2.0.3 release on 3rd of Nov 2009

by Vincent Massol

Hi, We have 2 critical fixes in XE 2.0.3: - The stats are broken (since 2.0.1) - The object editor doesn't allow to add objects for which the user doesn't have edit rights on the document holding the class definition (since 2.0) + some other fixes: http://jira.xwiki.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10010… Thus I'm proposing to release ASAP, which is next Tuesday (since Thomas is on holidays till next Monday - That's unless someone else want to do the release of course). Here's my +1 Thanks -Vincent

15 years, 3 months

[xwiki-devs] [VOTE] Don't release 2.1M1 and instead replace 2.1M2 with 2.1M1

by Vincent Massol

Hi, We were supposed to release 2.1M1 yesterday according to our initial roadmap. However we've all been working on 2.0.x releases and as a consequence there isn't much in 2.1M1 that isn't in 2.0.x releases. Namely there are 11 issues and most of them are not very important (see http://tinycoke.com/_6rvPPs9pSbA/picture_1.png) and don't warrant a release IMO. I'm proposing to remove 2.1M2 and extend 2.1M1 till 16 Nov (ie the date when 2.1M2 was supposed to be released). The other dates are kept unchanged, see http://enterprise.xwiki.org/xwiki/bin/view/Main/Roadmap Here's my +1 Thanks -Vincent

15 years, 3 months

[xwiki-devs] Xwiki Flyer

by Leon Wang

Hi Marius, I will make Xwiki a advertisement flyer. After I done I will sent it to you. Thank you for your reply! Have a nice night! Leon

15 years, 3 months

Re: [xwiki-devs] [Proposal][UX] User Profile and Preferences

by PERINAUD Christophe

Hi again, Same problem, can't reach page. I have the same problem with all myxwiki.org subdomains. > -----Message d'origine----- > De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] > De la part de Ecaterina Valica > Envoyé : jeudi 29 octobre 2009 16:13 > À : XWiki Mailinglist > Objet : [xwiki-devs] [Proposal][UX] User Profile and Preferences > > Hi devs, > > With the new ActionMenu > Proposal<http://incubator.myxwiki.org/xwiki/bin/view/Improveme > nts/ActionMenuProposal>I've > made a separation between: > > - Profile - things related to the user > - > > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/UserP > rofileProposal > - Preferences - things related to user's account > - > > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/UserP > referencesProposal > > Please give feedback about: > > 1. the utility of the functionality added: Groups, Recent Activity > 2. Default Fields: > 1. is there a way to have dynamic fields in user class? > 2. what fields should be default in the static case? > 1. fields web oriented > 2. fields business oriented > 3. which are those fields? > > Thanks, > Caty > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -------------------------------------------------------------------------------- This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies. While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection. KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1

15 years, 3 months

Re: [xwiki-devs] Use WYSIWG New Backgournd Color API To: XWiki Developers

by Leon Wang

Hi Marius, I integrate the tree in the latest XE snapshot, it works! Thank you! Where can I find the color vocabulary specified by your API? Can I use hex number to specify color? It seems the snapshot version can not save document and it will automatically generate so many sessions. It only works on my Dell pc, does not work on the linux server. If I try to save document (on linux I even can not create and save edit panel) it will prompt me this error: HTTP Status 500 - ------------------------------ *type* Exception report *message* ** *description* *The server encountered an internal error () that prevented it from fulfilling this request.* *exception* java.lang.StringIndexOutOfBoundsException: String index out of range: -1 java.lang.String.substring(Unknown Source) java.lang.String.substring(Unknown Source) com.xpn.xwiki.web.ActionFilter.getTargetURL(ActionFilter.java:167) com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:105) com.xpn.xwiki.plugin.webdav.XWikiDavFilter.doFilter(XWikiDavFilter.java:68) com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:295) com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) Next Friday it is our University Graduate Forum, I have a poster presentation. Do you need me to print and hand out flyer of Xwiki to people to give Xwiki a advertisement? Really appreciate your help! Have a nice weekend! -Leon

15 years, 3 months

Re: [xwiki-devs] [Proposal][UX] Action Menu

by PERINAUD Christophe

Hi, Can't get to the page. I got this : The XML page cannot be displayed Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later. -------------------------------------------------------------------------------- The operation was timed out. Error processing resource 'http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd'. I use IE 6.0 Christophe Périnaud Windows Server 2003 SP2 in a VMWare instance Oracle 10g Java 1.6.0_12 Xwiki 1.9.2 from the pack Jetty/HSQL > -----Message d'origine----- > De : devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org] > De la part de Ecaterina Valica > Envoyé : jeudi 29 octobre 2009 16:03 > À : XWiki Mailinglist > Objet : [xwiki-devs] [Proposal][UX] Action Menu > > Hi devs, > > Part of the XE 2.1 roadmap is the improvement of the action bar. > > Proposal can be viewed at: > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Actio > nMenuProposal > > There are some icon usage variants: > > - no icons (just like Colibri) > - Var1: partial icons > - > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Actio > nMenuVar1 > - Var2: full icons > - > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/Actio > nMenuVar2 > > Ideas: > > - there could be an option to display or not the icons in the > administration > > I would like if you could give: > > 1. some feedback about the proposals > 2. a preference between the icons variants (Var1, Var2) > > Thanks, > Caty > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -------------------------------------------------------------------------------- This e-mail is intended only for the addressee named above. It does not bind the sender, except in the case of an existing written convention with the addressee. This e-mail may contain material that is confidential and privileged for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender and delete all copies. While reasonable precautions have been taken to ensure that this e-mail and any attachments are free from any computer virus or similar defect, no liability will be accepted in that respect. Anyone accessing this e-mail must take their own precautions as to security and virus protection. KBL European Private Bankers S.A., 43 boulevard Royal L-2955 Luxembourg, R.C.S. Luxembourg B 6395, T (352) 47 97 1

15 years, 3 months

[xwiki-devs] XWiki Watch 1.1 M1

by ivm-dev

Hi, we'd like to test the XWiki Watch 1.1 M1 release. Tried to build it but couldn't manage to build only the xar-File. Is that not possible or are we missing something. Thanks Helmut -- View this message in context: http://n2.nabble.com/XWiki-Watch-1-1-M1-tp3905468p3905468.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

15 years, 3 months

[xwiki-devs] [Proposal] Add "always on this page" value for SSX "use" property

by Teofil Achirei

Hi! I was wondering if it's OK to add a third possible value for stylesheet extension "use" property, something like "always on this page". This could also be the default value. As far as I know, the two possible values for SSX "use" property are: - "on demand" - which means that any page can demand that SSX - "always" - which means that all pages will have the CSS for that object While these two properties are very good and practical, there are some minor aspects: 1) Somebody (perhaps a designer) can create a SSX and other users (perhaps content editors) forget to "demand" it 2) Having a SSX with use="always" and a second SSX with use="on demand" both on the same page makes the two objects available for all wiki pages (in term of client side CSS) 3) The content is aware of the design. It's ok if in the content of a wiki page we can demand the stylesheet of another page, and that we can create some stylesheet that will be used by all wiki pages. But, in my opinion, the content must not be aware of it's own design. This third value ("use"="always on this page") will also help other projects like XOffice and XOO. At this moment, XWord, for example, should follow these steps: - save the page first (you can't create a SSX on an unpublished/nonexistent page) - identify saved page syntax (XWord works with XHTML) - "know" how the SSX macro looks-like in page's syntax (yeah, not a big deal, but it's something that XWord shouldn't care about) - edit the content to insert the $xwiki.ssx.use($docFullname) - publish the page, again "Always on this page" (or "always on parent page") usage could improve some of the aspects mentioned above. Any other solution is welcomed. What do you think? Thanks! -- Teofil Achirei

15 years, 3 months

[xwiki-devs] Deploy the lastest XE snapshot

by Leon Wang

Dear Devs, Could anyone give me some idea or give me a reference a material/ or example to help me deploy the last XE snapshot. My guess is to write maven pom file. I think just one pom file will do the work, right? Just mvn install. I do look up the Maven definitive guide, it says we could the a version value of LASTEST to refer to the lastest released or snapshot version of a particular artifact. Could anyone send me one please? Thank you everyone! Have a nice day! :-) Leon

15 years, 3 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