The idea is to keep Albatross the default skin in 1.3M2 but package
the Toucan skin so that users can easily use it and test it more.
Then in 1.3RC1 we would make Toucan the default skin. We should keep
the Albatross skin too I think and only remove it in 1.4 (i.e. users
would download it from code.xwiki.org to get it).
WDYT?
Thanks
-Vincent
Right now this interface isn't used anywhere. It's a burden. It has
lots of cruft methods, etc.
I hereby propose to send it to the guillotine!
In the future it'll be reborn as component interface when we split
that mammoth XWiki java class into components.
Here's my +1
Thanks
-Vincent
Hi,
I'm proposing a reorg of our tools releases. Here are the proposed
changes:
1) Release each tool module separately from the others. This means
creating one jira project per tools module. Since there'll be plenty
I'll also create a new jira category called "XWiki Tools"
2) Remove the build-tools/ directory and move all tools directly in
xwiki-platform-tools
3) Rename some tools as a consequence of 2). Here are the renames I
propose:
build-verifications --> xwiki-verification-resources
build-xar-handlers --> xwiki-xar-handlers
build-xar-plugin --> xwiki-xar-plugin
build-xmldoc-update-plugin --> xwiki-xmldoc-update-plugin
shared-tests --> xwiki-shared-tests
xwiki-configuration-resources (no change)
xwiki-jetty-resources (no change)
packager --> xwiki-packager-plugin
4) Remove cryptpasswords and instead move it to the sandbox
Let me know quickly what you think since I'd like to make those
changes in the coming hours so that Jerome can release what he needs
to XWiki Watch.
Thanks
-Vincent
Well you can see progress of my experimentation based on xwiki platform
there: http://apeiron.lirmm.fr:9006/xwiki
I develop a plugin to annotate documents and use it to debate.
And I still have some questions:
How to add an url to an annotation (my plugin) ?
Indeed we want to add annotation to annotation. And so we need to open
an annotation as a document in xwikicontent div.
Currently, to see the annotation form you need to get comment right.
I have set this right allowed to xwikiallgroup.
But, if you don't have the edit right, you cannot submit the form.
Submitting the form call the method : $doc.getURL('objectadd')
So how can i resolve this problem?
Maybe creating a new method to add annotation? But how to do that?
And last question, where can i see wiki editor comportment?
Thank for your time
Antoine SEILLES
I have an AnnotationPluginApi.java class and i have a method to get all
the annotations associated to a document:
public Vector getAnnotations(Document doc){
return doc.getObjects("AnnotationClass");
}
Now i'd like to have a method to get all the annotations associated to a
document having a specific value specified in parameters for one field :
public Vector getAnnotations(Document doc, String field, String value)
Wich should return all the annotations having the value "value" for the
field "field".
How to do that?
In fact, how to access fields of my objects "AnnotationClass"?
Thank for your time.
Ps: in AnnotationPlugin i have this method:
public BaseClass getAnnotationClass(XWikiContext context) throws
XWikiException {
XWikiDocument doc;
XWiki xwiki = context.getWiki();
boolean needsUpdate = false;
try {
doc = xwiki.getDocument("XWiki.AnnotationClass", context);
} catch (Exception e) {
doc = new XWikiDocument();
doc.setSpace("XWiki");
doc.setName("AnnotationClass");
needsUpdate = true;
}
BaseClass bclass = doc.getxWikiClass();
bclass.setName("XWiki.AnnotationClass");
needsUpdate |= bclass.addTextField("author", "Author", 30);
needsUpdate |= bclass.addDateField("created", "Created",
"dd/MM/yyyy");
needsUpdate |= bclass.addTextAreaField("comment", "Comment", 40, 5);
needsUpdate |= bclass.addTextAreaField("selection", "Selection",
40, 5);
needsUpdate |= bclass.addTextAreaField("reformulation",
"Reformulation", 40, 5);
needsUpdate |= bclass.addNumberField("begin", "Begin", 100,
"integer");
needsUpdate |= bclass.addNumberField("end", "End", 100, "integer");
needsUpdate |= bclass.addTextField("emotion", "Emotion", 30);
needsUpdate |= bclass.addTextField("judgmentUniversel",
"JudgmentUniversel", 30);
needsUpdate |= bclass.addTextField("judgmentParticulier",
"JudgmentParticulier", 30);
needsUpdate |= bclass.addTextField("domain", "Domain", 30);
String content = doc.getContent();
if ((content == null) || (content.equals(""))) {
needsUpdate = true;
doc.setContent("1 AnnotationClass");
}
if (needsUpdate)
xwiki.saveDocument(doc, context);
return bclass;
}
From: Evelina Slatineanu [mailto:evelyne24@gmail.com]
Sent: Thursday, February 07, 2008 5:05 PM
To: 'XWiki Developers'
Subject: Lightbox proposals
Hello all,
Due to the fact that we want to make the lightbox a standard feature for
xwiki and the current lightbox used for Users & Groups management is not
quite complete (and the code needs to be cleaned a little bit), I was
thinking that we need a "multi-purpose" lightbox that could support Ajax but
still work fine without it (which is not the case of the current one), that
could load media files (for instance .swf, quicktime movies etc), .pdf,
pages containing frames, inline content (no Ajax) etc. Therefore we would
need a nicer lightbox.
So, there are 2 proposals from me:
1. To spend some time improving the current lightbox to support all
the above (which will mean practically re-writing it FROM SCRATCH and will
take some time - one, two weeks or more, depending of my time, as my
priority now is Chronopolys)
2. Use one of the existing lightboxes that I found on the Internet
(customized for xwiki), like:
- LightWindow (using prototype and scriptaculous), which is quite
complete and MIT - licenced
http://www.wildbit.com/labs/modalbox/
- A lightbox based on yui library (which is already in the
albatross and probably will remain.is quite a nice library imo), like the
one below, which has the nice feature of being "movable":
http://test.thecodecentral.com/demos/lightboxrev/lightbox.html
- ModalBox, another lightbox using prototype + scriptaculous, which
looks nice but I am not sure about the licence
http://test.thecodecentral.com/demos/lightboxrev/lightbox.html
and there are more out there on the web :P
Personaly, I think the one with most features is LightWindow, but that would
mean to keep scriptaculous framework .
So, I would like your opinions on this matter (ideas, suggestions, maybe
some other lightbox features you would like to have as standard in xwiki
etc)
Thanks,
Evelina
Good day community.
Bridge between xwiki and legacy relational databases can be interesting for
some applications.
I just wrote plugin for this: http://xwikisql.gradsoft.ua
(Hope, this plugin can be integrated into general xwiki infrastructure)
Regards!
--
Ruslan Shevchenko
GradSoft. http://www.gradsoft.ua
Hello devs,
In a previous mail, I said I was going to release platform-tools/ (see
http://tinyurl.com/2khge6). There were a last minute change as Vincent
proposed me to integrate in that release a maven plugin I wrote for XWiki
Watch. The plugin is now integrated, it allows to attach files to xwiki
XML documents within the build process.
Will release this afternoon.
Jérôme.
Is there a right level required to call the method $doc.getURL('objectadd')?
I have a form showed only to user with comment right..
But when they submit this form, if they don't have an admin or maybe
edit right, they have an error "...not allowed to access this page...".
So how can i call the method $doc.getURL('objectadd') or something that
would have the same effect but with only comment right?
Thank you
Hi,
I think it would be better to publish the plugin API javadoc on the
XWiki site, instead of manually putting some pseudo java interface in a
{code} block. We do the same for the platform-core, by uploading the
generated javadoc jar and using the zipexplorer plugin to show the index
page.
Sergiu