xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] [Proposal] XEM 1.1 based on XE 1.3

by Thomas Mortagne

Hi all, As XEM 1.1 is planned for current March I would like to synchronise XEM 1.1 release on XE 1.3 final release planned for 14th of March. WDYT ? -- Thomas Mortagne

16 years, 9 months

[xwiki-devs] Creating an application on Xwiki

by Kamna Jain

Pardon me if I am asking very basic questions. But, my question is about being able to build enterprise level application on top of XWiki. For doing something like this, do I have to use the XWiki platform (core ) source code or XWiki Enterprise code or both? Is there a location on XWiki website which talks about the details of this. Thanks

16 years, 9 months

Re: [xwiki-devs] XWikiAttachments in SVN

by Kamna Jain

Vincen, Thanks much for the reply. It is very helpful But, the http://tinyurl.com/3352dy does not seem to work. Thanks On 2/21/08, devs-request(a)xwiki.org <devs-request(a)xwiki.org> wrote: > > Send devs mailing list submissions to > devs(a)xwiki.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.xwiki.org/mailman/listinfo/devs > or, via email, send a message with subject or body 'help' to > devs-request(a)xwiki.org > > You can reach the person managing the list at > devs-owner(a)xwiki.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of devs digest..." > > > Today's Topics: > > 1. Re: [VOTE] Bring forward XE 1.3 final + create branch > (Sergiu Dumitriu) > 2. Re: [vote] Switch to java 5 (Ludovic Dubost) > 3. Re: [vote] Switch to java 5 (Sergiu Dumitriu) > 4. XWikiAttachments in SVN ? (Kamna Jain) > 5. Re: XWikiAttachments in SVN ? (Vincent Massol) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 20 Feb 2008 14:11:46 +0100 > From: Sergiu Dumitriu <sergiu(a)xwiki.com> > Subject: Re: [xwiki-devs] [VOTE] Bring forward XE 1.3 final + create > branch > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: <47BC2712.3070305(a)xwiki.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > Vincent Massol wrote: > > Hi, > > > > I'd like to bring forward the release dates for XE 1.3 final, as > > follows: > > > > * 1.3RC1 - 25/02 > > * 1.3Final - 3/03 > > > > I'd also like to create a branch for 1.3 since it's now in RC stage > > and trunk will become 1.4-SNAPSHOT so that committers eager to work on > > 1.4 can start doing so and so that we're not tempted to push non bug > > changes in 1.3... > > > > The reasons: > > 1) We're ready to release it barring any regression we have introduced > > (which will be fixed in 1.3RC1) > > 2) Some of us are eager to work on 1.4 (like JV who's working on > > performance improvements for ex) :) > > 3) I'd like to drop support for 1.2 ASAP since it's hard to support > > several branches at once. When 1.3 is released it means we will be > > supporting 1.3 and 1.4 but no longer 1.2 (since our standard rule is > > to support 2 versions - Of course anyone is free to support whatever > > he wants but this is our general rule to make it easy to progress in > > our devs). > > 4) 1.3 hasn't had any major changes since 1.2 and thus should be > > pretty stable > > > > Here's my +1 to both the new dates and the branch creation. > > > > Thanks > > -Vincent > > > > +1 > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > > > ------------------------------ > > Message: 2 > Date: Wed, 20 Feb 2008 15:07:08 +0100 > From: Ludovic Dubost <ludovic(a)xwiki.org> > Subject: Re: [xwiki-devs] [vote] Switch to java 5 > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: <47BC340C.2080507(a)xwiki.org> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > > +1 > > Sergiu Dumitriu wrote: > > Hi devs, > > > > I think it is time to completely switch to Java 5. It adds several nice > > features we could use. > > > > I think it is safe to make the switch, given that: > > > > - We get only few mails related to deployment on Java 1.4, and only very > > few say that they cannot drop 1.4. > > - Java 1.4 is in the late EOL process (should end this summer) > > - We already have some requirements on 1.5 libraries, so XWiki doesn't > > really work on 1.4, anyway > > > > Here's my +1 > > > > > -- > Ludovic Dubost > Blog: http://blog.ludovic.org/ > XWiki: http://www.xwiki.com > Skype: ldubost GTalk: ldubost > > > > ------------------------------ > > Message: 3 > Date: Wed, 20 Feb 2008 15:21:33 +0100 > From: Sergiu Dumitriu <sergiu(a)xwiki.com> > Subject: Re: [xwiki-devs] [vote] Switch to java 5 > To: XWiki Developers <devs(a)xwiki.org> > Message-ID: <47BC376D.7080109(a)xwiki.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > 5 +1, 3 nb +1. > > Now I hope Velocity knows about enums... > > Sergiu Dumitriu wrote: > > Hi devs, > > > > I think it is time to completely switch to Java 5. It adds several nice > > features we could use. > > > > I think it is safe to make the switch, given that: > > > > - We get only few mails related to deployment on Java 1.4, and only very > > few say that they cannot drop 1.4. > > - Java 1.4 is in the late EOL process (should end this summer) > > - We already have some requirements on 1.5 libraries, so XWiki doesn't > > really work on 1.4, anyway > > > > Here's my +1 > > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > > > ------------------------------ > > Message: 4 > Date: Wed, 20 Feb 2008 12:41:16 -0600 > From: "Kamna Jain" <kammy.scorpi(a)gmail.com> > Subject: [xwiki-devs] XWikiAttachments in SVN ? > To: devs(a)xwiki.org > Message-ID: > <fb681d280802201041r462f5314k9f3e56f8470d726c(a)mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > Hi, > > I was wondering if this has ever been discussed before in this mailing > list > - Having the attched files being version controlled by SVN? > We use SVN a lot in our company and it would be great if there exists some > integration between XWiki and SVN to save the attached files. > > Thanks >

16 years, 9 months

[xwiki-devs] XWikiAttachments in SVN ?

by Kamna Jain

Hi, I was wondering if this has ever been discussed before in this mailing list - Having the attched files being version controlled by SVN? We use SVN a lot in our company and it would be great if there exists some integration between XWiki and SVN to save the attached files. Thanks

16 years, 9 months

[xwiki-devs] [vote] Switch to java 5

by Sergiu Dumitriu

Hi devs, I think it is time to completely switch to Java 5. It adds several nice features we could use. I think it is safe to make the switch, given that: - We get only few mails related to deployment on Java 1.4, and only very few say that they cannot drop 1.4. - Java 1.4 is in the late EOL process (should end this summer) - We already have some requirements on 1.5 libraries, so XWiki doesn't really work on 1.4, anyway Here's my +1 -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 9 months

[xwiki-devs] [Proposal] Skin Tester application

by Vincent Massol

Hi, Since we've realized that testing a new skin isn't easy, I'm going to start a Skin Tester application (a XAR) that will have some specially built page made for testing a skin. The idea is not to duplicate what's already in the default wiki. I'll start with a page listing all the macros so that they can be easily tested. I'll commit it in the platform applications. Feel free to improve it afterwards. Thanks -Vincent

16 years, 9 months

[xwiki-devs] modified jira dashboard

by Vincent Massol

Just wanted to let you know that I've modified the jira dashboard on http://jira.xwiki.org/jira/secure/Dashboard.jspa Whereas previously the 2 graphs were taking into account all JIRA projects on jira.xwiki.org they are now only taking into accout XE/XEM and all platform projects only. Thanks -Vincent

16 years, 9 months

[xwiki-devs] [ANN] XWiki Enterprise 1.3 Milestone 2 Released

by Vincent Massol

The XWiki development team is pleased to announce the release of XWiki Enterprise1.3 Milestone 2. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download Second and last milestone of the XWiki Enterprise 1.3 version. Next version will be a release candidate. Main changes from 1.3M1: * Lots of bugs fixed * New Toucan Skin. Warning: The Toucan skin requires that you have the Albatross 1.2 or greater version installed and that you have XWiki Enterprise 1.3M2 or greater installed. * Complete rewrite of the LDAP authentication support (see XWIKI-1079 for more details). Main changes: o Support for LDAP groups o If LDAP authentication fails, XWiki DB authentication takes over o Improved configuration parameters * Allow skin document attachments to override/provide templates * Tightened Wiki Syntax for strikethrough (XWIKI-1207), underline (XWIKI-1243), italics (XWIKI-1245) and strong (XWIKI-1248). * Verified XWiki on PostGreSQL 8.3 * Syntax Help Panel now opens the XWiki Syntax help from xwiki.org in a separate window + lots of other changes For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise13M2 Thanks -The XWiki dev team

16 years, 9 months

[xwiki-devs] [VOTE] XEclipse 1.1 Release

by Stéphane Laurière

Hi everyone, I'm forwarding you the mail below by Fabio, who currently has issue with his mail account. Here's my +1 Cheers Stéphane ---------- Dear all, as on the schedule I'd like to publicly release XEclipse 1.1 today (or tomorrow). These are the release notes: Bug [XECLIPSE-70] - Invalid text in delete dialog box [XECLIPSE-84] - Invalid version displayed when editing a page [XECLIPSE-87] - Cannot reconnect after disconnecting [XECLIPSE-89] - Login name with space Improvement [XECLIPSE-23] - Double-clicking on a tree node should open the node [XECLIPSE-73] - Add edit working set feature [XECLIPSE-77] - In preview panel, display the current URL and allow typing any URL [XECLIPSE-78] - In preview pane, add right click action to open the current URL in external browser [XECLIPSE-81] - Let user decide if they want to overwrite the server version rather than merge it I've partially initiated the release process otherwise I will not able, in case, to complete it at home (slow internet connection not suitable for transferring several MB of stuff) Let me know WDYT. Cheers, Fabio ----------

16 years, 9 months

[xwiki-devs] very fragmented javscript code

by Sachin Mittal

Hi, I have noticed that we have javascript files lying at several places in the xwiki web application. Further we seem to be using lot of javascript code developed by many independent OEM vendors. All this makes very hard to understand what all components are present in each js file. I would like to know why we use such fragmented set of js code, where as almost all the functionality could have been achieved by using single ajax toolkit and any additional work could have been done by using plugins on top of these tool kits. Every good ajax toolkits provides ways to extend and there is a good library of useful plugins found for each. In the xwiki application I have found at least 4 ajax toolkits: general toolkits found ---------------------- scriptaculous rico prototype yui Further there are lot of other js code also lying around. Again I am not sure if most of this is extension of one of the above toolkit or again these are independent set of javascript code (ajax/dhtml widgets). other js files found: --------------------- wysiwyg editor --------------- tiny_mce wiki_editor color picker --------------- chwScripts panels wizard ---------------- panelWizard miscelaneous --------------- ajaxSuggest lightbox tablefilterNsort usersandgroups tdwScripts wzToolTip Almost of the functionality present in these javascript file could have been built using just one ajax toolkit. Is there any attempt to clean this stuff. To start with I suggest to keep all the possible js code a one place, probably in scrips directory. Next we can replace code by using agreed toolkit. This way lot of extra js code would be removed and we would have much compact UI. Also can someone mention 1 liners as what is the purpose of each js file we use in xwiki. I am planning to redesign the complete UI using ext-js and jquery and it would help me a lot in knowing how can each be replaced with new component. Like after a lot of hit and trial I found that if I include ext-js and rico together, ext-js does not get loaded. So now I can replace whats being done by rico toolkit with ext-js/jquery equivalent. Let me know what are your opinions on this. Thanks Sachin ----- http://www.assembla.com/wiki/show/sachin_mittal about me: -- View this message in context: http://www.nabble.com/very-fragmented-javscript-code-tp15561552p15561552.ht… Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years, 9 months

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs