incubator-photark-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Subash Chaturanga <>
Subject Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums
Date Fri, 15 Oct 2010 13:56:05 GMT

On Mon, Oct 11, 2010 at 11:10 PM, Luciano Resende <>wrote:

> On Mon, Oct 11, 2010 at 10:35 AM, Subash Chaturanga <>
> wrote:
> >> 4) When I go back to albums view, it does not show any of the remote
> >> albums. Is that part supposed to be working already ?
> >>
> >
> >
> > No , as a first step I just stored remote album meta data in a java
> > collection.Didn't show them in gallery. As I hadn't a clear idea
> of,whether
> > to store them in the repository or not.For that I have to change the
> method
> > and store those meta data in the repository as the next step.And retrieve
> > them and create albums and put them in gallery (as i feel) .
> >
> Can you describe what your thoughts on how you are going to do this ?

In my patch the method addAlbumSubscriptionImages(String feedURL) can be
improved to store the album images in the repository by using
JCRGalleryImpl.addAlbum() , JCRImageUploadServiceImpl.addPictureToAlbum()
methods . So that they will directly show in the gallery and it will count
to search results as well. Further we can add a new property to album
node specifying whether it is a remote album or not, so that we can view
them separately in gallery.

                                             {   But in  addPictureToAlbum()
method we find album.addPicture() which just add a new node with a image
name.That code block catches only the Repositoryexception. As jackrabbit
100% JCR compliant it must support SNS (same-name-sibblings). So that if we
add an image with already exist image name it will not overwrite it (which
we want to happen). But as I know nt:folder(not quite sure) does not support
SNS. Then it will throw ItemExistsException and we can modify the code at
addPicture() and catch that and overwrite the new image    }

And we can put a refresh button to each remote album which will update the
node again. This will be done only if refresh is clicked (which is fare
enough). So that we do not have any overhead of sync.

> Who is going to be responsible for what ?

As we going through the typical procedure to add an album (addAlbum
, addPictureToAlbum) everything will be done after checking the
authorization level.

> --
> Luciano Resende



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message