xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] ApplicationResources vs. ApplicationResources_en

by Jean-Vincent Drean

Hi XWikiers, I've resolved the (very few) conflicts between ApplicationResources and ApplicationResources_en. Should'nt we remove the second ? JV.

16 years, 7 months

[xwiki-devs] [GSoC]how will office importer be integrated into xwiki

by Wang Ning

Hi devs, As you know, the office importer(or office converter) project for xwiki can convert office documents like MS word, MS excel to xwiki syntax. Furthermore, it can even convert xwiki page to the MS word or PDF. My question: how to integrate the office converter into xwiki? Where should be the integration points for the conversion feature? Following is my proposal and I need you feedback. Thanks. Now the office converter is just a xwiki plugin, and the integration would base on this plugin. a) a converter application. A xwiki application based on office converter plugin and fileupload plugin can import a office document to a new xwiki page. b) a macro like {import} which can convert the office document attached to the xwiki page to html and insert the html code in the page. c) attachment review. Review the office documents attachment. This is similar to the gmail attachment review. d) integrate with xwiki WYSIWYG editor. This is similar to a). Click the import button and select the office document, then click the import button. The document will insert to the current WYSIWYG area. e) export xwiki page to MS word or Openoffice odt. Please feel free to suggest new proposal. Any feedback is very appreciated. Thanks. Wang Ning

16 years, 7 months

[xwiki-devs] [DEMO] Class/Object management improvement + editors refactoring

by Pascal Voitot

Hello guys, I'm back with my classes and objects... After some work in the middle of my other projects, I have finally something to propose to you. Now you can disable/remove properties and synchronize objects and I have refactored the class/object editor. I have launched a demo environment so that you can test the result of my study. Go to: http://feebrox.dyndns.org:8888/xwiki/ Everything is explained there... What do you think about this? You can disagree with everything and even with my graphical choices ;) best regards Pascal

16 years, 7 months

[xwiki-devs] Currikdevs

by Joshua Marks

Thank you Ludovic for making the Curriki-devs mailing list: http://lists.xwiki.org/mailman/listinfo/curriki-devs To join out project discussions, please sign-up. Joshua Marks CTO Curriki: The Global Education and Learning Community jmarks(a)curriki.org www.curriki.org US 831-685-3511

16 years, 7 months

[xwiki-devs] Debugging XWiki - xwiki-core

by Markus Lanthaler

Hi, I'm currently trying to debug XWiki with Eclipse. I set up everything as explained in http://dev.xwiki.org/xwiki/bin/view/Community/DebugXEWithEclipse and everything runs fine. Also debugging works, but my problem is that the downloaded xwiki-core JAR is used instead of my xwiki-core project in my Eclipse workspace. If I attach the the xwiki-core project as the source to that JAR (Eclipse asks me for that) the lines don't correspond if I set a breakpoint and try to step through the program. I set my xwiki-core project as a J2EE module dependency and also as project dependency of my xe-debug-web project. Any ideas what goes wrong? Thanks a lot, Markus

16 years, 7 months

[xwiki-devs] [proposal] Named Queries in QueryManager

by Artem Melentyev

Hi devs. I almost completed implementation of QueryManager (see http://markmail.org/message/l3zlqq4kqndokkif ) I think we should use named queries in core whenever possible, because it reduce code size and independent from query languages. It is also best practice in db world. I would like to discuss about: How we should store/load named queries? 1. Hibernate Named queries in hibernate usually stored in mapping files. (see http://www.hibernate.org/hib_docs/v3/reference/en/html/objectstate.html#obj… ) I think we should use this way too. So I propose to add queries.hbm.xml - special hibernate mapping for queries. Here is example: {code} <hibernate-mapping> <query name="getSpaceDocsName"> select distinct doc.name from XWikiDocument doc where doc.space=:space </query> ... {/code} 2. JCR Analogue for named queries in JCR is queries stored in special jcr nodes. So queries stored *inside* repository. Queries are content. But there is a problem how to initialize them at startup: 2.1) We can use standard import feature of JCR and import queries from xml file at startup. -: import needed for all workspaces (all virtual xwiki) -: increase time of startup -: slightly verbose xml file (<testquery jcr:primaryType="nt:query" jcr:language="xpath" jcr:statement="//*"/>) +: potentially faster quering. 2.2) Or we can don't use queries as nodes feature of JCR and store/load queries by self for example in standard java.util.ResorceBundle (for example jcr/Queries.properties). +: simple, universal, independent. There is another way: use ResourceBundles for both Hibernate and JCR. But I think we should use Hibernate's way for named queries. There is no standard way for init named queries in JCR except import. But import has much disadvantages. So I'd like to use ResourceBundle for jcr named queries. So, in short, I propose: add Queries.hbm.xml for hibernate named queries. add jcr/Queries.properties for jcr named queries. (xpath) WDYT? -- Artem Melentyev

16 years, 7 months

[xwiki-devs] Debugging XWiki - xwiki-core

by Markus Lanthaler

16 years, 7 months

[xwiki-devs] [GSOC] CBDF application

by Miguel Bento

Hi devs, I've been working on the Collaborative Business Drawing Framework API and integration with the xwiki and have a small demo of my current work: http://carmarket.gotdns.com:8090/xwiki/bin/view/Main/CBDF Known bugs: - When in select mode, if you click on another object, the transform points became appearing out of place - When you execute bring to front, the object stays in front of the transform points I'm sure it has more bugs, and i hope you guys help me finding them :) Small regard on the user experience: - To do the last point of a polyline use double-click instead of click. - To edit a object property you have to select it first! The bugs listed are easily solved, except in the case of the transform points out of place, but it's a Tatami's bug and i found i workaround so after my exam i'll solve them and hopefully continue developing.If you want to have a look at my messy source code, its located at https://svn.xwiki.org/svnroot/sandbox/xwiki-product-cbdf/ All kinds of comments are appreciated, enjoy your drawing! Best Regards, Miguel Bento.

16 years, 7 months

[xwiki-devs] [GSOC] [WEBDAV] Issue running the prototype

by Ludovic Dubost

I've followed the instructions on the readme and try to connect to http://localhost:8080/xwiki-webdav/root/ When I try to launch the wiki using a web browser I get this error: http://127.0.0.1:8080/xwiki-webdav/ or http://localhost:8080/xwiki-webdav/bin/view/Main/ Caused by: java.lang.ClassCastException: org.apache.maven.plugin.MavenPluginDiscoverer at org.codehaus.plexus.component.discovery.DefaultComponentDiscovererManager.initialize(DefaultComponentDiscovererManager.java:94) at org.codehaus.plexus.container.initialization.InitializeComponentDiscovererManagerPhase.initializeCoreComponent(InitializeComponentDiscovererManagerPhase.java:36) at org.codehaus.plexus.container.initialization.AbstractCoreComponentInitializationPhase.execute(AbstractCoreComponentInitializationPhase.java:37) at org.codehaus.plexus.DefaultPlexusContainer.initializePhases(DefaultPlexusContainer.java:914) at org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusContainer.java:858) at org.codehaus.plexus.DefaultPlexusContainer.construct(DefaultPlexusContainer.java:834) at org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:204) at com.xpn.xwiki.plugin.webdav.XWikiDavServlet.getComponentManager(XWikiDavServlet.java:279) -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

16 years, 7 months

[xwiki-devs] [GSOC][WEBDAV] Need a complete refactoring of code.

by Asiri Rathnayake

Hi Ludovic, I have added PUT / MKCOL support for xwiki-webdav but MKCOL support is limited at this point. Users can add spaces, pages (into spaces), edit / write changes into pages. But i've hit a wall trying to implement prent-child relationships (adding child pages). At this point i have to emphasize that we need to refactor our code base before moving any further, because XWikiDavResourceImpl is really huge and it's complexity drives me nuts at some points (sooo many if-else switches). At a first glance i see following class structure, DavResource | + - XWikiDavResource (abstract) | + - XWikiRootDavResource (for views) | + - XWikiSpaceDavResource | + - XWikiPageDavResource | + - XWikiAttachmentDavResource I've almost hit a dead-end with the current code base (because i was trying to stick with it) and i seriously believe we have to refactor. I can complete this refactoring within a week's time so that it won't affect my time line. Ludovic, what so you think ? If any of you have comments about the design i propose, please let me know. Thanks. - Asiri

16 years, 7 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs