xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

Re: [xwiki-devs] Use WYSIWG New Backgournd Color API

by Leon Wang

Hi Marius, I have change it to $wnd["wysiwyg_editor"], so now it looks like: native void setBackgroudColor(String color) /*-{ $wnd["wysiwyg_editor"].getCommandManager().execute('backcolor', color); alert($wnd["wysiwyg_editor"].getCommandManager().getValue('backcolor')); }-*/; And this time the error says:"$wnd[ab].getCommandManager is not a function" Please see the screenshot: http://picasaweb.google.com/lh/photo/wLOJbhbvl0xZe1ZWshA5wg?feat=directlink I was wondering is it because the Java code setBackgroudColor("yellow"); and in native JavaScript do not accept double quoted string only single quoted string? I do deleted all xwiki web 2.0 jar files in lib and replaced with 2.02 jar files. I have no idea what went wrong. Any advise? Thank you, Marius! -Leon

15 years, 3 months

Re: [xwiki-devs] Use WYSIWG New Backgournd Color API

by Leon Wang

Hi Marius, I successfully load the tree panel in the WYSIWYG editing model. Thank you so much! :-) I put the compiled xwiki-web-gwt, xwiki-web-wysiwyg and xwiki-webdav 2.02 jar file to the lib folder. After the tree loaded, I found there 2 errors using firebug (thank you for recommendation), one is saying "isc is not defined" in overwritesc.js(), one is saying "isc is not defined" in overwritesc.js(). Here is the screenshot: http://picasaweb.google.com/lh/photo/BxK7IksttDQFB4KtJAJOvg?feat=directlink. Here is what I did, first I modify the template/macros.vm file: Wysiwyg.onModuleLoad(function() { window["wysiwyg_editor"] = new WysiwygEditor($jsVarName); $jsVarName = undefined; }); In the GWT file: native void setBackgroudColor(String color) /*-{ wysiwyg_editor.getCommandManager().execute('backcolor', 'yellow'); alert(wysiwyg_editor.getCommandManager().getValue('backcolor') ); }-*/; /** * This is the entry point method. */ @SuppressWarnings("unchecked") public void onModuleLoad() { Tree tree = new Tree(); tree.setAnimationEnabled(true); TreeItem outerRoot = new TreeItem("DR Tag Tree"); outerRoot.addItem("Alternative"); outerRoot.addItem("Assumption"); outerRoot.addItem("Argument"); outerRoot.addItem("Claim"); outerRoot.addItem("Decision"); outerRoot.addItem("Requirement"); tree.addItem(outerRoot); tree.addSelectionHandler(new SelectionHandler() { public void onSelection(SelectionEvent event) { if (((TreeItem) event.getSelectedItem()).getText().equals( "Alternative")) { setBackgroudColor("yellow"); } else if (((TreeItem) event.getSelectedItem()).getText() .equals("Requirement")) { setBackgroudColor("blue"); } else if (((TreeItem) event.getSelectedItem()).getText() .equals("Decision")) { setBackgroudColor("green"); } Window.alert(((TreeItem) event.getSelectedItem()).getText()); } }); Could you give me some ideas what is wrong? Or what I missed? Thank you, Marius! -Leon

15 years, 3 months

[xwiki-devs] [VOTE] Modify ParameterDescriptor/PropertyDescriptor to support id/name

by Thomas Mortagne

Hi devs, We want to display macros parameters pretty names in the WYSIWYG. For that we need to provide it in the WYSIWYG. The current ParameterDescriptor#getName actually return the parameter identifier/technical name. So I see two solutions: 1) the general rule in new XWiki architecture is to use id/name instead of name/prettyname so i propose to break ParameterDescriptor and PropertyDescriptor to follow this rule. 2) add a getDisplayName method and let getName for the identifier WDYT ? +1 for 1). I never like to break an API but doubt this API is used a lots yet except by us internally and it would like we use the same rule everywhere as much as possible. -- Thomas Mortagne

15 years, 3 months

[xwiki-devs] Fwd: [ANN] Maven Javadoc Plugin 2.6.1 Released

by Vincent Massol

I'm upgrading our top level POM. Thanks -Vincent Begin forwarded message: > From: Vincent Siveton <vsiveton(a)apache.org> > Date: October 26, 2009 4:36:01 PM CEST > To: announce(a)maven.apache.org, users(a)maven.apache.org > Subject: [ANN] Maven Javadoc Plugin 2.6.1 Released > Reply-To: "Maven Users List" <users(a)maven.apache.org> > > The Maven team is pleased to announce the release of the Maven Javadoc > Plugin, version 2.6.1 > > This plugin uses the javadoc tool for generating javadocs for the > specified project. > > http://maven.apache.org/plugins/maven-javadoc-plugin/ > > You should specify the version in your project's plugin configuration: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-javadoc-plugin</artifactId> > <version>2.6.1</version> > </plugin> > > > Release Notes - Maven 2.x Javadoc Plugin - Version 2.6.1 > > ** Bug > * [MJAVADOC-244] - Javadoc plugin: java files under > src/main/javadoc and doc-files directory are being compiled > * [MJAVADOC-246] - ExceptionInInitializerError with > maven-site-plugin:2.1-SNAPSHOT and mvn > 2.1 > * [MJAVADOC-251] - Configuration of javadoc:javadoc fails with NPE > upon disadvantageous order of config injection > * [MJAVADOC-252] - javadoc link : nonproxyhosts not used > * [MJAVADOC-257] - maven-javadoc-plugin 2.5, 2.6 and mojo: Error > extracting plugin descriptor > * [MJAVADOC-259] - Resource copying from javadoc dir is incomplete > * [MJAVADOC-262] - Parameters like sourcepath depend on system > path separator (colon/semicolon) > * [MJAVADOC-268] - performance problem in > AbstractJavadocMojo.getModulesLinks() > > ** Improvement > * [MJAVADOC-258] - Grouping example could show multiple packages > per group > * [MJAVADOC-266] - META-INF directory copied from resource > artifacts > * [MJAVADOC-267] - Allow changing the reportOutputDirectory from > the commandline > > > ** Task > * [MJAVADOC-248] - Site 'Usage' page references 2.5 version of m- > javadoc-p > > Enjoy, > > -The Maven team

15 years, 3 months

Re: [xwiki-devs] [xwiki-users] Call for testimonials

by Vincent Massol

Hi everyone, I've just started a Testimonial page on xwiki.org at http://www.xwiki.org/xwiki/bin/view/References/Testimonials If you want to give a testimony feel free to edit the page or add a comment to it. If you find existing testimonies please help me move them there. Thanks -Vincent On Mon, Oct 26, 2009 at 10:50 AM, Emilie Ogez <Emilie.Ogez(a)xwiki.com> wrote: > 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

15 years, 3 months

[xwiki-devs] Date format is appearing wrong

by Jasvent Singh

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.

15 years, 3 months

[xwiki-devs] Moving the new Skins Tutorial in the Dev Guide

by Raluca Stavro

Hello, I would like to move the new Skins Tutorial ( http://dev.xwiki.org/xwiki/bin/view/Drafts/XWikiNewSkin ) in the Dev Guide and link it from Adminstration Guide. Here is my +1. Thank you, Raluca.

15 years, 3 months

[xwiki-devs] Call for testimonials

by Emilie Ogez

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.com http://www.twitter.com/eogez

15 years, 3 months

[xwiki-devs] Editor Panels

by Leon Wang

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! :-)

15 years, 3 months

[xwiki-devs] Use WYSIWG New Backgournd Color API

by Leon Wang

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

15 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs