You are viewing a plain text version of this content. The canonical link for it is here.
Posted to photark-dev@incubator.apache.org by Luciano Resende <lu...@gmail.com> on 2010/10/11 04:14:39 UTC

Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

On Sun, Oct 10, 2010 at 4:20 PM, Luciano Resende <lu...@gmail.com> wrote:
> On Sun, Oct 10, 2010 at 12:03 PM, Subash Chaturanga <su...@gmail.com> wrote:
>> Hi all ,
>>
>> On Thu, Oct 7, 2010 at 1:47 PM, Avdhesh Yadav <av...@avdheshyadav.com> wrote:
>>
>>> check this thread.
>>> http://www.mail-archive.com/photark-dev@incubator.apache.org/msg00784.html
>>
>>
>> The first patch i submitted stores each subscribed albums in a java
>> collection .So based on that, for the next step, I went through the above
>> discussion and what i feel was to store the meta data
>> (location,name,description) of images in a JCR node. As, a JCR  property can
>> hold multiple values, I think we can store each album as a property and we
>> can have two nodes for flicker and picasa . So that when we want to show
>> them in gallery we can retrieve those data and on the fly create albums and
>> show them in the gallery. I would like to know, if anything wrong with this
>> approach or is there any better way to do this?
>>
>>
>>
>>
>
> I'd recommend following the same node structure as the "local JCR"
> albums, which the exception that when it's a subscription, the actual
> image is stored remotely and we only have it's URL.
>

I was taking a look at the latest patch, and I'd have couple
suggestions to the Subscription UI:

1) Today for the upload ui, a user can choose a "New Album" or select
an existing album. How about we just create a new entry "New Remote
Album" for the Picasa or Flickr albums, and then show required fields
like : type (Picasa, Flickr, or anything new we might have) and then
the URL, username and password ?

2) Both upload.html and upload.js seems to have specific fields to
picasa_xxxx. This will not scale when we add support for different
types of remote albums. We should just make generic fields like
album_remote_url, album_remote_user, etc and use those independent of
the type of remote album that is being added to the gallery

3) It seems that subscription is actually working, but the ui is
acting a little weird as it seems to have succeeded adding the new
remote album, but it then stays on the same page with the fields all
populated as if a error had happened.

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 ?


I'll look in the backend part later on when I find more time :)


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Avdhesh Yadav <av...@avdheshyadav.com>.
On Mon, Oct 11, 2010 at 9:44 AM, Luciano Resende <lu...@gmail.com>wrote:

> On Sun, Oct 10, 2010 at 4:20 PM, Luciano Resende <lu...@gmail.com>
> wrote:
> > On Sun, Oct 10, 2010 at 12:03 PM, Subash Chaturanga <su...@gmail.com>
> wrote:
> >> Hi all ,
> >>
> >> On Thu, Oct 7, 2010 at 1:47 PM, Avdhesh Yadav <av...@avdheshyadav.com>
> wrote:
> >>
> >>> check this thread.
> >>>
> http://www.mail-archive.com/photark-dev@incubator.apache.org/msg00784.html
> >>
> >>
> >> The first patch i submitted stores each subscribed albums in a java
> >> collection .So based on that, for the next step, I went through the
> above
> >> discussion and what i feel was to store the meta data
> >> (location,name,description) of images in a JCR node. As, a JCR  property
> can
> >> hold multiple values, I think we can store each album as a property and
> we
> >> can have two nodes for flicker and picasa . So that when we want to show
> >> them in gallery we can retrieve those data and on the fly create albums
> and
> >> show them in the gallery. I would like to know, if anything wrong with
> this
> >> approach or is there any better way to do this?
> >>
> >>
> >>
> >>
> >
> > I'd recommend following the same node structure as the "local JCR"
> > albums, which the exception that when it's a subscription, the actual
> > image is stored remotely and we only have it's URL.
> >
>
> I was taking a look at the latest patch, and I'd have couple
> suggestions to the Subscription UI:
>
> 1) Today for the upload ui, a user can choose a "New Album" or select
> an existing album. How about we just create a new entry "New Remote
> Album" for the Picasa or Flickr albums, and then show required fields
> like : type (Picasa, Flickr, or anything new we might have) and then
> the URL, username and password ?
>
> +1.In flicker user only needs to give the feed URL , no  need of user name
and password .and i think its also true with pisaca(i have to check it).

2) Both upload.html and upload.js seems to have specific fields to
> picasa_xxxx. This will not scale when we add support for different
> types of remote albums. We should just make generic fields like
> album_remote_url, album_remote_user, etc and use those independent of
> the type of remote album that is being added to the gallery
>
+1

>
> 3) It seems that subscription is actually working, but the ui is
> acting a little weird as it seems to have succeeded adding the new
> remote album, but it then stays on the same page with the fields all
> populated as if a error had happened.
>
Well the backed code is incomplete.we need to add code for storing the
remote albums subscriptions to JCR.

>
> 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 ?
>
>
> I'll look in the backend part later on when I find more time :)
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
Avdhesh Yadav
http://www.avdheshyadav.com
http://twitter.com/yadavavdhesh

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Luciano Resende <lu...@gmail.com>.
On Mon, Oct 11, 2010 at 7:23 AM, Subash Chaturanga <su...@gmail.com> wrote:
> Hi Luciano,
> I did the changes (as said) in upload.js and upload.html. Also in the UI .
> So before submitting the new patch i would like to know is this the UI you
> expected ? Please find the following attachment.
> Thanks
> /subash
>

Attachments get filtered, better is to submit a patch and one of us
will take a look.


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Subash Chaturanga <su...@gmail.com>.
Hi Luciano,

I did the changes (as said) in upload.js and upload.html. Also in the UI .
So before submitting the new patch i would like to know is this the UI you
expected ? Please find the following attachment.

Thanks
/subash

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Subash Chaturanga <su...@gmail.com>.
Hi,

On Mon, Oct 11, 2010 at 11:10 PM, Luciano Resende <lu...@gmail.com>wrote:

> On Mon, Oct 11, 2010 at 10:35 AM, Subash Chaturanga <su...@gmail.com>
> 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
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
sk

Regards
/subash

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Luciano Resende <lu...@gmail.com>.
On Mon, Oct 11, 2010 at 10:35 AM, Subash Chaturanga <su...@gmail.com> 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 ?
Who is going to be responsible for what ?

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Subash Chaturanga <su...@gmail.com>.
On Tue, Oct 12, 2010 at 12:47 AM, Avdhesh Yadav <av...@avdheshyadav.com>wrote:

> On Mon, Oct 11, 2010 at 11:05 PM, Subash Chaturanga <subashsdm@gmail.com
> >wrote:
>
> > On Mon, Oct 11, 2010 at 9:44 AM, Luciano Resende <luckbr1975@gmail.com
> > >wrote:
> >
> > > On Sun, Oct 10, 2010 at 4:20 PM, Luciano Resende <luckbr1975@gmail.com
> >
> > > wrote:
> > > > On Sun, Oct 10, 2010 at 12:03 PM, Subash Chaturanga <
> > subashsdm@gmail.com>
> > > wrote:
> > > >> Hi all ,
> > > >>
> > > >> On Thu, Oct 7, 2010 at 1:47 PM, Avdhesh Yadav <avd@avdheshyadav.com
> >
> > > wrote:
> > > >>
> > > >>> check this thread.
> > > >>>
> > >
> >
> http://www.mail-archive.com/photark-dev@incubator.apache.org/msg00784.html
> > > >>
> > > >>
> > > >> The first patch i submitted stores each subscribed albums in a java
> > > >> collection .So based on that, for the next step, I went through the
> > > above
> > > >> discussion and what i feel was to store the meta data
> > > >> (location,name,description) of images in a JCR node. As, a JCR
> >  property
> > > can
> > > >> hold multiple values, I think we can store each album as a property
> > and
> > > we
> > > >> can have two nodes for flicker and picasa . So that when we want to
> > show
> > > >> them in gallery we can retrieve those data and on the fly create
> > albums
> > > and
> > > >> show them in the gallery. I would like to know, if anything wrong
> with
> > > this
> > > >> approach or is there any better way to do this?
> > > >>
> > > >>
> > > >>
> > > >>
> > > >
> > > > I'd recommend following the same node structure as the "local JCR"
> > > > albums, which the exception that when it's a subscription, the actual
> > > > image is stored remotely and we only have it's URL.
> > > >
> > >
> > > I was taking a look at the latest patch, and I'd have couple
> > > suggestions to the Subscription UI:
> > >
> > > 1) Today for the upload ui, a user can choose a "New Album" or select
> > > an existing album. How about we just create a new entry "New Remote
> > > Album" for the Picasa or Flickr albums, and then show required fields
> > > like : type (Picasa, Flickr, or anything new we might have) and then
> > > the URL, username and password ?
> > >
> > > 2) Both upload.html and upload.js seems to have specific fields to
> > > picasa_xxxx. This will not scale when we add support for different
> > > types of remote albums. We should just make generic fields like
> > > album_remote_url, album_remote_user, etc and use those independent of
> > > the type of remote album that is being added to the gallery
> > >
> > > 3) It seems that subscription is actually working, but the ui is
> > > acting a little weird as it seems to have succeeded adding the new
> > > remote album, but it then stays on the same page with the fields all
> > > populated as if a error had happened.
> > >
> > > 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) .
> >
>
> I am Thinking of one use case.Lets say user wants to subscribe a remote
> album(e.g flicker).He adds a feedurl and clicks to subscribe button.Now we
> have two options.
>
> - One we immediately fetch the meta data from the feedurl(name,titile,
> location) etc and save it to jcr repository.When user wants to view the
> album we fetch remote album meta  data from our local JCR and display
> them.I
> think performance wise it beneficial but we have to sync our repo
> frequently


> - Another option is that we only save the feedurl to our jcr repository
> initially and only fetch the meta data when user actually wants to view the
> remote album.The benefit of this approach is that we do not need to
> frequently sync our jcr.
>
> Thoughts ?
>
>

Say I subscribe to album "A1" and view the album and logout. After I come
back (I think i must see the subscribed album in the gallery(at least the
name of the album), in a separate partition called subscribed albums).And
with each album name, we can provide a refresh (or view) button or link
which reload all current images of the particular album based on the feed
url .

+1 for option2 as we don't need frequent sync.

But as we want search option to find subscribed albums or images we can
still store meta data in the repository and in every refresh we can update
the node (album) meta data while album viewing part is done as previously
said.


>
> >
> > >
> > >
> > > I'll look in the backend part later on when I find more time :)
> > >
> > >
> > > --
> > > Luciano Resende
> > > http://people.apache.org/~lresende<
> http://people.apache.org/%7Elresende>
> > > http://twitter.com/lresende1975
> > > http://lresende.blogspot.com/
> > >
> >
> >
> >
> > --
> > sk
> >
> >
> > Thanks
> > /subash
> >
>
>
>
> --
> Avdhesh Yadav
> http://www.avdheshyadav.com
> http://twitter.com/yadavavdhesh
>



Regards
/subash

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Luciano Resende <lu...@gmail.com>.
On Mon, Oct 11, 2010 at 12:53 PM, Avdhesh Yadav <av...@avdheshyadav.com> wrote:
> On Tue, Oct 12, 2010 at 1:00 AM, Luciano Resende <lu...@gmail.com>wrote:
>
>> On Mon, Oct 11, 2010 at 12:17 PM, Avdhesh Yadav <av...@avdheshyadav.com>
>> wrote:
>> >
>> > I am Thinking of one use case.Lets say user wants to subscribe a remote
>> > album(e.g flicker).He adds a feedurl and clicks to subscribe button.Now
>> we
>> > have two options.
>> >
>> > - One we immediately fetch the meta data from the feedurl(name,titile,
>> > location) etc and save it to jcr repository.When user wants to view the
>> > album we fetch remote album meta  data from our local JCR and display
>> them.I
>> > think performance wise it beneficial but we have to sync our repo
>> > frequently.
>> >
>> > - Another option is that we only save the feedurl to our jcr repository
>> > initially and only fetch the meta data when user actually wants to view
>> the
>> > remote album.The benefit of this approach is that we do not need to
>> > frequently sync our jcr.
>> >
>> > Thoughts ?
>>
>> I'd say that we would want to let the user specify title, and the URL
>> of the remote album.
>>
>> As for storing stuff locally in our JCR repo and fetching it all the
>> time, we should have metadata stored locally to allow searching.
>>
>> As for how we go about approaching this, I'd recommend that we start
>> with retrieving it from the remote site and storing in a local cache
>> (e.g a map) inside of a @Scope("COMPOSITE") component, and then on a
>> second phase, we would add the full blow sync and test searching, etc.
>>
>> Thoughts ?
>>
>
> Yes its good idea to develop this functonality in small increments.+1
>
> I thinking of following data structure for the local cache.
>
> Map<String,List<Image> cache = new HashMap<String, List<image>();
> cache.put("title", remoteImages);
>
>

I need to look into the code again, particular with the recent
changes. But we might be able to do something like
Map<String, Album> cache ?



-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Avdhesh Yadav <av...@avdheshyadav.com>.
On Tue, Oct 12, 2010 at 1:00 AM, Luciano Resende <lu...@gmail.com>wrote:

> On Mon, Oct 11, 2010 at 12:17 PM, Avdhesh Yadav <av...@avdheshyadav.com>
> wrote:
> >
> > I am Thinking of one use case.Lets say user wants to subscribe a remote
> > album(e.g flicker).He adds a feedurl and clicks to subscribe button.Now
> we
> > have two options.
> >
> > - One we immediately fetch the meta data from the feedurl(name,titile,
> > location) etc and save it to jcr repository.When user wants to view the
> > album we fetch remote album meta  data from our local JCR and display
> them.I
> > think performance wise it beneficial but we have to sync our repo
> > frequently.
> >
> > - Another option is that we only save the feedurl to our jcr repository
> > initially and only fetch the meta data when user actually wants to view
> the
> > remote album.The benefit of this approach is that we do not need to
> > frequently sync our jcr.
> >
> > Thoughts ?
>
> I'd say that we would want to let the user specify title, and the URL
> of the remote album.
>
> As for storing stuff locally in our JCR repo and fetching it all the
> time, we should have metadata stored locally to allow searching.
>
> As for how we go about approaching this, I'd recommend that we start
> with retrieving it from the remote site and storing in a local cache
> (e.g a map) inside of a @Scope("COMPOSITE") component, and then on a
> second phase, we would add the full blow sync and test searching, etc.
>
> Thoughts ?
>

Yes its good idea to develop this functonality in small increments.+1

I thinking of following data structure for the local cache.

Map<String,List<Image> cache = new HashMap<String, List<image>();
cache.put("title", remoteImages);


> --
> Luciano Resende
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
Avdhesh Yadav
http://www.avdheshyadav.com
http://twitter.com/yadavavdhesh

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Luciano Resende <lu...@gmail.com>.
On Mon, Oct 11, 2010 at 12:17 PM, Avdhesh Yadav <av...@avdheshyadav.com> wrote:
>
> I am Thinking of one use case.Lets say user wants to subscribe a remote
> album(e.g flicker).He adds a feedurl and clicks to subscribe button.Now we
> have two options.
>
> - One we immediately fetch the meta data from the feedurl(name,titile,
> location) etc and save it to jcr repository.When user wants to view the
> album we fetch remote album meta  data from our local JCR and display them.I
> think performance wise it beneficial but we have to sync our repo
> frequently.
>
> - Another option is that we only save the feedurl to our jcr repository
> initially and only fetch the meta data when user actually wants to view the
> remote album.The benefit of this approach is that we do not need to
> frequently sync our jcr.
>
> Thoughts ?

I'd say that we would want to let the user specify title, and the URL
of the remote album.

As for storing stuff locally in our JCR repo and fetching it all the
time, we should have metadata stored locally to allow searching.

As for how we go about approaching this, I'd recommend that we start
with retrieving it from the remote site and storing in a local cache
(e.g a map) inside of a @Scope("COMPOSITE") component, and then on a
second phase, we would add the full blow sync and test searching, etc.

Thoughts ?

-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Avdhesh Yadav <av...@avdheshyadav.com>.
On Mon, Oct 11, 2010 at 11:05 PM, Subash Chaturanga <su...@gmail.com>wrote:

> On Mon, Oct 11, 2010 at 9:44 AM, Luciano Resende <luckbr1975@gmail.com
> >wrote:
>
> > On Sun, Oct 10, 2010 at 4:20 PM, Luciano Resende <lu...@gmail.com>
> > wrote:
> > > On Sun, Oct 10, 2010 at 12:03 PM, Subash Chaturanga <
> subashsdm@gmail.com>
> > wrote:
> > >> Hi all ,
> > >>
> > >> On Thu, Oct 7, 2010 at 1:47 PM, Avdhesh Yadav <av...@avdheshyadav.com>
> > wrote:
> > >>
> > >>> check this thread.
> > >>>
> >
> http://www.mail-archive.com/photark-dev@incubator.apache.org/msg00784.html
> > >>
> > >>
> > >> The first patch i submitted stores each subscribed albums in a java
> > >> collection .So based on that, for the next step, I went through the
> > above
> > >> discussion and what i feel was to store the meta data
> > >> (location,name,description) of images in a JCR node. As, a JCR
>  property
> > can
> > >> hold multiple values, I think we can store each album as a property
> and
> > we
> > >> can have two nodes for flicker and picasa . So that when we want to
> show
> > >> them in gallery we can retrieve those data and on the fly create
> albums
> > and
> > >> show them in the gallery. I would like to know, if anything wrong with
> > this
> > >> approach or is there any better way to do this?
> > >>
> > >>
> > >>
> > >>
> > >
> > > I'd recommend following the same node structure as the "local JCR"
> > > albums, which the exception that when it's a subscription, the actual
> > > image is stored remotely and we only have it's URL.
> > >
> >
> > I was taking a look at the latest patch, and I'd have couple
> > suggestions to the Subscription UI:
> >
> > 1) Today for the upload ui, a user can choose a "New Album" or select
> > an existing album. How about we just create a new entry "New Remote
> > Album" for the Picasa or Flickr albums, and then show required fields
> > like : type (Picasa, Flickr, or anything new we might have) and then
> > the URL, username and password ?
> >
> > 2) Both upload.html and upload.js seems to have specific fields to
> > picasa_xxxx. This will not scale when we add support for different
> > types of remote albums. We should just make generic fields like
> > album_remote_url, album_remote_user, etc and use those independent of
> > the type of remote album that is being added to the gallery
> >
> > 3) It seems that subscription is actually working, but the ui is
> > acting a little weird as it seems to have succeeded adding the new
> > remote album, but it then stays on the same page with the fields all
> > populated as if a error had happened.
> >
> > 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) .
>

I am Thinking of one use case.Lets say user wants to subscribe a remote
album(e.g flicker).He adds a feedurl and clicks to subscribe button.Now we
have two options.

- One we immediately fetch the meta data from the feedurl(name,titile,
location) etc and save it to jcr repository.When user wants to view the
album we fetch remote album meta  data from our local JCR and display them.I
think performance wise it beneficial but we have to sync our repo
frequently.

- Another option is that we only save the feedurl to our jcr repository
initially and only fetch the meta data when user actually wants to view the
remote album.The benefit of this approach is that we do not need to
frequently sync our jcr.

Thoughts ?


>
> >
> >
> > I'll look in the backend part later on when I find more time :)
> >
> >
> > --
> > Luciano Resende
> > http://people.apache.org/~lresende<http://people.apache.org/%7Elresende>
> > http://twitter.com/lresende1975
> > http://lresende.blogspot.com/
> >
>
>
>
> --
> sk
>
>
> Thanks
> /subash
>



-- 
Avdhesh Yadav
http://www.avdheshyadav.com
http://twitter.com/yadavavdhesh

Re: Subscription UI, was Re: [jira] Created: (PHOTARK-62) UI support to subscribe external albums

Posted by Subash Chaturanga <su...@gmail.com>.
On Mon, Oct 11, 2010 at 9:44 AM, Luciano Resende <lu...@gmail.com>wrote:

> On Sun, Oct 10, 2010 at 4:20 PM, Luciano Resende <lu...@gmail.com>
> wrote:
> > On Sun, Oct 10, 2010 at 12:03 PM, Subash Chaturanga <su...@gmail.com>
> wrote:
> >> Hi all ,
> >>
> >> On Thu, Oct 7, 2010 at 1:47 PM, Avdhesh Yadav <av...@avdheshyadav.com>
> wrote:
> >>
> >>> check this thread.
> >>>
> http://www.mail-archive.com/photark-dev@incubator.apache.org/msg00784.html
> >>
> >>
> >> The first patch i submitted stores each subscribed albums in a java
> >> collection .So based on that, for the next step, I went through the
> above
> >> discussion and what i feel was to store the meta data
> >> (location,name,description) of images in a JCR node. As, a JCR  property
> can
> >> hold multiple values, I think we can store each album as a property and
> we
> >> can have two nodes for flicker and picasa . So that when we want to show
> >> them in gallery we can retrieve those data and on the fly create albums
> and
> >> show them in the gallery. I would like to know, if anything wrong with
> this
> >> approach or is there any better way to do this?
> >>
> >>
> >>
> >>
> >
> > I'd recommend following the same node structure as the "local JCR"
> > albums, which the exception that when it's a subscription, the actual
> > image is stored remotely and we only have it's URL.
> >
>
> I was taking a look at the latest patch, and I'd have couple
> suggestions to the Subscription UI:
>
> 1) Today for the upload ui, a user can choose a "New Album" or select
> an existing album. How about we just create a new entry "New Remote
> Album" for the Picasa or Flickr albums, and then show required fields
> like : type (Picasa, Flickr, or anything new we might have) and then
> the URL, username and password ?
>
> 2) Both upload.html and upload.js seems to have specific fields to
> picasa_xxxx. This will not scale when we add support for different
> types of remote albums. We should just make generic fields like
> album_remote_url, album_remote_user, etc and use those independent of
> the type of remote album that is being added to the gallery
>
> 3) It seems that subscription is actually working, but the ui is
> acting a little weird as it seems to have succeeded adding the new
> remote album, but it then stays on the same page with the fields all
> populated as if a error had happened.
>
> 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) .

>
>
> I'll look in the backend part later on when I find more time :)
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>



-- 
sk


Thanks
/subash