Tag: Seaside

Lately I found the reason for an annoying bug in my Seaside Application in VA Smalltalk. It is once again related to encoding/decoding of Ajax request parameters. Once again I've been bitten by the fact that VAST is not unicode-ready yet (well, we've been waiting for unicodesupport in VAST for more than 4 years now, … Continue reading VA Smalltalk, Seaside, Ajax and … unicode!

Share this:

Like this:

Sometimes there are things that sound easy in the first place and then take a lot of time trying, yahooing and stackoverflowing etc. Lots of mosaic pieces are found on each iteration of the famous search-try-fail cycle. This is one of these. So what do we have? I wanted to add a double click handler … Continue reading Seaside: click a link using jQuery

Like this:

Well, a developer's day is full of victories and waterloos. So I've had my developer's day today. After I had discussed my Server startup problems related to ports already in use, Marten came up with an explanation for VAST's behavior on the VAST Support Group: The reason for this behaviour is located in the method: … Continue reading The WASstServerAdaptor story and its (preliminary) end

Like this:

There are probably a few questions that you may ask about this problem I just posted about. And I try to answer them here so you may understand better why I ask for an exception (or at least a Warning): Why don't you simply make sure the image is only running once on the server? … Continue reading More on WASstServerAdaptor and used ports

Like this:

[Update: Please be sure tor read this post as well if you're interested in more details on this subject and this one if you want to see what my solution finally looks like] This is a little lesson I learned with my VAST-based Seaside Application on a headless Linux Server that is probably not really … Continue reading Starting WASstServerAdaptor and handling used ports