Get your own customer support community

About me

Location
Near Ghent, Belgium
Website
http://stoneship.org/

Recent activity

Subscribe to this feed
  • idea

    Denis Defreyne replied on August 20, 2009 19:39 to the idea "API for accessing snaps" in Realmac Software:

    Denis Defreyne
    I'm sorry, but using ember is not the solution I was looking for. It is a very cumbersome solution for two reasons:

    * It generates a lot of unnecessary traffic. All images have to be uploaded (and I have a lot of them), only to be downloaded again, after which they are uploaded once more to my own web host.

    * The API responses are forcefully prevented from being cached (distant-past Expires header, no-cache and no-store Cache-Control headers, ...). This means that API calls have to be made every time the site is built, unnecessarily creating delays and slowing down the entire process.

    What I am looking for is an API that is similar to ember, except offline and applicable to LittleSnapper.

    For completeness' sake: I would use this API in conjunction with nanoc, an offline web site publishing system that I wrote.
    Do you think this is one of the best points? Mark it as a good point
  • idea

    Denis Defreyne shared an idea in Realmac Software on August 19, 2009 19:11:

    Denis Defreyne
    API for accessing snaps
    I own LittleSnapper and I enjoy using it, but it lacks one major feature that I would really benefit from: an API for accessing images stored by LittleSnapper.

    For creating my web site, I use a system that loads data from various sources, and a LittleSnapper API would allow me to load images from LittleSnapper directly without having to export and then re-import them.

    The API would consist of at least three distinct methods: a method for getting a list of all items in the database, a method for getting the details (metadata) associated with item, and a method for getting the actual image data (as a stream or as a string containing the filename to where the image is stored).

    Alternatively, an export API in which the user can call an external program when exporting items (rather than using the built-in website publishing feature) would be beneficial, as well.