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

[Proposal] New SVN directory structure to accommodate the different applications we have

by Vincent Massol

Hi, Note: This email supercedes all my other proposals on the SVN directory structure. The rationale for this mail is that we're starting to have lots of applications built on top of the xwiki platform: XWiki Enterprise (default wiki), XEM, Watch, Curriki, Chronopolys, etc. We need to accomodate them in our directory structure. Top level structure =============== /svnroot/xwiki/ |_ xwiki-platform/ |_ xwiki-applications/ |_ xwiki-enterprise/ |_ xwiki-enterprise-manager/ |_ xwiki-watch/ |_ curriki/ |_ chronopolys/ |_ xwiki-extensions/ |_ xwiki-eclipse/ |_ xwiki-concerto/ |_ sandbox/ where: * xwiki-platform is the xwiki platform on which all the applications are built. * xwiki-applications are applications that extend the platform with: skins, xwiki pages (XAR), plugins * xwiki-enterprise is the name of our previously known "default wiki" application. * xwiki-extensions are any other extensions of xwiki not fitting in xwiki-applications. For example the XWiki Eclipse integration, etc. I've put concerto there but I'm not sure what it'll look like. Definition of xwiki-platform ===================== /svnroot/xwiki/xwiki-platform/ |_ tools/ |_ core/ (JAR) |_ plugins/ (JARs) |_ skins/ (ZIPs) |_ dodo/ |_ finch/ |_ albatross/ |_ web/ (WARs) |_ gwt/ |_ standard/ |_ xarlets (XARs) |_ selenium/ |_ blog/ |_ calendar/ |_ ... where: * tools/ contains tools used to build the platform and xwiki applications * xarlets/ contains independent xwiki apps (we need a word better than xarlets and different than applications which we should reserve for things like curriki, xwiki enterprise, xem, etc) that can be installed in any running xwiki app * In the future core/ will be replaced with: |_ components/ (JARs) |_ xwiki-model/ |_ xwiki-storage/ |_ ... * In the future web/ will be replaced with UI components (see the UI proposal for more) Definition of xwiki-enterprise/ ======================= /svnroot/xwiki/xwiki-applications/xwiki-enterprise/ |_ wiki/ |_ distribution/ |_ distribution-test/ where: * wiki/ contains the xar pages Generic definition of an xwiki-application/ ================================= /svnroot/xwiki/xwiki-applications/<app name>/ |_ wiki/ |_ web/ (optional) |_ plugins/ (optional) |_ skin/ (optional) |_ distribution/ |_ distribution-test/ For example for xwiki-watch/: /svnroot/xwiki/xwiki-applications/xwiki-watch/ |_ wiki/ |_ web/ (the gwt stuff) |_ distribution/ |_ distribution-test/ I think this pretty much includes everything we currently have in SVN. WDYT? Thanks -Vincent

18 years, 2 months

7
34
0 0

Proposal for full-editing mode

by evelyne24＠gmail.com

Hello all, First of all, thank you for your replays and please forgive my short absence....I was left without electricity and Internet for a few days because a short storm. Sergiu has given me the task to implement a fullscreen editing mode, similar to WYSIWYG or WIKI and I thought about it and found several solutions, each one with advantages and disadvantages. I will present them now and I would like to receive some feedback from you, to know which of the solutions (or maybe other solution if none of mines is good enough) will be better. Ideeas for a new way of editing in xwiki (like WYSIWYG and WIKI in FULLSCREEN) --------------------------------------------------------------------------------- Ideea no. 1: A button in the editor itself, like in FCK editor --------------------------------------------------------------------------------- Sample here: http://www.fckeditor.net/demo (the one next to Help button) Advantages: 1. it doesn't need any other graphical implementation in xwiki (like a new tab for instance), because xwiki has already 2 rows of tabs 2. with a good, expressive icon it can be easily spotted by the user 3. it's very easy and intuitive to use, even for a non-initiated user (specially with a tooltip); the user can use tabs to move to the button, if he doesn't have a mouse 4. it can appear anywhere the editor toolbar is needed, therefore allowing full editing for all those cases (not only for wysiwyg and wiki...) 5. can be more impressive with a nice transition animation 6. it covers all the area in xwiki (no elements visible like panels, header etc, otherwise it will not be fullscreen editing, it will be just like the existing WYSIWYG editing mode) 7. by reducing the size of the textarea, the user is brough back to normal wysiwyg editor and has access to other elements in xwiki...like panels... just like in the existing editing mode. Disadvantages: 1. it's depedent of the editor toolbar 2. in order to save or cancel or save and continue, the user has to reduce the size by pressing the same button and then press the submit button(save, cancel...) --------------------------------------------------------------------------------- Ideea no. 2: Two small buttons, in the corner of both WYSIWYG and WIKI editor, just like in Gmail (composing), which opens a new fullscreen window with the editor, the textarea and save, cancel...buttons --------------------------------------------------------------------------------- Advantages: 1. the user can have acces to other xwiki elements (panels...) in the parent window 2. independent of the editor itself 3. pretty intuitive to use Disadvantages: 1. when the new window is opened, the parent window must be redirected to the view mode -> reloading the page 2. if the user clicks cancel, to edit again he must press Edit (WYSIWYG or WIKI) and then press the little button on the tab -> 2 reloadings 3. what happens if the user opens twice the same editor? the modifications from one must be seen in all other open editor -> quite difficult to implement 4. harder to implement 5. a button like this can be placed in each tab (wysiswyg and wiki) and it a new tab is added in xwiki which supports full screen editing, the button has to be place in it too. --------------------------------------------------------------------------------- Ideea no. 3: Resizable textarea --------------------------------------------------------------------------------- Advantages: 1. the user can resize the textarea as much as he wants, not necessarily fullscreen 2. pretty easy to use, but only if the user has a mouse to drag the textarea Disadvantages: 1. the resizing of the textarea can damage the xwiki interface (all the page has to be resized) -> pretty nasty distorsions 2. the user will have to scroll down a lot to see the footer if the textarea is resized a lot. --------------------------------------------------------------------------------- Ideea no. 4: Like the no. 1 except that when pressed, the button will open a floating pane with a nice animation, that will cover about 60% -70% of the page which will contain only a resizable textarea, the editor and the save, cance,..buttons, while the rest of the page will be covered by a translucent blocking background (similar to those which appear when you have to fill in the username and password in order to access something). When the user finishes editing and presses one of the buttons, the panel closes and the text is put back in the tab from which the editor button was pressed (i.e wysiwyg or wiki or other tab that has the editor) --------------------------------------------------------------------------------- Advantages: 1. advantages of no. 1 and the fact that will be more spectaculous (with a nice effect) Disadvantages: 1. same as no. 1 (dependent of editor etc..) So, these are my ideas for now... I would like to know which seems more appealing to you and also, if you have other opinions, ideeas... Thanks, Evelina Slatineanu

18 years, 2 months

2
1
0 0

Re: Headless X11 with Xvfb (for running selenium tests without the browser popping up)

by Vincent Massol

Hi catalin, I've checked and yes the selenium plugin we're using is too old. That xvfb support has been added recently. Actually the selenium plugin has been completely rewritten recently (it was in java it's now in groovy... first time I see a maven plugin in groovy). BTW it now supports running HTML selenium tests. I've set up our CI with Raffaello on http://teamcity.xwiki.org and I've discussed the need for an X display. Raffaello is setting up a vncserver which will act as an X server. He prefers this over xvfb as he's more experienced with it and knows it works for sure. I guess we could do the same locally if we wanted. I think the steps are: 1- set up the DISPLAY env variable 2- start vncserver 3- start the selenium RC server 4- launch the browser 5- execute the tests I guess we could integrate steps 1 and 2 in the m2 build in a profile. Of course I think the best solution is http://www.realityqa.com/ realityview.jsp (which I'm working on getting - I've asked Patrick if it's ready to be used) but this vncserver solution would be a nice backup solution in case the realityqa server is down or in offline mode. WDYT? Thanks -Vincent PS: I'm copying the xwiki dev list so that others know what we're working on. On Jun 23, 2007, at 12:30 PM, Catalin Hritcu wrote: > Hi Vincent, > > I was not able to run the tests in headless mode, because I'm getting > a strange error. When you have some time maybe you can have a look. > > So what I did was modify Step 3 in the > xwiki-product-enterprise/distribution-test/pom.xml as documented here: > http://mojo.codehaus.org/selenium-maven-plugin/examples/headless- > with-xvfb.html > Now that part looks like this: > >  > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>selenium-maven-plugin</artifactId> > <version>1.0-beta-2-SNAPSHOT</version> > <executions> > <execution> > <id>xvfb</id> > <phase>pre-integration-test</phase> > <goals> > <goal>xvfb</goal> > </goals> > </execution> > <execution> > <id>start-selenium</id> > <phase>pre-integration-test</phase> > <goals> > <goal>start-server</goal> > </goals> > <configuration> > <background>true</background> > </configuration> > </execution> > </executions> > <configuration> > <background>true</background> > <multiWindow>true</multiWindow> > </configuration> > </plugin> > > > The error I get is as follows: > catalin-4:~/JavaApps/xwiki-trunks-devs/xwiki-product-enterprise/ > distribution-test > hritcu$ mvn install > [INFO] Scanning for projects... > [INFO] > ---------------------------------------------------------------------- > ------ > [INFO] Building XWiki Products - Enterprise - Functional Tests > [INFO] task-segment: [install] > [INFO] > ---------------------------------------------------------------------- > ------ > [INFO] > ---------------------------------------------------------------------- > -- > [ERROR] BUILD ERROR > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] Failed to construct build plan for: > com.xpn.xwiki.products:xwiki-enterprise-test:pom:1.1-SNAPSHOT ( > task-segment: [install] ). Reason: Mojo: xvfb does not exist in > plugin: org.codehaus.mojo:selenium-maven-plugin:1.0-beta-2-SNAPSHOT. > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] For more information, run Maven with the -e switch > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] Total time: 1 second > [INFO] Finished at: Sat Jun 23 12:22:06 CEST 2007 > [INFO] Final Memory: 6M/11M > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] BUILD SUCCESSFUL > [INFO] > ---------------------------------------------------------------------- > -- > [INFO] Total time: 1 second > [INFO] Finished at: Sat Jun 23 12:22:06 CEST 2007 > [INFO] Final Memory: 6M/11M > [INFO] > ---------------------------------------------------------------------- > -- > catalin-4:~/JavaApps/xwiki-trunks-devs/xwiki-product-enterprise/ > distribution-test > hritcu$ > > > However the documentation says this mojo exists > http://mojo.codehaus.org/selenium-maven-plugin/xvfb-mojo.html > So this is really strange for me. > > I tried deleting the selenium-maven-plugin from the local repository > and the usual stuff but without any result. It gets downloaded again > from the XWiki(!) repository: > > [INFO] snapshot > org.codehaus.mojo:selenium-maven-plugin:1.0-beta-2-SNAPSHOT: checking > for updates from xwiki.plugin.snapshot > [INFO] snapshot > org.codehaus.mojo:selenium-maven-plugin:1.0-beta-2-SNAPSHOT: checking > for updates from xwiki.plugins > [INFO] snapshot > org.codehaus.mojo:selenium-maven-plugin:1.0-beta-2-SNAPSHOT: checking > for updates from xwiki > [INFO] snapshot > org.codehaus.mojo:selenium-maven-plugin:1.0-beta-2-SNAPSHOT: checking > for updates from openqa.org > Downloading: http://maven.xwiki.org/org/codehaus/mojo/selenium- > maven-plugin/1.0-beta-2-SNAPSHOT/selenium-maven-plugin-1.0-beta-2- > SNAPSHOT.pom > 8K downloaded > Downloading: http://maven.xwiki.org/org/codehaus/mojo/selenium- > maven-plugin/1.0-beta-2-SNAPSHOT/selenium-maven-plugin-1.0-beta-2- > SNAPSHOT.jar > 12K downloaded > > Is it possible that the snapshot in the xwiki repository is too old? > Otherwise how do I force it to download from the "official" > repository? > > Regards, > Catalin

18 years, 2 months

2
3
0 0

XWiki Eclipse IDE Integration - Milestone 1

by tharindu jayasuriya

Hi All, We have completed milestone-1 of the eclipse xwiki plug-in binary and source (eclipse project) are available via, http://jira.xwiki.org/jira/browse/XWIKI-1360 Implemented features, 1. Login to XWiki 2. Selectively import spaces 3. Navigate through document hierarchy Thanks. - Tharindu

18 years, 2 months

4
7
0 0

RE: [xwiki-dev] XWiki Eclipse IDE Integration - Milestone 1

by Kito D. Mann

Thanks for the clarification, Tharindu. Really smart idea! From: tharindu jayasuriya [mailto:djtharindu@gmail.com] Sent: Monday, June 25, 2007 3:32 AM To: kmann(a)virtua.com Subject: Re: [xwiki-dev] XWiki Eclipse IDE Integration - Milestone 1 On 6/25/07, Kito D. Mann <kmann(a)virtua.com> wrote: Tharindu, This looks extremely interesting J . However, I don't quite understand _what_ you'd be doing in Eclipse. Would you use Eclipse for editing and creating pages, Yes, this is the main intension of the plug-in; letting developers manage their documentation within the IDE itself. administration, creating objects and classes, or all of the above? You can add/remove spaces/pages as well as edit/view them within eclipse IDE. But authoring objects or classes will not be possible (yet) since we are using Confluence <http://confluence.atlassian.com/display/DOC/Remote+API+Specification> XMLRPC API which does not have remote methods for such manipulations. But that is a nice feature to have; may be later ... ;-) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Kito D. Mann - Author, JavaServer Faces in Action <http://www.virtua.com/> http://www.virtua.com - JSF/Java EE consulting, training, and mentoring <http://www.jsfcentral.com/> http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info * Sign up for the JSF Central newsletter! http://oi.vresp.com/?fid=ac048d0e17 * From: tharindu jayasuriya [mailto:djtharindu@gmail.com] Sent: Saturday, June 23, 2007 7:31 AM To: xwiki-dev(a)objectweb.org Subject: [xwiki-dev] XWiki Eclipse IDE Integration - Milestone 1 Hi All, We have completed milestone-1 of the eclipse xwiki plug-in binary and source (eclipse project) are available via, http://jira.xwiki.org/jira/browse/XWIKI-1360 Implemented features, 1. Login to XWiki 2. Selectively import spaces 3. Navigate through document hierarchy Thanks. - Tharindu -- You receive this message as a subscriber of the xwiki-dev(a)objectweb.org mailing list. To unsubscribe: mailto: xwiki-dev-unsubscribe(a)objectweb.org For general help: mailto: <mailto:sympa@objectweb.org> sympa(a)objectweb.org?subject=help ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

18 years, 2 months

1
0
0 0

XWiki-Eclipse Integration

by tharindu jayasuriya

Hi All, We ( myself and Asiri ) have implemented the logging and xwiki navigation components of the above plug-in. We have tested the components on a local installation but need a remote url (confluence) to test it further. We tried to connect to www.xwiki.org using our usernames and passwords but could not connect ( verfied with XMLRPCExample too ). Is it not possible to connect to www.xwiki.org with XML RPC ? if it is possible, can any of you give us the correct url ? One more thing, the XMLRPCExample uses the server url http://<server>/xwiki/xmlrpc/confluence. We followed the same convention and get user input for the <server> part only (append the rest). Is it ok to do this ? or shall we let the user to provide whole url ? Thanks a million. - Tharindu & Asiri

18 years, 2 months

3
2
0 0

What happened with build.xml

by evelyne24＠gmail.com

Hello, I updated yesterday my xwiki sources and I see you've changed all the svn directories. The problem is that when I try to build it in Eclipse I can't find the build.xml file and also, I create a new project based on xwiki-platform-core and it gives me lots of errors in eclipse, like some files missing or some classes not found. Can anyone tell me how to build the standalone now that there is no build file? I would very much appreciate it. Thank you. Evelina

18 years, 2 months

3
4
0 0

Big problem with building the xwiki-platform-core

by evelyne24＠gmail.com

Hello, Sorry if this mail arrives twice...I sent one in the morning but no reply so...I guess no one's got it. The problem is that after this change in the svn repository I can't build the xwiki-platform-core in Eclipse. There is no build.xml file and there are a lot of errors when I create a new project based on xwiki-platform-core directory (lots of libraries missing and othes errors). Sergiu has been trying to help me since this morning, but unfortunately it still doesn't work. I tried with mvn, in order to build the war and then put in the tomcat or jetty but when I run mvn install in the xwiki=platform-core directory I get a lot of errors, like D:\XWiki\src2\xwiki-platform-core>mvn install [INFO] Scanning for projects... [INFO] ------------------------------------------------------------------------ [ERROR] FATAL ERROR [INFO] ------------------------------------------------------------------------ [INFO] Error building POM (may not be this project's POM). Project ID: null:xwiki-core:jar:1.1-SNAPSHOT Reason: Cannot find parent: com.xpn.xwiki:xwiki for project: null:xwiki-core:jar :1.1-SNAPSHOT for project null:xwiki-core:jar:1.1-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Cannot find parent: com.xpn.xw iki:xwiki for project: null:xwiki-core:jar:1.1-SNAPSHOT for project null:xwiki-c ore:jar:1.1-SNAPSHOT at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent : com.xpn.xwiki:xwiki for project: null:xwiki-core:jar:1.1-SNAPSHOT for project null:xwiki-core:jar:1.1-SNAPSHOT at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(D efaultMavenProjectBuilder.java:1261) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def aultMavenProjectBuilder.java:747) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFi leInternal(DefaultMavenProjectBuilder.java:479) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMave nProjectBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:553) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364) ... 11 more Caused by: org.apache.maven.project.ProjectBuildingException: POM 'com.xpn.xwiki :xwiki' not found in repository: Unable to download the artifact from any reposi tory etc..... I have no access to svn://svn.forge.objectweb.org/svnroot/xwiki/trunks-devs (apparently Sergiu is not getting this errors but he's using this while I'm using svn://svn.forge.objectweb.org/svnroot/xwiki/trunks-users ) So, if anyone has succeeded in building the xwiki after the change in the svn directory, please help me, I'm in big trouble and I can' continue working. Thank you very much. Evelina

18 years, 2 months

4
5
0 0

[Proposal] Switch to using Maven2

by Vincent Massol

Hi, I'd like to propose 2 things: 1) Use Maven2 to perform the 1.1M3 release 2) Remove the Ant build in 1.1M4 Rationale: * It's a real pain to maintain 2 builds * The m2 build is already doing more than the Ant build Things left to do on the m2 build: * Finish setting up TeamCity (I need Raffaello's help as ObjectWeb's SVN is bad and we need to set up a SVN ready only replicate on which we could plug TC) * Fix an issue with the database importer (XWIKI-1104) * Review the versions of the dependencies What this means is that you should try using Maven 2 yourself from today onward and see if can make it work. If not, ask questions here on the list and I'll help and I'll tune the build accordingly. There's already some doc on: http://www.xwiki.org/xwiki/bin/view/Community/ Building#HBuildingwithMaven2 WDYT? Thanks -Vincent

18 years, 2 months

2
2
0 0

[XWIKI-1390]: "Sample mode" for PanelWizard

by Erin Schnabel

I was talking to Vincent about this on IRC, and he suggested that I open a jira issue, and send an email to the list, so here it is. When loading the PanelWizard against a fairly large XWiki, the page can take a fairly long time to load. Vincent and I talked about a few approaches: Adding a "Sample mode" field to the Panels, where the panels would render themselves w/ sample/dummy data to avoid queries to the DB. The PanelWizard would then have to somehow display these panels in "sample" mode. The other is to skip rendering of all of the panels entirely: list the title, links to edit/delete and provide a some kind of new button to "display panel" or "display panel contents", which would defer panel loading until requested... This collapsed view would apply to the drag-n-drop off to the sidebars as well... Thoughts? -- 'Waste of a good apple' -Samwise Gamgee

18 years, 3 months

1
0
0 0

C3P0 or DBCP?

by Vincent Massol

Hi, I've noticed that we're bundling both C3P0 and Apache DBCP connection pools frameworks. Do we need to bundle 2? By default we have DBCP configured in our hibernate.cfg.xml files. I'm thus proposing to drop C3P0 from the distribution WAR. WDYT? Thanks -Vincent

18 years, 3 months

1
0
0 0

XWiki Watch Developer Release 1.0M1

by Ludovic Dubost

[reposting because of wrong xwiki-users address. please reply to this email and not the previous one] Hi, I'm beating Vincent by announcing XWiki Watch 1.0M1 before he announces XWiki 1.1M2 (which is needed for XWiki Watch 1.0M1). XWiki Watch 1.0M1 is the first official release and is a functional beta. XWiki Watch is: - A collaborative RSS/Atom Feed aggregator - Feeds, Groups and Keywords configuration using an AJAX interface. Configuration are managed by spaces. - Storing of articles themselves in XWiki pages using the FeedPlugin's capabilities - AJAX UI to navigate articles, open the content - Collaborative tagging, commenting and flagging of articles, store a 'read' status - Filtering UI to see only articles from a group, a feed, only flagged articles, matching a keyword, etc.. - TagCloud of tags applied to articles - Text analysis feature on the content of articles matching a filter - Press Review feature allowing to generate an HTML, RSS or PDF page listing articles and comments matching a filter - Look and Feel adapted to the Albatross skin by Laurent Lunati ! - Packaged as an XWiki Application (xar) that can run on XWiki 1.1M2 or later - French and English User Interface This release needs some developer skills to be installed. If you are interested in beta-testing XWiki Watch but don't feel that you can install XWiki and tweak configuration files, you can send us an email at marketing(a)xwiki.com to get access to our online beta. Don't hesitate to send us your feedback with bugs and suggestions. We manage bugs and new feature requests on JIRA at http://jira.xwiki.org/jira/browse/XWATCH Ludovic -- Ludovic Dubost Blog: http://www.ludovic.org/blog/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost AIM: nvludo Yahoo: ludovic

18 years, 3 months

2
2
0 0

Re: [xwiki-users] XWiki Watch Developer Release 1.0M1

by Vincent Massol

On Jun 19, 2007, at 11:49 PM, Ludovic Dubost wrote: > > Hi, > > I'm beating Vincent by announcing XWiki Watch 1.0M1 before he > announces XWiki 1.1M2 (which is needed for XWiki Watch 1.0M1). Well, you "thought" you were beating but mail arrived first here! ;-) > XWiki Watch 1.0M1 is the first official release and is a functional > beta. Congrats for this nice release and all the hard work. We need to discuss on how to integrate XWiki Watch's release process into the main dev process for XWiki. Thanks -Vincent > > XWiki Watch is: > > - A collaborative RSS/Atom Feed aggregator > - Feeds, Groups and Keywords configuration using an AJAX interface. > Configuration are managed by spaces. > - Storing of articles themselves in XWiki pages using the > FeedPlugin's capabilities > - AJAX UI to navigate articles, open the content > - Collaborative tagging, commenting and flagging of articles, store > a 'read' status > - Filtering UI to see only articles from a group, a feed, only > flagged articles, matching a keyword, etc.. > - TagCloud of tags applied to articles > - Text analysis feature on the content of articles matching a filter > - Press Review feature allowing to generate an HTML, RSS or PDF > page listing articles and comments matching a filter > - Look and Feel adapted to the Albatross skin by Laurent Lunati ! > - Packaged as an XWiki Application (xar) that can run on XWiki > 1.1M2 or later > - French and English User Interface > > This release needs some developer skills to be installed. If you > are interested in beta-testing XWiki Watch but don't feel that you > can install XWiki and tweak configuration files, you can send us an > email at marketing(a)xwiki.com to get access to our online beta. > > Don't hesitate to send us your feedback with bugs and suggestions. > We manage bugs and new feature requests on JIRA at http:// > jira.xwiki.org/jira/browse/XWATCH > > Ludovic

18 years, 3 months

1
0
0 0

[ANN] XWiki 1.1 Milestone 2 Released

by Vincent Massol

The XWiki development team team is pleased to announce the availability of the 1.1 Milestone 2 release. Go grab it on http://www.xwiki.org/xwiki/bin/view/Main/Download Main changes: * Lots of bugs fixed * WYSIWYG editor improvements: o Added new toolbar icon for creating horizontal lines o Added new toolbar icon for removing all styling on the selected text o Make current cell visible when selected in a table * Improved Photo Album performances * When deleting a page, first show the list of pages linking to it and warn about them * Improved AllDocs page on the default wiki by adding an Index with A-Z links and added a Treeview tab for showing pages with parent- children relationships * The Navigation panel now displays all pages when the logged in user has Admin rights * The "Recently Created", "Recently Visited" and "Members" Panels now only display the last 5 elements * Added a cancel button to the Rename page * Added support for the Derby Database and bundled version 10.2.2.0 of Derby * The Zip Explorer plugin and the AutoTag plugins are now activated by default in the default configurations * Added new "Recently Modified Documents" Panel * New space rights inheritance mechanism + lots of other changes. See the full release notes on http://www.xwiki.org/xwiki/bin/view/ Main/ReleaseNotesXWiki11M2 Enjoy -The XWiki development team

18 years, 3 months

1
0
0 0

Changing BaseClass to put metadatas ?

by OliverT

Hello, Is there a way to add meta-attributes to a class ? Like BeforeAfterMetaclasses approaches or hooks. The underlying use case is to synchronize XWiki objects with a backend repository. A typical approach is to have the following attributes automatically changed or incremented on object change : lastmodificationdate, lastsynchronization, uptodateSequenceNumber, highwatermark... Or do you see another way for synchronization ? Thanks ! Oliver -- View this message in context: http://www.nabble.com/Changing-BaseClass-to-put-metadatas---tf3946533.html#… Sent from the XWiki- Dev mailing list archive at Nabble.com.

18 years, 3 months

1
0
0 0

[VOTE] Switch to JDK 1.5

by Vincent Massol

Hi, I think it's time to officially decide if we want to standardize on 1.5. Some reasons we may want to do this: * JDK 1.4 is old. 1.5 is mainstream. 1.6 is about to be released. * Most libraries have now switched to 1.5 and it's going to be real hard to stay on 1.4 if we want to get bug fixes/new features from the libraries we use * Radu needs to use some google jars for his GSOC and they seem to require JDK 1.5 * We already require 1.5 I believe (although it's a light dependency) and have been requiring 1.5 for now several months (> 5 months) and we haven't heard complaints from users about this The vote is about officially dropping support for 1.4 and standardizing on 1.5 (and thus allowing us to use the new features of the language too like generics, annotations, etc). Here's my +1 Please cast your votes. Thanks -Vincent

18 years, 3 months

10
17
0 0

LDAP fix

by dennis.carroll＠dot.state.mn.us

There is a fix (http://jira.xwiki.org/jira/secure/attachment/11161/LDAPAuthServiceImpl-r334…) for http://jira.xwiki.org/jira/browse/XWIKI-238 (1.0 r 3342) to let a user with mixed case username in LDAP login with all lower case. I do not see how to attach file to this so I attached the patch to http://jira.xwiki.org/jira/browse/XWIKI-238. I have tested by adding a DB user both before and after deploying the change. Regards, Dennis

18 years, 3 months

1
0
0 0

[Fwd: Re: [xwiki-dev] Regarding issue XWIKI-523 (Tags should be shown with comments and attachments)]

by Thomas Drevon

Hi! I never got an answer to this email. Did I miss a point in some way? Were my comments not what you guys actually asked for? Maybe I should add the suggestions and the screenshots to the jira issue XWIKI-523? Anyway, I'll be offline for a month now, so I won't have the chance to follow up on the discussion. I hope all you devoted developers also get the break you want or deserve this summer; you're doing an impressive job on xwiki! best regards :-) Thomas -------- Original Message -------- Subject: Re: [xwiki-dev] Regarding issue XWIKI-523 (Tags should be shown with comments and attachments) Date: Mon, 11 Jun 2007 11:45:28 +0200 From: Thomas Drevon <thomas.drevon(a)intermedia.uio.no> Reply-To: thomas.drevon(a)intermedia.uio.no To: xwiki-dev(a)objectweb.org References: <4665547D.4040408(a)intermedia.uio.no> <C7BC95C2-AF6F-4F77-94E8-D615340B188C(a)massol.net> Vincent Massol wrote: > > Here's how we could work together: you send some emails on the list, > maybe with some GUI mockups about how you think tags should be > integrated. You'll get lots of feedbacks I'm sure, especially if you > show something in a mockup (people love images ;-)). Then you start > sending some emails about how you think it should be done and committers > will comment, tell you if there's a better way. And you can ask for any > question you have along the way. > > WDYT? Sure! Ok here we go: 1. View tags along with a document. It doesn't really matter what kind of document, but for this example I've used a blog entry. See the attached file called blog_entry_view.png. In order to achieve this, just add the following lines to an appropriate place in XWiki.ArticleClassSheet: <code> Tags: #foreach($tag in $doc.getTagList()) <a href="$xwiki.getURL("Main.Tags", "view", "tag=$tag")")">$tag</a> #end </code> This code is tested and works fine. Problem: On docs without a template sheet, this gets a bit more messy, as it seems the above code must be added directly to content.vm. Maybe all docs should inherit from some sort of generic template sheet? This will give users more flexibility by sparing them the messing up of velocity files, and thus making an upgrade of their xwiki version harder. And by the way, is it correct that while viewing this doc, the breadcrumbs read "BLOG: Administration > Samarkand" even though I'm not logged in? "Administration" here seems a bit strange? 2. Intuitive edit of tags while in edit mode. See the attached file called blog_entry_edit.png. In order to achieve this, add the following lines to the correct place in XWiki.ArticleClassSheet: <code> <dt>Tags:</dt> <dd><input type="text" id="tags" name="tags" size="60" value="$!tdoc.tags"/></dd> </code> Though this code produces a nice input field as expected, tags entered here will not be saved along with the doc, unless the servlet engine is restarted between the creation of the docs and the editing of tags. Strange. Well, what do you think? Oh yes, and I'm all for letting users turn on/off the tag functionality in xwiki.cfg, by the way. cheers :-) Thomas

18 years, 3 months

1
0
0 0

[ArchitectureV2] Model proposal

by Vincent Massol

Hi, Starting from today I'm going to spend some time every week on the V2 Architecture/Redesign. Today I'd like to start at the heart of the topic with the domain model. Here's my proposal: * Model classes are classes representing the XWiki model. The main classes are: - Farm - Wiki - Space - Document - XObject - XClass - (probably lots of others) * As you can see I'd like to introduce the Space and Farm objects * We create a model/ build module in trunks-devs/xwiki/model for storing model classes * Model classes cannot access other classes outside of the model/ module. They are meant to be used by components to provide services but they shouldn't provide services themselves. They can methods to manipulate their fields and they can call each other but they cannot call outside of their model. * We use the org.xwiki.model package for storing Model classes * These model classes are all user public (API) WDYT? Barring any negative feedback I'll start implementing this today and in the coming days. One question that remains unanswered in my mind is how do we integrate back these model classes into the V1 architecture. I think we should be able to retrofit the existing classes to use these classes by composition. For example the Document object could have 2 fields: one org.xwiki.model.Document and one org.xwiki.model.Space. The XWiki object could have 2 fields: Wiki and Farm, etc. I'm not sure how this would work out though. Any idea is welcome. Thanks -Vincent

18 years, 3 months

6
21
0 0

Trouble with refresh after update from xmlrpc

by Thomas Drevon

Hi! We're experimenting with xmlprc calls to xwiki (using code from http://www.xwiki.org/xwiki/bin/view/UserGuide/XMLRPCExample), and are encountering some strange behaviour: A newly created document will appear directly in xwiki as expected. However, when we update this newly created doc the database is updated, but when we view the page in xwiki, we still see the old doc. If a restart of tomcat is done, the updated doc appears as expected. It seems as if xwiki is sticking more closely to it's cached verion of what's in the database than what we would prefer. And it looks very similar to what I discovered while editing tags on blog entries. Is this behaviour considered a bug? Is there any code that can be invoke in order to re-read the object in question from the database? Once again, any help would be greatly appreciated. cheers :-) Thomas

18 years, 3 months

3
2
0 0

XWiki-Eclipse plug-in

by tharindu jayasuriya

Hi all, Here I have attached some mock GUIs and a very intuitive requirements spec that illustrate the basic workings of XWiki-Eclipse plug-in. It's better if we can finalize these drafts soon because I need to go on with the development :). I have few doubts on the java package structure as well as about the icon graphics for the plug-in (i thought of re-using eclipse's ones where suitable). I went through XWiki XML RPC APIs and am comfortable with thw way they work (had to sharpen my SWT skills too). I'm looking forward to hear from you.. - Tharindu

18 years, 3 months

3
7
0 0

Escaping velocity code inside form fields does not work properly on xwiki.org

by Catalin Hritcu

Hi, Escaping velocity code inside form fields does not work properly on xwiki.org. For example any of the following alternatives cause an error when entered inside a form field (but causes no problem when the same text is entered inside the body of a normal document): \#set(\$myfeed=\$xwiki.feed.getFeed(\$feedUrl)) {code} \#set(\$myfeed=\$xwiki.feed.getFeed(\$feedUrl)) {code} #literal() #set($myfeed=$xwiki.feed.getFeed($feedUrl)) #end Surprisingly a third (old) way to do it works, even in form fields: {code} #\set($\myfeed=$\xwiki.feed.getFeed($\feedUrl)) {code} I was not able to reproduce this problem on my local installation of XWiki, however on xwiki.org there are many pages that are affected by this bug: http://www.xwiki.org/xwiki/bin/view/FAQ/HowToListDocumentsWithACertainPrope… http://www.xwiki.org/xwiki/bin/view/FAQ/HowCanIescapeOutQuotationMarksFromA… http://www.xwiki.org/xwiki/bin/view/FAQ/HowDoIFindTheBacklinksForAGivenPage http://www.xwiki.org/xwiki/bin/view/FAQ/HowDoIEmbedXwikiCodeAsText http://www.xwiki.org/xwiki/bin/view/FAQ/HowToSetWebPreferences http://www.xwiki.org/xwiki/bin/view/FAQ/HowDoIIntegrateAnRSSFeedWithinAPage http://www.xwiki.org/xwiki/bin/view/FAQ/PrepopulateQuestionFieldOnFAQClassS… Does any of you have an idea on what might cause this? Regards, Catalin

18 years, 3 months

1
0
0 0

Feature Request: Maximize edit window

by shivshan

Hi In Albatross skin, by default, the edit window is quite small. A big part of the screen real estate is taken up by the XWiki Document information panel on the right, the header and footer. Some wiki's have a feature by which the editor can be popped into a seperate window which can be maximised. Some others let you increase the editor area as much as you want. This would make edits of larger pages much easier, and you can focus on editing the document rather than scroll continuosly up and down. I had posted a screen shot of this problem sometime back. How easy is it to make this change? And is the popup editor feasible with XWiki architecture? Thanks Shiva -- View this message in context: http://www.nabble.com/Feature-Request%3A-Maximize-edit-window-tf3913467.htm… Sent from the XWiki- Dev mailing list archive at Nabble.com.

18 years, 3 months

1
0
0 0

[Proposal] New generic Action for calling an API and returning the result as XML

by Vincent Massol

Hi, I'm writing a treeview (using the yahoo treeview javascript api) to display the list of all pages of a wiki and in order to have good performances I need to call a server-side method for getting all children pages of a given page (so that the nodes or the treeview are loaded dynamically). In order to implement this I thus need a new XWiki Action. Now I think it would be good to generalize this common need. As we add more Ajax to our UIs we'll need more and more calls from JS to the server side. I'm thus proposing a generic ExecuteXMLAction (or AjaxAction or another name) that would do the following: * Get the class, method and parameter to execute from the HTTP request * Verify that the class is in the api package (to prevent security issues) * Call the method using introspection * Return the result as XML using XStream (it generates automatically XML from any java object) Note: I'd need to define the format for sending the information in the request. Not sure about which format to use. WDYT? Thanks -Vincent

18 years, 3 months

2
3
0 0

issue: new blog post created in wrong space

by xwiki xwiki

Hi, When I use the new page panel in XWiki 1.0 final to create a blog post, I found that the new blog post has been created in the Blog space not Current space (noted at bottom of the panel). I did some look in the calling, and I found that equalvalent is adding, e.g., following line after a page link: ?xpage=create&tocreate=post&title=testblogcreation also I did a test on the xwiki.org page: http://www.xwiki.org/xwiki/bin/view/Main/WebHome?xpage=create&tocreate=post… which should result in create a new page at Main space but I got directed here: http://www.xwiki.http://www.xwiki.org/xwiki/bin/inline/Blog/testblogcreatio… see, it's not Main. test for "tocreate=page" result in right place. thus I doubt that the code for "tocreate=post" has some where miss the space parameter. as we need use the "new page" panel tool for creating blog posts in the calling space, anywhere I can get into solving this? Thanks in advance! Muzi

18 years, 3 months

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