I will definitely test it. Thanks for your port. Is the storage mechanism works in the same way than in VisualWorks? Cheers, Alexandre On Wed, Dec 08, 2004 at 11:42:35PM +0100, Chris Burkert wrote: -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.iam.unibe.ch/~bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Hi! Some comments related to my try to load Smallwiki with Squeak 3.7 or 3.9. First, the installer script you provided does not work for me. I had to install all the packages manually. When I evaluate 'SWServer startOn: 9090' I got immediately a rollback: MessageNotUnderstood: OrderedCollection>>removeAtIndex: not found. Fine, I just replace this call by removeAt: Here a more serious issue. SWServer>>start is abstract (contains self subclassResponsability). And it is invoked by StartOn:host:ip:. I did not check how is it in VW... I do not have so much time. Cheers, Alexandre On Thu, Dec 09, 2004 at 07:53:58PM +0100, Chris Burkert wrote: -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.iam.unibe.ch/~bergel ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Hi all, I have attached two changesets for SmallWiki1 in Squeak: *HierarchyMenu* outputs a menu like the one on our site, for example http://www.squeak-ev.de/Dokumentation/Glossar/Malkasten/ *Umlaut* just adds one line to SWHtmlWriteStream.text: text: aString | table escape | table := self escapeTable. aString do: [ :character | ">>> following line added" character _ character isoToSqueak. escape := table at: character ifAbsent: [ nil ]. escape isNil ifTrue: [ self nextPut: character] ifFalse: [ self nextPutAll: escape] ] If I am not completely wrong, this line is essential to anyone, who wants to properly handle characters > 127, unless he runs his image on a MacOs-Server... Regards Andreas 'From Squeak3.6 of ''6 October 2003'' [latest update: #5429] on 20 December 2004 at 3:18:33 pm'! "Change Set: SmallWikiUmlaut Date: 20 December 2004 Author: Andreas Gerdes Adds one line to properly handle characters whose ascii value > 127."! !SWHtmlWriteStream methodsFor: 'html-primitive' stamp: 'ag 10/22/2004 15:49'! text: aString | table escape | table := self escapeTable. aString do: [ :character | character _ character isoToSqueak. escape := table at: character ifAbsent: [ nil ]. escape isNil ifTrue: [ self nextPut: character] ifFalse: [ self nextPutAll: escape] ] ! ! 'From Squeak3.6 of ''6 October 2003'' [latest update: #5429] on 20 December 2004 at 3:11:18 pm'! "Change Set: SmallWikiHierarchyMenu Date: 20 December 2004 Author: Andreas Gerdes Adds a Hierarchical Menu to the templates of SmallWiki. In your CSS you should define an ID named #hierarchymenu and two selectors named .current and .norm"! SWTemplateBody subclass: #SWHierarchyMenu instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'SmallWiki-Templates-Menu'! !SWHierarchyMenu commentStamp: 'skag 12/20/2004 13:59' prior: 0! Hierarchical Menu showing the tree of a selected node. In css it can be formatted via #hierarchymenu ! !SWHierarchyMenu methodsFor: 'as yet unclassified' stamp: 'skag 12/20/2004 14:57'! buildUlForChild: aChild ofParents: aParentCollection baseStruct: aStructure on: html html unorderedList: [ aChild isComposite ifTrue:[ aChild children do: [:child | self doRenderChild: child on:html currentStructure: aStructure. (aParentCollection includes: child) ifTrue: [ self buildUlForChild: child ofParents: aParentCollection baseStruct: aStructure on:html] ] ] ]! ! !SWHierarchyMenu methodsFor: 'as yet unclassified' stamp: 'skag 12/20/2004 14:08'! doRenderChild: aStructure on: html currentStructure: aCurStructure (aStructure = aCurStructure) ifTrue: [html cssClass: 'current'] ifFalse: [html cssClass: 'norm']. html listItem: [html anchorWithUrl: aStructure url do: aStructure title ].! ! !SWHierarchyMenu methodsFor: 'as yet unclassified' stamp: 'skag 12/20/2004 15:00'! renderBodyWith: anAction on: html "this template does not involve a visitor class, because it recursively rebuilds the whole document tree by itself" |current theRoot theParents | current _ anAction structure. theParents _ current parents. "note that SWStructure.parents includes current!!" theRoot _ current root. self renderDivFor: anAction on: html with: [ html unorderedList: [ "always render the rootnode" self doRenderChild: theRoot on: html currentStructure: current. "render the rootnodes children" theRoot children do: [:aChild | self doRenderChild: aChild on: html currentStructure: current. (theParents notEmpty) ifTrue: [ (theParents includes: aChild) ifTrue: [ "aChild is THE FIRST LEVEL ANCESTOR of the current node, so go on recursively showing aChilds children, until current itself is included in theParents:" self buildUlForChild: aChild ofParents: theParents baseStruct: current on: html. ] ] ] ] ] ! ! !SWHierarchyMenu class methodsFor: 'as yet unclassified' stamp: 'skag 12/20/2004 13:54'! title ^'HierarchyMenu'! !

Am 09.12.2004 um 15:09 schrieb Charles A. Monteiro: SmallWiki is a non-commercial product, too. Yet everybody *using* it in a commercial setting has to have a *developers* license. We asked. This is official Cincom policy. The same is true for other projects, e.g. Moose and CodeCrawler. Marcus

On 9 déc. 04, at 16:34, Charles A. Monteiro wrote: No you get us wrong. We are the same. It happens that I know really small companies that have really to pay attention and this is their choice not mine. :) But the message of cincom is not that clear and this is not really my problem. Because if a small company is making money but just enough I'm not sure that 6% to pay on the net income can work. If the 6% would be on the benefit this would be different. We are not in this setup. But imagine we are developing reengineering tools: the tools are freely available but now is a company authorised to use it without paying a fee or having a commercial version of VW to run it when it uses our free tools on their bug software. I do not really know. Because may be what they are doing with it is gaining advantage of our tools. I think that from cincom point of view they do not care since we are not selling the tools. But this is what marcus was implying. For me I really do not care because my goal is not to make money but we do not want that SmallWiki gets less participation because it is on VW. So we gave a try in VW and now we are giving a try on Squeak and we will see what are the best communities for SmallWiki but we will pay attention that people can port it from one to the other. as we did for SmallWiki one. Stef

Hi charles In fact this is a bit complex than that: - James said that normally if you do not ask for support you would not have to pay - I have no problem to pay for VW but others have. - for example this is not clear if you should pay because you use a wiki for a company if the wiki is used to get cusotmer information .... - we decided to move to Squeak because lukas was only developing in VW for SmallWiki (but back porting to VW is something that we will always keep in mind). - May be VW is better for serving than squeak but we had to try :) - this is true that store is a bit painful (even if the tool of MC are still for my taste a bit raw). But waiting 40 min for a merge is not possible for me. - We hope that more people will contribute to SmallWiki 2 :) because we felt a bit alone. - SmallWiki 2 will be more a really cool contents management system than a simple wiki so small companies may want to help and they often do not work in VW. - for traits they are not yet in squeak but in the pipeline for 3.9. But as lukas said this should not be a problem I hope that this makes our move clearer but Stef On 9 déc. 04, at 15:09, Charles A. Monteiro wrote:

On 9 déc. 04, at 16:50, Charles A. Monteiro wrote: Me too. Because Cincom should do a much better work to communicate that. And for me this is crucial that VW exist and get clients but I will not do their job. I do not know. I discussed with alan and we change the postgres server but we got even a slow down with the latest postgres. On Moose which is not that bigger. I can tell you that I went eating waiting that the merge (really nothing may be ten methods there and there) was done. I know. Exact but what can I do. Cincom should communicate better. I know but as I said SmallWiki should first build a strong community and VWers were not there. So let us cross our fingers and see. SW II will be really cool (and is already with seaside components) but this is open source so people will be able to do what they want with it, even money if they can. So I think that we will learn from the experience and the second iteration will be really better (command, better url, seaside, metadescription, backend based on a db....) Stef