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

Re: [xwiki-devs] [xwiki-notifications] r14514 - in sandbox/xwiki-core-rest: . .settings src src/main src/main/java src/main/java/org src/main/java/org/xwiki src/main/java/org/xwiki/rest

by Asiri Rathnayake

On Tue, Dec 2, 2008 at 11:17 PM, SVN fmancinelli < sandbox-notifications(a)xwiki.org> wrote: > Author: fmancinelli > Date: 2008-12-02 18:47:06 +0100 (Tue, 02 Dec 2008) > New Revision: 14514 > > Added: > sandbox/xwiki-core-rest/.classpath > sandbox/xwiki-core-rest/.project > sandbox/xwiki-core-rest/.settings/ > sandbox/xwiki-core-rest/.settings/org.eclipse.jdt.core.prefs > sandbox/xwiki-core-rest/.settings/org.eclipse.wst.common.component > > sandbox/xwiki-core-rest/.settings/org.eclipse.wst.common.project.facet.core.xml > sandbox/xwiki-core-rest/.settings/org.maven.ide.eclipse.prefs I think it's not ok to commit these files. May be it's ok for sandbox ? - Asiri

16 years, 9 months

1
0
0 0

[xwiki-devs] Office importer not in 1.7

by Vincent Massol

Hi everyone, I've discussed with Asiri and seen that we're in a hurry with the 1.7 release and it's a bit late we've agreed that the best course of action was to postpone the office importer inclusion in XE till XE 1.7.x or 1.8M1. I hope this is fine with everyone (not that I don't see much option apart from delaying XE 1.7). Asiri is thus currently focusing on finishing webdav support and fixing outstanding issues till 1.7 final. He'll need help from committers to apply his patches. Thanks -Vincent

16 years, 9 months

1
0
0 0

[xwiki-devs] [VOTE][UI] WYSIWYG Wiki Explorer

by Jean-Vincent Drean

In a previous thread we've discussed about how to add a link in the WYSIWYG editor, and more generally, how to browse the wiki from a WYSIWYG dialog box (See http://markmail.org/message/tyxrcr24w3n6m2pn for more details). After some thinking and a discussion with Laurent Lunati, I'd like to suggest a 3rd way of browsing the wiki from the WYSIWYG: an enhanced tree menu. I've put the mockups and Pros/Cons on this wiki page : http://dev.xwiki.org/xwiki/bin/view/Design/NewWysiwygEditorWikiExplorer This wiki explorer widget would be used in the link dialogs, image dialogs, file (attachment) dialogs. Here's my +1 for 3) A). +1 for 3) with filter option. >From the implementation POV 3) is probably the most difficult proposal and 1) the simplest one. Widget 3) would need to be a reusable (and highly configurable) GWT component so that we could use it as our main navigation/reorganization tool in the future. This tree would replace our current treeview (Main.AllDocs) which is AFAIR the only page using the YUI library in XE. Thanks, JV.

16 years, 9 months

11
47
0 0

[xwiki-devs] [VOTE] Include URL path based multiwiki in 1.6.2 and 1.7

by Thomas Mortagne

Hi devs, I just finished a feature to be able to use mutiwiki without any use of virtual host (ans so no need for a configured DNS server). It does not replace the DNS based multiwiki it just add another way to access subwiki so you can still use both. However all the URLs will be generated in a way or another depending if urlpath is enabled or not. So basically it add the possibility to access the wiki "wikiname" using http://127.0.0.1/xwiki/subwiki/wikinname/view/Main/WebHome. See http://jira.xwiki.org/jira/browse/XWIKI-2824 Normally I would wait for 1.8 branch to commit this but we have an internal need for it to be included in the 1.6 branch (and if it's included in 1.6, why not include this in 1.7 ;)). Can we include it safely in 1.6/1.7 ? : it should be, if you don't enable xwiki.virtual.urlpath in xwiki.cfg (and it will be disabled by default), all will work exactly like this feature did not exists. Here is my +1 Thanks, -- Thomas Mortagne

16 years, 9 months

7
9
0 0

Re: [xwiki-devs] [Proposal] Adding/Editing a link in the new WYSIWYG (was Re: [Proposal] WYSIWYG 1.7 Roadmap)

by Ecaterina Valica

For a new user will be best just to have an "Insert link" action. If the link is external - default behavior is internal - transparent (like an external one - but parse the URL for advanced editing, letting user browse wikis, spaces) After editing: new page inserted exists - change the link the page doesn't exist - create the page + change the link See the image:http://dev.xwiki.org/xwiki/bin/download/Design/NewWysiwygEditorInterf… The actions are just sketched, all the thinks previously discussed can be inserted. So, the idea is to take the URL and break it in <wikiName>:<SpaceName>.<PageName> if you need this format for further browsing and editing. This way you let beginner user to insert a link in one step. Thanks Observation: When clicking on [Space Name > "Features"] the E dialog appears.

16 years, 9 months

1
0
0 0

[xwiki-devs] [WEBDAV] Getting rid of xwiki-webdav-plugin.

by Asiri Rathnayake

Hi Devs, xwiki-webdav-plugin was developed to provide means to calculate webdav urls of xwiki documents and attachments. But as it turns out, for a given document or an attachment, calculating webdav url is simply a string manipulation operation. It doesn't require any support from the webdav component (and thus the webdav plugin). So, I'm thinking we should remove the webdav plugin completely. WDYT ? Thanks. - Asiri

16 years, 9 months

5
4
0 0

[xwiki-devs] Programming rights checks against top-level including doc or included doc

by Denis Gervalle

Hi, There is a major discrepancy in the way the programming rights are evaluated for the access to the privileged API from velocity compare to the right to execute groovy code. In the API, the right to access a priviledged API is evaluated against the sdoc in the current context, which is the document that contains the currently executed velocity code. Here is the code extracted from the current RightService implementation that does so: public boolean hasProgrammingRights(XWikiContext context) { XWikiDocument sdoc = (XWikiDocument) context.get("sdoc"); if (sdoc == null) sdoc = context.getDoc(); return hasProgrammingRights(sdoc, context); } In the XWikiGroovyRenderer, the right to render a groovy code is evaluated against the content doc, which is the top-level document that have directly or indirectly included the document that contains the evaluated groovy code. Here the excerpt from the code that made this check: if (! context.getWiki().getRightService().hasProgrammingRights(contentdoc, context)) { return content; } These are two opposed methods. As a direct consequence, a Sheet document (ie XWikiUserSheet) may be developed in velocity and use the priviledged API, but it is impossible to put a single line of Groovy in it, since the "instance" of the template documents that include the Sheet are usually created by users without programming rights. The debate is now, what is the original or current intend. Do you want: 1) to have a very secure situation, and therefore change hasProgrammingRights() implementation (why do we have a sdoc than?), or 2) to have a flexible, more responsible solution, were user having programming rights should take care not writing risky code, and therefore change the groovy renderer to accept groovy code based on contextdoc (sdoc in that place), so groovy and velocity gets the same access level ? The current situation is for me not acceptable, since it is a mix of 1) and 2) depending on the language, and there is no reason that the language influence the rights you have. Thanks for your comments... Denis -- Denis Gervalle SOFTEC sa http://www.softec.st

16 years, 9 months

3
4
0 0

[xwiki-devs] about the xwiki table cell split and merge

by Huang Sheng

hi,All I have a question about the xwiki table usage.When I have a table ,I try to split one cell to more cells or merge some cells into one cell,I find this function is invalid,when I click the save button ,the saved table is not what I want,is anybody know how to solve this issue?or anyone who has the same problem?is xwiki support this syntax?if so,who has the xwiki script for the table? Thanks Steven

16 years, 9 months

2
1
0 0

[xwiki-devs] Inclusive groups and membership test in velocity

by Hoani Cross

Hi ! I installed recently the 1.6 version of XWiki and found that a new functionnality allows to add logical groups to the group members list : great ! This recursive inclusion is properly managed in global rights (like allowing a global group for accessing a space) but this does not seem to be included in velo xwiki API. For example I have one client that belongs to its company group XWiki.MyClientCompanyGroup that I added to the group XWiki.Clients. I have a dedicated part of my menu for clients and I tests whether the current user is a client or not with the test `$xwiki.user.isUserInGroup("XWiki.Clients")` which always return false :( Maybe a special macro could help... anyone has a clue ? -- Hoani CROSS Globotraders Tahiti Founder [http://globotraders-tahiti.com]

16 years, 9 months

2
1
0 0

[xwiki-devs] Using SmartGWT?

by Vincent Massol

Hi, SmartGWT has just been released: http://www.jroller.com/sjivan/entry/smartgwt_1_0_released See also: http://code.google.com/p/smartgwt/ Last, interesting interview on InfoQ: http://www.ongwt.com/post/2008/11/27/SmartGWT-%3A-A- QampA-with-Sanjiv-Jivan2 Both smartGWT and smartClient are under LGPL (v3 for SmartClient, see http://www.smartclient.com/product/smartLGPL.jsp) It seems to me this is something we could use, it has some great widgets such as live grids, draggable treeview, and in general everything we could need. WDYT? Thanks -Vincent

16 years, 9 months

2
1
0 0

[xwiki-devs] [VOTE] XEclipse release

by Fabio Mancinelli

Dear all, I would like to release XEclipse soon. During the last days I've fixed many of the outstanding bugs thanks also to the effective collaboration of Eduard Moraru who provided a lot of patches and I think that now XEclipse is pretty stable, usable and functional. This release incorporates a lot of features that have been implemented during the last months. In particular a better integration with the Eclipse ecosystem, object editor, translation management, page history, syntax highlighting and completion (thanks to the work done by Malaka during the last GSoC and Venkatesh) and many other improvements. There are still many things to do but I think that it's a priority to have a new version out asap in order to have more feedbacks from users and to build upon it. Due to some previous engagements I think I will be able to release it on Friday or during the weekend. WDYT? -Fabio ____________________________________

16 years, 9 months

7
9
0 0

[xwiki-devs] [Proposal] Add JAR resource HTML extension in SX

by Jerome Velociter

Hello everybody, Right now with Skin eXtensions we can hit "jsx" and "ssx" action URLs to retrieve JavaScript and CSS files, that either comes from XObjects (the original SX idea) or from JAR resources (since SX 1.3). I'm playing with the idea of adding a new action that would return text/html, possibly available as JAR resource extension _only_. I explain below how I came to this need. This morning I gave some thoughts on the behavior the {{map}} macro should have when the Internet is not reachable, but the wiki is (any resemblance to actual facts is... not coincidental;)). The only alternative I found not to have the macro blocking the whole page loading until the HTTP requests gives up trying to get the library from the service provider (google, yahoo, etc.) is to have it being loaded in an iframe (and then display the map in that iframe, too). For this to happen however, I need to pass an URL to that iframe which will give the html needed (<script> tag for the library, <script> to consume the library, and probably a <div> container for the map itself, etc.) Since I work with the constraint of being to publish the macro as a jar only, I would like this HMTL file to be a resource file of my macro (otherwise, a simple wiki page called with "xpage=plain" would do the trick, obviously). Since ssx and jsx returns content type according to the resource they provide, we cannot use them for this purpose (and it would be hackish use anyway). Thus I propose we add a new action "hsx" for example, to return "text/html" content. This extension does not have much sense as a document extension (since we don't know where to inject the result, unless the new XClass has a "extension point" field but then it becomes somehow an IX class), so I it would be available only as JAR resource extension. Did I miss something there ? Sergiu what do you think ? Others ? Jerome.

16 years, 9 months

1
3
0 0

[xwiki-devs] [Rendering] Refactoring Idea: JCR...

by Vincent Massol

Hi, One refactoring idea: we could probably replace our Block implementation by the JCR API. This would allow to benefit from already existing code (JackRabbit for ex) such as the query manager, navigation in the XDOM tree, etc. Pros: - less code to write - more powerful API - standard-based Cons: - Need to rewrite our Block implementation - more external dependencies (jackrabbit and what it draws) WDYT? Thanks -Vincent

16 years, 9 months

1
1
0 0

[xwiki-devs] Join me on Bebo

by Arvind Gupta

You will like it. Click to find out why Please accept or reject this invitation by clicking below: http://www.bebo.com/in/8210404647a433319350b135 ...................................................................... This email was sent to you at the direct request of Arvind Gupta <arvind.bernaulli(a)gmail.com>. You have not been added to a mailing list. If you would prefer not to receive invitations from ANY Bebo members please click here - http://www.bebo.com/unsub/8210404647a433319350 Bebo, Inc., 795 Folsom St, 6th Floor, San Francisco, CA 94107, USA.

16 years, 9 months

2
2
0 0

[xwiki-devs] Resolving the mismatch between an xwiki page and a dav collection resource.

by Asiri Rathnayake

Hello Devs, In webdav view of xwiki, a wiki page (document) is represented by a webdav collection resource (somewhat like a directory). This collection resource is comprised of wiki.txt, wiki.xml, attachments & child pages. As you can see, there is a mismatch between these two concepts: without wiki.txt & wiki.xml (children), a wiki page (the parent) cannot exist, but this is the otherway around in a filesystem like structure. So a question arises, in webdav space what does it mean to delete a wiki page ? 1. We can treat deleting wiki.txt and/or wiki.xml as deleting the whole page. But deleting the parent when only the children were asked to be deleted is wrong. And most of the webdav clients go insane. 2. We can prohibit wiki.txt & wiki.xml being deleted (i.e. throw an exception). But this would prohibit users from deleting pages on some clients because they use a recursive delete procedure (i.e. delete children first and then delete the parent). When deleting children fails, the whole operation fails. 3. We can trick the clients to believe that the delete was a success (repport AOK) and continue like nothing went wrong. This way a recursive delete will succeed. But if the client re-request the resource just to make sure the delete was a success, the deleted wiki.xml and wiki.txt will appear again. Some clients indeed behave like this and they fail. This is the current approach we have taken. 4. We can put wiki.txt & wiki.xml inside the HttpSession object the first time we initialize a particular resource. This way, the deletes will succeed and even if the client re-validates the delete, those child resources will not appear again. This approach seems to prevent all of the above mentioned problems but again, we're using a hack. Also, this implies that a page (dav collection) can exist without wiki.txt & wiki.xml. I voting in favour of the 4th option. Do you see any other way to get around this mismatch ? Thanks. - Asiri [image: Asiri Rathnayake's Facebook profile]<http://www.facebook.com/people/Asiri_Rathnayake/534607921>

16 years, 9 months

2
3
0 0

[xwiki-devs] [Rendering] Honor whitespaces in cells or not?

by Vincent Massol

Hi, Do we want to honor whitespaces in table cells or not? The main advantage of trimming them is to get aligned cell symbols. See http://www.wikicreole.org/wiki/Creole1.0#section-Creole1.0-Tables Right now we're honoring whitespaces (they are significant). If we want to be consistent with normal wiki text we should honor them since we're honoring spaces in wiki text. However we just need to agree that it won't be possible to get nicely aligned cell delimiters then. WDYT? Thanks -Vincent

16 years, 9 months

6
13
0 0

[xwiki-devs] [Rendering] Refactoring Proposal

by Vincent Massol

Hi, I'd like to propose refactoring the Listener/Renderer classes for the following reasons: * too hard to write renderers since they're using a "streaming" API which makes it very difficult to have lookaheads * streaming api not required since we're using a XDOM object which "breaks" streaming anyway Thus I'm proposing to: * Remove Listener interface * Modify Renderer interface to have a single method: render(XDOM, WikiPrinter) * Rewrite existing Renderers and make them components (it would now be possible) I have brainstormed on this with Thomas Mortagne and we have both agreed that we don't see any problems with this since we absolutely need the XDOM object for: * ability to have macro priorities (TOC, Include macro, etc) and powerful transformations in general * ability to cache parsed content Let me know what you think quickly since I'd like to start the refactoring ASAP since it's a prerequisite for doing another refactoring (moving the XWikiXhtmlEscapeHandler to the XWikiSyntaxRenderer) which itself is required for solving this issue: http://jira.xwiki.org/jira/browse/XWIKI-2851 Thanks -Vincent

16 years, 9 months

1
0
0 0

[xwiki-devs] Translations : syntax to use (msg.get values) to internationalize pages

by Thomas Eveilleau

Hello, I'd like to work on translations of default XE pages (pages that are not internationalized yet) like Photos.WebHome, Main.Tags, Panels etc. In order to do things correctly I'd like to now the syntax I should use for the $msg.get values. What we have in a page like XWiki.XWikiUserSheet is : "platform.core.profile.firstname" for the firstname 1 ) Should I use the same syntax ("platform.core.tags.title" for the title of Main.Tags - if i keep my example) ? 2 ) Or should we use more scalable values (tomorrow we will have a core and applications on it : should we consider the Panels as an application and have something like "application.panel.panelname.element" ?). 3 ) Maybe that we also can use things like the fullname of a page in the value (to quickly identify it) and having something like : "appplication.panel.Panels.Search.title" I'm waiting for your advices on this (1 / 2 / 3 or another proposal). Thanks, Thomas Eveilleau

16 years, 9 months

5
9
0 0

[xwiki-devs] java.lang.ClassNotFoundException: org.xwiki.container.servlet.XWikiPlexusServletContextListener

by Juergen Lorenz Simon

Hi, I'm trying to develop plugins for XWiki using Eclipse 3.4. I went through the process outlined in the developer wiki twice and can not get the project to start up. (xe- debug-web). When I start the web project in Tomcat 6, I get hit by this exception: Nov 26, 2008 6:47:52 PM org.apache.tomcat.util.digester.SetPropertiesRule begin WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting property 'source' to 'org.eclipse.jst.jee.server:xe-debug-web' did not find a matching property. Nov 26, 2008 6:47:52 PM org.apache.catalina.core.AprLifecycleListener init INFO: The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: .:/Users/simon/Library/Java/Extensions:/Library/ Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java Nov 26, 2008 6:47:52 PM org.apache.coyote.http11.Http11Protocol init INFO: Initializing Coyote HTTP/1.1 on http-8080 Nov 26, 2008 6:47:52 PM org.apache.catalina.startup.Catalina load INFO: Initialization processed in 633 ms Nov 26, 2008 6:47:52 PM org.apache.catalina.core.StandardService start INFO: Starting service Catalina Nov 26, 2008 6:47:52 PM org.apache.catalina.core.StandardEngine start INFO: Starting Servlet Engine: Apache Tomcat/6.0.18 Nov 26, 2008 6:47:52 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Error configuring application listener of class org.xwiki.container.servlet.XWikiPlexusServletContextListener java.lang.ClassNotFoundException: org.xwiki.container.servlet.XWikiPlexusServletContextListener at org .apache .catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java: 1387) at org .apache .catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java: 1233) at org .apache .catalina.core.StandardContext.listenerStart(StandardContext.java:3786) at org.apache.catalina.core.StandardContext.start(StandardContext.java: 4342) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java: 1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:719) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java: 1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java: 443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java: 710) at org.apache.catalina.startup.Catalina.start(Catalina.java:578) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun .reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: 39) at sun .reflect .DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: 25) at java.lang.reflect.Method.invoke(Method.java:585) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Nov 26, 2008 6:47:52 PM org.apache.catalina.core.StandardContext listenerStart SEVERE: Skipped installing application listeners due to previous error(s) Nov 26, 2008 6:47:52 PM org.apache.catalina.core.StandardContext start SEVERE: Error listenerStart Nov 26, 2008 6:47:52 PM org.apache.catalina.core.StandardContext start SEVERE: Context [/xe-debug-web] startup failed due to previous errors Nov 26, 2008 6:47:52 PM org.apache.coyote.http11.Http11Protocol start INFO: Starting Coyote HTTP/1.1 on http-8080 Nov 26, 2008 6:47:53 PM org.apache.jk.common.ChannelSocket init INFO: JK: ajp13 listening on /0.0.0.0:8009 Nov 26, 2008 6:47:53 PM org.apache.jk.server.JkMain start INFO: Jk running ID=0 time=0/37 config=null Nov 26, 2008 6:47:53 PM org.apache.catalina.startup.Catalina start INFO: Server startup in 1003 ms I took extra care the second time round to ensure I followed the instructions to the letter. I noticed again that the WEB-INF/lib directory is EMPTY. I assumed that Maven should download and install the required jarfiles there? Am I missing something? Cheers, J.L.Simon

16 years, 10 months

2
1
0 0

Re: [xwiki-devs] [xwiki-notifications] r14446 - sandbox/xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/officeimporter/filter

by Sergiu Dumitriu

asiri (SVN) wrote: > Author: asiri > Date: 2008-11-26 07:18:39 +0100 (Wed, 26 Nov 2008) > New Revision: 14446 > > Modified: > sandbox/xwiki-plugin-officeimporter/src/main/java/com/xpn/xwiki/plugin/officeimporter/filter/HtmlStyleFilter.java > Log: > XAOFFICE-1 : Develop the initial feature set for office-importer plugin. > > * Adding 'colspan' attribute to the allowed attribute lists under strict & moderate filter levels. This is acceptable since 'colspan' is a structuring element rather than styling element. Then rowspan should be allowed, too. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 10 months

1
0
0 0

Re: [xwiki-devs] [xwiki-notifications] r14455 - in xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors: . contentassist contentassist/strategies scanners scanners/rules utils

by Sergiu Dumitriu

fmancinelli (SVN) wrote: > Author: fmancinelli > Date: 2008-11-26 13:28:10 +0100 (Wed, 26 Nov 2008) > New Revision: 14455 > > Modified: > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/Constants.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/Preferences.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/XWikiEditorActionContributor.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/XWikiSourceViewerConfiguration.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/contentassist/CompoundContentAssistProcessor.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/contentassist/MacroContentAssistProcessor.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/contentassist/VelocityVariableContentAssistProcessor.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/contentassist/XWikiHeadingContentAssistProcessor.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/contentassist/XWikiLinkContentAssistProcessor.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/contentassist/XWikiStyleContentAssistProcessor.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/contentassist/strategies/TableAutoEditStrategy.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/contentassist/strategies/VelocityAutoEditStrategy.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/contentassist/strategies/XWikiMarkupAutoEditStrategy.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/scanners/VelocityScanner.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/scanners/XWikiMarkupScanner.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/scanners/XWikiPartitionScanner.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/scanners/rules/BalancedParenthesisRule.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/scanners/rules/RegExRule.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/utils/CharacterScannerCharSequence.java > xeclipse/trunk/plugins/org.xwiki.eclipse.ui/src/main/java/org/xwiki/eclipse/ui/editors/utils/XWikiApiTemplateManager.java > Log: > Cleanup. Removed all @author tags from source code in order to comply with XWiki code guidelines. You should add @version $Id$. -- Sergiu Dumitriu http://purl.org/net/sergiu/

16 years, 10 months

1
0
0 0

[xwiki-devs] [VOTE] Postpone 1.7 branches creation after XE 1.7 release

by Jean-Vincent Drean

Hi, XE 1.7 RC1 is to be released this afternoon and we had planned to create 1.7 branches after it. While most (all?) of us will be working on stabilizing XE 1.7 in the coming week I suggest to postpone the 1.7 branches creation after XE 1.7 release (dec 3rd). Here's my +1. I plan to start the release at 13:30 UTC. Release plan : xwiki-configuration-resources 1.19 xwiki-core 1.7-rc-1 xwiki-plugin-skinx 1.4 xwiki-platform-web 1.7-rc-1 xwiki-product-enterprise 1.7-rc-1 Thanks, JV.

16 years, 10 months

7
6
0 0

[xwiki-devs] [ANN] XWiki Enterprise 1.7 Release Candidate 1 Released

by Jean-Vincent Drean

The XWiki development team is pleased to announce the release of XWiki Enterprise 1.7 RC 1. Go grab it at http://www.xwiki.org/xwiki/bin/view/Main/Download This is the first release candidate for the 1.7 version. Changes from 1.7M3: * Link feature implemented in the new WYSIWYG editor (link to wiki page, web page, email). * Work in progress on the new experimental WYSIWYG editor. * Work in progress on the new XWiki Syntax v2.0 * Reorganized, documented and enhanced xwiki.cfg configuration file Important bug fixes: * XWIKI-2873 : Wrong user name is inserted in group during LDAP membership synchronisation Note that general goals for XWiki Enterprise 1.7 are: * Working and usable (i.e. users can use them for their day to day work instead of the old Syntax and old WYSIWYG editor) versions of new rendering and new WYSIWYG editor. * Working JCR (can be used for day to day work instead of Hibernate). * Blog revamping * Webdav integration For more information see the Release notes at: http://www.xwiki.org/xwiki/bin/view/Main/ReleaseNotesXWikiEnterprise17RC1 Thanks -The XWiki dev team

16 years, 10 months

3
2
0 0

Re: [xwiki-devs] [xwiki-users] Office-Importer Test Server.

by Asiri Rathnayake

Hi Vincent, On Wed, Nov 26, 2008 at 1:49 PM, Vincent Massol <vincent(a)massol.net> wrote: > > On Nov 26, 2008, at 4:13 AM, Asiri Rathnayake wrote: > > > Hi Vincent, > > > > On Tue, Nov 25, 2008 at 9:07 PM, Vincent Massol <vincent(a)massol.net> > > wrote: > > > >> Guillaume, > >> > >> I can see some other problems: > >> * title is not correct > > > > > > Did you mean the title content (spellings?) or the font size of the > > title? > > If it's the latter, it's because openoffice server in this case has > > used > > <font size=""></font> for sizing, and this is filtered in the strict > > filtering mode. > > A title should be converted to a title (i.e. using the == syntax in > wiki). > > Wasn't this a real title in the original word doc? It seems not. If the user editing the document was using headings instead of font sizes, this would result in a title. > > > > I'm pretty sure you didn't mean the latter one, if so please explain > > what's > > exactly wrong :) > > > > * lots of empty lines > > > > > > Good point. > > > > If any of you have some free time (which excludes vincent ;)) please > > try > > this : > > > > Open a new text document in openoffice and: > > > > 1. Type one line of text. > > > > 2. Press enter twice and type another line of text. > > > > So you'd have something like : > > > > " Hi, This is the first line > > > > And this is the second line" > > > > 3. Save the document as *html*. > > > > 4. Open the document in firefox and see the result. > > > > The same thing happens when converting documents via openoffice > > server. The > > problem is, for each empty line in a word document, open office uses : > > > > <p style="margin-bottom: 0in"><br/></p> > > What is the effect of "margin-bottom: 0in"? If it removes the new line > then we should check for this and remove the paragraph altogether (for > all filterings IMO). Well it is supposed to, but it doesn't work in either FireFox or IE. But anyway, since it is supposed to mean there is no newline in between, we could remove such paragraphs. But consider the following case : <p style="margin-bottom: 0in; background-color: red;" >Paragraph-1</p> <p>Paragraph-2</p> In this case if we blindly remove the first paragraph, it will loose other styles along with it. So we should only filter such paragraphs in strict/moderate filtering scenarios. In non-restricted mode, we can't do the same. Again, I'm thinking whether this filtering belongs to office-importer or xhtml parser ? WDYT ? > > > > For spacing. And this is obviously not correct. May be I should take > > this to > > openoffice guys ? > > Yes you should but in the meantime we can filter this (only when > margin-bottom is 0). > > > Vincent, if you remember, I tried to replace these empty paragraphs > > with > > <br/> elements. But I didn't mention this to you at that time. > > Yes you didn't mention that there was a CSS with margin-bottom: 0in > which changes everything... Well I saved the best for the end ;) Thanks. - Asiri > > > -Vincent > > > I simply > > didn't like these empty paragraphs ;) > > > > Thanks. > > > > - Asiri > > > > > > > > > >> > >> > >> Thanks > >> -Vincent > >> > >> On Nov 25, 2008, at 4:30 PM, Guillaume Lerouge wrote: > >> > >>> Hi Asiri, > >>> > >>> I tested strict filtering with my usual test document and apparently > >>> something went wrong with links (see the bottom of the page): > >>> http://91.121.237.216/xwiki/bin/view/Main/GuillaumeTestProgrammez > >>> > >>> Apart from this, it looks pretty good. > >>> > >>> Guillaume > >>> > >>> On Tue, Nov 25, 2008 at 4:14 PM, Asiri Rathnayake < > >>> asiri.rathnayake(a)gmail.com> wrote: > >>> > >>>> Hi Devs, Users, > >>>> > >>>> I have uploaded yet another new version of office-importer @ > >>>> http://91.121.237.216/xwiki/bin/view/Import/. > >>>> > >>>> This version utilizes the latest rendering module which has > >>>> improved a lot > >>>> since the last upload. > >>>> > >>>> Also a moderate style filtering option is introduced. > >>>> > >>>> Please try it out and let us know what you think. > >>>> > >>>> Thanks. > >>>> > >>>> - Asiri > _______________________________________________ > users mailing list > users(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/users >

16 years, 10 months

1
0
0 0

[xwiki-devs] Valid XWiki Page Names

by Jonas von Malottki

Hello Devs, is there some Documentation (or a Regex) which Characters are practically allowed in page and space names? I am unable to find this. From the syntax page it is kind of clear that the following ones are not really usable: "." Because of Space Prefix "[]" Link itself "()%" new formatting characters ">" alias of links I was playing around and if you enter some page name like "hello.hello.hello" you'll get a page named "hello" in the Space "hello.hello". If you enter "hello\.hello" it'll just display nothing. (on XWiki 1.7 M2) Maybe XWiki should check if the given page or space name is actually valid, before creating the page? Nice greetings Jonas

16 years, 10 months

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