> A question: when I start an empty one, I can experiment with
> everything. But when I click history, I get prompted to log on. What
> is the username/password to use?
admin/smallwiki
> Maybe this should be on the Welcome page as well (the default one you
> can use to play).
Yeah the welcome page still needs a lot of improvement. We will see
what is possible to do, but as I am writing most of the documentation
within SmallWiki itself and automatically generate the latex using this
tree structure, it might be also easy to include it into a newly
generated wiki.
I expect to have a first draft version of the documentation ready by
the end of this day. It is almost complete for the automatically
generated parts, basically I trying to put it together in a nice form
right now.
Lukas
--
Lukas Renggli
http://renggli.freezope.org
> If you have some trouble for generating the latex files, or for using
> CVS, you can always ask...
Thanks a lot for you help! I reused your source-code to write a more
sophisticated latex-generator: It takes all the comments from a
specified browser-environment - in that case I just use all classes
from the SmallWiki namespace - parses them using wiki syntax and builds
abstract-document-trees like those of the wiki pages. So I then just
use the existing visitors to generate latex or html output. The only
missing thing right now, is to make the comments more readable.
Cheers
Lukas
--
Lukas Renggli
http://renggli.freezope.org
Hi,
I quickly fixed most of the suggestions that John Brand made on my
code. The only thing I did not really understand, was the following one:
You shouldn't need to refer to SmallWiki.* in the
SmallWiki namespace. Instead just refer to the class
or shared variable directly.
I expected that he did not like direct references to the namespace as
in the following expression.
SmallWiki.Visitor new
To get a list of those problems I browsed all the references to the
SmallWiki namespace, but only found about 5 references looking all
somehow like this one:
SmallWiki at: aString asSymbol ifAbsent: [ nil ]
So my question: Is there something wrong about this code? If nobody of
you has got an idea I will ask John ...
Lukas
--
Lukas Renggli
http://renggli.freezope.org
I will do them all to be sure that I understand. I guess that roel will
do the same. So you should have a
really good document after.
Please pay attention that we should generate the class description from
the class comment themselves.
This way we are sure that the comments are good.
By the way david was at the apero of roel and he told me that he will
contact you to get in sync with you.
Dragos also told me that he is starting to get into smalltalk which is
excellent.
Stef
Thanks a lot for reviewing my code!
> *) Template>>initialize refers to an undeclared parent variable.
We are currently redesigning the Template part of SmallWiki and go for
a much simpler approach based on Cascading Style Sheets (CSS). There
are lots of open-source style-sheets (http://www.csszengarden.com)
around and every graphic designers might provide such a file to define
the look of the wiki. Also from the implementation point of view, this
approach seems to be much simpler.
> *) The storage class seems to be linked to your storage mechanisms
> (image or
> sixx files). Instead I would like to be able to store the pages into a
> database. However, the default implementation of Storage doesn't really
> support this (since it is dealing with a delay loop that just
> checkpoints
> the wiki every so many minutes).
There is a notification mechanism to let the storage know about what
changed in the wiki-tree. But you are right, I should probably add
another abstract-class called SnapshotStorage to make the hierarchy
look like:
Storage
SnapshotStorage
SixxStorage
ImageStoarge
XyzStorage
So other Storage implementations liek XyzStorage not needing a delay
loop could just subclass Storage.
> *) How difficult/easy would it be to change to a WikiWorks syntax? --
> just
> wondering about converting existing wikis (e.g., the wiki.cs.uiuc.edu
> pages).
Basically you would just need to write a Parser to be able to read the
WikiWorks syntax. As the original source string is not stored anywhere,
you would also need a visitor to render the document as WikiWorks
syntax, in order to be able to do a full round-trip. There is a old
comparison of wiki-syntaxes at
http://scgwiki.iam.unibe.ch:8080/SCG/526. As you see, they are all
about the same, so I think this would be a very easy to do.
Lukas
--
Lukas Renggli
http://renggli.freezope.org
> From: Vassili Bykov <vassili(a)parcplace.com>
> Date: Die Sept 9, 2003 21:22:14 Europe/Zurich
> To: Lukas Renggli <renggli(a)student.unibe.ch>
> Subject: Re: SmallWiki
>
> Hi Lukas,
>
> This should be announced on vw-dev as well soon. The deadline for the
> goodies is October 15, at least according to the current schedule.
> Dave, our packaging guy, may fit something else after then, but better
> not try that. :)
>
> Cheers,
>
> --Vassili
>
--
Lukas Renggli
http://renggli.freezope.org
> From: "John Brant" <brant(a)refactory.com>
> Date: Die Sept 9, 2003 04:27:59 Europe/Zurich
> To: <renggli(a)student.unibe.ch>
> Subject: smallwiki
>
> I was looking at porting SmallWiki to my #Smalltalk since it looks much
> better than WikiWorks and it has tests. Anyway, when I was looking
> over the
> code I had some questions/comments:
>
> *) #= methods should test the class of the argument
>
> *) The Structure class is using become: to model the history of pages.
> The
> current page is become:d with the new page (making the new page the
> current
> one). Instead of relying on VW's object header records to perform
> become
> quickly, I think a better solution would be to explicitly model the
> page
> collection with the current page. In addition to being explicit about
> what
> is happening, it will also make it easier to port to other Smalltalk's
> (e.g., #Smalltalk which can't implement a become:). Finally, I believe
> it
> would make it easier to support a database as a backing store (instead
> of
> the sixx or image formats).
>
> *) Template>>initialize refers to an undeclared parent variable.
>
> *) You shouldn't need to refer to SmallWiki.* in the SmallWiki
> namespace.
> Instead just refer to the class or shared variable directly.
>
> *) In the ParserTests>>setUp method there is a missing ";":
> (Role name: 'anonymous')
> add: Page permissionCode
> yourself
>
> *) Your namespace defines Text so the Server class>>defaultWorkspace
> reference to Text is referring to your Text class instead of the
> default VW
> Text object.
>
> *) The storage class seems to be linked to your storage mechanisms
> (image or
> sixx files). Instead I would like to be able to store the pages into a
> database. However, the default implementation of Storage doesn't really
> support this (since it is dealing with a delay loop that just
> checkpoints
> the wiki every so many minutes).
>
> *) You don't need to specify a starting state for SmaCC if your
> starting
> state is the first one listed. You only need to specify the start
> state if
> you want multiple start states or the production isn't the first one
> listed.
>
> *) Why not provide an instance creation method for Text? Everywhere
> that you
> create a new Text object, you always send the #text: message (and
> sometimes
> it then sends the #yourself message).
>
> *) You should use the #includesKey: method on Dictionary instead of
> defining
> a method like:
> templates at: aName ifAbsent: [ ^false].
> ^ true
>
> *) Instead of using "??? isNil not" and "??? isEmpty not", you should
> use
> "??? notNil" and "??? notEmpty".
>
> *) How difficult/easy would it be to change to a WikiWorks syntax? --
> just
> wondering about converting existing wikis (e.g., the wiki.cs.uiuc.edu
> pages).
>
>
> John Brant
Michael
In SmallWiki we will propose a set of possible scenario to ensure
different level of security. Once SmallWiki will be stable in terms of
what we think is needed we will port it to squeak. Cees already ported
the document structures, visitor and parser/scanner for its small
contents management system. Daniel is also using that in Garden.
On Samedi, sep 6, 2003, at 10:53 Europe/Zurich, Michael Rueger wrote:
>
> Hi all,
>
> it finally happened: a couple of hackers discovered that swikis are an
> easy target. They already used three (!) of the ones I'm running to
> store links, videos and stuff. As a consequence I will need to lock
> all of them with a password.
> If you are running swikis on the net, either lock them or at least
> keep a close eye on them.
>
> So ignoring the issue of security finally comes back to haunt us
> (again).
>
> Michael
>
>
>
Hi Eric,
> Maybe you can answer this question right now:
> At the university of Chile, I have a web page accessible at
> www.dcc.uchile.cl/~etanter
>
> This page maps to my folder ~etanter/public_www
>
> Is there a way to make this page being SmallWiki? Knowing that I won't
> get the rights to do special stuff on the university server (I can
> just manage my account).
it is exactly the same for the machines here at my university.
What you could do, is to run it on a higher port number - ports above
1024 are allowed to be used for such purposes here at Bern. Then you
just put a new index-file into your directory ~etanter/public_www that
is either redirecting to SmallWiki or displaying SmallWiki within a
html frame-set.
Hope that helps,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
