[Flashr] ResultsSet object

[Kelvin Luck]

Thanks for the responses guys :)

It looks like v0.5 will forget about backwards compatibility where it
makes the API less comprehensible. When I get a chance I'll look
through the code and see if there is any other areas where I can make
things clearer (one thing that jumps out at me is in the way lists of
tags are stored and passed - this seems to have caused confusion to a
lot of people...).

So - while I am at it is there any other places where people have
found Flashr confusing or any other improvements people would like to
see made?

Cheers,

Kelvin :)

On 1/11/06, Doug Marttila <dmarttila at gmail.com> wrote:
> I'm with Buck. Either way is easy enough for me, but, having two objects
> passed back is probably more confusing than it's worth in terms of backward
> compatability. My guess is there are going to be a lot more users going
> forward than there are now - so making it easier for them to understand is
> probably better.
>
> The following code should work fine for old apps - no matter what version of
> flashr..
>
> _flickr.photosSearch(searchO);
> _flickrResponseListener.onPhotosSearch = function(photos) {
> //new code here
>    if ( thePhotos.length==undefined){
>     photos=photos.photos
> }
> //end new code
> //do something here..}
>
> cheers
>
> doug
>
>
>
> On 1/10/06, Buck DeFore <bdefore at gmail.com> wrote:
> > My vote is go ahead with the ResultsSet changes irregardless of
> > backward compatibility. v.0.4 works well enough for those who might
> > not want to make the translation.
> >
> > I would have a bit of work converting Flappr in a few situations, but
> > in most areas I've already moved forward to the advantages of
> > ResultsSet.
> >
> > -Buck