thanks for the valuable feedback!
In the old one, Folder was a subclass of Page. This was reasonable.
new one, Page is a subclass of Folder, and this seems wrong. It looks
Folder is never used, and all Pages can be Folders.
I decided not to support pages anymore, as people didn't understand the
difference between Pages and Folder. Now the idea is, that all the
Pages can potentially have children.
The worst part of the old SmallWiki was the callbacks. They are a
design, virtually impossible to understand. I had hoped that the
version would fix them, but it didn't. Actions went away, and they
that bad, aside from the callbacks. So, tell us why the Seaside
an improvement? In my opinion, it is a big step backward.
In my opinion callbacks are great. They make a huge improvement of the
abstraction over the dumb and error prone HTTP-protocol: basically they
remove all the manual handling of request and response fields.
Seaside provides a lot of functionality in a much better tested and
designed manner, that I implemented on my own in SmallWiki 1. The
possibility to have state in components make a big improvement over the
old SmallWiki implementation, e.g. see the interface to edit resources
(something like this would have been almost impossible with SmallWiki
One of the bad features of the Seaside version is that actions are
in the user interface, not in the model. For example, a page is
the #save version of EditRenderer, but in the accept (or maybe
method of DocumentEditor.
I don't understand.
What I want is a separation of the model (SmallWiki-Model), the
controller (SmallWiki2-Seaside) and View (SmallWiki2-Seaside).
Eventually more code from the controller part should be moved to the
It looks like DocumentEditor does not create history, so the
trippy interface does something different from the Seaside
The trippy interface was just a test of the model. It isn't complete at
all and I didn't update it anymore since working on the seaside
This bug is due partly to bad design. There should be a single
place where documents are edited, like an Action. The model should
change the model.
Yes, I see. I will try to move more of the controller code to the
model. But unfortunately my time is very very limited. So don't expect
We got an error in the new SmallWiki whenever we tried to put a new
link on a page. Is there a newer version?
The link functionality is currently not implemented.