xwiki-devs August 2008

xwiki-devs@xwiki.org

51 participants
174 discussions

[xwiki-devs] [GSoC][OfficeConverter]have convert2html feature back

by Wang Ning

Hi Vincent & devs, You are busy for 1.6M1 today, so you can handle this email later at your convenience. To provide something can work for gsoc, I take the convert2html feature back with a little change about the filter. So the officeconverter core + officeconvert plugin + office import appliation can do: 1. import office document like doc, xls, ppt, odt, odp, ods to xwiki page in html format. This feature works well in most case. Just try it. It handles the images, the slides in ppt odp. 2. import office documents to xwiki page in xwiki syntax 2.0 format. This feature is relative to xhtmlparser in new rendering. So it can only work for some case. table, link, image, list are not supported well. I think this can be called some thing works in some extent. -- Thanks Wang Ning

16 years, 3 months

[xwiki-devs] [Proposal] XE 1.6 Roadmap/Dates

by Vincent Massol

Hi, We're a bit late on the planning/roadmap so here's a first try. * 1.6M1: 18 Aug * 1.6M2: 8 Sep * 1.6RC1: 15 sep * 1.6RC2 or 1.6 final: 22 sep Tentative Roadmap for XE 1.6: Must have: ======== * Beta versions of new rendering + new WYSIWYG editor (Vincent & Marius) * One of the following two: ** Revamped Blog UI + features (who?) ** Easy creating of structured pages (JV) * Security issues already in JIRA (marked as high priority) + bug fixes or course Good to have ========== * Office import maybe but I think that should be optional depending on how fast it progresses. It could be released as a separate plugin for sure. * Single sign on w/ openID * French XE * Send forgotten password * Improved RSS feeds * Excel plugin * Installation wizard * Skin extension/Interface extension finalization * CSS + templates cleanup/simplification * Invitation manager in XE My personal take is that the core development team should really focus on the "Must Have" and continue consolidating what we have by working on make it more stable, nicer looking and more usable, rather than working on new features. Of course we have all those nice SOC projects (office import, sso) that we should release/integrate if they are ready at the end of the milestone 2 of XE 1.6. WDYT? Thanks -Vincent

16 years, 3 months

[xwiki-devs] Siteminder Integration

by sharanabasavaraj.x.mudgal＠jpmchase.com

Hi! I am looking for some information on the supportablitlty of Xwiki with SSO for authentication. At this stage, I am exploring the options on how to set this configuration up. There is not much documentation available on the Xwiki site on information for integrating with SSO siteminder though a reference to siteminder is available on the site( http://platform.xwiki.org/xwiki/bin/view/AdminGuide/Authentication check under Custom Aunthentication). I was wondering if any of you could direct me towards more resources/documentation... Thanks. Sharan. ----------------------------------------- This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase & Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase & Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to UK legal entities.

16 years, 3 months

[xwiki-devs] [Proposal] New Configuration design

by Vincent Massol

Hi, Here's a proposal for implementing configuration in the new architecture, using components. Note: I think this is compatible with Sergiu's proposal here: http://tinyurl.com/6md5jd General requirements ================= * Each module/component can define its own configuration * Accessing configuration parameters from Java should be strongly typed (ie. getLinkLabelFormat() for getting the link label and not getParameter("linklabelformat")) * It should be possible to load Configuration data from different sources (properties file, xml files, database, xwiki documents, etc) * Configuration sources should have an order * Any module/component should be able to get the configuration for other module/component but in read only mode * It should be possible to dynamically add a new configuration source at runtime * Configuration data should be loaded and cached Proposed Implementation ==================== * Each module/component defines its configuration in a component which is a java beans. For example let's take the rendering module. We would have a RenderingConfiguration component as in: public interface RenderingConfiguration { String getLinkLabelFormat(); } public class DefaultRenderingConfiguration implements Initializable, Reloadable, RenderingConfiguration (in practice will extend AbstractConfiguration class probably) { private String linkLabelFormat; // Injected private ConfigurationManager manager; public void initialize() { // Define the Configuration sources here. Default configuration sources would be defined in AbstractConfiguration probably) List configurationSources = .... // Configuration namespace (all properties should start with the namespace value) String namespace = "rendering"; reload(); } // Should be located in AbstractConfiguration public void addConfigurationSource(ConfigurationSource source); public void reload() { // Populate java bean manager.populate(this, configurationSources, namespace); } public void setLinkLabelFormat(String linkLabelFormat) {...} public String getLinkLabelFormat() {...} } * The DefaultRenderingConfiguration class is registered as a component in components.xml and with a singleton lifecycle. This means the data it contains are cached for the whole application lifetime. They can be reloaded using reload(). * The ConfigurationManager implementation will use Jakarta BeanUtils to automatically populate a javabeans. It'll also use Jakarta Commons Configuration for implementations of ConfigurationSource. * ConfigurationSource interface should have a method like: Object getParameter(String name). More details to be defined later. * Code wanting to get Rendering Configuration would simply define a component dependency on DefaultRenderingConfiguration and they'll have it injected for them. * There'll be a XWikiDocumentConfigurationSource that gets parameter values from one or several xwiki documents. We'll need to define how we get them but we could provide some standard XWikiConfigurationClass for a single configuration element for example. * The idea of the namespace is to use the package name and remove the "org.xwiki" or "com.xpn.xwiki" prefix. For example "org.xwiki.rendering.*" leads to "rendering.*". WDYT? If we agree I can whip up a first implementation of this relatively quickly I think. Thanks -Vincent

16 years, 3 months

[xwiki-devs] XWiki - Delete All The Users.

by Prathap Pandian

Hi, How can i delete all the users from xwiki except XWiki.Admin. Like (Create Dummy Users Snippet). -- Prathap

16 years, 3 months

[xwiki-devs] best way to integrate a neighbour webapp

by Paul Libbrecht

Hello XWiki fellows, in order to customize Curriki for our needs, I need to some functionaiity. I need some GUI modifications, some of which can be done in GWT, some of which have to happen on the server, within velocity or java to call to a lucene-based tool. This tool is already as a webapp, aside of /xwiki, as /SearchI2G What would be the best way to make such a call? - make curriki's java server code depend on SearchI2G's or make a macro. In both cases, most webapp's jars need to be shared which I don't like too much - make a web-call (such as json RPC call), that's the loosest integration - make something else that would use some sort of naming interface (pointers welcome). what do you think? paul

16 years, 3 months

[xwiki-devs] Tutorial to write validations and tooltips in forms

by Ludovic Dubost

Hi developers, I've written a tutorial to help write validation and tooltips in forms. It's available here: http://platform.xwiki.org/xwiki/bin/view/DevGuide/Creating+a+form+with+vali… Some features are enabled only with the following patch: http://jira.xwiki.org/jira/browse/XWIKI-2386 Reviews of the patch are welcome for inclusion in the XWiki Core. Ludovic -- Ludovic Dubost Blog: http://blog.ludovic.org/ XWiki: http://www.xwiki.com Skype: ldubost GTalk: ldubost

16 years, 3 months

[xwiki-devs] toucan skin style in trunk

by Pascal Voitot

Hello, I have compiled XE from trunk... (NOT UNDER Eclipse3.4, it can't work :)) I see some rendering differences using Toucan skin... apparently Headings renderer has changed! For example: 1.1 chboing before(version 1.5) was rendered as: <h3 class="heading-1-1><span>chboing</span></h3> but now as: <h2><span>chboing</span></h2> So some style has disappeared and under FF3, paragraph begins just under header without any margin and edit section is not more aligned with paragraph but stands on a line between header and paragraph... I can change it by myself but this is a "standard" skin so I prefer asking. Is it normal or is it a side-effect of recent modifications? regards Pascal

16 years, 3 months

[xwiki-devs] Dependencies in skins

by adoro

Hello devs, it was a good idea to separate templates and skins, but skins are still not completely self-contained – e.g. toucan uses .js files from the albatross skin. (fullscreenEdit.js, userandgroups.js etc). It would be great fo fix it, so xwiki-users could use only one skin as prototype to create their own skins. Thanks, Alla -- View this message in context: http://n2.nabble.com/Dependencies-in-skins-tp781062p781062.html Sent from the XWiki- Dev mailing list archive at Nabble.com.

16 years, 3 months

[xwiki-devs] [VOTE] Monospace, superscript and subscript in XWiki Syntax 2.0

by Vincent Massol

Hi, I'd like to propose the following syntaxes: * Monospace: ##monospace## * Subscript: ,,subscript,, * Superscript: ^^superscript^^ This is the same syntax as creole and several other wikis: * http://www.wikicreole.org/wiki/CreoleAdditions * http://www.wikimatrix.org/syntax.php?i=26 * http://www.wikimatrix.org/syntax.php?i=28 * http://www.wikimatrix.org/syntax.php?i=29 Note: We need a syntax since otherwise users will have to write: * Mono: {{html}}<tt> monospace</tt>{{/html}} * Superscript: {{html}}<sup>superscript</sup>{{/html}} * Subscript: {{html}<sub>subscript</sub>{{/html}} ... which is hardly convenient... Here's my +1 Thanks -Vincent

16 years, 3 months

← Newer
1
2
3
4
5
6
7
8
9
...
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs August 2008