Squeak - PhotoPublisher update
It's pretty common to publish your digital
photographs to a shared resource on the web. Apple's iPhoto , part of the
iLife suite included free with Macintosh computers, has had this feature for
years. I'm sure there are tools of a similar kind for other platforms. Flickr is, by far, the most recent
and popular public forum for sharing photos. And with the Flickr iPhoto plugin you
can easily use iPhoto to publish your digital photos to Flickr. So there are
many excellent ways to do this.
There is value in having this capability in Squeak. For one, it's multi-platform, and it becomes part of the personal computer experience when the user can review, modify and possibly extend the code as part of their Squeak environment. About 4 years ago I wrote PhotosPublisher for Squeak and made it available to the open source community. It had one specific purpose in mind. I wanted a way to share my photographs using a Squeak application as the tool. It's one of the popular enhancements on my Squeak enhancements page.
Last week a user wrote to me about a bug they encountered. And sure enough after I did a quick test I verified they were right. The truth is that I patched the bug that same morning and published an update. But, this always happens, once I was back in that code I decided to take on some of my previous ideas and add some more enhancements. Writing in Smalltalk is such a breeze.
This morning I published an update to PhotosPublisher. It has some minor bug fixes, lots of refactoring, and 2 visible new features. The first is that there is now a progress bar. This becomes essential when you are processing a fairly large library of photographs for publication. Squeak just takes a while to produce all of the required output files. It was fun to create a progress object as a model, incorporate that into the photo processing model, create a new progress morph - just for the publisher - and then incorporate that progress morph into the application GUI.
The second enhancement is that the HTML pages now use a cascaded style sheet. I'd been wanting to do that for a long time. The application creates a photos.css file which is then referenced by each generated page. With this technique the css file can be edited to change the style of the generated HTML pages without running the program again. The actual styles defined in the style sheet generated by the program are pretty lame. Nothing fancy in there. But the technical part is solved and that's all I really wanted to accomplish.
There is value in having this capability in Squeak. For one, it's multi-platform, and it becomes part of the personal computer experience when the user can review, modify and possibly extend the code as part of their Squeak environment. About 4 years ago I wrote PhotosPublisher for Squeak and made it available to the open source community. It had one specific purpose in mind. I wanted a way to share my photographs using a Squeak application as the tool. It's one of the popular enhancements on my Squeak enhancements page.
Last week a user wrote to me about a bug they encountered. And sure enough after I did a quick test I verified they were right. The truth is that I patched the bug that same morning and published an update. But, this always happens, once I was back in that code I decided to take on some of my previous ideas and add some more enhancements. Writing in Smalltalk is such a breeze.
This morning I published an update to PhotosPublisher. It has some minor bug fixes, lots of refactoring, and 2 visible new features. The first is that there is now a progress bar. This becomes essential when you are processing a fairly large library of photographs for publication. Squeak just takes a while to produce all of the required output files. It was fun to create a progress object as a model, incorporate that into the photo processing model, create a new progress morph - just for the publisher - and then incorporate that progress morph into the application GUI.
The second enhancement is that the HTML pages now use a cascaded style sheet. I'd been wanting to do that for a long time. The application creates a photos.css file which is then referenced by each generated page. With this technique the css file can be edited to change the style of the generated HTML pages without running the program again. The actual styles defined in the style sheet generated by the program are pretty lame. Nothing fancy in there. But the technical part is solved and that's all I really wanted to accomplish.
Posted: Sunday - March 27, 2005 at 07:48 AM |
Quick Links
Statistics
Total entries in this blog:
Total entries in this category:
Published On: Jan 19, 2008 09:36 PM
Total entries in this category:
Published On: Jan 19, 2008 09:36 PM