4 Apr
2011
4 Apr
'11
4:35 p.m.
Hi,
On Sat, Apr 2, 2011 at 14:03, shweta agrawal <shweta.9996(a)gmail.com> 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) <
valicac(a)gmail.com> wrote:
On Mon, Mar 28, 2011 at 16:38, shweta agrawal <shweta.9996(a)gmail.com>wrote;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+Ma…
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
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs