Re: [xwiki-devs] [GSOC] [Status Request] Middle of Community Bonding period
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 <[email protected]> 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/ImproveandroidXWikico... 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 <[email protected]> wrote:
On Tue, May 8, 2012 at 4:51 PM, sasinda rukshan <[email protected]> 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 <[email protected]>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 <[email protected]> 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 [email protected] http://lists.xwiki.org/mailman/listinfo/devs
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Thomas Mortagne
-- Thomas Mortagne
Le 13 mai 2012 à 19:10, Thomas Mortagne a écrit :
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).
Sasindra, I use and love IntelliJ IDEA, feel free to ask (on list!). My most trustable practice is to keep importing "from external model (maven)". Also, in syntax 1.0, I often add the following comments near to the top: #* @vtlvariable name="xwiki" type="com.xpn.xwiki.api.XWiki" *# ## #* @vtlvariable name="request" type="javax.servlet.http.HttpServletRequest" *# ## #* @vtlvariable name="response" type="javax.servlet.http.HttpServletResponse" *# ## #* @vtlvariable name="msg" type="com.xpn.xwiki.web.XWikiMessageTool" *# ## #* @vtlvariable name="doc" type="com.xpn.xwiki.api.Document" *# #* @vtlvariable name="util" type="com.xpn.xwiki.api.Util" *# ## #* @vtlvariable name="escapetool" type="org.apache.velocity.tools.generic.EscapeTool" *# ## this allows me to have auto-completion on the method names. I am pretty sure this can work for the new syntax as well. paul
participants (2)
-
Paul Libbrecht -
Thomas Mortagne