Vincent Massol wrote:
On Sep 21, 2009, at 4:42 PM, Vincent Massol wrote:
On Sep 21, 2009, at 4:33 PM, Asiri Rathnayake wrote:
Hi,
On Mon, Sep 21, 2009 at 6:07 PM, Vincent Massol
vinc...@massol.net wrote:
I'd also like to know if we can support the use case of having a
normal table for
BTW, it would be good that the callback supports the JSON given by our
REST API natively.
I think the base versions (like {{documents}}, {{objects}}) should
consume REST resources.
We could decide that the livetable only consumes REST, but that would be
a strong limitation compared to what
Hi XWikiers,
as promised I posted a blog article listing the results of the XWiki
Features Survey. You can read it here:
http://www.xwiki.org/xwiki/bin/view/Blog/Features+Survey+Results
We'll use the results during the discussion about the XE 2.1 roadmap.
I've also included the original result
Hi,
On Sun, Sep 27, 2009 at 1:27 PM, Jerome Velociter jer...@xwiki.com wrote:
Vincent Massol wrote:
Hi there,
I'd like to start a overhaul of the xwiki.org home page + a first
level navigation overhaul.
Today:
* Home page = list the different products
* First level nav = the
On Sep 28, 2009, at 2:57 PM, Guillaume Lerouge wrote:
Hi,
On Sun, Sep 27, 2009 at 1:27 PM, Jerome Velociter jer...@xwiki.com
wrote:
Vincent Massol wrote:
Hi there,
I'd like to start a overhaul of the xwiki.org home page + a first
level navigation overhaul.
Today:
* Home page =
Hi,
No: in this case the admin should remove the officeimporter app.
The only drawback I see is that until we have an application manager it's a
bit harder for the Admin to bring the application back after deleting it
(he
needs to re-install it instead of simply changing a configuration
ping? :)
- Asiri
On Tue, Sep 1, 2009 at 3:13 PM, Asiri Rathnayake asiri.rathnay...@gmail.com
wrote:
Hi all,
Currently XWikiRightService has two methods for evaluating programming
rights:
XWikiRightService#hasProgrammingRights(XWikiContext context);
On Sep 28, 2009, at 5:43 PM, Asiri Rathnayake wrote:
Hi,
No: in this case the admin should remove the officeimporter app.
The only drawback I see is that until we have an application
manager it's a
bit harder for the Admin to bring the application back after
deleting it
(he
needs
Hi,
I thought we agree not to display the office importer menu entry if
the office importer app wasn't installed?
Yes, this is already implemented. I was talking about office importer
wysiwyg plugin only.
To be consistent we shouldn't have an office import action in the
wysiwyg if the
On Sep 28, 2009, at 6:05 PM, Asiri Rathnayake wrote:
Hi,
I thought we agree not to display the office importer menu entry if
the office importer app wasn't installed?
Yes, this is already implemented. I was talking about office importer
wysiwyg plugin only.
To be consistent we
Hi,
My suggestion was about file upload tab inside officeimporter wysiwyg
dialog, which requires openoffice server to function.
Yes, my question was: why have this tab enabled when the openoffice
server is not started?
Yes, we can either:
1. Completely hide the file upload tab if the
Hi All,
This is very trivial, I have put the message:
You can change these configuration options via
*WEB-INF/xwiki.properties*file.
In OpenOffice server administration UI which is actually not required (since
this UI is meant to be used by admins who knows about xwiki.properties).
I'm not
On Sep 28, 2009, at 6:19 PM, Asiri Rathnayake wrote:
Hi All,
This is very trivial, I have put the message:
You can change these configuration options via
*WEB-INF/xwiki.properties*file.
In OpenOffice server administration UI which is actually not
required (since
this UI is meant to
Hi,
Well we're not doing this right now for the office importer UI I
reported it in jira AFAIR.
Right now the top level menu entry is always present and if you click
on it you have the form available to upload a file even if the server
is not ready.
Yes, I'm going to fix
1. If the officeimporter application is installed create-page from
office document will be present. will be present, otherwise it will not be
displayed.
typo: create-page from office document will be present.
- Asiri
___
devs mailing list
Hi,
Last proposal I make:
[Proposal 5] Two colors
XE -
http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/XWATCH5/XE5.png
XWATCH -
http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/XWATCH5/XWATCH5.png
XMANAGER -
Hey whuuu !
I'd like to congratulate the whole dev-team for this achievement.
It is a great, marvelous, awesome and in the details stunning release.
Fabian
On Fri, Sep 25, 2009 at 6:49 PM, Thomas Mortagne
thomas.morta...@xwiki.comwrote:
The XWiki development team is pleased to announce the
Hi,
I've been wondering how to test exceptions in JUnit 4.x when you want
to assert the exception message. Just found an answer:
http://www.wakaleo.com/blog/225-testing-exceptions-in-junit-47
It looks to me slightly better than using the try/fail/catch strategy.
WDYT?
Thanks
-Vincent
http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/XWATCH5/XE5.png
http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/XWATCH5/XWATCH5.
png
Combining red and blue is visually stressful. They focus at different
lengths and therefore your eyes will be fighting to focus both
I have not followed everything about the new skin so my opinion is a bit
late but I look the last proposals and I agree with you, Niels, red blue
is a bit stressful...
blue, red or orange pastel colors are too tasteless to make it
attractive also...
Moreover, colibri skin seems quite angular and
The XWiki development team is pleased to announce the release of
XWiki Enterprise and XWiki Enterprise Manager 2.0.
Bravo! :-)
Stéphane
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
21 matches
Mail list logo
