From ssastre at seaswork.com.ar Tue Jun 1 02:13:41 2004 From: ssastre at seaswork.com.ar (=?iso-8859-1?Q?Sebasti=E1n_Sastre?=) Date: Mon, 31 May 2004 21:13:41 -0300 Subject: uploading and downloading files Message-ID: Hi all, I'm using the wiki testing to domcument some projects. I found this problems: 1) Some file extensions seems to be not suported by smallwiki because when I download them (a .exe and a .tgz) they are sent without extension. 2) The ImageStorage mechanism hangs up the squeak when it tries to save automatically. I read on archive that in march 2004 this happen to somebody and it will be fixed. 3) Even putting a storage:nil , after a while the CPU starts to run 100% and looking at the VM process there is a SWImageStore process. When (manually) terminated that process, the CPU runned normally again (arround 3%) 4) Even setting the charset=iso-8859-1 I cannot edit and view correctly some of the latin alphabet characters. There is now some patch o fix I missed out? best regards, Sebasti?n Sastre ssastre at seaswork.com.ar www.seaswork.com.ar -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20040531/80d8eefa/attachment.htm From brant at refactory.com Tue Jun 1 20:10:26 2004 From: brant at refactory.com (John Brant) Date: Tue, 01 Jun 2004 13:10:26 -0500 Subject: Page edits don't display Message-ID: <40BCC692.2060106@refactory.com> Sometimes when I edit a page under IE on Windows, it doesn't display the saved page. The page save succeeds, but all that is displayed is a blank page. SmallWiki appears to send the 302 response back, but doesn't receive the request for the new page. Any ideas? John Brant From davidroe at bluewin.ch Tue Jun 1 23:03:19 2004 From: davidroe at bluewin.ch (=?iso-8859-1?Q?David_R=F6thlisberger?=) Date: Tue, 1 Jun 2004 23:03:19 +0200 Subject: Page edits don't display References: <40BCC692.2060106@refactory.com> Message-ID: <030f01c4481b$dfb90ce0$569c3e51@david715t080hb> Hello, > Sometimes when I edit a page under IE on Windows, it doesn't display the > saved page. The page save succeeds, but all that is displayed is a blank > page. SmallWiki appears to send the 302 response back, but doesn't > receive the request for the new page. Any ideas? I have had the same problem and tried a lot to fix it, but haven't found a solution... :( It seems to me that this problem only appears when using IE. Using any other browser than IE, Mozilla or Netscape for instance, I have never encountered this problem anymore. greets, David From ssastre at seaswork.com.ar Thu Jun 3 16:45:27 2004 From: ssastre at seaswork.com.ar (=?iso-8859-1?Q?Sebasti=E1n_Sastre?=) Date: Thu, 3 Jun 2004 11:45:27 -0300 Subject: Space is low ! Message-ID: Hi, I'm experiencing "Space is low" warnings on a squeak image with smallWiki in several ocasions. This warning reapears every time and the image has to be shutdown (some changes are lost). The smallwiki is running in a red hat 9 on a xp2600+ with 512MB Ram. The store mechanism is set to nil due to the StoreImage problem in squeak. any clues? I *beleive* this is happening only when I'm upload some file. There is a limit on the file size of the uploads? The upload speed is restricted for some reason? (in the lan it takes minutes tu upload 800KB, and a few seconds, wich is normal, to download it) Is normal that the use of the CPU goes to 100% when uploading/downloading? best regards, Sebasti?n Sastre ssastre at seaswork.com.ar Tel.:(5411) 4553-1367 Cel.:(5411) 155422-6800 www.seaswork.com.ar -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20040603/f1da785b/attachment.htm From ssastre at seaswork.com.ar Thu Jun 3 22:25:22 2004 From: ssastre at seaswork.com.ar (=?iso-8859-1?Q?Sebasti=E1n_Sastre?=) Date: Thu, 3 Jun 2004 17:25:22 -0300 Subject: Space is low ! In-Reply-To: <40BF449D.10609@chrisburkert.de> Message-ID: > Use the process Browser. Is the storage process still alive? There > should only be one (or none) storage process! Nope, I've already terminated that process. > > I *beleive* this is happening only when I'm upload some > file. There is > > a limit on the file size of the uploads? > > Yes ... use the -memory when starting squeak. Default is 48MB > I believe. OK, I'm testing now with -memory 128m but I thought that the squeak take memory from the linux dinamically. I mean, I din't hope that a max value has to be set. I don't know wath is going to happen when 128 would be short. > > The upload speed is restricted for some reason? (in the lan it takes > > minutes tu upload 800KB, and a few seconds, wich is normal, > to download it) > > Is normal that the use of the CPU goes to 100% when > > uploading/downloading? > > I have not tried yet. Regards, Sebasti?n Sastre ssastre at seaswork.com.ar www.seaswork.com.ar From chris at chrisburkert.de Fri Jun 4 15:19:54 2004 From: chris at chrisburkert.de (Chris Burkert) Date: Fri, 04 Jun 2004 15:19:54 +0200 Subject: Space is low ! In-Reply-To: References: Message-ID: <40C076FA.6010302@chrisburkert.de> Sebasti?n Sastre wrote: >> >>Yes ... use the -memory when starting squeak. Default is 48MB >>I believe. > > OK, I'm testing now with -memory 128m but I thought that the squeak take > memory from the linux dinamically. I mean, I din't hope that a max value > has to be set. I don't know wath is going to happen when 128 would be > short. It should allocate the heap dynamically. I believe this wasn't the case in older VMs ... which version do you use? Regards Chris Burkert -- http://www.chrisburkert.de/ From ssastre at seaswork.com.ar Fri Jun 4 16:33:33 2004 From: ssastre at seaswork.com.ar (=?iso-8859-1?Q?Sebasti=E1n_Sastre?=) Date: Fri, 4 Jun 2004 11:33:33 -0300 Subject: {posible spam} Re: Space is low ! In-Reply-To: <40C076FA.6010302@chrisburkert.de> Message-ID: > > OK, I'm testing now with -memory 128m but I thought that the squeak > > take memory from the linux dinamically. I mean, I din't hope that a > > max value has to be set. I don't know wath is going to > happen when 128 > > would be short. > > It should allocate the heap dynamically. I believe this > wasn't the case > in older VMs ... which version do you use? I'm using an image of squeak 3.6 but right now I'm asking to the executable with -version (in the linux server) and it says: 3.4-1 #1 XShm Tue Mar 4 05:30:53 CET 2003 gcc 2.95.4 Squeak3.4 of 1 March 2003 [latest update: #5170] Linux xombul.inria.fr 2.4.19 #2 Mon Aug 5 12:44:11 CEST 2002 i686 GNU/Linux default plugin location: /usr/local/lib/squeak/3.4-1/*.so I'm a little concern about this, I guess I shoul upgrade the VM on that server. That's right? Other question: if I have to upload to the wiki really big files like 70MB or more (and perhaps serveral of them) what storage strategy should I use? Regards, Sebasti?n Sastre ssastre at seaswork.com.ar www.seaswork.com.ar From renggli at iam.unibe.ch Mon Jun 21 16:07:23 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 21 Jun 2004 16:07:23 +0200 Subject: Camp Smalltalk Project (Oregon 2004) Message-ID: <512CE49A-C38C-11D8-9032-000393CFE6C8@iam.unibe.ch> http://wiki.cs.uiuc.edu/CampSmalltalk/What's+Going+on+at+CSOregon2004 http://wiki.cs.uiuc.edu/CampSmalltalk/SmallWiki -- Lukas Renggli http://renggli.freezope.org From ducasse at iam.unibe.ch Mon Jun 21 17:24:59 2004 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Mon, 21 Jun 2004 17:24:59 +0200 Subject: Camp Smalltalk Project (Oregon 2004) In-Reply-To: <512CE49A-C38C-11D8-9032-000393CFE6C8@iam.unibe.ch> References: <512CE49A-C38C-11D8-9032-000393CFE6C8@iam.unibe.ch> Message-ID: <285CDC9A-C397-11D8-AE76-000A9573EAE2@iam.unibe.ch> Therefore I think that this is really important for us and them to release a version based on seaside before the camp. On 21 juin 04, at 16:07, Lukas Renggli wrote: > http://wiki.cs.uiuc.edu/CampSmalltalk/What's+Going+on+at+CSOregon2004 > > http://wiki.cs.uiuc.edu/CampSmalltalk/SmallWiki > > -- > Lukas Renggli > http://renggli.freezope.org > From johnson at cs.uiuc.edu Tue Jun 22 00:17:30 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Mon, 21 Jun 2004 17:17:30 -0500 (CDT) Subject: configuring SmallWiki Message-ID: <200406212217.RAA07134@salad.cs.uiuc.edu> I can't find how to add sub-folders to the top folder. When I start it up, I get a top foler that contains a folder called "Information". I'd like to add siblings to "Information". The Workspace should tell me how to do this. Surely that is more important information than how to change the callback cache! So, where is this documented? If it is not documented, how do you do it? -Ralph Johnson From avanos at xs4all.nl Tue Jun 22 01:03:48 2004 From: avanos at xs4all.nl (Adriaan van Os) Date: Tue, 22 Jun 2004 01:03:48 +0200 (CEST) Subject: configuring SmallWiki In-Reply-To: <200406212217.RAA07134@salad.cs.uiuc.edu> References: <200406212217.RAA07134@salad.cs.uiuc.edu> Message-ID: <17071.213.84.174.51.1087859028.squirrel@webmail.xs4all.nl> Just make a new link like *new folder*. Then save the document and choose Folder. hth, Adriaan. > I can't find how to add sub-folders to the top folder. > When I start it up, I get a top foler that contains > a folder called "Information". I'd like to add siblings > to "Information". The Workspace should tell me how to > do this. Surely that is more important information than > how to change the callback cache! > > So, where is this documented? If it is not documented, > how do you do it? > > -Ralph Johnson > -- http://vdg38bis.xs4all.nl From johnson at cs.uiuc.edu Tue Jun 22 01:09:36 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Mon, 21 Jun 2004 18:09:36 -0500 (CDT) Subject: SmallWiki Persistence Message-ID: <200406212309.SAA07230@salad.cs.uiuc.edu> It appears to me that the only SmallWiki persistence mechanism so far is to save the entire image. Is that correct? I'd like a persistence mechanism a bit more like that of WikiWorks. Having used WikiWorks for a long time, I'd like to improve upon it. In particular, file names should be meaningful, and all the versions of a page should be stored in one file. It should be easy to delete past history. The file format should make the system very tolerant of crashes. It should be plain text and easy to edit with any text editor. wiki.cs.uiuc.edu has 33 wikis on it. Most of them are small, but at least three of them have several thousand pages apiece. The image is over 100 meg, since all pages are stored in memory (like SmallWiki). When the machine pages, I will buy more memory. It gets several hits a second, all day long. It runs for several months between reboots. I need a persistence mechanism that can handle this. -Ralph Johnson From avanos at xs4all.nl Tue Jun 22 01:17:57 2004 From: avanos at xs4all.nl (Adriaan van Os) Date: Tue, 22 Jun 2004 01:17:57 +0200 (CEST) Subject: SmallWiki Persistence In-Reply-To: <200406212309.SAA07230@salad.cs.uiuc.edu> References: <200406212309.SAA07230@salad.cs.uiuc.edu> Message-ID: <24992.213.84.174.51.1087859877.squirrel@webmail.xs4all.nl> External SIXX persistance exists. It's currently not part of the 'official' release. It's available at the cincom repository. BTW, an archive of the mailing list is available at http://impara.de/pipermail/smallwiki/ Adriaan. > It appears to me that the only SmallWiki persistence mechanism > so far is to save the entire image. Is that correct? I'd like > a persistence mechanism a bit more like that of WikiWorks. > > Having used WikiWorks for a long time, I'd like to improve upon it. > In particular, file names should be meaningful, and all the versions > of a page should be stored in one file. It should be easy to delete > past history. The file format should make the system very tolerant > of crashes. It should be plain text and easy to edit with any text > editor. > > wiki.cs.uiuc.edu has 33 wikis on it. Most of them are small, but at > least three of them have several thousand pages apiece. The image > is over 100 meg, since all pages are stored in memory (like SmallWiki). > When the machine pages, I will buy more memory. It gets several hits > a second, all day long. It runs for several months between reboots. > I need a persistence mechanism that can handle this. > -Ralph Johnson > -- http://vdg38bis.xs4all.nl From johnson at cs.uiuc.edu Tue Jun 22 01:35:33 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Mon, 21 Jun 2004 18:35:33 -0500 (CDT) Subject: configuring SmallWiki Message-ID: <200406212335.SAA07280@salad.cs.uiuc.edu> I think I understand about folders. When you create a link, the system asks whether the new item is a folder, page, etc. When I select an option, I get a blank page in IE. (I haven't tried other browsers yet.) Is that correct? It should say "xxx is a folder" or, better yet, show a blank folder. Are there any other wikis that do this? I haven't seen it before. It should be better documented. It isn't in the "Information/syntax" page, for example. The Information folder should be a user manual for SmallWiki. I read smallwiki.pdf quickly, and missed this idea, though it might very well be in there. -Ralph From johnson at cs.uiuc.edu Tue Jun 22 01:42:29 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Mon, 21 Jun 2004 18:42:29 -0500 (CDT) Subject: SmallWiki Persistence Message-ID: <200406212342.SAA07327@salad.cs.uiuc.edu> >External SIXX persistance exists. I haven't looked at it yet, but I am skeptical. Do you think it will do what I want? XML is just barely human readable. It tends to be slow. It is OK for a least common denominator, but you can almost always do better. I've looked at the mailing list. I didn't read the whole thing, though, and I probably didn't understand a lot that I read. -Ralph Johnson From johnson at cs.uiuc.edu Tue Jun 22 04:06:17 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Mon, 21 Jun 2004 21:06:17 -0500 Subject: Keeping robots away from SmallWIki Message-ID: Does SmallWiki have support for robot.txt? There needs to be a way to tell the robots to stay away from history and edit pages. The way I did this in WikiWorks was to generate a robot.txt file that tells them to stay away. For every wiki XXX, it puts in lines of the form wiki.cs.uiuc.edu/XXX/EDIT wiki.cs.uiuc.edu/XXX/HISTORY This only works because the page name comes AFTER the command. SmallWiki puts the command after the page name, so you'd have to generate a line for every command on every page. Or am I missing something? Suppose I wanted to change the URLs around so that I could prevent robots from executing actions. Would this be a major change, or easy? -Ralph From brant at refactory.com Tue Jun 22 04:48:28 2004 From: brant at refactory.com (John Brant) Date: Mon, 21 Jun 2004 21:48:28 -0500 Subject: SmallWiki Persistence In-Reply-To: <200406212342.SAA07327@salad.cs.uiuc.edu> References: <200406212342.SAA07327@salad.cs.uiuc.edu> Message-ID: <40D79DFC.6040407@refactory.com> Ralph Johnson wrote: >>External SIXX persistance exists. > > > I haven't looked at it yet, but I am skeptical. Do you think > it will do what I want? XML is just barely human readable. > It tends to be slow. It is OK for a least common denominator, > but you can almost always do better. I haven't looked at the sixx stuff since it was removed from the base, but I don't think it would work well. Essentially, it would save out everything every X seconds. If you had a power failure you could loose edits. Also, since it was saving everything, it would be quite slow -- you don't need to save everything for one edited page. I have built a storage mechanism that stores everything in two files. Whenever a page is edited, both files are updated. One file contains a one line description of a wiki item. This line then indexes into the other file for the full text. For example, the first file would look like: --------------- +1 Folder ~1 0 0 559 +2 Folder ~2 0 559 1189 +3 Page ~3 0 1189 3605 +4 Page ~4 0 3605 6611 +5 Page ~5 0 6611 7862 --------------- Lines that begin with + are new wiki items (page/folder/resource). Lines that begin with ~ are edits -- the last two numbers are the indices into the other file. The detail is stored in the other file. For example, here's the detail for the "~1 0 0 559" record: --------------- ID: 1 Title: 'SmallWiki' Timestamp: 2004-06-21T20:52:46.7-05:00 Version: 0 Children: 2 Data: Welcome to SmallWiki, a new Wiki-Wiki implementation in Smalltalk. Below you can find a list with the contents of the root folder of this Wiki. By default this list is generated automatically, but you might replace it with your own welcome-message and page-index. !Contents of this Site [ "If you are not logged-in as administrator, please remove everything between the square-brackets before saving the page!" structure renderListOfChildrenOn: html ] --------------- When the wiki is restarted, it scans the description file and loads the latest version of each page/folder/resource. Previous versions are loaded only when they are accessed. It takes less than 20 seconds for #Smalltalk to load my clone of the VW wiki from November -- ~830 pages & ~2MB. With this scheme you can edit the description file, but you really can't edit the detail file. You can append a new item at the end of the file, but if you edit in the middle you will likely mess up the indices. BTW, this scheme doesn't address the problem of resources being stored in memory. For example, if some idiot uploads his 50MB video to your server, it will increase the size of the running program by 50MB. Large resources shouldn't be held in memory -- they should be stored directly to disk. John Brant From johnson at cs.uiuc.edu Tue Jun 22 04:57:17 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Mon, 21 Jun 2004 21:57:17 -0500 Subject: Structures, folders, pages, and resources Message-ID: "Structure" is a bad name. It is vague and can mean just about any thing. PageComponent could be called "structure", too. Maybe rename Structure to WikiComponent. Or call it WikiStructure in the program and in writing but just call it Structure when you are talking. I can now see that SmallWiki is a tree of folders, with leaf nodes being pages and resources. Each folder has its own name space. WikiWorks has two levels, SmallWiki allows an arbitrary number. This is a big difference from other wikis, and you do not emphasize it like you should. How do you link to a page in a different folder? You need to say that when you describe the wiki syntax. Does searching just When you make a link on a page to something, it is created in the same folder that the page is in. A resource is something that is uploaded to the wiki. Are these stored in the image? Wiki.cs.uiuc.edu has over a gigabyte uploaded. I wouldn't want them to be stored in the image! That should be easy to fix by using proxies. Why are the classes List, Document, ListItem, and Paragraph essentially empty? They have no instance variables and only have the one method to support visiting? Is this because any data they hold is in children? -Ralph From dsiegel at acm.org Tue Jun 22 06:14:48 2004 From: dsiegel at acm.org (dsiegel@acm.org) Date: Mon, 21 Jun 2004 23:14:48 -0500 Subject: SmallWiki Persistence In-Reply-To: <200406212342.SAA07327@salad.cs.uiuc.edu> References: <200406212342.SAA07327@salad.cs.uiuc.edu> Message-ID: <20040622031454.HVEZ18566.out011.verizon.net@aSqueakSystem> Ralph Johnson wrote: > > >External SIXX persistance exists. > > I haven't looked at it yet, but I am skeptical. Do you think > it will do what I want? XML is just barely human readable. > It tends to be slow. It is OK for a least common denominator, > but you can almost always do better. I've experimented a bit with SIXX persistence. I had intended to use it to move the contents of a SmallWiki server running on VW to Squeak. There were two problems: a. The root SmallWiki folder has the Swazoo server as a dependent. Consequently, SIXX tries to persist the Swazoo server, and generates noncompliant XML that cannot be parsed. To avoid this, break the dependency before persisting, then restore it. b. The Squeak version is older than the VW, and is missing some classes/inst vars. I didn't explore porting the most current version. As to SIXX as a persistence strategy: Seems to me that SIXX's intended as a maximally portable mechanism for moving data cross-dialect. Readability and performance are not a concern -- the SIXX format is massive, slow and not suitable for modification. I'd aim at database storage for SmallWiki. Postgresql and SQLite seem like good choices. -dms From dsiegel at acm.org Tue Jun 22 06:40:04 2004 From: dsiegel at acm.org (dsiegel@acm.org) Date: Mon, 21 Jun 2004 23:40:04 -0500 Subject: Structures, folders, pages, and resources In-Reply-To: References: Message-ID: <20040622034012.PMEE24784.out014.verizon.net@aSqueakSystem> Ralph Johnson wrote: > How do you link to a page in a different folder? You need to say that when > you describe the wiki syntax. Does searching just See Structure>>resolveTo: I'm not happy with this approach, since it looks up single part names in the root, not the current node. I'd prefer hierarchy style lookup. For example, if the current structure is /Top/Middle, *Leaf* is resolved as /Leaf. I'd prefer /Top/Middle/Leaf. There are also no tools at present for moving structures around the tree. -dms From johnson at cs.uiuc.edu Tue Jun 22 05:51:07 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Mon, 21 Jun 2004 22:51:07 -0500 Subject: My plans for persistence in SmallWiki Message-ID: Here are my current plans. Any comments? Everything will be stored in files. It will be very portable. It will be fast. It will be robust. You can edit all the text files safely. A SmallWiki folder is a directory. It has one directory called resources and one called pages. A page is stored as a text file in the "page" directory. A resource is stored as a binary file in the "resources" directory. A folder will probably have other files in its directory. If we make new kinds of structures, we can make new subdirectories. Each new version of a page gets added to the end of the file. Each delta has a timestamp, the author, maybe the version number, and the data. A timestamp line starts with T, an author line with A, the version number with V, and the data lines with D. The delta ends with a line that starts with E. Lines end with one of a set of end of line characters, including CR and LF. Blank lines are ignored. This should make it so we don't care about the end-of-line rules of the creator of the file, so it should be easy to more from Unix to Windows. Resources are only stored in the file system. Folders and pages are stored in the image. The disk version of the folders and pages are only read when the image is starting up. Otherwise, they are only written to, not read. It should be easy to write the storage manage to handle new pages, new folder, page edits, and resources. However, I am worried about renames. Renaming a file is easy. But don't we also have to change all the files that are in existing pages? Also, I said this is fast, but it has to open a file for each write, and it might be opening files in huge directories. First, there won't be huge directories. If directories get too big then we'll split them. If a directory is "big" (for some definition of big) then it will divide its contents into groups with the same first letter in their name. If it is really big then it will divide them into groups with the same first two letters in their name. Also, the storage manager could cache open files. It could try to reuse open files and close them on a LRU basis. Since there is a lot of locality of writing, this should reduce the number of file opens. But I will measure the performance before implementing this, because I am not sure it will be necessary. I am pretty sure the first one will be, though. 10K files in one directory takes a long time to search. In addition to writing a storage manager to update these files, I'll have to write something to build up a wiki from a file system, and will have to make proxies for resources so they don't have to be in the image. Please tell me what is wrong with this. -Ralph Johnson From dsiegel at acm.org Tue Jun 22 07:11:48 2004 From: dsiegel at acm.org (dsiegel@acm.org) Date: Tue, 22 Jun 2004 00:11:48 -0500 Subject: My plans for persistence in SmallWiki In-Reply-To: References: Message-ID: <20040622041152.XRTH3910.out005.verizon.net@aSqueakSystem> Ralph Johnson wrote: > Here are my current plans. Any comments? > > Everything will be stored in files. It will be very portable. It will be > fast. It will be robust. You can edit all the text files safely. > > A SmallWiki folder is a directory. It has one directory called resources > and one called pages. A page is stored as a text file in the "page" > directory. A resource is stored as a binary file in the "resources" > directory. A folder will probably have other files in its directory. If we > make new kinds of structures, we can make new subdirectories. > > Each new version of a page gets added to the end of the file. Each delta > has a timestamp, the author, maybe the version number, and the data. A > timestamp line starts with T, an author line with A, the version number with > V, and the data lines with D. The delta ends with a line that starts with > E. Lines end with one of a set of end of line characters, including CR and > LF. Blank lines are ignored. This should make it so we don't care about > the end-of-line rules of the creator of the file, so it should be easy to > more from Unix to Windows. Make it easier to retrieve the current version. Why not store the current version in its own file, and the history in a second? I'd expect reads to dominate writes. Some version control systems have taken this approach. > Resources are only stored in the file system. Folders and pages are stored > in the image. The disk version of the folders and pages are only read when > the image is starting up. Otherwise, they are only written to, not read. > > It should be easy to write the storage manage to handle new pages, new > folder, page edits, and resources. However, I am worried about renames. > Renaming a file is easy. But don't we also have to change all the files > that are in existing pages? Absolutely. With this kind of approach, you've got to traverse the entire tree, rewriting references as needed. This is part of the reason I was leaning to a database approach, and maintaining dependency links. On the other hand, renames shouldn't be that common, and your approach's simpler. Another reason I was thinking about database storage, is that I'd like to support placing objects on pages, and treating pages as collections of articles and objects. An object might be a query that retrieves a set of objects to form the page. This is all a significant step beyond a traditional Wiki, though. -dms From ducasse at iam.unibe.ch Tue Jun 22 07:47:36 2004 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Tue, 22 Jun 2004 07:47:36 +0200 Subject: SmallWiki Persistence In-Reply-To: <200406212309.SAA07230@salad.cs.uiuc.edu> References: <200406212309.SAA07230@salad.cs.uiuc.edu> Message-ID: Hi ralph having a persistence mechanism for smallWiki would be excellent. We are aware of that but we did not find the time. The news from SmallWiki are: - We would like to integrate the new security model we have. - We hope to have a new version of SmallWiki working on top of Seaside. We will discuss than this friday. Ideally we hope to have something on by the end of the first week of July. Stef On 22 juin 04, at 01:09, Ralph Johnson wrote: > It appears to me that the only SmallWiki persistence mechanism > so far is to save the entire image. Is that correct? I'd like > a persistence mechanism a bit more like that of WikiWorks. > > Having used WikiWorks for a long time, I'd like to improve upon it. > In particular, file names should be meaningful, and all the versions > of a page should be stored in one file. It should be easy to delete > past history. The file format should make the system very tolerant > of crashes. It should be plain text and easy to edit with any text > editor. > > wiki.cs.uiuc.edu has 33 wikis on it. Most of them are small, but at > least three of them have several thousand pages apiece. The image > is over 100 meg, since all pages are stored in memory (like SmallWiki). > When the machine pages, I will buy more memory. It gets several hits > a second, all day long. It runs for several months between reboots. > I need a persistence mechanism that can handle this. > -Ralph Johnson > From ducasse at iam.unibe.ch Tue Jun 22 08:05:51 2004 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Tue, 22 Jun 2004 08:05:51 +0200 Subject: Structures, folders, pages, and resources In-Reply-To: <20040622034012.PMEE24784.out014.verizon.net@aSqueakSystem> References: <20040622034012.PMEE24784.out014.verizon.net@aSqueakSystem> Message-ID: <3690A496-C412-11D8-985D-000A9573EAE2@iam.unibe.ch> Hi On 22 juin 04, at 06:40, dsiegel at acm.org wrote: > Ralph Johnson wrote: >> How do you link to a page in a different folder? You need to say >> that when >> you describe the wiki syntax. Does searching just > > See Structure>>resolveTo: > > I'm not happy with this approach, since it looks > up single part names in the root, not the current > node. I'd prefer hierarchy style lookup. > > For example, if the current structure is > /Top/Middle, *Leaf* is resolved as /Leaf. > I'd prefer /Top/Middle/Leaf. > > There are also no tools at present for moving > structures around the tree. David vogel has been developing an interface to move/cut/paste tree around and a new security model but this has not been integrated into the latest release. We hope to know more by friday. > > -dms > From renggli at iam.unibe.ch Tue Jun 22 08:08:30 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 22 Jun 2004 08:08:30 +0200 Subject: configuring SmallWiki In-Reply-To: <17071.213.84.174.51.1087859028.squirrel@webmail.xs4all.nl> References: <200406212217.RAA07134@salad.cs.uiuc.edu> <17071.213.84.174.51.1087859028.squirrel@webmail.xs4all.nl> Message-ID: <959124FE-C412-11D8-9032-000393CFE6C8@iam.unibe.ch> > Just make a new link like *new folder*. Then save the > document and choose Folder. If you prefer the workspace do: server root add: (Folder title: 'My New Folder') Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org From renggli at iam.unibe.ch Tue Jun 22 08:08:31 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 22 Jun 2004 08:08:31 +0200 Subject: SmallWiki Persistence In-Reply-To: <200406212342.SAA07327@salad.cs.uiuc.edu> References: <200406212342.SAA07327@salad.cs.uiuc.edu> Message-ID: <9667BA52-C412-11D8-9032-000393CFE6C8@iam.unibe.ch> >> External SIXX persistance exists. > > I haven't looked at it yet, but I am skeptical. Do you think > it will do what I want? XML is just barely human readable. > It tends to be slow. It is OK for a least common denominator, > but you can almost always do better. Yes, SIXX is very slow and not recommended for daily use. It didn't work on it for about a year and I suggest to use it solely to move wikis from one image to another one. Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org From renggli at iam.unibe.ch Tue Jun 22 08:08:34 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 22 Jun 2004 08:08:34 +0200 Subject: Structures, folders, pages, and resources In-Reply-To: References: Message-ID: <97C55152-C412-11D8-9032-000393CFE6C8@iam.unibe.ch> > I can now see that SmallWiki is a tree of folders, with leaf nodes > being > pages and resources. Each folder has its own name space. WikiWorks > has two > levels, SmallWiki allows an arbitrary number. This is a big > difference from > other wikis, and you do not emphasize it like you should. See chapter 3.2, page 16 in the documentation. > How do you link to a page in a different folder? You need to say that > when > you describe the wiki syntax. Does searching just Using absolute paths, e.g. */Folder/Subfolder/My Page* > When you make a link on a page to something, it is created in the same > folder that the page is in. Yes, except for folders, if you create a link from a folder it points to one of its children by default. > A resource is something that is uploaded to the wiki. Are these > stored in > the image? Wiki.cs.uiuc.edu has over a gigabyte uploaded. I wouldn't > want > them to be stored in the image! That should be easy to fix by using > proxies. Yes, the data is currently kept in the image. Fixing this problem should be easy, indeed. > Why are the classes List, Document, ListItem, and Paragraph essentially > empty? They have no instance variables and only have the one method to > support visiting? Is this because any data they hold is in children? These are essentially classes that have a collection of children, see the implementation of the superclass DocumentComposite. Different classes are basically needed, because they represent different entities in the parse-tree of the wiki that are rendered (or more generally, visited) differently. Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org From renggli at iam.unibe.ch Tue Jun 22 08:08:46 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 22 Jun 2004 08:08:46 +0200 Subject: Structures, folders, pages, and resources In-Reply-To: <20040622034012.PMEE24784.out014.verizon.net@aSqueakSystem> References: <20040622034012.PMEE24784.out014.verizon.net@aSqueakSystem> Message-ID: <9F1D1A37-C412-11D8-9032-000393CFE6C8@iam.unibe.ch> > There are also no tools at present for moving > structures around the tree. There are, but as an extension to SmallWiki. David could you point out how to install and use your tool? Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org From renggli at iam.unibe.ch Tue Jun 22 08:08:49 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 22 Jun 2004 08:08:49 +0200 Subject: My plans for persistence in SmallWiki In-Reply-To: References: Message-ID: Some thoughts and additions: > A SmallWiki folder is a directory. There are several extentsions available that subclass from folder (e.g. Photo Folder), they should be handled properly as well. > It has one directory called resources > and one called pages. A page is stored as a text file in the "page" > directory. A resource is stored as a binary file in the "resources" > directory. A folder will probably have other files in its directory. > If we > make new kinds of structures, we can make new subdirectories. I don't understand why a pages and resources are handled differently (pages are put into the directory, resources get an extra directory). Maybe pages and folders should be put into some artificial folders (e.g. _classname_) as well, so that there is more of an uniformity: /_Folder_ SubFolder1 SubFolder2 /_Page_ Page1 Page2 /_Resource_ Resource2 /_Glossary_ Entry2 Or more simple (shouldn't we do it as simple as possible?) one could put all the data into the same directory and to put the type/class-name as file-extension: SubFolder1.Folder SubFolder2.Folder Page1.Page Page2.Page Resource2.Resource Entry2.Glossary > Each new version of a page gets added to the end of the file. Each > delta > has a timestamp, the author, maybe the version number, and the data. A > timestamp line starts with T, an author line with A, the version > number with > V, and the data lines with D. The delta ends with a line that starts > with > E. Lines end with one of a set of end of line characters, including > CR and > LF. Blank lines are ignored. This should make it so we don't care > about > the end-of-line rules of the creator of the file, so it should be easy > to > more from Unix to Windows. Personally, I prefer to have human-readable tags (like the ones suggested by John Brant). Also name-clashes from different extensions are less probably if proper names are used. > It should be easy to write the storage manage to handle new pages, new > folder, page edits, and resources. However, I am worried about > renames. > Renaming a file is easy. But don't we also have to change all the > files > that are in existing pages? Yes, this is a problem. In the very beginning of SmallWiki I used weak-object-references to represent links, so this was very cool: Whenever a page got renamed, moved or deleted the whole wiki-composite was kept in a well defined state automatically and all the links were still valid (nil, if the target has been deleted). Unfortunately this approach lead to problems with platform portability and also storing the structure was more difficult. So I went back to have strings representing the references, what is the worst thing in SmallWiki in my opinion. Currently I have no better solution: when renaming a page I have to walk over the whole wiki using a visitor and change all the strings, however this works only for leave nodes :( > In addition to writing a storage manager to update these files, I'll > have to > write something to build up a wiki from a file system, and will have > to make > proxies for resources so they don't have to be in the image. There are lots of visitors walking over the whole structure (e.g. to create the rss-feed, the history, the search engine, ....) so this should be efficiently possible. Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org From vogel at iam.unibe.ch Tue Jun 22 09:12:43 2004 From: vogel at iam.unibe.ch (David Vogel) Date: Tue, 22 Jun 2004 09:12:43 +0200 Subject: Structures, folders, pages, and resources In-Reply-To: <9F1D1A37-C412-11D8-9032-000393CFE6C8@iam.unibe.ch> References: <20040622034012.PMEE24784.out014.verizon.net@aSqueakSystem> <9F1D1A37-C412-11D8-9032-000393CFE6C8@iam.unibe.ch> Message-ID: <1087888363.40d7dbeb5576a@www.iam.unibe.ch> hi, see: http://impara.de/pipermail/smallwiki/2004-April/001815.html better use the admin package called Smallwiki.AdminDefault for now. if you have more questions on it fell free to ask. cheers, david. Zitat von Lukas Renggli : > > There are also no tools at present for moving > > structures around the tree. > > There are, but as an extension to SmallWiki. David could you point out > how to install and use your tool? > > Cheers, > Lukas > > -- > Lukas Renggli > http://renggli.freezope.org > > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From johnson at cs.uiuc.edu Tue Jun 22 12:17:02 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Tue, 22 Jun 2004 05:17:02 -0500 (CDT) Subject: SmallWiki Persistence Message-ID: <200406221017.FAA08871@salad.cs.uiuc.edu> >We hope to have a new version of SmallWiki working on top of Seaside. Seaside is cool. However, I hope that using Seaside does not mess up URLs. It is important that all pages have URLs that are easy to reference from outside the wiki. Actions do not need stable URLs, though. If it is on Seaside, does this mean that you are abandoning Swazoo? -Ralph From johnson at cs.uiuc.edu Tue Jun 22 12:43:42 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Tue, 22 Jun 2004 05:43:42 -0500 (CDT) Subject: Structures, folders, pages, and resources Message-ID: <200406221043.FAA08936@salad.cs.uiuc.edu> >> I can now see that SmallWiki is a tree of folders, with leaf nodes >> being >> pages and resources. Each folder has its own name space. WikiWorks >> has two >> levels, SmallWiki allows an arbitrary number. This is a big >> difference from >> other wikis, and you do not emphasize it like you should. >See chapter 3.2, page 16 in the documentation. That is completely inadequate. I had read it several times before posting my message. If I did not understand it, few people will. Class hierarchies are abstract. People do not learn how to use an abstraction by reading the abstraction. They learn abstractions by learning examples. Your documentation needs to be more concrete. It should be based on using a wiki, not on looking at the Smalltalk code. Once people know what SmallWiki does then you can give them class diagrams and they will make sense. "Structure" is a wretched name. It is too vague. Section 3.2 is too abstract. It says little that I couldn't get by reading the code. The result is that the section makes sense only AFTER someone has figured out SmallWiki. A structure "represents the model of a single page". But there is a Page class, as well. This is confusing. I think that what is important about Structure is that it has a URL. Though actions also have URLs. If a structure is a model, what are its observers? The storage manager is one. Anything else? -Ralph From johnson at cs.uiuc.edu Tue Jun 22 12:57:44 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Tue, 22 Jun 2004 05:57:44 -0500 (CDT) Subject: My plans for persistence in SmallWiki Message-ID: <200406221057.FAA08976@salad.cs.uiuc.edu> Writes will dominate reads, because once the wiki is loaded from the file system, pages and folders will never be read. Only resources will be read. Keeping everything in memory is good because it is fast and easy. Memory is cheap. If I can run wiki.cs.uiuc.edu on a 200 Mhz machine then it is proof that big systems can run on old computers if you store it all in memory. I avoid database systems when I can. Smalltalk is more powerful than a RDBMS. The file system is mostly to prevent loss of data. This works until your image gets to 4G (which has never happened to me). Then you have to move to a 64 bit Smalltalk. -Ralph From johnson at cs.uiuc.edu Tue Jun 22 13:23:58 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Tue, 22 Jun 2004 06:23:58 -0500 (CDT) Subject: My plans for persistence in SmallWiki Message-ID: <200406221123.GAA09758@salad.cs.uiuc.edu> >I don't understand why a pages and resources are handled differently >(pages are put into the directory, resources get an extra directory). That is not what I meant. Pages get an extra directory, too. I didn't mention folders, but they should get an extra directory. >Maybe pages and folders should be put into some artificial folders >(e.g. _classname_) as well, so that there is more of an uniformity: Yes, that is what I want. If we use _classname_ then it should be possible for someone to add a new class and for the storage manager to automatically add it. >Or more simple (shouldn't we do it as simple as possible?) one could >put all the data into the same directory and to put the type/class-name >as file-extension: I don't think it is simpler. I think that the subdirectory is just as easy to program, maybe simpler. And it has the added benefit of making directories smaller, thus making open() be faster. >Personally, I prefer to have human-readable tags (like the ones >suggested by John Brant). Also name-clashes from different extensions I want to tag every line so that the system can better handle the case where only half of the page is written. Note that there will probably only be one class that writes these tags, so different extensions will have to worry about clashes to this class anyway. -Ralph From johnson at cs.uiuc.edu Tue Jun 22 14:45:03 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Tue, 22 Jun 2004 07:45:03 -0500 Subject: Security test case Message-ID: I have been wanting a wiki to do the following thing for a long time. It looks to me like SmallWiki will make it much easier. Your comments on persistence were helpful, so I would like to discuss this for awhile. I teach a course in which students do most of the lecturing. We read several books, and each student presents a chapter. They also write a couple of study questions, and students are expected to read the chapter and answer the study questions. The presenter will grade the answers. I'd like to do it on the wiki. At first, all answers are secret. Students can read what they wrote, but nobody else can. Except the presenter/grader. Once the answers are graded, the grader will publish them, making special notes of the good ones. Here is how I think it will work. I'll need a new kind of structure called a "virtual folder". First, each student has their own folder named after their UIUC net ID. There will be a folder called Students and it has subfolders for each student. A students subfolder is private. The students create pages called "chapter 1" and "chapter 2" for their answers. The administrator will create a special page in the folder of the grader. This is the virtual folder, which is a capability page. It pretends to be a folder with all the answers in it. It might be called "chapter 1 answers" and it will be parameterized to show all the pages in subfolders of Students that are called "chapter 1". The grader will make a new page that discusses the answers, says which ones are especially good, and contains pointers to them. Then he will publish the page in read-only mode. The virtual folder is a way of changing roles of structure. Pages in it will use the security policies that it defines rather than the policies of their own folder. >From my quick reading of the security paper, it appears that security is implemented using Chain of Responsibility from the root, which means that structure inherits from its parent because control passes through the parent. Therefore, a virtual folder should be able to change security policies. In contrast, if security was implemented by having each structure ask its parent whenever it needed a security policy, this would not work. So, what do you think? Is there already a virtual folder class? If not, will it be hard to make? -Ralph Johnson From renggli at iam.unibe.ch Tue Jun 22 15:34:55 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 22 Jun 2004 15:34:55 +0200 Subject: Security test case In-Reply-To: References: Message-ID: > From my quick reading of the security paper, it appears that security > is > implemented using Chain of Responsibility from the root, which means > that > structure inherits from its parent because control passes through the > parent. Yes, it is implemented using the Chain of Responsiblity Pattern, but it starts even before the root. The security roles and its permissions are initialized from the settings of the server (if I remember correctly the security-extensions of David change this behaviour somehow). While doing to look-up of the URL each structure (mostly folders are used to do this, but it can be also done at page level) has the possibility to replace the role definition. > So, what do you think? Is there already a virtual folder class? If > not, > will it be hard to make? I don't think that implementing something like this is difficult. However building an user-interface to make it easily useable is more difficult, this will certainly change as soon as SmallWiki is based on Seaside. Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org From cputney at wiresong.ca Tue Jun 22 16:44:36 2004 From: cputney at wiresong.ca (Colin Putney) Date: Tue, 22 Jun 2004 09:44:36 -0500 Subject: SmallWiki Persistence In-Reply-To: <200406221017.FAA08871@salad.cs.uiuc.edu> References: <200406221017.FAA08871@salad.cs.uiuc.edu> Message-ID: On Jun 22, 2004, at 5:17 AM, Ralph Johnson wrote: > Seaside is cool. However, I hope that using Seaside does not mess > up URLs. It is important that all pages have URLs that are easy to > reference from outside the wiki. Actions do not need stable URLs, > though. > > If it is on Seaside, does this mean that you are abandoning Swazoo? Hi Ralph, It's good to see you'll be working on this stuff at CS. A couple of data points on Seaside. First, Seaside does provide a mechanism for providing stable URLs to specific resources, it just doesn't to it by default. So with a little care, this should be fine. Second, Seaside doesn't provide a full web server of its own, it relies on being plugged into an external server. On Squeak this is Comanche or Swazoo, and I believe the VW port can use Swazoo as well, though I'm not current on that. In any case it would be easy to implement if it's not done already: I connected Seaside to a stripped-down version of Swazoo in Squeak by implementing one class with a handful of methods. So congrats to the SCG guys on taking this step, I think it will be a big win in terms of being able to integrate robust wikis into other Seaside apps. Colin From michael.cole at nimiq.net Tue Jun 22 16:23:32 2004 From: michael.cole at nimiq.net (michael.cole@nimiq.net) Date: Tue, 22 Jun 2004 08:23:32 -0600 Subject: Restoring SmallWiki using SIXX Message-ID: <20040622152329.15EC6292C6@carmine.bestweb.net> Hi, Is there a resource describing the procedure to restore a SmallWiki using SIXX and the root.xml object file? Simply reading the root.xml file returns parser errors under Squeak3.7 Thanks, Michael Cole michael.cole at nimiq.net From renggli at iam.unibe.ch Wed Jun 23 12:22:07 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 23 Jun 2004 12:22:07 +0200 Subject: Smallwiki question In-Reply-To: <827F6BB0-C4F8-11D8-A11F-000A957C9CB2@iam.unibe.ch> References: <5EACA7DC-C4E5-11D8-93D2-000A958EE9C4@iam.unibe.ch> <019BE85D-C4E9-11D8-A69F-000393CFE6C8@iam.unibe.ch> <827F6BB0-C4F8-11D8-A11F-000A957C9CB2@iam.unibe.ch> Message-ID: <2E341D3C-C4FF-11D8-A69F-000393CFE6C8@iam.unibe.ch> Yes, this is true. As Folder is a subclass of Page, a folder inherits all the functionality of a page and adds the possibility to have children. The reason for making this difference between Pages and Folders is that the look-up is different: if you have a link like *Other*, a folder looks for a child named 'Other' while a page looks for a matching brother/sister. This difference applies also while creating new structural entities in SmallWiki. What is more, folders do automatically render a list of their children if the default content isn't changed. And, as you can see on the ESUG web-page (http://www.esug.org), the menu-template renders slightly different when the current structure has the possibility to contain children. Cheers, Lukas On Jun 23, 2004, at 11:34, Oscar Nierstrasz wrote: > > Actually, I never understood the need to distinguish pages and folders. > Why not just have PageFolders? Pages with contents, and the > possibilities to add subpages? > > Oscar > > On Jun 23, 2004, at 9:43, Lukas Renggli wrote: > >> Hi Oscar >> >>> I would like the Traits page in the SCG Smallwiki to be >>> turned into a folder. Is there a way to do this? >> >> No, currently there is no easy way to do this. You have to create a >> new folder, copy the content of the old page to the new folder and >> then delete the old page. >> >> The good news: We were brainstorming with Roel yesterday about having >> a refactoring tool for Smallwiki that should be able to do such a >> conversion (and other things) more easily. >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://renggli.freezope.org >> > -- Lukas Renggli http://renggli.freezope.org From renggli at iam.unibe.ch Wed Jun 23 12:22:07 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 23 Jun 2004 12:22:07 +0200 Subject: Smallwiki question In-Reply-To: <827F6BB0-C4F8-11D8-A11F-000A957C9CB2@iam.unibe.ch> References: <5EACA7DC-C4E5-11D8-93D2-000A958EE9C4@iam.unibe.ch> <019BE85D-C4E9-11D8-A69F-000393CFE6C8@iam.unibe.ch> <827F6BB0-C4F8-11D8-A11F-000A957C9CB2@iam.unibe.ch> Message-ID: <2E341D3C-C4FF-11D8-A69F-000393CFE6C8@iam.unibe.ch> Yes, this is true. As Folder is a subclass of Page, a folder inherits all the functionality of a page and adds the possibility to have children. The reason for making this difference between Pages and Folders is that the look-up is different: if you have a link like *Other*, a folder looks for a child named 'Other' while a page looks for a matching brother/sister. This difference applies also while creating new structural entities in SmallWiki. What is more, folders do automatically render a list of their children if the default content isn't changed. And, as you can see on the ESUG web-page (http://www.esug.org), the menu-template renders slightly different when the current structure has the possibility to contain children. Cheers, Lukas On Jun 23, 2004, at 11:34, Oscar Nierstrasz wrote: > > Actually, I never understood the need to distinguish pages and folders. > Why not just have PageFolders? Pages with contents, and the > possibilities to add subpages? > > Oscar > > On Jun 23, 2004, at 9:43, Lukas Renggli wrote: > >> Hi Oscar >> >>> I would like the Traits page in the SCG Smallwiki to be >>> turned into a folder. Is there a way to do this? >> >> No, currently there is no easy way to do this. You have to create a >> new folder, copy the content of the old page to the new folder and >> then delete the old page. >> >> The good news: We were brainstorming with Roel yesterday about having >> a refactoring tool for Smallwiki that should be able to do such a >> conversion (and other things) more easily. >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://renggli.freezope.org >> > -- Lukas Renggli http://renggli.freezope.org From oscar at iam.unibe.ch Wed Jun 23 13:54:35 2004 From: oscar at iam.unibe.ch (Oscar Nierstrasz) Date: Wed, 23 Jun 2004 13:54:35 +0200 Subject: Smallwiki question In-Reply-To: <2E341D3C-C4FF-11D8-A69F-000393CFE6C8@iam.unibe.ch> References: <5EACA7DC-C4E5-11D8-93D2-000A958EE9C4@iam.unibe.ch> <019BE85D-C4E9-11D8-A69F-000393CFE6C8@iam.unibe.ch> <827F6BB0-C4F8-11D8-A11F-000A957C9CB2@iam.unibe.ch> <2E341D3C-C4FF-11D8-A69F-000393CFE6C8@iam.unibe.ch> Message-ID: <18CC4A06-C50C-11D8-BEAE-000A957C9CB2@iam.unibe.ch> From a user's point of view, this is not necessarily what you want. It would be very useful to be able to add children to any page. Also, to be able to transparently move pages around, just as one can move files between directories ... My 2 Rappen's worth. Oscar On Jun 23, 2004, at 12:22, Lukas Renggli wrote: > Yes, this is true. As Folder is a subclass of Page, a folder inherits > all the functionality of a page and adds the possibility to have > children. > > The reason for making this difference between Pages and Folders is > that the look-up is different: if you have a link like *Other*, a > folder looks for a child named 'Other' while a page looks for a > matching brother/sister. This difference applies also while creating > new structural entities in SmallWiki. > > What is more, folders do automatically render a list of their children > if the default content isn't changed. And, as you can see on the ESUG > web-page (http://www.esug.org), the menu-template renders slightly > different when the current structure has the possibility to contain > children. > > Cheers, > Lukas > > On Jun 23, 2004, at 11:34, Oscar Nierstrasz wrote: > >> >> Actually, I never understood the need to distinguish pages and >> folders. >> Why not just have PageFolders? Pages with contents, and the >> possibilities to add subpages? >> >> Oscar >> >> On Jun 23, 2004, at 9:43, Lukas Renggli wrote: >> >>> Hi Oscar >>> >>>> I would like the Traits page in the SCG Smallwiki to be >>>> turned into a folder. Is there a way to do this? >>> >>> No, currently there is no easy way to do this. You have to create a >>> new folder, copy the content of the old page to the new folder and >>> then delete the old page. >>> >>> The good news: We were brainstorming with Roel yesterday about >>> having a refactoring tool for Smallwiki that should be able to do >>> such a conversion (and other things) more easily. >>> >>> Cheers, >>> Lukas >>> >>> -- >>> Lukas Renggli >>> http://renggli.freezope.org >>> >> > -- > Lukas Renggli > http://renggli.freezope.org > From johnson at cs.uiuc.edu Wed Jun 23 16:41:52 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Wed, 23 Jun 2004 09:41:52 -0500 (CDT) Subject: Smallwiki question Message-ID: <200406231441.JAA13384@salad.cs.uiuc.edu> > From a user's point of view, this is not necessarily what you want. >It would be very useful to be able to add children to any page. >Also, to be able to transparently move pages around, just as one can >move files between directories ... To me, this looks like two refactorings; convert page to folder and move structure. -Ralph From Andreas.Semt at gmx.net Wed Jun 23 20:26:11 2004 From: Andreas.Semt at gmx.net (Andreas Semt) Date: Wed, 23 Jun 2004 20:26:11 +0200 Subject: A newbie question Message-ID: <40D9CB43.4020109@gmx.net> Hello list! This is my first post on the list and i hope the question is not too "newbie" ... I am using VisualWorks Non Commercial 7.2 and installed SmallWiki 0.9.48 from Cincom-Store. So now I try to setup SmallWiki described on http://kilana.unibe.ch:9090/smallwiki/smallwikisetup/ and run the tests. However I am new to Smalltalk (also VisualWorks) and to SmallWiki so I don't know how to "Select all the test-cases and click on run." Can anybody give me some advices how to run the tests in VisualWorks? A lot of thanks in advance! Best regards, Andreas Semt From johnson at cs.uiuc.edu Wed Jun 23 20:59:32 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Wed, 23 Jun 2004 13:59:32 -0500 (CDT) Subject: A newbie question Message-ID: <200406231859.NAA14384@salad.cs.uiuc.edu> A word of warning: when I tried this last week, I ran into a problem. John Brant said that the latest version of Swazoo had a problem with Windows. Once I realized that, I was able to fix it pretty easily. Perhaps Swazoo is fixed now, or perhaps you are not using Windows. But if you are having problems with it, let me know and I wlil send you the fix. -Ralph Johnson From Andreas.Semt at gmx.net Wed Jun 23 23:28:56 2004 From: Andreas.Semt at gmx.net (Andreas Semt) Date: Wed, 23 Jun 2004 23:28:56 +0200 Subject: A newbie question In-Reply-To: <200406231859.NAA14384@salad.cs.uiuc.edu> References: <200406231859.NAA14384@salad.cs.uiuc.edu> Message-ID: <40D9F618.1050705@gmx.net> Ralph Johnson wrote: > A word of warning: when I tried this last week, I ran into a problem. > John Brant said that the latest version of Swazoo had a problem with > Windows. Once I realized that, I was able to fix it pretty easily. > Perhaps Swazoo is fixed now, or perhaps you are not using Windows. > But if you are having problems with it, let me know and I wlil > send you the fix. > > -Ralph Johnson > Hello Ralph, yes i am using Windows 2000 Pro (SP4) and Swazoo 0.9.76-bb28 also from Cincom-Store. However I don't know if that means problems because I don't know HOW to run the tests under VisualWorks 7.2. Where can I find the SUnit tests of SmallWiki and HOW can I execute them (i am *really* a Smalltalk newbie)? Best regards, Andreas Semt From johnson at cs.uiuc.edu Thu Jun 24 05:35:31 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Wed, 23 Jun 2004 22:35:31 -0500 (CDT) Subject: A newbie question Message-ID: <200406240335.WAA15644@salad.cs.uiuc.edu> You can get the test runner by typing "TestRunner open" in a workspace (really, anyplace that you can type text) and then selecting it and choosing "doit" from the menu. This is how you evaluate a Smalltalk expression. If you read the SmallWiki workspace then you will see that you evaluate expressions like server := SmallWiki.SwazooServer startOn: 8080 to start up the wiki server. But you wanted to run tests. The test runner has a bunch of tests, which you can see on the pulldown list at the top of the test runner window. Ideally, you could just press "RunAll", except that you will see that nine tests fail. They are mostly in Swazoo, a package that SmallWiki uses. This is with VW7.2 on Windows. John Brant suggested that the problem was in OSkSocket>>setAddressReuse: I commented out the big message to self by putting " around "self setOptionForLevel: ... value: optionValue" Then I could start the wiki, but one of the tests still failed. It was Swazoo.SwazooSocketTest>>#testReadTimeout. I read this test, and discovered that it reads from a socket and sets a timeout, but for some reason the timeout never happens. It is only supposed to wait for .2 seconds, but it waits forever. This is with VW7.2 on Windows. You can select tests one after another Novices shouldn't have to fix this. Wait until the authors fix the problem. -Ralph Johnson From ducasse at iam.unibe.ch Thu Jun 24 11:04:26 2004 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Thu, 24 Jun 2004 11:04:26 +0200 Subject: A newbie question In-Reply-To: <200406240335.WAA15644@salad.cs.uiuc.edu> References: <200406240335.WAA15644@salad.cs.uiuc.edu> Message-ID: <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> Hi lukas could you specify in the bundle the right version of swazoo so that we can have a one click loadable SW? Stef ph Johnson wrote: > Novices shouldn't have to fix this. Wait until the authors > fix the problem. > > -Ralph Johnson From renggli at iam.unibe.ch Thu Jun 24 11:56:57 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 24 Jun 2004 11:56:57 +0200 Subject: A newbie question In-Reply-To: <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> References: <200406240335.WAA15644@salad.cs.uiuc.edu> <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> Message-ID: > could you specify in the bundle the right version of swazoo so that we > can have a one click loadable SW? It is load-able with one click into a clean 7.2 image now. And all SW tests run green. Lukas > ph Johnson wrote: > >> Novices shouldn't have to fix this. Wait until the authors >> fix the problem. >> >> -Ralph Johnson -- Lukas Renggli http://renggli.freezope.org From ducasse at iam.unibe.ch Thu Jun 24 13:13:11 2004 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Thu, 24 Jun 2004 13:13:11 +0200 Subject: A newbie question In-Reply-To: References: <200406240335.WAA15644@salad.cs.uiuc.edu> <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> Message-ID: <7A695169-C5CF-11D8-8179-000A9573EAE2@iam.unibe.ch> >> could you specify in the bundle the right version of swazoo so that >> we can have a one click loadable SW? > > It is load-able with one click into a clean 7.2 image now. And all SW > tests run green. Thanks lukas. I appreciate your efforts. This often difficult to have clients :) > > Lukas From Andreas.Semt at gmx.net Thu Jun 24 13:50:45 2004 From: Andreas.Semt at gmx.net (Andreas Semt) Date: Thu, 24 Jun 2004 13:50:45 +0200 Subject: A newbie question In-Reply-To: References: <200406240335.WAA15644@salad.cs.uiuc.edu> <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> Message-ID: <40DAC015.3040204@gmx.net> Hello Lukas, Lukas Renggli wrote: >> could you specify in the bundle the right version of swazoo so that we >> can have a one click loadable SW? > > > It is load-able with one click into a clean 7.2 image now. And all SW > tests run green. > I loaded the new version of SmallWiki (0.9.50) from Cincom-Store. However the test "Swazoo.ACLResourceTest" hangs at "Swazoo.SwazooSocketTest>>#testReadTimeout" on Windows 2000 (SP4) with VW7.2. Does that mean i can't use SmallWiki? Best regards, Andreas Semt From avanos at xs4all.nl Thu Jun 24 14:53:18 2004 From: avanos at xs4all.nl (Adriaan van Os) Date: Thu, 24 Jun 2004 14:53:18 +0200 (CEST) Subject: escape smilies In-Reply-To: <7A695169-C5CF-11D8-8179-000A9573EAE2@iam.unibe.ch> References: <200406240335.WAA15644@salad.cs.uiuc.edu> <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> <7A695169-C5CF-11D8-8179-000A9573EAE2@iam.unibe.ch> Message-ID: <6494.62.58.162.194.1088081598.squirrel@webmail.xs4all.nl> Hoi Lukas, Thanks for the smilies :). I just figured how to escape them. Eg., for :) using \:) or \:\) or even :) doesn't work. But :) does. Adriaan. -- http://vdg38bis.xs4all.nl From renggli at iam.unibe.ch Thu Jun 24 17:38:38 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 24 Jun 2004 17:38:38 +0200 Subject: escape smilies In-Reply-To: <6494.62.58.162.194.1088081598.squirrel@webmail.xs4all.nl> References: <200406240335.WAA15644@salad.cs.uiuc.edu> <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> <7A695169-C5CF-11D8-8179-000A9573EAE2@iam.unibe.ch> <6494.62.58.162.194.1088081598.squirrel@webmail.xs4all.nl> Message-ID: <8FADF3CB-C5F4-11D8-A69F-000393CFE6C8@iam.unibe.ch> > Thanks for the smilies :). Ehh, the smilies are an extension made by 'David R?thlisberger' some time ago. You have to send your thank-you to him, I'm sorry that it took me a lot of time to finally publish all the changes from my image ;) Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org From Andreas.Semt at gmx.net Sat Jun 26 02:18:37 2004 From: Andreas.Semt at gmx.net (Andreas Semt) Date: Sat, 26 Jun 2004 02:18:37 +0200 Subject: A newbie question In-Reply-To: References: <200406240335.WAA15644@salad.cs.uiuc.edu> <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> Message-ID: <40DCC0DD.6050404@gmx.net> Lukas Renggli wrote: >> could you specify in the bundle the right version of swazoo so that we >> can have a one click loadable SW? > > > It is load-able with one click into a clean 7.2 image now. And all SW > tests run green. Do you also use Windows 2000 as platform? Test hangs at "Swazoo.SwazooSocketTest>>#testReadTimeout" on my pc (version 0.9.50/51 and clean VW 7.2). Any suggestions how to fix that problem? Again: THANKS for help! Greetings, Andreas Semt From umejava at mars.dti.ne.jp Sat Jun 26 08:08:20 2004 From: umejava at mars.dti.ne.jp (Masashi Umezawa) Date: Sat, 26 Jun 2004 15:08:20 +0900 Subject: Restoring SmallWiki using SIXX In-Reply-To: <20040622152329.15EC6292C6@carmine.bestweb.net> References: <20040622152329.15EC6292C6@carmine.bestweb.net> Message-ID: Hi, Tue, 22 Jun 2004 08:23:32 -0600 michael.cole at nimiq.net wrote: > Hi, > > Is there a resource describing the procedure to restore a SmallWiki > using SIXX and the root.xml object file? > > Simply reading the root.xml file returns parser errors under Squeak3.7 Did you install YAXO before SIXX? In Squeak 3.7, YAXO was removed from the basic image. And SIXX installer was written in 3.6, assuming YAXO is in the image. So, if you use 3.7, you have to install YAXO manually. Sorry for inconvenience. I'll update SIXX(and installer) soon. Cheers, --- [:masashi | ^umezawa] From gtsab at shaw.ca Sat Jun 26 08:35:50 2004 From: gtsab at shaw.ca (Glenn Swanlund) Date: Fri, 25 Jun 2004 23:35:50 -0700 Subject: Reduce Image Size Message-ID: <000001c45b47$d5db9640$2202a8c0@MyToshiba> I've just started playing with SWImageStorage after playing with SWSIXXStorage. With SWImageStorage the image size grows as I add resources. Even when I remove resources, the image size grows. Is there a way to keep the image size down as resources are removed? I tried garbage collecting after removing a resource but this did not help reduce the image size. Regards, Glenn -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20040625/3a8b813d/attachment.htm From ducasse at iam.unibe.ch Sat Jun 26 08:58:49 2004 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sat, 26 Jun 2004 08:58:49 +0200 Subject: Internal plan for 2.0 and other Message-ID: <467E1576-C73E-11D8-8A05-000A9573EAE2@iam.unibe.ch> Hi all we got a meeting yesterday. Here are the basic decisions: Lukas will try to get the core of SmallWiki on Seaside. Monday morning we will know more. Then David Rothlisberger will help lukas porting. But Lukas and david can only afford to spend one day a week on that so if you are a seaside expert, love SmallWiki and have a bit of time, please contact lukas and david rothlisberger. We expect to have something in three weeks at that speed. So if you want to help please do. At that time we will release SmallWiki2.0 We loaded the security bundles available on Cincom store on the kilana wiki to test whether the changes did by david vogel with his extended security model are working on a real case. David will report the problems (bad code) about his code soon. Alex should (he is not aware of that ;)) finish the Swiki importer :) Frederic and I started to work on simple boolean expressions so that we can query the wiki with more advanced queries. We plan to introduce first class tags and some meta description. And frederic will start to build some wiki management tools with tests!!!!. We plan to integrate them on top of SmallWiki 2.0 and release them regularly. Frederic should DESCRIBE what we plan to have at: http://kilana.unibe.ch:9090/smallwiki/inprogresslist/ Stef From renggli at iam.unibe.ch Sat Jun 26 09:12:56 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 26 Jun 2004 09:12:56 +0200 Subject: Reduce Image Size In-Reply-To: <000001c45b47$d5db9640$2202a8c0@MyToshiba> References: <000001c45b47$d5db9640$2202a8c0@MyToshiba> Message-ID: <3F4A6410-C740-11D8-AF71-000393CFE6C8@iam.unibe.ch> > With SWImageStorage the image size grows as I add resources. Even when > I remove resources, the image size grows. Is there a way to keep the > image size down as resources are removed? I tried garbage collecting > after removing a resource but this did not help reduce the image size. SmallWiki does version all changes, therefor even when you delete a resource the amount of the memory consumption grows. In case you accidentally deleted a resource you might restore it at a later point in time. Delete the history of the parent folder to completely release the memory of a deleted page. Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org From johnson at cs.uiuc.edu Sat Jun 26 10:56:32 2004 From: johnson at cs.uiuc.edu (Ralph Johnson) Date: Sat, 26 Jun 2004 03:56:32 -0500 (CDT) Subject: Reduce Image Size Message-ID: <200406260856.DAA24355@salad.cs.uiuc.edu> I intend to change resources so that they are not stored in the image. Once that happens, the problem should go away. -Ralph Johnson From davidroe at bluewin.ch Sat Jun 26 11:02:41 2004 From: davidroe at bluewin.ch (=?iso-8859-1?Q?David_R=F6thlisberger?=) Date: Sat, 26 Jun 2004 11:02:41 +0200 Subject: A newbie question References: <200406240335.WAA15644@salad.cs.uiuc.edu> <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> <40DCC0DD.6050404@gmx.net> Message-ID: <009801c45b5c$587f8ed0$bd2e03d5@david715t080hb> hello, > Do you also use Windows 2000 as platform? Test hangs at > "Swazoo.SwazooSocketTest>>#testReadTimeout" on my pc (version 0.9.50/51 > and clean VW 7.2). Any suggestions how to fix that problem? yes, I have encountered the same problem under WinXP. This seems to be a problem related to Windows, I don't know how to fix it. But that doesn't affect SmallWiki at all, at least I haven't encountered any problems with SmallWiki related to this issue of Swazoo. When all the tests of SmallWiki run green, everything should be ready to use SW properly, even though the Swazoo tests don't run green. greets David From umejava at mars.dti.ne.jp Sat Jun 26 12:07:15 2004 From: umejava at mars.dti.ne.jp (Masashi Umezawa) Date: Sat, 26 Jun 2004 19:07:15 +0900 Subject: Reduce Image Size In-Reply-To: <3F4A6410-C740-11D8-AF71-000393CFE6C8@iam.unibe.ch> References: <000001c45b47$d5db9640$2202a8c0@MyToshiba> <3F4A6410-C740-11D8-AF71-000393CFE6C8@iam.unibe.ch> Message-ID: Hi, > SmallWiki does version all changes, therefor even when you delete a > resource the amount of the memory consumption grows. In case you > accidentally deleted a resource you might restore it at a later point > in time. > > Delete the history of the parent folder to completely release the > memory of a deleted page. > How about trying to move older versions of resources to some 'old space' (disk storage, using OODB or SIXX) and leave proxies? Older versions are not so frequently referenced. We can apply the strategy of 'generation scavenging' of resources. Cheers, --- [:masashi | ^umezawa] From nevin at bountifulbaby.com Sat Jun 26 22:37:14 2004 From: nevin at bountifulbaby.com (Nevin Pratt) Date: Sat, 26 Jun 2004 13:37:14 -0700 Subject: Reduce Image Size In-Reply-To: <200406260856.DAA24355@salad.cs.uiuc.edu> References: <200406260856.DAA24355@salad.cs.uiuc.edu> Message-ID: <40DDDE7A.8020007@bountifulbaby.com> Ralph Johnson wrote: >I intend to change resources so that they are not >stored in the image. Once that happens, the problem >should go away. > >-Ralph Johnson > > > > For what it's worth, I've never liked the way SmallWiki keeps resources in the image either. In my case (for the Bountiful Baby "Forum"), I completed disabled resource uploading (photos, files, etc). I simply don't allow it _at all_. Each Wiki user must find their own place to store their own required "resources" (photos or whatever), and then they reference those resource links in their Wiki pages, where-ever they might be stored. When I look at photos that are showing up in our Wiki pages, I find that folks are storing them in their own personal AOL accounts, or some other picture host (picturetrail.com, or andale.com, are a couple of common ones). And then the Wiki page just has the familiar html image tags to reference them. Nevin -- Nevin Pratt Bountiful Baby http://www.bountifulbaby.com The Most Complete Reborn Supply Store On The Web! (801) 992-3137 From ducasse at iam.unibe.ch Sun Jun 27 09:59:15 2004 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 27 Jun 2004 09:59:15 +0200 Subject: Reduce Image Size In-Reply-To: <40DDDE7A.8020007@bountifulbaby.com> References: <200406260856.DAA24355@salad.cs.uiuc.edu> <40DDDE7A.8020007@bountifulbaby.com> Message-ID: Hi nevin and others We were never totally satisfied with our solution for resources but this was the simplest one that we could afford to do. We are really interested in the back-end effort led by ralph. Please keep in mind that smallWiki is the result of a project made by lukas nearly alone (With roel we supervised SmallWiki but never really help concretely coding. ), Lukas refactored several time SmallWiki. And the result is quite good. Now Lukas has something else to do even if he is wiling to continue to support SmallWiki. So we are open to any improvements that are sent to us with tests and that do not break our tests (or fix them). Stef On 26 juin 04, at 22:37, Nevin Pratt wrote: > > > Ralph Johnson wrote: > >> I intend to change resources so that they are not >> stored in the image. Once that happens, the problem >> should go away. >> >> -Ralph Johnson >> >> >> > > For what it's worth, I've never liked the way SmallWiki keeps > resources in the image either. In my case (for the Bountiful Baby > "Forum"), I completed disabled resource uploading (photos, files, > etc). I simply don't allow it _at all_. Each Wiki user must find > their own place to store their own required "resources" (photos or > whatever), and then they reference those resource links in their Wiki > pages, where-ever they might be stored. > > When I look at photos that are showing up in our Wiki pages, I find > that folks are storing them in their own personal AOL accounts, or > some other picture host (picturetrail.com, or andale.com, are a couple > of common ones). And then the Wiki page just has the familiar html > image tags to reference them. > > Nevin > > -- > Nevin Pratt > > Bountiful Baby > http://www.bountifulbaby.com > The Most Complete Reborn Supply Store On The Web! > > (801) 992-3137 > > From Andreas.Semt at gmx.net Sun Jun 27 12:57:34 2004 From: Andreas.Semt at gmx.net (Andreas Semt) Date: Sun, 27 Jun 2004 12:57:34 +0200 Subject: A newbie question In-Reply-To: <009801c45b5c$587f8ed0$bd2e03d5@david715t080hb> References: <200406240335.WAA15644@salad.cs.uiuc.edu> <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> <40DCC0DD.6050404@gmx.net> <009801c45b5c$587f8ed0$bd2e03d5@david715t080hb> Message-ID: <40DEA81E.3020707@gmx.net> David R?thlisberger wrote: > hello, > > >>Do you also use Windows 2000 as platform? Test hangs at >>"Swazoo.SwazooSocketTest>>#testReadTimeout" on my pc (version 0.9.50/51 >>and clean VW 7.2). Any suggestions how to fix that problem? > > > yes, I have encountered the same problem under WinXP. This seems to be a > problem related to Windows, I don't know how to fix it. > But that doesn't affect SmallWiki at all, at least I haven't encountered any > problems with SmallWiki related to this issue of Swazoo. When all the tests > of SmallWiki run green, everything should be ready to use SW properly, even > though the Swazoo tests don't run green. Thanks for your answer. Good to know that i can use SmallWiki with that broken Swazoo test. Did you know on which OS the Swazoo tests run green? Best regards, Andreas Semt From renggli at iam.unibe.ch Mon Jun 28 21:57:32 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 28 Jun 2004 21:57:32 +0200 Subject: SmallWiki 2 Message-ID: <64D370CB-C93D-11D8-AF71-000393CFE6C8@iam.unibe.ch> Hi SmallWiki-To-Seaside-Porters, I started with the port of SmallWiki to Seaside today. Unfortunately there are some problems with VisualWave (the default web-server of Seaside for VisualWorks), that I have to sort out to enable SmallWiki to do manual url handling. I will continue working on it and will try to publish a first version tomorrow on the SCG-StORE, so that people can start porting missing actions, renderers, template-comentents, etc. :) Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org From ducasse at iam.unibe.ch Mon Jun 28 22:40:09 2004 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Mon, 28 Jun 2004 22:40:09 +0200 Subject: SmallWiki 2 In-Reply-To: <64D370CB-C93D-11D8-AF71-000393CFE6C8@iam.unibe.ch> References: <64D370CB-C93D-11D8-AF71-000393CFE6C8@iam.unibe.ch> Message-ID: <589EA912-C943-11D8-B52C-000A9573EAE2@iam.unibe.ch> thanks lukas! Stef On 28 juin 04, at 21:57, Lukas Renggli wrote: > Hi SmallWiki-To-Seaside-Porters, > > I started with the port of SmallWiki to Seaside today. Unfortunately > there are some problems with VisualWave (the default web-server of > Seaside for VisualWorks), that I have to sort out to enable SmallWiki > to do manual url handling. I will continue working on it and will try > to publish a first version tomorrow on the SCG-StORE, so that people > can start porting missing actions, renderers, template-comentents, > etc. :) > > Cheers, > Lukas > > -- > Lukas Renggli > http://renggli.freezope.org > From renggli at iam.unibe.ch Tue Jun 29 16:15:15 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 29 Jun 2004 16:15:15 +0200 Subject: [VW][BUG][FIX] WAWalkback>>renderObject:labelled:on: Message-ID: Hi, WAWalkback>>renderObject: anObject labelled: aString on: html | objectString | [objectString := anObject printStringLimitedTo: 100] on: Error do: [objectString := '>renderObject: anObject labelled: aString on: html | objectString | [objectString := anObject printStringLimitedTo: 100] on: Error do: [:err|objectString := '>renderObject:labelled:on: In-Reply-To: References: Message-ID: <5B1F79B0-C9EA-11D8-AF71-000393CFE6C8@iam.unibe.ch> Oupps sorry, this was the wrong mailing list. Should have gone to the SmallWiki-Wiki list. On Jun 29, 2004, at 16:15, Lukas Renggli wrote: > Hi, > > WAWalkback>>renderObject: anObject labelled: aString on: html > | objectString | > [objectString := anObject printStringLimitedTo: 100] > on: Error > do: [objectString := ' html tableRowWithLabel: aString column: objectString. > > should be > > WAWalkback>>renderObject: anObject labelled: aString on: html > | objectString | > [objectString := anObject printStringLimitedTo: 100] > on: Error > do: [:err|objectString := ' html tableRowWithLabel: aString column: objectString. > > else VisualWorks raises "Unhandled exception: This block expects 0 > argument(s)". Maybe it would be good practice to add the > block-variable in the seaside version as well. One can find the > occurrences using: > > ``@block on: ``@class do: [ ``@stmts ] > > Cheers, > Lukas > > -- > Lukas Renggli > http://renggli.freezope.org -- Lukas Renggli http://renggli.freezope.org From davidroe at bluewin.ch Tue Jun 29 19:57:55 2004 From: davidroe at bluewin.ch (=?iso-8859-1?Q?David_R=F6thlisberger?=) Date: Tue, 29 Jun 2004 19:57:55 +0200 Subject: A newbie question References: <200406240335.WAA15644@salad.cs.uiuc.edu> <7DFC4992-C5BD-11D8-8179-000A9573EAE2@iam.unibe.ch> <40DCC0DD.6050404@gmx.net> <009801c45b5c$587f8ed0$bd2e03d5@david715t080hb> <40DEA81E.3020707@gmx.net> Message-ID: <012c01c45e02$9e1aab70$73353f51@david715t080hb> > Thanks for your answer. Good to know that i can use SmallWiki with that > broken Swazoo test. Did you know on which OS the Swazoo tests run green? Probably they run green on a MacOS, but Lukas, Stef and the other mac users can tell you more. I have tested Swazoo only on Windows. bye David From renggli at iam.unibe.ch Tue Jun 29 21:42:08 2004 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 29 Jun 2004 21:42:08 +0200 Subject: [SW2] First Commit to SCG StORE Message-ID: <686ADE2A-CA04-11D8-AF71-000393CFE6C8@iam.unibe.ch> Hi, I published a first version of SmallWiki 2 to the SCG StORE. The bundle is called 'SmallWiki2'. It should be runnable, but not useable at all. There are still a lot of important things missing, but basic features are implemented and one should see a web-page when browsing the root. As you will see, the design is quite different: maybe somebody wants to have a look at it and give some comments. The rendering isn't implemented yet. Unfortunately tomorrow I won't have much time to work on it. I will keep you informed about the updates in the mailing-list. Cheers, Lukas -- Lukas Renggli http://renggli.freezope.org From ducasse at iam.unibe.ch Tue Jun 29 22:28:20 2004 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Tue, 29 Jun 2004 22:28:20 +0200 Subject: [SW2] First Commit to SCG StORE In-Reply-To: <686ADE2A-CA04-11D8-AF71-000393CFE6C8@iam.unibe.ch> References: <686ADE2A-CA04-11D8-AF71-000393CFE6C8@iam.unibe.ch> Message-ID: Hi lukas, > I published a first version of SmallWiki 2 to the SCG StORE. The > bundle is called 'SmallWiki2'. It should be runnable, but not useable > at all. There are still a lot of important things missing, but basic > features are implemented and one should see a web-page when browsing > the root. As you will see, the design is quite different: maybe > somebody wants to have a look at it and give some comments. The > rendering isn't implemented yet. I will not have the time before leaving on holiday. May be you should publish to cincom store so that other people of the mailing-list that do not have access to our store can give comments. David R. have you some time to give feedback to lukas? Stef > > Unfortunately tomorrow I won't have much time to work on it. I will > keep you informed about the updates in the mailing-list. > > Cheers, > Lukas > > -- > Lukas Renggli > http://renggli.freezope.org > From davidroe at bluewin.ch Wed Jun 30 21:11:52 2004 From: davidroe at bluewin.ch (=?iso-8859-1?Q?David_R=F6thlisberger?=) Date: Wed, 30 Jun 2004 21:11:52 +0200 Subject: [SW2] First Commit to SCG StORE References: <686ADE2A-CA04-11D8-AF71-000393CFE6C8@iam.unibe.ch> Message-ID: <022301c45ed6$1b62f960$fb913e51@david715t080hb> > As you will see, the design is quite different: maybe somebody wants to > have a look at it and give some comments. yes, it looks nice, good job. :) So can I now start to port the actions and templates? I have some free time tomorrow and Friday. BTW: does anyone know why it takes hours to load SmallWiki2 from SCG store? I spent at least two hours to load it, even though my internet connection is quite fast. I can't understand that, really annoying... What does VW in the background when I load a module? It seems to me that loading from CinCom Store is a bit faster, but it's also very slow.... kind regards, David