xwiki-devs

xwiki-devs@xwiki.org

9400 discussions

[xwiki-devs] [GSOC 2009] XWiki Cross Platform Web and Desktop Widget

by Alexandru Cismaru

Hi. I'm Alexandru Cismaru (MSc student in Iasi) , last year I was a GSOC student at XWiki, with the RESTful API project. This year I'm interested again in another project, *XWiki Cross Platform Web and Desktop Widget*. I have done some research and talked with Ludovic, Sergiu and Guillaume on the IRC, so this is what I came out so far: http://dev.xwiki.org/xwiki/bin/view/Design/XWikiWidgetandFirefoxextension . Please give me your feedback and ideas. Thank you, Alexandru Cismaru

16 years, 3 months

[xwiki-devs] Fwd: [ANN] Maven Release Plugin 2.0-beta-9 Released

by Vincent Massol

fyi, especially the part: * [MRELEASE-375] - release plugin does not work with subversion > 1.5.0 -Vincent Begin forwarded message: > From: Olivier Lamy <olamy(a)apache.org> > Date: March 28, 2009 6:36:36 PM CEST > To: announce(a)maven.apache.org, Maven Users List <users(a)maven.apache.org > > > Cc: Maven Developers List <dev(a)maven.apache.org> > Subject: [ANN] Maven Release Plugin 2.0-beta-9 Released > Reply-To: "Maven Developers List" <dev(a)maven.apache.org> > > Hi, > The Maven team is pleased to announce the release of the Maven Release > Plugin, version 2.0-beta-9. > > http://maven.apache.org/plugins/maven-release-plugin/ > > You should specify the version in your project's plugin configuration: > > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-release-plugin</artifactId> > <version>2.0-beta-9</version> > </plugin> > > > Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-9 > > > ** Bug > * [MRELEASE-273] - Regression: NullPointerException at end of > standalone "release:perform" > * [MRELEASE-375] - release plugin does not work with subversion > > 1.5.0 > * [MRELEASE-379] - return results after performing a release > * [MRELEASE-381] - url syntax not good enough for the git scm > provider > * [MRELEASE-386] - Sneaky bug in DefaultReleaseManager.perform() > * [MRELEASE-393] - NoSuchMethodError when using > InvokerMavenExecutor with cmd line arg "--quiet" > * [MRELEASE-405] - Wrong branch-name parameter > > ** Improvement > * [MRELEASE-385] - Upgrade to last scm version (1.2) > * [MRELEASE-392] - Align release-parent, release-manager and > release-plugin versions > * [MRELEASE-427] - Add a mojo parameter for using the new remote > tagging for svn scm provider (to prevent issue with svn > 1.5.0) > * [MRELEASE-429] - Support for a [token]-SNAPSHOT in addition to > [number]-SNAPSHOT > > > ** Task > * [MRELEASE-390] - Add VSS dependency > > Have Fun! > > -- > The Maven Team

16 years, 3 months

[xwiki-devs] Google gadgets / Google docs integration / Calender Application

by Arosh Perera

Hi, I'm Arosh. In last few days I go through the Google API and find out the component features and the data model of it. I think this should be the correct project to me for this summer.Because I am a Sun Certified Java Programmer and four to five years experience with Java. Also I have the experience of working with several APIs.In last 6 months I working with mobile APIs like Android and Brew, WAP frameworks like mymobileweb and netbiscuits and also JSF ect. So before I further researching on these projects I think it is very much important to have a strong understanding about XWiki data model.I would like to know what are the relevant steps should I take to make my interest a reality. Further I would like to know what are the weakness that was there in old calender specifically. -- regards Arosh Thilanka Perera Dpt of Computer Science & Engineering University of Moratuwa Sri Lanka.

16 years, 3 months

[xwiki-devs] GSoC : Proposal submitted

by apurv gupta

Hi Dear, After a full day of brain storming, I finally submitted my proposal for Calendar application. Please have a look on my proposal and let me know how can I improve it. Thanks for your consideration. regards, -- Apurv Gupta Indian School of Mines University

16 years, 3 months

[xwiki-devs] [GSoC] pubsub idea as modyfication one from list.

by Jan J. Roman

Hi all. I would like to participate GSoC and work by XWiki. I am interested in idea "XWiki Jabber, Google Talk, Skype Integration". Main aim of described idea is to use some kind of chat rooms. Those chat rooms should be used for discuss editions and log this discussions to wiki(please correct me if I am wrong). What I propose is publish-subscribe mechanism, it is part of XMPP(Jabber/GTalk) standard. It allows to create messages categorized by nodes. When message is add, modify or delete from node there is notification sent to all subscribers (like RSS or ATOM). Main advantage of this solution is that users may use their jabber accounts for subscribe discussion or publish something in it. Here is small comparison: chat logging: * To be at home in subject someone have to read all chat log. pubsub: * You may subscribe only nodes you are interested in and ignore uninteresting. chat logging: * Chat has specific convention, there is a lot of short messages, statements are not well-thought-out, there are a lot of misunderstandings and explanations of it * After logged all chat. It may be necessary to moderate discussion. We have to create special tool for this and someone have to do the work. pubsub: * When people publish some "post" they have more time to think about it. It is possible to modify posted unclear statements. Author can even delete unnecessary own posts (in both situations all subscribers will be notify). Main disadvantage of pubsub is that it will be more difficult to port this for Skype and other closed protocols. But users can always use expected built-in XWiki pubsub client. Plese give me feedback about this idea. Jan J. Roman

16 years, 3 months

[xwiki-devs] [GSoC 2009] Additional information for JSR-168 proposal

by Karel Piwko

Hello, I'm master student in informatics. I would like to apply for JSR-168 full compatibility proposal in this year's GSoC for XWiki. There's a list of my experience concerning this application: - Java (mainly databases and web portals - JTA, JPA, JDBC, JBoss, Apache Tomcat and Jetty) - 2 years of continuous work at portal www.abclinuxu.cz - project design - (re)implementation of CSS 2.1 parser concerning easy update as specification of CSS evolves http://cssbox.sourceforge.net/jstyleparser/ - team implementation of XML database on scratch with client-server SSL access with JSP frontend sample application, abstract availablee at http://www.esiee.fr/~bureaud/Unites/Pr302i/0607/i307et05.pdf - ability to connect different pieces of code and/or software flawlessly - bachelor thesis, comparison of Wikipedia portals based on Apache Coocon with XML database exist and Stripes with 'Wicket' like extension and PostgreSQL I would like have more information what I will be supposed to do. For example, it would be great if code is done with concerning JSR-286 forward compatibility. Thank in advance for response Karel Piwko

16 years, 3 months

[xwiki-devs] GSOC 2009 project idea "Survey Application" functional view of the survey application

by Chathura Prabuddha

Hai Ludovic,Serigue and Other GSOC ppl I had upload the functional view of the survey. Click here <http://www.xwiki.org/xwiki/bin/view/XWiki/ChathuraPrabuddha>to view it. Plan to add the architecture diagram in next fix few days. Hope that this will be helpfull to other gsoccers too.. Mean while I had uploaded my application to the gsoc site. Also I mailled the pdf it to Asiri and Ludovic. So dear mentors please send me your kind feedback about my application. good luck

16 years, 3 months

[xwiki-devs] [GSoC2009] Google Gadget and OpenSocial Integration

by Anamaria Stoica

Hi, I need some help locating the code for Google Gadgets ( http://incubator.myxwiki.org/xwiki/bin/view/Gadgets/). I don't see it in platform/xwiki-applications or platform/xwiki-plugins (in http://svn.xwiki.org/svnroot/xwiki/). Also what is it : an application, plugin, component ? (combination of them?) Is it implemented as a container that supports the original gadgets API. How about the Open Social API ? (as the project specifies, they should both be implemented) I think it would be nice to allow users to add gadgets/open social gadgets to the sidebar as well, not only on the Dashboard page. What do you think ? Thanks, Anamaria

16 years, 3 months

[xwiki-devs] [VOTE] Use annotations for new code and slowly refactor old code to use them

by Vincent Massol

Hi, I've finished the annotation implementation for registering components. The rendering modules have been migrated to annotations fully so I believe it's now strong enough to be used globally in XWiki. I'd like to propose that we use annotations for all new code from now on and slowly refactor existing code to use them. Here's my +1 Thanks -Vincent

16 years, 3 months

[xwiki-devs] [Proposal] Best practice for component configuration

by Vincent Massol

Hi, So far we've been using plexus configuration mechanism in components.xml to define component configuration data. I'm proposing to drop this. Reasons: 1) This is trying us to plexus and is not generic enough for all IOC frameworks 2) It doesn't easily allow overriding config values (for ex if the user wants to override a value in a wiki page or in xwiki.properties file) I thus propose 3 things: 1) to use our new xwiki configuration mechanism to store component configuration data 2) to have a META-INF/<module prefix>.properties file located in the module jar where <module prefix> is org.xwiki.rendering for example for the rendering module (we could also have a submodule if the module is split into several modules). The idea is that the file name needs to be unique across jars so that we can create uberjars later on if need be. 3) in general we shouldn't have component-specific config data and instead make the data as generic config data as much as possible and bound to the module's Configuration component instead. For 1) and 2), it's very easy to do: - the component which requires config data need to have ConfigurationManager and ConfigurationSources injected and implement the Initializable interface and then call in initialize(): this.configurationManager.initializeConfiguration(this, this.sourceCollection.getConfigurationSources(), <prefix>); - store data using a FQN in META-INF/<module prefix>.properties, for example: org.xwiki.rendering.internal.macro.RealmMacroSource.priority = 10 In this example you would call initializeConfiguration with a prefix value of RealmMacroSource.getClass().getName(). 3) is important because otherwise users will be able to override private config data and if the internal implementation changes the config data won't be valid anymore. The reason for 2) is to hide these config data from the users as much as possible since these are advanced config options that shouldn't normally be used. For example we would defined a default priority for macros but in some very exceptional cases the user would want to change the priority so that the macro executes at a different time for a given reason. Another example if the velocity components which contain lots of data. I believe these data should be moved to a VelocityConfiguration component instead. WDYT? Thanks -Vincent

16 years, 3 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