xwiki-devs June 2012

xwiki-devs@xwiki.org

35 participants
107 discussions

[xwiki-devs] [GSOC][doubt] Solr Search Component

by savitha sundaramurthy

Hi all, While trying to retrieve the search results had the following doubts. *Problem: * * * * *Say XWiki has three languages English, Spanish, French. I give a query in English(some *proper noun*) , should it return the documents pertaining only to english or it can return documents pertaining to other languages too? If the scenario is such that it retrieves the documents irrespective of languages, I have few ideas to deal with it. 1) We can get the documents, merge them, add the scores and give it a high rating. This would help to avoid super results such as a display of a different match in each language to some extent. 2) Make it a part of facet search , where search results could be differentiated base don language. Would be really helpful to gain your suggestions. -- Thanks a lot, Savitha.s

12 years, 2 months

[xwiki-devs] Fwd: [GSoc] XDroid Platform

by sasinda rukshan

---------- Forwarded message ---------- From: sasinda rukshan <sasindarukshan(a)gmail.com> Date: Mon, Jun 18, 2012 at 2:56 PM Subject: Re: [xwiki-devs] [GSoc] XDroid Platform To: XWiki Developers <devs(a)xwiki.org> Hi Thomas, Thanks for the explanations. The methods toXML , toEmbedXML are wrong.It was just an idea that came up without much thinking. I will use a separate model converter.(xwikitTosimpleModelConverter implements ModelConverter like thing). So the model objects don't know about it at all. By what you ment by "user" I think it is the client app developer is it? you did not mean end user. I never reveal the xml representations to end users. I came up with a simpler design. I will post diagram later tomorrow. To give a brief on it, XObject : has protected property List<XProperty> |__XPoperty :<< all objects that can be added as a property of an objects should extend this. Has an attribute list. cancels the | property list of XObject | |_____XString : |__Abstract XDocObject :<< all documents should have an object of this. This is the pages class. Has a object List<XObject> | |____XBlog :<< all documents which are blogs should have a object of this. This determines the class of the object. | but this data is not posted anywhere in <link rel="...../class"> . It is just kept for type checks. That is like | this page should include XBlogPost objects. |__XBlogPost : <<the BlogPostClass object. In my view I assume every page has an object of some class. And this object holds the objects which you can get under .../pages/BlogPg1/objects/ [ an added advantage: I think we can make a ViewEngine to generate android View components from the above model. Since the objects in the page carry rendering descriptions.We can make a general model like a browser to brows xwiki using generated the views. But the problem is some features in specific spaces like blog do not seem to be totally defined by the XWiki Object model behind them. Also this is just an idea (not suggesting I do for the GSoc).Making it a usable reality is a little challenge. ] So as you said if a document (I think it equivalent to a page) can have many class types my assumption fails. Why should a document be of multiple classes. I was thinking a page belongs to a class. And the page is an instance of that class. If page can have multiple classes my understanding should be wrong. Isn't it? Thanks Best Regards Sasinda. > >>>> >>>> > On Wed, May 30, 2012 at 1:11 PM, Thomas Mortagne > >>>> >>>> > <thomas.mortagne(a)xwiki.com>wrote: > >>>> >>>> > > >>>> >>>> >> On Wed, May 30, 2012 at 4:28 AM, sasinda rukshan > >>>> >>>> >> <sasindarukshan(a)gmail.com> wrote: > >>>> >>>> >> > Hi, > >>>> >>>> >> > I am studying ORM Lite these days. > >>>> >>>> >> > Please It would be comforting if you can confirm whether it > is > >>>> worth > >>>> >>>> >> > the > >>>> >>>> >> > overhead to use ORM Lite. > >>>> >>>> >> > > >>>> >>>> >> > >>>> >>>> >> > >>>> > http://logic-explained.blogspot.com/2011/12/using-ormlite-in-android-projec… > >>>> >>>> >> > http://ormlite.com/ > >>>> >>>> >> > ORM Lite features: > >>>> >>>> >> > Automatically Creates standard DAOs for an annotated entity. > >>>> >>>> >> > Coding will be lot easier. > >>>> >>>> >> > >>>> >>>> >> Remember it's a framework for a mobile platform so it has to > >>>> remain > >>>> >>>> >> light and have good performances. I can see that Android > version > >>>> of > >>>> >>>> >> ormlite is very small but I never used it so I don't know if > >>>> it's good > >>>> >>>> >> or not. At least it seems petty active which is a good point > so I > >>>> >>>> >> don't have anything against it. > >>>> >>>> >> > >>>> >>>> >> > > >>>> >>>> >> > Can you suggest how to name the entities. > >>>> >>>> >> > I am going to go with, > >>>> >>>> >> > <entity> org.xwiki.xdroid.data.User --> <table> C_USER > >>>> >>>> >> > >>>> >>>> >> Note that there is already a package name prefix and group id > >>>> defined > >>>> >>>> >> for the framework and it's org.xwiki.android as you can see on > >>>> >>>> >> https://github.com/xwiki-contrib/android-client. Why do you > >>>> want to > >>>> >>>> >> change it ? It's more consistent with > >>>> >>>> >> org.xwiki.commons/org.xwiki.rendering/org.xwiki.platform so I > >>>> would > >>>> >>>> >> prefer to keep it that way unless you can give arguments. The > >>>> goal is > >>>> >>>> >> not to redo something completely but complete and improve the > >>>> existing > >>>> >>>> >> framework. > >>>> >>>> >> > >>>> >>>> >> Also as far as I can see there is already several things > called > >>>> >>>> >> "xdroid" on Google play among which an application developer > >>>> >>>> >> (https://play.google.com/store/apps/developer?id=x-droid) > and an > >>>> >>>> >> application ( > >>>> >>>> >> > >>>> >>>> >> > >>>> > https://play.google.com/store/apps/details?id=com.gurudigitalsolutions.xdro… > >>>> >>>> >> ). > >>>> >>>> >> > >>>> >>>> >> > > >>>> >>>> >> > Thanks, > >>>> >>>> >> > Best Regards > >>>> >>>> >> > > >>>> >>>> >> > Sasinda. > >>>> >>>> >> > > >>>> >>>> >> > > >>>> >>>> >> > > >>>> >>>> >> > > >>>> >>>> >> > > >>>> >>>> >> > On Wed, May 30, 2012 at 7:42 AM, sasinda rukshan > >>>> >>>> >> > <sasindarukshan(a)gmail.com>wrote: > >>>> >>>> >> > > >>>> >>>> >> >> Hi, > >>>> >>>> >> >> > >>>> >>>> >> >> I am commiting my work to my fork > >>>> >>>> >> >> https://github.com/sasinda/android-client. > >>>> >>>> >> >> I ll request to pull it to xwiki-contrib later. > >>>> >>>> >> >> > >>>> >>>> >> >> I was running in a wrong path these days. Wanted to save > login > >>>> >>>> >> >> history > >>>> >>>> >> and > >>>> >>>> >> >> suggest login. I was going to do it using an xml file > (login > >>>> >>>> >> attempts.xml). > >>>> >>>> >> >> Now it seems database is better. > >>>> >>>> >> >> Any way before I go wrong again I will say what I am going > to > >>>> do. > >>>> >>>> >> >> I am going to enforce following conventions.These are not > yet > >>>> >>>> >> >> needed, > >>>> >>>> >> >> considered the small scale.But when the system grows it > would > >>>> be > >>>> >>>> >> >> nice to > >>>> >>>> >> >> have them to avoid confusions. > >>>> >>>> >> >> *Database prefixes for:* > >>>> >>>> >> >> *Platform tables (can begin with appropriate prefix)* > >>>> >>>> >> >> AD_ //application dictionary : don't know when it will be > >>>> needed ;-) > >>>> >>>> >> >> C_ //core functionality > >>>> >>>> >> >> *Client Applications.* > >>>> >>>> >> >> X<App name prefix> ex: XBLOG_ for Blog app// All client > >>>> add in > >>>> >>>> >> modules > >>>> >>>> >> >> must begin with table prefix X(for xwiki and ordering) + > App > >>>> name. > >>>> >>>> >> This is > >>>> >>>> >> >> for my blog. > >>>> >>>> >> >> > >>>> >>>> >> >> I will create > >>>> >>>> >> >> C_User for user data. > >>>> >>>> >> >> C_LoginAttempt for saving login attempts. > >>>> >>>> >> >> > >>>> >>>> >> >> From C_LoginAttempt I can filter uniqe login combinations > and > >>>> give > >>>> >>>> >> >> suggestions in the login UI component. Also save the > history. > >>>> >>>> >> >> > >>>> >>>> >> >> All saved data for blog app will be linked to a perticular > >>>> login : > >>>> >>>> >> >> User, > >>>> >>>> >> >> XWiki server. > >>>> >>>> >> >> But only a single user will be most probably using his > >>>> personal > >>>> >>>> >> >> device. > >>>> >>>> >> So > >>>> >>>> >> >> above will be relevant only when he has multiple wikis. > >>>> >>>> >> >> > >>>> >>>> >> >> Best Regards, > >>>> >>>> >> >> Sasinda Rukshan. > >>>> >>>> >> >> > >>>> >>>> >> >> > >>>> >>>> >> >> > >>>> >>>> >> >> > >>>> >>>> >> >> > >>>> >>>> >> >> On Sun, May 27, 2012 at 5:43 PM, Chamika Weerasinghe < > >>>> >>>> >> chamikaw(a)gmail.com>wrote: > >>>> >>>> >> >> > >>>> >>>> >> >>> On Fri, May 25, 2012 at 1:25 AM, Jerome Velociter < > >>>> >>>> >> jerome(a)winesquare.net > >>>> >>>> >> >>> >wrote: > >>>> >>>> >> >>> > >>>> >>>> >> >>> > On Thu, May 24, 2012 at 6:09 PM, Thomas Mortagne > >>>> >>>> >> >>> > <thomas.mortagne(a)xwiki.com> wrote: > >>>> >>>> >> >>> > > On Thu, May 24, 2012 at 5:52 PM, sasinda rukshan > >>>> >>>> >> >>> > > <sasindarukshan(a)gmail.com> wrote: > >>>> >>>> >> >>> > >> Hi all, > >>>> >>>> >> >>> > >> I am starting this thread for my XWiki Android > Platform > >>>> >>>> >> >>> > >> Project. > >>>> >>>> >> >>> > >> > >>>> >>>> >> >>> > >> Please check whether following are OK. > >>>> >>>> >> >>> > >> [1] INFO > >>>> >>>> >> >>> > >> I tried to start my new modules with the > >>>> >>>> >> >>> de.akquinet.android.archetypes: > >>>> >>>> >> >>> > >> android-quickstart:1.0.8. (added eclipse plugins > m2e, > >>>> >>>> >> >>> > >> m2e-android[a.k.a *Android > >>>> >>>> >> >>> > >> Configurator* ]). But this seems buggy in eclipse. > >>>> >>>> >> >>> > >> Any way the earlier project has not followed the > above > >>>> >>>> >> >>> > >> archtype > >>>> >>>> >> >>> either. > >>>> >>>> >> >>> > So > >>>> >>>> >> >>> > >> I am going to write pom.xml manually for my each > module. > >>>> >>>> >> >>> > >> > >>>> >>>> >> >>> > >> [2] ADVICE NEEDED > >>>> >>>> >> >>> > >> xwiki-rest-model module contains 2 submodules > >>>> >>>> >> >>> > >> |-- xwiki-rest-model-gson ( gson should be > corrected > >>>> to > >>>> >>>> >> >>> > >> json) > >>>> >>>> >> >>> > > > >>>> >>>> >> >>> > > No the g is not a mistake, it's a model to be used > with > >>>> the > >>>> >>>> >> >>> > > gson > >>>> >>>> >> >>> > > library (http://code.google.com/p/google-gson/). See > >>>> >>>> >> >>> > > > >>>> >>>> >> >>> > > >>>> >>>> >> >>> > >>>> >>>> >> > >>>> >>>> >> > >>>> > http://extensions.xwiki.org/xwiki/bin/view/Extension/Google+Android+Client#… > >>>> >>>> >> >>> > . > >>>> >>>> >> >>> > > > >>>> >>>> >> >>> > >> |-- xwiki-rest-model-simplexml > >>>> >>>> >> >>> > >> I think the xwiki-rest-model-gson is redundant. The > >>>> classes > >>>> >>>> >> >>> > >> in xwiki-rest-model-simplexml is added with simple > xml > >>>> >>>> >> annotations, > >>>> >>>> >> >>> > >> otherwise both modules have same classes. There is no > >>>> problem > >>>> >>>> >> >>> > >> with > >>>> >>>> >> >>> the > >>>> >>>> >> >>> > >> added annotations for using the same model objects > for > >>>> Json > >>>> >>>> >> >>> > >> REST > >>>> >>>> >> web > >>>> >>>> >> >>> > >> services. And I intend to add my JPA (ORMLite library > >>>> for > >>>> >>>> >> >>> persistence) > >>>> >>>> >> >>> > >> annotations on top of it. > >>>> >>>> >> >>> > >> Shall I re-factor them to a single module > >>>> xwiki-rest-model. > >>>> >>>> >> >>> > > > >>>> >>>> >> >>> > > No keep them separated, the idea is that both are > useful > >>>> tool > >>>> >>>> >> >>> > > to be > >>>> >>>> >> >>> > > used by someone else that might be moved to > >>>> xwiki-platform at > >>>> >>>> >> >>> > > some > >>>> >>>> >> >>> > > point along with the current xwiki-rest-model (to be > >>>> renamed to > >>>> >>>> >> >>> > > xwiki-rest-model-jaxb). > >>>> >>>> >> >>> > > > >>>> >>>> >> >>> > > Chamika initially started with gson and since XWiki > REST > >>>> JSON > >>>> >>>> >> >>> > > representation had some limitation he moved to XML > >>>> >>>> >> >>> > > representation. > >>>> >>>> >> >>> > > Maybe at some point Android will have native support > for > >>>> jaxb > >>>> >>>> >> >>> > > which > >>>> >>>> >> >>> > > would obviously be the easier for us (embedding jaxb > is > >>>> not an > >>>> >>>> >> option > >>>> >>>> >> >>> > > in mobile world where size it still pretty important > >>>> especially > >>>> >>>> >> >>> > > on > >>>> >>>> >> >>> > > phones). Maybe it's already the case on most recent > >>>> versions > >>>> >>>> >> >>> > > like > >>>> >>>> >> 4.0 > >>>> >>>> >> >>> > > I don't know. > >>>> >>>> >> >>> > > >>>> >>>> >> >>> > There's also Jackson that could be tried for JSON > >>>> >>>> >> >>> > deserialization, if > >>>> >>>> >> >>> > said limitations are actually GSON limitations. > >>>> >>>> >> >>> > > >>>> >>>> >> >>> GSON wasn't the limitation. > >>>> >>>> >> >>> It was XWiki RESTful API which doesn't support JSON in > some > >>>> cases. > >>>> >>>> >> >>> So > >>>> >>>> >> it's > >>>> >>>> >> >>> safe to go with xml. > >>>> >>>> >> >>> > >>>> >>>> >> >>> > > >>>> >>>> >> >>> > Having full JAXB support sound a bit overweight for > such an > >>>> >>>> >> >>> > "embedded > >>>> >>>> >> >>> > API", even if one day it is natively supported by > Android. > >>>> What's > >>>> >>>> >> >>> > important is to have an easy and fast deserialization, > IMO. > >>>> >>>> >> >>> > The only advantage I can see of going JAXB would be in > >>>> re-using > >>>> >>>> >> >>> > the > >>>> >>>> >> >>> > exact representations and body readers/writers from > XWiki > >>>> core. > >>>> >>>> >> >>> > But > >>>> >>>> >> >>> > you probably don't even want to do that since it would > mean > >>>> >>>> >> >>> > dragging > >>>> >>>> >> >>> > XWiki core with you :) > >>>> >>>> >> >>> > > >>>> >>>> >> >>> > Jerome > >>>> >>>> >> >>> > > >>>> >>>> >> >>> > > > >>>> >>>> >> >>> > >> > >>>> >>>> >> >>> > >> [3] INFO > >>>> >>>> >> >>> > >> I had to change some pom.xml s. As the current > project > >>>> at: > >>>> >>>> >> >>> > >> > https://github.com/xwiki-contrib/android-client.gitdoes not > >>>> >>>> >> build. > >>>> >>>> >> >>> > Error > >>>> >>>> >> >>> > >> with parent pom.xml coordinates. > >>>> >>>> >> >>> > > > >>>> >>>> >> >>> > > You probably did not setup you maven install properly > >>>> since > >>>> >>>> >> >>> > > what's > >>>> >>>> >> on > >>>> >>>> >> >>> > > > https://github.com/xwiki-contrib/android-client.gitbuild > >>>> >>>> >> perfectly > >>>> >>>> >> >>> as > >>>> >>>> >> >>> > > you can see on > >>>> >>>> >> http://ci.xwiki.org/view/All/job/xwiki-android-client/ > >>>> >>>> >> >>> > > which run a build every time something changes on the > git > >>>> >>>> >> repository.. > >>>> >>>> >> >>> > > You should look at > >>>> >>>> >> >>> > > > http://dev.xwiki.org/xwiki/bin/view/Community/Building. > >>>> >>>> >> >>> > > > >>>> >>>> >> >>> > >> > >>>> >>>> >> >>> > >> > >>>> >>>> >> >>> > >> Thank you > >>>> >>>> >> >>> > >> Best Regards. > >>>> >>>> >> >>> > >> Sasinda Rukshan > >>>> >>>> >> >>> > >> _______________________________________________ > >>>> >>>> >> >>> > >> 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 > >>>> >>>> >> >>> > > >>>> >>>> >> >>> > > >>>> >>>> >> >>> > > >>>> >>>> >> >>> > -- > >>>> >>>> >> >>> > Jérôme Velociter > >>>> >>>> >> >>> > Winesquare > >>>> >>>> >> >>> > http://www.winesquare.net/ > >>>> >>>> >> >>> > _______________________________________________ > >>>> >>>> >> >>> > devs mailing list > >>>> >>>> >> >>> > devs(a)xwiki.org > >>>> >>>> >> >>> > http://lists.xwiki.org/mailman/listinfo/devs > >>>> >>>> >> >>> > > >>>> >>>> >> >>> _______________________________________________ > >>>> >>>> >> >>> devs mailing list > >>>> >>>> >> >>> devs(a)xwiki.org > >>>> >>>> >> >>> http://lists.xwiki.org/mailman/listinfo/devs > >>>> >>>> >> >>> > >>>> >>>> >> >> > >>>> >>>> >> >> > >>>> >>>> >> > _______________________________________________ > >>>> >>>> >> > 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 > >>>> >>>> >> > >>>> >>>> > _______________________________________________ > >>>> >>>> > devs mailing list > >>>> >>>> > devs(a)xwiki.org > >>>> >>>> > http://lists.xwiki.org/mailman/listinfo/devs > >>>> >>>> > >>>> >>>> > >>>> >>>> > >>>> >>>> -- > >>>> >>>> Thomas Mortagne > >>>> >>> > >>>> >>> > >>>> >> > >>>> >> > >>>> >> > >>>> >> -- > >>>> >> Thomas Mortagne > >>>> > > >>>> > > >>>> > > >>>> > -- > >>>> > Thomas Mortagne > >>>> > >>>> > >>>> > >>>> -- > >>>> Thomas Mortagne > >>>> > >>> > >>> > >> > > _______________________________________________ > > devs mailing list > > devs(a)xwiki.org > > http://lists.xwiki.org/mailman/listinfo/devs > > > > -- > Thomas Mortagne >

12 years, 2 months

[xwiki-devs] [Idea] Bundle jQuery ?

by Jerome Velociter

Hi devs, Now that all the scripts on the Internets are implemented as jQuery plugins, should we bite the bullet and make it easier for extensions developers to integrate such scripts ? Note it would not necessarily mean we use it ourselves in web/XE. If we don't do something about it, there is the risk that many extensions bring their own jQuery to the party, which will translate in slower page loads and more importantly a less enjoyable extension developer experience. An alternative idea would be an "official" jQuery extension (with a JSX) that other extensions can depend upon, should they need jQuery. What do you think ? Jerome

12 years, 2 months

Re: [xwiki-devs] [GSoC] Responsive Skin

by Jonathan Solichin

Hello friends, > The root application >> wikis >> spaces in a wiki >> Pages in a space. > If you reveal that in the menu users get the intuitive feeling that they > can create a wiki also. And in a wiki they can have spaces and etc... > Well the first time I used XWiki my intuition was to use the drop down at > space to get a list of spaces.I thought the document index would list the > spaces available. Ah ok, I think I understand what you mean. Clarify if I am wrong: on the bread crumb, you think that it would be a good idea if it listed the adjacent areas in the drop down. eg. if you hover over the pages, it will reveal all the pages in the same space as the current document. As a status update. I've done most of the mobile of the skin. Go ahead and try it in your respective browser: http://jssolichin.com/xwiki. I have presently tested it on android and Windows Phone along with browser resize on Chrome. Trying to get my hands on some iphone/blackberry. Let me know any glaring issues on those browsers in the mean time. What do you guys think about my implementation/solution to the sidebar? I handled the swiping a bit differently than the Coffin example. The issue with coffin is that it seems that it is not cross compatible. The swipe gesture does not work on WP7 nor on a browser. If you load coffin in a browser with a small viewport, you lose the ability to scroll completely and have no way to access the rest of the pages or the menu (unless i'm doing it wrong). The way I solved this issue is by making the sidebar in a negative position. In the mobile browser I tested, it seems to disregard this, so you can still swipe to see the sidebar. But since you can not do this is a desktop browser, i implemented the links to access it (sort of reminiscent of WP's right arrow for apps access). Another benefit is that it allows the browser to natively direct user to a specific div using #. So if I sent someone a link to http://jssolichin.com/xwiki#attachments, it should load the webpage in that area (also why I used scrolling instead of tabs). What do you guys think? One thing that I am wondering though is, sometimes a few lines of extra code is needed to make sure all the feature work properly upon resize. Should I worry about this? Like if a viewer resizes the browser from a desktop to a mobile size, should I add extra lines to make sure he can view it correctly? A lot of this has to do with the resizing capability of the sidebar (which can't be accomplished with css). Next step: implement all the drop down and test compatibility on mobile (as I can get a hold of them) and firefox/safari/ie. Also, begin porting over to xwiki/simplifying/standardizing. Thanks friends! JS

12 years, 2 months

[xwiki-devs] WYSIWYG goes to cache instead of opening the editor?

by echocoder

When editing an Xwiki page and choosing the WYSIWYG option instead of showing the editor it takes the user to a blank HTML cache page in /xwiki/resources/js/xwiki/xwe/*.cache.html. Do any of you know the cause of this and/or how to fix such? -- View this message in context: http://xwiki.475771.n2.nabble.com/WYSIWYG-goes-to-cache-instead-of-opening-… Sent from the XWiki- Dev mailing list archive at Nabble.com.

12 years, 2 months

[xwiki-devs] [ANN] XWiki Summer 2012 Hackathon

by Vincent Massol

Hi devs and community at large, Every year XWiki SAS (http://xwiki.com) gathers all its employees for a Seminar and every year we have an internal hackathon. For example here are the results of last year: http://www.xwiki.com/xwiki/bin/view/Company/Hackathon2011 Previously the Hackathon was a 1 day event only. However this year we're changing the format; it'll run for 8 days! :) Thus we thought it could be a good idea to invite the XWiki Community to join us for a mega distributed Hackathon! So here's how I think we could organize it: * Start date: 20th of July. A mail will be posted on this day to announce the start * End date: 27th of July. A mail will be posted on this day to announce the end * Gathering results: from 28th to 6th of August. Everyone who participated should reply to the end of hackathon mail with what they did and post their stuff on http://extensions.xwiki.org or elsewhere * On around the 6th of August we'll have a blog post written on xwiki.org summarizing all that was done by everyone Those who have participated will also get XWiki T-Shirts. Anyone interested in joining the fun? Thanks -Vincent with my XWiki SAS employee hat

12 years, 2 months

[xwiki-devs] Improved supported database testing and testing results

by Sorin Burjan

Hello, As you know, we have defined a supported database strategy, found here: http://dev.xwiki.org/xwiki/bin/view/Community/DatabaseSupportStrategy At the moment, in our release notes, we report the supported list of databases in the "Tested Databases" section. This is a little bit misleading, because we don't perform a full manual test on each of them. Also, at the moment, we don't have automated tests running on these databases. What I currently do is to test migration on each databases from an older version (in my case, I am using 2.7.2) to the current upcoming release. I usually perform these tests before RC1 so we make sure issues won't slip in the final release. Also, this testing is done on vanilla wiki's, so they don't reflect or simulate a large wiki migration with thousands of users and pages. What I want to propose is: 1) improve the "Tested Databases" section, so we list that we only test migrations and we don't perform a full test on each of the databases. This would mean adding a small explanation about this in the release notes pages. 2) When we release a new version, migrate myxwiki.org to the latest version, so users using it can report possible issues due to migration. This is a little hard for me to do since if something goes wrong, I could break a lot of things. Someone with more experience should do it, if there volunteers. I am waiting your feedback about this since I want to improve the visibility of testing, and also try to test migrations in a more real world environment Regards, Sorin B.

12 years, 2 months

[xwiki-devs] Open Windows Explorer folder

by Hamster

I thought that this should be possible with 2.1 syntax, but I think I am overlooking something small... How can I create a link so a Windows Explorer opens to a (network)drive? For example: [[Open Temp>>unc:c:\temp\]] -- View this message in context: http://xwiki.475771.n2.nabble.com/Open-Windows-Explorer-folder-tp7579903.ht… Sent from the XWiki- Dev mailing list archive at Nabble.com.

12 years, 2 months

[xwiki-devs] [VOTE] Move all platform app PO from XE to platform

by Thomas Mortagne

Hi devs, Marius is currently witting PO for EM UI and I'm moving XR POs from XE to platform. Both are already pretty big stuff with various projects so it's easy. But we require admin app PO so we will have to move them to platform along with the admin app xar project. Problem is that right now admin app is a standalone project so transforming it in a multi module (XAR et PO) will change the XAR project id. It's not too much a bid deal right now because it's not installed a lot with EM so the sooner we change it the better. Since admin app is not the only one with this issue I propose to transform right now all standalone XAR projects in platform into multimodules and so change right now all their ids to *-ui so that we can have a *-po project for each of them. Here is my +1. -- Thomas Mortagne

12 years, 2 months

[xwiki-devs] New commons-repository module?

by Vincent Massol

Hi devs and Thomas, Just noticed a new commons-repository module. Could someone explain to me what is this new module and why it's not part of xwiki-commons-extension, even though it's full of references to "extension" everywhere in it? (109 occurrences) Note1: Its description in pom.xml is pretty vague: <description>XWiki Commons - Repository</description> In commons-repository-api it's even worse: <description>Contains commons stuff to use in a a client or a server implementation</description> Note2: On http://commons.xwiki.org/xwiki/bin/view/Main/WebHome it's not described either, nor on e.x.o Thanks -Vincent

12 years, 2 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs June 2012