smallwiki March 2003

smallwiki@list.inf.unibe.ch

14 participants
40 discussions

by Lukas Renggli

On Donnerstag, Mär 13, 2003, at 17:43 Europe/Zurich, Serge Stinckwich wrote: > On Thu, 13 Mar 2003 12:27:02 +0100 > Lukas Renggli <renggli(a)student.unibe.ch> wrote: > >>> i'm trying the new 1.166 version of SmallWiki. After launching the >>> server, there is an 500 Internal Server Error on >>> http://localhost:8080/ and i've got a Message not understood: #value >>> in the Launcher workspace >> >> I loaded 1.166 into a fresh image and it seems to work well on my >> machine when executing >> >> SmallWiki.SwazooServer startOn: 8080 >> >> It looks like a problem of the Swazoo-Server, but I don't know. Could >> you send me the stack-dump you get? >> >> Have you run the tests? On my machine I got just one failed >> (StorageTests>>testStorage), because StORE did not load the SIXX >> bundle >> correctly. I am not a StORE-Expert and I absolutely do not understand >> why it does not load everything inside the SIXX bundle. Roel could you >> have a look at this? > > Sorry to bother you again. > I just found my problem. It's a bit strange ... > > I use Mozilla. When i use http://localhost:8080/ it doesn't work. It > works with http://127.0.0.1:8080/ > Seems to be a Mozilla related problem. I have no problem with Konqueror Just today Alexandre found a bug, that is related to that problem. SmallWiki.SwazooServer>>start swazoo port: self port. swazoo ip: '*'. "this line have to be changed" swazoo start Note that the latest releases are somehow ugly, as I was changing the rendering stuff and did not implement a cool layout yet. There are also some new bugs introduced ;-) Cheers Lukas -- Lukas Renggli http://renggli.freezope.org

21 years, 9 months

[BUG][FIX]Opening a port

by Alexandre Bergel

Hello! I have found bug when I tried to deploy Smallwiki. Here is the method I've changed: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= SmallWiki.SwazooServer>>start swazoo port: self port. swazoo ip: '*'. swazoo start -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= The idea was to change 'localhost' by '*'. Having 'localhost' allows only __local__ connection. For instance, I couldn't connect to the smallwiki from a web browser launched on a different host. I didn't check the documentation of Swazoo (is there any?), so what I just said is the result of my personnal experience. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Bergel Alexandre http://www.iam.unibe.ch/~bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

21 years, 9 months

Template Components

by Lukas Renggli

Hi, as we discovered some severe design issues in the coding session yesterday, I am now rewriting the complete rendering and template related classes. The main idea is to use components and visitors, instead of the static template rendering classes I used in my first approach. I think the best is to give an example: To define the components visible on a page you create simply a composite of different template components. Please note, that this is independent of the actual design of your site, you just specify the basic layout, say: I want the wiki title on top. On the next line the current path should be displayed. Then we have two columns: on the left there is an operation-menu and a list of references and on the right there is the actual page content. ^TemplateRoot new add: TemplateGlobalTitle new; add: TemplatePath new; add: (TemplateColumns new add: (TemplateRows new add: TemplateOperations new; add: TemplateReferences new; yourself); add: (TemplateRows new add: TemplatePageTitle new; add: TemplatePageContent new; yourself); yourself); yourself The rendering is done using an visitor. It walks trough the tree (and if necessary also trough your document) and creates the html in its own design. If you like to have a different look you have to subclass the visitor. To implement a new widget (e.g. a history functionality) we simply create a new component and create a class-extension to the rendering-visitor to render our widget. You might already have a look at the code, if you like. But be warned, it has been tagged as "Under progress" because the code is quite a mess (unused code) now and there are a lot of bugs to be expected. Also I have not written a cool renderer yet, so you will feel like in the good old Lynx days ... Cheers Lukas -- Lukas Renggli http://renggli.freezope.org

21 years, 9 months

Re: Problem with 1.166

by Lukas Renggli

> i'm trying the new 1.166 version of SmallWiki. After launching the > server, there is an 500 Internal Server Error on > http://localhost:8080/ and i've got a Message not understood: #value > in the Launcher workspace I loaded 1.166 into a fresh image and it seems to work well on my machine when executing SmallWiki.SwazooServer startOn: 8080 It looks like a problem of the Swazoo-Server, but I don't know. Could you send me the stack-dump you get? Have you run the tests? On my machine I got just one failed (StorageTests>>testStorage), because StORE did not load the SIXX bundle correctly. I am not a StORE-Expert and I absolutely do not understand why it does not load everything inside the SIXX bundle. Roel could you have a look at this? Cheers Lukas -- Lukas Renggli http://renggli.freezope.org

21 years, 9 months

self halt

by Lukas Renggli

Ok, I just fixed the nasty problem with self halt in the serving part of the code. It is now save to use it and all other exceptions still get processed correctly. This is really a quite useful piece of code, as everybody might follow now how the page is processed, generated, etc. I wished I implemented that earlier ;-) Lukas -- Lukas Renggli http://renggli.freezope.org

21 years, 9 months

Re: Smallwiki and Storage

by Lukas Renggli

Hi Alex, > I would to know a bit more about the storage process. Right now, I > have a swiki running on my machine (moore.unibe.ch:8080) but if I stop > the process, everything is lost. How do you think we could manage > > that. Right, there is no storage defined by default. But if you start your sever (or modify the running one) using the following code, every change will be dumped out with SIXX immediately. server := SmallWiki.SwazooServer startOn: 8080. server storage: SIXXStorage new. Make sure you use the patched version of SIXX (it is version 3.0 in the SCG StORE), since the official one has got a sever bug and made it impossible to load the data again. > If you want, we can meet us when you can. Today I am working here at the SCG student-pool, so you can come and we could discuss before the official meeting at 16:30. Cheers Lukas -- Lukas Renggli http://renggli.freezope.org

21 years, 9 months

Using Store for supporting distributed developpement

by Stephane Ducasse

Hi We will release soon a first version of SmallWiki a new (and cool) Wiki implementation for VisualWorks. We are thinking about how people can provide patches and extension. I have the impression that for - an extension publishing a separate package is a good solution. - a patch may be publishing a parcel containing the patches that will then be reviewed, then incorporated. Does anybody has some ideas or tried a process that is efficient? Stef Prof. Dr. Stéphane DUCASSE (ducasse(a)iam.unibe.ch) 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: www.squeak.org, www.gnu.org/software/smalltalk/smalltalk.html Free books for Universities at http://www.esug.org/sponsoring/promotionProgram.html Free Online Book at www.iam.unibe.ch/~ducasse/FreeBooks.html

21 years, 9 months

Re: Using Store for supporting distributed developpement

by eliot＠parcplace.com

Stephane, the parcel loader now supports reloading and the bugs of the initial 5i.3 implementation are fixed. So one can simply publish a new complete version and have users reload it. The parcel loader then does a binary compare of the system's current parcel with the new version being loaded and updates only those methods that have changed, removing methods no longer in the parcel, adding new ones, and replacing ones that have changed. Using parcel reloading avoids problems with maintennance of patches. Reloading also works forwards and backwards in that one can reload an older version over a newer version to revert to a previous version. +----------------------------- | Date: Sat, 08 Mar 2003 11:55:22 +0100 | From: Stephane Ducasse <ducasse(a)iam.unibe.ch> | Subject: Using Store for supporting distributed developpement | Hi | We will release soon a first version of SmallWiki a new (and cool) Wiki = | implementation for VisualWorks. | We are thinking about how people can provide patches and extension. | I have the impression that for | - an extension publishing a separate package is a good solution. | - a patch may be publishing a parcel containing the patches that will=20 | then be reviewed, then incorporated. | Does anybody has some ideas or tried a process that is efficient? | Stef | Prof. Dr. St=E9phane DUCASSE (ducasse(a)iam.unibe.ch)=20 | http://www.iam.unibe.ch/~ducasse/ | "if you knew today was your last day on earth, what would you do=20 | different? ... especially if, | by doing something different, today might not be your last day on=20 | earth" Calvin&Hobbes | "The best way to predict the future is to invent it..." Alan Kay. | Open Source Smalltalks: www.squeak.org,=20 | www.gnu.org/software/smalltalk/smalltalk.html | Free books for Universities at=20 | http://www.esug.org/sponsoring/promotionProgram.html | Free Online Book at www.iam.unibe.ch/~ducasse/FreeBooks.html --- Eliot Miranda ,,,^..^,,, mailto:eliot@parcplace.com VisualWorks Engineering, Cincom Smalltalk: scene not herd Tel +1 408 216 4581 3350 Scott Blvd, Bldg 36 Suite B, Santa Clara, CA 95054 USA Fax +1 408 216 4500

21 years, 9 months

SmallWiki alpha testing

by Hannes Hirzel

Hi Lukas I would like to have a SmallWiki alpha release and help with user level testing - take a fresh Squeak 3.4 image - load Comanche (which version?) - load Smallwiki - do various user level lests (description in use case style). I would come up with these use cases if they do not exist already. What do you think? Regards Hannes

21 years, 9 months

Re: Patch and enhancements for SmallWiki ?

by Lukas Renggli

> how can i send you patches and enhancements for SmallWiki ? Great! Patches: I am not sure how to do this with VisualWorks the best. As I'm coming from the Squeak world, I would suggest to use Change-Sets. But there are probably better solutions using StORE, I just don't know. Enhancements: I think that there will be setup a special SmallWiki StORE for the Smalltalk lecture. Probably you could publish your enhancements there. > I already try to understand the whole framework. I've attached a PDF of a small presentation I did about SmallWiki. The full demo was done inside the wiki itself, but it is somehow difficult to load, because it needs an unofficial alpha-patch to SIXX. Cheers Lukas -- Lukas Renggli http://renggli.freezope.org

21 years, 9 months

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

smallwiki March 2003