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

by Sergiu Dumitriu

Hi devs, I almost finished implementing http://jira.xwiki.org/jira/browse/XWIKI-1609 What remains to be done, is to find a good font to embed in XWiki. The best candidate would be the one from the StixFonts project, but that one is not yet released (delayed several years, now apparently is in the packaging stage; the expected date is August, but given the history of their release dates, it's more likely sometime in the winter or even next year). The next best candidate is FreeFont (http://savannah.gnu.org/projects/freefont/), but that one is GPL, and doesn't have complete support for asian characters. The third best candidate is an extended version of Computer Modern (http://canopus.iacp.dvo.ru/~panov/cm-unicode/), which is distributed under the X11 license, but it is less complete than FreeFont. For the moment, I'd be in favor of including the FreeFont, but we need to see if a GPL font can be redistributed or not, and maybe ask for permission to include it. WDYT? -- Sergiu Dumitriu http://purl.org/net/sergiu/

17 years, 2 months

2
2
0 0

[xwiki-devs] [GSoC]Try the Office Importer Plugin

by Wang Ning

Hi Vincent & all, I finish the clean of the plugin code and write a simple user manual. You can see it in http://dev.xwiki.org/xwiki/bin/view/Design/OfficeImporter#HQuickStart. All files needed for this plugin can be found in that page http://dev.xwiki.org/xwiki/bin/view/Design/OfficeImporter, except the openoffice install . Please give some feedback after try the plugin. Any feedback will be very appreciated. This plugin is very initial. It only put out the html code , not xwiki syntax, because the html code to xwiki syntax conversion should be done by XHTMLParser which is not ready yet. Open question: Now the plugin can handle the file which is uploaded to xwiki as a attachment. Do you think it's necessary that the office importer would have the upload feature itself or should provide a XWikiAction something like "bin/importer/Main/page"? Now the plugin can work. However it's a little complicate. If you want to convert a office document 1. you first upload the document 2. copy the attachment name(because the name of document change after upload) 3. edit the page and add the velocity code to use the importer plugin 4. save and view. I think it should be more simple. WDYT -- Sincerely, Wang Ning

17 years, 2 months

4
9
0 0

[xwiki-devs] XWiki - Browser full URL in xwiki page

by Prathap Pandian

Hi, How can i print the current browser full URL in xwiki page. I tired this one $doc.getURL("view"), but it displaying the url from the application name like this */xwiki/bin/view/Main/ *Is there any other way to print the whole browser URL in xwiki page like this* http://<server>:<port>/xwiki/bin/view/Main/ *-- Prathap* *

17 years, 2 months

3
3
0 0

[xwiki-devs] [GOSC] WebDav status

by Ludovic Dubost

Hi Asiri, When do you plan to deliver your milestone status ? Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

17 years, 2 months

2
1
0 0

[xwiki-devs] [GSOC][WEBDAV] Comments & Exposed properties

by Asiri Rathnayake

Hi Ludovic & All, Two small questions, 1. According to my understanding, current design of xwiki-webdav interface<http://dev.xwiki.org/xwiki/bin/view/Design/WebDAVService>does not take document comments into account (shouldn't they be exposed via webdav ?). 2. Which xwiki specific properties are to be exposed through this interface (out of author, revision , etc. etc.) ? Thanks a lot. - Asiri

17 years, 2 months

2
2
0 0

[xwiki-devs] [GSOC] [WEBDAV] MKCOL Where should it be allowed ?

by Asiri Rathnayake

Hi devs, current xwiki-webdav interface is exposed as follows, root | + - library | + - orphans | + - attachments | + - home | + - spaces My questions is, where should MKCOL (create collection) operation be allowed ? I believe it only makes sense in `spaces` view where we can allow the user to create a space (if he has appropriate access levels). Also, another doubt i have is about creating pages, should it be same as with collections where we manually add the wiki.txt and wiki.xml files into the collection once it is created ? Thanks a lot. - Asiri

17 years, 2 months

2
2
0 0

[xwiki-devs] [GSOC] help choosing a js lybrary/wrapper

by Miguel Bento

First of all, hi again! I'm developing the collaborative business drawing framework to integrate on XWiki and currently need some feedback. In order to provide the abillity of drawing SVG/VML/Canvas objects in the browser, this framework has many options that i shall explain: * A) Tatami, the GWT wrapper of the Dojo Toolkit library ( http://code.google.com/p/tatami/)* This is by far the most used option, and the reasons are somewhat obvious. - It wraps up the dojo toolkit code for GWT providing access to the GFX package's functionalities and thus giving us the possibility to draw objects in SVG/VML/Canvas. This is a very important point as it provides support for Safari with canvas objects and IE with VML objects, accomplishing thus a better product. - Provides the creation of basic and advanced drawing figures from squares to paths with drag and drop, scale, rotate and parameters specification. - It has the biggest active developer's base, having a lot of activity on their forum (http://groups.google.com/group/tatami) - It gives us efficiency and usability by being well developed. Personally, this is a key point for me as i've seen a lot of svg drawing boards slow and badly done. A demo of the tatami can be found here ( http://tatami.googlecode.com/svn/trunk/site/samples/TatamiDemo/index.html ) but don't mind the slow reaction of the site as it's using aloot of dojo objects(Fisheye, etc) and it's runing from the svn. After some coding with it, i realized it can indeed be very fast. IMHO, this looks like the winner.. we should use this wrapper for the job and if necessary develop some new items on it to provide us the required functionalities, which will also be needed in any other option. *B) JSGraphic's library ( http://www.walterzorn.com/jsgraphics/jsgraphics_e.htm) *As it's the case with Dojo Toolkit, this library can be used in GWT by including a wrapper on the project. The downsides of this alternative are obvious as, for example, it doesn't support's drag and drop or any interaction with the objects and is a one man project. It's allways good to have options heh! *C) Develop an API fit to the job* As this option might bring some (? small) benefits in efficiency and additional funcionalities, on the other hand, it's slowed by the time required to develop the API knowing that there are some fully functional good options out there. Talking about functionalities, Tatami provides every svg object and property that i remind me of and it's efficiency and usability are high, so there shouldn't be much more to do in this area. (besides implementating screw transformations, which aren't included in the latest realease of Tatami :) In the next days i'll be building a propotype of a drawing API so please give me your opinions. My vote : +1 Tatami Best Regards, Miguel Bento.

17 years, 2 months

7
10
0 0

[xwiki-devs] [GSOC] Collaborative Drawing content

by Miguel Bento

As some of you know, the collaborative drawing application will use svg( http://www.w3.org/Graphics/SVG) syntax in order to draw the various objects and therefore we have to found a way to store and edit this information. Currently we have two implementation options to perform this task, the Object approach and the Attachment approach, and are trying to decide which one is the better, so, in order to perform that i've prepared a few mockups. To clarify the intent of these approachs, it's good to keep in mind that a drawing has various edition modes and privileges.More specifically, we should have 3 user modes: - Administrator: In administrator mode the drawing content will be presented by the SVG editor and the user can: - Edit the drawing - Add or remove users - Modify the drawing name and description - Editor: In the editor mode the drawing content will also be presented by the SVG editor but the user can only edit the drawing content. - Viewer: In the viewer mode the drawing will be presented as .png file using the Batik plugin and therefore the user only has rights to view the drawing. The object approach: In this perspective, the SVG content would be saved on a SVG object with the following properties: http://dl.getdropbox.com/u/47956/XWiki_SVG_Object_Description.pdf , this SVG object would be available in the page, could be accessed by the getContent() method and edited with a simple saveContent() call. In order to store the privileges and the creation date the current page should be used and to show that here's example: ( http://dev.xwiki.org/xwiki/bin/download/Design/CollaborativeDrawing/XWikipa…) Here's a example of the view mode: ( http://dev.xwiki.org/xwiki/bin/download/Design/CollaborativeDrawing/SVGObje…) And finally here's a edition mode example: ( http://dev.xwiki.org/xwiki/bin/download/Design/CollaborativeDrawing/SVGObje…) The attachment approach: In this approach, the SVG content will be stored on a attachment and so all the edition operations would be saved on it as new versions. It's identical to the object approach except in the fact that the svg content wouldn't be in the page itself(we still would need a reference to the attachment on it). When a user want's to go to edition mode, in this approach a full-screen editor will be launched like the next one: ( http://dev.xwiki.org/xwiki/bin/download/Design/CollaborativeDrawing/SVGObje…) and all the document properties would have to be stored on the attachment. Note: Obviously the full screen mode can be used in both approaches and the examples shown are possible desings for the UI which in the future will be discussed. (Refer to http://dev.xwiki.org/xwiki/bin/view/Design/CollaborativeDrawingfor a better version) So, WDYT? Best Regards, Miguel Bento

17 years, 2 months

2
1
0 0

[xwiki-devs] XWiki - Dynamic Space Name In The Links

by Prathap Pandian

Hi, I tried to display the space name dynamically in the links. Example: In the new panel i have give like this [Home>*Main.WebHome*] Basically all the spaces will have WebHome page by default. So i tried to change the space name dynamically. And here what i have given in the panel... [Home>*$doc.space.WebHome*] But it seems not working for me. And it provided me the following *url*http:// <server>:<port>/xwiki/bin/edit/%24doc.space/WebHome?parent=Main.WebHome&editor=wysiwyg Is there any other way to do this...? *OR* I did it wrong...? -- Prathap

17 years, 2 months

2
2
0 0

[xwiki-devs] [GSOC][WEBDAV] DAVExplorer on Linux

by Asiri Rathnayake

Hi All, I'm having a small issue with DAVExplorer on fedora 6 where i cannot put the password (for login) into password box because it doesn't accept keyboard input. I know this is something wrong with fedora (or the jdk i'm using) because it works fine on XP. This is not a big issue for me because i can simply disable authentication related code in the webdav servlet and carry on my development but i thought it is best to make a note (in case someone knows how to fix it). Up untill now i have been using nautilus's built-in webdav support for testing but for advaced functionality i need DAVExplorer. Anyway, as i said, this is not a big issue (but surely it is a big annoyance), if anyone knows how to fix it, feel free to advice :) Thanks. - Asiri

17 years, 2 months

1
0
0 0

[xwiki-devs] Mirror offer

by Squirrel

Hi guys, I'm just downloading the 1.5M2 release to test your new administration GUI. The speed is currently 30KB/s.... I've a 100Mbit/s dedicated server located in Germany (Hoster: Hetzner). I can spend, let's say 100GB/month at full speed, would that help? Cheers, Squirrel PS: Will you sometime publish some statistics on this topic?

17 years, 2 months

1
1
0 0

[xwiki-devs] How I fix another encoding problem and my experience on encoding for non-English language

by LiDan

I met another encoding problem. In firefox, I edited a page by wysiwyg editor, when I saved the page, all the links with Chinese name are ill formated(the href part).So you can not get the right page by click a link. But in IE, there is no such problem. So I checked the wysiwyg editor to find where the hrefs begin ill-formated. Finally I found the file wiki_editor/plugins/core.js After line 173, I add a new line. href = this.trimString(att["href"]); href=decodeURI(href);//added by lidan, decode URI Then tested again, it's OK, the problem's gone. I didn't go deeply why only in firefox there is such problem. I don't know if others have met the same problem. If you do, you can try this way, it may help. I have been implementing my own wiki based on xwiki for about several months. Normally, xwiki is a very good product. But when I'm trying to implemented it in my language, Chinese, I met many encoding problems. Fortunatelly I can get help from this forum, and many of the problems has been fixed. In my experience, there are several factors will affect the encoding, the operation system, web server, web server configuration, xwiki configuration, your web-browser. But it seems that you can not find a general way to fix all the problems. Sometimes you should deal with them one by one. -- View this message in context: http://www.nabble.com/How-I-fix-another-encoding-problem-and-my-experience-… Sent from the XWiki- Dev mailing list archive at Nabble.com.

17 years, 2 months

1
0
0 0

Re: [xwiki-devs] Export/Import batch mode

by Thomas Mortagne

On Mon, Jun 30, 2008 at 8:59 PM, <acannone(a)imolinfo.it> wrote: > Invoking directly the class com.xpn.xwiki.tool.backup.ExporterMain I have the following Exception: > > Exception in thread "main" java.lang.RuntimeException: Component manager has not been initialized before lookup for [org.xwiki.cache.CacheFactory] for hint [default] > at com.xpn.xwiki.web.Utils.getComponent(Utils.java:553) > at com.xpn.xwiki.XWiki.getCacheFactory(XWiki.java:5130) > at com.xpn.xwiki.store.XWikiCacheStore.initCache(XWikiCacheStore.java:86) > at com.xpn.xwiki.store.XWikiCacheStore.initCache(XWikiCacheStore.java:80) > at com.xpn.xwiki.store.XWikiCacheStore.<init>(XWikiCacheStore.java:62) > at com.xpn.xwiki.XWiki.initXWiki(XWiki.java:675) > at com.xpn.xwiki.XWiki.<init>(XWiki.java:618) > at com.xpn.xwiki.XWiki.<init>(XWiki.java:612) > at com.xpn.xwiki.tool.backup.AbstractPackager.createXWikiContext(AbstractPackager.java:73) > at com.xpn.xwiki.tool.backup.Exporter.exportDocuments(Exporter.java:53) > at com.xpn.xwiki.tool.backup.ExporterMain.main(ExporterMain.java:57) This error is because you are trying to use XWiki Platform without initializing it. This particular error is about plexuw component manager needed because since versio 1.5M2 XWiki cache service is a plexus component. You should look at shared-test (trunks//xwiki-platform-tools/xwiki-shared-tests/src/main/java/com/xpn/xwiki/test/AbstractXWikiComponentTestCase.java) project for a way to create and initialize one you will need the plexus.xml also in shared-tests. You could directly extends AbstractXWikiComponentTestCase like unit tests do but it's... for unit tests and extends junit, jmock etc. > > Any ideas or suggestions? > > I have the previous error calling a script that contains something like this: > java -classpath $XWIKICLASSPATH com.xpn.xwiki.tool.backup.ExporterMain /home/acannone/xwiki/prova/export xwiki /home/acannone/xwiki/prova/hibernate.cfg.xml > > There is someone that can tell me how to invoke and configure the maven packager plugin in my example? > > > > Thanks > > > Thomas Mortagne wrote: >> >> Hi, >> >> I doubt there is any java level documentation on import/export but you >> can look at some good examples of how to use packager plugin : >> - com.xpn.xwiki.web.ExportAction#exportXAR(XWikiContext) >> - com.xpn.xwiki.web.ImportAction#render(XWikiContext) >> >> On Mon, May 5, 2008 at 3:19 PM, Lorenzo Manzoni <lmanzoni(a)imolinfo.it> >> wrote: >>> I would like to execute an export of all/some of the wiki pages in a >>> batch mode (ex. with a script and a java program). >>> In the same way I would like to execute an import. >>> Is there an easy way to do this? >>> >>> Looking forward in the xwiki sources I found two classes that seem to do >>> what I want: >>> >>> * com.xpn.xwiki.tool.backup.ExporterMain >>> * com.xpn.xwiki.tool.backup.ImporterMain >>> >>> Both classes are in the maven plugin called xwiki-packager-plugin. >>> Is there any documentation that explain how use that plugin? >>> >>> >>> thanks, >>> Lorenzo >>> _______________________________________________ >>> devs mailing list >>> devs(a)xwiki.org >>> http://lists.xwiki.org/mailman/listinfo/devs >>> >> >> >> >> -- >> Thomas Mortagne >> _______________________________________________ >> devs mailing list >> devs(a)xwiki.org >> http://lists.xwiki.org/mailman/listinfo/devs >> >> > Quoted from: > http://www.nabble.com/Export-Import-batch-mode-tp17061634p17062120.html > > -- Thomas Mortagne

17 years, 2 months

2
5
0 0

[xwiki-devs] XWiki - Print Skin Name

by Prathap Pandian

Hi, How can i print the current skin name in the xwiki page. -- Prathap

17 years, 2 months

2
1
0 0

[xwiki-devs] [VOTE] Remove branch 1.3 builds from Continuum + Remove 1.3 branch

by Vincent Massol

Hi, I'd like to propose removing core 1.3 from Continuum. It's taking resources and the build even fails. Then I'd also like to propose removing branch 1.3 for Core/Web/XE since: * We're no longer supporting it here. * Apparently according to Ludovic it has some problems. If someone needs to release a new 1.3.3 one day he can always take the 1.3.3 tag and branch it. Here's my +1 Thanks -Vincent

17 years, 2 months

6
6
0 0

[xwiki-devs] XWiki - Check Two Objects

by Prathap Pandian

Hi, I need to check the two values are equal. One is in object($todoObj.Assignee) and another one in string($context.user). We tried this way, but it seems not working #set($username=$context.user) #if($username.equals(todoObj.Assignee)) #end -- Prathap

17 years, 2 months

2
2
0 0

[xwiki-devs] XWiki - Watch List In Panels.

by Prathap Pandian

Hi, Is it possible to have my watch list options in the panels. -- Prathap

17 years, 2 months

2
2
0 0

[xwiki-devs] New rendering don't parse and render xhtml properly

by Wang Ning

Hi Vincent, I just tried the new rendering class. My test xhtml is: <html> <head> <title>title of this page</title> </head> <body> <div> <p>first paragraph, really.</p> <p>second paragraph for test.</p> </div> </body> </html> I use WikiModelXHTMLParser to parse it and use XWikiSyntaxRenderer to write the result to a file. The output is : page paragraph really. test. I have tried add a <a href="">link</a> to the input which bring a parser exception. Just tell you what I find and I'll drill into the code to see what's wrong. Any suggestion? Thanks. Wang Ning

17 years, 2 months

3
4
0 0

[xwiki-devs] Font used by the code macro (was : Problem with Code Macro)

by Jean-Vincent Drean

You can add this in style.css : ------------8<---------------------------- pre, pre span { font-family:Courier; } ------------8<---------------------------- Devs : I'd be +1 to modify this in our skins, may be should add a special css class to the PREs generated by the code macro to achieve this. WDYT ? On Wed, Jul 2, 2008 at 4:35 PM, atw <traninger(a)mdw.ac.at> wrote: > > > Most likely I'm missing something, but maybe someone can help me out with > this: > > when I insert something like: > > {code} > #set($e = "Test") > {code} > > in a page, I'd expect the content displayed in Courier or a similar font. > But all I can get is Arial... > > (XE 1.5 RC2 as well as 1.41 on Windows XP, Tomcat 6.0, Oracle 10.2.0.3, > Firefox 2). > > Thanks for any help on this! > -- > View this message in context: http://www.nabble.com/Problem-with-Code-Macro-tp18238925p18238925.html > Sent from the XWiki- Users mailing list archive at Nabble.com. > > _______________________________________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/users > -- Jean-Vincent Drean

17 years, 2 months

3
4
0 0

Re: [xwiki-devs] Administration Application Needed Files

by Thomas Mortagne

On Thu, Jun 26, 2008 at 7:00 PM, Evelina Slatineanu <evelina.slatineanu(a)xwiki.com> wrote: > Hi all, > > > > For the new Administration application to work properly in an empty wiki > (create users, groups, set rights etc), the following files have to be moved > from XE to Administration: > > > > Xwiki.Admin > > Xwiki.Users > > Xwiki.XwikiUserSheet > > Xwiki.XWikiUserTemplate > > Xwiki.AdminGroup > > Xwiki.AllGroup > > Xwiki.Groups > > Xwiki.XwikiGroupSheet > > Xwiki.XwikiGroupTemplate > > Xwiki.Rights > > Xwiki.GlobalRights > > Xwiki.DefaultSkin > > Xwiki.Skins > > Xwiki.XwikiPreferences -1 for XWiki.XWikiPreferences at least the one from XE which contains rights configuration in it. Plus admin should be able to automatically create the XWiki.XWikiPreferences page when needed. > > > > I already sent the patch to JV, we only need votes. I'm +1 > > > > Thanks, Evelina > > > > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs > -- Thomas Mortagne

17 years, 2 months

3
5
0 0

[xwiki-devs] Bug Fixing Day Results for 02 July 2008

by Jean-Vincent Drean

Yesterday was our 4th bug fixing day. The following bugs were fixed: http://tinyurl.com/5evc9r - Artem * XWIKI-1976 : Importing attachments will increase the attachment version - Evelina * XAADMINISTRATION-4 : New Administration UI doesn't display nicely under the Albatross skin - Jean-Vincent * XWIKI-2536 : French translation is outdated * XWIKI-2535 : Patch to English translation - Thomas * XWIKI-2495 : LDAP Authentication re-create global user locally So that's a total of 5 bugs fixed. Well done everybody and thanks to all who participated. JV.

17 years, 2 months

1
0
0 0

[xwiki-devs] New Comments & Ratings design proposal

by raluca.morosan＠xwiki.com

Hi devs, Due to the fact that we have to extend the platform features, a proposal would be to extend the current comment feature, and add 2 new ones: annotations and ratings. Here are the design proposals for comments and ratings: http://dev.xwiki.org/xwiki/bin/view/Design/RatingSystem http://dev.xwiki.org/xwiki/bin/view/Design/NewCommentsPlugin You can review them and give feedbacks. Thank you, Raluca.

17 years, 2 months

3
2
0 0

[xwiki-devs] XWiki - User ID

by Prathap Pandian

Hi, How to print the user id in xwiki pages.(Like this:XWiki.Admin). *$!xwiki.getUserName($context.user, false) This one is to print the user name. *-- Prathap* *

17 years, 2 months

2
2
0 0

[xwiki-devs] [discussion] configuration files loading

by Artem Melentyev

Hi, devs. I would like to discuss about How we should load external configuration files (such as hibernate.cfg.xml, repository.xml and others) AFAIK, we agreed the following algorithm to load external config files: 1. filesystem 2. ServletContext 3. classpath. But we still lack some implementation for it. So we duplicate code in store, cache and others modules. How can it be implemented right? (Spring fwk for example have nice Resource classes: http://static.springframework.org/spring/docs/2.5.x/reference/resources.html and Resource classes injected simply by string path.) I see 2 ways: 1. Add InputStream getResourceAsStream(String) method to our Utils class. +: simple but I'm not sure it is right in V2 arch. 2. Implement Chained, FileSystem and ClassPath application contexts and provide one chained application context which tries to load resource from filesystem, servlet and classpath contexts in this order. -: I think it is overhead for now. I'm +1 for 1. now. Another question is How we should configure config file path. I think we should provide default path in component class (String somepath = "some/path") and we can override it in components.xml So no more "xwiki.store.hibernate.path" and others params in xwiki.cfg. Use components.xml instead. xwiki.cfg should contain more useful and global params. WDYT? -- Artem Melentyev

17 years, 2 months

2
1
0 0

[xwiki-devs] Releasing xwiki-spacemanager 1.0.2 and xwiki-invitation manager 1.0.1

by Jerome Velociter

Hello devs, I'm about to release the following plugins : * xwiki-spacemanager 1.0.2 (with this changelog: http://tinyurl.com/4adfuq) * xwiki-invitationmanager 1.0.1 (with this changelog: http://tinyurl.com/4xtqw7) Both are bugfixe releases, mainly for the curriki project. Regards, Jerome.

17 years, 2 months

3
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