Work is continuing on adding support for image uploads with BloGTK. In addition to the Picasa support mentioned earlier, work has begun on native uploads for blogging systems that support the metaWeblog.newMediaObject method. So far, the preliminary code is working well, although there’s a lot of work to be done to make sure it works right.

The next version (tentatively 2.1) will also hopefully be much better with error handling. Right now, when something throws an error, it’s not easy to diagnose just what happened. The next version should do better, not only giving you a better warning of errors, but also creating an error log that can be used to diagnose problems.

BloGTK is continuing to evolve, and I’m getting more and more assistance in making it better. Again, thank you to everyone who has contributed code and bug reports and feature suggestions. Every little bit helps.

Happy Thanksgiving to those BloGTK users in the US of A!

BloGTK 2.0 is steadily being refined, so if you’ve installed from the PPA you’ll get some crucial bug fixes next time you update your system. If you’ve installed from the tarball, there’s an updated download you can install that fixes some critical bugs in Fedora and other distributions.

There’s also some very exciting stuff that’s coming down the road for the next version of BloGTK 2.0. Thanks to a new BloGTK contributor, there’s a patch out there that adds support for Picasa uploads right from BloGTK. Just insert a local image on your computer and hit the upload version, and the new patch will automatically upload your images to Picasa, change the links over, and post your blog entry. It’s a completely seamless experience.

Image uploading is just one feature planned for the future of BloGTK. There are other great new features coming that will make BloGTK even better. Keep checking back here for more news as development pushes forward.

<professor>Good news, everybody!</professor>

It appears that the infamous segfault bug in Karmic has been vanquished, and BloGTK 2.0 no longer tends to fall down and go boom when editing posts. Apparently the WebKit view does NOT want to die, and will decide to take down the entire app if you try. This behavior is more than a little strange, but thankfully there’s a workaround that appears to kill the bug.

The trunk branch on Launchpad has the fix. Hopefully this will fix some other bugs on other platforms.

At this stage, once the fix is confirmed not to cause massive breakage, there will be a point release (2.0.1) with the fix.

From here on out, the next step will be squashing additional bugs, making sure that i18n will work out, and then planning for some new features.

As always, please keep sending bug reports and ideas my way.

Development on BloGTK 2.0 is continuing, with a formal release getting closer and closer. Here’s what’s been done lately:

• The MetaWeblog API routines have been patched to allow for better compatibility with b2evolution.
• Coding on offline editing has been started.
• The beginnings of internationalization (i18n) support have been added. BloGTK 1.x was not build with internationalization in mind. BloGTK 2.0 will be much easier to translate into other languages.
• The file structure for the app has changed for packaging. It is now possible to install BloGTK into the system. Packages for Ubuntu can now be built from the source.

However, there are a few things that need to be done:

• There are several bugs with BloGTK in Ubuntu 9.10 “Karmic”. For example, there are some visual bugs with the progress indicator in the settings dialog and the editor preview system tends to segfault.
• Offline post editing support needs to be finished. BloGTK 2.0 will not have the most robust offline editing features, but I hope to improve on them in subsequent releases.
• Adding full support for the old Blogger API as a fallback. (Although this may be left out—is there really a need for supporting this depricated API?)

The biggest task is ironing out the remaining bugs. BloGTK 1.x was somewhat flaky. BloGTK 2.0 should be much more stable. While it is inevitable that bugs will crop up, BloGTK 2.0 has been more heavily tested than its predecessor.

As always, the source code can be downloaded from Launchpad. Keep those bug reports coming, and with luck, there will be a release soon.

A few bits and pieces from the BloGTK front.

A new Ubuntu package for the old BloGTK 1.1 codebase has been released. This packages fixes a major bug with Python 2.6 and is recommended for all. For details, see the official release message. Thanks to Ralph Taylor for the fix.

Development on BloGTK 2.0 has lulled a little bit this summer, but is now picking back up. The focus right now is on squashing bugs rather than adding new features. Once the system is ready, the code will be moved on to the packaging phase – turning all the code from a bunch of code in one directory to something that can be installed and packaged.

Again, keep on filing bug reports and/or playing around with the source code for BloGTK. Already, there’s been one helpful contributor that’s helped with b2evolution compatibility. The more bug reports or patches, the better BloGTK will be.

Development on BloGTK 2.0 is nearing public release, but before BloGTK 2.0 is ready for primetime, it needs testers to put it through its paces. So, if you are feeling adventurous and want to give BloGTK a spin on your distro and blog, here is how to do it.

Getting Started

First of all, you will need the following packages for your system:

• bzr
• python (2.6.2 recommended. BloGTK is not Python 3 compatible.)
• python-gtk2
• python-gnome2
• python-gnome2-extras
• python-feedparser
• python-gdata
• python-webkit

On Ubuntu, you can add them all by going into a Terminal window and executing the command:

sudo apt-get install bzr python-gtk2 python-gnome2
python-gnome2-extras python-feedparser python-gdata python-webkit

On other distributions, follow the instructions for your particular distribution. (For RedHat-based systems, you should be able to replace “apt-get install” with “yum install”. Some distributions may have slightly different names for these packages (such as “python-webkitgtk” instead of “python-webkit”)

Once you have the required packages, you’ll be able to start testing BloGTK.

Getting the Code

The next step is to get the code for BloGTK from launchpad. Go to the directory where you want the BloGTK code to be located. Next, you will use Bazaar to get the actual code. In your Terminal window, execute the following command:

bzr branch lp:blogtk

Bazaar will then download the BloGTK code to a “blogtk” directory.

Right now, BloGTK is run from its own directory. When the program is ready, it will be installed for all users. For right now, you can install the development version without disturbing any older version of BloGTK on your system.

Using BloGTK

Go to the newly-created “blogtk” directory in your Terminal and execute the following command:

bin/blogtk2

BloGTK should open up and prompt you to configure your first blog account. From the configuration screen you should be able to add as many blog accounts as you wish. From there, you should be able to play with BloGTK to your heart’s content.

How to Create a Helpful Bug Report

The goal, of course, is to get as many people testing BloGTK as possible, and for them to find and help squash as many bugs as possible. To do that, I need bug reports. You can either submit a bug report through Launchpad or leave a bug report right here on the blog. (I would prefer bugs to be put into Launchpad, but will settle for blog comments.) Here are the things you should include to make your bug report helpful:

• Your Distribution (i.e. Ubuntu, Fedora, Mandriva, Arch, etc…)
• What Version of Your Distro? (i.e. Fedora 11, Ubuntu 9.04, etc…)
• What Blogging System? (i.e. WordPress 2.8, Movable Type 4, Blogger)
• What Error Did You Get? To find out what errors may have occurred, look both at any printed message in the Terminal window and any messages in the status bar of the application. If there’s an error message in the Terminal, try copying it into the bug report.
• What Were You Doing When You Got The Error? For instance, something like “I was editing a post on my Blogger blog in the editor, and then tried to insert a new blockquote by hitting the toolbar button, and then I got the error.” The more details, the better.

Again, the more bugs that can get squashed, the better. Also, if there’s a feature you want added in a future version, feel free to bring that up as well. However, at this point the focus of development will be on getting rid of bugs and fixing code before adding something new.

A hearty thank you in advance to everyone who helps in testing BloGTK. This program has taken a long time to develop, and I hope that the wait will have been worth it. Each bug report will help make BloGTK better.

UPDATE: Added python-gnome2-extras to the list of required packages.

UPDATE: Changed instructions to reflect the change to the folder structure in the newest revisions.

I’m proud to announce that BloGTK 2.0 will now be using WebKit as its rendering engine for HTML content. WebKit is an ultra-fast rendering engine used in Apple’s Safari browser as well as Google’s Chrome browser. With the very nice and easy-to-use pywebkitgtk bindings, adding WebKit to BloGTK took almost no time at all.

What does this mean for you? For one, WebKit is a much better HTML rendering library than the old GTK html viewer. It’s much faster, much nicer, and is generally easier to use.

The other possibility is adding WSIWYG editing to BloGTK. I’m not sure that will appear in 2.0, just so I can get 2.0 out the door quicker, but it’s something that is now possible to add and have it work right. It’s definitely part of the road map for the next release after 2.0.

Development is continuing on BloGTK 2.0, and the addition of WebKit makes BloGTK 2.0 are much better blog editing platform than before. It will open up a whole bunch of new avenues for working with HTML in the application. It’s the sort of thing that makes a humble app programmer very happy…

The latest release in the old BloGTK codebase is now being hosted on Launchpad. This release fixes many outstanding bugs from 1.1 and includes new code to bring it up to date with new versions of Python and PyGTK. This version will likely be the last update to the old BloGTK codebase, as 2.0 is back in development.

Some of the fixes include a modern file chooser for opening and saving files, and improved security for saved passwords.

BloGTK may be tested by getting the code from the BloGTK 1.2 page on Launchpad. Don’t forget to file bug reports for any bugs you see.

Hopefully, BloGTK will be finalized and available for packaging shortly.

UPDATE: Preliminary Ubuntu packages can be found here.

As you may have noticed, BloGTK 2.0 hasn’t been worked on in a while. That is due to the annoying thing called “real life” getting in the way.

Thankfully, I am hoping to have some free time for the first time in years, and may be able to work on BloGTK 2.0 again in the next few weeks.

In the meantime, I have moved this site to a new server, since Sourceforge and WordPress tend not to play too well together, especially since I couldn’t use Askimet for spam control. The good news is that this server will not have the problem with comments that existed before.

The current code for BloGTK will need some updates for newer versions of Python and libglade. For one, the current Glade file crashes the Glade editor. This is, needless to say, a major annoyance.

As always, I would appreciate help, especially help in the form of code patches and development help. Bug reports are nice, but patches that fix the bugs are even better.

More when development continues.

I apologize for the lack of updates in the last few months. My time, sadly, has been extremely limited, and work on BloGTK has gone to the sidelines.

If anyone would like to help complete BloGTK, please contact me at blogtk at jayreding.com. Or you can contribute code directly through Launchpad. My time will continue to be limited, and getting BloGTK out the door may take a long time at this rate.

Secondly, many have reported problems with commenting on the site. Apparently my anti-spam system was bouncing all comments instead of just spam. I’ve replaced it with another anti-spam plugin that should hopefully work better. If that fails, I will be moving the site to a new server that lets me use Askimet. I apologize for the bounced comments.

The goal for BloGTK is to get the remaining functionality working, get offline editing working correctly, and then concentrate primarily on bug fixes and the like. BloGTK already seems to work fairly well, and rather than keep adding features, I would like to develop BloGTK into a stable product that does a few things, and does them well.

Again, I apologize for the lack of updates. BloGTK is a hobby for me, and I don’t have much time these days. As always, any contributions that anyone has are always appreciated.