I'm trying to add a custom action to a template (Squeak version).
I did everything in the FAQ (even registering the action with SWPage
etc) and I'm also able to evaluate the action using the ? notation.
But, when I'm editing the template settings the add, remove, up, down
button are not doing anything.
I'm probably overlooking something really obvious ;-)
Stéphane ducasse posted to squeak-dev:
> What we are doing or planning to do:
> - port SmallWiki to Seaside so that we can have a better CMS. If you
> want to help
> please contact send an email in the smallWiki mailing list
> - David rothlisberger is starting to have a forum on top of Seaside
> and will start to
> port smallWiki to Seaside.
> - this means that we could integrate a forum with a super extra
> SmallWiki and SqueakSource.
I've been thinking about this as well. My Wiresong site
(www.wiresong.ca) runs Smallwiki for the main part of the site, but
Smallblog for the blog section - it's a completely separate app in a
separate image. I'd also like to better integrate my Monticello
repository with the site, but SqueakSource isn't quite what I want for
So, yes, a Seaside version of SmallWiki would be great. I won't be able
to do any work on it until after I get back from StS though.
Another thing I was thinking about is a VW port of Monticello. That
would let us maintain SmallWiki in MC and keep the Squeak version in
synch with the main VW branch more easily. I sat up and took notice
when Lukas mentioned recently that he didn't want to do a merge with
StORE. Avi and I have kicked around a few ideas for how to maintain
cross-platform packages using MC, but we didn't come up with anything
really solid. I guess we'll have to try it out to find out what works
and what doesn't. Anybody else interested in that?
You can't change the title of a page by adding or removing a space of
semicolon, or whatever character that is ignored in the structure name.
As a workaround you change the title in two steps by making an extra
change in the first step and remove that again in the second step.
I made a patch of internationalization for the VisualWorks SmallWiki.
You can set any charset by admin menu with this patch. Then, it encodes
pages by the VisualWorks encoder corresponded with the charset.
I hope this code will be merged into the core packages. How can I
contribute my patch? send it Lukas or publish a bundle on the public
store registry temporally?
Koji Yokokawa <yokokawa(a)logical.design.co.jp>
I see the fine manual says
"As Table 2.1 shows, the syntax of SmallWiki is similar to SqueakWiki or
WikiWorks. Changing the grammar of the parser is no big deal, if you are
more familiar with a different one and want to support that. However, as for
all other parsers, it is difficult to write extensions that can be added and
removed independently in order to parse new document entities."
Where can I find tutorials/pointers/whatever on how to change the grammar?
Thanks to the help of Michael Rueger there is now a full archive of the
SmallWiki mailing list accessible at:
Michael imported all the mails that I've collected over the past in my
personal mailbox and is kindly hosting the archive on his server.
> Sorry to bother you at this time with this subject. Do you know if I
> use '[', ']', '<' and '>' in a SmallWiki page? Or else tell me where I
> read this.
> The problem is that I want to describe the syntax of my test tool using
> regular expressions:
> <command> <mandatory parameter> [optional parameter]
you can use all special wiki characters by escaping them: that is you
escape them by putting a back-slash in front like \[, \*, \!, ... For <
and > this is slightly different, as they are used to build the xhtml
and are preserved by SmallWiki. You have to write them using
html-syntax: > and <
Actually all the escaping isn't necessary if you use preformatted-text,
maybe want to do this anyway when displaying source-code.
= #( a b c ) do: [ :eaach |
= Transcript show: '<'; show: each; show: '>'; cr ]
Hope this helps,
> Preferably it should work within a table.
Escaping works in any context :)