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

by Suhas Prakash

Hi, There is a note on Tags and it further goes on to say how to create Structured tags. I'm not able to get the tags in that form. Can anyone please tell me how I can have tags to be displayed in a check box as shown in this link <http://http://www.xwiki.org/xwiki/bin/view/UserGuide/Tags>. With Thanks & Regards, Suhas.

17 years, 11 months

1
0
0 0

[xwiki-devs] [Panels/Widgets] Use wiki panels objects in page

by Thomas Mortagne

Hi, For XEM and statistics needs, Laurent designed a nice "in page" style CSS for panels to be able to use them to display informations in a page. Based on that I made a #panelLayout macro that take number of columns and list of panels to print and construct a very simple "Netvibes" like look. You can view an example here : http://sandbox.xwiki.org/xwiki/bin/view/TestPanels/Layout2. The current macro/CSS support from 1 to 5 columns, take all available with and redistribute for each column by percent values. I would like to add this feature in xwiki-web-standard 1.2 but also in 1.1.2 as XEM is based on xwiki-platform 1.1.* WDYT ? Regards, -- Thomas Mortagne

17 years, 11 months

1
0
0 0

[xwiki-devs] Error in saving the changes

by anuj sharma

Note: forwarded message attached. ANUJ SHARMA. --------------------------------- Download prohibited? No problem. CHAT from any browser, without download.

17 years, 11 months

1
0
0 0

Re: [xwiki-devs] [Proposal][UI] Top menu refactoring

by goldring, richard

Why FILE? - why not call the menu PAGE because that's what it is - it's not a FILE. -----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of Jean-Vincent Drean Sent: 10 October 2007 11:15 To: XWiki Developers Subject: Re: [xwiki-devs] [Proposal][UI] Top menu refactoring 2007/10/10, jerome(a)xwiki.com <jerome(a)xwiki.com>: > > * With the space we gained from "rename" and "copy", I think we can afford > a whole "Whatch" menu item, that will contain "Watch this page", "Watch > this space" and possibly "Watch settings..." for administrators. (And by > the way, it allow, if the notification feature is disabled for some reason > on a wiki, not to impact other menu lists - but I don't know if this > disable notification feature will be) You'll like my last proposal ;) http://www.xwiki.org/xwiki/bin/view/Design/RefactorActionMenu#H12M228proposa l32CAKAyouthoughtyouwereinawebapp3F29 > * I like the "Access Right" in the "Edit" menu, but that's maybe juste me :) Yes, may be ;) JV. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail is confidential. It may also be legally privileged. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. We may monitor all e-mail communications through our networks. If you have received this e-mail in error, please inform us immediately on +44 (0) 1749 672081 and delete it and all copies from your system. We accept no responsibility for changes to any e-mail which occur after it has been sent. Attachments to this e-mail may contain software viruses which could damage your system. We therefore recommend you virus-check all attachments before opening. A business of Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. 868273

17 years, 11 months

4
7
0 0

[xwiki-devs] [Package plugin] Export documents with withVersions=false

by Thomas Mortagne

Hi all, The packager internal plugin take care if import/export of XAR. It also can be configured and one of theses options is "withVersion". In export mode this options just indicate that the document history is included in export or not. In fact this option is really used in XWikiDocument.toXMLDocument(boolean, boolean, boolean, boolean, XWikiContext). What I dont understand is why this option did not also reset or delete all version related document's parameters : "version" and "creator", "author", "contentAuthor", "creationDate", "date", "contentUpdateDate" (and maybe more I forget) that are also related to version for me. I would like to add a "if withVersion=true" for all theses values. WDYT ? Regards, -- Thomas Mortagne

17 years, 11 months

5
9
0 0

[xwiki-devs] PS: Hook mechanism for XWiki ?

by jvivien.m2 jvivien.m2

and it would also be really cool if i could intercept import events. Though it could be very simple, since I guess I just have to modify the script for the 'import' admin page. -- Jean-Vivien MAURICE Elève Ingénieur Informatique et Gestion, Polytech'Montpellier (ISIM) E-mail : jvivien.m2(a)wanadoo.fr Tél. : 0046 7 62 33 20 46 Skype : jean.vivien

17 years, 11 months

2
1
0 0

[xwiki-devs] Error saving..

by anuj sharma

Hi everyone, Error while giving global access rights,importing pages and saving panel layout I have installed "xwiki-enterprise-manager-web-1.0-milestone-1" and after all set up i am getting error 1) Importing XWiki.XWikiPreferences 2) Saving Panel Layout http://localhost:9080/xwiki/bin/view/Panels/PanelLayoutUpdate?xpage=plain&l… SimpleLog4JLogSystem:logVelocityMessage:154 - Method save threw exception for reference $prefsdoc in template Panels.PanelLayoutUpdate at [26,12] org.apache.velocity.exception.MethodInvocationException: Invocation of method 'save' in class com.xpn.xwiki.api.Document threw exception com.xpn.xwiki.XWikiException: Error number 3201 in 3: Exception while saving document XWiki.XWikiPreferences Wrapped Exception: could not update: [com.xpn.xwiki.doc.XWikiDocumentArchive#104408758] @ Panels.PanelLayoutUpdate[26,22] at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:286) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.value(ASTReference.java:419) at org.apache.velocity.runtime.parser.node.ASTExpression.value(ASTExpression.java:73) at org.apache.velocity.runtime.parser.node.ASTSetDirective.render(ASTSetDirective.java:125) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:88) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74) at org.apache.velocity.runtime.parser.node.ASTElseIfStatement.render(ASTElseIfStatement.java:93) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:107) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:240) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:143) at com.xpn.xwiki.render.XWikiVelocityRenderer.render(XWikiVelocityRenderer.java:91) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:222) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:154) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderText(DefaultXWikiRenderingEngine.java:125) at com.xpn.xwiki.render.DefaultXWikiRenderingEngine.renderDocument(DefaultXWikiRenderingEngine.java:117) at com.xpn.xwiki.doc.XWikiDocument.getRenderedContent(XWikiDocument.java:401) at com.xpn.xwiki.api.Document.getRenderedContent(Document.java:347) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245) at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:203) at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:294) at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:74) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:107) at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:318) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:240) at com.xpn.xwiki.render.XWikiVelocityRenderer.evaluate(XWikiVelocityRenderer.java:143) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1271) at com.xpn.xwiki.XWiki.parseTemplate(XWiki.java:1240) at com.xpn.xwiki.web.Utils.parseTemplate(Utils.java:94) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:157) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414) at javax.servlet.http.HttpServlet.service(HttpServlet.java:690) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) Caused by: com.xpn.xwiki.XWikiException: Error number 3201 in 3: Exception while saving document XWiki.XWikiPreferences Wrapped Exception: could not update: [com.xpn.xwiki.doc.XWikiDocumentArchive#104408758] at com.xpn.xwiki.store.XWikiHibernateStore.saveXWikiDoc(XWikiHibernateStore.java:317) at com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:97) at com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:91) at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:953) at com.xpn.xwiki.api.Document.saveDocument(Document.java:1488) at com.xpn.xwiki.api.Document.save(Document.java:1455) at com.xpn.xwiki.api.Document.save(Document.java:1449) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:295) at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:245) ... 58 more 3) and saving global access rights Error number 3201 in 3: Exception while saving document XWiki.XWikiPreferences Wrapped Exception: could not update: [com.xpn.xwiki.doc.XWikiDocumentArchive#104408758] com.xpn.xwiki.XWikiException: Error number 3201 in 3: Exception while saving document XWiki.XWikiPreferences Wrapped Exception: could not update: [com.xpn.xwiki.doc.XWikiDocumentArchive#104408758] at com.xpn.xwiki.store.XWikiHibernateStore.saveXWikiDoc(XWikiHibernateStore.java:317) at com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:97) at com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:91) at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:953) at com.xpn.xwiki.web.SaveAction.save(SaveAction.java:113) at com.xpn.xwiki.web.SaveAction.action(SaveAction.java:122) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:147) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) Wrapped Exception: java.sql.SQLException: setString can only process strings of less than 32766 chararacters at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227) at oracle.jdbc.driver.OraclePreparedStatement.setStringInternal(OraclePreparedStatement.java:4746) at oracle.jdbc.driver.OraclePreparedStatement.setString(OraclePreparedStatement.java:4717) at org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:131) at org.apache.commons.dbcp.DelegatingPreparedStatement.setString(DelegatingPreparedStatement.java:131) at org.hibernate.type.StringType.set(StringType.java:26) at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:85) at org.hibernate.type.NullableType.nullSafeSet(NullableType.java:58) at org.hibernate.persister.entity.AbstractEntityPersister.dehydrate(AbstractEntityPersister.java:1826) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2172) at org.hibernate.persister.entity.AbstractEntityPersister.updateOrInsert(AbstractEntityPersister.java:2118) at org.hibernate.persister.entity.AbstractEntityPersister.update(AbstractEntityPersister.java:2374) at org.hibernate.action.EntityUpdateAction.execute(EntityUpdateAction.java:84) at org.hibernate.engine.ActionQueue.execute(ActionQueue.java:243) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:227) at org.hibernate.engine.ActionQueue.executeActions(ActionQueue.java:141) at org.hibernate.event.def.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:296) at org.hibernate.event.def.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:27) at org.hibernate.impl.SessionImpl.flush(SessionImpl.java:1009) at org.hibernate.impl.SessionImpl.managedFlush(SessionImpl.java:356) at org.hibernate.transaction.JDBCTransaction.commit(JDBCTransaction.java:106) at com.xpn.xwiki.store.XWikiHibernateBaseStore.endTransaction(XWikiHibernateBaseStore.java:611) at com.xpn.xwiki.store.XWikiHibernateBaseStore.endTransaction(XWikiHibernateBaseStore.java:585) at com.xpn.xwiki.store.XWikiHibernateStore.saveXWikiDoc(XWikiHibernateStore.java:307) at com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:97) at com.xpn.xwiki.store.XWikiCacheStore.saveXWikiDoc(XWikiCacheStore.java:91) at com.xpn.xwiki.XWiki.saveDocument(XWiki.java:953) at com.xpn.xwiki.web.SaveAction.save(SaveAction.java:113) at com.xpn.xwiki.web.SaveAction.action(SaveAction.java:122) at com.xpn.xwiki.web.XWikiAction.execute(XWikiAction.java:147) at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431) at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236) at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196) at org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) at javax.servlet.http.HttpServlet.service(HttpServlet.java:710) at javax.servlet.http.HttpServlet.service(HttpServlet.java:803) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at com.xpn.xwiki.web.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:117) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:584) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) ANUJ SHARMA. --------------------------------- 5, 50, 500, 5000 - Store N number of mails in your inbox. Click here.

17 years, 11 months

1
0
0 0

[xwiki-devs] Hook mechanism for XWiki ?

by jvivien.m2 jvivien.m2

Hi all, I would like to know if there is a way to add behaviour to a standard xwiki installation, like a java plugin with a function that would be executed every time a document/object is created/modified/deleted in xwiki. Thanks a lot ! Keep up the good work -- Jean-Vivien MAURICE Elève Ingénieur Informatique et Gestion, Polytech'Montpellier (ISIM) E-mail : jvivien.m2(a)wanadoo.fr Tél. : 0046 7 62 33 20 46 Skype : jean.vivien

17 years, 11 months

2
1
0 0

[xwiki-devs] xwiki favicon

by haiko van der Schaaf

Hi there, I set up a xwiki for my company and wanted t o change the tomcat favicon so I made my own xwiki favicon. I just want to share it. Maybe I nice thought for the next release. The icon is attached. Gr. Haiko van der Schaaf

17 years, 11 months

1
0
0 0

[xwiki-devs] [XEM][VOTE] Postpone XEM 1.0M2 and following

by Thomas Mortagne

Hi, XEM 1.0M1 version was suppose to be released on the 8th of October but cumulate one week late waiting for new right management API supposed to appear in XE 1.1.2 (and 1.2M2). Some works has been done in that delay that was supposed to be released after 1.0M2 (M3 and M4) so I propose to change XEM schedule to : - M2 : Monday the 22nd - M3 : Monday the 29th - RC1 : Monday the 5th of October - RC2 : Monday the 12th of October Here my +1 Regards, -- Thomas Mortagne

17 years, 11 months

4
5
0 0

[xwiki-devs] Fwd: An Experiment with GIT

by Vincent Massol

Interesting... After reading about distributed SCMs for some time now I think I'm ready to take the plugin and try some experiments as Jason as done. My only worry so far about using a tool like Git was about the tooling (in IDE, etc). Now that Jason as taken the plunge, I'll do some research on it too in the background. -Vincent Begin forwarded message: > From: Jason van Zyl <jason(a)maven.org> > Date: September 29, 2007 7:40:42 PM CEDT > To: Maven Developers List <dev(a)maven.apache.org> > Subject: An Experiment with GIT > Reply-To: "Maven Developers List" <dev(a)maven.apache.org> > > Hi, > > For anyone who wants to make changes to Maven but doesn't have > access I am going to setup a GIT repository to try and enable some > distributed development. After using GIT for about a week I'm > having a hard time using SVN but obviously we're not going to be > switching anytime soon. > > But for anyone who has patches or wants to try and work with me to > get changes in I am going to try this method of publishing Maven as > a GIT repository which will allow anyone to clone the repository > and work on any changes you like in a controlled way. Once you > clone you can commit changes to your own copy of Maven and do > whatever you like. Then in order for me to see your changes I can > simply pull from your originally cloned repository to a branch on > my side and merge. Merging is sooooooo easy with GIT. So easy in > fact that it makes you wonder how SVN got it so wrong and makes it > so painful compared to GIT. > > This is the model that the Linux kernel uses where anyone has a > real copy of the repository, they work as they like, creating > branches for features of what have you. > > I am trying this with Oleg Gusakov who has many ideas and is > helping me do some experiments with the artifact resolution system. > But anyone else who is interested in trying just let me know. This > document is the most helpful: > > http://utsl.gen.nz/talks/git-svn/intro.html > > And a little collection of things I have read about GIT: > > http://del.icio.us/jvanzyl/git > > It is so damn fast it is unbelievable. With the visual tool that > comes with it you can see the entire history of the project in a > few minutes. It is very, very cool. I simply cannot believe how > easy it is to merge bits from all over the place. My hope is that > this method being truly distributed means that people can work on > their branches in a way that's natural and we remove the immense > tedium working with patches. If you have something good, it's now > very easy for me to pull a branch from you and try it. If that > branch works it then takes me a second to merge it. I test and them > push back to subversion using the git-svn bridge. > > In the short term I really only want to try with a few people but > if you're keen, want to learn about GIT (which I highly, highly > recommend) then I will take your patches. I think any developer > here and anyone who has ever tried to contribute changes sees that > the JIRA+patch model is highly unworkable and bordering on > completely useless. JIRA might be fine to raise the issue but with > a reference to a GIT repository to pull from it will make life > infinitely easier. People who are not committers can work with > people that are in a way that resembles everyon being part of the > team. Dealing with patches just sucks ass and as a result we don't > look at them nearly as often as we should so I hope this can become > a model that enables people to contribute in a more effective way. > I'm going to try this with Oleg but I am highly hopeful. I will > help anyone who wants to try this as I see this as a way to truly > collaborate with the community. Down with JIRA+patches! All hail > JIRA+GIT! :-) > > Thanks, > > Jason

17 years, 11 months

5
4
0 0

[xwiki-devs] Announcing the XWiki Concerto research project

by Stéphane Laurière

Hi everyone, I don't think this news was shared with the community yet: XPertNet's team (http://www.xwiki.com) has been selected by the French Research Agency together with a set of partners for conducting a research project for adding P2P and mobility capabilities to XWiki. This project is called "XWiki Concerto". The objectives are the following: - design a fault tolerant P2P architecture for XWiki supporting large scale collaborative editing on a set of peers that synchronize their changes regularly using reconciliation algorithms, - support mobility work: off-line capabilities and UI dedicated to mobile handsets. This project will allow to design a P2P XWiki farm that will scale at much lower costs than classical solutions and will let XWiki users work offline and from handsets with limited capabilities. The set of partners are INRIA, ENST, Mandriva and EISTI. The project's web site is http://concerto.xwiki.com. INRIA teams include ECOO (Environments for COOperation) [1] and ATLAS [2]. ECOO team has expertise in reconciliation techniques, ATLAS has expertise in P2P databases. ENST team focuses on the mobility aspects. EISTI is bringing security expertise. XPertNet, Mandriva and INRIA will experiment with the solutions respectively in the context of the XWiki.com farm, the Mandriva Club wiki and the OW2 wiki. [1] http://www.loria.fr/equipes/ecoo/english/index.html [2] http://www.sciences.univ-nantes.fr/lina/ATLAS/ We already delivered a first version of specifications and use cases but it's in French: http://concerto.xwiki.com/xwiki/bin/download/Main/L2/xwikiconcerto-l2.pdf We're currently designing a set of complementary XWiki APIs. I'll send some proposals to the devs list in the next days. Your feedback will be most welcome. There will be many interesting synergies with XEclipse off-line work of course. That'd be good also to investigate about the eRCP capabilities http://www.eclipse.org/ercp/ Cheers Stéphane -- Stéphane Laurière slauriere(a)xwiki.com XWiki http://www.xwiki.com http://concerto.xwiki.com http://nepomuk.semanticdesktop.org

17 years, 11 months

1
0
0 0

[xwiki-devs] [Watch][Proposal] Insert a web module or/and inject conf in web.xml

by Jerome Velociter

Dear All, Currently XWiki Watch product has a "web" module that holds java sources for the GWT client application. The maven build then generate a war with : * gwt-compiled JS files (+ other resources) * the standard xwiki webapp war. I would like to propose to split that module into two "gwt" and "web" modules. The gwt module build would only take care of gwt compiling, and the web module would build the actual war. The advantage of this would be we can add stuff to our webapp (for example a future skin if we want one), and define our own web.xml. Overriding the web.xml would allow us to have gwt server code for Watch (for now Watch works only with client code + the xwiki gwt api. while it makes it easier for deploying, IMHO it has some limitations on the developer side). However, for this purpose (having specific gwt server code), I see another possibility : we inject some configuration in web.xml as we are doing with xwiki.cfg, thus letting us choose the XWikiService servlet implementation class. If I'm not wrong, this requires modifications in the xwiki configuration resources. Vincent can you tell us if it's stupid/possible/desirable ? Also, again if I'm not wrong, having a web module would allow us to define a jetty run profile, that could be usefull for developers. So my point would be then to : 1- Split the web module into gwt and web (on the same scheme as the curriki product) 2- Inject the XWikiService impl class in web.xml, so that we don't fully override the standard web existing one, and can benefit from its evolutions. Does it make sense ? WDYT ? Jérôme.

17 years, 11 months

1
0
0 0

[xwiki-devs] XEclipse Off-Line

by Asiri Rathnayake

Hi All, I've undertaken the task of implementing XEclipse off-line and thought I would start a thread with status updates (as told by Vincent). As of today I have implemented caching of documents into local repository. When the user navigates through the document hierarchy, each visited node is stored into the local repository. Also, all edits to documents are saved into local repository as well. To complete XEclipse off-line, following tasks need to be done, * Add an "off-line" flag to XWikiConnection and divert user actions into local repository when user is working off-line. * Add necessary routines to re-construct the document hierarchy using local repository. * Add a sync function to sync the above created hierarchy with remote server. * Make necessary changes to UI components. As you can see there is lot to be done. Due to my exams I won't be able to work on XEclipse for about 2-3 weeks (till 28th), but I will definitely get on with it after that. A big sorry about the missed dead-line (XEclipse Off-line was promised to deliver on 10th). Thanks. - Asiri

17 years, 11 months

6
13
0 0

Re: [xwiki-devs] [Proposal][UI] Top menu refactoring

by goldring, richard

Bookmarks/favourites - what a good idea! Perhaps with a favorites left hand flyout menu tree? Although you always have your browser bookmarks/favourites but this means you'd have access to your favourites independent of the PC or browser you were using. -----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of Jean-Vincent Drean Sent: 11 October 2007 01:18 To: XWiki Developers Subject: Re: [xwiki-devs] [Proposal][UI] Top menu refactoring 2007/10/11, Vincent Massol <vincent(a)massol.net>: > Hi, > > I've just reviewed this last proposal and here are my comments: > > * I'm -1 on naming the menu entry "File" unless someone convinces > me... Right now I don't understand the rationale. Why not call it > "Orange Juice"? ;) I'm -1 for "File" too, "Page seems more appropriate" > * I hate those Microsoft menu entries! ;) Ok so let's talk about mozilla menu entries then ;) > * Don't put CTRL+P in the menu (since the keys are different > depending on the OS) Ok > * Edit menu should be on the left since it's the most used menu I was waiting for someone to raise this one, I'm testing the proposal 3 on my local xwiki and I confirm that it's annoying for people accustomed to the edit at the left. > * Not sure why we're changing "Show" to "View". Show looks fine to me > and since it's been around for some time why change it? This proposal was an attempt of a more desktopish layout. (Page/Edit/View). BTW i never liked "Show" ;) > * I don't like the Watchlist menu entry. This is a very specific > application and I'm not sure why it gets its own menu entry compared > to other applications. Page/Edit/View wait for it.. Bookmarks -> File/Edit/View/Watchlist (since bookmark doesn't fit here). > * I'd be fine with keeping the current Edit and Show menus and > collapse the Delete, Rename and other actions into an "Actions" menu > (or "Other actions") -1 for the hodge-podge until we had discussed all the other options ;) JV. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail is confidential. It may also be legally privileged. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. We may monitor all e-mail communications through our networks. If you have received this e-mail in error, please inform us immediately on +44 (0) 1749 672081 and delete it and all copies from your system. We accept no responsibility for changes to any e-mail which occur after it has been sent. Attachments to this e-mail may contain software viruses which could damage your system. We therefore recommend you virus-check all attachments before opening. A business of Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. 868273

17 years, 11 months

2
1
0 0

[xwiki-devs] [Proposal][UI] Top menu refactoring

by Jean-Vincent Drean

Hi XWikiers! We currently have features planned for 1.2M2 with a common point : the xwiki top menu. Features : - New space admin UI : http://jira.xwiki.org/jira/browse/XWIKI-1780 [incomplete jira issue] - Email notifications (aka watchlist) : http://jira.xwiki.org/jira/browse/XWIKI-268 - RSS for spaces/pages : http://jira.xwiki.org/jira/browse/XWIKI-448 - Improve Admin.WebHome : http://jira.xwiki.org/jira/browse/XE-14 [I'll write later about this one] To address needs from those features we'll have to add entries in the top menu without breaking our "800x600 users" compatibility. We currently run out of place in this menu, I've made a proposal of refactoring here : http://www.xwiki.org/xwiki/bin/view/Design/Topmenurefactoring WDYT ? JV.

17 years, 11 months

5
17
0 0

Re: [xwiki-devs] [xwiki-notifications] r5354 - xwiki-products/xwiki-watch/trunk

by Vincent Massol

On Oct 10, 2007, at 8:40 AM, jvelociter (SVN) wrote: > Author: jvelociter > Date: 2007-10-10 17:40:51 +0200 (Wed, 10 Oct 2007) > New Revision: 5354 > > Modified: > xwiki-products/xwiki-watch/trunk/pom.xml > Log: > XWATCH-68 Added property for enterprise wiki version (needed by the > wiki module) > > > > Modified: xwiki-products/xwiki-watch/trunk/pom.xml > =================================================================== > --- xwiki-products/xwiki-watch/trunk/pom.xml 2007-10-10 15:34:16 > UTC (rev 5353) > +++ xwiki-products/xwiki-watch/trunk/pom.xml 2007-10-10 15:40:51 > UTC (rev 5354) > @@ -46,6 +46,7 @@ > <platform.tools.version>1.7-SNAPSHOT</platform.tools.version> > <platform.core.version>1.1-SNAPSHOT</platform.core.version> > <platform.web.version>1.1-SNAPSHOT</platform.web.version> > + <products.enterprise.wiki.version>1.1-SNAPSHOT</ > products.enterprise.wiki.version> I see that thomas has used: product.xe.version Would be better to all use the same property name. My preference goes to: product.enterprise.version (product.manager.version, product.watch.version, product.curriki.version, etc). WDYT? Thanks -Vincent

17 years, 11 months

3
2
0 0

[xwiki-devs] [VOTE] Commit rights to Fabio on XEclipse

by Stéphane Laurière

Hi all, I'd like to propose that Fabio becomes a committer on XEclipse. Fabio has created a first patch for XEclipse (connection persistence feature): http://jira.xwiki.org/jira/browse/XECLIPSE-28 and he has gained an expertise in Eclipse by creating the Eclipse PSEW prototype in the frame of the Nepomuk project [1]. He has also developed an XWiki library for indexing XWiki resources in RDF at [2], that we'll announce and discuss on the list in a separate message. PSEW is a generic metadata workbench for Eclipse. It integrates optionaly XEclipse, which makes it then possible to annotate XWiki documents from Eclipse using one or several ontologies. This lets you for example add private tags and personal comments to remote XWiki documents, or draw links between XWiki pages and some local files. The idea would be then to also let you publish some of these annotations to the public server if you feel like it, or to share them with others over a P2P protocol. In this context we'd like to help adding several features to XEclipse like storing various XWiki addresses in the user's preferences, displaying several XWiki trees, adding custom editors, classifying the resources by their types (all classes in a common folder, all Groovy scripts in another one etc.). Tharindu, Asiri, everyone, what do you think? Of course we would discuss with you the features we have in mind before committing them, and we'll use extension points in XEclipse whenever appropriate for not turning XEclipse into a bloated thing! Here's my +1 [1] http://nepomuk-eclipse.semanticdesktop.org/xwiki/bin/view/Main/PSEW [2] http://dev.nepomuk.semanticdesktop.org/repos/trunk/java/org.xwiki.aperture/ Cheers Stéphane -- Stéphane Laurière slauriere(a)xwiki.com XWiki http://www.xwiki.com http://concerto.xwiki.com http://nepomuk.semanticdesktop.org

17 years, 11 months

7
11
0 0

Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a set of criteria

by goldring, richard

Yes I've tried this, but XWiki doesn't execute this code it just displays: $doc.display($prop.name, "view", $obj) as if its just any other text on the page! What's happening? Why won't it execute? -----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of Erin Schnabel Sent: 09 October 2007 18:15 To: XWiki Developers Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a set of criteria try this: #set($obj = $bentrydoc.getObject("XWiki.ArticleClass")) $doc.display($prop.name, "view", $obj) On 10/9/07, goldring, richard <richard.goldring(a)uk.thalesgroup.com> wrote: > Jean-Vincent, > > I've developed this code for searching and then displaying the properties > and property values of an documents object - only the line indicated doesn't > display the properties value - any ideas how to do this? > > #set ($list = $xwiki.search("select doc.fullName from XWikiDocument doc, > BaseObject obj, StringProperty prop where doc.fullName=obj.name and > obj.className='XWiki.ArticleClass' and prop.id.id=obj.id and > prop.name='title' and prop.value like 'Art%'", 5, 0)) > > #foreach ($item in $list) > #set($bentrydoc = $xwiki.getDocument($item)) > > #set($class = $bentrydoc.getObject("XWiki.ArticleClass").xWikiClass) > $bentrydoc.name > <table border="1" cellspacing="0" cellpadding="2"> > #foreach($prop in $class.properties) > <tr> > <td> *${prop.prettyName}* </td> > <td>Value: $doc.display($prop.value)</td> <--- this line! > </tr> > #end > </table> > > Regards, > > Richard > > -----Original Message----- > From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of > Jean-Vincent Drean > Sent: 09 October 2007 13:12 > To: XWiki Developers > Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a > set of criteria > > > Added here : > http://www.xwiki.org/xwiki/bin/view/DevGuide/velocityHqlExamples#HGettingdoc > umentswhereobjects27propertiesequalssomevalue > > JV. > > 2007/10/9, goldring, richard <richard.goldring(a)uk.thalesgroup.com>: > > Thanks Jean-Vincent, > > > > What you've done helps ... but how does one list documents with a certain > > object attached whom's properties = a certain value? > > > > Regards, > > > > Richard > > > > -----Original Message----- > > From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of > > Jean-Vincent Drean > > Sent: 09 October 2007 12:34 > > To: XWiki Developers > > Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a > > set of criteria > > > > > > I've started documenting hql queries through public and privileged APIs > > here: > > http://www.xwiki.org/xwiki/bin/view/DevGuide/velocityHqlExamples > > > > The privileged API will fit your need (don't forget to protect the > > edition of your scripts pages by non-admins). > > > > JV. > > > > 2007/10/9, goldring, richard <richard.goldring(a)uk.thalesgroup.com>: > > > Jean-Vincent, > > > > > > Thanks - I tried it and it worked. > > > > > > What I'd like to do now is to have a set of pages with objects attached > > and > > > to search those pages by the attributes on those objects. > > > > > > So for example the pages could represent 'tasks', the objects would > store > > > details of those tasks e.g. task status, task owner, task description, > > task > > > date, etc. On a browser page a search/filter could then be done on say > > task > > > status to list all uncompleted tasks. > > > > > > Any idea how to do that? > > > > > > Also is there any documentation on how to do these searches using: > > > > > > $xwiki.xWiki.search("select count(doc) from XWikiDocument doc ${query}", > > > $context.context).get(0)) > > > > > > and > > > > > > #set ($list = $xwiki.searchDocuments($query, $resultsPerPage, $start)) > > > > > > i.e. what database tables to search - a description of how these methods > > > work and how to use them, etc > > > > > > If anyone has some more examples and explaination of these then it would > > > really help! Thanks! > > > > > > Regards, > > > > > > Richard > > > > > > -----Original Message----- > > > From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of > > > Jean-Vincent Drean > > > Sent: 03 October 2007 15:00 > > > To: XWiki Developers > > > Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a > > > set of criteria > > > > > > > > > The snippet on xwiki.org : > > > http://www.xwiki.org/xwiki/bin/view/Code/PaginateSearch > > > > > > 2007/10/3, Jean-Vincent Drean <jv(a)xwiki.com>: > > > > Hi, > > > > > > > > It's a recurrent need but AFAIK we don't have any generic solution. > > > > I've made a 5' snippet, hope it will be useful. > > > > > > > > This snippet requires programming rights ($xwiki.xWiki.search) so > > > > you'll have to make sure that simple users can't edit this page. > > > > > > > > > > > > > > -----------------------------------------------8<--------------------------- > > > ---------------------------------------- > > > > #macro(paginedSearch $query $currentPage $resultsPerPage) > > > > #set ($start = $resultsPerPage * $currentPage) > > > > #set ($resultsnb = $xwiki.xWiki.search("select count(doc) from > > > > XWikiDocument doc ${query}", $context.context).get(0)) > > > > #if ($resultsnb > $resultsPerPage) > > > > #set ($pagesnb = $resultsnb / $resultsPerPage) > > > > #foreach ($pagenb in [0..$pagesnb]) > > > > [$pagenb>$doc.fullName?page=$pagenb] > > > > #end > > > > #end > > > > #set ($list = $xwiki.searchDocuments($query, $resultsPerPage, $start)) > > > > #foreach ($item in $list) > > > > * $item > > > > #end > > > > #end > > > > > > > > #if ($request.page) > > > > #set ($desiredStart = $xwiki.parseInt($request.page)) > > > > #else > > > > #set ($desiredStart = 0) > > > > #end > > > > > > > > #paginedSearch("where 1=1" $desiredStart 5) > > > > > > > > > > -----------------------------------------------8<--------------------------- > > > ---------------------------------------- > > > > > > > > 2007/10/3, goldring, richard <richard.goldring(a)uk.thalesgroup.com>: > > > > > Anyone? > > > > > > > > > > > > > > > Hi all, > > > > > > > > > > Does anyone know how to generate a list of links to wiki pages that > > meet > > > a > > > > > set of defined features i.e. filter and sort (features defined on > the > > > > > objects or tags on those pages)? Perhaps like the Google search, > list > > > the > > > > > first 20 or 30 pages and have a next/previous, 1, 2, 3, etc buttons > to > > > list > > > > > the next selections of page links (to cope with the display of large > > > numbers > > > > > of page links). > > > > > > > > > > If anyones got any code snipits to get me started then that would be > > > really > > > > > useful - thanks. > > > > > > > > > > The idea is perhaps to explore how to use XWiki to semi > automatically > > > > > generate pages to record tasks or issues, and then to list those > pages > > > > > (tasks/issues) according to say the status or owners of those > > > tasks/issues. > > > > > For tasks I'm thinking XWiki might be used to help guide users > through > > > > > business processes and semi-automatically document they have > followed > > > those > > > > > processes (for CMMI) so they can be simply audited. Documents > > generated > > > > > through users following the tasks/processes can then be generated > from > > > > > templates and stored within the wiki. If anyone else has any > > ideas/code > > > that > > > > > could help perhaps realise this then let me know! > > > > > > > > > > Regards, > > > > > > > > > > Richard Goldring > > > > > > > > > > TAO > > > > > Wookey Hole Road > > > > > Wells, Somerset > > > > > BA5 1AA > > > > > > > > > > Direct Line: 01749 682694 > > > > > Switchboard: 01749 672081 > > > > > richard.goldring(a)uk.thalesgroup.com > > > > > > > > > > > > > > > > > > > > > > > > > Thales UK Ltd (Wells) DISCLAIMER: The information contained in this > > > e-mail > > > > > is confidential. It may also be legally privileged. It is intended > > only > > > for > > > > > the stated addressee(s) and access to it by any other person is > > > > > unauthorised. If you are not an addressee, you must not disclose, > > copy, > > > > > circulate or in any other way use or rely on the information > contained > > > in > > > > > this e-mail. Such unauthorised use may be unlawful. We may monitor > all > > > > > e-mail communications through our networks. If you have received > this > > > e-mail > > > > > in error, please inform us immediately on +44 (0) 1749 672081 and > > delete > > > it > > > > > and all copies from your system. We accept no responsibility for > > changes > > > to > > > > > any e-mail which occur after it has been sent. Attachments to this > > > e-mail > > > > > may contain software viruses which could damage your system. We > > > therefore > > > > > recommend you virus-check all attachments before opening. A business > > of > > > > > Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne > > > Business > > > > > Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England > No. > > > > > 868273 > > > > > _______________________________________________ > > > > > devs mailing list > > > > > devs(a)xwiki.org > > > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > > > > > > > _______________________________________________ > > > devs mailing list > > > devs(a)xwiki.org > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > Thales UK Ltd (Wells) DISCLAIMER: The information contained in this > e-mail > > > is confidential. It may also be legally privileged. It is intended only > > for > > > the stated addressee(s) and access to it by any other person is > > > unauthorised. If you are not an addressee, you must not disclose, copy, > > > circulate or in any other way use or rely on the information contained > in > > > this e-mail. Such unauthorised use may be unlawful. We may monitor all > > > e-mail communications through our networks. If you have received this > > e-mail > > > in error, please inform us immediately on +44 (0) 1749 672081 and delete > > it > > > and all copies from your system. We accept no responsibility for changes > > to > > > any e-mail which occur after it has been sent. Attachments to this > e-mail > > > may contain software viruses which could damage your system. We > therefore > > > recommend you virus-check all attachments before opening. A business of > > > Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne > > Business > > > Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. > > > 868273 > > > _______________________________________________ > > > devs mailing list > > > devs(a)xwiki.org > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail > > is confidential. It may also be legally privileged. It is intended only > for > > the stated addressee(s) and access to it by any other person is > > unauthorised. If you are not an addressee, you must not disclose, copy, > > circulate or in any other way use or rely on the information contained in > > this e-mail. Such unauthorised use may be unlawful. We may monitor all > > e-mail communications through our networks. If you have received this > e-mail > > in error, please inform us immediately on +44 (0) 1749 672081 and delete > it > > and all copies from your system. We accept no responsibility for changes > to > > any e-mail which occur after it has been sent. Attachments to this e-mail > > may contain software viruses which could damage your system. We therefore > > recommend you virus-check all attachments before opening. A business of > > Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne > Business > > Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. > > 868273 > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > > Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail > is confidential. It may also be legally privileged. It is intended only for > the stated addressee(s) and access to it by any other person is > unauthorised. If you are not an addressee, you must not disclose, copy, > circulate or in any other way use or rely on the information contained in > this e-mail. Such unauthorised use may be unlawful. We may monitor all > e-mail communications through our networks. If you have received this e-mail > in error, please inform us immediately on +44 (0) 1749 672081 and delete it > and all copies from your system. We accept no responsibility for changes to > any e-mail which occur after it has been sent. Attachments to this e-mail > may contain software viruses which could damage your system. We therefore > recommend you virus-check all attachments before opening. A business of > Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business > Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. > 868273 > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- 'Waste of a good apple' -Samwise Gamgee _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail is confidential. It may also be legally privileged. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. We may monitor all e-mail communications through our networks. If you have received this e-mail in error, please inform us immediately on +44 (0) 1749 672081 and delete it and all copies from your system. We accept no responsibility for changes to any e-mail which occur after it has been sent. Attachments to this e-mail may contain software viruses which could damage your system. We therefore recommend you virus-check all attachments before opening. A business of Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. 868273

17 years, 11 months

3
2
0 0

[xwiki-devs] [XEclipse] Design improvements discussion

by Fabio Mancinelli

Dear all, I am starting to take a deeper look at XEclipse and I think there are some improvements at the design level that, IMHO, are worth to be taken into account. These improvements leverage Eclipse platform's features that, to some extent, have been re-implemented in XEclipse. 1) Deferred tree content managers. I am a big fan of this feature and I tend to use it whenever I can. Basically a deferred tree content manager allows you to "fetch" tree children in a deferred way. One example is the "SVN Repository" or "CVS Repository" views in your Eclipse IDE. When you expand a node it displays a "Pending..." element and, when the fetching job is over, the actual elements (i.e., files and directories available on the repository) are displayed. The same mechanism could be used in XEclipse to fetch Spaces and Pages. The good thing about this approach is that the manager takes care of everything: * A tree node that is collapsed before the fetching job is terminated deletes the corresponding job; * Changing the input element of the tree invalidates all the active jobs * You can expand different tree nodes without waiting that the previous ones terminate their fetching job: in this case you will have several "Pending..." indicators in the tree. You can play a bit with the "SVN Repository" view and see what I mean. The best news is that all of this already implemented and available in the eclipse platform through the DeferredTreeContentManager[1] class. Using the deferred tree content fetching mechanism eliminates the need of having additional logic in XWikiSpace for understanding when pages are ready (i.e., all the code that manages isPagesReady in XWikiSpace.java). You will simply have a method getPages that could take possibly forever and that directly fetches the pages from the XMLRPC source (or from the offline cache). I think that this will also have impact on the Decorators that are used to wrap XWiki* elements in order to provide a visual feedback on what's going on (i.e., all the GuiUtils.runOperationWithProgress will be unnecessary since the deferred tree content manager will take care of everything) 2) Adapters I noticed that there is a TreeAdapter interface that basically is used for providing labels, children and so on. All classes that can be "displayed" in a tree implements this interface (i.e., XWikiConnection, XWikiPage, XWikiSpace). I think that this "pollutes" the model because, for example, getPages and getTreeChildren basically return the same thing and, therefore, are duplicated methods. Moreover in this way you put "GUI"-oriented stuff in the model and this is not good. The Eclipse platform has a mechanism for providing adapters that are able to give information about model elements to GUI components[2]. Not surprisingly they are called Adapters and are handled via extension points. Basically you register an AdapterFactory that provides IWorkbenchAdapters. An IWorkbenchAdapter[3] actually contains what was declared in XEclipse TreeAdapter. When you need structural information about an object, you can then query the platform for an adapter that matches a given interface and is suitable for a given object. In our case I can register an adapter for XWikiSpace that implements the getChildren method and that will simply call the getPages method of the XWikiSpace model object. In this way I can clearly separate the "GUI" code from the "model" code and leave Eclipse handle the rest. It is worth to notice that many GUI content providers directly support IWorkbenchAdapters out of the box, so if you carefully write your model adapters you will never have to write a content/label provider; but even when you write your own content provider you can always put a lookup to the adapter and then talk to it for getting the information to display (this is actually a standard practice). In the attachment you can find a sample implementation of the "deferred tree" way of displaying the XWiki navigator that makes use of adapters. Notice the getChildren methods in XWikiSpaceAdapter (declared in AdapterFactory.java). It calls a method myGetPages that I've added for testing purposes to the IXWikiSpace interface and that basically does the following straight simple thing: public Collection<IXWikiPage> myGetPages() throws ConfluenceException, SwizzleConfluenceException { Confluence rpc = getConnection().getRpcProxy(); String spaceKey = getKey(); List<Object> pages = rpc.getPages(spaceKey); List<IXWikiPage> result = new ArrayList<IXWikiPage>(); for (int i = 0; i < pages.size(); i++) { PageSummary pageSummary = (PageSummary) pages.get(i); XWikiPage xWikiPage = new XWikiPage(this, pageSummary); result.add(xWikiPage); } return result; } Of course this is a proposal to discuss about. But I think that we should spend some time on it because we could end up with a lighter design and a more maintainable product. WDYT? Cheers, Fabio [1] http://help.eclipse.org/help33/index.jsp?topic=/ org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/progress/ DeferredTreeContentManager.html [2] Of course the adapters mechanism is not limited to GUI components but can be used to adapt an object to whatever interface we need to. [3] http://help.eclipse.org/help33/index.jsp?topic=/ org.eclipse.platform.doc.isv/reference/api/org/eclipse/ui/model/ IWorkbenchAdapter.html These are the XML lines in plugin.xml that defines the org.eclipse.core.runtime.adapters extension point for registering the AdapterFactory and types: <extension point="org.eclipse.core.runtime.adapters"> <factory adaptableType="org.xwiki.plugins.eclipse.model.IXWikiConnection" class="fm.AdapterFactory"> <adapter type="org.eclipse.ui.progress.IDeferredWorkbenchAdapter"></adapter> </factory> <factory adaptableType="org.xwiki.plugins.eclipse.model.IXWikiSpace" class="fm.AdapterFactory"> <adapter type="org.eclipse.ui.progress.IDeferredWorkbenchAdapter"></adapter> </factory> </extension>

17 years, 11 months

3
2
0 0

Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a set of criteria

by goldring, richard

Jean-Vincent, Thanks. Seems that the line: #set($class = $bentrydoc.getObject("XWiki.ArticleClass").xWikiClass) seemed to cause the $class not to get set and "$bentrydoc.display($prop.name,"view", $class)" not to evaluate and just got displayed on the page - removing ".xWikiClass" solved the problem i.e. #set($class = $bentrydoc.getObject("XWiki.ArticleClass")) Was ".xWikiClass" just a typo? Also "<td> *${prop.prettyName}* </td>" didn't evaluate and just got displayed on the page! So my working code is now: #set ($list = $xwiki.search("select doc.fullName from XWikiDocument doc, BaseObject obj, StringProperty prop where doc.fullName=obj.name and obj.className='XWiki.ArticleClass' and prop.id.id=obj.id and prop.name='title' and prop.value like 'Art%'", 5, 0)) #foreach ($item in $list) #set($bentrydoc = $xwiki.getDocument($item)) #set($class = $bentrydoc.getObject("XWiki.ArticleClass")) $bentrydoc.name <table border="1" cellspacing="0" cellpadding="2"> #foreach($prop in $class.properties) <tr> <td> *${prop.name}* </td> <td> $bentrydoc.display($prop.name,"view", $class) </td> </tr> #end </table> #end I might try your refactored code as well - thank :) Regards, Richard -----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of Jean-Vincent Drean Sent: 10 October 2007 09:58 To: XWiki Developers Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a set of criteria 2007/10/9, goldring, richard <richard.goldring(a)uk.thalesgroup.com>: > #set ($list = $xwiki.search("select doc.fullName from XWikiDocument doc, > BaseObject obj, StringProperty prop where doc.fullName=obj.name and > obj.className='XWiki.ArticleClass' and prop.id.id=obj.id and > prop.name='title' and prop.value like 'Art%'", 5, 0)) Remember that you'll get only the 5 first results with this call : http://build.xpertnet.biz/latestdoc/api/com/xpn/xwiki/api/XWiki.html#search( java.lang.String,%20int,%20int) from : http://build.xpertnet.biz/latestdoc/api/com/xpn/xwiki/api/package-summary.ht ml > #foreach ($item in $list) > #set($bentrydoc = $xwiki.getDocument($item)) > > #set($class = $bentrydoc.getObject("XWiki.ArticleClass").xWikiClass) > $bentrydoc.name > <table border="1" cellspacing="0" cellpadding="2"> > #foreach($prop in $class.properties) > <tr> > <td> *${prop.prettyName}* </td> > <td>Value: $doc.display($prop.value)</td> <--- this line! > </tr> > #end > </table> While you know the type of the object you want to display you don't have to use the xWikiClass (which is privileged API). You can consult the list of the class properties at : /xwiki/bin/edit/XWiki/ArticleClass?editor=class (class editor, accessible from the top menu). I'd refactor your snippet like this : #foreach ($item in $list) #set($bdoc = $xwiki.getDocument($item)) $bdoc.title <table border="1" cellspacing="0" cellpadding="2"> <tr> <td> *Title* </td> <td>$bdoc.display("title")</td> </tr> <tr> <td> *Category* </td> <td>$bdoc.display("category")</td> </tr> <tr> <td> *Content* </td> <td>$bdoc.display("content")</td> </tr> </table> #end JV. _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail is confidential. It may also be legally privileged. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. We may monitor all e-mail communications through our networks. If you have received this e-mail in error, please inform us immediately on +44 (0) 1749 672081 and delete it and all copies from your system. We accept no responsibility for changes to any e-mail which occur after it has been sent. Attachments to this e-mail may contain software viruses which could damage your system. We therefore recommend you virus-check all attachments before opening. A business of Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. 868273

17 years, 11 months

1
0
0 0

Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a set of criteria

by goldring, richard

Jean-Vincent, I've developed this code for searching and then displaying the properties and property values of an documents object - only the line indicated doesn't display the properties value - any ideas how to do this? #set ($list = $xwiki.search("select doc.fullName from XWikiDocument doc, BaseObject obj, StringProperty prop where doc.fullName=obj.name and obj.className='XWiki.ArticleClass' and prop.id.id=obj.id and prop.name='title' and prop.value like 'Art%'", 5, 0)) #foreach ($item in $list) #set($bentrydoc = $xwiki.getDocument($item)) #set($class = $bentrydoc.getObject("XWiki.ArticleClass").xWikiClass) $bentrydoc.name <table border="1" cellspacing="0" cellpadding="2"> #foreach($prop in $class.properties) <tr> <td> *${prop.prettyName}* </td> <td>Value: $doc.display($prop.value)</td> <--- this line! </tr> #end </table> Regards, Richard -----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of Jean-Vincent Drean Sent: 09 October 2007 13:12 To: XWiki Developers Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a set of criteria Added here : http://www.xwiki.org/xwiki/bin/view/DevGuide/velocityHqlExamples#HGettingdoc umentswhereobjects27propertiesequalssomevalue JV. 2007/10/9, goldring, richard <richard.goldring(a)uk.thalesgroup.com>: > Thanks Jean-Vincent, > > What you've done helps ... but how does one list documents with a certain > object attached whom's properties = a certain value? > > Regards, > > Richard > > -----Original Message----- > From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of > Jean-Vincent Drean > Sent: 09 October 2007 12:34 > To: XWiki Developers > Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a > set of criteria > > > I've started documenting hql queries through public and privileged APIs > here: > http://www.xwiki.org/xwiki/bin/view/DevGuide/velocityHqlExamples > > The privileged API will fit your need (don't forget to protect the > edition of your scripts pages by non-admins). > > JV. > > 2007/10/9, goldring, richard <richard.goldring(a)uk.thalesgroup.com>: > > Jean-Vincent, > > > > Thanks - I tried it and it worked. > > > > What I'd like to do now is to have a set of pages with objects attached > and > > to search those pages by the attributes on those objects. > > > > So for example the pages could represent 'tasks', the objects would store > > details of those tasks e.g. task status, task owner, task description, > task > > date, etc. On a browser page a search/filter could then be done on say > task > > status to list all uncompleted tasks. > > > > Any idea how to do that? > > > > Also is there any documentation on how to do these searches using: > > > > $xwiki.xWiki.search("select count(doc) from XWikiDocument doc ${query}", > > $context.context).get(0)) > > > > and > > > > #set ($list = $xwiki.searchDocuments($query, $resultsPerPage, $start)) > > > > i.e. what database tables to search - a description of how these methods > > work and how to use them, etc > > > > If anyone has some more examples and explaination of these then it would > > really help! Thanks! > > > > Regards, > > > > Richard > > > > -----Original Message----- > > From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of > > Jean-Vincent Drean > > Sent: 03 October 2007 15:00 > > To: XWiki Developers > > Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a > > set of criteria > > > > > > The snippet on xwiki.org : > > http://www.xwiki.org/xwiki/bin/view/Code/PaginateSearch > > > > 2007/10/3, Jean-Vincent Drean <jv(a)xwiki.com>: > > > Hi, > > > > > > It's a recurrent need but AFAIK we don't have any generic solution. > > > I've made a 5' snippet, hope it will be useful. > > > > > > This snippet requires programming rights ($xwiki.xWiki.search) so > > > you'll have to make sure that simple users can't edit this page. > > > > > > > > > -----------------------------------------------8<--------------------------- > > ---------------------------------------- > > > #macro(paginedSearch $query $currentPage $resultsPerPage) > > > #set ($start = $resultsPerPage * $currentPage) > > > #set ($resultsnb = $xwiki.xWiki.search("select count(doc) from > > > XWikiDocument doc ${query}", $context.context).get(0)) > > > #if ($resultsnb > $resultsPerPage) > > > #set ($pagesnb = $resultsnb / $resultsPerPage) > > > #foreach ($pagenb in [0..$pagesnb]) > > > [$pagenb>$doc.fullName?page=$pagenb] > > > #end > > > #end > > > #set ($list = $xwiki.searchDocuments($query, $resultsPerPage, $start)) > > > #foreach ($item in $list) > > > * $item > > > #end > > > #end > > > > > > #if ($request.page) > > > #set ($desiredStart = $xwiki.parseInt($request.page)) > > > #else > > > #set ($desiredStart = 0) > > > #end > > > > > > #paginedSearch("where 1=1" $desiredStart 5) > > > > > > -----------------------------------------------8<--------------------------- > > ---------------------------------------- > > > > > > 2007/10/3, goldring, richard <richard.goldring(a)uk.thalesgroup.com>: > > > > Anyone? > > > > > > > > > > > > Hi all, > > > > > > > > Does anyone know how to generate a list of links to wiki pages that > meet > > a > > > > set of defined features i.e. filter and sort (features defined on the > > > > objects or tags on those pages)? Perhaps like the Google search, list > > the > > > > first 20 or 30 pages and have a next/previous, 1, 2, 3, etc buttons to > > list > > > > the next selections of page links (to cope with the display of large > > numbers > > > > of page links). > > > > > > > > If anyones got any code snipits to get me started then that would be > > really > > > > useful - thanks. > > > > > > > > The idea is perhaps to explore how to use XWiki to semi automatically > > > > generate pages to record tasks or issues, and then to list those pages > > > > (tasks/issues) according to say the status or owners of those > > tasks/issues. > > > > For tasks I'm thinking XWiki might be used to help guide users through > > > > business processes and semi-automatically document they have followed > > those > > > > processes (for CMMI) so they can be simply audited. Documents > generated > > > > through users following the tasks/processes can then be generated from > > > > templates and stored within the wiki. If anyone else has any > ideas/code > > that > > > > could help perhaps realise this then let me know! > > > > > > > > Regards, > > > > > > > > Richard Goldring > > > > > > > > TAO > > > > Wookey Hole Road > > > > Wells, Somerset > > > > BA5 1AA > > > > > > > > Direct Line: 01749 682694 > > > > Switchboard: 01749 672081 > > > > richard.goldring(a)uk.thalesgroup.com > > > > > > > > > > > > > > > > > > > > Thales UK Ltd (Wells) DISCLAIMER: The information contained in this > > e-mail > > > > is confidential. It may also be legally privileged. It is intended > only > > for > > > > the stated addressee(s) and access to it by any other person is > > > > unauthorised. If you are not an addressee, you must not disclose, > copy, > > > > circulate or in any other way use or rely on the information contained > > in > > > > this e-mail. Such unauthorised use may be unlawful. We may monitor all > > > > e-mail communications through our networks. If you have received this > > e-mail > > > > in error, please inform us immediately on +44 (0) 1749 672081 and > delete > > it > > > > and all copies from your system. We accept no responsibility for > changes > > to > > > > any e-mail which occur after it has been sent. Attachments to this > > e-mail > > > > may contain software viruses which could damage your system. We > > therefore > > > > recommend you virus-check all attachments before opening. A business > of > > > > Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne > > Business > > > > Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. > > > > 868273 > > > > _______________________________________________ > > > > devs mailing list > > > > devs(a)xwiki.org > > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail > > is confidential. It may also be legally privileged. It is intended only > for > > the stated addressee(s) and access to it by any other person is > > unauthorised. If you are not an addressee, you must not disclose, copy, > > circulate or in any other way use or rely on the information contained in > > this e-mail. Such unauthorised use may be unlawful. We may monitor all > > e-mail communications through our networks. If you have received this > e-mail > > in error, please inform us immediately on +44 (0) 1749 672081 and delete > it > > and all copies from your system. We accept no responsibility for changes > to > > any e-mail which occur after it has been sent. Attachments to this e-mail > > may contain software viruses which could damage your system. We therefore > > recommend you virus-check all attachments before opening. A business of > > Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne > Business > > Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. > > 868273 > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > > Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail > is confidential. It may also be legally privileged. It is intended only for > the stated addressee(s) and access to it by any other person is > unauthorised. If you are not an addressee, you must not disclose, copy, > circulate or in any other way use or rely on the information contained in > this e-mail. Such unauthorised use may be unlawful. We may monitor all > e-mail communications through our networks. If you have received this e-mail > in error, please inform us immediately on +44 (0) 1749 672081 and delete it > and all copies from your system. We accept no responsibility for changes to > any e-mail which occur after it has been sent. Attachments to this e-mail > may contain software viruses which could damage your system. We therefore > recommend you virus-check all attachments before opening. A business of > Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business > Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. > 868273 > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail is confidential. It may also be legally privileged. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. We may monitor all e-mail communications through our networks. If you have received this e-mail in error, please inform us immediately on +44 (0) 1749 672081 and delete it and all copies from your system. We accept no responsibility for changes to any e-mail which occur after it has been sent. Attachments to this e-mail may contain software viruses which could damage your system. We therefore recommend you virus-check all attachments before opening. A business of Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. 868273

17 years, 11 months

3
2
0 0

[xwiki-devs] [Proposal] Nearly remove Admin.WebHome

by Jean-Vincent Drean

After seeing XE-14 [1] I've made a quick evaluation of what Admin.WebHome contains, available here : http://www.xwiki.org/xwiki/bin/view/Design/RefactoringAdminWebHome My suggestion is at the end of the document, I suggest to remove the link to this page in the quicklinks panel and replace its content by a small description since it would be useless after some minor additions in the top menu. WDYT ? JV. [1] : http://jira.xwiki.org/jira/browse/XE-14

17 years, 11 months

3
4
0 0

[xwiki-devs] [Proposal] Nearly remove XWiki.WebHome

by Jean-Vincent Drean

Sorry, made a mistake in the page name. 2007/10/9, Jean-Vincent Drean <jv(a)xwiki.com>: > After seeing XE-14 [1] I've made a quick evaluation of what > Admin.WebHome contains, available here : > http://www.xwiki.org/xwiki/bin/view/Design/RefactoringAdminWebHome > > My suggestion is at the end of the document, I suggest to remove the > link to this page in the quicklinks panel and replace its content by a > small description since it would be useless after some minor additions > in the top menu. > > WDYT ? > > JV. > > [1] : http://jira.xwiki.org/jira/browse/XE-14 >

17 years, 11 months

1
0
0 0

Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a set of criteria

by goldring, richard

Hey it works! I coded it thus: 1.1 Listing documents by searching on their object properties - XWikiUsers and first name #set ($list = $xwiki.search("select doc.fullName from XWikiDocument doc, BaseObject obj, StringProperty prop where doc.fullName=obj.name and obj.className='XWiki.XWikiUsers' and prop.id.id=obj.id and prop.name='first_name' and prop.value='Graham'", 5, 0)) #includeForm("XWiki.Results") 1.1 Listing documents by searching on their object properties - Article and title #set ($list = $xwiki.search("select doc.fullName from XWikiDocument doc, BaseObject obj, StringProperty prop where doc.fullName=obj.name and obj.className='XWiki.ArticleClass' and prop.id.id=obj.id and prop.name='title' and prop.value like 'Art%'", 5, 0)) #includeForm("XWiki.Results") and it displays the results using the Results table (although with two #includeForm("XWiki.Results") it displays the filter columns twice on the first table and no fitler columns on the second table on the same page?). So thanks again Jean-Vincent!!!! This is really going to help me (and others) use XWiki to develop useful applications with it. Best Regards, Richard -----Original Message----- From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of Jean-Vincent Drean Sent: 09 October 2007 13:12 To: XWiki Developers Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a set of criteria Added here : http://www.xwiki.org/xwiki/bin/view/DevGuide/velocityHqlExamples#HGettingdoc umentswhereobjects27propertiesequalssomevalue JV. 2007/10/9, goldring, richard <richard.goldring(a)uk.thalesgroup.com>: > Thanks Jean-Vincent, > > What you've done helps ... but how does one list documents with a certain > object attached whom's properties = a certain value? > > Regards, > > Richard > > -----Original Message----- > From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of > Jean-Vincent Drean > Sent: 09 October 2007 12:34 > To: XWiki Developers > Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a > set of criteria > > > I've started documenting hql queries through public and privileged APIs > here: > http://www.xwiki.org/xwiki/bin/view/DevGuide/velocityHqlExamples > > The privileged API will fit your need (don't forget to protect the > edition of your scripts pages by non-admins). > > JV. > > 2007/10/9, goldring, richard <richard.goldring(a)uk.thalesgroup.com>: > > Jean-Vincent, > > > > Thanks - I tried it and it worked. > > > > What I'd like to do now is to have a set of pages with objects attached > and > > to search those pages by the attributes on those objects. > > > > So for example the pages could represent 'tasks', the objects would store > > details of those tasks e.g. task status, task owner, task description, > task > > date, etc. On a browser page a search/filter could then be done on say > task > > status to list all uncompleted tasks. > > > > Any idea how to do that? > > > > Also is there any documentation on how to do these searches using: > > > > $xwiki.xWiki.search("select count(doc) from XWikiDocument doc ${query}", > > $context.context).get(0)) > > > > and > > > > #set ($list = $xwiki.searchDocuments($query, $resultsPerPage, $start)) > > > > i.e. what database tables to search - a description of how these methods > > work and how to use them, etc > > > > If anyone has some more examples and explaination of these then it would > > really help! Thanks! > > > > Regards, > > > > Richard > > > > -----Original Message----- > > From: devs-bounces(a)xwiki.org [mailto:devs-bounces@xwiki.org]On Behalf Of > > Jean-Vincent Drean > > Sent: 03 October 2007 15:00 > > To: XWiki Developers > > Subject: Re: [xwiki-devs] Ref: Displaying lists of wiki pages given a > > set of criteria > > > > > > The snippet on xwiki.org : > > http://www.xwiki.org/xwiki/bin/view/Code/PaginateSearch > > > > 2007/10/3, Jean-Vincent Drean <jv(a)xwiki.com>: > > > Hi, > > > > > > It's a recurrent need but AFAIK we don't have any generic solution. > > > I've made a 5' snippet, hope it will be useful. > > > > > > This snippet requires programming rights ($xwiki.xWiki.search) so > > > you'll have to make sure that simple users can't edit this page. > > > > > > > > > -----------------------------------------------8<--------------------------- > > ---------------------------------------- > > > #macro(paginedSearch $query $currentPage $resultsPerPage) > > > #set ($start = $resultsPerPage * $currentPage) > > > #set ($resultsnb = $xwiki.xWiki.search("select count(doc) from > > > XWikiDocument doc ${query}", $context.context).get(0)) > > > #if ($resultsnb > $resultsPerPage) > > > #set ($pagesnb = $resultsnb / $resultsPerPage) > > > #foreach ($pagenb in [0..$pagesnb]) > > > [$pagenb>$doc.fullName?page=$pagenb] > > > #end > > > #end > > > #set ($list = $xwiki.searchDocuments($query, $resultsPerPage, $start)) > > > #foreach ($item in $list) > > > * $item > > > #end > > > #end > > > > > > #if ($request.page) > > > #set ($desiredStart = $xwiki.parseInt($request.page)) > > > #else > > > #set ($desiredStart = 0) > > > #end > > > > > > #paginedSearch("where 1=1" $desiredStart 5) > > > > > > -----------------------------------------------8<--------------------------- > > ---------------------------------------- > > > > > > 2007/10/3, goldring, richard <richard.goldring(a)uk.thalesgroup.com>: > > > > Anyone? > > > > > > > > > > > > Hi all, > > > > > > > > Does anyone know how to generate a list of links to wiki pages that > meet > > a > > > > set of defined features i.e. filter and sort (features defined on the > > > > objects or tags on those pages)? Perhaps like the Google search, list > > the > > > > first 20 or 30 pages and have a next/previous, 1, 2, 3, etc buttons to > > list > > > > the next selections of page links (to cope with the display of large > > numbers > > > > of page links). > > > > > > > > If anyones got any code snipits to get me started then that would be > > really > > > > useful - thanks. > > > > > > > > The idea is perhaps to explore how to use XWiki to semi automatically > > > > generate pages to record tasks or issues, and then to list those pages > > > > (tasks/issues) according to say the status or owners of those > > tasks/issues. > > > > For tasks I'm thinking XWiki might be used to help guide users through > > > > business processes and semi-automatically document they have followed > > those > > > > processes (for CMMI) so they can be simply audited. Documents > generated > > > > through users following the tasks/processes can then be generated from > > > > templates and stored within the wiki. If anyone else has any > ideas/code > > that > > > > could help perhaps realise this then let me know! > > > > > > > > Regards, > > > > > > > > Richard Goldring > > > > > > > > TAO > > > > Wookey Hole Road > > > > Wells, Somerset > > > > BA5 1AA > > > > > > > > Direct Line: 01749 682694 > > > > Switchboard: 01749 672081 > > > > richard.goldring(a)uk.thalesgroup.com > > > > > > > > > > > > > > > > > > > > Thales UK Ltd (Wells) DISCLAIMER: The information contained in this > > e-mail > > > > is confidential. It may also be legally privileged. It is intended > only > > for > > > > the stated addressee(s) and access to it by any other person is > > > > unauthorised. If you are not an addressee, you must not disclose, > copy, > > > > circulate or in any other way use or rely on the information contained > > in > > > > this e-mail. Such unauthorised use may be unlawful. We may monitor all > > > > e-mail communications through our networks. If you have received this > > e-mail > > > > in error, please inform us immediately on +44 (0) 1749 672081 and > delete > > it > > > > and all copies from your system. We accept no responsibility for > changes > > to > > > > any e-mail which occur after it has been sent. Attachments to this > > e-mail > > > > may contain software viruses which could damage your system. We > > therefore > > > > recommend you virus-check all attachments before opening. A business > of > > > > Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne > > Business > > > > Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. > > > > 868273 > > > > _______________________________________________ > > > > devs mailing list > > > > devs(a)xwiki.org > > > > http://lists.xwiki.org/mailman/listinfo/devs > > > > > > > > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail > > is confidential. It may also be legally privileged. It is intended only > for > > the stated addressee(s) and access to it by any other person is > > unauthorised. If you are not an addressee, you must not disclose, copy, > > circulate or in any other way use or rely on the information contained in > > this e-mail. Such unauthorised use may be unlawful. We may monitor all > > e-mail communications through our networks. If you have received this > e-mail > > in error, please inform us immediately on +44 (0) 1749 672081 and delete > it > > and all copies from your system. We accept no responsibility for changes > to > > any e-mail which occur after it has been sent. Attachments to this e-mail > > may contain software viruses which could damage your system. We therefore > > recommend you virus-check all attachments before opening. A business of > > Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne > Business > > Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. > > 868273 > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > > Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail > is confidential. It may also be legally privileged. It is intended only for > the stated addressee(s) and access to it by any other person is > unauthorised. If you are not an addressee, you must not disclose, copy, > circulate or in any other way use or rely on the information contained in > this e-mail. Such unauthorised use may be unlawful. We may monitor all > e-mail communications through our networks. If you have received this e-mail > in error, please inform us immediately on +44 (0) 1749 672081 and delete it > and all copies from your system. We accept no responsibility for changes to > any e-mail which occur after it has been sent. Attachments to this e-mail > may contain software viruses which could damage your system. We therefore > recommend you virus-check all attachments before opening. A business of > Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business > Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. > 868273 > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list devs(a)xwiki.org http://lists.xwiki.org/mailman/listinfo/devs Thales UK Ltd (Wells) DISCLAIMER: The information contained in this e-mail is confidential. It may also be legally privileged. It is intended only for the stated addressee(s) and access to it by any other person is unauthorised. If you are not an addressee, you must not disclose, copy, circulate or in any other way use or rely on the information contained in this e-mail. Such unauthorised use may be unlawful. We may monitor all e-mail communications through our networks. If you have received this e-mail in error, please inform us immediately on +44 (0) 1749 672081 and delete it and all copies from your system. We accept no responsibility for changes to any e-mail which occur after it has been sent. Attachments to this e-mail may contain software viruses which could damage your system. We therefore recommend you virus-check all attachments before opening. A business of Thales UK Ltd. Registered Office: 2 Dashwood Lang Road, The Bourne Business Park, Addlestone, Weybridge, Surrey KT15 2NX Registered in England No. 868273

17 years, 11 months

2
1
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