xwiki-devs May 2012

xwiki-devs@xwiki.org

32 participants
102 discussions

[xwiki-devs] Functional tests in continuous integration

by Edo Beutler

Hi devs Yesterday the hard disk of our local machine running Jenkins crashed. We decided to use that as a reason to move Jenkins to one of our servers. This should be easy to do, with exception of the functional tests (Selenium). Currently we are evaluating if it's worth it to install our own test environment or if we should use an SAAS solution. I tried to figure out how you solved this problem, but I couldn't find the details of how / where you run your functional tests during the continuous integration. So, do you run your functional tests for the different browsers (and browser versions) on you own servers or do you use a third party solution? Thanks for a hint / inspiration Edo

13 years

[xwiki-devs] Velocity uberspector to automatically convert String method arguments to Enum when possible

by Marius Dumitru Florea

Hi devs, I just committed a new Velocity uberspector that automatically converts String method arguments to Enum when possible. Please review it and tell me if there's something wrong. The idea is to be able to call #someMethod(SomeEnum) with $obj.someMethod('VALUE') if SomeEnum.VALUE is a valid constant. See https://github.com/xwiki/xwiki-commons/commit/dbf1e06cc4f949c6f0b5a03c57067… . Thanks, Marius

13 years

[xwiki-devs] Inconsistency in page REST resource: raw vs. display title

by Marius Dumitru Florea

Hi devs, While debugging the failing REST integration tests I discovered an inconsistency in the page REST resource. Take for instance the response returned for this URL: /xwiki/rest/wikis/xwiki/spaces/Blog/pages/BlogIntroduction * The returned content is the raw (not rendered) content. In this particular case, since the blog post content is saved in the blog post object, and also because the blog uses the new sheet system, the raw content of Blog.BlogIntroduction page is empty * The returned title is the display title (i.e. the rendered title). In this particular case, since the raw title is empty, but the blog post sheet, which controls how the title is displayed, renders the 'title' property of the blog post. The inconsistency is that the content is raw while the title is rendered. I think the page REST resource should provide data in the first place, so raw title. It could provide the rendered title or content additionally, but that is secondary IMO. WDYT? I'll fix the REST integration tests by using a page that doesn't have a sheet. Thanks, Marius

13 years

[xwiki-devs] XWiki 4.1 Milestone 1 release is in staging.

by Caleb James DeLisle

13 years

[xwiki-devs] [proposal] Change the release repository to nexus so all releases will be staged by default.

by Caleb James DeLisle

Hi, I'd like to change the <repository> in each top level pom to nexus so that on release, all releases will go directly to staging by default. Agent1 already has an account in the staging repository from my last release so this should just work. WDYT? Caleb

13 years

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

by Jonathan Solichin

Hello friends, First thank you for the inputs. > About the tentative time-line, please confront each step with a date. I'm not sure whether it was unclear or not, but the numbers represents the weeks of GSOC and are not arbritrary. Unless you want the exact date, then I can go ahead and revise it again. I also appended to the beginning: a design exploration stage as per your request. [1] > About the mock-ups, personally I would prefer we make it a complete > > initial phase of the project, to take the time to create a skin > > afresh, trying as much as possible to forget about what has been done > > in colibri (the current default skin of XWiki) and instead think > > outside the box. This would mean forgetting about how menus, links, > > information etc. is displayed, and come up with an actual new skin. > > Especially since I understand you have design skills ;) Thank you. Right, ok so I wasn't sure how much creativity i am allowed with the skin and that's why my first mock up is pretty close to colibri. I created a second mock up of a more "brave" skin. desktop [2], mobile [3], What does the community think? wrong or right direction? > I would love to see some fresh ideas of how the responsive skin would look > like. > Jonathan should provide some a timeline in order to see how expensive this > phase would be. Ok so at the moment, I am aiming for a week of design exploration. But to be honest, I have never worked on a project like this, or created a time line. If someone could comment on my timeline [1] as to whether it is totally skewed or just about right, that would be great. Please also take a look at other ideas/layouts for the mobile skin > http://incubator.myxwiki.org/xwiki/bin/view/Improvements/MobileSkin This is a great resource. I will definitely look into this more deeply. Thank you! On a non Responsive Skin topic, is there a place where I can read/reply to the mailing list, beside email, that is more dedicated (like how google groups have an online "viewer")? Like the way links are delineated at the bottom as footnotes, does everyone do that manually, or is there a dedicated place that does this for you? It is a little bit confusing to read emails with multi-level quotes. Or maybe I am just not used to it. Thanks in advance. Kind Regards, Jonathan Solichin [1] http://dev.xwiki.org/xwiki/bin/view/Design/ResponsiveSkin [2] http://jssolichin.com/public/2/desktop.jpg [3] http://jssolichin.com/public/2/mobile.jpg

13 years, 1 month

Re: [xwiki-devs] [GSOC] [Status Request] Middle of Community Bonding period

by Paul Libbrecht

Sasinda, please keep on list. What you describe is indeed the spirit I envision. paul Le 14 mai 2012 à 16:38, sasinda rukshan a écrit : > Thanks. That means I document the descriptive architecture on the Design page. And a total prescriptive one on an extra section. > Anyway the already showed figure "tentative architecture " is a prescriptive one. > Shall I do as follows. Two sections for > Descriptive architecture: Actual implemented architecture. documentation modified as I actually implement the platform. > Prescriptive architecture: How it is envisioned but may not actually implemented. > > If the page is getting lengthy(hope not) can I create more extension pages? If so where? > > Thanks. > Best Regards. > Sasinda > > > On Mon, May 14, 2012 at 7:57 PM, Paul Libbrecht <paul(a)hoplahup.net> wrote: > > Le 14 mai 2012 à 14:47, sasinda rukshan a écrit : > >> But should I add that in the design page and describe? > > I would add this as a separate section of the design page. > It should be clear to evaluate that the currently implemented design is "useful enough", the extra section should show a "perspective". > > my 2p. > > paul >

13 years, 1 month

[xwiki-devs] [VOTE] Drop Firefox 3.6 Support

by Sorin Burjan

Hello everybody, As you know, starting with Firefox 4 Mozilla changed the release strategy of its browsers. They are having a new (rapid) release cycle, releasing a new version each 6 weeks. [1] Firefox 3.6 having a large market spread, Mozilla decided to keep the support for it in the past months. On the 24th April 2012, Mozilla announced it will no longer offer support for Firefox 3.6, making it EOL (End Of Life) During the meeting from yesterday (9th May 2012) they officially pulled the plug on Firefox on 3.6 [2], allowing the possibility of Firefox 3.6 users to upgrade to the latest version. [3] Since Firefox 3.6 will not be supported by Mozilla, I propose we also drop the support for Firefox 3.6. Here is my +1 (note that my vote is not binding) Regards, Sorin B. [1] http://www.tomsguide.com/us/firefox-rapid-releases-browserwars,news-12613.h… [2] https://wiki.mozilla.org/Firefox/Planning/2012-05-09#Release_.2812.2C_10esr… [3] https://bugzilla.mozilla.org/show_bug.cgi?id=753006

13 years, 1 month

[xwiki-devs] State of release 4.1

by Caleb James DeLisle

Hi, It looks like I've managed to let another release date slip by, my apologies. Right now we have only 1 failing integration test and it's failing because of a potentially unexpected feature but not a bug. The difference between this and last year is like night and day. Everyone deserves a pat on the back for the hard work getting the build in shape! We have 2 open blocker issues: http://jira.xwiki.org/browse/XWIKI-7309 Denis do you know the status of this? Is it a "cannot reproduce, waiting and watching" situation? and http://jira.xwiki.org/browse/XWIKI-6987 From the description, it looks like the issue is more about misunderstanding of the permissions system, Andreas? and open 7 non-blocker issues with a fix-for version of 4.1M1, ordered by assignee: Vincent: http://jira.xwiki.org/browse/XWIKI-7737 http://jira.xwiki.org/browse/XWIKI-7738 Jerome: http://jira.xwiki.org/browse/XWIKI-7785 Is this one finished? Marius: http://jira.xwiki.org/browse/XWIKI-7764 Thomas: http://jira.xwiki.org/browse/XWIKI-7652 http://jira.xwiki.org/browse/XWIKI-7366 http://jira.xwiki.org/browse/XWIKI-7501 Hopefully we can get these issues cleared up today and tomorrow and I'll push a build into staging tomorrow or over the weekend so we can do proper testing on Monday before pushing the binaries to the repositories. WDYT? Caleb

13 years, 1 month

Re: [xwiki-devs] [GSOC] [Status Request] Middle of Community Bonding period

by Thomas Mortagne

Please, there is no reason to send mail like that to me personally. Especially when you answer to a mail sent on the mailing list ;) On Sun, May 13, 2012 at 3:18 PM, sasinda rukshan <sasindarukshan(a)gmail.com> wrote: > Hi All,Thomas, > I created the initial design page and edited the progress page. > Named the project XWiki Android Platform. If you don't like the name feel > free to change it :). It's your project, and better choosing something you fill is the right one ;) I'm ok with this name and it make it clear is a framework more than a final application. > http://dev.xwiki.org/xwiki/bin/view/Design/XWikiAndroidPlatform > http://dev.xwiki.org/xwiki/bin/view/GoogleSummerOfCode/ImproveandroidXWikic… > I will check maven. > Also will compare development with IDEAJ vs eclipse ADT. I ll familirize > myself with XWiki REST model and earlier Android Client work this week. Ok cool. Note that I'm using Eclipse myself so I would not help you much for IntelliJ. ADT was pretty nice from what I remember (and this was last year, did not have much time to play with Android since then). > > Thanks, > Best regards > Sasinda. > > > On Wed, May 9, 2012 at 1:34 PM, Thomas Mortagne <thomas.mortagne(a)xwiki.com> > wrote: >> >> On Tue, May 8, 2012 at 4:51 PM, sasinda rukshan >> <sasindarukshan(a)gmail.com> wrote: >> > Hi Thomas, >> > Sorry for not being able to participate in the community bonding yet. >> > I am very busy with exams these days. Hope you noticed me in the >> > proposal >> > that I am unable to actively participate until 10 th May. 1 exam got >> > postponed. I will start after 12th May and document the project details. >> > I >> >> Sure but starting creating a page and put in it the design work you >> already started for the GSOC proposal should not take very long. You >> can improve it later. >> >> > made the proposal publicly available just for now. Hope 12 to 21 is >> > enough >> > to catch up since XWiki mobile project is a bit separate from XWiki. >> >> It is technically separated since it's running in Android but will >> still have to deal with XWiki model and REST API. Also if you never >> worked with maven before you will need some time to learn how the >> project build works and you should probably start by updating it with >> the latest plugin versions etc. >> >> > Thank you. >> > Best Regards. >> > >> > On Sun, May 6, 2012 at 3:36 AM, Jonathan Solichin >> > <jssolichin(a)gmail.com>wrote: >> > >> >> Hello friends, >> >> >> >> Here is the design page for Responsive Skin implementation [1]. >> >> Included: >> >> Goal, Approach, Tentative Timeline, Mock Ups. >> >> Early questions for the current design: >> >> >> >> 1. Specific support for non-javascript capable browser? I feel like it >> >> is >> >> not necessarily since browser which can not support javascript will >> >> fall >> >> back by itself. More over, it would not be capable of carrying out >> >> media-queries required for responsive design and some XWIKI features >> >> (such >> >> as live tables?) anyway. >> >> 2. Is the community ok with trying to use "true (html)" drop downs / >> >> forms >> >> in order to fully utilize functions built in to phone/tablets [3]? >> >> 3. Pressable Links: should they be bigger on mobile to help facilitate >> >> touching on words, or would it be better to use a "background" to >> >> create a >> >> "touch area"? Both are in the phone mock up [3]. Former demonstrated in >> >> quicklinks, latter in the "Spaces" section. >> >> >> >> [1] http://dev.xwiki.org/xwiki/bin/view/Design/ResponsiveSkin >> >> [2] http://css-tricks.com/convert-menu-to-dropdown/ >> >> [3] http://jssolichin.com/public/mobile.jpg >> >> >> >> Thank you again. Cheers & best, >> >> Jonathan Solichin >> >> >> >> On Fri, May 4, 2012 at 8:08 AM, Eduard Moraru <enygma2002(a)gmail.com> >> >> wrote: >> >> >> >> > Hello students, >> >> > >> >> > As you probably already know, we are almost at the middle of the >> >> community >> >> > bonding period [1]. >> >> > >> >> > From the previous mail [2] and XWiki's GSoC page [3], you also know >> >> > that >> >> > this is the time where you learn about XWiki's development processes, >> >> code >> >> > and community and, to better understand the code, you must fix at >> >> > least >> >> one >> >> > jira issue related directly or indirectly to your project. >> >> > >> >> > This is in no way a radio silence period, quite the contrary. >> >> > >> >> > In other words, you need to: >> >> > >> >> > 1. Answer this mail :) >> >> > 2. Create a Design page [4] regarding your project >> >> > 3. Start idling on the IRC channel >> >> > 4. Start chatting on the mailing list and on IRC about your project >> >> > and >> >> > other aspects of XWiki that you don't yet understand >> >> > 5. Get your hands dirty by diving into the code and fixing at least >> >> > one >> >> > Jira issue (2 more weeks left) >> >> > 6. Talk about your project >> >> > >> >> > What we want from you with this mail is to see where you stand with >> >> regard >> >> > to what has been written above. We want to know what you don`t >> >> > understand >> >> > about XWiki, what issue you are planning to undertake, what you want >> >> > to >> >> > start with, etc. >> >> > >> >> > It helps you more to start saying incorrect things and fixing them >> >> > early >> >> > instead of staying quiet and making a big bad choice towards the end. >> >> > >> >> > And a last thing, please remember that one-to-one conversations with >> >> > your >> >> > mentor are not encouraged and are actually harmful to the success of >> >> > your >> >> > project. Talk to the community, ask for help early and life will be >> >> sweeter >> >> > :) >> >> > >> >> > Thanks, >> >> > Eduard >> >> > >> >> > ---------- >> >> > [1] http://www.google-melange.com/gsoc/events/google/gsoc2012 >> >> > [2] http://markmail.org/thread/u6jhsqwxn6uitcjo >> >> > [3] http://gsoc.xwiki.org >> >> > [4] http://dev.xwiki.org/xwiki/bin/view/Design/WebHome >> >> _______________________________________________ >> >> 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

13 years, 1 month

← Newer
1
...
5
6
7
8
9
10
11
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

xwiki-devs May 2012