Hi devs,
For 2.0 syntax we make XWikiDocument.display() enclose the result in
{{html}}{{/html}} since it's supposed to generate html and that we
should not have to use {{html}}{{/html}} in the syntax when we call
$doc.display("somefield").
Now the issue is that public api Object and Document get() methods
does not return the value but call display. But users (and us) used to
access string value using $object.somefield instead of
$object.getProperty("somefield").getValue() which is the correct form
to access an object field value.
Because of this wrong use of display() we have a big change in the api
form user point so the question is what do we do ?
I can see the following solution:
1) it's not a real change in the API, user should use the right way.
It's ok like that.
2) we "optimize" XWikiDocument.display() by generating
{{html}}{{/html}} only when it's necessary (if the result really is
html)
2.a) if it contains "<" or ">"
2.b) when it's not a BaseStringProperty/NumberProperty/DateProperty
since theses properties does not really need to produce HTML
3) we clean the display result in Object/Document.get by removing the
{{html}}{{/html}} when the result does not really contains html (more
or less the same way to find it than 2))
WDYT ?
I'm +1 for 2.a) (I don't like b, i think the generic way is better)
since i don't think we can "change" the API even if it's not a real
change and this solution is not that much a hack, it makes display()
return cleaner anyway.
3) as the advantage of fixing only the problematic API but it's really
too crappy IMO
Hi,
Following the mail vote for enabling the 2.0 syntax in 1.9 final we
need to decide on our strategy for the XE XAR.
I propose that we only support 1 XAR (since I don't think we have the
manpower to support 2) and that this XAR is in 2.0 syntax.
For 1.9 we would only convert a few pages (listed in http://jira.xwiki.org/jira/browse/XWIKI-3605)
and in 2.0 we will continue till we have a full 2.0 syntax XAR.
We would also add a warning in the release notes for 1.9 listing the
pages that have been converted to 2.0 syntax.
Here's my +1
Thanks
-Vincent
The XWiki development team is pleased to announce the release of XWiki
Office 1.0 Milestone 3.
Go grab it at
http://www.xwiki.org/xwiki/bin/view/Main/Download#HXWikiOffice !**
XWiki Office is a XWiki.org project that provides integration between
Microsoft Office and XWiki servers.
For more information about XOffice go at: -
http://xoffice.xwiki.org/xwiki/bin/view/Main/
Main changes from version 1.0 Milestone 2:
- Basic XML-RPC support
- Opening, editing & publishing pages(XHTML content only)
- Downloading, opening, editing & uploading attachments
- Viewing the wiki in the Wiki Explorer
- Support for multiple encodings
- Improved wiki explorer
- Inhibited unnecessary Word messages & dialogs
- Better sync between Word instances
- Better & cleaner output
All active XWord M2 clients and snapshot instances will be automatically
updated to the latest version.
For details about this release see the Release Notes at:
- http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXOffice10M3
You can also view the roadmap here:
- http://xoffice.xwiki.org/xwiki/bin/view/Main/Roadmap#HVersion10Milestone3
Thanks
-The XWiki dev team
Hi,
I have a small doubt on how listener is implemented in
MediaWiki2XWikiExtension
Groovy Code Snippet --
http://code.xwiki.org/xwiki/bin/view/Extensions/MediaWiki2XWikiExtension
<%
import org.dom4j.io.SAXReader
import org.dom4j.*
import groovy.net.xmlrpc.*
import java.net.ServerSocket
import org.wikimodel.wem.mediawiki.MediaWikiParser
import org.wikimodel.wem.xwiki.*
class PruningPageHandler implements ElementHandler {
def proxy, token;
def counter = 0;
def max = 10000;
PruningPageHandler(proxy, token) {
this.proxy = proxy
this.token = token
}
def messages = []
public void onStart(ElementPath path) { }
public void onEnd(ElementPath path) {
def page = path.current
def title = page.elementText('title')
title = title.replaceAll(' ','_')
def id = page.elementText('id')
println(title+ '('+counter+')')
def revision = page.element('revision')
def revid = revision.elementText('id');
def revtext = revision.elementText('text');
def contributor = revision.element('contributor')
def username = contributor.elementText('username')
def index = revtext.substring(0,
Math.min(30,revtext.length())).toLowerCase().indexOf("redirect")
counter++;
if (counter < max && index < 0) {
revtext = revtext.replaceFirst("^-", "*");
revtext = revtext.replaceAll("__","")
revtext = revtext.replaceAll("[\\|][\\+]","")
def buffer = new StringBuffer()
buffer.append(revtext)
try {
*def reader = new StringReader(revtext);
def parser = new MediaWikiParser();
buffer = new StringBuffer()
def listener = new XWikiSerializer(buffer);
parser.parse(reader, listener);*
} catch (Exception e) {
println(e.getMessage())
}
def map = new HashMap()
map.put('content', buffer.toString())
map.put('modifier', username)
map.put('space','Wikipedia')
map.put('title',title)
try {
proxy.confluence1.storePage(token, map)
} catch (Exception e) {
println(e.getMessage())
}
}
page.detach() // prune the tree
}
}
%>
XWikiSerializer has a constructor with some class implementing IWikiPrinter
. But how come a StringBuffer is used here.
Am trying to simulate the same from a java application,and a fact that use
of StringBuffer fails here. How to create a listener object in that case.
Thanks and Best Regards,
Arun Reddy
Hi XWikiers,
Ludovic (XWiki's founder) and I (XWiki OSS product manager) will be at
JavaOne in San Francisco from Sunday, May 31 to Saturday, June 6 included.
We'd be really happy to meet and hook up with community members and XWiki
users from the far side of the world :-)
We'll be on OW2 booth from Tuesday, June 2 to Thursday, June 4 during the
conference. We'd be really happy to meet with users outside the timeframe of
the conference too... Simply let us know whether you're in the area and
we'll go grab a beer while feverishly discussing XObjects and XClasses ;-)
Also, Jim Grisanzio told me there would be many people from the OpenSolaris
community hanging around, so JavaOne will be the perfect opportunity for
other XWiki Users to discover what the OpenSolaris community has been doing
with XWiki of late (cf.
http://opensolaris.org/os/community/web/restructuring/preview/ for more
information on the topic).
Looking forward hearing from you guys (and gals !!),
Guillaume
--
Guillaume Lerouge
Product Manager - XWiki
Skype ID : wikibc
http://guillaumelerouge.com/
Hello guys,
I'm developing my first application in syntax 2 for a customer.
I started on a 1.8.2 XE and just moved on a 1.8 Snapshot (the latest
build - 05/16).
Here is my problem :
I have a little #if in a #foreach that works on my 1.8.2 but not on my
1.8 Snapshot and I totally don't know why.
#set($tradliste = $doc.getObjects("RimayCode.Traduction"))
#foreach($traduc in $tradliste)
#if($!traduc.langue == "Francais")
$!traduc.langue : $!traduc.traduction <br />
#end
#end
On my 1.8.2 the "foreach" returns all the objects with the good values,
and the "if" is a filter to display the items with a "Francais" value in
the "langue" field.
On my 1.8 Snapshot the "foreach" returns all the objects with the good
values, but the "if" doesn't work : not any result.
There is probably a pb, something new to do to create a test like this
but I can't see what...
"langue" is a static list with 4 options (1=Francais|2=Tibetain|3=...)
Any idea ?
Thomas
Hai...
I have some doubts regarding the Document Type Manager. I need some detail
specification regarding the Document Type Manager.This is what I realised
about it.
According to the mockups
http://incubator.myxwiki.org/xwiki/bin/view/Mockups/DocumentTypeManager
figure 1:
Is to define the class name and the space like the class editor wizard. But
I'm not clear about the other fields "Create Invitation Text" and "Grid
Invitation Text"
As in the heading of the mockup its says "DocumentTypeManagerEditType". I'm
not clear about from where the new document type is going to create. Is that
Mockup is missing.Or is it this UI also use in creating the document.If so I
feel that "Create this Document Type."button is missing.
figure2 & 3:
Use to add the properties for the new or existing document type and to
define the properties of properties.
I'm not clear about the next two tabs.
Grid Tab: Lists the documents with the same type.
Template Tab:Not clear about this tab.
This is the action flow I had realised.
1.User define a new document type by giving a name and space .(So document
manager creates the document based on the request paramerters)Or based on
the selection of the document types from the list shown in the left side,
Tab will shows the details regarding to the relevant selection.
2.Then user add the properties for the document type. Like in class editor
wizard.(After clicking the save button document type complete its
generation)
I'm not clear about the action flow of the other tabs. (Grid and Template
tab)
As an abstraction what I was feel that this is same as the class editor
wizard with different looking.Its like hiding the complxity of creating
classes and sheets. All the things will be automated using this wizard.If I
was wrong please correct me.
Currently I'm studying the "class editor wizard code,protoype and
smartclient".Hoping to get on to the design after I get the good
understanding about the document type manager.
Thank you.
--
~ Chathura Prabuddha Ganegoda~
Undergraduate,
Department of Computer Science & Engineering,
University of Moratuwa,
Sri Lanka.
http://gacpganegoda.blogspot.com/
Hi,
I want to change the color of links Login/Register wich is white to black
so i want to know wich css is responsible for this kind of links and what
should i do?
thank you very much
--
View this message in context: http://n2.nabble.com/Change-color-of-login-register-tp2932039p2932039.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
I have a java macro that requires the page to include an external js (e.g. jQuery) that works best if included in the head section of the document. Is there a way for a macro to trigger inclusion of resources like this to be included in the page header? In confluence this was done by having a #requireResource statement in a velocity template included by the macro.
How can this be done in xwiki?
--
Glenn
Hi developers,
I am currently working on getting the XWiki Watch trunk up to date working on a
1.8.x enterprise.
When I will be done with it, I would like to release a 1.1 M2 (to contain
currently fixed bugs + this update), based on 1.8.3 platform version, WDYT?
Here's my +1.
Happy coding,
Anca Luca