Hi,
XWiki has evolved a lot in the past year and new client apps were created.
Our current Xml-Rpc API is aligned to the Confluence 1.0 API
specification and hasn't been really enriched in a long time.
Since we have some distinct features like 'polyglot wiki' I propose to
create a new "xwiki2" method set to handle XWiki 2.0 method calls.
The new handler will be added to the Apache Xml-Rpc servlet properties file.
Proposed new xml-rpc methods(mostly needed for XEclipse, XOffice and XOO):
- parseFromHtml(String html, String syntax) : String
- render(String source, String syntaxId) : String
- cleanHtml(String dirtyHtml) : String
- add class ( http://jira.xwiki.org/jira/browse/XWIKI-3499 )
- getConfiguredSyntaxes
- getVirtualWikisNames
- getMacros, etc.
Proposed Xml-Rpc model extensions:
- Page
- syntaxId;
- ServerInfo/Wiki:
- isMultiWiki
- defaultSyntax
- encoding
WDYT?
Thanks,
Florin Ciubotaru
* one for the API: xwiki-configuration-api
* one for the default implementation: xwiki-configuration-default
The reason is that I'd like to implement
- XWikiPreferencesConfigurationSource
- SpacePreferencesConfigurationSource
- UserPreferencesConfigurationSource
And they'll need access to the DocumentAccessBridge
And I don't think it's a good idea to have that dep in the API.
WDYT?
Thanks
-Vincent
Hi Guys
I am able not able to instaal xwiki. I am using tomcat 6 on
ubuntu intrepid. Error I am gettting is
*exception*
javax.servlet.ServletException: com.xpn.xwiki.XWikiException: Error
number 3 in 0: Could not initialize main XWiki context
Wrapped Exception: Error number 3001 in 3: Cannot load class
com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager
from param xwiki.store.migration.manager.class
Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
Wrapped Exception: Hibernate Dialect must be explicitly set
org.apache.struts.action.RequestProcessor.processException(RequestProcessor.java:535)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:433)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:155)
com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:111)
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)
*root cause*
com.xpn.xwiki.XWikiException: Error number 3 in 0: Could not
initialize main XWiki context
Wrapped Exception: Error number 3001 in 3: Cannot load class
com.xpn.xwiki.store.migration.hibernate.XWikiHibernateMigrationManager
from param xwiki.store.migration.manager.class
Wrapped Exception: Error number 0 in 3: Exception while hibernate execute
Wrapped Exception: Hibernate Dialect must be explicitly set
com.xpn.xwiki.XWiki.getMainXWiki(XWiki.java:327)
com.xpn.xwiki.XWiki.getXWiki(XWiki.java:388)
com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:135)
com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:115)
org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
com.xpn.xwiki.wysiwyg.server.filter.ConversionFilter.doFilter(ConversionFilter.java:155)
com.xpn.xwiki.web.ActionFilter.doFilter(ActionFilter.java:111)
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)
Please help me to getover from this error.
-arvind
On Fri, Jun 26, 2009 at 21:41, Sergiu Dumitriu<sergiu(a)xwiki.com> wrote:
> tmortagne (SVN) wrote:
>> Author: tmortagne
>> Date: 2009-06-22 15:07:18 +0200 (Mon, 22 Jun 2009)
>> New Revision: 21405
>>
>> Added:
>> platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/IndentVelocityMacroFilter.java
>> platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/test/java/org/xwiki/rendering/internal/macro/velocity/filter/IndentVelocityMacroFilterTest.java
>> Log:
>> XWIKI-4018: Create an indentation velocity macro filter
>>
>> Added: platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/IndentVelocityMacroFilter.java
>> ===================================================================
>> --- platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/IndentVelocityMacroFilter.java (rev 0)
>> +++ platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/IndentVelocityMacroFilter.java 2009-06-22 13:07:18 UTC (rev 21405)
>
>> + /**
>> + * Match indentation spaces.
>> + */
>> + private static final Pattern INDENT_PATTERN = Pattern.compile("^[ \t]*", Pattern.MULTILINE);
>
> Replace with "^[ \t]++":
> - * means that it matches all line starts, doing a useless replace for
> the empty string. Thus the first +.
> - The second + is not that useful, since there's no backtracking to
> perform, but just to be explicit, it might save some ifs and elses.
Yes it's better, i did this regexp too quickly.
>
> --
> Sergiu Dumitriu
> http://purl.org/net/sergiu/
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
--
Thomas Mortagne
On Fri, Jun 26, 2009 at 19:53, Sergiu Dumitriu<sergiu(a)xwiki.com> wrote:
> tmortagne (SVN) wrote:
>> Author: tmortagne
>> Date: 2009-06-19 13:02:05 +0200 (Fri, 19 Jun 2009)
>> New Revision: 21347
>>
>> Modified:
>> platform/core/branches/xwiki-core-1.9/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/HTMLVelocityMacroFilter.java
>> platform/core/branches/xwiki-core-1.9/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/test/java/org/xwiki/rendering/internal/macro/velocity/filter/HTMLVelocityMacroFilterTest.java
>> Log:
>> XWIKI-3988: Default Velocity macro filter does not match directives on multiple lines
>> * add support for non UNIX newlines
>>
>> Modified: platform/core/branches/xwiki-core-1.9/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/HTMLVelocityMacroFilter.java
>> ===================================================================
>> --- platform/core/branches/xwiki-core-1.9/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/HTMLVelocityMacroFilter.java 2009-06-19 07:28:54 UTC (rev 21346)
>> +++ platform/core/branches/xwiki-core-1.9/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/HTMLVelocityMacroFilter.java 2009-06-19 11:02:05 UTC (rev 21347)
>
>> + * Match not UNIX new lines to replace them.
>> + */
>> + private static final Pattern MSNEWLINE_PATTERN = Pattern.compile("\\r\\n|\\r");
>
> I ran a quick test, and using \\r\\n? instead of \\r\\n|\\r is 40%
> faster. I think it's also safer, since '?' is by definition greedy,
> while '|' doesn't clearly indicate which of the two branches is
> executed, so it might replace just the \r with a new \n, leaving the old
> \n in place, thus yielding the wrong result.
>
>
> And I don't like this name, since \r is MacOS. You could call it
> ALTERNATIVE_LINE_ENDINGS.
Good ideas, i'm applying it.
>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
--
Thomas Mortagne
tmortagne (SVN) wrote:
> Author: tmortagne
> Date: 2009-06-21 11:52:13 +0200 (Sun, 21 Jun 2009)
> New Revision: 21370
>
> Modified:
> platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/ldap/XWikiLDAPConfig.java
> platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/render/DefaultVelocityManager.java
> platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/render/XWikiScriptContextInitializer.java
> Log:
> XWIKI-3942: Can't have the xwiki api Context as "context" binding in most of the JSR-223 engines
> * add "xcontext" binding and deprecate "context" in velocity
>
> Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/ldap/XWikiLDAPConfig.java
> ===================================================================
> --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/ldap/XWikiLDAPConfig.java 2009-06-20 16:35:07 UTC (rev 21369)
> +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/plugin/ldap/XWikiLDAPConfig.java 2009-06-21 09:52:13 UTC (rev 21370)
> @@ -134,7 +134,7 @@
> */
> public String getLDAPParam(String prefName, String cfgName, String def, XWikiContext context)
> {
Wrong commit.
> - String param = def;
> + String param = null;
>
> try {
> param = context.getWiki().getXWikiPreference(prefName, context);
>
> Modified: platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/render/DefaultVelocityManager.java
> ===================================================================
> --- platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/render/DefaultVelocityManager.java 2009-06-20 16:35:07 UTC (rev 21369)
> +++ platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/render/DefaultVelocityManager.java 2009-06-21 09:52:13 UTC (rev 21370)
> @@ -85,7 +85,9 @@
>
> // We put the com.xpn.xwiki.api.Context object into the context and not the com.xpn.xwiki.XWikiContext one
> // which is for internal use only. In this manner we control what the user can access.
"Deprecated" should be more than this. How about printing a warning in
the log when using $context?
> + // "context" binding is deprecated since 1.9.1
> vcontext.put("context", new Context(xcontext));
> + vcontext.put("xcontext", new Context(xcontext));
>
> // Make the Syntax Factory component available from Velocity.
> // TODO: We need to decide how we want to expose components in general and how to protect users from
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
vmassol (SVN) wrote:
> Author: vmassol
> Date: 2009-06-19 21:18:47 +0200 (Fri, 19 Jun 2009)
> New Revision: 21360
>
> Modified:
> platform/core/branches/xwiki-core-1.8/xwiki-xml/src/main/java/org/xwiki/xml/XMLUtils.java
> platform/core/branches/xwiki-core-1.8/xwiki-xml/src/test/java/org/xwiki/xml/internal/html/DefaultHTMLCleanerTest.java
> Log:
> XWIKI-4005: HMTL Cleaner should not expand empty elements for BR and HR in order to support IE6
>
>
> Modified: platform/core/branches/xwiki-core-1.8/xwiki-xml/src/main/java/org/xwiki/xml/XMLUtils.java
> ===================================================================
> --- platform/core/branches/xwiki-core-1.8/xwiki-xml/src/main/java/org/xwiki/xml/XMLUtils.java 2009-06-19 16:35:08 UTC (rev 21359)
> +++ platform/core/branches/xwiki-core-1.8/xwiki-xml/src/main/java/org/xwiki/xml/XMLUtils.java 2009-06-19 19:18:47 UTC (rev 21360)
> @@ -213,7 +225,16 @@
> format.setOmitDeclaration(omitDeclaration);
>
> XMLOutputter outputter = new XWikiXMLOutputter(format, omitDoctype);
> - return outputter.outputString(jdomDoc);
> + String result = outputter.outputString(jdomDoc);
> +
> + // Since we need to support IE6 we must generate compact form for the following HTML elements (otherwise they
> + // won't be understood by IE6):
> + for (String specialElement : OMIT_ELEMENT_CLOSE_SET) {
> + result = result.replaceAll(MessageFormat.format("<{0}></{0}>", specialElement),
Shouldn't this be something like "<{0}[^>]*+></{0}>"? I doubt that there
really is <img></img>, and if it is, it won't make much difference which
way it's written.
> + MessageFormat.format("<{0}/>", specialElement));
> + }
> +
> + return result;
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
tmortagne (SVN) wrote:
> Author: tmortagne
> Date: 2009-06-22 15:07:18 +0200 (Mon, 22 Jun 2009)
> New Revision: 21405
>
> Added:
> platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/IndentVelocityMacroFilter.java
> platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/test/java/org/xwiki/rendering/internal/macro/velocity/filter/IndentVelocityMacroFilterTest.java
> Log:
> XWIKI-4018: Create an indentation velocity macro filter
>
> Added: platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/IndentVelocityMacroFilter.java
> ===================================================================
> --- platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/IndentVelocityMacroFilter.java (rev 0)
> +++ platform/core/trunk/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/IndentVelocityMacroFilter.java 2009-06-22 13:07:18 UTC (rev 21405)
> + /**
> + * Match indentation spaces.
> + */
> + private static final Pattern INDENT_PATTERN = Pattern.compile("^[ \t]*", Pattern.MULTILINE);
Replace with "^[ \t]++":
- * means that it matches all line starts, doing a useless replace for
the empty string. Thus the first +.
- The second + is not that useful, since there's no backtracking to
perform, but just to be explicit, it might save some ifs and elses.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
tmortagne (SVN) wrote:
> Author: tmortagne
> Date: 2009-06-19 13:02:05 +0200 (Fri, 19 Jun 2009)
> New Revision: 21347
>
> Modified:
> platform/core/branches/xwiki-core-1.9/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/HTMLVelocityMacroFilter.java
> platform/core/branches/xwiki-core-1.9/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/test/java/org/xwiki/rendering/internal/macro/velocity/filter/HTMLVelocityMacroFilterTest.java
> Log:
> XWIKI-3988: Default Velocity macro filter does not match directives on multiple lines
> * add support for non UNIX newlines
>
> Modified: platform/core/branches/xwiki-core-1.9/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/HTMLVelocityMacroFilter.java
> ===================================================================
> --- platform/core/branches/xwiki-core-1.9/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/HTMLVelocityMacroFilter.java 2009-06-19 07:28:54 UTC (rev 21346)
> +++ platform/core/branches/xwiki-core-1.9/xwiki-rendering/xwiki-rendering-macros/xwiki-rendering-macro-velocity/src/main/java/org/xwiki/rendering/internal/macro/velocity/filter/HTMLVelocityMacroFilter.java 2009-06-19 11:02:05 UTC (rev 21347)
> + * Match not UNIX new lines to replace them.
> + */
> + private static final Pattern MSNEWLINE_PATTERN = Pattern.compile("\\r\\n|\\r");
I ran a quick test, and using \\r\\n? instead of \\r\\n|\\r is 40%
faster. I think it's also safer, since '?' is by definition greedy,
while '|' doesn't clearly indicate which of the two branches is
executed, so it might replace just the \r with a new \n, leaving the old
\n in place, thus yielding the wrong result.
And I don't like this name, since \r is MacOS. You could call it
ALTERNATIVE_LINE_ENDINGS.
Hi!
I've managed to implement the bidirectional converter as you suggested .
Thank you very much for your help. Now I have another problem :( .. I tried
to use the OpenOffice cleaner XWiki Component from the OpenOffice Importer
module
http://svn.xwiki.org/svnroot/xwiki/platform/core/trunk/xwiki-officeimporter…
My code is this one:
HTMLCleaner openOfficeHTMLCleaner = (HTMLCleaner)
ecm.lookup(HTMLCleaner.class,"openoffice");
ecm is an EmbeddableComponentManager instance.
And I have at Runtime the follow exceptions: http://pastebin.com/m1920f9cf
I've added openoffice module as dependency. Sorry I'm not very familiar with
XWiki Components. Has anybody an idea what I am missing?
Thanks a lot,
Cristina
Hi XWiki Devs & Users,
here's the current proposal for the XWiki Enterprise 2.0 roadmap. Please
give us your feedback about it and tell us whether you think we missed
anything important. Please note that this roadmap covers the next 3 months
of development work. Improvements not included here will be discussed at the
beginning of the next roadmap (in September 2009).
Shout if you think we forgot something ;-)
The list of tasks is divided in 3 parts: tasks we have already planned to
have people working on, tasks that we would like to complete during the
course of the release but have nobody planning to work on yet and tasks that
will have to be postponed until the next release cycle.
*Tasks with people already planned to work on:*
- Rendering (Thomas)
- Fix bugs
- Make sure the XWiki 2.0 syntax doesn't move any more once XE 2.0 is
out
- WYSIWYG editor (Marius, Anca)
- Fix bugs
- Implement search in the link insertion dialog box
- Improve the macro insertion dialog box
- CAPTCHA integration (Jérôme)
- Clustering (Thomas)
- Write a clustering component based on XWiki events
- Activity Stream integration (JV)
- Watchlist (JV)
- Rewrite the watchlist feature based on the activity stream
- Make the watchlist work in XEM
- Macros (Asiri)
- Write the velocity macro bridge
- Write a number of velocity macros
- UI Improvements (Caty)
- Blog
- User Profile
- Architectural Improvements (Vincent)
*Tasks with nobody planned to work on as of today:*
- Migrate all XWiki Enterprise pages to use the XWiki 2.0 syntax
(Collective effort?)
- Rewrite XWiki's Lucene Search backend (Sergiu?)
- Improve XWiki's default skin (Laurent?)
*Tasks that will have to be postponed to the next release cycle:*
- Application Manager
- Document Type Manager
- Invitation Manager
The current roadmap dates are the following:
- XE 2.0 M1: June 22
- XE 2.0 M2: July 13
- XE 2.0 M3: August 3
- XE 2.0 RC: August 17
- XE 2.0: August 31
Thanks in advance for your feedback.
Guillaume, on behalf of the XWiki Development Team
Hello Devs,
I have been examining Dan Miron's patches for
http://jira.xwiki.org/jira/browse/XWIKI-3313 &
http://jira.xwiki.org/jira/browse/XWIKI-2883 and they are working fine.
However I think there are few improvements / refactorings that should be
done before comitting the code. Most importantly, I would like us to agree
upon the xwiki-chart api and xwiki-chart-macro format.
xwiki-chart module
==============
In dan's implementation, the chart module is actually called
xwiki-jfreechart because it is dependant on the jfreechart api. However I
think we can extract a generic chart api from dan's implementation without
much of a trouble. In his implementation there are three interfaces:
* ChartGenerator
* DataSource
* DataSourceFactory
* PlotFactory
Out of these interfaces only PlotFactory is dependant on jfreechart.
IMO we can construct a generic chart api by making ChartGenerator &
DataSource interfaces component roles, hiding PlotFactory in an internal
package and getting rid of DataSourceFactory. So the final API would be
something like:
interface ChartGenerator {
File buildChart(DataSource dataSource, Map<String, Object>
parameters, File outputDirectory)
throws ChartGeneratorException;
}
And
interface DataSource {
// Usual tablemodel like api (from dan's implementation)
void init (params) // Initializes this datasource from the parameters
passed in, no need of a separate factory.
}
We can also go to a api / implementation approach with multiple modules as
in:
/platform/core/trunk/xwiki-chart
|
|-> xwiki-chart-api
|
|-> xwiki-chart-jfree
But I don't know if this is worth the trouble.
xwiki-chart-macro
=============
Currently the chart macro has a format like:
{{chart chartType="line" source="type:XDOM;
table_number:1;range:A1-C3;series:rows" title="line (xy_line_and_shape,
default)" width="640" height="480"/}}
I think we should change the "chartType" parameter to just "type" and the
source parameter would be changed like:
source="<id>|<params>"
here we will use the <id> part as the component hint for the corresponding
DataSource... and the <params> string can be anything specific for that
DataSource (so we don't put any restrictions).
For an example, we could have a datasource named "xdom" like:
source="xdom|document=Main.WebHome;table=someTableId;series=rows;hasHeaderRow=true;hasHeaderColumn=true"
We load the DataSource corresponding to "xdom" and let it initialize with
the parameters string.... (that's why i put a init() method inside
DataSource component role).
The rest of the parameters would be standard : title, height, width etc.
As a start we will have two types of DataSources: XDom and Inline (Already
there).
This is a quite big discussion and I don't know If I have explained myself
correctly. Please let me know what you think about this and how it can be
improved.
Thanks a lot.
- Asiri
The XWiki development team is pleased to announce the release of XWiki
Enterprise 2.0 Milestone 1.
Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download
It's the first milstone of the 2.0 version.
The main goal of 2.0 is to make XWiki fully Xwiki 2.0 syntax.
Main changes from 1.9:
* Lots of improvements and new features in the new WYSIWYG editor
* Lots of improvements and bugfixes in the rendering engine and
the syntax converter
* New Chart macro for XWiki 2.0 syntax
* New info, warning and error macros
* Improvements for the blog application
* New Search Interface
* New events for XWiki startup/shutdown
For more information see the Release notes at:
http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise20M1
Thanks
-The XWiki dev team
To late,
Please make any changes in the future to l10n. Because we cannot reload
changes from the Application Resources file. We can only do that once
intially.
After it's better to do it with l10n because we can handle reviews and
view changes needed.
It would be great if you could find somebody to run a "review" using the
review function on l10n. This allows then to setup a gradual review
system for new translations.
So, to summarize, l10n is now the reference for latvian translations and
we will regularly (before releases) commit changes done there in our
svn repository.
The current status is commited both in XWiki 1.9 branch and 2.0. So it
will be part of 1.9.1 and 2.0M2 (it was too late for 2.0M1)
Thanks for your contribution
Ludovic
Valdis Vītoliņš a écrit :
> Hmm...
> I found that minor updates are easier to make in resource file.
> Please use attached resource file
>
> Valdis
>
>
>> Translation in l10n.xwiki.org
>>
>> Valdis
>>
>>> I see you have put things on l10n.xwiki.org. Which one is the most up to
>>> date ? The file added to XE-444 or the translations on l10n.xwiki.org ?
>>>
>>> Ludovic
>>>
>>> Valdis Vītoliņš a écrit :
>>>
>>>> Thanks Ludovic!
>>>> It looks quite good.
>>>>
>>>> When I will do some updates, do I need to care about
>>>> http://l10n.xwiki.org/xwiki/bin/view/XE/ only?
>>>> I assume all other stuff to implement it in vanilla Xwiki you will do
>>>> "automagically"?
>>>>
>>>> Valdis
>>>>
>>>>
>>>>> To test it, copy your resource file to
>>>>>
>>>>> webapps/xwiki/WEB-INF/classes/ApplicationResources_lv.properties
>>>>>
>>>>> and restart your instance.
>>>>>
>>>>> Ludovic
>>>>>
>>>>> Valdis Vītoliņš a écrit :
>>>>>
>>>>>
>>>>>> Hello Ludovic!
>>>>>> I've prepared resource file and attached it to the bug in
>>>>>> http://jira.xwiki.org/jira/browse/XE-444
>>>>>>
>>>>>> Can you provide guide how can I import it in test instance?
>>>>>> (Do I need the latest XWiki version or ~ similar?)
>>>>>>
>>>>>> Thanks,
>>>>>> Valdis
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>> Attach us your initial resource file to the bug if you have one already
>>>>>>>
>>>>>>> Ludovic
>>>>>>>
>>>>>>> Valdis Vītoliņš a écrit :
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Thanks Ludovic!
>>>>>>>>
>>>>>>>> I've created task in jira, look at description in
>>>>>>>> http://jira.xwiki.org/jira/browse/XE-444
>>>>>>>>
>>>>>>>> 2 character ISO code for Latvian is lv.
>>>>>>>>
>>>>>>>> http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
>>>>>>>>
>>>>>>>> Valdis
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> Great ! This is very cool.
>>>>>>>>>
>>>>>>>>> Guillaume will add the language for you. What's the ISO code for latvian ?
>>>>>>>>> Concerning the initial loading of the resource file we have to do it.
>>>>>>>>> You can create a task on http://jira.xwiki.org and once it's commited
>>>>>>>>> we'll load the file in l10n.xwiki.org
>>>>>>>>>
>>>>>>>>> Ludovic
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Valdis Vītoliņš a écrit :
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> Hello Ludovic!
>>>>>>>>>> I'd like to participate in Xwiki translation to Latvian.
>>>>>>>>>> Guide in http://l10n.xwiki.org/xwiki/bin/view/L10N/ is too short.
>>>>>>>>>> It doesn't say how to add new language and how to upload resource file.
>>>>>>>>>>
>>>>>>>>>> Also by looking examples I understood non ASCII characters should be
>>>>>>>>>> written as escape sequences.
>>>>>>>>>> What is the most efficient/user friendly way to do it?
>>>>>>>>>>
>>>>>>>>>> Thanks in advance,
>>>>>>>>>> Valdis Vitolins
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
To test it, copy your resource file to
webapps/xwiki/WEB-INF/classes/ApplicationResources_lv.properties
and restart your instance.
Ludovic
Valdis Vītoliņš a écrit :
> Hello Ludovic!
> I've prepared resource file and attached it to the bug in
> http://jira.xwiki.org/jira/browse/XE-444
>
> Can you provide guide how can I import it in test instance?
> (Do I need the latest XWiki version or ~ similar?)
>
> Thanks,
> Valdis
>
>
>> Attach us your initial resource file to the bug if you have one already
>>
>> Ludovic
>>
>> Valdis Vītoliņš a écrit :
>>
>>> Thanks Ludovic!
>>>
>>> I've created task in jira, look at description in
>>> http://jira.xwiki.org/jira/browse/XE-444
>>>
>>> 2 character ISO code for Latvian is lv.
>>>
>>> http://en.wikipedia.org/wiki/List_of_ISO_639-1_codes
>>>
>>> Valdis
>>>
>>>
>>>> Hi,
>>>>
>>>> Great ! This is very cool.
>>>>
>>>> Guillaume will add the language for you. What's the ISO code for latvian ?
>>>> Concerning the initial loading of the resource file we have to do it.
>>>> You can create a task on http://jira.xwiki.org and once it's commited
>>>> we'll load the file in l10n.xwiki.org
>>>>
>>>> Ludovic
>>>>
>>>>
>>>> Valdis Vītoliņš a écrit :
>>>>
>>>>
>>>>> Hello Ludovic!
>>>>> I'd like to participate in Xwiki translation to Latvian.
>>>>> Guide in http://l10n.xwiki.org/xwiki/bin/view/L10N/ is too short.
>>>>> It doesn't say how to add new language and how to upload resource file.
>>>>>
>>>>> Also by looking examples I understood non ASCII characters should be
>>>>> written as escape sequences.
>>>>> What is the most efficient/user friendly way to do it?
>>>>>
>>>>> Thanks in advance,
>>>>> Valdis Vitolins
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost
Hi devs,
Here is a vote for the release of the first milestone of XWiki Enterprise 2.0.
The main goal of this release is to make XE fully 2.0 syntax and new WYSIWYG.
Among other things (72 fixed issues since 1.9 version) this release introduce:
- new char macro
- new info, warning, error macros
- new search UI
- components can receive XWiki startup/shutdown events
- it's now easier to change velocity engine properties and provide tools
And many other improvements and bugfixes.
Here is my +1
--
Thomas Mortagne
Hi devs,
The chosen filter (B2) is becoming more and more complex (I had to
code an almost complete velocity parser to support it correctly) and
after some more usability tests from Vincent it does not look so good
after all.
I coded a very simple parser (based on another of the ideas listed)
which only take care of indentation: basically it mean it remove all
first white spaces of each line. Vincent tested it and use ## to
aerate code and actually it looks pretty good. See
http://pastebin.com/m4a681aaf for example (the B2 based one is
http://pastebin.com/m17149f85) and most of all it's just one line a
code, a simple and quick regexp replaceAll.
So i propose to put the new filter as default filter.
WDYT ?
Here is my +1
On Thu, Jun 4, 2009 at 12:54, Vincent Massol<vincent(a)massol.net> wrote:
> Hi,
>
> We really need to close this before 1.9 final. After discussing it
> with Thomas here's what we propose:
>
> * Introduce a "mode" parameter to the Velocity macro. It's a cleaning mode.
> * Implement 2 modes for now:
> - the current mode where no cleaning is done
> - the B2 mode as defined below (using $nl and $sp)
> * Introduce a xwiki.properties config to define the default mode
> (which would be B2 by default for now)
>
> This allows users who are already using the 2.0 syntax today to keep
> using the current mode. It also allows us to introduce new cleaning
> mode later on (such as the one Ludovic wanted).
>
> WDYT?
>
> Here's my +1
>
> Thanks
> -Vincent
>
> PS: Please answer ASAP since 1.9 is supposed to be today and Thomas
> will need a few hours to implement this.
>
> On Thu, Apr 16, 2009 at 3:56 PM, Vincent Massol <vincent(a)massol.net> wrote:
>> Hi devs,
>> We need to come to a conclusion for handling New Lines(NL) and white spaces
>> (WS) in HTML and Velocity Macro.
>> If you remember from http://markmail.org/thread/mhqhxnz5twhev5se the current
>> problem is that we cannot indent scripts since WS and NL are meaningful.
>> I'd like to reiterate the proposal that was sent but not enough people voted
>> on it (only Thomas did).
>> A) For the HTML macro, we propose to make the following changes:
>> - strip NL/WS between elements (elements that don't accept CDATA)
>> - strip leading/trailing NL/WS for element content before passing them to
>> the wiki syntax parser
>> B) for the Velocity macro we have 2 choices I can think of:
>> 1) strip all leading spaces for all lines (but keep NL)
>> Note that this means that inside a velocity macro you wouldn't be able to
>> have a line break with the new line starting with spaces without escaping
>> the leading space with ~(space).
>> Note also that this means we will not be able to add extra new lines to
>> format the text nicely (since that would add new paragraphs) or split a
>> single line into several lines for extra readability. This is the case today
>> with the old syntax and it's a pain not to be able to aerate the text with
>> empty lines.
>> Ex:
>> some text
>> ~ next line #if (...) this goes on the same line #something(...) #end
>> This is a new paragraph
>> In this example notice that we need the velocity #if to be on the same line
>> since NL are significant.
>> 2) strip all leading spaces for all lines + remove all NL too.
>> This means we need to ensure we still have one space remaining between
>> "words" (same as HTML).
>> The user would use something like $nl and $sp to explicitely enter new lines
>> and spaces.
>> The advantage is that you control completely the formatting (no magic
>> anymore) at the cost of a little extra work (adding the $nl where
>> required).
>> Basically this means the same pros/cons as when you work with HTML where you
>> need to explicitly add <br/> when you want new lines.
>> Ex:
>> some text $nl
>> $sp next line
>> #if (...)
>> this goes on the same line
>> #something(...) <-- this is also on the same line
>> #end
>> $nl $nl
>> This a new paragraph
>> Note: I've aerated the text by putting extra new lines around the velocity
>> #if to show that it would work.
>> 3) Same as 1) + strip 1 NL (i.e. line breaks) and only allow "forced" line
>> breaks with "\\".
>> The exact algorithm is: if there's 1 NL remove it, if there's more than 1
>> leave them.
>> Ex:
>> some text\\
>> ~ next line
>> #if (...)
>> this goes on the same line
>> #something(...) <-- this is also on the same line
>> #end
>> This a new paragraph
>> I'm +1 for A)
>> For B) I think the most flexible is 2) but I'm wondering if it's too big a
>> change for our users or not. If not 2) then 3).
>> Thanks
>> -Vincent
>>
> _______________________________________________
> devs mailing list
> devs(a)xwiki.org
> http://lists.xwiki.org/mailman/listinfo/devs
>
--
Thomas Mortagne
When I go to the syntax page at http://platform.xwiki.org/xwiki/bin/view/Main/XWikiSyntax the contents are empty except for a message: Error number 4001 in 4: Error while parsing velocity page Main.XWikiSyntax Wrapped Exception: Failed to evaluate content with id XWiki Syntax.
The current page version is 38.1 and I see the same or similar behavior for versions 37.5, 37.4, 37.3, 37.2 and 37.1. The most recent version that works for me is 36.1.
There is a mention of this error in the devs mailing list archive as being fixed in 2008: http://markmail.org/message/wiqd7lrcpre3lo2b
Regards,
Kevin
Hi XWikiers,
LinuxTag will be held in Berlin from tomorrow to saturday onwards. I'll be
there to talk about XWiki.
>From their website ( http://www.linuxtag.org/ ):
"LinuxTag is the most important place for Linux and open source software in
Europe. In 2009, the 15th LinuxTag presents news for professional users,
decision makers, developers, beginners and the Linux community - from 24th
until 27th June on the Fairground in Berlin."
If you're around please come say hello and ask all your questions about
XWiki ;-)
Guillaume