Hi devs,
We didn't manage to release 5.3M1 on time (1 week delay..) and this
leaves only 1 week for M2 which is not enough for me to finish my work
on Solr (see http://www.xwiki.org/xwiki/bin/view/Roadmaps/WebHome ) so
I propose to take 1 week from RC1:
5.3M2: 11th of November (was 4th)
5.3RC1: 18th of November
5.3Final: 25th of November
WDYT?
Thanks,
Marius
The XWiki development team is proud to announce the availability of
XWiki 5.3 Milestone 1.
This is more a developer oriented release with new Extension Manager
APIs, an XWiki Enterprise Maven Archetype, XAR plugin improvements and
fold observation events but it also has a number of bug fixes (36) and
improvements (22) that the users will appreciate.
You can download it here: http://www.xwiki.org/xwiki/bin/view/Main/Download
Make sure to review the release notes:
http://www.xwiki.org/xwiki/bin/view/ReleaseNotes/ReleaseNotesXWiki53M1
Thanks
-The XWiki dev team
Hi,
i didnt find a documentation for creating an XObject to a Wiki-Page when a
new Page is created.
I think it must something like that, but who do i place it?
EntityReference entRef = doc.resolveClassReference("Space.WhateverClass");
int objectIndex = doc.createXObject(entRef, getXWikiContext());
BaseObject o = doc.getXObjects(entRef).get(objectIndex);
I know i can create a new object and page by velocity
(http://extensions.xwiki.org/xwiki/bin/view/Extension/Create+Page+With+Object),
but i want to add a default and predefined object when a user add a new
page.
Is there a way to do this from plugin-side?
Regards,
Matthias
--
View this message in context: http://xwiki.475771.n2.nabble.com/Create-Object-by-Default-with-a-new-Page-…
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hello, i programmed some Objects which can be related to any page. Then i
draw a graph (see an example at http://jsfiddle.net/7aMBr/3/). I programmed
it as a service which creates a html5-canvas and the javascript for the
drawing (Here a screen
http://s1.directupload.net/file/d/3421/3a4twrov_jpg.htm). Is is done with
{{velocity}}
$services.graph.calculate(640, 320, "Hierarchic")
{{/velocity}}
I defined some type-classes which can predefine the node or edge style, for
example the icon or the arrow layout (here a preview
http://s14.directupload.net/file/d/3421/hxkwe5bs_jpg.htm).
Here now my questions:
1. I use a defined id which uses Space.PageName.NodeLabel (ObjectUUID). This
references the Graph-Elements to others or the types. Everything works fine,
but now i realised that the change of the label in the object forces an
error in the ClassBuilder because all depended elements did't realize the
change. Is there a objectchange listener i can use for every change?
2. I programmed also a remove- and create-method in the ScriptService. As
you can see in one picture i defined a custom menubar. So i want to create a
link which can start a service. Is that possible?
{{velocity}}
$services.graph.removeNode("Main.Test.N2
(94c5fe2d-a92f-413e-ba1d-efc35bb7f84f)")
{{/velocity}}
Regards,
Matthias
--
View this message in context: http://xwiki.475771.n2.nabble.com/Object-Handling-tp7587724.html
Sent from the XWiki- Dev mailing list archive at Nabble.com.
Hi devs,
As you may know, I have taken over the work done by Thomas Delafosse
regarding security in XWiki, and in particular, a very good idea initially
proposed by Alex Busenius in the early days of the security mailing list in
June 2010, replacing PR by Signed Scripts ! A lot of discussions had
already been done around the subject, mainly on the security mailing list
and Thomas D. has written a very interesting PoC that demonstrate the
feasibility and also some drawbacks and issues with our initial concept.
I have therefore reviewed all those information, and I have try to draw a
conclusion that I am now sharing with you in an open design proposal:
http://dev.xwiki.org/xwiki/bin/view/Design/SignedScripts
I know you are all really busy with your stuffs and that this is not a
short document, but introduction of this change in XWiki will not be a
small event, and it may become really difficult to properly evolve if we
made it wrong. So I strongly insist that all of you read this proposal and
comment on any point that looks odd. For those who would not be at ease
with cryptographic matters, a small cryptographic introduction is also
included, so (I hope) you may understand the document.
There are still some open points in the proposal, marked TODO, on which I
would be please to receive your suggestions. I will continue to evolve the
proposal based on your comments, until we reach an acceptable solution, but
I also start the implementation.
Thanks in advance for your time,
--
Denis Gervalle
SOFTEC sa - CEO
Hi!
I have two jira issues that I need to fix for 5.3:
* http://jira.xwiki.org/browse/XWIKI-9558 - Rename {{workspaces /}} gadget
to {{wikis /}}
* http://jira.xwiki.org/browse/XWIKI-9491 - Rename
"WorkspaceInformationPanel" to "WikiInformationPanel"
The implementation is very trivial. In both cases I just rename a document,
and in one case I only change the field "name" of the WikiMacro.
But how do we handle upgrade?
A: If someone has used the {{workspaces /}} macro in her content, she will
not see the expected result anymore.
B: If WorkspaceInformationPanel is used in a layout, should we
automatically update this layout to use WikiInformationPanel?
Do we consider we should let the user fix this issues herself, or should we
provide an automatic solution to that? If so, how could we do?
Thanks for your help,
Louis-Marie.
Hi devs,
For content pages, the bottom tabs (comments, attachments, history,
information) are very useful features. But does it make sense to keep
those active for very technical pages?
For example, when viewing details about a tag, (Main/Tags?do=viewTag),
why should people be allowed to comment? They might wrongly think that
they're commenting on a tag, but that's just one complex page that
handles almost everything about tags, so a comment like "this tag has a
typo" doesn't help at all.
Other pages should have no bottom tabs as well: user directory, blog
category management, the whole scheduler space, share by email...
While the homepage is a technical page (by default), it does make sense
to leave the comments active, since it's the entry point for every user
(although I think that the messaging system is a better way to send
global messages).
IMO, the advantage is that we're hiding actions that are rarely useful,
but could be misused. The disadvantage is that we're breaking the
universality of the UI.
I'm +1 for hiding, fewer mis-usable features is always better.
--
Sergiu Dumitriu
http://purl.org/net/sergiu/
hmm seems we've missed the release date yesterday for 5.3M1… :(
We need a Release Manager to step forward for 5.3 ASAP. Any volunteer?
Reminder: here are the scores so far for RMs:
http://dev.xwiki.org/xwiki/bin/view/Community/ReleaseManagerRoster
Note that on http://dev.xwiki.org/xwiki/bin/view/ReleasePlans/WebHome we have:
* Marius: 11
* Thomas: 11
* Vincent: 11
* Caleb: 6
* Edy: 4
* Sergiu: 1
* Jerome: 1
* Denis: 1
* Fabio: 1
We need to release ASAP.
Thanks
-Vincent
PS: I'm on holiday starting tomorrow till the end of the week.