>> The problem with StORE is the following:
>> - I want to move the message Server>>defaultPort to Server
>> class>>defaultPort. It works fine in the image, but when I publish
>> and reload everything into a new image, the message is again in
>> Server>>defaultPort. I already tried about 100 times, but it does not
>> get it. Roel could you help?
> Roel is on holiday. for another week now. The problem you are
> describing is really strange. I do not know how to help you. Are you
> sure that you publish and reload from the same store?
Indeed, that is a good question: But I checked my connection strings
twice and this is definitely not the problem.
It just looks like I discovered a bug in StORE. The following process
finally did it:
1. delete Server>>defaultPort
3. add Server class>>defaultPort
I will publish the new versions on ST-StORE, as soon as it is known to
be working well.
I did several changes to SmallWiki today:
- When you create a new wiki there are now a few pages added and there
will be the nice renderer selected. The pages are not very useful yet,
but that will change in the future.
- There is now also a default administrator initialized when creating a
new wiki with the username 'admin' and password 'smallwiki'. For system
running in public this should be changed.
- I have created a registration mechanism for actions and permission on
the Structure class, that is now much cleaner than the first approach.
Implementing that, I experienced something really nasty about StORE/VW:
It does not call the initialize message on classes that do not
implement initialize, but it should as its superclass does understand
- There is now also a special permission for the Smalltallk client side
code. This permission is checked in the wiki-parser: everybody is able
to see the result of such code evaluation, but only admins might modify
and save such a page.
- I also cleaned the code slightly, extended some tests and made them
run successful again.
The problem with StORE is the following:
- I want to move the message Server>>defaultPort to Server
class>>defaultPort. It works fine in the image, but when I publish and
reload everything into a new image, the message is again in
Server>>defaultPort. I already tried about 100 times, but it does not
get it. Roel could you help?
You can download and try smallwiki by fetching this very big files (about 30Mo):
I made a small script which run only under linux and solaris, but you can easily make it running on other OS.
under linux/solaris just type: run 8080
under windows: visual -nologo image/headlessSmallwiki.im -smallwiki port8080 save
it will start smallwiki on the port 8080
there is a saving mechanism, but my script doesn't handle it yet.
the complete image is saved each hour under snapshot_smallwiki.im (I do not remember exactly the name)
But do not forget this is only for testing...
Alexandre Bergel http://www.iam.unibe.ch/~bergel
I discovered that I have to use the full path to reference a page.
For example *How To/Add an Action* because How to is a folder.
Let us that we should be really careful can be really disruptive as my
experience showed it.
Now what is the semantics of remove?
if I point to a page A from page B
then A got removed from a folder C
do I still see the page B I hope.
I think that remove is not a good name (is it remove the link or delete
Then what is the password to remove page?
Finally we see quickly that we will need move page from there to there
because I wanted to reorganise the
page alex did and I put the mess.
Prof. Dr. Stéphane DUCASSE
"if you knew today was your last day on earth, what would you do
different? ... especially if,
by doing something different, today might not be your last day on
"The best way to predict the future is to invent it..." Alan Kay.
Open Source Smalltalks: http://www.squeak.org,
Free books for Universities at
Free Online Book at
... and running, still on: kilana:9090
Everything is saved
Alexandre Bergel http://www.iam.unibe.ch/~bergel
- The class Chapter class has been renamed to Folder to give a more
descriptive name. As far as I could test, this should have no big
impact on running systems, but old SIXX dumps won't be loadable anymore.
- The rendering of a folder is slightly different now: the title is
displayed as "Contents of aFolderTitle" instead of "aFolderTitle", to
make it clear in what context you are.
- A page describing the supported wiki-syntax is now accessible from
the edit-page action. The text has been basically copied from SWiki, it
should be probably rewritten as it is not a very user-friendly document.
- The security model has been attached to all the actions. By default
the anonymous user is assigned to the request. It has almost all the
permissions except for the history-commands, the removal-of-structures
and the execution of client-side code.
- The security system should even work with other users and roles, you
just have to define them. It should be also possible to modify the
roles according to the chapter the request is been processed on. I
haven't tried (due to lack of time) any of the features described in
that paragraph (but there are a lot of tests, working with the model),
so be careful: bugs to be expected!
Might I just throw a silly question in-between the visitor discussion?
How do I get the process-viewer in VW. I know that there must be
somewhere such a tool, but I don't know what parcel to load or where to
look in the image.
Right now I am working on a extended storage model that runs in a
background thread and should be much faster than the current
implementation and should not interfere with people browsing the
web-site the same time. It is a bit boring using "Process allInstances
inspect" all the time.