xwiki-devs September 2007

xwiki-devs@xwiki.org

35 participants
95 discussions

[xwiki-devs] [VOTE] Jerome Velociter as a committer

by Vincent Massol

Hi everyone, I'd like to propose voting Jerome Velociter as a XWiki committer. Jerome has been sending patches (see http://tinyurl.com/3cbz2j) for a long time now and his patches are good. I like the fact that in his latest patches he takes care of submitting nice code with nice javadocs ;) I propose we let him commit his own patches! Here's my +1. Note: For full disclosure, Jerome is working for XPertNet, the company behind the creation of XWiki. FWIW, out of the 24 committers (http://www.xwiki.org/xwiki/bin/view/Community/HallOfFame), 7 are working for XPertNet (including myself). Note that we're running XWiki as a meritocratic project (trying to follow the Apache rules as much as possible) and thus anyone can become a committer (see http:// www.xwiki.org/xwiki/bin/view/Community/Committership). The more the merrier! Thanks -Vincent

17 years, 2 months

[xwiki-devs] [Discussion] Designing the new Rendering/Parsing component/API

by Vincent Massol

Hi, I've started working on designing the new Rendering/Parsing components and API for XWiki. The implementation will be based on WikiModel but we need some XWiki wrapping interfaces around it. Note that this is a prerequisite for the new WYSIWYG editor based on GWT (see http://www.xwiki.org/xwiki/bin/view/Design/ NewWysiwygEditorBasedOnGwt). I've updated http://www.xwiki.org/xwiki/bin/view/Design/ WikiModelIntegration with the information below, which I'm pasting here so that we can have a discussion about it. I'll consolidate the results on that wiki page. Componentize the Parsing/Rendering APIs ================================== We need 4 main components: * A Scripting component to manage scripting inside XWiki documents and to evaluate them. * A Rendering component to manage rendering Wiki syntax into HTML and other (PDF, RTF, etc) * A Wiki Parser component to offer a typed interface to XWiki content so that it can be manipulated * A HTML Parser component (for the WYSIWYG editor) Different Syntaxes =============== Two possible solutions: 1. Have a WikiSyntax Object (A simple class with one property: a combox box with different syntaxes: XWiki Legacy, Creole, MediaWiki, Confluence, JSPWiki, etc) that users can attach to pages to tell the Renderers what syntax is used. If no such object is attached then it'll default to XWiki's default syntax (XWiki Legacy or Creole for example). 2. Have some special syntax, independent of the wiki syntaxes to tell the Rendered that such block of content should be rendered with that given syntax. Again there would be a default. XWiki Interfaces ============= * ScriptingEngineManager: Manages the different Scripting Engines, calling them in turn. * ScriptingEngine o Method: evaluate(String content) o Implementation: VelocityScriptingEngine o Implementation: GroovyScriptingEngine * RenderingEngineManager: Manages the different Rendering Engines, calling them in turn. * RenderingEngine o Method: render(String content) o Implementation: XWikiLegacyRenderingEngine (current rendering engine) o Implementation: WikiModelRenderingEngine * Parser: content parsing o HTMLParser: parses HTML syntax o WikiParser: parses wiki syntax o Implementation: WikiModelHTMLParser o Implementation: WikiModelWikiParser Open Questions: * Does WikiModel support a generic syntax for macros? * Is the Rendering also in charge of generating PDF, RTF, XML, etc? o I think so, need to modify interfaces above to reflect this. * The WikiParser needs to recognizes scripts since this is needed for the WYSIWYG editor. Use cases ======== * View page o ViewAction -- template -> ScriptingEngineManager.evaluate () -- wiki syntax -> RenderingEngineManager.render() ---> HTML, XML, PDF, RTF, etc * Edit page in WYSIWYG editor o Uses the WikiParser to create a "DOM" of the page content and to render it accordingly. NOTE: This is required since rendering in the WYSIWYG editor is different from the final rendering. For example, macros need to be shown in a special way to make them visible, etc. o Changes done by the user are entered in HTML. Note: it would be better to capture them so that they are entered in the "DOM". Is that possible? If not, then the HTMLParser is used to convert from HTML to Wiki Syntax but they're likely be some loss in the conversion. The advantage is the ability to take any HTML content and generate wiki syntax from it. This is my very earlier thinking but I wanted to make it visible to give everyone the change to 1) know what's happening and 2) suggest ideas. I'll refine this in the coming days and post again on this thread. Thanks -Vincent

17 years, 2 months

[xwiki-devs] [ANN] XWiki Enterprise 1.1.1

by Vincent Massol

The XWiki development team is pleased to announce the release of XWiki Enterprise 1.1.1. This is a bug fix release. It's a stable release. Everyone using XWiki Enterprise 1.1 should upgrade to it. Bugs fixed in 1.1.1: * Fullscreen doesn't work on IE6 or IE7 * Cache issue on new document creation in multilingual mode * Document change notification not sent for new documents * Code macro doesn't like groovy code * Backlinks are not working anymore * Cannot delete Space with a simple quote in its name * Lucene Plugin does not index creation or modification dates * Import with history throws exception from time to time * Panels Wizard not saving panels correctly For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise111 Thanks -The XWiki dev team

17 years, 2 months

[xwiki-devs] how to EMAIL a "document change notification" to all users

by M Faisal

Hello All, how can I email a "document change notification" to all users or a group of users, once a change is made in a xwiki document. Regards....

17 years, 2 months

[xwiki-devs] [VOTE] Release XE 1.1.1

by Vincent Massol

Hi, I'd like to release XE 1.1.1 ASAP. This is a bug fix release fixing the following since 1.1 has been released. It's mean to be a stable release for projects who cannot afford unstability by moving to 1.2M1 (not released yet either). Here are the stuff already fixed: * [XWIKI-1682] - Fullscreen doesn't work on IE6 or IE7 * [XWIKI-1729] - Cache issue on new document creation in multilingual mode * [XWIKI-1739] - Document change notification not sent for new documents * [XWIKI-1747] - Code macro doesn't like groovy code * [XWIKI-1766] - Backlinks are not working anymore * [XWIKI-1754] - Platform WAR should be generic and not dependent on database In addition I'd like to apply the following (I sent a VOTE email but not many responses so I'll just go ahead): * [XWIKI-1768] - Cannot delete Space with a simple quote in its name * [XWIKI-1770] - Add new searchDocuments() API that accepts named HQL queries I'll also apply the patch for this issue; * [XWIKI-1735] - Lucene Plugin does not index creation or modification dates I'll also remove a commit done in 11 that Ludovic asked me to remove: r4721 - <li>$item</li> + <li><a href="$xwiki.getURL($item)">$item</a></li> Apparently this is causing exceptions sometimes when importing with history. I'll do this work today. Here's my +1 to release ASAP after I've finished the work hilighted above. Thanks -Vincent

17 years, 2 months

[xwiki-devs] Error number 4001 in 4 :

by V. Harikrishnan Nair

Hello. I created a class and template using the Static List class property. But when I want to create a new document, the following error is shown Error number 4001 in 4: Error while parsing velocity page PMT.NewDoc Wrapped Exception: Invocation of method 'substring' in class java.lang.String threw exception java.lang.StringIndexOutOfBoundsException: String index out of range: -1 @ PMT.NewDoc4,26? I tried to use small lists and other variations but the error seems to come from an entirely different place... please help asap. regards, V. Harikrishnan Nair || Lokah Samastah sukhino bhavantu ||

17 years, 2 months

[xwiki-devs] Error when using the 'Level class' property

by V. Harikrishnan Nair

Hi all, I am getting the following error when I edited my class to add the Level Class property - Error number 0 in 11: Uncaught exception Wrapped Exception: com.xpn.xwiki.objects.meta.LevelsMetaClass cannot be cast to com.xpn.xwiki.objects.classes.PropertyClass com.xpn.xwiki.XWikiException: Error number 0 in 11: Uncaught exception Wrapped Exception: com.xpn.xwiki.objects.meta.LevelsMetaClass cannot be cast to com.xpn.xwiki.objects.classes.PropertyClass at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:163) 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:616) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1565) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1517) at org.mortbay.http.HttpServer.service(HttpServer.java:954) at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) Wrapped Exception: java.lang.ClassCastException: com.xpn.xwiki.objects.meta.LevelsMetaClass cannot be cast to com.xpn.xwiki.objects.classes.PropertyClass at com.xpn.xwiki.web.PropAddAction.action(PropAddAction.java:55) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:147) 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:616) at javax.servlet.http.HttpServlet.service(HttpServlet.java:689) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:830) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(WebApplicationHandler.java:821) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:471) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568) at org.mortbay.http.HttpContext.handle(HttpContext.java:1565) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:633) at org.mortbay.http.HttpContext.handle(HttpContext.java:1517) at org.mortbay.http.HttpServer.service(HttpServer.java:954) at org.mortbay.http.HttpConnection.service(HttpConnection.java:816) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:983) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:833) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:244) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534) Can anyone check this out ? regards, V. Harikrishnan Nair || Lokah Samastah sukhino bhavantu ||

17 years, 2 months

[xwiki-devs] urgent

by anuj sharma

Hi Everybody, Can anybody please tell me steps to disable WYSIWYG editor. Also please let me know how to upgrade xwiki.I have 1.1 milestone 4 and getting problem in its editor. Please ,Its Urgent.... ANUJ SHARMA. --------------------------------- Flying to Bangalore or Bhopal? Search for tickets here.

17 years, 2 months

[xwiki-devs] [VOTE] Add new XWiki.searchDocuments() API

by Vincent Massol

Hi, In order to properly fix the issues with escaping of single quote characters, I'd like to propose adding the following methods in *.api.XWiki: public List searchDocuments(String wheresql, List whereParams) throws XWikiException public List searchDocuments(String wheresql, int nb, int start, List whereParams) throws XWikiException The idea is to allow parametrized HQL queries in XWiki documents hence removing the issues with SQL escaping (For example this will allow solving http://jira.xwiki.org/jira/browse/XWIKI-1768). Here's my +1 Thanks -Vincent

17 years, 2 months

[xwiki-devs] changing default editor

by anuj sharma

Hi, Can we change default editor for users from WYSWYG to Wiki.If yes,then how can we do it? ANUJ SHARMA. --------------------------------- Unlimited freedom, unlimited storage. Get it now

17 years, 2 months

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs September 2007