Oh, and put the note about the API key in the /readme file ...

A thought regarding the placement of the API key, longer term we want to make a "modules configuration" interface within the CMS, so that users of the CMS are able to "enable flicker integration", then be prompted where to go to get the API key, and given a box to fill it in.

Having an interface for the management of modules also opens up a number of other possibilities, such as the ability to view all available SilverStripe modules (as published via a web service from the main SilverStripe website), and having a "one click, download and install" or even simply comparing the version numbers of the modules already installed/enabled with what else is available.

Tim/Lakshan... good idea. Sam... perhaps this is something for consideration either with 2.1 or the subsequent release.

NB. Will Scott has started on this in terms of putting a login area in the CMS, which is similar (i.e. its not hardcoded in a config file);

http://www.willscott.name/images/6.png

I like the fact it asks for the information in-situ, rather than in some far off galaxy called "configuration". Seems like the API key could be asked up-front, and then accessed for revision later in a sensible (but as yet, undefined, place)

Yeah, that would be a great feature to implement. I think we could more genralized interface on CMS as "Add-on Management", which could be used to install, update and configure various modules as well as themes.

Another thing I would like to get to your focus is about the Wigets (See the footer of www.web2media.net/sstheme/home/, for an example). Currently one would need to place the necessary code inside a controller to appear in the pages. Should we have the option to insert widgets via the CMS ?

I think we should have a right balance between features added to CMS (not to overload it) while having extensibility via the framework.

Hey Lakshan, I like your work and use the module now on my site. ;)
Ok, the next sentences are only experiences which I want to share.

Offline I hade no problems with the “Flickr Image Gallery” - module and everything worked fine. But online at my web-server it was not working and I always get an error.

„Error. The website server has not been able to respond to your request.“

After some time of debugging I recognized that the Flickr request was send with a “&” as separator. I fixed it by configuring the php function:

“http_build_query($params, '', '&');” (restfulService.php line 22)

Now it runs. : )
http://www.5oc.org/flickr-pics/

I also have a feature request for the lightbox div. Is it possible to add the “last/next picture” functionality? This would really be great.

Cheers 5oc! Nice to see a real life implementation of Flickr Gallery :)

Fixed the http_build_query issue and it'll appear in the daily builds. Thanks for your contribution.

About your request on lightbox's prev/next links, you could do a small change in FlickrGallery.ss;
in line 15 (inside FlickrPhotos.PhotoItems control) change the "rel" attribute from "lightbox" to something like "lightbox[group]".

[html]
<a href="http://farm1.static.flickr.com/{$image_path}.jpg" rel="lightbox[group]" title="{$title}">
[/html]

Hope this helps...

Lakshan, sounds like a good idea to do the next/prev thing in lightbox for the dailybuilds too. If you remember to put very clear SVN commit messages in, then when we release 0.2 we'll be able to easily provide a changelog...

cool thx. this was a easy change ;)