I installed SmallWiki in Squeak today--I'm impressed! Thanks for sharing
this.
When trying to get SmallWiki started, I found that the method in the
attached changeset was sending #removeAtIndex: instead of #removeAt: to
an OrderedCollection instance.
After getting it up and running, I ran the SmallLint methods sent but
not implemented checks and found the following issues:
#postCopy should be implemented in Object. The following send super
postCopy but don't have any superClass that …
[View More]implements it:
SWUser
SWText
SWDocumentComposit
SWDocumentComposite
SWBasicRole
SWStructure
SWPropertyManager
SWDocumentComposit is probably a typographical
error--SWDocumentComposite was probably intended. It appears that
something strange is going on with these two similarly named classes.
SWSIXXStorage>>directoryTime sends #hour to a TimeStamp instance, which
is not implemented.
SWServer>>emitContext:on: sends #localScope which is not implemented.
SWCode>>internalEvaluate:on:with: sends
#evaluate:in:allowReceiver:receiver:environment:notifying:ifFail:handler: to a Compiler instance, which is not implemented.
-Mark
[View Less]
when searching Google for SmallWiki pages, only the views are indexed
and listed by the search-engine. Searching other wikis often gives
results that point to edit-, history- and changes-pages, usually not
the intention of the user.
http://www.google.com/search?q=site:kilana.unibe.ch+smallwiki
SmallWiki tags the pages to tell search-eninges, whether they should
index a page or whether they should just follow the links. Of course
this behaviour can be customized using the template editor.…
[View More]
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
[View Less]
Hi,
> I'm loading from public rep version 0,9,21.
this should be fixed in 0.9.22
Cheers,
Lukas
> it seems that there is package loading sequence problems, becouse i
> get an error when the system try do initialize
> the class SmallWiki.Structure. the method initializePermission has
> some undefined. Commenting it make the load procede.
>
> The problem is that initializePermission in Page class try to add a
> permission to the class instance var …
[View More]<permission>,
> but this one is nil, not some kind of collection.
>
> ciao
>
> Giorgio Ferraris
--
Lukas Renggli
http://renggli.freezope.org
[View Less]
* How do I create a LaTex-Document with the content of a SmallWiki?
Which expression do I have to evaluate?
- load the bundle SmallWiki Examples
- in the SmallWiki workspace inspect server root and navigate to the
page you want to turn into latex (currently the visitors do not support
rendering a whole wiki at once, but this could be changed easily)
- inspect one of the following the expression in the evaluation-pane:
(VisitorRendererLatex render: self) contents
VisitorRendererLatex render: …
[View More]self on: aStream
* How do I create one large XHTML file with the content of a SmallWiki?
This is basically the same as above, you just have to use
VisitorRendererHtml instead. It is not needed to load the
examples-bundle as this functionality is provided by the core-system
already. Support for rendering multiple pages is also missing
right-now, there was no need to do this up-to now (calling super
acceptFolder: aFolder in VisitorRendererHtml>>acceptFolder: aFolder
should change this behaviour, but will most certainly break the wiki,
so it is probably a better idea to create a new subclass).
--
Lukas Renggli
http://renggli.freezope.org
[View Less]
Hi Hannes,
please post you questions, comments, bug-reports, etc. to the SmallWiki
mailing-list so everybody is able to join the discussion and profit
from the answers ...
> Als ich vor 10 Tagen von der Elfenbeinküste zurückkam war ich
> begeistert zu sehen, dass Chris und Stephen SmallWiki auch auf Squeak
> portiert haben. Ich habe eben zur Zeit all mein Zeugs in Squeak und
> kann es mir zeitlich einfach nicht leisten mich noch auf VisualWorks
> einzulassen auch …
[View More]wenn das technisch nicht mal so schwierig ist,
> organisatorisch und zeitlich eben dann schon ....
I tried the Squeak-Port too and it is great to see all the tests pass.
Thanks a lot to Chris and Stephen! Unfortunately there seem to be a
problem when submitting the login-form in my image, probably just
because I did not take a fresh one ...
Keep in mind that when replying to questions I am always referring to
the VisualWorks implementation. As I am taking a lot of lectures at
university and as I am working on different other Smalltalk projects
too I will concentrate my energy onto the main-platform of SmallWiki
solely; but obviously this shouldn't be no problem as the
implementations should be the same ;) ...
> Das hat mich dazu geführt drei Fragen in der FAQ zu notieren
> http://kilana.unibe.ch:9090/SmallWiki/FAQ/
I've added the answers to those questions to the FAQ:
* After installing SmallWiki - how do I get access to the example
actions?
Go to your favorite web-browser and browse to the structure you want to
execute your action on. If the action is not listed at the top right
corner you might want to try to execute it manually by adding/replacing
the action-parameter to the url:
http://localhost:8080/?action=MyExampleActionClassName.
In order to make your (new) action appear automatically, you have to
make sure the following conditions are set:
-An action should return a title on the class-side, else it is
considered to be abstract and not displayed anywhere.
-An action should not throw an exception during evaluating
#executePermissions, else it is not evaluated as some permissions are
considered to be missing.
-An action has to register to the structures it is able to handle: Page
registerAction: MyExampleActionClassName
-Last but not least, you should add the action to the current template
using the template-editor.
* Which export formats are available at the moment? Can I export the
wiki text into plain text files?
Right now there is no plain-text renderer (visitor) implemented and it
is left to the reader to implement one ;) ... Actually it is very easy
to do something like this, you might get an idea when looking at the
existing renderers: HTML (VisitorRendererHtml), Wiki
(VisitorRendererWiki) or Latex (VisitorRendererLatex).
* If I begin using SmallWiki today in a productive environment, will it
be possible to upgrade to the next versions and keep the data without
too much effort?
Yep, in fact I am doing this with http://kilana.unibe.ch:9090 since
this spring and never got troubles updating the code. Basically you
have to do the following:
-save the current image: server storage snapshot
-stop the storage thread by evaluating: server storage: nil
-stop the web-server by evaluating (most of the time not even
necessary): server stop
-connect to StORE and load updates
-run the tests to see if nothing got broken
-start the web-server by evaluating (if you have stopped it): server
start
-browse to your wiki and check if everything is still there (if
something is broken, you still have your old image!)
-start the storage thread by evaluating: server storage: ImageStorage
new
-save the current image: server storage snapshot
> Als ersten kleines Bsp. möchte ich konkret das Glossar (ca. 200
> linguistische Fachbegriffe), die wir im Swahili-Kurs verwenden über
> das SmallWiki editieren lassen
>
> Swahili-Kurs:
> http://www.unizh.ch/spw/afrling/aliswahili/yal/matini/90/aswi-01.html
>
> Glossar
> http://www.unizh.ch/spw/afrling/aliswahili/yal/matini/00/U00sar-
> ec07.html
>
> Bei Swahili kommt man mit nur-ASCII klar.
A glossary of linguistic expressions seem to be an interesting project
to use SmallWiki for.
> Ich möchte also das SmallWiki als kollaborativen Editor für einfache
> HTML-Texte (später auch zwischen Afrika und Europa) verwenden; wichtig
> ist für mich der Import und Export der Dateien.
What you could do is to write a visitor rendering the content of a page
as plain-text. Then you add an action to provide the output of that
page as a download. So finally you have a link on every-page, where you
are be able to download those generated files ...
> Was ist bereits eingebaut und aus Benutzersicht einfach zugänglich?
There is no such a thing yet, but I am doing the documentation using a
latex-visitor, what is probably very similar to your needs. Although I
don't use the latex-visitor yet to generate files from within
SmallWiki-Pages, but instead I parse and generate the documentation
using the class- and method-comments of my code. However it is simple
to add an action to use that visitor to export wiki-pages from within
SmallWiki, if you like I can come up with an (almost no lines-of-code)
example ...
> Wenn ich ein SmallWiki-Image (inkl. VM) auf einem Memory-Stick
> jemanden weitergebe: Wie kann er den Inhalt importieren / exportieren?
Sure, you can pass around SmallWiki-Images like any other Smalltalk
image, run it on different platforms, etc.
> Übrigends: Eure Arbeit (Berner) nehme ich als herausragendes Bsp. im
> Squeak-Bereich wahr von seriöser Arbeit. Ich habe bisher wenig
> sauberes Design und auch die Doku dazu gesehen. Dein Paper gefällt
> mir, wenn es auch noch etwas knapp ist. Ich schätze Euren Gesamtansatz
> sehr.
Thanks, I am glad to hear that ...
Cheers,
Lukas
--
Lukas Renggli
http://renggli.freezope.org
[View Less]
> From: Hannes Hirzel <hannes.hirzel.squeaklist(a)bluewin.ch>
> Newsgroups: gmane.comp.lang.smalltalk.squeak.general
> Subject: Re: [ANN] Squeak People
> Date: Thu, 13 Nov 2003 21:03:18 +0000
> Reply-To: The general-purpose Squeak developers
> list<squeak-dev(a)lists.squeakfoundation.org>
>
> [...]
>
> As a summary: I was away for some time and I'm surprised and excited
> to find Squeak in such a good shape!!! It is amazing what one finds on
> …
[View More]SqueakMap. Today I set up a SmallWiki site; it was extremly easy. It
> is exciting to have a wiki I can easily transfer from a Mac to a PC
> with basically nil setup and and configuration efforts. And the whole
> wiki is a real object (one root, composite pattern).
>
> [...]
--
Lukas Renggli
http://renggli.freezope.org
[View Less]
an idea for security in SmallWiki look at the
http://people.suqeakfoundation.org/
Stef
Begin forwarded message:
> From: "Andreas Raab" <andreas.raab(a)gmx.de>
> Date: Jeu nov 13, 2003 13:02:02 Europe/Zurich
> To: "'The general-purpose Squeak developers list'"
> <squeak-dev(a)lists.squeakfoundation.org>
> Subject: RE: [ANN] Squeak People
> Reply-To: The general-purpose Squeak developers list
> <squeak-dev(a)lists.squeakfoundation.org>
>
> Hi,
&…
[View More]gt;
>> I agree with Stephane, what is the intention of this thing?
>
> I guess Cees' intention is simply to experiment with "just another"
> approach
> to community sites. Couple of things I like about it (and why I think
> it's
> going to be successful):
> * It's really simple to use and very intuitive
> * It has a model of trust which seems really nice[*]
> * It is very clean in its presentation and simple to read for anyone
> new to
> Squeak
>
> [*] If the trust model works out I could imagine that we use
> authorizations
> derived from the site - e.g., something like "for the front page you
> have to
> be certified journeyman or higher". Doing this would (I think) almost
> immediately block any of the abuse we see on the Swiki today.
>
>> And why not wait for the results of the November task force
>> before opening another space for discussion?
>
> TFNR has (in my understanding) very different goals. The site can be
> used to
> discuss some of these but other than this I don't see any overlap
> whatsoever. Do you?
>
>> Such a thing could be a nice thing for a task force who works
>> on a specific project; but at the moment this context is missing
>> ... why not enhance the existing processes?
>
> Not sure I understand this. Personally, I think the site _is_ an
> enhancement
> of the existing processes.
>
> Cheers,
> - Andreas
>
>
>
[View Less]
Hi Anthony,
thanks a lot for reporting those nasty mistakes. I've corrected them
and put an updated version of the documentation on our server:
http://www.iam.unibe.ch/~scg/smallwiki/smallwiki.pdf
Cheers,
Lukas
On Wednesday, Nov 12, 2003, at 13:59 Europe/Zurich, Anthony Labarre
wrote:
> Good afternoon,
>
> I am a student at the ULB, attending Roel Wuyts' course on software
> engineering, and we currently have to work on SmallWiki extensions, so
> I began by reading your …
[View More]document entitled "SmallWiki Collaborative
> Content Management", especially chapter 4. I noticed two errors
> (little mistakes, but nonetheless errors) I thought you would
> appreciate being told about :
>
> 1) page 39 : instead of : "http://localhost:8080/?action=ActionInfo",
> it should be: "http://localhost:8080/?action=InfoAction"
> 2) page 39 : there's an 'a' missing in 'initialize' ("InfoAction
> class>>initilize", last code snippet at the bottom of the page)
>
> Have a nice day,
> A.
--
Lukas Renggli
http://renggli.freezope.org
[View Less]
Hi,
Here is the example for why to put the <div> inside the <td> tags (I
tried it on Safari and Internet Explorer on Mac and on both the margin
option is not taken into consideration for the <td> tag):
<?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/2000/REC-xhtml1-20000126/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<style type="text/css">
…
[View More]<!--
.cellDiv {
margin: 20px;
background-color: #FFAAAA;
}
td {
margin: 20px;
background-color: #AAAAFF;
border: 1px solid black;
}
-->
</style>
<head>
<title>Girba Test</title>
</head>
<body>
<table border="0">
<tr>
<td>table cells as in SmallWiki</div></td>
<td>some cell</td>
</tr><tr>
<td>some cell</td>
<td>some cell</td>
</tr>
</table>
<table border="0" cellspacing="0">
<tr>
<td><div class="tableCell">table cells with a div</div></td>
<td><div class="tableCell">some cell</div></td>
</tr><tr>
<td><div class="tableCell">some cell</div></td>
<td><div class="tableCell">some cell</div></td>
</tr>
</table>
</body>
</html>
On Tuesday, Nov 11, 2003, at 07:52 Europe/Zurich, Lukas Renggli wrote:
> Hi,
>
> these are some things that I missed or left out yesterday:
>
> Tudor Girba <girba(a)iam.unibe.ch>:
>
>> 1. In the morning I manage to have a table by putting | (now it does
>> not seem to work anymore). I saw that the <td> has no tags inside,
>> therefore it is not possible to have padding or margin css options
>> for the text in a cell. I suggest to have a <div class="tableCell">
>> there.
>
> What about overloading the table-tags? This has the same effect as if
> I put a <div class="tableCell"> into every cell, right?
Doru.
--
Tudor Adrian Girba Software Composition Group
(www.iam.unibe.ch/~girba) University of Bern, Switzerland
"Problem solving efficiency grows with the abstractness level
of problem understanding."
[View Less]