Hi Alexandre,
Alexandre Souza wrote:
Thanks, Guillaume
But I think that PUT method doesn't work for Panels, only for Pages.
I trying another way, using a velocity script in a panel already created,
but I have a doubt.
Do you known how I can get all existing pages in specific Space to show
Hi,
Im trying to fix http://jira.xwiki.org/jira/browse/XWIKI-4274
Basically if you do $xwiki.getDocument(someDoc).getRenderedContent()
it'll get executed in the context of the current doc which I believe
is wrong especially since other signatures of getRenderedContent()
execute in the
BTW I think it's wrong that we set the XWiki.Import doc in the
XWiki.AdminSheet page.
It should be set internally as the current in XWiki.AdminImportSheet.
There's no reason AdminSheet should know about it IMO.
WDYT?
Thanks
-Vincent
On Sep 4, 2009, at 10:07 AM, Vincent Massol wrote:
Hi,
On Sep 4, 2009, at 10:07 AM, Vincent Massol wrote:
Hi,
Im trying to fix http://jira.xwiki.org/jira/browse/XWIKI-4274
Basically if you do
$xwiki.getDocument(someDoc).getRenderedContent() it'll get
executed in the context of the current doc which I believe is wrong
especially since
On Fri, Sep 4, 2009 at 10:07, Vincent Massolvinc...@massol.net wrote:
Hi,
Im trying to fix http://jira.xwiki.org/jira/browse/XWIKI-4274
Basically if you do $xwiki.getDocument(someDoc).getRenderedContent()
it'll get executed in the context of the current doc which I believe
is wrong
On Sep 4, 2009, at 10:30 AM, Thomas Mortagne wrote:
On Fri, Sep 4, 2009 at 10:07, Vincent Massolvinc...@massol.net
wrote:
Hi,
Im trying to fix http://jira.xwiki.org/jira/browse/XWIKI-4274
Basically if you do
$xwiki.getDocument(someDoc).getRenderedContent()
it'll get executed in the
On Fri, Sep 4, 2009 at 10:39, Vincent Massolvinc...@massol.net wrote:
On Sep 4, 2009, at 10:30 AM, Thomas Mortagne wrote:
On Fri, Sep 4, 2009 at 10:07, Vincent Massolvinc...@massol.net
wrote:
Hi,
Im trying to fix http://jira.xwiki.org/jira/browse/XWIKI-4274
Basically if you do
Well, if you expect to use the default URLClassLoader for dynamically
load some JARs for script executions, you should consider class
unloading and caching issue with great care. Especially that you
suggest to use attachment of the XWiki for storing JARs.
I tell you that by experience,
I can't promise anything yet I stared the topic so...
if you need advices.
2009/9/2 Thibaut DEVERAUX thibaut.dever...@gmail.com
+1
2009/9/2 Ludovic Dubost ludo...@xwiki.org
One important thing I think is that you need to put an annotation
feature demo on a public server somewhere, so that
Hi,
Because we want to make a standard from vertical-aligned form, this means
the buttons should be left-ordered with the most important action first.
This should be changed also in Toucan and Albatross skin, not only just in
Colibri.
Right now the Edit Actions are Cancel, Preview, SaveContinue,
+1 (C)
For my opinion the Preview button is necessary because the final structure of
the page is different then the edition one. Because of panels, colors etc, you
can want to check the global look and integration of your page
And also all buttons should be in one group. It's all actions that
Ecaterina Valica wrote:
Hi,
Because we want to make a standard from vertical-aligned form, this means
the buttons should be left-ordered with the most important action first.
This should be changed also in Toucan and Albatross skin, not only just in
Colibri.
Right now the Edit Actions
Hi,
We currently have a bug with script macros and contexts:
http://jira.xwiki.org/jira/browse/XWIKI-4279
I can easily solve it by backuping and restoring the Execution Context
in getRenderedContent(String, String, String).
I think this is the correct way since the context should be isolated
The vote is open until the end of today.
Score:
(4) 7,5
(B) 6
(2) 7,32
Themes:
(4)
http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Proposal4/Proposal4.png
(B)
http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/BColorTheme/SchemeB.png
(2)
Personally I never understand thoose different buttons. Just amazing me.
So there the user chains are (tell me if I'm right) :
Use SAVE VIEW only
The user is writting a message. He saves it.
Dangers :
- He may save and then see errors and come back to modify : why PREVIEW
exists
- He may find
On Fri, Sep 4, 2009 at 2:16 PM, Ecaterina Valica vali...@gmail.com wrote:
The vote is open until the end of today.
Score:
(4) 7,5
(B) 6
(2) 7,32
In that case, please count my vote as a full +1 instead of +0.66 for (2) :)
Themes:
(4)
Hi,
On Fri, Sep 4, 2009 at 2:19 PM, Thibaut DEVERAUX thibaut.dever...@gmail.com
wrote:
Personally I never understand thoose different buttons. Just amazing me.
So there the user chains are (tell me if I'm right) :
Use SAVE VIEW only
The user is writting a message. He saves it.
Dangers :
On Fri, Sep 4, 2009 at 2:54 PM, Guillaume Lerougeguilla...@xwiki.com wrote:
We actually had a remark from a customer not so long ago who asked us to
rename Save View into Publish on their wiki.
About renaming, WDYT of:
Save and quit editor Save Quit editor without saving
or the shorter:
+1
It will be also useful fo other things
On Fri, Sep 4, 2009 at 14:06, Vincent Massolvinc...@massol.net wrote:
Hi,
We currently have a bug with script macros and contexts:
http://jira.xwiki.org/jira/browse/XWIKI-4279
I can easily solve it by backuping and restoring the Execution Context
Save and quit editor Save Quit editor without saving
or the shorter:
Save and quit Save Quit
+1 I find it ot be an exellent idea !
It makes evident that when saving only you will not quit.
The longuer may be more securized. I'm not sur it is mandatory anyway.
2009/9/4 Thibaut DEVERAUX
Thanks, after re-reading Sergiu's points I think my preference would go to:
[Preview] [Save Quit Editor] [Save] [Quit]
I think that if we refactor the edit mode so that the Source WYSIWYG
tab becomes our wiki editor [1] the WYSIWYG will de facto become the
easiest way to do a preview, making
On Sep 4, 2009, at 4:08 PM, tmortagne (SVN) wrote:
Author: tmortagne
Date: 2009-09-04 16:08:55 +0200 (Fri, 04 Sep 2009)
New Revision: 23282
Modified:
platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/objects/
classes/DBListClass.java
Log:
[misc] Improve log
Modified:
On Fri, Sep 4, 2009 at 16:21, Vincent Massolvinc...@massol.net wrote:
On Sep 4, 2009, at 4:08 PM, tmortagne (SVN) wrote:
Author: tmortagne
Date: 2009-09-04 16:08:55 +0200 (Fri, 04 Sep 2009)
New Revision: 23282
Modified:
platform/core/trunk/xwiki-core/src/main/java/com/xpn/xwiki/objects/
+0
Thanks,
Marius
Vincent Massol wrote:
Hi,
We currently have a bug with script macros and contexts:
http://jira.xwiki.org/jira/browse/XWIKI-4279
I can easily solve it by backuping and restoring the Execution Context
in getRenderedContent(String, String, String).
I think this is
On Sep 4, 2009, at 4:23 PM, Thomas Mortagne wrote:
On Fri, Sep 4, 2009 at 16:21, Vincent Massolvinc...@massol.net
wrote:
On Sep 4, 2009, at 4:08 PM, tmortagne (SVN) wrote:
Author: tmortagne
Date: 2009-09-04 16:08:55 +0200 (Fri, 04 Sep 2009)
New Revision: 23282
Modified:
On Fri, Sep 4, 2009 at 16:31, Vincent Massolvinc...@massol.net wrote:
On Sep 4, 2009, at 4:23 PM, Thomas Mortagne wrote:
On Fri, Sep 4, 2009 at 16:21, Vincent Massolvinc...@massol.net
wrote:
On Sep 4, 2009, at 4:08 PM, tmortagne (SVN) wrote:
Author: tmortagne
Date: 2009-09-04 16:08:55
+0
JV.
On Fri, Sep 4, 2009 at 2:06 PM, Vincent Massolvinc...@massol.net wrote:
Hi,
We currently have a bug with script macros and contexts:
http://jira.xwiki.org/jira/browse/XWIKI-4279
I can easily solve it by backuping and restoring the Execution Context
in getRenderedContent(String,
[Preview] [Save Quit Editor] [Save] [Quit]
+1, love...
About preview by WYSIWYG for my psychology it all depends on how the
editor lets me psycologically able to think is text in context.
I'd may take Knol as an example of it (try to edit) :
+1 for (C)
-1 on Quit. Like Caty says Quit is used for quiting applications.
I think Save and View Save and Continue are good name choices that
serve their purpose. I think we should keep them provided we don't receive
additional user/customer remarks.
Ecaterina Valica-2 wrote:
What do
Ecaterina Valica wrote:
Hi,
Because we want to make a standard from vertical-aligned form, this means
the buttons should be left-ordered with the most important action first.
This should be changed also in Toucan and Albatross skin, not only just in
Colibri.
Right now the Edit Actions
Hi,
On Fri, Sep 4, 2009 at 5:46 PM, Ecaterina Valica vali...@gmail.com wrote:
The vote is open until the end of today.
Score:
(4) 7,5
(B) 6
(2) 7,32
Themes:
(4)
http://incubator.myxwiki.org/xwiki/bin/download/ColorThemes/Proposal4/Proposal4.png
(B)
Hi all,
I'm joining here a component diagram of annotation feature.
As you can see on the diagram, AnnotationFeature uses AnnotationTarget
in order to alter both selection (using SelectionService) and document
source (using severals Alterers and IOTargetService).
AnnotationFeature use IOService
+1 on Wiki code should be named Source.
On Fri, Sep 4, 2009 at 16:40, Ecaterina Valica vali...@gmail.com wrote:
-1 on Quit. Quit is when you QUIT an application, just like Exit. When you
press that button you don't quit your wiki, you just leave the editor.
I felt it a bit too, was my problem about securizing. So if you felt
it too I add my +1
--- [Quit editor] ???
I would say code more than source. Source sounds like a dev jargon terme to me.
2009/9/4 Ecaterina Valica vali...@gmail.com:
+1 on Wiki code should be named Source.
On Fri, Sep 4,
I uploaded a demo here http://www.vimeo.com/6433080
An annotation enabled test server will be available soon.
Lucien.
Thibaut DEVERAUX wrote:
I can't promise anything yet I stared the topic so...
if you need advices.
2009/9/2 Thibaut DEVERAUX thibaut.dever...@gmail.com
+1
2009/9/2
Hi!
One of the biggest problems I've been facing concerning changes in a
property, or the access rights to a document or space is how to keep
track of the reasons that cause them.
I mean, for instance, how could we document the reason (a message sent
by the responsible of some contents, a
Nice tool lucien !!
Nice mockup caty. ;-)
- I would like to see in the panel's title the number of all existing
annotations;
Did you make it to show evryting even if some are hidden in the panel?
Question:
- What happens if you have more that 5 annotations?
- How many annotation will you
great tool :)
eager to use it :)
could be really useful and bring new ideas...
regards
Pascal
On Fri, Sep 4, 2009 at 6:39 PM, Lucien Pereira lucien.pere...@xwiki.comwrote:
I uploaded a demo here http://www.vimeo.com/6433080
An annotation enabled test server will be available soon.
Lucien.
Hi Lucien,
Great feature and work.
These are just some ideas for your design and a mockup with some
suggestions:
- The annotated text in panel is much too powerful if it's bold;
- The ... should be after the annotated text, on the same line, not before
by;
- for the Delete action, you should use
Q: Can I select to view only the annotation made by a specific user?
___
devs mailing list
devs@xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs
Hi,
So seems that the final Default Color Theme for XWiki is going to be (2).
Thanks everyone for voting. Have a nice week-end.
Caty
On 04/09/2009, Asiri Rathnayake asiri.rathnay...@gmail.com wrote:
Hi,
On Fri, Sep 4, 2009 at 5:46 PM, Ecaterina Valica vali...@gmail.com wrote:
The vote is
Hi all,
first of all, thanks for the great work, xwiki is a great product
i'm trying to integrate the rendering component of xwiki into our
application for hours, without success.
I included all the libraries from XWiki 2.0 M4 and was running
following code in a standalone application (not
42 matches
Mail list logo
