Hi, On Wed, Apr 6, 2011 at 22:23, shweta agrawal <[email protected]> wrote:

Hi,

I have identified following task list.

*File Uploading Part -* Allow upload of Zip files and Extracting image files from zip archive (java.util.zip package). //use storage implementation accordingly - filesystem or database. //image compression can be done by using java image io api. As Marius said there is only resizing capability available in xwiki and jpeg with quality near to 60% are optimum for web display, so compression can be used.

*Extracting EXIF information from image files.* (This information can be stored in a separate db table. I found this http://www.drewnoakes.com/drewnoakes.com/code/exif/. It's a java metadata extractor library for jpeg image files. )

Tags - allowing *tagging of attachments*. We can have a separate column of tags in the attachment_content table where different tags can be stored (separeted via pipeline). WDYT?

Tags can be displayed just for the attachments in the photo application. We can make it general, but we need to see more use cases. Right now in XWiki the only things you can add tags are pages. Tags are represented as objects.

Comments - associating *comments with an attachment*. As I have no idea how comments are stored so can't say anything about it right now.

Just like tags, comments are stored as objects to pages.

Designing and Implementing *Browsing Interface and Album/Photo manipulation interface* Browsing Interface - interface that allows users to browse albums easily thumbnail view and slide show browse based on some metadata info like author or location Album manipulation interface Add Photos Delete Photos Managing manipulation rights for the album Editing basic info about Album Photo Manipulation Interface Using canvas element - manipulate rotation, opacity, cropping, adjusting gamma, contrast, brightness etc Editing basic info about Photo

Currently I am working on gsoc proposal and basic drafts of album browsing interface. Is this task list ok?

The list is ok. Go ahead and complete your proposal. Thanks, Caty

Further, I am thinking that I should start with Browsing Interface, then after that file uploading part and EXIF information extraction will be implemented. What do you say? (I need it for describing project plan and timeline in gsoc proposal).

Looking for your feedback.

Thanks Shweta Agrawal

On Mon, Apr 4, 2011 at 8:05 PM, Ecaterina Moraru (Valica) < [email protected]> wrote:

Hi,

...

On Sat, Apr 2, 2011 at 14:03, shweta agrawal <[email protected]>wrote:

Hi,

...

I have checked out the HTML 5 specifications for geo-location api, file uploading api and canvas container.

At present, all the attachments are stored in database irrespective of their nature (the old photo album also uses db to store images). I browsed to find out which is better for storing image files - database or file system and found that most of the posts favored filesystem (in case of large number of images). I need your suggestion regarding which one is better in xwiki's context. In case of using filesystem for storing image files, migration of older version photo albums will be complicated as image files will need to be imported from database to file system.

Right now from what I know attachments are stored in the database. Caleb is working on a new storage that will use the filesystem. So IMO you don't have to worry about this aspect and also it will not be very relevant for this project (you will only have to use the storage, not implement it). See http://markmail.org/thread/pl7v4sew2ujksrvv

...

Secondly, most of the online photo album application (flickr, picasa web album, facebook) uses image compression for rendering images fastly on slower networks, so do we also intend to use some compression algorithm and optimize the image files for display on web. (xwiki can have something of this sort that is if image size is more than some threshold value (say 1 Mb or 512 kb) then it can be stored as a compressed image). I haven't checked out which algorithms are used and does there exist any library or API for image compression, so can't say how much time it will take to implement.

I think we already have some image compression on the server side. Marius can give more information about this. See http://markmail.org/thread/kbazwdlgmrlsllcv

...

what about sharing photo album only with a specific group not all users and also having manipulating rights to some users only (unlike the old photo album application, any registered user can add or delete photos created by some other user)?

This won't be a problem either. If the application is located at space level and let's say albums are identified at page level, then you can easily play with the rights system and give permissions just to a group or user, etc. See http://platform.xwiki.org/xwiki/bin/view/Features/RightsManagement

Thanks, Caty

...

Thanks Shweta Agrawal

On Tue, Mar 29, 2011 at 2:35 AM, Ecaterina Moraru (Valica) < [email protected]> wrote:

...

On Mon, Mar 28, 2011 at 16:38, shweta agrawal <[email protected]>wrote:

Hi,

...

I am Shweta Agrawal, final year computer science student at IIT Roorkee, India. I want to apply for GSoC this year and am interested in working on Photo Album Application. I have four year experience in web development and have good understanding of HTML, CSS, Php, python and Javascript. I have worked on creating user interfaces for a couple of websites and developed applications like online music player (similar to grooveshark), online notice board etc for my Institute's intranet.

As far as I understand the project, it's aimed at developing an application where users can

- upload the photos (one by one or zip files or folders) with information like date, caption, location etc.- this info can be extracted by reading exif information. *additional* - multiple file selection and upload, drag and drop functionality (supported by HTML 5 compliant browsers). ** *doubt* that do we intend to create a default album for all the images uploaded/attached by user on any of the pages i.e. not only the images that are uploaded for some album. It will provide user an easy way to manipulate and browse through all uploaded image files.

the intent is to have albums. This means the user specifies the desired

photos he wants to add to his album. About your idea: to have an album with all the images uploaded by user: this is already accessible if you go to Main/AllDocs?view=attachments and filter the user.

...

- create albums and add information like title, caption, description and location. *doubt* - will there be any limit on maximum number of photographs in an album?

we don't have any limit on the number of attachments we add to a page, so we shouldn't have a limit here either.

...

- browse through the uploaded photographs (available in browsers not having javascript - It can be done using css3).

we recently have something like http://extensions.xwiki.org/xwiki/bin/view/Extension/Gallery+Macro and

http://extensions.xwiki.org/xwiki/bin/view/Extension/Attachment+Selector+Mac... to give you some example of extensions that handle attachment viewers.

...

- view as thumbnails and slideshow (with adjustable timer and with manual browsing).

- migration tool from the old version photo albums. *doubt* - what does old version photo albums refer to?

This is the very old Photo album application that we want to replace.

http://extensions.xwiki.org/xwiki/bin/view/Extension/Photo+Album+Application

...

- ability to tag and associate comments with attachments. *doubt* - does attachments here refers to image files only or any type of files.

for the purpose of this project refers to images, but this should be extensible so we could comment on any type of files.

...

I have browsed through the code of older photo album application. I need guidance that is how should I start working on this application? I am thinking about starting with uploading part.

Learn a bit XWiki structure and the way applications and extensions are done, integrated and reused. You can find lots of applications at http://extensions.xwiki.org/xwiki/bin/view/Main/ You can play with them, see also the source code, etc.

The specifications for this project are very oriented towards the HTML5 standard so you should check that out too.

Thanks, Caty

...

Looking forward to your feedback.

Regards

Shweta Agrawal B.Tech IV YR CSE IIT Roorkee _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs