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 thilanka geeganage <lg...@yahoo.com> on 2010/03/04 04:44:43 UTC

Re: Providing support for subscribing for different photo album streams (PHOTARK-18 and PHOTARK-19)

HI , 
     Thanks for providing these information. when I tried to upload files using http://localhost:8080/photark/admin/upload.htmlit doesn't show the name of previously created albums at the admin UI. Instead of that it shows [object Object] name at the select album drop down list. The number of names are equal in both cases. 
So what is this problem at the upload UI. Can you help me on that. 
Regards,Thilanka.
--- On Wed, 3/3/10, Luciano Resende <lu...@gmail.com> wrote:

From: Luciano Resende <lu...@gmail.com>
Subject: Providing support for subscribing for different photo album streams  (PHOTARK-18 and PHOTARK-19)
To: photark-dev@incubator.apache.org
Date: Wednesday, March 3, 2010, 8:50 AM

In our previous release, we had the ability to subscribe/reference to
external photos using Tuscany references (see composite below)
Although that works fine, the user experience is not so dynamic, as
the user needs to update the composite and then re-deploy the
application.

    <component name="AlbumAgregator">
        <implementation.java class="services.AlbumAgregator"/>
        <service name="Album">
            <t:binding.jsonrpc/>
           </service>
        <reference name="album" target="Album"/>
        <reference name="albumFeed">
           <t:binding.atom
uri="http://api.flickr.com/services/feeds/photoset.gne?set=72157601530865813&nsid=36437931@N00&lang=en-us"/>
        </reference>
    </component>


Going forward, I would like to have a more flexible user experience
here, where a user could go to the admin ui and create a new album of
type subscription and provided the right URL for the remote album. In
order to have this user experience working, we will need to provide
local album implementations that would provide similar functionality
offered by the Tuscany ATOM, GDATA bindings and would understand the
formats of the external feeds to extract album/image information from
it. This is the ideas I had when I created photark-18 and photark-19
jiras and I guess that, them combined (with possible other album
types) + plus support for admin ui could be a great GSoC project.




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



      

Re: Providing support for subscribing for different photo album streams (PHOTARK-18 and PHOTARK-19)

Posted by Avdhesh Yadav <av...@avdheshyadav.com>.
Hi,

I think you have older code..Please get the latest code and build and
redeploy again..

On Thu, Mar 4, 2010 at 10:14 AM, thilanka geeganage
<lg...@yahoo.com>wrote:

> HI ,
>      Thanks for providing these information. when I tried to upload files
> using http://localhost:8080/photark/admin/upload.htmlit doesn't show the
> name of previously created albums at the admin UI. Instead of that it shows
> [object Object] name at the select album drop down list. The number of names
> are equal in both cases.
> So what is this problem at the upload UI. Can you help me on that.
> Regards,Thilanka.
> --- On Wed, 3/3/10, Luciano Resende <lu...@gmail.com> wrote:
>
> From: Luciano Resende <lu...@gmail.com>
> Subject: Providing support for subscribing for different photo album
> streams  (PHOTARK-18 and PHOTARK-19)
> To: photark-dev@incubator.apache.org
> Date: Wednesday, March 3, 2010, 8:50 AM
>
> In our previous release, we had the ability to subscribe/reference to
> external photos using Tuscany references (see composite below)
> Although that works fine, the user experience is not so dynamic, as
> the user needs to update the composite and then re-deploy the
> application.
>
>     <component name="AlbumAgregator">
>         <implementation.java class="services.AlbumAgregator"/>
>         <service name="Album">
>             <t:binding.jsonrpc/>
>            </service>
>         <reference name="album" target="Album"/>
>         <reference name="albumFeed">
>            <t:binding.atom
> uri="
> http://api.flickr.com/services/feeds/photoset.gne?set=72157601530865813&nsid=36437931@N00&lang=en-us
> "/>
>         </reference>
>     </component>
>
>
> Going forward, I would like to have a more flexible user experience
> here, where a user could go to the admin ui and create a new album of
> type subscription and provided the right URL for the remote album. In
> order to have this user experience working, we will need to provide
> local album implementations that would provide similar functionality
> offered by the Tuscany ATOM, GDATA bindings and would understand the
> formats of the external feeds to extract album/image information from
> it. This is the ideas I had when I created photark-18 and photark-19
> jiras and I guess that, them combined (with possible other album
> types) + plus support for admin ui could be a great GSoC project.
>
>
>
>
> --
> 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