« Back to blog
Viewed
times
Favorited 0 times
June 9, 2010
 

New version of Snapper available !

Hi all,

I just finished a new version of snapper.

Download link:

Screenshot:

Snapper-0

Recommandations / instructions:

- If you install the extension for the first time, you need to reload the page. Sorry, but thats just how the safari extension system works. You only have to do it once.
- When you want to make a screenshot, click on the small picture frame icon in the safari toolbar, somewhere between the back/forward buttons and the address bar.
- When the button is clicked, a black rectangle appears on the top right of the safari content. There, you can see a thumbnail of the screenshot which you can drag on your desktop. Close the orange button when you are finished.
- The toolbar icon is disabled if Safari shows an empty page or if the extension is currently showing a snapshot to be dragged away.

Limitations:

- Currently the safari extension system does not allow snapshots of the whole page, only the current viewport. I am looking into solutions, but no solution yet.
- Its still not possible to name the snapshot image, this is because of the way the snapshot system works in safari. Again, as soon as a solution presents itself, I will keep you all posted.

I would like to thank you all for your support and patience. Safari extensions are still very new so bear with us !

Kind regards,

Dave

Comments (2)

Jun 10, 2010
Kody said...
I'm curious - where does the extension initially save it? Is a cache folder created somewhere, is it allocated/removed in memory? I ask because after using the extension for a while, my Safari process has ballooned to over 1.5GB on my RAM. I'm using a MacBook Pro with 4GB of DDR3, and while Safari's process expanding to 500MB-900MB is typical (oddly), I was curious if this is a side effect of the extension or if there's a way to remove old web clippings?

Thanks for the extension, it's incredibly useful! I can't wait to see what you'll do with this in the future~

Jun 13, 2010
David Grevink said...
Hi there Kody,

The extension is solely based on Javascript APIs provided by Apple.

I'm looking into the memory leaks you are mentioning but preliminary tests seem to show that they might be related to how the extension system works in Safari internally.

I will update the plugin if I find a way to correct the problem myself.

Kind regards and thanks for your input !

Dave

Leave a comment...