xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] Need tempresource support to integrate office-preview

by Asiri Rathnayake

Hello Devs, I've been looking at integrating office-preview module into our main source but I'm really not happy with how presentation preview support is currently implemented, its a load of hacks (btw, its myself who coded it that way). When a presentation office document is imported, it generates a bunch of html files (slides) and a set of images. I need a way to group these artifacts into a single temporary directory and link from the wiki page into the main slice (html page). This is not … [View More]

14 years, 9 months

[xwiki-devs] Programmatically Login

by Luiz Marcelo Serique

Hi, I'm new on list, and new on xwiki too, we have successfully deployed the XWiki Enterprise 2.3 in our company, but there is some pre requisites that we must accomplish to integrate the system to our SSO aplication. The SSO is a very simple aplication that stores all users and groups on a independent database, the SSO system have a interface that shows, like a catalog, all the internal systems that a specific person (logged in person) has access. The archictecture is very simple, and almost … [View More]

14 years, 9 months

Re: [xwiki-devs] [xwiki-notifications] r28950 - platform/web/branches/xwiki-web-2.3/standard/src/main/webapp/resources/js/xwiki/table

by Vincent Massol

On May 20, 2010, at 7:15 PM, dgervalle (SVN) wrote: > Author: dgervalle > Date: 2010-05-20 19:15:53 +0200 (Thu, 20 May 2010) > New Revision: 28950 > > Modified: > platform/web/branches/xwiki-web-2.3/standard/src/main/webapp/resources/js/xwiki/table/livetable.js > Log: > XWIKI-5212 - Livetable filter serialization does not properly support multi-valued form elements > Merge from trunk r28947 Do we have a test for this? How do we unit-test UI components? Thanks -… [View More]Vincent > Modified: platform/web/branches/xwiki-web-2.3/standard/src/main/webapp/resources/js/xwiki/table/livetable.js > =================================================================== > --- platform/web/branches/xwiki-web-2.3/standard/src/main/webapp/resources/js/xwiki/table/livetable.js 2010-05-20 17:11:02 UTC (rev 28949) > +++ platform/web/branches/xwiki-web-2.3/standard/src/main/webapp/resources/js/xwiki/table/livetable.js 2010-05-20 17:15:53 UTC (rev 28950) > @@ -609,11 +609,12 @@ > for (var i = 0; i < this.inputs.length; ++i) { > var key = this.inputs[i].name; > if ((this.inputs[i].type == "radio") || (this.inputs[i].type == "checkbox")) { > - if (this.filters[key]) { > - if (this.filters[key] == this.inputs[i].value.strip()) { > - this.inputs[i].checked = true; > + var filter = this.filters[key]; > + if (filter) { > + if (Object.isArray(filter)) { > + this.inputs[i].checked = (filter.indexOf(this.inputs[i].value.strip()) != -1); > } else { > - this.inputs[i].checked = false; > + this.inputs[i].checked = (filter == this.inputs[i].value.strip()); > } > } > } else { > @@ -624,14 +625,14 @@ > } > > for (var i = 0; i < this.selects.length; ++i) { > - if (!this.filters[this.selects[i].name]) { > - continue; > - } > - for (var j = 0; j < this.selects[i].options.length; ++j) { > - if (this.selects[i].options[j].value == this.filters[this.selects[i].name]) { > - this.selects[i].options[j].selected = true; > - } else { > - this.selects[i].options[j].selected = false; > + var filter = this.filters[this.selects[i].name]; > + if (filter) { > + for (var j = 0; j < this.selects[i].options.length; ++j) { > + if (Object.isArray(filter)) { > + this.selects[i].options[j].selected = (filter.indexOf(this.selects[i].options[j].value) != -1); > + } else { > + this.selects[i].options[j].selected = (this.selects[i].options[j].value == filter); > + } > } > } > } > @@ -649,7 +650,7 @@ > // Ignore filters with blank value > if (!filters[i].value.blank()) { > if ((filters[i].type != "radio" && filters[i].type != "checkbox") || filters[i].checked) { > - result += ("&" + filters[i].name + "=" + encodeURIComponent(filters[i].value)); > + result += ("&" + filters[i].serialize()); > } > } > } [View Less]

14 years, 9 months

[xwiki-devs] New search admin UI and icon

by Thomas Mortagne

Hi devs, I committed the new search admin UI and fixed some issuse, should work well now. Some notes: * the actual configuration is put in a document automatically created if it does not exist so that you can upgrade the whole app without having to worry about what you will overwrite * it's using Configurable system but just to be "injected" as admin app, would be nice to be able to have some reusable code when you need custom UI but still we some standard configuration style in the middle of … [View More]

14 years, 9 months

Re: [xwiki-devs] [xwiki-notifications] r28950 - platform/web/branches/xwiki-web-2.3/standard/src/main/webapp/resources/js/xwiki/table

by Jerome Velociter

----- "Denis Gervalle" <dgl(a)softec.lu> wrote: > On Thu, May 20, 2010 at 19:23, Vincent Massol <vincent(a)massol.net> > wrote: > > > > > On May 20, 2010, at 7:15 PM, dgervalle (SVN) wrote: > > > > > Author: dgervalle > > > Date: 2010-05-20 19:15:53 +0200 (Thu, 20 May 2010) > > > New Revision: 28950 > > > > > > Modified: > > > > > > platform/web/branches/xwiki-web-2.3/standard/src/main/webapp/… [View More]resources/js/xwiki/table/livetable.js > > > Log: > > > XWIKI-5212 - Livetable filter serialization does not properly > support > > multi-valued form elements > > > Merge from trunk r28947 > > > > Do we have a test for this? How do we unit-test UI components? > > > > This would be nice to have. Building proper tests is not so easy, this > could > be very long to setup, since you need to test in several browsers and > you > need full AJAX interaction. That's basically what we do with Selenium, except that we test the integration of the features in the wiki, not the atomic behaviors of the components. There isn't really an alternative to launching a browser for testing our JS components, since most if not all of them heavily rely on a DOM, so just a JS runtime will not be enough. We could envisage a JS unit-testing system like this : - Write tests in .js files, using JSUnit or any other unit testing JS framework (http://ejohn.org/blog/which-unit-testing-framework/) - Slurp the tests in a XAR using a maven plugin - Execute the tests inside XE, using Selenium wdyt ? Jerome. > I am not used to such automated testing, > but I > am not sure the investment is worse the improvement we could get from > them. > > On the other side, I use livetables JS heavily, so you could be > assured that > my fixes/improvements are either well tested or will be fixed ASAP > since all > changes I introduce is already in production. We also usually test > them on > all supported browsers, and at least on IE6/7/8, FF3 (Win/Mac), > Safari4 > (Mac) and Chrome (Mac) > FYI, I found this one when we have introduced the usage of hashes to > provide > "Back to the list" links. I will soon commit an improvement supporting > the > page size in hash as well, so you can really get very precise "back to > the > list" return links. > > Denis > > Thanks > > -Vincent > > > > > -- > Denis Gervalle > SOFTEC sa - CEO > eGuilde sarl - CTO > _______________________________________________ > devs mailing list > devs(a)xwiki.org > http://lists.xwiki.org/mailman/listinfo/devs [View Less]

14 years, 9 months

[xwiki-devs] 答复: Embed xwiki to existing project

by 靳雄飞

XWiki support XMP-RPC and REST, So I am wondering if one can integrate third-party-app with XWiki through XML-RPC. That is, use XWiki as a page store/search/versioning platform, and third-party-app response for page editing and display. If there's a easy way to embed XWiki's editor and render engine into my application, the integration work will be very easy I think. I'm not sure if this can be achieved, I am studying. > >Hi... Good to know there are people with common interest in … [View More]

14 years, 9 months

[xwiki-devs] Extension Manager - First Objective

by Vincent Massol

Hi devs, Just to keep you abreast, Thomas and I are working on the following use case POC fpr midle of next week (hopefully): - Ability to install the JRuby macro from our XWiki Remote repo in a running XE (note that installing this macro is interesting since it has dependencies on another artifact (jruby)). For this we'll develop: - A xwiki-extension-manager module (in sandbox for now). The code will use Maven classes underneath to download the jruby macro + its dependencies to a local repo -… [View More]

14 years, 9 months

[xwiki-devs] [Discussion] OSGi POC result and base for the Extension Manager

by Vincent Massol

Hi devs, I've explored enough of OSGi to get a handle of how it works and what it would mean to use it for XWiki as the basis for our Extension Manager (Thomas helped me with this too). The executive summary is that I don't think we need to use OSGi right now for the Extension Manager and we can defer its usage for later. Let me start by listing what would OSGi bring for XWiki: 1) Known framework with good documentation, books, etc 2) Users would be able to write extensions using OSGi … [View More]programming model (without using XWiki's programming model), this also means the ability to reuse OSGi bundles inside XWiki 3) ClassLoader isolation and thus ability to have several versions of classes 4) OBR (Bundle Repository) for downloading and installing remote jars Now here are the problems found with OSGi so far: A) Impedance mismatch with the webapp/WAR model (classloader and visibility issues). Two examples: - it would mean having a special directory somewhere, where to put the bundles, and this means not going through the standard WAR deployment process. - if we want to keep WEB-INF/lib in order to have a standard WAR deployment then it would mean keeping for ex the core jars in WEB-INF/lib and using OSGi only for extensions. However doing this is not really possible since it would mean extension (OSGi bundles) would have Imports on core classes but this won't work since core classes won't be OSGi bundles B) In practice it's very hard to use OSGi with only a part of the modules being OSGi bundles and another part being standard external libraries. Everything must be OSGified for it to work well. In addition we might want not need the features listed above: 1) Not really needed especially since we have the XWiki programming model that we don't want to loose right now 2) is a nice to have but not a requirement for the Extension Manager 3) in practice it's going to be very hard to support multiple versions of classes. Imagine for example an application A which is providing a macro in a wiki page. Application B requires version 1.0 of A and application C requires version 2.0 of A. How do we support that? OSGi won't help here since this is about wiki pages. It's only helping for jars. The jar isolation could also easily be implemented using a custom URL classloader without too much problem IMO, but I'm inclined to say that we don't need to support multiple versions in a first version of the Extension Manager. 4) We can easily use the Maven 3 Embedder to download and install maven artifacts into a local repository. This is convenient since we already deploy our applications/modules to a maven repository. Note that the only "difficult" part here might be searching into a remote repository; I don't know if a maven api exists for this (but probably). In the worst of cases we could use the Nexus REST API to provide this feature for now. And here's what I think we should do right now: i) focus on the 2 features we need for the Extension Manager: -- ability to install an application containing not only wiki pages but also jars -- ability to install an application from a remote repository ii) then once i) is done focus on the upgrade part of the extension manager Implementation note: - To implement i) we can do this easily I believe using a custom URL ClassLoader (we already have one btw used in the script macro) that we pass to the Component Annotation Loader when a new JAR is installed (in order to register the components in that jar) + set that custom URL ClassLoader as the new thread context classloader (for code that would use the thread context classloader to load classes). WDYT? Thanks -Vincent PS: I'd be interested to hear from OSGi experts what they have to say about this since I'm an OSGi newbie and there might be stuff I have not seen/realized. PPS: I'm just realizing that the proposal in this mail is close to Pomegranate's idea: http://www.caucho.com/projects/pomegranate/ [View Less]

14 years, 9 months

[xwiki-devs] YourKit Java Profiler 9.0 Released

by Vincent Massol

See http://bit.ly/b1iPgf Note that all xwiki committers have a Yourkit license key available to them on dev.xwiki.org (tools page). Thanks -Vincent

14 years, 9 months

[xwiki-devs] Fwd: [ANNOUNCE] Apache VelocityTools 2.0 release

by Vincent Massol

Possible candidate for upgrade in XWiki too. Thanks -Vincent Begin forwarded message: > From: Nathan Bubna <nbubna(a)apache.org> > Date: May 19, 2010 2:56:21 AM GMT+02:00 > To: Velocity Users List <user(a)velocity.apache.org>, Velocity Developers List <dev(a)velocity.apache.org>, private <private(a)velocity.apache.org>, announce(a)apache.org > Subject: [ANNOUNCE] Apache VelocityTools 2.0 release > > The Apache Velocity project is pleased to announce … [View More]the release of > VelocityTools 2.0. > > Downloads are available here: > http://velocity.apache.org/download.cgi > > This should be useable as a drop in replacement for Tools 2.0-beta4 or > Tools 1.4, with a few minor exceptions. The 2.x series of > VelocityTools requires Velocity 1.5+ and JDK 1.5+. > > For those new to Tools 2, here's an overview of the work done since 1.4: > * More convention over configuration and smart defaults > * New configuration formats (more concise/flexible/powerful xml, > properties, java) > * Provision of default and auto-loaded configurations > * Entirely new core infrastructure (lazy-loading tools, easier > access, standalone support etc) > * Added VelocityViewTag for JSP integration > * Added DisplayTool, ConversionTool, ClassTool, LoopTool, > FieldTool, a generic version of LinkTool and more > * Refactored and enhanced a number of existing tools > * Improved documentation > * Deprecated many outdated things > * Legacy support for almost all Tools 1.4 configurations and extensions > * Better integration of $application, $session and $request scope > control objects > * and lots more... > > For those following the betas, here's the notable changes since 2.0-beta4: > * Added a 'readOnly' config option to allow write operations on > ValueParser and ParameterTool (when set to false) > * Added a beta-quality UiDependencyTool (included in > velocity-view, but not in default tools.xml) > * Added an alpha-quality MarkupTool (included in generic tools, > but not in default tools.xml) > * Fixed (as much as possible) some significant last-iteration > LoopTool problems, and added a $loop.this property to serve as a more > reliable workaround in nested loops. See > https://issues.apache.org/jira/browse/VELTOOLS-124 > * VelocityLayoutServlet now checks request attributes for > non-default layouts. > * The velocity-view.tld is now valid. > * VelocityView[Servlet] has improved exception and http management > (particularly for ResourceNotFoundExceptions). > * Miscellaneous documentation and build.xml improvements > > The Velocity developers are very interested in all feedback regarding > Tools 2.0, especially regarding backwards compatibility with apps > designed for Tools 1.4 or earlier. We aim to enable a smooth, > incremental transition for developers and their applications. [View Less]

14 years, 9 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