Hi,
I am using xwiki for my organization.
In some cases the date format is appearing wrong, like the month filed
is displaying "36".
How can it be possible and what should i do to correct this.
Warm Regards
Jasvent Singh
Eperium Business Solutions India Pvt Ltd
2nd/3rd Floor, NSIC-STP Extension,
Administrative Block, NTSC Okhla Phase III,
New Delhi - 110020
Email : jasvent.singh(a)eperiumindia.com
Ph. No.(Off) : 91-11-46583900
Mob. No. : 91- 9015781898
Web : http://www.eperiumindia.com
<http://www.eperiumindia.com/>
eperium. e-commerce unlimited
This message may contain confidential or legally privileged information.
In the event of any error in transmission, unauthorized recipients are
requested to contact the sender immediately and not to disclose or make
use of this information. No warranties or assurance are made or given as
to the accuracy of the information given or in relation to the safety of
this e-mail and any attachments. No liability whatsoever is accepted for
any consequences arising from this e-mail.
Hi!
XWiki SAS is interestred to gather testimonials about XWiki Enterprise
and propose an original way to get them. Tell us why you love this
solution, why you find it interesting, innovating... in less than 140
characters on Twitter (by sending a tweet to @xwiki
<http://www.twitter.com/xwiki>). All the tweets will be listed on
http://xwiki.com and http://www.xwiki.org
"You can also help the project by creating a page on
http://www.xwiki.org/xwiki/bin/view/References/ that explains how you
use XWiki."
Many Thanks, in advance, for your participation.
Emilie Ogez
--
Marketing & Communication Manager
Mob. : +33( 0)623414368
Email : Emilie.Ogez(a)xwiki.com
http://www.xwiki.comhttp://www.twitter.com/eogez
Hi Everyone,
I met some problem with adding my personal edit panel to the panels
displayed in the WYSIWYG editing mode and Wiki editing mode. Here is what I
did:
I imitate the script of Class Switcher and Rights Help. Here is what I
wrote:
Name: DesignRationale
Type:edit
Category: Information
Content:
#largepanelheader($msg.get('Design Rationale'))
$xwiki.jsfx.use("js/xwiki/treeview/treeview.nocache.js", true) <div
id="DR_TreeView"></div> #panelfooter()
When I specify its type is "view", it can display in the right panel.
Then I modify the template file: editpanelsvars.vm . I add
"Panels.DesignRationale"
to both $editorPanelsWysiwyg and $editorPanelsWysiwyg . Here is the result:
#set($editorPanelsWiki =
"Panels.DocumentInformation,Panels.EditTranslations,Panels.SyntaxHelp, Panels.
DesignRationale")
#set($editorPanelsWysiwyg =
"Panels.DocumentInformation,Panels.EditTranslations,Panels.SyntaxHelp,Panels.
DesignRationale")
I reload the Tomcat and refresh the Xwiki page in WYSIWYG editing or Wiki
editing page. My customized panel did not appear.
Even I modify these two line like this:
#set($editorPanelsWiki = "Panels.DocumentInformation")
#set($editorPanelsWysiwyg = "Panels.DocumentInformation")
After I reload Tomcat, the other edit panel like SyntaxHelp
and EditTranslations would not disappear.
Could anyone Guru give me some idea what I missed? I do found out that
in editpanelsvars.vm there one line comment: ## Define variables containing
the list of edit panels for the Albatross skin
Does it mean it only take effect on albatross skin?
Big thanks in advance! :-)
Hi Marius,
Thank you for creating the API!
I am still trying to figure out how to display the gwt tree edit panel in
the WYSIWYG editing mode.
Is it correct that I use the new api like last time you told me? Please see
the code below:
native void setBackgroudColor(String color)
/*-{
editorJSReference.execute('backcolor', color);
}-*/;
and
if
(((TreeItem)event.getSelectedItem()).getText().equals("Alternative"))
{
setBackgroudColor("yellow");
}
What do you think? Do you think that will work?
Thank you! Hope I could get it done before meeting in the coming week.
Otherwise, my advisors will give me unhappy look again =_=
If there are anything I could help free feel to let me know, like
documenting how to use your new background API. Remember you have to create
the page for me first.
Leon
Hi devs,
Following the previous mail with the desired improvements for the annotation
feature, I would like to discuss some options for implementing the first of the
enhancements, namely the ability to configure easily the type of added
annotation. (see
http://dev.xwiki.org/xwiki/bin/view/Design/AnnotationFeature#HFeaturesimpro…
for details).
Two alternatives for this would be:
A) to preserve the current architecture of the annotations plugin and only add a
map of "extra fields" to the annotation type. The type of the annotation would
be known by the js client through the configuration of an XWiki class and the js
client would create a "generic" form for any such type.
See more details about this solution at
http://dev.xwiki.org/xwiki/bin/view/Design/AnnotationFeature#HSolution1extr…
.
Pros: preserves the current annotations architecture, creates an easy way to
plug an annotation storage service
Cons: the Annotation class would be nothing else but a "BaseCollection" the same
as a generic XWiki object, and we would be reimplementing view, save, edit,
delete of this type (already implemented through the xwiki action) from the web
forms level (editing and displaying an annotation), through the controller (REST
this time instead of actions in the standard wiki servlet), to the storage level
(XWikiIOService will only transform a map (the Annotation class) to another map
(the XWikiObject in the xwiki document)).
B) to make an XWiki object model based implementation where the js client, to
create the UI, would just asynchronously fetch standard actions in XWiki (edit,
view, save). In this case, where all is handled exclusively through the XWiki
model, Scribo would be plugged as an external service performing periodic
updates between the XWiki instance and its RDF store.
See more details about this solution at:
http://dev.xwiki.org/xwiki/bin/view/Design/AnnotationFeature#HSolution2XWik…
Pros: uses the xwiki object model 100%, there's no reimplementing of the whole
process of saving, editing objects, etc, the forms and views are light
customizations of standard XWiki mechanisms
Cons: the annotation mapping to document source cannot be implemented
straightforward (there are changes needed in the architecture and algorithm),
Scribo (or any other storage model different from XWiki) would need to duplicate
data, and it would not be 100% real time (since it would be a periodical
synchronizer)
The current implementation is illustrated in the
http://dev.xwiki.org/xwiki/bin/view/Design/AnnotationFeature#HCurrentImplem…
section.
I like the elegance of the first solution more, for the way a different storage
can be easily plugged, but I don't like that we're reimplementing a lot of XWiki
objects manipulation (which is why 2 would be a better solution).
WDYT?
Thanks,
Anca
Hi Marius,
I tried the the first way, "i) access the editor in Java (GWT) code by
writing a simple native getter", the dependency is killing me. I can not
compile it use eclipse the dependency is the way too complicated. I tried
use maven to build it, but I tried for a whole afternoon and I really don't
know how to write the correct pom to compile them together.
Could you please extend the native JavaScript API so that I can write
something like:
native void setBackgroudColor(String color)
/*-{
editorJSReference.execute('backcolor', color);
}-*/;
Could you please also tell me what you did to extend the native JavaScript
API, so I can learn about how to save the location of highlighted sentence
to help software maintainer easily trace back to the high lighted document.
If you want I can collect your reply and write document for you for this
one too.
Here is another problem, please see the screenshot:
http://picasaweb.google.com/freeleons/Xwiki#5394862411574232850 in the
WYSIWYG edit mode, the customized sidebar are disappeared, which means that
I can not use the GWT tree to interact with the WYSIWYG editor. Is there
anyway to keep the customized toolbar?
I have finished the document writeup here is the url:
http://dev.xwiki.org/xwiki/bin/view/Drafts/LoadingGWTApplicationsInXWik
You are literally saving my life. Thank you so much!
I've done a nice experiment with SocialCalc and I'm pretty happy of the
results:
It allows to edit a spreadsheet stored in a Wiki Page. It lacks a
server-side transformation of the spreadsheet to a Wiki table for
rendering, printing and pdfs, but it's already interesting.
http://incubator.myxwiki.org/xwiki/bin/view/Test/Calc
Ludovic
--
Ludovic Dubost
Blog: http://blog.ludovic.org/
XWiki: http://www.xwiki.com
Skype: ldubost GTalk: ldubost