Dolphins near the Seaside

About #isolate:

2008-01-08T04:41:00.001-08:00

I was looking how to properly use WATransaction decoration (#isolate:) to prevent the backbutton usage, and found this message from Ramon Leon in the Seaside mailing list:

#isolate: is used to wrap what is essentially #call: to several
components in succession. You could use isolate in a callback, if the
callback is calling another component to display, but not if it's just
setting instance variables.

The point is, all isolate does is expire any components created within
the block passed to it, when the execution of the block is complete.
Once execution has passed beyond the isolate block, the user cannot go
back to any component called from within the block.

Now I get it.

Dolphin is back

2008-01-07T03:31:00.000-08:00

Andy Bower, of Object-Arts, announced the last sunday:

For several years now, in a climate of free and open source development tools, it has been difficult for us to create and sell our products in a maner which is commercially viable. For this reason we have decided that it would be financially impossible for us to commit to major new developments of Dolphin Smalltalk into the future. What this means is that Dolphin will continue to support Win32 under both XP and Vista but we will not be porting the IDE to .NET or any other platform. We will still offer the Community Edition for free download and the Professional version can be purchased by those who have evaluated that the Win32 product meets their needs.

Which means that Dolphin is back, and Seaside still have future on it. I've been developing with Seaside since a couple of months, and the developing experience is far far better than any of the others Smalltalk dialects. And BTW, Seaside never crashed, nor killed the VM, as happened to me with VW in previous versions (I think this is fixed now).

2008 started great!

FAQ Proposal

2007-11-30T06:44:00.000-08:00

Q: When you know if you're working too much with Seaside?

A: When you want to "Toggle halos" on every website you visit. :-)

Benchmarks everywhere

2007-11-20T07:21:00.000-08:00

It seems that my benchmarking "initiative" caused some effects, and many vendors/frameworks are doing the test with the same tool.

AIDA/Web vs Seaside:
http://www.aidaweb.si/benchmarks/wapt-swazoo-20.html

Seaside on VisualWorks, Squeak, vs Ruby on Rails :
http://www.cincomsmalltalk.com/blog/blogView?showComments=true&printTitle=More_Seaside_Testing&entry=3372921925

My own tests (which will be replayed):
http://dolphinseaside.blogspot.com/2007/11/some-benchmarks.html

And the initial, and more exhaustive, Seaside on Gemstone benchmark:
http://gemstonesoup.wordpress.com/2007/10/19/scaling-seaside-with-gemstones/

Considering all of us are using the same tool I've choosen (WAPT), we should define a clear and unique test suite, upload it to a public place, and run it against the different implementations. The results published by AIDA and Cincom have a significant difference between them.

Anyway is important that we put "benchmarking" over the table.

See you in Smalltalks 2007.

Taking it easy

2007-11-16T14:37:00.000-08:00

I got the feeling that the latest post about the benchmarks caused some bad reactions. So just to feel less paranoid (I'm new on this thing of "blogging"), or just for the record I want to give some explanations about it:

I consider myself Smalltalker, it is: I want that the entire Smalltalk community to grow healthy.
I like Dolphin Smalltalk. In fact, I love Dolphin Smalltalk.
By no means I want to bias the numbers towards point #2.
It is, I'm not making any value judgement about the quality of any of the tested Smalltalk.
Just ran the same test against the different Seaside implementations (I'll replay this test against GLASS and VW 7.6 too)
The test has low value, because It doesn't represent a real usage, except if you have a plublic website running on Seaside, and get slashdotted.

Now I feel much better. Feeling that all are my friends again. Come with us, Smalltalks 2007 will be great.

Some benchmarks

2007-11-15T03:58:00.001-08:00

Yesterday I ran some benchmark tests against Seaside on Dolphin, Squeak and VW.

The test is basically a brute force conection initiation, against the basic Seaside Counter.

I won't do any analysis or conclusion yet, just some observations, however I'm publishing the results for you our own review.

All the test were ran by separate in the same machine, an Athlon64 X2 3600+, 1GB RAM, Windows XP Pro.
Simulating 20 concurrent users starting connections against the server, one after the other, to see how much load it can handle.

Dolphin (Swazoo 1.1.4):
http://emaringolo.users.dolphinmap.net/seaside/reports/20071114/SeasideDolphin.html

Dolphin stopped answering connections when they reached the 8000, however, during the test, the image (a workspace) was still responsive (slow, but usable). Once the test ended, the image was responsive again, having more than 8000 instances of WASession, invoking a garbage collect with all those sessions in memory (with all its continuations, i.e. processes), caused a failure, and Windows showed a message saying "Dolphin Smalltalk stop responding". Why it happens at that moment, is unknown to me.

Squeak (Kom 6.2):
http://emaringolo.users.dolphinmap.net/seaside/reports/20071114/SeasideSqueak.html

The result for Squeak are similar as Dolphin. Same number of instances (average), with the difference of no having "processes" for its continuations, during the test the workspace wasn't responsive as Dolphin's one, but you can evaluate some expressions, and with patience get the print-it or do-it. But passed the test without dying. Invoking a GC forced me to interrupt the VM, because the GC blocked it.

VW (WebToolkit):
http://emaringolo.users.dolphinmap.net/seaside/reports/20071114/SeasideVW.html

VW started answer a large number of hit per second, which was as expected considering its fast VM, but started to halve its performance, and in less than 2 minutes started to show "Process Emergency" (or something similar I don't remember exactly). During the test all the windows were a dark grey rectangle, so no interaction can be done. After two minutes of test, the VM showed a out of memory message, and died abruptly.

Back to the future

2007-11-14T09:39:00.001-08:00

I've just downgraded my workstation from Vista Business to XP Professional.

Vista is pretty, but with this hardware is slow (Athlon 64 X2 3600+, 1GiB RAM, 160 GB HDD SATA2). With XP, this computer is like a Bugatti Veyron

And again...

2007-11-13T07:47:00.000-08:00

New release, which uses the newer version of IDB DateAndTime and Duration and fixes a wrong link for the icons.

Download it from:
http://emaringolo.users.dolphinmap.net/seaside/downloads/Seaside-2.8a1-eam.528_e.zip

Seaside 2.8 for Dolphin candidate release

2007-11-12T08:12:00.000-08:00

I've just released a candidate "stable" version of Seaside 2.8 for Dolphin Smalltalk, it supports file uploads and multiple options forms elements. I had to fix some methods of Swazoo to get rid of the dead processes too.

From now on I'll be dedicating less time to the port itself and more time to build software based on it for my company.

However I'll be fixing bugs as required, and I will follow the development of the 2.9 version of Seaside, codename STABILO, which will be more modular, and easier to port.

The download link is:
http://emaringolo.users.dolphinmap.net/seaside/downloads/Seaside-2.8a1-eam.528_d.zip

The installations instructions are the same as with the previous release.

Enjoy!

Keep it candy

2007-11-11T13:30:00.001-08:00

Spurred by the latest addition to the Dolphin autocompleter done by Udo Schneider, I added some icons to the Seaside and Scriptaculous classes, this way will be easier to identify them (apart from its class prefix), and it will be nicer, as Dolphin itself is (well... Dolphin isn't nicer, it's definitely the nicest).

I'll publish this modification in the next release.

Remember remember...

2007-11-09T18:29:00.000-08:00

...the 9th of November.

If you want a probably stable version of Seaside for Dolphin, do this little two modifications to the recently released version:

Replace HTTPConnection>>#close by this:


close
 self stream close.
 self server removeConnection: self.
 self loop notNil ifTrue: [self loop terminate].
 loop := nil

And replace HTTPConnection>>#interact by this:


interact
 "longer description is below method"
 | interactionBlock |
 interactionBlock := [
  [ [ true ] whileTrue: [ self getAndDispatchMessages. Processor yield ] ]
   on: SpError
   do: [:ex |  self close ]
   on: ProcessTermination
   do: [:ex | self loop: nil ]].
 self server isMultiThreading
  ifTrue: [self loop: (interactionBlock forkAt: Processor userBackgroundPriority)]
  ifFalse: [interactionBlock value].
 ^self

And all the zombie processes won't be there anymore. Isn't that what you was after? :-)

Being almost midnight it remembers me a fantastic goal in extended time.

Thanks to Sebastián Calvo (aka Gallego) by working together with me to solve this until this late, after all he is talented to solve this kind of stuff. Hat tip gallego!

Elementary, my dear Watson

2007-11-09T16:23:00.000-08:00

One more reason to keep using Windows XP (or leave Vista).

Some minutes ago I installed the recently released version in a notebook to keep working (or playing) during the weekend. After installation I accessed the examples, and to my own surprise, it runs much more fast! But not 2x or 3x, it's about one order of magnitude.

I thought it was because of the CPU being Intel (Thinkpad T60, Centrino Duo), because my computer at work is an Athlon64 X2 3600+, so I tested it in my home computer (Athlon64 X2 4000+), but it still was 10 times faster than my computer at work.

And guess what... both the Thinkpad and my home computer have XP Pro, whereas my workstation has Vista Business.

Elementary.

Seaside 2.8a1-eam.528 preview version

2007-11-09T12:19:00.000-08:00

For those waiting to test the latest version of Seaside on Dolphin, it can be downloaded from http://emaringolo.users.dolphinmap.net/seaside/downloads/Seaside-2.8a1-eam.528_c.zip.

The ZIP includes the packages (.pac) and the project editions exports for those using STS (recommended).

Install order using PAC files (.stp):

IDB\IDB Duration.pac
IDB\IDB DateAndTime.pac
SPort\SPort Tests.pac (will load SPort.pac)
Swazoo\Swazoo-Tests.pac (will load all Swazoo Pacs)
Seaside\Seaside-Dolphin.pac
Seaside\Seaside-Browser.pac
Seaside\Seaside.pac
Seaside\Seaside-Swazoo.pac
Seaside\Scriptaculous.pac

Install order using STS project editions files
(first import all the project editions into the repository):

Seaside Prereqs 0.002
SPort 0.5
Swazoo 1.1.4 R3
Seaside 2.8a1-eam.528 c

Starting an example site:

In order to start an example site, open the 'example.st' in the Seaside folder, then point to any of the following:

It's not ready for production, because it still leaves dangling processes around until the handlers are cleared. I must fix it, so if nobody does it first, I'll will. However it can be used for development (we will), so I'll be releasing small fixes from now on. Feel free to add comments here, or send suggestions, bug reports, fixes or flames by email to eMaringolo at gmail dot com.

Regards,

EDIT: Fixed the Scriptaculous link (thanks JSC)

Less is more, but not this time

2007-11-09T10:46:00.000-08:00

I made a mistake when I removed the message send metioned in
my previous post, so we are one step back. However, I'll be releasing a beta version today.

Less is more

2007-11-06T16:24:00.000-08:00

A stated in other Smalltalk blog, less is more. And that was the case with the suspended processes left when running Seaside on Dolphin, to fix it I had to "remove" code, not to add.

Removing one method send in Continuation>>#value:, everything started to work as expected.

The only thing remaining is the reference to some dead processes of Swazoo (HTTPConnection>>#interact) by some handlers of Seaside, once done, Seaside on Dolphin will rock!

Benchmarking

2007-11-06T11:50:00.000-08:00

I've been running some benchmarks against Seaside on Dolphin.

I must say it runs very well, with an good page/sec rate for business apps. Anyway it can't handle being "slashdotted".

However, there is a severe problem with something leaving dangling processes in suspended or dead state, which collapses the image after 4 minutes of brute requests (above 8000 requests one after the other), generating a similar number of processes (think of it, 8000 processes!!!!).

Something smells near the Continuation implementation. Once solved the request rate should rise.

I'll publish the graphs and results when I learn how to do it. :-)

Even with that "little" problem, the performance is a little better than the Squeak implementation (15% faster).

More coming soon...

Twittering

2007-11-02T08:11:00.000-07:00

Scriptaculous is on its way too...

Evergreen Terrace

2007-11-01T14:08:00.001-07:00

When all is green, I feel happy:

Doesn't it look pretty?

And of course, it's running on Dolphin X6.

The status is:

All the tests passes

The Unicode tests were omited because Dolphin doesn't support unicode

Some processes are left suspended, when I clear the handlers they leave, something is referencing them
I learnt how to use Monticello (nice tool)
The web based browser doesn't work, I'll will try to fix it, however it's not prioritary.

This looks promising...

Third time's charm

2007-10-31T18:00:00.000-07:00

This is the third time I begin to port Seaside. First was 2.6, then 2.7 and now 2.8.
And this time I'm not doing it in my spare time at home, now I'm doing it here where I work, at InfOil, in an effort to "webify" our new platform which as always in our company is developed with Smalltalk. So now I'm suposed to be able to work on this during my working hours, and then cooldown at home.

By now I can say that this time Seaside is better factored, probably because of the GemStone port and because project maturity itself.

So far is going well, with only 7 failed test over 171.

Let's see if this time a dolphin can be sought near the Seaside.

POST

2007-10-31T06:11:00.000-07:00

Power On Self Test running... [OK]

Development will resume soon...

Seaside 2.7 on its way

2007-02-11T17:45:00.000-08:00

Even with my "getting worst every day" garbled screen problem, I could make Seaside 2.7a-169mb version work mostly stable on the computer. I'll try to finish it as soon as it's possible. The sushi store, halos, and some other stuff is working.

Below is a screenshot of Sushi Store running on seaside 2.7, over Dolphin Smalltalk X6.
And BTW, it runs fast!

Getting back

2007-02-09T15:35:00.000-08:00

I'm trying to get back to the work on maintaining the Dolphin port of Seaside. Stay tuned.

Sport + Swazoo 1.1.4 + Seaside 2.6 for Dolphin X6

2006-07-19T06:16:00.000-07:00

Sport, Swazoo 1.1.4 and Seaside 2.6 are available for download. You can download them from my DolphinMap homepage.
Feel free to report errors, send suggestions or postal cards to my mailbox.
Also, you can report them to:

General Dolphin questions at news://comp.lang.smalltalk.dolphin
Swazoo and Sport swazoo-devel at lists.sourceforge.net
Seaside stuff to Seaside Mailing List seaside at lists.squeakfoundation.org

Enjoy!

Sport and Swazoo released

2006-07-17T18:37:00.000-07:00

I've completed the port of Swazoo 1.1.4 and Sport.
I don't have a hosting yet, so if you want them, drop me a request on eMaringolo at gmail dot com.

I have it available in STS Project Export XML format (.pex), and good old .pac packages.

To load the .pac's you must first load Sport, and then Swazoo.
First load Sport in this order:

VW Filenames.pac
MD5.pac
Sport
Sport tests

Then load Swazoo in this order:

Swazoo-Compatibility.pac
Swazoo-Headers.pac
Swazoo-Server.pac
Swazoo-Resources.pac
Swazoo-Examples.pac
Swazoo-Tests.pac

Then you can test it evaluating:

site := Site new name: 'swazoo'.
site host: 'localhost' ip: '127.0.0.1' port: 8888.
site addResource: (comp := CompositeResource uriPattern: '/').
comp addResource: (HelloWorldResource uriPattern: 'hello').
SwazooServer singleton addSite: site.
site start.

Then to stop your server do:

site stop

For more information visit Swazoo.org, or Swazoo Sourceforge homepage.

More to follow...

The three S's

2006-07-14T09:04:00.000-07:00

I'm packaging and testing an "usable" (I can't tell if it's stable) release for Dolphin of:

Sport
Swazoo 1.1.4 latest release ported from the main codestream on Cincom Public Repository, based on the Sport compatbility layer
Seaside (adapted from Avi Bryant's port, and with better integration with Swazoo).

Stay tuned, my intention is to release during this weekend.

Dolphin Seaside Community

2006-06-15T08:15:00.000-07:00

The Dolphin community of Seaside users/contributors is growing slowly, today Martin Rubi published his port of Scriptaculous for Seaside.

I've done nothing but the smallest changes to make the
scriptaculous examples to work in Dolphin. I don't intend this to be a real
port, consider it more like something to play with.
Anyway, in case someone is interested, here it is.
http://mrubi.users.dolphinmap.net/Scriptaculous.rar

Gracias Martin!

Dolphin Port Available

2006-05-26T05:32:00.000-07:00

Good news in this shore: Avi Bryant announced an early port of Seaside for Dolphin Smalltalk X6.
One note to have in mind is:

This is a preliminary port - although most things seem to work, testing has been minimal and there are doubtless many problems remaining. Please write about your experiences on the list and I'll do my best to fix things.

You can download this port and see an extended detail of what's working and what not in the Seaside Dolphin download page.

This weekend we'll have something to play with. :)

Enjoy Dolphin and Seaside.

Keeping the buzz loud

2006-05-18T05:47:00.000-07:00

By now, we only have buzzing and gossip, but here is what Avi Bryant said about the status of the Dolphin port of Seaside:

I haven't forgotten, I'm just slightly behind schedule (so what else is new... sigh). But there's nothing like a public commitment to make things happen, so: I promise that I will release some useful version of Seaside on Dolphin by this time next week - on or before Thursday, May 25.

Go Avi!

Seems like May 25 will have another celebration cause.
Here, we already have one: May revolution (spanish)

Object Arts will pay the development

2006-03-23T04:25:00.000-08:00

It's confirmed, Avi Bryant will do the Dolphin port of Seaside.
According to his own words, he is "aiming to have an initial port done by May", so we have to wait until then, and see what "initial" means, and what will be the strategy choosen to continue its maintenance.

However, once again, thanks Object Arts for supporting and investing in the improvement of Dolphin Smalltalk , and thanks Avi Bryant / Smalltought for accepting the work.

We have to sit and wait. We can start a bonfire.

Avi Bryant will do the port?

2006-03-16T17:35:00.000-08:00

Considering a post on comp.lang.smalltalk.dolphin, does exists the possibility that OA pays to Avi Bryant to do the Dolphin port of Seaside.
That would be great, considering that, for those who don't know, the original developer would do the port.
Who will maintain the port? Nobody cares by now :-)

New tides

2006-03-15T05:20:00.000-08:00

There has been some new intereset in having Seaside in Dolphin, so we can try to arrange developers and resources to complete the port once and forever (and maintain it forever also ;-) ).

What we need:

A Wiki or some similar collaboration space

A communication medium

A way of automating the conversion of monticello packages to Dolphin PACs

Check the if the Dolphin VM supports everything needed to run the continuations of Seaside2

Developers :-) (few but with criteria)

Notes about reqs above:

This weblog isn't enough, IMHO

May be comp.lang.smalltalk.dolphin

This way we can add third party add ons to Seaside without having to rewrite a possible exporter from Squeak

Continuations was implemented having Seaside1 in mind, I have some problems in the current port, returning to expired or across processes, this is the big shadow that should be cleared, if possible implementing a regression test.

So feel free to post comments here if you want to collaborate with resources or as developer.

Keep the Dolphin swimming.

Packaging the unpackageable...

2005-11-23T18:21:00.000-08:00

Until now I was working with 4 or 5 packages, containing all the seaside stuff, the seaside loose, tests, and the squeak compatibility. Last night I was trying to packagize the classes and loose methods of Seaside.

My first approach was to use a separate package for each of the seaside class categories (which are pretty well categorized). So I could write an exporter in Squeak, that could export each category into a separate package. That way I would maintain the core, the widgets, and other classes separately. Well... I've failed. The coupling between the packages was so big, that I couldn't save any package, or just a few.

So I rolled back, put almost all into a big bag package named "Seaside Common", and left out the packages which don't cause cyclic dependencies.

The packages not in "Seaside Common" are, whose includes classes corresponding to the squeak class category:

Seaside Configuration
Seaside Continuations
Seaside Examples Test
Seaside HTTP
Seaside Libraries
Seaside Utilities
Seaside Canvas (includes also the Canvas Tags)

I don't know if it's possible to decouple things, I would like to have the widgets and all which is not really core in other packages. Then everything else is convenience (which will be installed as soon is proven that are convenient :-).

However, it's still active. And so I am.

Images working

2005-11-18T18:04:00.000-08:00

I'm back with news (good I think).

All the images stuff is working!
Thanks to Object Arts, and all the people who did the GDI+ implementation for Dolphin (SW, CU, LS, DA), it's extremely full featured and very Smalltalk.

As usual with a good Smalltalk, I searched through the class library and found exactly what I needed. It happens that GdiplusImage implements a method named #asByteArray: , which expects the MIME type string (i.e. 'image/png'), using that for the encoding, plus four or five methods, it began to work. Without considering the side effect of polymorphism/dynamic binding, because all the Seaside (and Squeak) expects Forms as it base for all the image/pictures working, I use Gdiplus images and both understand a minimum common protocol, including #width, #height, etc.

However, it's working!.
I've found some other (worst?) problems, but all will be fixed, in their time.

I'll keep walking on the seaside, until the sun falls...

Uploads working

2005-11-17T09:46:00.000-08:00

The uploads are working.
WAFile expected a sequenced stream as it's contents.
Once done that, and implemented #asMIMEDocument in SequencedStream it began to work.

Wohoo! few things remains...

Seaside tides report

2005-11-16T10:27:00.000-08:00

Well, this intends to be a report of how it's going on.

By now this is the status of the functionality available, which were
tested using the alltests application:

Things OK:

Input
Html
Exception
Transaction
Parent
Task
Cookies
Callbacks
Canvas
Home
Cache
Submit

Things that are half-working:

- Error, this trows the warning and the error, but I can't debug the
error. I get a "Cannot return a WAWalkback to expired context or
across Processes."

- Live - It live updates how it likes, and whatever it likes. It is,
it updates but refreshing the whole page. Or doesn't updates et all.
Michel Bany said that this behavior occured to him in VW, and in the
new SeasideAsync package it is solved, so once I get things done
with the rest, I'll move ahead with it.

- Upload, It's uploading, but I get a blind DNU that I will track
later. Last night I found that the HTTPPost didn't build the part's
properly, ommiting the filename in the PostDatum which may require it.

- Encoding, some characters are missing from the map, so it isn't
working just because of laziness.

- Path, It shows aWACounter, so I guess something isn't working
properly.

Things not ported yet:

Images
Default form

I'll have fun work porting the image/form stuff, I'll try to do it
using the available GDI+ functionality (if something already exists).

ToDo

- Once the most important things begins to work, I'll refactor and
"repackage" all the seaside classes.

- Then prepare everything and build an exporter from Squeak, which
exports what I want, in Dolphin package format. And try to keep an
up to date version of the port.

- Start to "dolphinize" the Seaside port, it is, add a Seaside Flipper inspector, implement some command query stuff. And some other crazy things I have in my head.

I know forgot a lot of things, I'll try to post here daily, so I forget less.

Once again, forgive my english grammar, I'm far from being a english speaker/writer.

Here we go

2005-11-15T04:29:00.000-08:00

Hi, this is the first post in this weblog. The intention of the weblog is to have a progress log of how is going the port of Seaside for Dolphin Smalltalk X6. Let's walk on the seaside...