[xwiki-devs] Willing to Contribute Xwiki in Gsoc 2009
Hi all I am an undergraduate at University of Moratuwa specializing in the field of Computer Science and Engineering and willing to take part in XWiki during this summer. I participated in Gsoc last year with Sahana community where i involved in implementing a project relating to social networking and i completed it successfully [1] . Where i had to play with photo related works and i extracted more on the methodologies of handling those information. I myself think this project is kind of interesting for me and will be able to contribute you effectively than last years as i am more passionate on FOSS and Gsoc. Further i am really interested in Java projects as most of the projects i have done and experienced are lied on Java.One of them is listed below [2]. Regarding the photo album application i want some more clarifications on migration tool from the old version photo albums. is it kind of extracting features based on the old implementation having their core logics, in new appliaction or just a tool to convert old photo albums to new one with their excisting features. Would you mind clarifying me on this. Further regarding the Import Export from any other Wiki , would it be kind of content transferring mechanism among wikis. In that case i can think in terms of providing a link aside to transfer a selected content on one wiki to another etc. I am glad to have more information on this too. [1] http://docs.google.com/Doc?id=dhh6gcfm_29cjk88fj8&hl=en [2] http://sci-flex.org/ Thanks in advance Harsha
Harsha Halgaswatta wrote:
Hi all
I am an undergraduate at University of Moratuwa specializing in the field of Computer Science and Engineering and willing to take part in XWiki during this summer. I participated in Gsoc last year with Sahana community where i involved in implementing a project relating to social networking and i completed it successfully [1] . Where i had to play with photo related works and i extracted more on the methodologies of handling those information.
Hi Harsha, Thanks for you interest in XWiki. Previous GSoC experience is good for your chances of being accepted.
I myself think this project is kind of interesting for me and will be able to contribute you effectively than last years as i am more passionate on FOSS and Gsoc. Further i am really interested in Java projects as most of the projects i have done and experienced are lied on Java.One of them is listed below [2].
Regarding the photo album application i want some more clarifications on migration tool from the old version photo albums. is it kind of extracting features based on the old implementation having their core logics, in new appliaction or just a tool to convert old photo albums to new one with their excisting features. Would you mind clarifying me on this.
The migration is a simple script that reads object from one type and saves the data to a different type. Once you learn the XWiki way of writing applications, you'll see that this is really easy. Reading a tutorial helps a lot: - http://www.theserverside.com/tt/articles/article.tss?l=XWiki - http://platform.xwiki.org/xwiki/bin/view/DevGuide/FAQTutorial So, short answer, it is a simple data migration tool.
Further regarding the Import Export from any other Wiki , would it be kind of content transferring mechanism among wikis. In that case i can think in terms of providing a link aside to transfer a selected content on one wiki to another etc. I am glad to have more information on this too.
This means being able to convert from MediaWiki to XWiki for example. Each major wiki has the ability to export data in a certain format, either XML pages, or plain text, whatever. There is no standard format for this. The use case is: - I've been a happy WhateverWiki user for 2 years. But I just found out about XWiki, which is way better than my old WhateverWiki - I want to migrate my old wiki to XWiki - I use the export feature of WhateverWiki to get an archive with my old content - I open XWiki and use the ImportFromWhateverWiki feature to automatically have my old data inside my new wiki The project targets exactly this process of reading that archive, creating a page for each archived page, and convert the syntax between the wiki syntax of WhateverWiki to XWiki. Fortunately the syntax conversion is easy to do using our new parsing/rendering engine, which is already able to convert to and from major wiki syntaxes. -- Sergiu Dumitriu http://purl.org/net/sergiu/
Hi sergiu Thanks a lot for your information. Now i am reading the document u specified and later will touch you upon any issues. Thanks Harsha
On Sat, Mar 21, 2009 at 1:36 AM, Harsha Halgaswatta < [email protected]> wrote:
Hi sergiu I did go through most of the stuff relating to what you already specified. It seems interesting that i inspired myself by mining deep into those. In point of a photo album it is pretty important to maintain more information relating to photos than it used to be along with the old version. In addition to what is mentioned it would be possible to add these features as well.
1) Commenting upon photos 2) Add description relating to photos 3) Image cropping feature to select what portion need to remain in the album etc. 4) Scaling photos as user wish 5) Tagging feature around photos (Ajax based) So i think in point of Xwiki it would better to have those features too. So i am glad to know what you think on this. Thanking you Harsha
Harsha Halgaswatta wrote:
On Sat, Mar 21, 2009 at 1:36 AM, Harsha Halgaswatta < [email protected]> wrote:
Hi sergiu I did go through most of the stuff relating to what you already specified. It seems interesting that i inspired myself by mining deep into those. In point of a photo album it is pretty important to maintain more information relating to photos than it used to be along with the old version. In addition to what is mentioned it would be possible to add these features as well.
1) Commenting upon photos
This should be done using the existing XWiki comment mechanism, if possible. We tend to make applications as reusable as possible, so that we don't have to duplicate functionality between different features.
2) Add description relating to photos
Yes, this is a must.
3) Image cropping feature to select what portion need to remain in the album etc. 4) Scaling photos as user wish
These will require a Java part as well, since currently there's no public API for this. An image processing plugin would be good for other purposes as well. You should start with this, so that it can be used by other parts of XWiki (the attachment section, the WYSIWYG editor).
5) Tagging feature around photos (Ajax based)
This could also be done using (and enhancing) the existing tagging feature.
So i think in point of Xwiki it would better to have those features too. So i am glad to know what you think on this.
I agree with these features. I'm sure that there are many other things that could be done, but the important thing is to have an application that works well with few features at the beginning, and which is easy to extend afterwards, meaning that after the base is polished, you can add features one by one, with little effort. -- Sergiu Dumitriu http://purl.org/net/sergiu/
Hi Now i have gone through many tutorials and documents and obtained a good picture of xwiki photo album over existing old photo album. I saw that the commenting features and some other features are very basic and even don't comply with the expected flow. Now i am in the process of making some mockups while thinking the class level interaction just to illustrate you the flow of the photo album along with their functionalities. After going through the xwiki way i feel it would better create a class while creating a new album and attach it to the page. Then anyone who creates an album would gain the reference (instance) of that class. This class would consist of the functionalities that are possible with the newly created album.Consequently the front end would invoke underlying logics as they suppose to gain the functionality out of the class. Perhaps i may need two or three classes accordingly (one class may be too big etc). What do you think ? Other than that Would you please let me know where the xwiki commenting features and tagging features retain, From where i would learn it. And also in some situations i may need to involve with Ajax based scenarios (maintaining privacy information , tagging features etc). How Ajax is used in xwiki , would i free to use any Ajax library or what else. I hope to present you the mockups of the photo album today evening or tomorrow. Thanking you. Harsha
On Mon, Mar 30, 2009 at 7:35 PM, Harsha Halgaswatta < [email protected]> wrote:
Hi
Now i have gone through many tutorials and documents and obtained a good picture of xwiki photo album over existing old photo album. I saw that the commenting features and some other features are very basic and even don't comply with the expected flow.
Now i am in the process of making some mockups while thinking the class level interaction just to illustrate you the flow of the photo album along with their functionalities.
After going through the xwiki way i feel it would better create a class while creating a new album and attach it to the page. Then anyone who creates an album would gain the reference (instance) of that class. This class would consist of the functionalities that are possible with the newly created album.Consequently the front end would invoke underlying logics as they suppose to gain the functionality out of the class. Perhaps i may need two or three classes accordingly (one class may be too big etc). What do you think ?
Other than that Would you please let me know where the xwiki commenting features and tagging features retain, From where i would learn it. And also in some situations i may need to involve with Ajax based scenarios (maintaining privacy information , tagging features etc). How Ajax is used in xwiki , would i free to use any Ajax library or what else.
Adding something : Commenting features are ok , i just went through it. It's pretty cool It mentions the UI should be Ajax based and should also be functional in browsers without JavaScript. In that case would i have to implement the same scenarios in two ways ? . I mean if i use Ajax libraries for a function it works on javascript enabled browsers, if not it fails. Then the functionality should be preserved without javascript using another techniques. is there a specific library or method in Xwiki to handle those kind of scenarios.
I hope to present you the mockups of the photo album today evening or tomorrow.
Thanking you. Harsha
participants (2)
-
Harsha Halgaswatta -
Sergiu Dumitriu