Hi Lukas, Stef,

the Pier presentation and demo at the Bern Smalltalk Gathering was very  
impressive, thank you very much.

I've looked around for other such things and found only the (relatively  
new) buzzword "Codeless Development" (which google suggests to reword into  
"Wireless Development" ;) and a site with screen shots from a $$$ solution

  http://www.codeless.com/ProductOverview/cde/modeler/

which is interesting in its own but far behind what Pier/Magritte/Seaside  
promises: software (and other multimedia) composition :)

Thanks again, will install Pier on my test server (3.8) next week.

/Klaus

On Sat, 19 Nov 2005 14:04:17 +0100, stéphane ducasse  
<ducasse at iam.unibe.ch> wrote:

>>
>> Hi,
>>
>> I just published a first version of Pier (formerly called SmallWiki
>> 2) on SqueakMap, it is still an unofficial and incomplete version,
>> but it is closer to release than ever. Some things are still
>> missing or incomplete (such as a proper and fully functional
>> persistency, lots of tests, query engine is probably too
>> complex ...), but that will certainly improve!
>>
>> The package includes all the requirements to use Pier within a 3.8
>> image, probably it also works in 3.7 and 3.9. The installer will
>> ask in the beginning if Seaside should be installed, if you tell
>> so, it will automatically go through all the requirements and load
>> DynamicBindings, KomServices, KomHttpServer, Seaside and
>> Scriptaculous. Then Magritte will be loaded and finally Pier.
>>
>> Start Seaside using "WAKom startOn: 8888" and fire up a browser on
>> "http://localhost:8888/seaside/pier" to play with the system ...
>>
>> Now for those that have an existing image with code and a model
>> inside they want to keep. That is possible as well of course, but
>> it is not strait-forward: loading the new code from SqueakMap or
>> Monticello won't work, because I renamed package- and class-
>> prefixes. Copy the attached script to a workspace and follow the
>> instructions step-by-step and everything will magically work. If
>> you followed the naming conventions of SmallWiki 2 your code will
>> be automatically updated as well, you just need to publish the new
>> packages ;-)