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

by Thomas Mortagne

On Mon, Dec 8, 2008 at 12:20 PM, Bartłomiej Radziszewski <br(a)debian.linux.pl> wrote: > Hi Thomas, > > Thx for replay. > > Yep I know about synchronization ldap to xwiki database. > I want to use xwiki like central managment system for other services like > for example SVN (For authentication to the SVN i'm using htaccess with > ldap). You mean synchronize the other way ? When something change in XWiki, it has to modify LDAP entry ? XWiki does not support this by default. But you can do that with a script or a plugin if know JAVA and a little LDAP apis. In your plugin you can register for receive notifications of user modifications and then connect to LDAP and modify the LDAP user entry. See http://platform.xwiki.org/xwiki/bin/view/DevGuide/Notifications In the meantime you can add an "idea" or "improvement" entry on http://jira.xwiki.org/jira/browse/XWIKI about "Synchronizing any XWiki user modification back to LDAP server" or something like that but I think you will have to wait quite a long time to see it unless someone provide a good patch/contrib for it ;) > > So.. after user registration i need to have the same user in ldap. > > It is posible in xwiki? > > Thx and Greetings! > Bart >> >> Hi Bart, >> >> 2008/12/6 Bartłomiej Radziszewski <br(a)debian.linux.pl>: >> >>> >>> hello Thomas, >>> >>> If i good know You are developing all ldap staff in xwiki. >>> I'm searching simple way how to synchronize xwiki users to ldap >>> posixAccount.. i need only login, pass and mail attributes.. do You have >>> idea how to make it? >>> >> >> You don't need to synchronize LDAP login or pass, the LDAP >> authenticator validate login/pass directly on LDAP server then the >> informations like name, mail etc... are synchronized with XWiki. >> >> To define which information to synchronize between LDAP and XWiki user >> profile you can use xwiki.authentication.ldap.fields_mapping. >> >> For example : xwiki.authentication.ldap.fields_mapping=email=mail if >> you want only email. >> >> See >> http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication#HGeneric… >> for more details on LDAP authentication configuration. >> >> >>> >>> Thanks and Greetings, >>> Bart >>> >>> -- >>> Bartłomiej Radziszewski >>> mobile: +48 509 561 540 >>> e-mail: br(a)debian.linux.pl >>> JID: br(a)debian.linux.pl >>> ICQ: #305569725 >>> >>> >>> >>> >> >> >> >> > > > -- > Bartłomiej Radziszewski > mobile: +48 509 561 540 > e-mail: br(a)debian.linux.pl > JID: br(a)debian.linux.pl > ICQ: #305569725 > > > -- Thomas Mortagne

16 years, 9 months

1
0
0 0

Re: [xwiki-devs] xwiki database -> ldap

by Thomas Mortagne

Hi Bart, 2008/12/6 Bartłomiej Radziszewski <br(a)debian.linux.pl>: > hello Thomas, > > If i good know You are developing all ldap staff in xwiki. > I'm searching simple way how to synchronize xwiki users to ldap > posixAccount.. i need only login, pass and mail attributes.. do You have > idea how to make it? You don't need to synchronize LDAP login or pass, the LDAP authenticator validate login/pass directly on LDAP server then the informations like name, mail etc... are synchronized with XWiki. To define which information to synchronize between LDAP and XWiki user profile you can use xwiki.authentication.ldap.fields_mapping. For example : xwiki.authentication.ldap.fields_mapping=email=mail if you want only email. See http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication#HGeneric… for more details on LDAP authentication configuration. > > > Thanks and Greetings, > Bart > > -- > Bartłomiej Radziszewski > mobile: +48 509 561 540 > e-mail: br(a)debian.linux.pl > JID: br(a)debian.linux.pl > ICQ: #305569725 > > > -- Thomas Mortagne

16 years, 9 months

1
0
0 0

[xwiki-devs] [VOTE] XMLRPC API Extension

by Fabio Mancinelli

Dear all, since the 1.7 release has been delayed I would like to propose to add 3 methods to the XMLRPC API. These methods are the following: /* Returns a list of all the changed pages starting from a given date */ public List<XWikiPageHistorySummary> getModifiedPagesHistory( Date date, Integer numberOfResults, Integer start, Boolean fromLatest) /* These are basically equivalent to original store functions, but if checkVersion is true then a check of the current page version is done before storing the page/object. This check handles the case in which a page has been modified by somebody else after the last getPage or getObject */ public XWikiPage storePage(XWikiPage page, Boolean checkVersion) public XWikiObject storeObject(XWikiObject object, Boolean checkVersion) Besides their usefulness there is also a rationale: these are actually a need for the Concerto project and it would be great to have them already available in 1.7. >From the implementation point of view, these methods have almost no impact on the current code base and they are purely an extension (i.e., no pre-existing critical code has been touched) Here it is my +1 -Fabio

16 years, 9 months

7
11
0 0

[xwiki-devs] users registration problem

by antoine Seilles

Hi My xwiki works fine. But when users try to register, they have the following error. The registry is allright but it seems that mail can't be send. A problem occured while trying to service your request. Please contact the support if this happens again. Detailed information: Error number 10003 in 10: Exception while sending email from antoineseilles(a)gmail.com to [Ljava.lang.String;@b5d71 Wrapped Exception: Connection refused com.xpn.xwiki.XWikiException: Error number 10003 in 10: Exception while sending email from antoineseilles(a)gmail.com to [Ljava.lang.String;@b5d71 Wrapped Exception: Connection refused at com.xpn.xwiki.XWiki.sendMessage(XWiki.java:3347) at com.xpn.xwiki.XWiki.sendMessage(XWiki.java:3370) at com.xpn.xwiki.XWiki.sendValidationEmail(XWiki.java:3284) at com.xpn.xwiki.XWiki.sendValidationEmail(XWiki.java:3249) at com.xpn.xwiki.XWiki.createUser(XWiki.java:3203) at com.xpn.xwiki.web.RegisterAction.action(RegisterAction.java:41) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:215) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:115) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:94) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:287) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:619) Wrapped Exception: java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at java.net.Socket.(Socket.java:366) at java.net.Socket.(Socket.java:180) at org.apache.commons.net.DefaultSocketFactory.createSocket(DefaultSocketFactory.java:53) at org.apache.commons.net.SocketClient.connect(SocketClient.java:162) at com.xpn.xwiki.XWiki.sendMessage(XWiki.java:3320) at com.xpn.xwiki.XWiki.sendMessage(XWiki.java:3370) at com.xpn.xwiki.XWiki.sendValidationEmail(XWiki.java:3284) at com.xpn.xwiki.XWiki.sendValidationEmail(XWiki.java:3249) at com.xpn.xwiki.XWiki.createUser(XWiki.java:3203) at com.xpn.xwiki.web.RegisterAction.action(RegisterAction.java:41) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:215) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:115) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:94) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.web.SavedRequestRestorerFilter.doFilter(SavedRequestRestorerFilter.java:287) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:112) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:874) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:619)

16 years, 9 months

3
5
0 0

[xwiki-devs] [VOTE] Make DocumentAccessBridge#getDocumentContent(String documentName) use the current language in place of the default one

by Thomas Mortagne

Hi devs, I was looking for issue http://jira.xwiki.org/jira/browse/XWIKI-2892 (Include Macro should support including pages matching the current language) and i'm thinking it's not the include macro work to take care of the language. Include macro use the DocumentAccessBridge to acces document content and I think unless you don't explicitly specify that you want the default language content DocumentAccessBridge#getDocumentContent(String documentName) should return the content for the current language. It's more consistent with DocumentAccessBridge#etDocumentContent(String documentName, String language) IMO and anyway except for very specific needs I don't see the point of manipulating the content of the document's default language for components. WDYT ? Here is my +1 Thanks, -- Thomas Mortagne

16 years, 9 months

4
4
0 0

[xwiki-devs] [Proposal] New Line behavior in the new WYSIWYG editor

by Guillaume Lerouge

Hi, In the current implementation of the WYSIWYG editor, when adding content, pressing the return key creates a new paragraph () and pressing shift-return creates a new line ( ). In the wiki editor, the following behavior was discussed and implemented ( http://www.mail-archive.com/devs@xwiki.org/msg04436.html ) : *>> So typing a new line in the wiki editor will result in a br tag in the >> corresponding HTML? And two consecutive new lines in wiki editor will >> result in a new paragraph? >> >> yep exactly.* After talking with our project managers and gathering their feedback from the way customers use our tool, I think that implementing a similar behavior in the WYSIWYG editor would be more intuitive for users : - Pressing return once generates a new line - - Pressing return twice generates a new paragraph - In order for this behavior to be transparent for the user, the CSS setting the height of blank space between 2 paragraphs should set it a one line's height. In order to respect user intentions on the screen, we would also need to handle the case where the user inputs, say, 4 return keypresses in a row. We could handle it by inputting tags and having the last tag be a paragraph : Some text some other text Another option would be to go the way of recent editors such as Google Docs and ditch in favor of tags only. So there are 3 options: 1. Keep the current implementation (*pros:* it's working this way already, *cons:* it's not what our project managers say our users expect) 2. Use 1 return keypress for and 2 return keypresses for (*pros: * it's more intuitive for users, it keeps the semantic meaning of , * cons:* it takes time to implement and we're already lacking time) 3. Input only everywhere, all the time (*pros:* that's what modern editors do, *cons:* additional work, we lose the semantic meaning of ) I'm +1 for option 2. Guillaume -- Guillaume Lerouge Product Manager - XWiki Skype ID : wikibc http://blog.xwiki.com/

16 years, 9 months

5
4
0 0

[xwiki-devs] [VOTE][UI] WYSIWYG Image dialogs

by Jean-Vincent Drean

Hi XWikiers, I've made mockups for the WYSIWYG Image dialogs, you can see them at : http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorInterface#HImage Votes for internal image insertion : 1) Image size ------------------ In the mockup you can see a dropdown allowing to set some predefined sizes to the image (inspired by google docs). We could rely on the browser's image resizing feature for this and drop this setting. I'm in favor of keeping it (see my votes below) since it allow to keep size consistency between multiple images (screenshots for example) in the same page. Also, IE and FF have this resizing feature but we can't assume that it'll be the same for all the browsers we will target in the future. 2) Image size option --------------------------- a) Allow to edit only the image width (guarantee that the image width/height ratio won't be affected by the resize). b) Allow to edit both image width and height. 3) Text flow --------------- I think it's a must have but since it'll rely on a touchy parameter I prefer that we vote for it. Generated wiki syntax example : [[image:awsome.jpg||style="float:right"]] Notes : - for the moment using this will cause issues with titles, see : http://www.jean-vincent.org/xwiki/bin/view/Main/Image - I'm not sure that we'll be able to combine position center + text flow. 4) Preview -------------- I've put an image preview in the mockup, we've multiple choices: a) Drop it since it makes the dialog heavy. a) Keep it stupid simple, the image is represented by a placeholder and the 6 possible states are "prerecorded" (could be images). d) Make it an advanced preview, the image is the selected image, the preview takes the size of the image into account (by calculating what the selected size would look like compared to the page content in a predefined resolution, like 1024x768). Votes for external image insertion : 5) Number of wizard steps ----------------------------------- Like for the link insertion dialogs we have a major difference between internal and external stuff. We could : a) Have 2 steps to be consistent with the internal insertion. First step : image URL, second step : image options. b) Ease the edit work and have all the settings in the same screen, this is how I've presented it in the mockup. My votes : 1) +1 2) +1 for a) 3) +1 4) +1 for d) if possible 5) +1 for b) Thanks, JV.

16 years, 9 months

8
13
0 0

[xwiki-devs] [VOTE][UI] WYSIWYG Link dialogs

by Jean-Vincent Drean

Hi, Now that we have agreed on the "wiki explorer" thing I've updated the link proposal accordingly. The mockups are available at : http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorInterface#HLink I've tried to spot all the items that we'd want to discuss but I may have forgotten some of them, feel free to raise new discussions. Votes for internal links : 1) Flyover ------------- Do we want to be able to easily set the link title ? Wiki syntax : [[current selection>>Main.WebHome||title="flyover"]] Votes for external links : 2) Number of wizard steps ----------------------------------- We have a major difference between external and internal links, pasting a URL doesn't require a fancy editor. We could : a) Have 2 steps to be consistent with the internal insertion. First step : link URL, second step : link options. b) Ease the edit work and have all the settings in the same screen (URL + options), this is how I've presented it in the mockup. My votes : 1) +1 2) +1 for b) JV.

16 years, 9 months

8
9
0 0

Re: [xwiki-devs] [xwiki-notifications] r14570 - in platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki: . web

by Sergiu Dumitriu

tmortagne (SVN) wrote: > Author: tmortagne > Date: 2008-12-05 12:29:12 +0100 (Fri, 05 Dec 2008) > New Revision: 14570 > > Modified: > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/XWiki.java > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web/XWikiRequestProcessor.java > Log: > XWIKI-2824: Support multiwiki using path urls and not host urls > * make action name for servlet configurable ("wiki" by default) > > + > + private String getProperty(String propertyKey, String defaultValue) > + { > + if (this.config == null) { > + // Make XWikiRequestProcessor own configuration loader since XWiki of Configuration component are not > + // initialized at this time This part should be synchronized, to prevent parallel initialization. Or, load it in a constructor or static block (making the config static, also). You could also comment this setting in xwiki.cfg.vm -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 9 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r14565 - in platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki: api doc

by Vincent Massol

On Dec 5, 2008, at 7:55 AM, sdumitriu (SVN) wrote: > Author: sdumitriu > Date: 2008-12-05 07:55:30 +0100 (Fri, 05 Dec 2008) > New Revision: 14565 > > Modified: > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/api/ > Document.java > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/doc/ > XWikiDocument.java > Log: > XWIKI-2549: Make Document.addAttachment public > Done. > > > Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/ > api/Document.java > =================================================================== > --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/api/ > Document.java 2008-12-05 04:30:58 UTC (rev 14564) > +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/api/ > Document.java 2008-12-05 06:55:30 UTC (rev 14565) > @@ -20,7 +20,6 @@ > */ > package com.xpn.xwiki.api; > > -import java.io.ByteArrayOutputStream; > import java.io.IOException; > import java.io.InputStream; > import java.util.ArrayList; > @@ -32,7 +31,6 @@ > import java.util.Vector; > > import org.apache.commons.fileupload.FileItem; > -import org.apache.commons.io.IOUtils; > import org.apache.commons.lang.StringUtils; > import org.suigeneris.jrcs.diff.DifferentiationFailedException; > import org.suigeneris.jrcs.rcs.Version; > @@ -1721,7 +1719,7 @@ > filename = filename.replaceAll("\\+", " "); > > if ((data != null) && (data.length > 0)) { > - XWikiAttachment attachment = > addAttachment(filename, data); > + XWikiAttachment attachment = > this.doc.addAttachment(filename, data, getXWikiContext()); > getDoc().saveAttachmentContent(attachment, > getXWikiContext()); > // commenting because this was already done by > addAttachment > // getDoc().getAttachmentList().add(attachment); > @@ -1736,39 +1734,26 @@ > return nb; > } > > - protected XWikiAttachment addAttachment(String fileName, > InputStream iStream) throws XWikiException, IOException > + public Attachment addAttachment(String fileName, InputStream > iStream) > { > - ByteArrayOutputStream bAOut = new ByteArrayOutputStream(); > - IOUtils.copy(iStream, bAOut); > - return addAttachment(fileName, bAOut.toByteArray()); > + try { > + return new Attachment(this, > this.doc.addAttachment(fileName, iStream, getXWikiContext()), > getXWikiContext()); > + } catch (XWikiException e) { > + // TODO Log the error and let the user know about it > + } catch (IOException e) { > + // TODO Log the error and let the user know about it I don't like this... Don't we have a solution to handle it in a better way? With the current solution scripts calling this method need to check for null and take action if null which I'm pretty sure none care about so it'll silently fail. The best current solution is probably to store the result in the "error" variable in the Velocity context (we have a variable for this) and modify a main template to check for errors in page execution and if there are redirect to an error page printing them. The script should then be able to do a check for null itself and have the ability to clear the error if it can handle it gracefully so that the error page doesn't appear for the user. WDYT? [snip] Thanks -Vincent

16 years, 9 months

2
1
0 0

[xwiki-devs] Fwd: [ANNOUNCE] Apache Velocity 1.6

by Vincent Massol

fyi. Seems like we can now refactor our ubespector to use Sergiu's patch that was committed in Velocity 1.6. Well done Sergiu :) Also this is very intriguing: "macro libraries to be programatically included when calling template.merge(...)" -Vincent Begin forwarded message: > From: "Nathan Bubna" <nbubna(a)apache.org> > Date: December 3, 2008 7:04:03 AM CEST > To: announce(a)apache.org, announcements(a)jakarta.apache.org, dev(a)velocity.apache.org > , user(a)velocity.apache.org > Subject: [ANNOUNCE] Apache Velocity 1.6 > > The Apache Velocity Team announces the immediate availability of the > of Apache Velocity Engine 1.6. This release is fully compatible with > the previous release and includes significant improvements in > performance, stability and features. > > Apache Velocity is well-known in the Java field as a lightweight, > easy-to-use templating library for creating dynamic web sites and > performing other text-generation tasks. > > Much work in this release has gone to making significant improvements > in the memory usage and speed of Velocity. Apart from this, a number > of small parser bugs were fixed, tempate/line/column information in > error messages has been corrected and made consistent, and many new > features were added. Many of the latter are listed below: > > * There are three new directives: > - #evaluate takes a single string of VTL as an argument and renders > it. > - #define is a cousin of #macro, that lets define a reference that > represents the body of the directive, which is then evaluated when the > reference is used. > - #break lets you exit a #foreach loop early. > > * There are reflection improvements: > - You may now call JDK 1.5 vararg methods on your tools and other > references with variable arguments. > - You can put a static utility class directly into the context and > be able to call its methods; no instance necessary. (e.g. > context.put("Math", java.util.Math.class)) > - If you have a reference that is an array, you can now call > fixed-length list methods on it. (e.g. $array.size() and > $array.get($index) ) > - There is now support for chaining and linking Uberspect > implementations to simplify custom introspection. > > * The underlying Velocimacro code has been refactored to allow: > - Much, much better performance than Velocity 1.5 > - #parse( 'mymacros.vm' ) to work as expected!! > - macro libraries to be programatically included when calling > template.merge(...) > - users to configure a velocimacro.max.depth property (to limit > recursion et al) > > * CommonsLogLogChute and ServletLogChute are now available without > including VelocityTools > > * The StringResourceLoader has undergone major refactoring to make it > much more user-friendly and flexible. > > * There is now an automatic $velocityHasNext reference in #foreach > loops > > * You can now configure the connection timeout for URLResourceLoader > (JDK 1.5+ only) > > Documentation Velocity 1.6 can be found here: > http://velocity.apache.org/engine/releases/velocity-1.6/ > > The change log is here: > http://velocity.apache.org/engine/releases/velocity-1.6/changes-report.html > > Apache Velocity 1.6 can be downloaded here: > http://velocity.apache.org/download.cgi > > For the Apache Velocity Team > Nathan Bubna

16 years, 9 months

3
2
0 0

Re: [xwiki-devs] [xwiki-notifications] r14548 - in platform: core/trunk/xwiki-core/src/main/java/com/xpn/xwiki web/trunk/standard/src/main/webapp/WEB-INF

by Sergiu Dumitriu

tmortagne (SVN) wrote: > Author: tmortagne > Date: 2008-12-04 18:31:07 +0100 (Thu, 04 Dec 2008) > New Revision: 14548 > > Modified: > platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/XWiki.java > platform/web/trunk/standard/src/main/webapp/WEB-INF/web.xml > Log: > XWIKI-2824: Support multiwiki using path urls and not host urls > * fix action name > > Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/XWiki.java > + String[] vhi = uri.split("/"); > + if (vhi.length > 2 && vhi[2].equals("wiki")) { > + host = vhi[3]; > + } > } This is wrong. This will break http://www.boston.com/yourtown/wiki/Newton/ /wiki/ should be configurable. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 9 months

2
7
0 0

Re: [xwiki-devs] [xwiki-notifications] r14542 - in platform: core/trunk/xwiki-core/src/main/java/com/xpn/xwiki core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/api core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/user/impl/xwiki core/trunk/xwiki-co

by Thomas Mortagne

On Fri, Dec 5, 2008 at 4:20 AM, Sergiu Dumitriu <sergiu(a)xwiki.com> wrote: > tmortagne (SVN) wrote: >> Author: tmortagne >> Date: 2008-12-04 14:00:49 +0100 (Thu, 04 Dec 2008) >> New Revision: 14542 >> >> Log: >> XWIKI-2824: Support multiwiki using path urls and not host urls >> >> Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/XWiki.java >> =================================================================== >> + public String getServletPath(String wikiName, XWikiContext context) >> + { >> + // unless we are in virtual wiki path mode we should return null >> + if (!context.getMainXWiki().equalsIgnoreCase(wikiName) && "1".equals(Param("xwiki.virtual.usepath", "0"))) { >> + String database = context.getDatabase(); >> + try { >> + context.setDatabase(context.getMainXWiki()); >> + XWikiDocument doc = getDocument(getServerWikiPage(wikiName), context); >> + BaseObject serverobject = doc.getObject("XWiki.XWikiServerClass"); >> + if (serverobject != null) { >> + String server = serverobject.getStringValue("server"); >> + return "wiki/" + server + "/"; >> + } >> + } catch (Exception e) { >> + LOG.error("Failed to get URL for provided wiki [" + wikiName + "]", e); >> + } finally { >> + context.setDatabase(database); >> + } >> + } >> + > > This means that only struts is accepted for this kind of virtual > servers? What about xmlrpc, webdav, wysiwg, gwt, and the incoming REST? It's really difficult to have a full support of url based multiwiki with the current tricky way of handling URLs (it's already pretty difficult to support only struts without breaking anything...). We really need the unique component based entry point we discussed and get rid of struts. > > -- > Sergiu Dumitriu > http://purl.org/net/sergiu/ > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Thomas Mortagne

16 years, 9 months

2
3
0 0

Re: [xwiki-devs] [xwiki-notifications] r14553 - in platform/web/trunk/wysiwyg/src/main: java/com/xpn/xwiki/wysiwyg/client java/com/xpn/xwiki/wysiwyg/client/editor java/com/xpn/xwiki/wysiwyg/client/plugin/image java/com/xpn/xwiki/wysiwyg/client/plugin/image/ui java/com/xpn/xwiki/wysiwyg/server resources/com/xpn/xwiki/wysiwyg/client/editor resources/com/xpn/xwiki/wysiwyg/public

by Sergiu Dumitriu

Marius Dumitru Florea wrote: > Sorry. I'm keeping only the important part this time. > > Marius Dumitru Florea wrote: >> Look at the end, >> >> lucaa (SVN) wrote: >>> Author: lucaa >>> Date: 2008-12-04 21:46:47 +0100 (Thu, 04 Dec 2008) >>> New Revision: 14553 >>> > > [snip] > >>> -div.clear { >>> +.xImagePreviewSelected img { >>> + border: solid 2px #FFA500; >>> +} >>> + >>> +div.clearfloats { >> You either use the clearfloats class from the current skin or make the >> selector specific to the image plugin. >> >>> clear: both; >>> + display: none; >> Does this work? From what I know if you set the display to none the DOM >> elements matched by the selector are not displayed thus they are not >> part of the flow thus they don't affect the flow. >> It doesn't. As you said, display: none makes clear to be ignored. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 9 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r14553 - in platform/web/trunk/wysiwyg/src/main: java/com/xpn/xwiki/wysiwyg/client java/com/xpn/xwiki/wysiwyg/client/editor java/com/xpn/xwiki/wysiwyg/client/plugin/image java/com/xpn/xwiki/wysiwyg/client/plugin/image/ui java/com/xpn/xwiki/wysiwyg/server resources/com/xpn/xwiki/wysiwyg/client/editor resources/com/xpn/xwiki/wysiwyg/public

by Vincent Massol

Hi Marius, On Dec 5, 2008, at 8:24 AM, Marius Dumitru Florea wrote: > Look at the end, I don't see anything at the end. I think a possibly better way is to snip whatever is not relevant to your answer with [snip] :) > lucaa (SVN) wrote: >> Author: lucaa >> Date: 2008-12-04 21:46:47 +0100 (Thu, 04 Dec 2008) >> New Revision: 14553 >> >> Added: >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/plugin/image/ImageConfig.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/plugin/image/ui/FileUploadForm.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/plugin/image/ui/ImageParametersPanel.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/plugin/image/ui/ImageSelector.java >> Removed: >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/plugin/image/ui/HasImage.java >> Modified: >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/WysiwygService.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/WysiwygServiceAsync.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/WysiwygServiceAsyncCacheProxy.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/editor/Strings.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/plugin/image/ImageHTMLGenerator.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/plugin/image/ImagePlugin.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/plugin/image/ui/ImageDialog.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> client/plugin/image/ui/ImagePreviewWidget.java >> platform/web/trunk/wysiwyg/src/main/java/com/xpn/xwiki/wysiwyg/ >> server/DefaultWysiwygService.java >> platform/web/trunk/wysiwyg/src/main/resources/com/xpn/xwiki/ >> wysiwyg/client/editor/Strings.properties >> platform/web/trunk/wysiwyg/src/main/resources/com/xpn/xwiki/ >> wysiwyg/public/Wysiwyg.css >> Log: >> XWIKI-2875: Allow to add images in the document >> * Added mechanism for image parameter setting: size, alt text, >> positioning >> * Improved UI, browser support, image data model [snip] Thanks -Vincent

16 years, 9 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r14542 - in platform: core/trunk/xwiki-core/src/main/java/com/xpn/xwiki core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/api core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/user/impl/xwiki core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/web core/trunk/xwiki-core/src/test/java/com/xpn/xwiki/test core/trunk/xwiki-core/src/test/java/com/xpn/xwiki/web skins/trunk/albatross/src/main/resources/albatross web/trunk/standard/src/main/webapp web/trunk/standard/src/main/weba

by Sergiu Dumitriu

tmortagne (SVN) wrote: > Author: tmortagne > Date: 2008-12-04 14:00:49 +0100 (Thu, 04 Dec 2008) > New Revision: 14542 > > Log: > XWIKI-2824: Support multiwiki using path urls and not host urls > > Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/XWiki.java > =================================================================== > + public String getServletPath(String wikiName, XWikiContext context) > + { > + // unless we are in virtual wiki path mode we should return null > + if (!context.getMainXWiki().equalsIgnoreCase(wikiName) && "1".equals(Param("xwiki.virtual.usepath", "0"))) { > + String database = context.getDatabase(); > + try { > + context.setDatabase(context.getMainXWiki()); > + XWikiDocument doc = getDocument(getServerWikiPage(wikiName), context); > + BaseObject serverobject = doc.getObject("XWiki.XWikiServerClass"); > + if (serverobject != null) { > + String server = serverobject.getStringValue("server"); > + return "wiki/" + server + "/"; > + } > + } catch (Exception e) { > + LOG.error("Failed to get URL for provided wiki [" + wikiName + "]", e); > + } finally { > + context.setDatabase(database); > + } > + } > + This means that only struts is accepted for this kind of virtual servers? What about xmlrpc, webdav, wysiwg, gwt, and the incoming REST? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 9 months

1
0
0 0

[xwiki-devs] Help with waging WAR ;)

by Juergen Lorenz Simon

Hi, I've created an XWiki plugin, which uses a whole lot of frameworks to do it's job, including WebObjects, ProjectWonder and some of our own frameworks. It's running fine in Eclipse. When I package the resulting webapp from the workspace's server area (.metadata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps/xe- debug-web) into a war file, I can deploy the result in a webserver. Now I would like to be able to package the xe-debug-web from the command line or Eclipse into a .war. However: When I invoke mvn clean package (or any other mvn command for that matter) inside the xe-debug-web project directory, i get the following error message: mvn package : [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: xe-debug-web:xe-debug-web Reason: Parent: null:xwiki-web-standard:war:null of project: xe-debug- web:xe-debug-web has wrong packaging: war. Must be 'pom'. for project xe-debug-web:xe-debug-web [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Parent: null:xwiki- web-standard:war:null of project: xe-debug-web:xe-debug-web has wrong packaging: war. Must be 'pom'. for project xe-debug-web:xe-debug-web at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun .reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39) at sun .reflect .DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java: 430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.ProjectBuildingException: Parent: null:xwiki-web-standard:war:null of project: xe-debug-web:xe-debug-web has wrong packaging: war. Must be 'pom'. for project xe-debug-web:xe- debug-web at org .apache .maven .project .DefaultMavenProjectBuilder .assembleLineage(DefaultMavenProjectBuilder.java:1377) at org .apache .maven .project .DefaultMavenProjectBuilder .buildInternal(DefaultMavenProjectBuilder.java:821) at org .apache .maven .project .DefaultMavenProjectBuilder .buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506) at org .apache .maven .project .DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365) ... 11 more [INFO] ------------------------------------------------------------------------ [INFO] Total time: < 1 second [INFO] Finished at: Wed Dec 03 18:41:14 CET 2008 [INFO] Final Memory: 1M/2M [INFO] ------------------------------------------------------------------------ I don't know what to do about this message. So my thought was to create a Maven goal in Eclipse from the run configurations. However, the 'war' goal seems to be quite fussy about the layout, and the xe-debug-web project layout does not to be satisfactory: ... [INFO] [war:war] [INFO] Packaging webapp [INFO] Assembling webapp[xe-debug-web] in [/Users/simon/Projects/ Kontrast/MavenWorkspace/xe-debug-web/target/xe-debug-web-1.6.1] [INFO] Processing war project [INFO] Copy webapp webResources[/Users/simon/Projects/Kontrast/ MavenWorkspace/xe-debug-web/target/maven-shared-archive-resources] to[/ Users/simon/Projects/Kontrast/MavenWorkspace/xe-debug-web/target/xe- debug-web-1.6.1] [INFO] Copy webapp webResources[/Users/simon/Projects/Kontrast/ MavenWorkspace/xe-debug-web/target/maven-shared-archive-resources/META- INF] to[/Users/simon/Projects/Kontrast/MavenWorkspace/xe-debug-web/ target/xe-debug-web-1.6.1] [INFO] Copy webapp webResources[/Users/simon/Projects/Kontrast/ MavenWorkspace/xe-debug-web/src/main/webInfResources] to[/Users/simon/ Projects/Kontrast/MavenWorkspace/xe-debug-web/target/xe-debug-web-1.6.1] Exception in thread "main" java.lang.IllegalStateException: basedir / Users/simon/Projects/Kontrast/MavenWorkspace/xe-debug-web/src/main/ webInfResources does not exist at org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java: 550) ... Since both approaches failed, I need some advice on how to package the xe-debug-web into a proper WAR file again. All pointers much appreciated, J.L.Simon

16 years, 9 months

2
13
0 0

[xwiki-devs] Unsubscribe

by Deepak24 S

Hi, Please unsubscribe my Email ID from this blog.I dnt want further mails. regards, Deepak Sharma ASE Tata Consultancy Services ,Phase IV, Gurgaon Gurgaon - 122001,Haryana India Cell:- 9911502444 Mailto: deepak24.s(a)tcs.com Website: http://www.tcs.com ____________________________________________ Experience certainty. IT Services Business Solutions Outsourcing ____________________________________________ =====-----=====-----===== Notice: The information contained in this e-mail message and/or attachments to it may contain confidential or privileged information. If you are not the intended recipient, any dissemination, use, review, distribution, printing or copying of the information contained in this e-mail message and/or attachments to it are strictly prohibited. If you have received this communication in error, please notify us by reply e-mail or telephone and immediately and permanently delete the message and any attachments. Thank you

16 years, 9 months

2
1
0 0

[xwiki-devs] XWiki Translation Tool: looking for volunteers

by Ludovic Dubost

Hi all, We have setup the new translation tool on a production server and we are now looking for volunteers to give it a test drive and start updating the translations of the XWiki Core. The new tool is at http://l10n.xwiki.org You will need to create an account on this wiki (the xwiki.org does not yet work, but we plan to connect it to xwiki.org using the new Open ID implementation done in the Summer of Code). The first thing that we can start with is working on the empty translations. For example here are the pages to modify the empty translations for a few languages German: http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources?action=viewempty… French: http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources?action=viewempty… Spanish: German: http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources?action=viewempty… Polish: German: http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources?action=viewempty… You can view the full list at German: http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources and click on "View Empty" next to your favorite language. Currently there is no locking mecanism, so I hope we won't have conflicts will working on this. The good thing is that of course everything is kept in wiki style so with versioning. Let us know who can test drive the application. Make sure you are putting in real translations since we want to use the result for real ! Once we start getting some updates I'll document the review process so that we can also start doing that. For reviews we will 'elect' reviewers that will have the right to review. If you are volunteer for review, please tell us by responding to this email. Thanks Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

16 years, 9 months

2
1
0 0

[xwiki-devs] [VOTE] Postpone XE 1.7 release

by Jean-Vincent Drean

Hi, I'd like to suggest to postpone the release by a couple of days. The reason is -- as explained in a previous email -- that in its current state the WYSIWYG 2.0 : 1) Is still causing IE6 crashes on key press (Blocker). It has been preventing testing on this browser during the last couple of weeks and last commit from Marius doesn't help (again, IE is a pain). See http://jira.xwiki.org/jira/browse/XWIKI-2915 2) Can't be considered as a valid replacement of the WYSIWYG 1.0 since the image and table plugins are deactivated by default (XWIKI-2917 and XWIKI-2916). See pending issues here : http://tinyurl.com/6hsaqg If it's ok for everyone I'd like to define december 5th as the new release date for XE 1.7 ? Here's my +1. Thanks, JV.

16 years, 9 months

5
4
0 0

[xwiki-devs] [VOTE][UI] WYSIWYG Wiki Explorer (SUMMARY)

by Jean-Vincent Drean

General wiki explorer UI : 3) Three +1 4) Five +1 (WINNER) Tree add options : A) Four +1 (WINNER) B) One +1 C) Three +1 JV. On Thu, Nov 27, 2008 at 7:37 PM, Jean-Vincent Drean <jv(a)xwiki.com> wrote: > On Tue, Nov 25, 2008 at 5:05 PM, Jean-Vincent Drean <jv(a)xwiki.com> wrote: >> In a previous thread we've discussed about how to add a link in the >> WYSIWYG editor, and more generally, how to browse the wiki from a >> WYSIWYG dialog box (See http://markmail.org/message/tyxrcr24w3n6m2pn >> for more details). >> >> After some thinking and a discussion with Laurent Lunati, I'd like to >> suggest a 3rd way of browsing the wiki from the WYSIWYG: an enhanced >> tree menu. >> > > After some more thinking and discussion with Laurent Lunati I've made > a mockup of a 4th wiki explorer : > http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorWikiExplorer#H42… > > It combines the best of the tree and wizard proposals : > > * Easy to use: users are guided throughout the process, one action at a time > * The dialog size is fixed, action buttons are always at the same > position on screen > * The dialog doesn't looked oversized compared to the WYSIWYG > * Small footprint: can be used even on low resolution displays > * Since it's a wizard it's highly extensible > * Scalable : we can have multiple wikis + spaces (even a space hierarchy) > * Allow to display parent/child relationships between pages (thus > allowing to handle a lot of pages in a space) > * Allows the user to see where he is currently located in the wiki > (default selection) > > Here's my +1 for 4). > > ps: I consider that the discussion about the position of the add page > / add spaces buttons is not over. > > JV. >

16 years, 9 months

1
0
0 0

[xwiki-devs] Need roadmap for new WYSIWYG UI needed

by Vincent Massol

Hi there, With XE 1.7 we're going to release some features that don't have the final planned UI (insert link, image, macro, table for example). We're still discussing the final UI designs but I'd like that we get started doing 2 things: * prepare a roadmap for finishing their definition and set milestones so that we don't drag on forever * prepare an implementation roadmap with dates and with whom will be able to implement them Re the implementation roadmap I feel it would be good to (iteratively) release the UIs in 1.7.x releases (1.7.1, 1.7.2, etc) as fast as we can. The reason is that we initially wanted to have them in 1.7 final and we're late since the wysiwyg implementation took longer than planned. Waiting for 1.8 would be too long I think. Ideally IMO it would be good if we could have most of them done before December end. We need to know if that's possible and define a roadmap. WDYT? Thanks -Vincent

16 years, 9 months

2
3
0 0

[xwiki-devs] notifications "start configuration"?

by Paul Libbrecht

Hello xwikiers, the page at http://platform.xwiki.org/xwiki/bin/view/DevGuide/Notifications is really nice and shows a real nice pearl of XWiki. I did similarly and my notifier seems to run smoothly. I would like to know, however, what is the way to make sure that a notifier (an implementation of XWikiDocChangeNotificationInterface) is running at every restart of our XWiki. I tried to add the fullname of either the velocity (the "starter") or the Groovy pages into that line and restarting but my notifier didn't seem to have been running after that. What is the correct way? It should definitely be documented at the pircbot page. thanks in advance paul

16 years, 9 months

3
7
0 0

Re: [xwiki-devs] [xwiki-users] [VOTE] XEclipse release

by Paul Libbrecht

Fabio, I would be eager to test it, especially with the changing java architectures on the mac nowadays (basically the 64-bit/32-bit switch). As soon as you have a release candidate I'll give it a try. paul Le 26-nov.-08 à 17:23, Fabio Mancinelli a écrit : > Dear all, > > I would like to release XEclipse soon. During the last days I've fixed > many of the outstanding bugs thanks also to the effective > collaboration > of Eduard Moraru who provided a lot of patches and I think that now > XEclipse is pretty stable, usable and functional. > > This release incorporates a lot of features that have been implemented > during the last months. In particular a better integration with the > Eclipse ecosystem, object editor, translation management, page > history, > syntax highlighting and completion (thanks to the work done by Malaka > during the last GSoC and Venkatesh) and many other improvements. > > There are still many things to do but I think that it's a priority to > have a new version out asap in order to have more feedbacks from users > and to build upon it. > > Due to some previous engagements I think I will be able to release > it on > Friday or during the weekend.

16 years, 9 months

2
3
0 0

[xwiki-devs] WYSIWYG development status

by Jean-Vincent Drean

Hi, the new WYSIWYG is still under heavy development, here are some estimations of its features completion : * Standard features : 75%. Implemented : bold, italics, underline, strikethrough, subscript, superscript, unordered list, ordered list, titles (h1,h2,etc), indent, outdent, ruler, special chars. Remaining : alignment, verbatim, quote, definition lists, custom parameters like (% style="color:red" %). Some bugs left too. * Link : 90%. Allow internal/external/email link insertion. Missing options. No automated tests. * Image : 40%. Allow image insertion from any document, image uploading and resizing. Still buggy. Missing options. No automated tests. * Table : 50%. Doesn't work with IE. Missing options. No automated tests. * Macro : 0%. * Import: 0%. In its current state the WYSIWYG 2.0 : - can't be considered as a valid replacement of the WYSIWYG 1.0 (image and table plugins deactivated by default), - was causing IE6 crashes after a few seconds of use, this has been fixed by the last commit from Marius a few minutes ago but has been preventing IE6 testing for a couple of weeks. I'm suggesting to postpone XE 1.7 release by a few days, I'll write another email about this. Note that the UI of all those features (buttons, dialog boxes, etc) is not final since the discussion about their ergonomics is still ongoing. See the "Need roadmap for new WYSIWYG UI needed" email. Thanks, JV.

16 years, 9 months

3
2
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs