KIPI plugin for screenshots.debian.net

The screenshots.debian.net site is a public repository of screenshots taken from applications contained in the Debian GNU/Linux distribution and its derivates like Ubuntu.

It was created by Cristoph Haas to help people get an impression of what a certain software will look like on your desktop before you install it. Everybody can take screenshots and upload them through the upload form. So far there are about 3100 screenshots, which is actually a small number if you consider Debian Squeeze contains about 15000 source packages

After I hacked a bit on KSnapshot, the KDE snapshot tool, Sune asked me to add an export to screnshots.debian.net command. I had not thought of it before but that looked like a great idea, it would make the process or taking-screenshot, visit-upload-form, upload-each-screen so much easier!. So I started to develop my first KIPI plugin.

Here is the resulting Debian Screenshots plugin, as you would use it in KSnapshot:

Being a KIPI plugin, it is available not only from KSnapshot but also from Digikam, Gwenview and the other applications which support KIPI plugins:

Which makes me think: what about having a debshots (the software powering screenshots.debian.net) installation over at kde.org and have screenshots for all the KDE applications? What do you think? Promo team? Sysadmins? Setting it up shouldn’t be difficult: I’m no Python or Pylons expert (I’m more of a Ruby and Wt C++ guy :-) and got it running in a VM in an afternoon, even solving some SQLAlchemy 0.6 issues.

11 thoughts on “KIPI plugin for screenshots.debian.net

  1. Tomaz Canabrava

    Can you put the ‘export to’ as a side-menu? it’s really big now, and will tend to grow as more services will be added, in a small screen as a netbook, this is terrible ;)

    Reply
  2. Jacob Rask

    I just got the latest updates to KSnapshot and automatically sending a screenshot via email will be very useful to report bugs on bug tracking systems that support automatic bug reporting via email.

    Btw, as the list of KIPI Plugins grows, is there some place to manage them? I will never export to iPod for instance, and would rather not see the option in all menus.

    Reply
  3. pgquiles Post author

    @Tomaz, Jacob:
    Rather than adding a “export to” side menu, I’d like to have a “Plugins” control module in System Settings to enable/disable which module will be shown. As Jacob says, there are modules I will never use.

    Reply
  4. pgquiles Post author

    @Paul:
    When a language option is supported in s.d.n, I will add it to the plugin.

    As for Debian/Ubuntu, what is your proposal? “Export to Debian/Ubuntu Screenshots…”? or maybe display “Export to Debian Screenshots…” on Debian systems, “Export to Ubuntu Screenshots…” on Ubuntu? I’m not particularly happy with either option, and after all, the name of the site is screenshots.debian.net :-?

    Reply
  5. Martin Klapetek

    Hi,

    I was just thinking about writing a kipi-plugin for imagebin.ca. Since these two services are very simillar, what do you think about merging these two plugins in one? :) I’d take care of the imagebin.ca backend. If you’re interested, please let me know, also I can be found on Freenode IRC at #kde as mck182.

    Looking forward to hear from you! :)

    Marty

    Reply
  6. pgquiles Post author

    @Martin Klapetek:
    Actually imagebin.ca is more different than it seems from screenshots.debian.net:
    - No completion, thus no HTTP/JSON required
    - It requires keeping track of the response from the server to report back to the user the URL the image is available from

    The main thing in common is the multipart/form-data upload method + HTTP post (take a look at mpform.{h,cpp} and KIO::http_post or QNetworkAccessManager::post)

    I’d say it’d be easier to maintain an imagebin.ca plugin in its own.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>