Begin forwarded message:
> Hi all,
> we just released an enhancement for Smallwiki 1 that supports
> external storage. This allows Smallwiki to run completely from
> disk, using the image basically as a cache only.
> Check out Thomas' (thf) posting at
> for more details and links.
The version used for the seaside website, Lukas sent the link for us
> and this version is currently used for squeak.org and considered as
> stable. So merging this stable version with the Chris port, because I
> noticed that there was several changes between both versions.
Ok I see
> Mmm what do you mean by works done by impara ? Where are this
> extensions ? Which repository ?
But it seems that we cannot read it.
I could not find the email where you offered the persistency backend
I'm working on smallwiki right now, and I'm trying to figure out what
has been done in the visual works version in order to gather as much
as possible and release a complete up-to-date version.
There is three main versions of smallwiki:
- the visual works one.
- the squeak port done by Chris Bukert
- the seaside stable image used for squeak.org
The task is merging them.
And merging is not easy !
For visual works:
The latest version is : 0.9.53 (29 September 2004) with the comment
"trying to understand publishing issue", the latest from lukas was
0.9.51 (24 June 2004) and changes from camp smalltalk was 0.9.52 (21
August 2004). I'm trying to figure out in which extent the public
store version in in sync with the scg one ! The VW smallwiki
development seems to have stop the last year, so it would be fun to
gather the work realized instead of getting it forever lost !
When I'm connected to the scg store, I see that the latest version was
18.104.22.168.2 by greevy (23 November 2004), but don't know if it
includes the changes from camp smalltalk. I tried the greevy version,
but found a lot of missing methods (prepareCookies for instance)
whereas the bulckaen version seems to be ok (17 September 2004). Is
the bulckaen version related to the latest public store release (29
September 2004) ? or the greevy version ? Someone knows ? This
archeological work will be valuable if people who participated could
give some information !
And is the seaside version based on the Chris port ? I guess so, but
it seems that there is a lot of changes, no ?
Anyway, I will try to figure out by testing and checking differences.
One of my favorite things to do is hit ctrl + shift + s in firefox, it'll disable the css and you can see immediately just how compliant any site is. A real css site will lose all layout and look totally plain, many sites still hold most of their layout so you can see css hasn't taken over just yet.
> -----Original Message-----
> From: owner-smallwiki(a)iam.unibe.ch
> [mailto:email@example.com] On Behalf Of stéphane ducasse
> Sent: Thursday, January 12, 2006 11:09 AM
> To: smallwiki(a)iam.unibe.ch
> Subject: Re: smalltalk repository
> Ok sorry I was judging the look and not the techno.
> Stupidly I thought that they used a css.
> On 12 janv. 06, at 18:37, Ramon Leon wrote:
> >> Nop I mean css.
> >> It would be good that Smallwiki gets as stable as those
> cms and this
> >> is why lukas needs help.
> >> Stef
> > Help me out then, I don't understand your comment, that
> link leads to
> > a site that's a table layout, not css layout. What am I missing?
> Nop I mean css.
> It would be good that Smallwiki gets as stable as those cms
> and this is why lukas needs help.
Help me out then, I don't understand your comment, that link leads to a
site that's a table layout, not css layout. What am I missing?
I decided to create a subclass of PRPierFrame to start a new site.
The only thing I overrode from PRPierFrame is the class method
createInvironemntFor:. I remove the view widget, and reordered the
other two on the left side of the display. I then initialized this
new class, gave it a new kernel name and root, and opened it up. It
displayed as I had expected it to.
Problem is, the existing pier app now displays the new structure
too. Why is this? Are some Pier classes singletons?
Most (current) books on XHTML will say not to use tables, to use
div's instead. I understand that div's have a bit of a higher
learning curve, but they are truely intended as page layout
elements. Will table use in Pier be replaced by div's?