How do you get back into your code after a week of doing something else?

• Start reading and put comments to what you don't understand.
• Add the categories you left out last week.

Both tasks involve a lot of typing, but that can be alleviated by using
features of your favorite text editor, vim in my case.

So here we go again ... this time using native Smalltalk code to describe package contents in a DRY way:

Eval [
  PackageBuilder new
    name: 'MyPackage';
    namespace: 'MyNamespace';
    prereq: 'Package1';
    prereq: 'Package2';
    ...
    testsBelow: 'Tests' matching: '*.st';
    filein: 'File1.st';
    filein: 'File2.st';
    ...
    buildXml
]

Hi again.

Now I want you to show, how to use the subclassed Iliad.Application class as a real dispatcher.

First, I will create a menu-class, that our web-pages has a seperate menu. And this menu is the same on every page, I created an extra class for that.

Hi!

The last one and a half week, I was playing with seaside, but now, Nicolas Petton introduced a new web-development framework which is called Iliad http://smalltalk.gnu.org/blog/nico/iliad-new-lightweight-web-framework-gnu-smalltalk that seems so interesting, that I decided to try it out for a new web application, which is currently in a planned status.

And because the documentation and howtos for Iliad is currently not widely accessible, I decided to write a bit about my expiriences.

And it's me again...

I'm currently using seaside to create a new WEB-site and I want you to show something of the configuration I use for the connection between seaside and apache, and for configuring seaside through some lines of code instead doing it through the configuration-dialog of seaside.

Apache is configured in my case as a reverse proxy and I needed some time, to figure out, how both should be configured, to let the seaside generated sites display well. (Even with the halos etc.)