Holger Hans Peter Freyther's blog

In the previous post I briefly mentioned the new feature of the PackageLoader that went into the development version of GNU Smalltalk. Today I am going show a usage of it.

GNU Smalltalk has a database abstraction called DBI and multiple backends (MySQL, SQLite and PostgreSQL). In general I am using the SQLite backend to develop my application and depending on the users (e.g. do I need concurrent access) I will move to PostgreSQL. When moving my new application to PostgreSQL the import of data failed and this was due some issues with the conversion of Smalltalk types to PostgreSQL.

GNU Smalltalk has the concept of packages for a long time. By default the gst-package application will read an XML file and then create a ZIP archive. This package format is called a Star archive in GNU Smalltalk.

When developing it is easier to just load the package from the filesystem and this is why we now have the above PackageLoader>>#loadPackageFromFile:.

I am using Iliad for the configuration of my GSM Basestation (another blog entry will follow) and the response time has not been that great when showing a lightbox (e.g. the one from todolist example). I wanted to see where Iliad is spending the time and potentially improve the performance of either GNU Smalltalk or Iliad.

In the last two years I have developed some Smalltalk packages that help me with (mobile) communication related tasks and I began making them available for Pharo as well. I'm using the gst-convert utility to do the conversion and the goal is to have this work as automatically as possible.

OsmoLogging is another logging framework modeled after the framework we developed for C. Besides having multiple backends (Transcript, syslog) and log levels there are some unique features.

Once up on a time I was sitting in a cold hall at the Barcelona exhibition ground, a power outage has taken down several DVB-H platforms (racks consisting of servers, streamers, RF equipment...) and once power was restored red LEDs were blinking, systems not coming up automatically, hordes of engineers trying to boot the right kernel, trying to remember the multicast routes they had typed in by hand, chaos, hectic. It was interesting to witness that as we could lay back, continue with our work, as our platform was configured to come up automatically and it did.