Hi all,
I was wondering how we should proceed to get more exposure from the
community and get
help.
Any idea? Should we try to plan for an official 0.9 version?
Publish it to the store repository, sending messages into the news and
various mailing-lists, wiki pages, open-source projects?
Alex what is the status?
Stef
Alex: When I'm back in shape (I hope) I would like to have some coding
sessions on SmallWiki so that it can start to run well: I was thinking
about the management aspect.
Prof. Dr. Stéphane DUCASSE
http://www.iam.unibe.ch/~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
earth" Calvin&Hobbes
"The best way to predict the future is to invent it..." Alan Kay.
Open Source Smalltalks: http://www.squeak.org,
http://www.gnu.org/software/smalltalk/smalltalk.html
Free books for Universities at
http://www.esug.org/sponsoring/promotionProgram.html
Free Online Book at
http://www.iam.unibe.ch/~ducasse/WebPages/FreeBooks.html
Hi,
> We can't debug our SmallWiki stuff anymore because you are trapping
> all exceptions.
>
> Can you please tell us how to disable the exception catching?
I already discovered that problem when switching from VisualWorks 7 to
7.1, but did not consider it too important. I am very sorry for the
resulting inconvenience!
Thanks to the help of Roel the problem is now fixed and the latest
version should behave the same and correctly with VisualWorks 7.0 and
7.1.
Unfortunately I was not able to publish the new code to the ST2003
StORE as some students were again publishing their projects within the
SmallWiki bundle. So you have to get the latest version from the SCG
StORE!
Cheers
Lukas
--
Lukas Renggli
http://renggli.freezope.org
Hi,
why the SmallWiki Syntax (HelpSyntax action) is not a WikiPage like in other Wiki implementations ?
In other words, why this is an action and not a page ? I think it's more WikiWay!
An other nice option is to have the syntax rules just above the edit form like in : http://twistedmatrix.com/users/jh.twistd/moin/moin.cgi/SergeStinckwich?acti…
Cheers,
--
Serge Stinckwich -< )
Université de Caen>CNRS UMR 6072>GREYC>MAD /~\
http://www.iutc3.unicaen.fr/serge/ (/ |
Smalltalkers do: [:it | All with: Class, (And love: it)] _|_/
Hi everybody,
I updated the slides (former used at SqueakNic and SCG meeting) due to
the discussion of today. I also tried to work more with colours and
added more information and a few quotes.
There is still some important stuff missing, at least one more slide
about templates and one about actions. I've also not yet decided what
example we should implement together.
But never-less I would love to hear your comments ...
Cheers
Lukas
--
Lukas Renggli
http://renggli.freezope.org
Hello Lukas, Roel and all!
In this email I will summarize all the problems I encountered the last few weeks when playing with SmallWiki.
Basically it is about the composition of extensions.
How do we want to collect any collaboration from other people?
Of course, we should not touch the bundle smallwiki for that. I want to load smallwiki, and the set of extensions and that should work.
When one extension (i.e., template) needs to be taken into account by the server, it should be included into the template hierarchy. That could be done by extending the method VisitorRendererHtmlLight>>defaultTemplates, and by extending the visitor in order to make the template "rendererable". I have discussed with Lukas, and we agree that is really completely bad.
One solution could be:
- an extension are not represented anymore by a template, this leads to
- have a kind of "TemplateComponentHolder" class, understandable by the visitor, charged to contain all the new extension and to make a layout location. In this case just a
- registration mechanism is necessary
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi all
I'm ****fighting**** to try to produce a first documentation of
SmallWiki.
The idea is to extract as much as possible from the class comments. But
when there is no comment, I cannot invent it and as it may change in
the future I do not want to spend time updating it.
So please think that for every class you will write we will generate a
wiki page that show that ***YOU*** did not write any comment :)
Your code will be read by others so....
For now you will have to live with the fact that the documentation of
SmallWiki will be draft, I cannot do too much about it.
Stef
Prof. Dr. Stéphane DUCASSE
http://www.iam.unibe.ch/~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
earth" Calvin&Hobbes
"The best way to predict the future is to invent it..." Alan Kay.
Open Source Smalltalks: http://www.squeak.org,
http://www.gnu.org/software/smalltalk/smalltalk.html
Free books for Universities at
http://www.esug.org/sponsoring/promotionProgram.html
Free Online Book at
http://www.iam.unibe.ch/~ducasse/WebPages/FreeBooks.html
Just load the bundle names 'SmallWiki Examples', and start a SmallWiki server, and that should work.
If not, please tell me.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.iam.unibe.ch/~bergel
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
