- xwiki-devs@xwiki.org - lists.xwiki.org

Re: [xwiki-devs] [xwiki-notifications] r19341 - in platform/core/trunk/xwiki-rendering: . xwiki-rendering-tests/src/test/java/org/xwiki/rendering xwiki-rendering-tests/src/test/resources/section

by Vincent Massol

On May 4, 2009, at 5:34 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2009-05-04 17:34:15 +0200 (Mon, 04 May 2009) > New Revision: 19341 > > Added: > platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/test/ > resources/section/section10.test > Modified: > platform/core/trunk/xwiki-rendering/pom.xml > platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/test/ > java/org/xwiki/rendering/RenderingTests.java > Log: > XWIKI-3668: Problem when there is a {{velocity}} marker in a title : > double line under the title > > Modified: platform/core/trunk/xwiki-rendering/pom.xml > =================================================================== > --- platform/core/trunk/xwiki-rendering/pom.xml 2009-05-04 14:56:49 > UTC (rev 19340) > +++ platform/core/trunk/xwiki-rendering/pom.xml 2009-05-04 15:34:15 > UTC (rev 19341) > @@ -41,7 +41,7 @@ > <dependency> > <groupId>org.wikimodel</groupId> > <artifactId>org.wikimodel.wem</artifactId> > - <version>2.0.7-20090430</version> > + <version>2.0.7-20090504</version> > </dependency> > </dependencies> > </dependencyManagement> > > Modified: platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/ > src/test/java/org/xwiki/rendering/RenderingTests.java > =================================================================== > --- platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/ > test/java/org/xwiki/rendering/RenderingTests.java 2009-05-04 > 14:56:49 UTC (rev 19340) > +++ platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/ > test/java/org/xwiki/rendering/RenderingTests.java 2009-05-04 > 15:34:15 UTC (rev 19341) > @@ -179,6 +179,7 @@ > suite.addTestsFromResource("section/section7", false); > suite.addTestsFromResource("section/section8", false); > suite.addTestsFromResource("section/section9", false); > + suite.addTestsFromResource("section/section10", false); > > // Escaping > suite.addTestsFromResource("escape/escape1", false); > > Added: platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/ > test/resources/section/section10.test > =================================================================== > --- platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/ > test/resources/section/section10.test (rev 0) > +++ platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/ > test/resources/section/section10.test 2009-05-04 15:34:15 UTC (rev > 19341) > @@ -0,0 +1,33 @@ > + > .#-------------------------------------------------------------------------------- > +.input|xwiki/2.0 > +.# Verify that a header content can start on a new line Are you sure this is the correct comment? Thanks -Vincent > > + > .#-------------------------------------------------------------------------------- > += Title level 1 {{simplemacro}}{{/simplemacro}}= > +.#----------------------------------------------------- > +.expect|event/1.0 > +.#----------------------------------------------------- > +beginDocument > +beginSection > +beginHeader [1, HTitlelevel1] > +onWord [Title] > +onSpace > +onWord [level] > +onSpace > +onWord [1] > +onSpace > +onMacroInline [simplemacro] [] [] > +endHeader [1, HTitlelevel1] > +endSection > +endDocument > +.#----------------------------------------------------- > +.expect|xhtml/1.0 > +.#----------------------------------------------------- > +<h1 id="HTitlelevel1"><span>Title level 1 </span></h1> > +.#----------------------------------------------------- > +.expect|xwiki/2.0 > +.#----------------------------------------------------- > += Title level 1 {{simplemacro/}} = > +.#----------------------------------------------------- > +.input|xhtml/1.0 > +.#----------------------------------------------------- > +<h1 id="HTitlelevel1"><span>Title level 1 </span></h1> > \ No newline at end of file

16 years, 4 months

1
0
0 0

[xwiki-devs] Custom Editor Panel

by RalphS

Sorry if this has been asked before or is documented, I have found it neither in the mailing list archives nor in the docs. I have created a custom panel that I would like to be visible when a user edits a page using the WIKI or WYSYWIG editor. I have successfully created the panel and set its type to "edit". Now how do I add it to the panel column? In the panel wizard, only panels of type "view" are available. This appears logical to me, because editor panels are not as straightforward to set up as view panels are, since editor panels must somehow be assciated with one or multiples types of editors. E.g. the "Document Information" panel is only visible when the WIKI or WYSIWYG editor is active, which is exactly the behavior I whish for my panel. Could someone please give me a pointer to where this is documented or explain what I have to do? Thanks in advance and best regards, Ralph -- View this message in context: http://n2.nabble.com/Custom-Editor-Panel-tp2761144p2761144.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years, 4 months

2
3
0 0

[xwiki-devs] [VOTE] Upgrade officeimporter to use JODConverter 3.0-beta-2 release and add support for auto-starting oo server

by Asiri Rathnayake

Hi Devs, Jodconverter 3.0-beta-2 version has been released: http://groups.google.com/group/jodconverter/browse_thread/thread/8b73b26b70… One of the most important fix for us is the first point mentioned there: "OOo is now started with -nofirststartwizard by default. This avoids the frequent problem of OOo refusing to work on a new machine because it's expecting somebody to accept its license dialogue even in -headless mode" Without this fix currently we have to copy an already initialized ooprofile directory to the destination server and point to it from xwiki.properties file. This is a pain. Also there are several other enhancements: http://code.google.com/p/jodconverter/issues/list?can=1&q=label%3ATarget-3.… Unfortunately some of the public APIs of jodconverter has been changed from beta-1 release to beta-2 release. But still, upgrading our officeimporter module to use this new jodconverter release will not require that much of code changes. Note: jodconverter is not available in any public maven repository AFAIK. So we need to release it to our externals repository as we did with the beta-1 version. The other feature is a frequently requested one (auto-strart) and admins are having a hard time without this feature :) Here is my +1 for both features. Thanks. - Asiri

16 years, 4 months

7
16
0 0

[xwiki-devs] [VOTE] What do we do with links inside links ?

by Thomas Mortagne

Hi devs, We have (at least) two issues about links inside links: http://jira.xwiki.org/jira/browse/XWIKI-3149 and http://jira.xwiki.org/jira/browse/XWIKI-3440 Basically the issue is that XHTML does not support links inside links. To fix this I see two possibilities: 1) valid in XDOM: this means XHTML renderer has to take care of this and skip link inside links 2) not valid in XDOM: this means each parser has to make sure not put link inside links in the XDOM +1 for 1) and -0 for 2) since it's a XHTML issue only and we could have some use cases supporting this like XWiki syntax support it. Thanks, -- Thomas Mortagne

16 years, 4 months

4
4
0 0

[xwiki-devs] recent problem with {{velocity}+{{html}}

by Pascal Voitot

Hello, I have compiled code directly from the trunk and I have a simple wiki page such as: {{velocity}} {{html}} #warning("(% style='font-size:120%' %) [[mylink>>myspace.mypage]]") {{/html}} {{/velocity}} and I get the following text: (% style='font-size:120%' %) [[mylink>>myspace.mypage]] The content in the velocity macro is not rendered. Ok apparently now, default {{html}} is {{html wiki="false"}} So I write: {{velocity}} {{html wiki="true"}} #warning("(% style='font-size:120%' %) [[mylink>>myspace.mypage]]") {{/html}} {{/velocity}} And I get following exception: ... org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getRenderedContent' in class com.xpn.xwiki.api.Document threw exception java.lang.StackOverflowError @ /templates/preview.vm[6,7] ... Caused by: java.lang.StackOverflowError at org.xwiki.rendering.renderer.printer.MonitoringWikiPrinter.print(MonitoringWikiPrinter.java:41) at org.xwiki.rendering.renderer.printer.XMLWikiPrinter.print(XMLWikiPrinter.java:79) at org.xwiki.rendering.renderer.printer.WrappingWikiPrinter.print(WrappingWikiPrinter.java:39) at org.xwiki.rendering.renderer.printer.MonitoringWikiPrinter.print(MonitoringWikiPrinter.java:41) at org.xwiki.rendering.renderer.printer.XMLWikiPrinter.print(XMLWikiPrinter.java:79) at org.xwiki.rendering.renderer.printer.WrappingWikiPrinter.print(WrappingWikiPrinter.java:39) at org.xwiki.rendering.renderer.printer.MonitoringWikiPrinter.print(MonitoringWikiPrinter.java:41) at org.xwiki.rendering.renderer.printer.XMLWikiPrinter.print(XMLWikiPrinter.java:79) ... Kind of infinite loop... I have tried other combinations with html before velocity, inside warning macro etc... but never works as it should... Do you have an idea??? regards Pascal

16 years, 4 months

2
9
0 0

[xwiki-devs] Fwd: [ANN] Versions Maven Plugin 1.0-alpha-3 released

by Vincent Massol

FYI -Vincent Begin forwarded message: > From: Stephen Connolly <stephen.alan.connolly(a)gmail.com> > Date: April 23, 2009 9:05:16 PM CEDT > To: "dev(a)mojo.codehaus.org" <dev(a)mojo.codehaus.org>, "user(a)mojo.codehaus.org > " <user(a)mojo.codehaus.org>, Maven Users List <users(a)maven.apache.org> > Subject: [ANN] Versions Maven Plugin 1.0-alpha-3 released > Reply-To: "Maven Users List" <users(a)maven.apache.org> > > The Mojo team is pleased to announce the release of the Versions Maven > Plugin, version 1.0-alpha-3. > > The Versions Plugin has the following goals. > > * versions:display-dependency-updates scans a project's > dependencies and > produces a report of those dependencies which have newer versions > available. > * versions:display-plugin-updates scans a project's plugins and > produces > a report of those plugins which have newer versions available. > * versions:update-parent updates the parent section of a project > so that > it references the newest available version. For example, if you use a > corporate root POM, this goal can be helpful if you need to ensure > you are > using the latest version of the corporate root POM. > * versions:update-properties updates properties defined in a > project so > that they correspond to the latest available version of specific > dependencies. This can be useful if a suite of dependencies must all > be > locked to one version. > * versions:update-child-modules updates the parent section of the > child > modules of a project so the version matches the version of the current > project. For example, if you have an aggregator pom that is also the > parent > for the projects that it aggregates and the children and parent > versions get > out of sync, this mojo can help fix the versions of the child > modules. (Note > you may need to invoke Maven with the -N option in order to run this > goal if > your project is broken so badly that it cannot build because of the > version > mis-match). > * versions:lock-snapshots searches the pom for all -SNAPSHOT > versions > and replaces them with the current timestamp version of that - > SNAPSHOT, e.g. > -20090327.172306-4 > * versions:unlock-snapshots searches the pom for all timestamp > locked > snapshot versions and replaces them with -SNAPSHOT. > * versions:resolve-ranges finds dependencies using version ranges > and > resolves the range to the specific version being used. > * versions:use-releases searches the pom for all -SNAPSHOT versions > which have been released and replaces them with the corresponding > release > version. > * versions:use-next-releases searches the pom for all non-SNAPSHOT > versions which have been a newer release and replaces them with the > next > release version. > * versions:use-latest-releases searches the pom for all non- > SNAPSHOT > versions which have been a newer release and replaces them with the > latest > release version. > * versions:use-next-versions searches the pom for all versions > which > have been a newer version and replaces them with the next version. > * versions:use-latest-versions searches the pom for all versions > which > have been a newer version and replaces them with the latest version. > * versions:commit removes the pom.xml.versionsBackup files. Forms > one > half of the built-in "Poor Man's SCM". > * versions:revert restores the pom.xml files from the > pom.xml.versionsBackup files. Forms one half of the built-in "Poor > Man's > SCM". > > The artifacts have been deployed to the mojo repository and will be > mirrored > to central within the next 24 hours. > > The Mojo Team. > > Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-3 > ================================================ > > ** Bug > * [MVERSIONS-3] - display-plugin-updates does not identify the > plugin > version as not being provided when derived from the super-pom > * [MVERSIONS-10] - Property Placedholders output in > versions:display-plugin-updates > * [MVERSIONS-13] - display-plugin-updates warns that version is not > defined if same versio as in parent pom is defined > > ** Improvement > * [MVERSIONS-25] - Users should be made aware that this plugin > relies on > accurate maven-metadata.xml files. > > ** New Feature > * [MVERSIONS-15] - Add comparisonMethod=mercury > * [MVERSIONS-18] - Expose updated versions as a report > * [MVERSIONS-21] - Add mojo to lock snapshots to timestamp version > * [MVERSIONS-24] - Enable resolution of dependency version ranges > * [MVERSIONS-28] - use-releases mojo > * [MVERSIONS-32] - Add versions:commit and versions:revert using a > "Poor-man's SCM" so that changes to the pom can be accepted and > rolled back > * [MVERSIONS-33] - add use-next-releases goal > * [MVERSIONS-34] - add a use-latest-releases goal > * [MVERSIONS-35] - add use-next-versions goal > * [MVERSIONS-36] - add use-latest-versions goal > * [MVERSIONS-37] - add a use-releases goal that replaces -SNAPSHOT > dependencies with their corresponding release version (if available) > > ** Task > * [MVERSIONS-12] - Documentation is incorrect on > http://mojo.codehaus.org/versions-maven-plugin/examples/update-parent.html > > > ** Wish > * [MVERSIONS-26] - Can't resolve pom properties for specifying > plugin > version in pluginmanagement

16 years, 4 months

1
0
0 0

[xwiki-devs] Survey Application

by Chathura Prabuddha

Hai Ludovic. I liked to continue the survey application project even if I not selected to GSOC. If you give me a chance I can show my commitment to the Xwiki. If I'm on the project. I would like to know about the following points. 1. Ideas that need to change in my application. 2. How the milestone plan should be adjusted based on the above ideas complexity. 3. Changes that need to be done with the mockups that I had created. Its better if I can have a mentor who can guide me to this target. Also I would like to thank all the community members of the Xwiki. I gathered lots of experience to my life during past month.This is my first FOSS community involvement. If something went wrong from me please forgive me. I don't want to loose this connections that I had build with those great people. So Good luck Xwiki... Thank you... -- ~ Chathura Prabuddha Ganegoda~ Undergraduate, Department of Computer Science & Engineering, University of Moratuwa, Sri Lanka. http://gacpganegoda.blogspot.com/

16 years, 4 months

3
7
0 0

[xwiki-devs] problem on xwiki.org

by Pascal Voitot

Hello, when you want to access the Syntax Help, you see: $newdocprivate.fromXML($content) something wrong? Pascal

16 years, 4 months

2
2
0 0

Re: [xwiki-devs] [xwiki-notifications] r19290 - in platform: core/trunk/xwiki-core/src/main/resources web/trunk/standard/src/main/webapp/resources/js/xwiki/table web/trunk/standard/src/main/webapp/templates

by Sergiu Dumitriu

jvelociter (SVN) wrote: > -.controlPagination div.prevPagination { > +.controlPagination span.prevPagination { Why don't you drop the element name from the selector? Isn't the classname enough? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 4 months

1
0
0 0

Re: [xwiki-devs] XWiki Jabber, Google Talk, Skype Integration

by Tharindu Madushanka

Hi, I have been looking at how to notify when an event has been finished. Here what I have currently understood and I got some confusion. In order to get notified when login event finished, I think I have to do the following things. 1. Create a LoginListener class that implements EventListener 2. Create object of DefaultObservationManager class (DefaultObservationManager implements ObservationManager) 3. Define class UserLoginEvent similar to DocumentSaveEvent 4. call addListener() of ObjectManager interface (using DefaultObjectManager) with parameters - object of UserLoginEvent and reference to login listener. 5. get reference to DefaultObjectManager instance 6. call notify() of DefaultObjectManager instance when user successfully logged in, with parameters - object of UserLoginEvent, doc and context 7. Implement notify() in LoginListener class. Q. But I have several confusions when I looked at XWiki class, saveDocument() 1. Where does it create and add a listener to ObservationManager object?? 2. And also it takes ObservationManager object from Util.getComponent()but where does this observationManager instance is added or set ? Please clarify me on what I currently understood and let me know if its the right steps to go with. Kind Regards, -Tharindu

16 years, 4 months

3
8
0 0

Re: [xwiki-devs] [xwiki-notifications] r19209 - in platform: core/trunk/xwiki-core/src/main/resources web/trunk/standard/src/main/webapp/resources/js/xwiki/table web/trunk/standard/src/main/webapp/templates

by Sergiu Dumitriu

jvelociter (SVN) wrote: > + a.href = (row.${jscolname}_url=="") ? "javascript:void(0)" : row.${jscolname}_url; Why do you use this javascript:void(0)? -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 4 months

2
1
0 0

[xwiki-devs] Officeimporter importing of document with "frames"

by Asiri Rathnayake

Hi devs, To be clear about what a "frame" means in OOo please have a look at following screenshots: http://i39.tinypic.com/293aptt.png http://i41.tinypic.com/259fnfq.jpg The problem with these frames is that OOo server generates html like below: <code> <SPAN ID="Frame1" DIR="LTR" STYLE="float: left; width: 3.09in; height: 3.8in; border: 1px solid #000000; padding: 0.06in; background: #ffffff"> <P CLASS="frame-contents">Hello, This is a frame as it is called on openoffice writer.</P> <P CLASS="frame-contents"><BR><BR> </P> <P CLASS="frame-contents">We have a problem with importing documents that contain this sort of frames.</P> <P CLASS="frame-contents"><BR><BR> </P> <P CLASS="frame-contents">This is the last paragraph</P> </SPAN> <code> Let's forget the fact that it should be a <div> instead of a <span> for the moment. But even if we convert it to a <div>, with our style filtering approach this kind of frames are filtered out (because the frame is made out of a style). So, the first question is, should these "frames" be filtered in "filter styles" mode? I think they should not be filtered because it is same as if we filter tables with "filter styles" mode. If they should not be filtered completely, what should be the output under "filter styles" mode? I can think of two outputs: <code> <DIV STYLE="float: left; border: 1px solid #000000;"> <P CLASS="frame-contents">Hello, This is a frame as it is called on openoffice writer.</P> <P CLASS="frame-contents"><BR><BR> </P> <P CLASS="frame-contents">We have a problem with importing documents that contain this sort of frames.</P> <P CLASS="frame-contents"><BR><BR> </P> <P CLASS="frame-contents">This is the last paragraph</P> </DIV> <code> Height & Width are removed because when styles are filtered fonts sizes change and the size of the box might not be enough for the content to fit in. The other output we can have is: <code> <table> <tr> <td> <P CLASS="frame-contents">Hello, This is a frame as it is called on openoffice writer.</P> <P CLASS="frame-contents"><BR><BR> </P> <P CLASS="frame-contents">We have a problem with importing documents that contain this sort of frames.</P> <P CLASS="frame-contents"><BR><BR> </P> <P CLASS="frame-contents">This is the last paragraph</P> </td> </tr> </table> <code> So it becomes a single cell table, problem solved. So, wdyt? Thanks. - Asiri

16 years, 4 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r19209 - in platform: core/trunk/xwiki-core/src/main/resources web/trunk/standard/src/main/webapp/resources/js/xwiki/table web/trunk/standard/src/main/webapp/templates

by Vincent Massol

Note that since you've used the HTML macro using renderers may not output the live grid (only renderers that support HTML will be able to output some result). I've checked the html and all of it could be replaced by wiki syntax except for the select part. We could use wiki syntax everywhere and use some JS to inject the select in the HTML DOM afterwards. This would allow to output it easily. We currently have only 2 renderers that we use: xwiki syntax and xhtml and both support Raw events when the syntax is HTML. We can imagine that PDF, RTF renderers would also support it (it'll depend on how we implement it, if we use FOP it's fine but there's also a very simple way to implement a PDF renderer using itext but then I don't think if it can support HMTL fragments). We have a LaTex renderer that we currently don't use and this one won't work for example. This is just a thought for now. We just need to be aware of it for the future. We need to remember that using the HTML macro bypasses the rendering mechanism and thus generate non standard stuff. Thanks -Vincent On Apr 30, 2009, at 8:08 AM, jvelociter (SVN) wrote: > Author: jvelociter > Date: 2009-04-30 08:08:53 +0200 (Thu, 30 Apr 2009) > New Revision: 19209 > > Modified: > platform/core/trunk/xwiki-core/src/main/resources/ > ApplicationResources.properties > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/ > table/livetable.css > platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/ > table/livetable.js > platform/web/trunk/standard/src/main/webapp/templates/macros.vm > Log: > XWIKI-3705 Clean and enhance the javascript Live Table component > XWIKI-3706 Provide a velocity macro to automate the creation of live > tables > > * Added support for multiple pagination nodes (for example one on > top, and one under the table). Formatting of livetable.js > * Added the #livetable macro in macros.vm, that supports syntax 1.0 > and 2.0 > > > Modified: platform/core/trunk/xwiki-core/src/main/resources/ > ApplicationResources.properties > =================================================================== > --- platform/core/trunk/xwiki-core/src/main/resources/ > ApplicationResources.properties 2009-04-30 01:14:08 UTC (rev 19208) > +++ platform/core/trunk/xwiki-core/src/main/resources/ > ApplicationResources.properties 2009-04-30 06:08:53 UTC (rev 19209) > @@ -1612,14 +1612,26 @@ > xe.pagination.results=Results > xe.pagination.results.of=out of > xe.pagination.page=Page > +xe.pagination.page.next.title=Next Page > +xe.pagination.page.prev.title=Previous Page > > -xe.attachments.all.filename=Filename > -xe.attachments.all.page=Page > -xe.attachments.all.space=Space > -xe.attachments.all.date=Date > -xe.attachments.all.author=Author > -xe.attachments.all.type=Type > +xe.grid.loading=Loading... > > +xe.index.doc.name=Page > +xe.index.doc.space=Space > +xe.index.doc.date=Date > +xe.index.doc.author=Last Author > +xe.index.actions=Actions > +xe.index.emptyvalue= > + > +xe.index.attachments.filename=Filename > +xe.index.attachments.title=Page > +xe.index.attachments.space=Space > +xe.index.attachments.date=Date > +xe.index.attachments.author=Author > +xe.index.attachments.type=Type > +xe.index.attachments.emptyvalue= > + > xe.document.copy=Copy a document > xe.document.copying=Copying document > xe.document.copy.source=Source Document: > > Modified: platform/web/trunk/standard/src/main/webapp/resources/js/ > xwiki/table/livetable.css > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/ > table/livetable.css 2009-04-30 01:14:08 UTC (rev 19208) > +++ platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/ > table/livetable.css 2009-04-30 06:08:53 UTC (rev 19209) > @@ -46,7 +46,7 @@ > padding:0!important; > float: right; > } > -.controlPagination a{ > +.controlPagination div{ > position:absolute; > top:0; > left:0; > @@ -55,22 +55,25 @@ > overflow:hidden; > border:none; > } > -.controlPagination a.prevPagination , .controlPagination > a.noPrevPagination, .controlPagination > a.nextPagination, .controlPagination a.noNextPagination { > - background-image:url("$xwiki.getSkinFile('js/xwiki/table/img/ > navigation.png')"); > +.controlPagination div.prevPagination , .controlPagination > div.noPrevPagination, .controlPagination > div.nextPagination, .controlPagination div.noNextPagination { > + background-image:url("$xwiki.getSkinFile('icons/xwiki/pagination- > controls.png')"); > width: 21px; > height: 22px; > } > -.controlPagination a.prevPagination { > +.controlPagination div.prevPagination:hover, .controlPagination > div.nextPagination:hover { > + cursor:pointer; > +} > +.controlPagination div.prevPagination { > background-position:left top; > } > -.controlPagination a.noPrevPagination{ > +.controlPagination div.noPrevPagination{ > background-position:left bottom; > } > -.controlPagination a.nextPagination { > +.controlPagination div.nextPagination { > background-position:right top; > left: 21px; > } > -.controlPagination a.noNextPagination { > +.controlPagination div.noNextPagination { > background-position:right bottom; > left: 21px; > } > @@ -126,7 +129,7 @@ > background:#dddddd url("$xwiki.getSkinFile('icons/silk/ > bullet_arrow_down.gif')") no-repeat scroll right center; > } > thead.xwiki-grid-display-header th.asc { > - background:#dddddd url("$xwiki.getSkinFile('icons/silk/ > bullet_arrow_up.png')") no-repeat scroll right center; > + background:#dddddd url("$xwiki.getSkinFile('icons/silk/ > bullet_arrow_up.gif')") no-repeat scroll right center; > } > thead.xwiki-grid-display-header th.selected { > color:#4D4D4D; > > Modified: platform/web/trunk/standard/src/main/webapp/resources/js/ > xwiki/table/livetable.js > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/ > table/livetable.js 2009-04-30 01:14:08 UTC (rev 19208) > +++ platform/web/trunk/standard/src/main/webapp/resources/js/xwiki/ > table/livetable.js 2009-04-30 06:08:53 UTC (rev 19209) > @@ -4,14 +4,14 @@ > * XWiki namespace > */ > if (typeof XWiki == "undefined") { > - XWiki = new Object(); > + XWiki = new Object(); > } > > /** > * widgets namespace > */ > if (typeof XWiki.widgets == "undefined") { > - XWiki.widgets = new Object(); > + XWiki.widgets = new Object(); > } > > /** > @@ -35,7 +35,7 @@ > * @todo Make this a valid ARIA grid: http://www.w3.org/TR/aria-role/#structural > */ > initialize: function(url, domNodeName, handler, options) > - { > + { > // id of the root element that encloses this livetable > this.domNodeName = domNodeName; > > @@ -45,21 +45,23 @@ > this.displayNode = $(domNodeName + "-display") || $('display1'); > > if (typeof options == "undefined") { > - options = {}; > + options = {}; > } > > this.limit = options.limit || 10; > this.action = options.action || "view"; // FIXME check if this > can be removed safely. > > - if ($(domNodeName + '-pagination')) { > - this.paginator = new GridPagination(this, domNodeName + "- > pagination", options.maxPages || 10); > + // pagination > + var paginationNodes = $(this.domNodeName).select(".xwiki-grid- > pagination"); > + if (typeof paginationNodes != "undefined") { > + this.paginator = new GridPagination(this, paginationNodes, > options.maxPages || 10); > } > if ($(domNodeName + '-filters')) { > - // Ideally we should pass domNodeName + "-filters" as the filter > node instead of the whole display table, > - // so that the filters elements (input/selects) are retrieved > down this filter node > - // But right now this would break the RMUI since the checkbox to > switch from group view to user view > - // in the rights UI is outside this element. > - // FIXME > + // Ideally we should pass domNodeName + "-filters" as the > filter node instead of the whole display table, > + // so that the filters elements (input/selects) are retrieved > down this filter node > + // But right now this would break the RMUI since the checkbox > to switch from group view to user view > + // in the rights UI is outside this element. > + // FIXME > this.filter = new GridFilter(this, > this.displayNode.up("table")); > } > if ($(domNodeName + "-tagcloud")) > @@ -174,27 +176,27 @@ > * @param limit Maximum number of rows to display. > */ > displayRows: function(offset, limit) > - { > + { > var f = offset + limit - 1; > if (f > this.totalRows) f = this.totalRows; > var off = (this.totalRows > 0) ? offset : 0; > var msg = "<strong>" + off + "</strong> - <strong>" + f + "</ > strong> $msg.get('xe.pagination.results.of') <strong>" + > this.totalRows + "</strong>"; > var msg = msg.toLowerCase(); > - > + > this.limitsDisplay.innerHTML = > "$msg.get('xe.pagination.results') " + msg; > this.clearDisplay(); > > for (var i = off; i <= f; i++) { > if (this.fetchedRows[i]) { > - var elem = this.handler(this.fetchedRows[i], i, this); > + var elem = this.handler(this.fetchedRows[i], i, this); > this.displayNode.appendChild(elem); > document.fire("xwiki:livetable:newrow", { > - "row":elem, > - "table":this > - }); > + "row":elem, > + "table":this > + }); > } > } > - if (this.paginator) this.paginator.refreshPaginator(); > + if (this.paginator) this.paginator.refreshPagination(); > }, > > /** > @@ -239,7 +241,7 @@ > this.getRows(min, max - min + 1, offset, limit); > } > > - if(this.paginator) this.paginator.refreshPaginator(); > + if(this.paginator) this.paginator.refreshPagination(); > > return buff; > }, > @@ -291,7 +293,7 @@ > this.showRows(newoffset, this.limit); > } > > - if (this.paginator) this.paginator.refreshPaginator(); > + if (this.paginator) this.paginator.refreshPagination(); > }, > > /** > @@ -346,47 +348,63 @@ > * Helper class to display pagination > */ > var GridPagination = Class.create({ > - initialize: function(table, domNode, max) > + initialize: function(table, domNodes, max) > { > this.table = table; > - this.domNode = $(domNode); > + var self = this; > + this.pagesNodes = []; > + domNodes.each(function(elem){ > + self.pagesNodes.push(elem.down(".xwiki-grid-pagination- > content")); > + }); > this.max = max; > + $ > (this > .table.domNodeName).select("div.prevPagination").invoke("observe", > "click", this.gotoPrevPage.bind(this)); > + $ > (this > .table.domNodeName).select("div.nextPagination").invoke("observe", > "click", this.gotoNextPage.bind(this)); > }, > - refreshPaginator: function() > + refreshPagination: function() > { > - this.domNode.innerHTML = ""; > + var self = this; > + this.pagesNodes.each(function(elem){ > + elem.innerHTML = ""; > + }); > var pages = Math.ceil(this.table.totalRows / this.table.limit); > var currentMax = (!this.max) ? pages : this.max; > var currentPage = Math.floor( this.table.lastoffset / > this.table.limit) + 1; > var startPage = Math.floor(currentPage / currentMax) * > currentMax - 1; > // always display the first page > if (startPage>1) { > - this.domNode.appendChild(this.createPageLink(1, false)); > - if (startPage>2) { > - this.domNode.appendChild(document.createTextNode(" ... ")); > + this.pagesNodes.each(function(elem){ > + elem.insert(self.createPageLink(1, false)); > + }); > + if (startPage>2) { > + this.pagesNodes.invoke("insert", " ... "); > } > } > // display pages > - var i; > + var i; > for (i=(startPage<=0) ? 1 : startPage;i<=Math.min(startPage + > currentMax + 1, pages);i++) { > var selected = (currentPage == i) ? true : false > - this.domNode.appendChild(this.createPageLink(i, selected)); > - this.domNode.appendChild(document.createTextNode(" ")); > + this.pagesNodes.each(function(elem){ > + elem.insert(self.createPageLink(i, selected)); > + }); > + this.pagesNodes.invoke("insert", " "); > } > // alwyas display the last page. > if (i<pages) { > - if (i+1 < pages) { > - this.domNode.appendChild(document.createTextNode(" ... ")); > + if (i+1 < pages) { > + this.pagesNodes.invoke("insert", " ... "); > } > - this.domNode.appendChild(this.createPageLink(pages, false)); > + //this.pagesNodes.invoke("insert", pageSpan.clone()); > + this.pagesNodes.each(function(elem){ > + elem.insert(self.createPageLink(pages, false)); > + }); > } > }, > createPageLink:function(page, selected) { > - var pageSpan = new Element("span", > {'class':'pagenumber'}).update(page); > - if (selected) { > - pageSpan.addClassName("selected"); > + var pageSpan = new Element("span", > {'class':'pagenumber'}).update(page); > + if (selected) { > + pageSpan.addClassName("selected"); > } > - var self = this; > + var self = this; > pageSpan.observe("click", function(ev){ > self.gotoPage(ev.element().innerHTML); > }); > @@ -400,16 +418,16 @@ > var currentPage = Math.floor( this.table.lastoffset / > this.table.limit) + 1; > var prevPage = currentPage - 1; > if (prevPage > 0) { > - this.table.showRows(((parseInt(prevPage) - 1) * > this.table.limit) + 1, this.table.limit); > - } > + this.table.showRows(((parseInt(prevPage) - 1) * > this.table.limit) + 1, this.table.limit); > + } > }, > gotoNextPage: function() { > var currentPage = Math.floor( this.table.lastoffset / > this.table.limit) + 1; > var pages = Math.ceil(this.table.totalRows / this.table.limit); > var nextPage = currentPage + 1; > if (nextPage <= pages) { > - this.table.showRows(((parseInt(nextPage) - 1) * > this.table.limit) + 1, this.table.limit); > - } > + this.table.showRows(((parseInt(nextPage) - 1) * > this.table.limit) + 1, this.table.limit); > + } > } > }); > > > Modified: platform/web/trunk/standard/src/main/webapp/templates/ > macros.vm > =================================================================== > --- platform/web/trunk/standard/src/main/webapp/templates/macros.vm > 2009-04-30 01:14:08 UTC (rev 19208) > +++ platform/web/trunk/standard/src/main/webapp/templates/macros.vm > 2009-04-30 06:08:53 UTC (rev 19209) > @@ -1369,4 +1369,248 @@ > *# > #macro(editActionButton $action $resourceIdentifier) > #submitButton("action_${action}", $msg.get("core.shortcuts.edit.$ > {resourceIdentifier}"), $msg.get($resourceIdentifier)) > +#end > + > +#** > + * AJAX Live table that displays XWiki data. > + * > + * Example of usage, in syntax 2.0: > + * <code> > + * {{velocity}} > + * #set($columns = [ "_avatar", "first_name", "last_name", "email"]) > + * #set($columnsProperties = { > + * "first_name" : { "type" : "text" , "size" : 10, > "link" : "view"}, > + * "last_name" : { "type" : "text" , "size" : 10, > "link" : "view"}, > + * "email" : { "type" : "text" , "size" : 20, > "link" : "editor"}, > + * "_avatar" : { "type" : "none" , "size" : 20, > "link" : "none", "html" : "true", "sortable":false } > + * }) > + * #set($options = { "className":"XWiki.XWikiUsers", > + * "translationPrefix" : "xe.index.users.", > + * "tagCloud" : true, > + * "rowCount": 15 }) > + * #livetable("userstable" $columns $columnsProperties $options) > + * {{/velocity}} > + * </code> > + * > + * @param divid the id of the table div > + * @param collist the column list > + * @param colprops the columns properties > + * @param options the livetable options. > + *# > +#macro(livetable $divid $collist $colprops $options) > + ## > + ## SX deps. > + ## > + #set($ok = $xwiki.jsfx.use("js/xwiki/table/livetable.js", true)) > + #set($ok = $xwiki.ssfx.use("js/xwiki/table/livetable.css", true)) > + ## > + ## Options / defaults > + ## > + #if("$!options.translationPrefix" != "") #set($transprefix = > $options.translationPrefix) #else #set($transprefix = "") #end > + #if("$!options.selectedColumn" != "") #set($selectedColumn = > $options.selectedColumn) #end > + #if("$!options.defaultOrder" == "desc") #set($defaultOrder = > "desc") #else #set($defaultOrder = "asc") #end > + #if("$!options.rowCount" != "") #set($count = $options.rowCount) > #else #set($count = 15) #end > + #if("$!options.maxPages" != "") #set($maxPages = > $options.maxPages) #else #set($maxPages = 10) #end > + #if("$!options.selectedColumn" != "") #set($selectedColumn = > $options.selectedColumn) #end > + #if("$!options.callback" != "") #set($callback = > $options.callback) #end > + #if("$!options.tagCloud" == "" || $options.tagCloud == false) > #set($tagcloud=false) #else #set($tagcloud = true) #end > + #set($classname = "$!options.className") > + ## > + ## Columns informations > + ## > + #set($collist2 = "") > + #set($classparams = "") > + #foreach($colname in $collist) > + #if("$!selectedColumn" == "" && !$colname.startsWith("_")) > + #set($selectedColumn = $colname) > + #end > + #set($collist2 = "${collist2},${colname}") > + #set($propClassName = "") > + #set($propClassName = $colprops.get($colname).get("class")) > + #if($propClassName!="") > + #set($classparams = "${classparams}&${colname}_class=$ > {propClassName}") > + #end > + #end > + #set($collist2 = $collist2.substring(1)) > + #if("$!options.url" != "") > + #set($dataurl = $options.url) > + #elseif("$!options.resultPage" != "") > + #set($dataurl = > $xwiki.getURL($options.resultPage,"view","xpage=plain&transprefix=$ > {transprefix}&classname=${className}&collist=${collist2}$ > {classparams}") ) > + #else > + #set($dataurl = > $ > xwiki > .getURL("XWiki.LiveTableResults","view","xpage=plain&transprefix=$ > {transprefix}&classname=${classname}&collist=${collist2}$ > {classparams}")) > + #end > + ## > + ## HTML Table > + ## > + #if($doc.syntaxId == "xwiki/2.0") > +{{html}} > + #end > + #if($tagcloud) > + #set($ok = $xwiki.ssx.use("XWiki.TagCloud")) > + <div id="${divid}-tagcloud"> > + <div class="xwiki-grid-tagcloud"></div> > + </div> > + #end > + <table id="${divid}" class="xwiki-grid"> > + <tr> > + <td class="xwiki-grid-pagination" colspan="2"> > + <span id="${divid}-limits" class="xwiki-grid-limits"></span> > + <span id="${divid}-ajax-loader" class="xwiki-grid- > loader"><img src="$xwiki.getSkinFile('icons/xwiki/ajax-loader- > large.gif')" alt="$msg.get('xe.grid.loading')" title="" /> > $msg.get("xe.grid.loading")</span> > + <span class="controlPagination"> > + <div title="$msg.get('xe.pagination.page.prev.title')" > class="prevPagination"></div> > + <div title="$msg.get('xe.pagination.page.next.title')" > class="nextPagination"></div> > + </span> > + <span class="pagination"> > + <span id="${divid}-pagination-text" class="xwiki-grid- > pagination-text">$msg.get("xe.pagination.page")</span> > + <span id="${divid}-pagination" class="xwiki-grid- > pagination-content" ></span> > + </span> > + </td> > + </tr> > + <tr> > + <td class="xwiki-grid-display-container"> > + <table class="xwiki-grid-display"> > + <thead class="xwiki-grid-display-header"> > + <tr> > + #foreach($colname in $collist) > + #set($colprop = $colprops.get($colname)) > + #if("$!colprop.sortable" == "" || $colprop.sortable ! > = false) > + #set($isSortable = true) > + #else > + #set($isSortable = false) > + #end > + <th class="xwiki-grid-display-header-text > #if($isSortable)sortable#end #if($colname == $selectedColumn) > selected $defaultOrder #elseif($isSortable) asc #end" > #if($isSortable)rel="${colname}"#end #if("$!colprop.type"=="hidden") > style="display: none" #end>$msg.get("${transprefix}${colname}")</th> > + #end > + </tr> > + <tr class="xwiki-grid-display-filters"> > + #foreach($colname in $collist) > + #set($colprop = $colprops.get($colname)) > + #if("$!colprop.filterable" == "" || > $colprop.filterable != false) > + #set($isFilterable = true) > + #else > + #set($isFilterable = false) > + #end > + #if("$!colprop.type"=="list" && $isFilterable) > + <td class="xwiki-grid-display-header-filter"> > + #if($colprop.get("class")) > + #set($propClassName = $colprop.get("class")) > + #else > + #set($propClassName = $className) > + #end > + #set($class = > $xwiki.getDocument($propClassName).getxWikiClass()) > + #set($list = "") > + #set($list = $class.get($colname).getListValues()) > + <select name='${colname}'><option value=''>none</ > option> > + #set($map = $class.get($colname).getMapValues()) > + #foreach($listitem in $list) > + <option value="$listitem"> > $map.get($listitem).getValue()</option> > + #end > + </select> > + </td> > + #elseif( ("$!colprop.type"=="text"||"$! > colprop.type"=="number") && $isFilterable) > + <td class="xwiki-grid-display-header-filter"><input > name="${colname}" type="text" #if($colprop.size!="") size="$ > {colprop.size}" #end title='$msg.get("xe.search.filters.title") > $msg.get("${transprefix}${colname}")' /></td> > + #elseif("$!colprop.type"=="hidden") > + #else > + <td class="xwiki-grid-display-header-filter"></td> > + #end > + #end > + </tr> > + </thead> > + <tbody id="${divid}-display" class="xwiki-grid-display- > body"><tr><td> </td></tr></tbody> > + </table> > + </td> > + </tr> > + <tr> > + <td class="xwiki-grid-pagination" colspan="2"> > + <span class="controlPagination"> > + <div title="$msg.get('xe.pagination.page.prev.title')" > class="prevPagination"></div> > + <div title="$msg.get('xe.pagination.page.next.title')" > class="nextPagination"></div> > + </span> > + <span class="pagination"> > + <span id="${divid}-pagination-text" class="xwiki-grid- > pagination-text">$msg.get("xe.pagination.page")</span> > + <span id="${divid}-pagination" class="xwiki-grid- > pagination-content" ></span> > + </span> > + </td> > + </tr> > + </table> > + <script type="text/javascript"> > + //<![CDATA[ > + #if($callback) > + var ta = new XWiki.widgets.LiveTable("$dataurl", "${divid}", > $callback ,{"maxPages":$maxPages}); > + #else > + var ta = new XWiki.widgets.LiveTable("$dataurl", "${divid}", > #livetablecallback($collist $colprops) ,{"maxPages":$maxPages}); > + #end > + //]]> > + </script> > + #if($doc.syntaxId == "xwiki/2.0") > +{{/html}} > + #end > +#end > + > +#** > + * Internal macro - Used by the livetable macro to generate a > JavaScript annonymous function > + * that is passed to the LiveTable object constructor. This is > function is dynamically written > + * according to columns properties passed to the livetable macro. > + * > + * @param collist the list of columns > + * @param colprops the columns properties > + * > + * @internal > + *# > +#macro(livetablecallback $collist $colprops) > +function (row, i, table) > +{ > + // This callback method code has been generated from velocity. > + var tr = new Element("tr"); > + #foreach($colname in $collist) > + // $colname > + #set($colprop = $colprops.get($colname)) > + #if("$!colprop.type"!="hidden") > + #if($colname.indexOf("doc.")==0) > + #set($jscolname = $colname.replaceAll("doc.", "doc_")) > + #else > + #set($jscolname = $colname) > + #end > + #if("$!colprop.link"=="view"||"$!colprop.link"=="field"||"$! > colprop.link"=="auto"||"$!colprop.link"=="editor") > + var a = new Element("a"); > + #if("$!colprop.link"=="auto") > + a.href = (row.${jscolname}_url=="") ? row.doc_url : row.$ > {jscolname}_url; > + #elseif($colprop.link=="field") > + a.href = (row.${jscolname}_url=="") ? > "javascript:void(0)" : row.${jscolname}_url; > + #elseif($colprop.link=="editor") > + #if($colprop.get("class")) > + #set($propClassName = $colprop.get("class")) > + #else > + #set($propClassName = $className) > + #end > + a.href = "javascript:void()"; > + #else > + a.href = row.doc_url; > + #end > + #if($colprop.html && $colprop.html==true) > + a.innerHTML = row.${jscolname}; > + #else > + a.update(row.${jscolname}); > + #end > + var fieldel = new Element("td"); > + fieldel.observe("click", function(event){ > + var tag = event.element().down("a"); > + editProperty(row.page, "${propClassName}", "${colname}", > function(value) { tag.innerHTML = value}); > + }); > + fieldel.className = "${jscolname} link${colprop.link} type$! > {colprop.type}"; > + fieldel.appendChild(a); > + tr.appendChild(fieldel); > + #else > + var fieldel = document.createElement('td'); > + fieldel.className = "${jscolname} link${colprop.link} type$! > {colprop.type}"; > + #if($colprop.html && $colprop.html==true) > + fieldel.innerHTML = row.${jscolname}; > + #else > + fieldel.update(row.${jscolname}); > + #end > + tr.appendChild(fieldel); > + #end > + #end > + #end > + return tr; > +} > #end > \ No newline at end of file > > _______________________________________________ > notifications mailing list > notifications(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/notifications

16 years, 4 months

2
4
0 0

Re: [xwiki-devs] [xwiki-notifications] r19193 - enterprise/branches/xwiki-enterprise-1.8

by Vincent Massol

On Apr 29, 2009, at 6:24 PM, jvelociter (SVN) wrote: > Author: jvelociter > Date: 2009-04-29 18:24:27 +0200 (Wed, 29 Apr 2009) > New Revision: 19193 > > Modified: > enterprise/branches/xwiki-enterprise-1.8/pom.xml > Log: > Locking down administration application version to 1.10 since > changes in 1.11-SNAPSHOT are not compatible with core/web 1.8 > > > Modified: enterprise/branches/xwiki-enterprise-1.8/pom.xml > =================================================================== > --- enterprise/branches/xwiki-enterprise-1.8/pom.xml 2009-04-29 > 16:13:28 UTC (rev 19192) > +++ enterprise/branches/xwiki-enterprise-1.8/pom.xml 2009-04-29 > 16:24:27 UTC (rev 19193) > @@ -57,7 +57,7 @@ > <platform.core.version>1.8-SNAPSHOT</platform.core.version> > <platform.web.version>1.8-SNAPSHOT</platform.web.version> > <platform.panels.version>1.20-SNAPSHOT</platform.panels.version> > - <platform.administration.version>1.11-SNAPSHOT</ > platform.administration.version> > + <platform.administration.version>1.10</ > platform.administration.version> would be great to add the commit comment as an xml comment here.... ;) -Vincent > > <platform.scheduler.version>1.8-SNAPSHOT</ > platform.scheduler.version> > <platform.watchlist.version>1.15-SNAPSHOT</ > platform.watchlist.version> > <platform.blog.version>1.4-SNAPSHOT</platform.blog.version>

16 years, 4 months

2
1
0 0

[xwiki-devs] xwiki videos

by walido

Hi, i would like to have videos-tutorials in my xwiki, pages like: http://enterprise.xwiki.org/xwiki/bin/view/UserGuide/ and http://enterprise.xwiki.org/xwiki/bin/view/UserGuide/EditVideo to be able to display swf files attached in the xwiki should i edit the page and add code like: [CODE] [/CODE] thanks for your help -- View this message in context: http://n2.nabble.com/xwiki-videos-tp2740767p2740767.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years, 4 months

1
0
0 0

[xwiki-devs] Status of OpenSocial specs and implementations (Shindig) for v0.8 and v0.9 versions

by Anamaria Stoica

Hi, I have made a little research about the current status of the OpenSocial specs and implementations (Shindig) for v0.8 and v0.9 versions. My findings resume to the following: Supported version by OpenSocial Containers: All OpenSocial containers listed on http://wiki.opensocial.org/index.php?title=Containers use at most version v0.8 Container Compliance Tests: A nice tool to check the compliance of the existing containers (including Shindig) against the open social specs is http://opensocial-compliance.appspot.com/. The test suits available are mostly for version v0.7 of the specs, and the test results are generated using the Compliance Gadget ( http://code.google.com/p/opensocial-resources/wiki/ComplianceTests) (all tests with priority P0 must pass in order for a container to be spec compliant). Note that a gadget for testing version v0.8 is available but there are no tests submitted by the containers (except one). v0.9 status: The final publication of the v0.9 version has been made on April 4th (2009), which is the last step in the OpenSocial Spec Process ( http://wiki.opensocial.org/index.php?title=Specification_Process). This page reflects the current status http://wiki.opensocial.org/index.php?title=Spec_Changes#Current_Status_At_a…. Other resources: Open Social Specification -- Implementing Version 0.9 http://sites.google.com/site/opensocialdraft/Home Open Social Specification -- Implementing Version 0.8.1 http://www.opensocial.org/Technical-Resources/opensocial-spec-v081#TOC-Comp… Release notes for v0.9 http://www.opensocial.org/Technical-Resources/opensocial-spec-v09/OpenSocia…: This page lists the improvements added by v0.9, many very helpful, like: - OpenSocial Templates and OpenSocial Markup Language - simplified JS API - proxied content - data pipelining - albums and media items - formal definition of the fetch/cache/invalidate model - IS_FRIENDS_WITH and set of mutual friends - etc. Applications and Gadgets: As v0.9 was just launched and all containers out there support v0.8, Applications and Gadgets are also implemented using the v0.8 version of the specs. New apps implementing the v0.9 will appear as containers also start implementing the new specs. Status of Shindig: Shindig includes all JavaScript APIs as described in OpenSocial API Reference ( http://www.opensocial.org/Technical-Resources/opensocial-spec-v08/opensocia…) and Gadgets API Reference ( http://www.opensocial.org/Technical-Resources/opensocial-spec-v08/gadgets-r…). (versions 0.8) They are currently implementing the v0.9 specs. See the correspondence between Shindig versions and OpenSocial Spec versions here : http://cwiki.apache.org/confluence/display/SHINDIG/Index;jsessionid=2AAEBC0… By integrating Shindig we would support whatever version of the OpenSocial specs they are supporting. Next steps: Besides continuing to read about OpenSocial and Shindig, as next steps I was thinking of trying to follow the tutorial on how to integrate shindig with your site ( http://cwiki.apache.org/confluence/display/SHINDIG/The+rough+guide+to+deplo… ) and check out the example OpenSocial applications based on Java/PHP Shindig : SocialSite(https://socialsite.dev.java.net/) and maybe Partuza( http://code.google.com/p/partuza/). Thanks, Anamaria

16 years, 4 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r19186 - platform/core/branches/xwiki-core-1.8/xwiki-officeimporter/src/main/java/org/xwiki/officeimporter/internal/openoffice

by Sergiu Dumitriu

asiri (SVN) wrote: > Author: asiri > Date: 2009-04-29 11:14:28 +0200 (Wed, 29 Apr 2009) > New Revision: 19186 > > Modified: > platform/core/branches/xwiki-core-1.8/xwiki-officeimporter/src/main/java/org/xwiki/officeimporter/internal/openoffice/DefaultOpenOfficeServerManager.java > Log: > XWIKI-3721: Starting an already started openoffice server should be prohibited > Shouldn't the UNKNOWN state also be considered, like: if (ServerState.UNKNOWN != currentState && ServerState.RUNNING != currentState) > - if (ServerState.UNKNOWN != currentState) { > + if (ServerState.RUNNING != currentState) { -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 4 months

2
4
0 0

[xwiki-devs] It's translation time again :-)

by Guillaume Lerouge

Hi, The XWiki translation tool located at http://l10n.xwiki.org/ has been upgraded yesterday. Starting today, new message strings are automatically loaded into the translation tool every night at 2:00 am Paris time. This means that whenever a developer commits a new portion of code that requires to be translated, it will show up on http://l10n.xwiki.org/ the next day. The immediate effect of this change is that approximately 120 new messages to translate have been added for XWiki Enterprise since yesterday. Some of the languages that used to be finished (such as german, romanian or spanish) are no longer complete. You can check the actual numbers here: http://l10n.xwiki.org/xwiki/bin/view/XE/XWikiCoreResources Additionally, some contributions have not been reviewed yet. Reviewing translations helps finding & fixing typos and other mistakes. It would be great if members from the community could look at it and review translations where applicable. Since we're close to the release date of XE 1.8.3 (and soon XE 1.9 M2) it would be awesome if some of you guys could update the tool with missing translations and reviews. I'm done with French already, 15 languages to go ;-) Many thanks in advance on behalf of the community, Guillaume -- Guillaume Lerouge Product Manager - XWiki Skype ID : wikibc http://guillaumelerouge.com/

16 years, 4 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r19183 - in platform/core/trunk/xwiki-officeimporter: . src/main/java/org/xwiki/officeimporter/internal/openoffice

by Sergiu Dumitriu

asiri (SVN) wrote: > Author: asiri > Date: 2009-04-29 09:52:15 +0200 (Wed, 29 Apr 2009) > New Revision: 19183 > > Modified: > platform/core/trunk/xwiki-officeimporter/pom.xml > platform/core/trunk/xwiki-officeimporter/src/main/java/org/xwiki/officeimporter/internal/openoffice/DefaultOpenOfficeServerManager.java > Log: > XWIKI-3711: Upgrade officeimporter to use jodconverter-3.0-beta-2 > Could this port be taken from a configuration? I don't like magic numbers. > + OfficeConnectionMode connectionMode = OfficeConnectionMode.socket(8100); -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 4 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r19164 - xoffice/trunk/xword/XWikiLib/Clients

by Sergiu Dumitriu

fciubotaru (SVN) wrote: > Author: fciubotaru > Date: 2009-04-28 18:39:39 +0200 (Tue, 28 Apr 2009) > New Revision: 19164 > > Modified: > xoffice/trunk/xword/XWikiLib/Clients/XWikiHTTPClient.cs > xoffice/trunk/xword/XWikiLib/Clients/XWikiXMLRPCClient.cs > Log: > XOFFICE-67 Implement the XmlRpc client using the CookComputing proxy > Modified: xoffice/trunk/xword/XWikiLib/Clients/XWikiXMLRPCClient.cs > =================================================================== > --- xoffice/trunk/xword/XWikiLib/Clients/XWikiXMLRPCClient.cs 2009-04-28 15:46:05 UTC (rev 19163) > +++ xoffice/trunk/xword/XWikiLib/Clients/XWikiXMLRPCClient.cs 2009-04-28 16:39:39 UTC (rev 19164) > @@ -2,20 +2,52 @@ This should be configurable, since not all instances use /xwiki/ > + private const string XML_RPC_PATH = "/xwiki/xmlrpc"; Typo: > + /// <param name="password">The passowrd used to authenticate.</param> You forgot to implement this: > + /// <summary> > + /// G > + /// </summary> > + /// <param name="docName"></param> > + /// <returns></returns> > public System.IO.Stream GetWikiPageAsPlainHTML(string docName) > { > throw new NotImplementedException(); > } -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 4 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r19162 - platform/core/trunk/xwiki-core/src/main/resources

by Vincent Massol

Warning, warning... The merge is wrong.... I had made some changes, see below On Apr 28, 2009, at 5:46 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2009-04-28 17:46:00 +0200 (Tue, 28 Apr 2009) > New Revision: 19162 > > Modified: > platform/core/trunk/xwiki-core/src/main/resources/ > ApplicationResources_fr.properties > Log: > XWIKI-3718: Update french translations > > Modified: platform/core/trunk/xwiki-core/src/main/resources/ > ApplicationResources_fr.properties > =================================================================== > --- platform/core/trunk/xwiki-core/src/main/resources/ > ApplicationResources_fr.properties 2009-04-28 14:29:14 UTC (rev 19161) > +++ platform/core/trunk/xwiki-core/src/main/resources/ > ApplicationResources_fr.properties 2009-04-28 15:46:00 UTC (rev 19162) [snip] > -XWiki.XWikiPreferences_smtp_server=Serveur > -XWiki.XWikiPreferences_smtp_port=Port > +XWiki.XWikiPreferences_smtp_server=Serveur SMTP This is not correct for example. There are other places too probably. You need to check the merge. Thanks -Vincent

16 years, 4 months

1
0
0 0

[xwiki-devs] In-wiki macros : generic wiki macro, or bridged script macros or selectable implementation ?

by Jerome Velociter

Hi devs, I'm going to continue the work on allowing users to write syntax 2.0 macros inside the wiki (http://jira.xwiki.org/jira/browse/XWIKI-3213) We have several implementations possible for this: 1. Having only one generic wiki macro implementation. This means macro authors will have to call explicitly the velocity macro inside if they need velocity scripting (same for other script languages) * Pros: - You can use wiki syntax in your macro. This is cool, it enables doing things like wikipedia templates (http://en.wikipedia.org/wiki/Help:Template) - We can easily provide the GWT-WYSIWYG to macro authors. This is an idea I like - It sound pretty natural to do it this way * Cons: - We'll have to put macro parameters in the XWiki context so that they are available to all script macros used in the macro. It means authors will have to refer to parameters using $context.get("parameterName") instead of $parameterName that would be doable with 2. 2. Writing one implementation per script language. This means authors will create a velocity macro and will write directly velocity code in the code are of the macro. * Pros: - Parameters don't need to be passed in the XWiki context (at least I think, if I'm wrong please explain me/us why) * Cons: - We'll have several XWiki classes, one per supported scripting language (XWiki.VelocityMacroClass, XWiki.GroovyMacroClass, etc.) - We cannot use wiki syntax in any implementation, so we cannot do the wikipedia templates-like thing 3. Keep for ourselves the ability to chose from the wiki the implementation class of the macro, but default on 1. the generic script macro. This means we will have a "class" field in the XWiki.MacroClass which allows to chose which implementation should be the code rendered against. If we do that I think this field should be hidden in the class sheet, and only be accessible using the object editor. This is similar to the way Scheduler Job objects works right now. * Pros: - Best of both world, we can have 1. and 2. - Leaves open the door for new macros implementations we could want in the future, or that developers would want just for their wiki * Cons: - Probably a little more code to handle that Right now, I tend to think we should do 3. with only one implementation available at first, being the generic wiki macro described in 1. WDYT ? Thanks in advance for your feedback. Cheers, Jerome.

16 years, 4 months

2
1
0 0

Re: [xwiki-devs] [xwiki-users] Links, WYSIWYG 2.0 (1.8.2)

by Anca Paula Luca

hel-o wrote: > Hi, > > the link dialog works much better than in 1.8.1, but one thing i found: > > i don't use the space for the page parent when i add the parent manually > (which i had to, since it wasn't added automatically in the new syntax) > because i found, that it's not needed to work (as it is in links when the > link is in the same space). > > Now when i want to create a link to a wiki-page i get the tree-view (which > is great) but it seems i cant see all those pages where no space is > provided. Hi Hel, thanks for reporting this behaviour! Of what I experimented just now, this seems to be caused by the REST API (used by the tree) for getting pages and the way it uses the passed "parent" parameter. Specifically, it does not interpret the value of the document parent field wrt the document's space. I see 2 solutions: 1/ either we change the panel to set the parent field to a fully qualified name (when a user inserts only a document name in the parent field, we append the space) 2/ either we fix the REST API. Solution 1 might cause problems when it will come to multiwikis, when the parent can be prefixed by the wiki name as well (wiki:Space.Page). Or: 3/ we change the parent-child relation in the explorer tree so that we make it survive such situations. Happy coding, Anca Luca > > hel. > > > > ----- > ---- > hel(a)hel.at >

16 years, 4 months

1
0
0 0

[xwiki-devs] [Proposal] Inline mode for XWiki Syntax 2.0

by Vincent Massol

Hi, We need to have automatic inline edit mode for XWiki Syntax 2.0 (http://jira.xwiki.org/jira/browse/XWIKI-2891) I'd like to implement this quickly since it prevents to use the xwiki syntax 2.0 as the default syntax (for ex if you create a user in 2.0 syntax and click edit you'll edit it in wysiwyg mode instead of inline mode). A quick solution I have: * Use the XWikiDocument template field to set the sheet to use * When a page has the template field set, when the user clicks on the edit button it goes automatically in inline edit mode * Add a new field in the information edit panel to set the template (only for advanced users I think) WDYT? Thanks -Vincent

16 years, 4 months

6
19
0 0

Re: [xwiki-devs] [xwiki-notifications] r19154 - in platform/core/trunk/xwiki-rendering: . xwiki-rendering-tests/src/test/java/org/xwiki/rendering xwiki-rendering-tests/src/test/resources/group

by Vincent Massol

On Apr 28, 2009, at 2:04 PM, tmortagne (SVN) wrote: > Author: tmortagne > Date: 2009-04-28 14:04:43 +0200 (Tue, 28 Apr 2009) > New Revision: 19154 > > Added: > platform/core/trunk/xwiki-rendering/xwiki-rendering-tests/src/test/ > resources/group/group11.test I'd have put put in the same test file we already have for testing parameters for groups (ie group9.test). Otherwise it doesn't sounds obvious why and we should add some comments anyway in group9.test saying that we test group parameters. [snip] Thanks -Vincent

16 years, 4 months

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs