From keith_hodges at yahoo.co.uk Tue Aug 1 04:16:41 2006 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Tue, 01 Aug 2006 03:16:41 +0100 Subject: SCG Smallwiki - wiki Message-ID: <44CEB989.7030906@yahoo.co.uk> Does one now need an account to edit this wiki? Keith ___________________________________________________________ Now you can scan emails quickly with a reading pane. Get the new Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html From damien.cassou at laposte.net Tue Aug 1 06:46:23 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Tue, 01 Aug 2006 06:46:23 +0200 Subject: [Pier] Simplest persistency layer In-Reply-To: <02d001c6b4d7$64a91a10$4b00a8c0@hq.allresnet.com> References: <02d001c6b4d7$64a91a10$4b00a8c0@hq.allresnet.com> Message-ID: <44CEDC9F.90108@laposte.net> Ramon Leon wrote: >> >> Oooops, I'm really sorry. What makes me understand that you >> did not understand was the reference to the variable >> 'contexts' which only exists in PRImagePersistency. So your >> code won't work on my persistency layer. What do I need to >> change to get the history ? >> >> >> Thanks > > > You should really just subclass PRImagePersistency, use the do and reverseDo > I sent, and override snapshot and log with your versions. Should #log: call super to fill the context collection ? From ramonleon at cox.net Tue Aug 1 16:37:41 2006 From: ramonleon at cox.net (Ramon Leon) Date: Tue, 01 Aug 2006 07:37:41 -0700 Subject: [Pier] Simplest persistency layer In-Reply-To: <44CEDC9F.90108@laposte.net> References: <02d001c6b4d7$64a91a10$4b00a8c0@hq.allresnet.com> <44CEDC9F.90108@laposte.net> Message-ID: <44CF6735.9040806@cox.net> Damien Cassou wrote: > Ramon Leon wrote: > >>>Oooops, I'm really sorry. What makes me understand that you >>>did not understand was the reference to the variable >>>'contexts' which only exists in PRImagePersistency. So your >>>code won't work on my persistency layer. What do I need to >>>change to get the history ? >>> >>> >>>Thanks >> >> >>You should really just subclass PRImagePersistency, use the do and reverseDo >>I sent, and override snapshot and log with your versions. > > > Should #log: call super to fill the context collection ? > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > Yes, and snapshot as well, you're overriding log and snapshot simply to extend them, not replace them. From renggli at iam.unibe.ch Tue Aug 1 18:06:39 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 1 Aug 2006 18:06:39 +0200 Subject: Trouble Following Pier Example in Master Thesis In-Reply-To: <20060725203249.24812.qmail@web53306.mail.yahoo.com> References: <20060725203249.24812.qmail@web53306.mail.yahoo.com> Message-ID: > Yes the PRForms work perfectly in the newest Pier. The main cause > was indeed the missing readUsing: and write:using: methods. You can find my code in the official Pier repository http://mc.lukas- renggli.ch/pier/. It is the package called Pier-Forms. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Tue Aug 1 18:12:10 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 1 Aug 2006 18:12:10 +0200 Subject: [Pier] Simplest persistency layer In-Reply-To: <44CCD6FD.2060905@cox.net> References: <44CC9D3D.2020201@laposte.net> <44CCD6FD.2060905@cox.net> Message-ID: <93BBE3DB-9403-4273-AD8A-71DF51E960B1@iam.unibe.ch> > Currently the lack of persistence is a serious show stopper with Pier, > hopefully Lucas, or someone with the necessary know how can find some > time in the near future to fix this. Yes, I know about this problem. I finished with my master studies at the university and will start with a PhD tomorrow. This means, I will be probably able to allocate time on this, but I don't know yet how much and when. Definitely I will need to concentrate on other things as well, so I am more limited than before. Of course, contribution/fixes/enhancements are always welcome. Remember, the repository is open for anybody to publish his/her changes. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Tue Aug 1 18:14:05 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 1 Aug 2006 18:14:05 +0200 Subject: [Smallwiki] [Pier] State of persistency ? In-Reply-To: <44CE4824.9070304@laposte.net> References: <44CC8B6D.5060406@laposte.net> <44CD59E3.4010003@yahoo.co.uk> <44CE4824.9070304@laposte.net> Message-ID: <4ECE41B3-F2DB-4DBC-B47F-DCDAB2C7E98E@iam.unibe.ch> > In fact, my Pier setup is meant to be used for a static website with > very rare modification and by only one person. I don't think I need > magma at all, but thank you for the proposal. My personal website has exactly the same requirements: mostly static, rare modification, editing only by one person (me). I just save the image after changes. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Tue Aug 1 18:16:16 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 1 Aug 2006 18:16:16 +0200 Subject: SCG Smallwiki - wiki In-Reply-To: <44CEB989.7030906@yahoo.co.uk> References: <44CEB989.7030906@yahoo.co.uk> Message-ID: <7E60A2D2-3D40-47DF-B745-3AE809A8FA85@iam.unibe.ch> Adrian, can you explain how to edit the SCG Smallwiki from outside the university? There are Smallwiki community members that are editing documentation on this wiki. Cheers, Lukas On 1 Aug 2006, at 04:16, Keith Hodges wrote: > Does one now need an account to edit this wiki? > > Keith > > > ___________________________________________________________ > Now you can scan emails quickly with a reading pane. Get the new > Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From alienhard at netstyle.ch Tue Aug 1 18:22:31 2006 From: alienhard at netstyle.ch (Adrian Lienhard) Date: Tue, 1 Aug 2006 18:22:31 +0200 Subject: SCG Smallwiki - wiki In-Reply-To: <7E60A2D2-3D40-47DF-B745-3AE809A8FA85@iam.unibe.ch> References: <44CEB989.7030906@yahoo.co.uk> <7E60A2D2-3D40-47DF-B745-3AE809A8FA85@iam.unibe.ch> Message-ID: Please find the original mail with the login below. Cheers, Adrian On Jun 19, 2006, at 22:49 , Adrian Lienhard wrote: > Due to spam on Smallwiki I've changed the security policy to > prevent modifications by users (or robots) outside the university. > > To edit a Smallwiki page from the outside you can log in as follows > to acquire the edit rights: > > username: anonymous > password: xopu > > This is an extended anonymous user which has the same rights like > the anonymous user as it existed up until today. This solution > allows us to distribute an account with edit rights to students > without needing to give out the admin account. > > From within the university you are automatically identified as the > extended anonymous user, hence you don't need to log in (*). > > Adrian On Aug 1, 2006, at 18:16 , Lukas Renggli wrote: > Adrian, can you explain how to edit the SCG Smallwiki from outside > the university? There are Smallwiki community members that are > editing documentation on this wiki. > > Cheers, > Lukas > > On 1 Aug 2006, at 04:16, Keith Hodges wrote: > >> Does one now need an account to edit this wiki? >> >> Keith >> >> >> ___________________________________________________________ >> Now you can scan emails quickly with a reading pane. Get the new >> Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > From ramon.leon at allresnet.com Tue Aug 1 18:30:09 2006 From: ramon.leon at allresnet.com (Ramon Leon) Date: Tue, 1 Aug 2006 09:30:09 -0700 Subject: [Pier] Simplest persistency layer In-Reply-To: <93BBE3DB-9403-4273-AD8A-71DF51E960B1@iam.unibe.ch> Message-ID: <034101c6b587$c1bfc220$4b00a8c0@hq.allresnet.com> > > Of course, contribution/fixes/enhancements are always welcome. > Remember, the repository is open for anybody to publish > his/her changes. > > Cheers, > Lukas I did at one point, publish some fixes to the PRImagePersistency class, and some comments to PRFilePersistency, you never merged them, so I've been waiting for you to get around to fixing persistence. From renggli at iam.unibe.ch Tue Aug 1 19:00:01 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 1 Aug 2006 19:00:01 +0200 Subject: [Pier] Simplest persistency layer In-Reply-To: <034101c6b587$c1bfc220$4b00a8c0@hq.allresnet.com> References: <034101c6b587$c1bfc220$4b00a8c0@hq.allresnet.com> Message-ID: >> Of course, contribution/fixes/enhancements are always welcome. >> Remember, the repository is open for anybody to publish >> his/her changes. >> >> Cheers, >> Lukas > > I did at one point, publish some fixes to the PRImagePersistency > class, and > some comments to PRFilePersistency, you never merged them, so I've > been > waiting for you to get around to fixing persistence. Yes, I do remember. I did not forget about them. The problem was that I could merge them only partly (I think I merged the Magritte changes, but not the ones of Pier) was that the changes introduced some comments that I didn't want to appear in the automatically generated documentation for my master. Still Monticello makes it very easy to fork a version and eventually merge it back in later on. I am doing this all the time. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From ramon.leon at allresnet.com Tue Aug 1 19:01:36 2006 From: ramon.leon at allresnet.com (Ramon Leon) Date: Tue, 1 Aug 2006 10:01:36 -0700 Subject: [Pier] Simplest persistency layer In-Reply-To: Message-ID: <035101c6b58c$25ed85d0$4b00a8c0@hq.allresnet.com> > > Yes, I do remember. I did not forget about them. The problem > was that I could merge them only partly (I think I merged the > Magritte changes, but not the ones of Pier) was that the > changes introduced some comments that I didn't want to appear > in the automatically generated documentation for my master. > > Still Monticello makes it very easy to fork a version and > eventually merge it back in later on. I am doing this all the time. > > Lukas Oh I know, I maintain my own fork with those changes locally, Monticello rocks. From ducasse at iam.unibe.ch Tue Aug 1 21:39:47 2006 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Tue, 1 Aug 2006 21:39:47 +0200 Subject: [Smallwiki] [Pier] State of persistency ? In-Reply-To: <44CD59E3.4010003@yahoo.co.uk> References: <44CC8B6D.5060406@laposte.net> <44CD59E3.4010003@yahoo.co.uk> Message-ID: <6BDAFAAE-A2B2-406C-A2D8-8DC64A0F7DE9@iam.unibe.ch> > Dear Damien, > > I am also working on the persistency issue, I need something working > well as soon as possible. Content authors for my site are nagging me > already, we go live in October. > > I figured that magma was at least worth a try. As as DB it is all > in the > smalltalk image without any dependency upon external servers. Magma > appears to be aiming to make persistency as simple as possible. Raw > performance is unlikely to be an issue for me. It seems like the > right fit. > > I would have had something working by now if it were not for my > windows > installation taking a dive due to disk errors. I am now up and running > again (just about). In the next couple of days/weeks I should have > something to show for my troubles. > > If you want to try magma with seaside there are some updates/bug fixes > around (email me or, check recent history of the magma list > because the > repository has yet to be updated) Hi Keith I would really be interested to learn more about it. I thought that using a changeset-like mechanism for a domain that is open (and can be extended) is a problem and may break the restoring facilities. I was thinking that we could at least save the page in XML or a similar format after each command. and we could recover the lastest changes. Will you publish and share your code? I would love to get a Smallwiki version whose image could get corrupted and that I could reconstruct :) Stef From renggli at iam.unibe.ch Wed Aug 2 08:39:36 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 2 Aug 2006 08:39:36 +0200 Subject: Pier download and installation In-Reply-To: <44C36816.3030608@telefonica.net> References: <44C36816.3030608@telefonica.net> Message-ID: <3F5C7C61-604B-4654-BA4D-DD797E435BD9@iam.unibe.ch> Hi Daniel, > I am really impressed with Pier, so I think it will be wonderfull > for me to make my webs with Pier instead of PHP. > I searched the download page or the way to install the package with > monticello, but I didn?t find the right way. > Can you help me? the easiest way to install and run Pier is to take a fresh 3.8 image, to open SqueakMap and to load the package 'Pier' or 'Pier Unix Security'. This package will pull in all the requirements automatically. There are a couple of other ways to install Pier: http://smallwiki.unibe.ch/smallwiki/pier/installationofpier/ Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From david.tibbe at hpi.uni-potsdam.de Wed Aug 2 09:51:51 2006 From: david.tibbe at hpi.uni-potsdam.de (David Tibbe) Date: Wed, 02 Aug 2006 09:51:51 +0200 Subject: [Smallwiki] [Pier] State of persistency ? In-Reply-To: <6BDAFAAE-A2B2-406C-A2D8-8DC64A0F7DE9@iam.unibe.ch> References: <44CC8B6D.5060406@laposte.net> <44CD59E3.4010003@yahoo.co.uk> <6BDAFAAE-A2B2-406C-A2D8-8DC64A0F7DE9@iam.unibe.ch> Message-ID: <44D05997.1070305@hpi.uni-potsdam.de> Hi, > I was thinking that we could at least save the page in XML or a > similar format after each command. > and we could recover the lastest changes. Do you know Thomas Froeb's PRXMLPersistency? You can get it at http://source.impara.de. I use it for a project wiki and it works quite fine. There are some problems when restoring an old version when a page title contains a german umlaut like ?. That Persistency module stores all data in XML-files, every version in a seperate one. Greets, David From renggli at iam.unibe.ch Wed Aug 2 10:07:29 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 2 Aug 2006 10:07:29 +0200 Subject: [Smallwiki] [Pier] State of persistency ? In-Reply-To: <44D05997.1070305@hpi.uni-potsdam.de> References: <44CC8B6D.5060406@laposte.net> <44CD59E3.4010003@yahoo.co.uk> <6BDAFAAE-A2B2-406C-A2D8-8DC64A0F7DE9@iam.unibe.ch> <44D05997.1070305@hpi.uni-potsdam.de> Message-ID: >> I was thinking that we could at least save the page in XML or a >> similar format after each command. >> and we could recover the lastest changes. > > Do you know Thomas Froeb's PRXMLPersistency? You can get it at > http://source.impara.de. I use it for a project wiki and it works > quite > fine. There are some problems when restoring an old version when a > page > title contains a german umlaut like ?. > That Persistency module stores all data in XML-files, every version > in a > seperate one. Interesting. How does it version the changes in the tree, e.g. deleting, moveing, copying, renaming pages? Is it open-source? Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Wed Aug 2 10:37:41 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 2 Aug 2006 10:37:41 +0200 Subject: Fwd: Pier download and installation References: <44D063E0.8090803@telefonica.net> Message-ID: <1D60C106-F2A2-4350-8211-A16F0A877AA5@iam.unibe.ch> Begin forwarded message: > From: Daniel Sancho Ehlert > Date: 2 August 2006 10:35:44 GMT+02:00 > To: Lukas Renggli > Subject: Re: Pier download and installation > Reply-To: daniel at caminante.org > > Lukas Renggli escribi?: >> Hi Daniel, >> >>> I am really impressed with Pier, so I think it will be wonderfull >>> for me to make my webs with Pier instead of PHP. >>> I searched the download page or the way to install the package >>> with monticello, but I didn?t find the right way. >>> Can you help me? >> >> the easiest way to install and run Pier is to take a fresh 3.8 >> image, to open SqueakMap and to load the package 'Pier' or 'Pier >> Unix Security'. This package will pull in all the requirements >> automatically. >> >> There are a couple of other ways to install Pier: >> >> http://smallwiki.unibe.ch/smallwiki/pier/installationofpier/ >> >> Cheers, >> Lukas >> >> --Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> >> > Hello Lukas: > > Thank you very much and sorry for so silly question. > I installed Pier and I'm now learning how to use it. I'm very > interested in Magritte. > > The main problem to install Pier, once I learned how to use > Monticello was this: > http://lists.squeakfoundation.org/pipermail/squeak-dev/2005- > December/098651.html > Another problem was trying to install Pier with SuperSwiki2. I can > not explain you why... I'm new in Smalltalk. But for me is more > important Pier. > > Thank you for your answer > > Daniel > > > > -- > ============================== > === Visita mis p?ginas === > === Visit my web pages === > ============================== > = http://www.teclas.org = > = http://www.caminante.org = > ============================== > > -- Lukas Renggli http://www.lukas-renggli.ch From frank.urbach at schmees.com Wed Aug 2 11:05:57 2006 From: frank.urbach at schmees.com (Frank Urbach) Date: Wed, 2 Aug 2006 09:05:57 +0000 GMT Subject: AW: Re: [Smallwiki] [Pier] State of persistency ? Message-ID: <1144440303-1154509522-cardhu_blackberry.rim.net-15797-@engine41-cell01.bwc.produk.on.blackberry> Hi all, >I would love to get a Smallwiki version whose >image could get >corrupted and that I could reconstruct :) the persistency based on XML for Pier was made by thomas froeb @ impara. I use this for my local wiki and the gsug-wiki use it to AFAIK. And so far it works. After one crash of my own wiki I was able to restore it with this. Thanks thomas! So I think ask him for more information about it. Cheers, Frank From david.tibbe at hpi.uni-potsdam.de Wed Aug 2 11:55:19 2006 From: david.tibbe at hpi.uni-potsdam.de (David Tibbe) Date: Wed, 02 Aug 2006 11:55:19 +0200 Subject: [Smallwiki] [Pier] State of persistency ? In-Reply-To: References: <44CC8B6D.5060406@laposte.net> <44CD59E3.4010003@yahoo.co.uk> <6BDAFAAE-A2B2-406C-A2D8-8DC64A0F7DE9@iam.unibe.ch> <44D05997.1070305@hpi.uni-potsdam.de> Message-ID: <44D07687.3040805@hpi.uni-potsdam.de> >> [PRXMLPersistency] > Interesting. How does it version the changes in the tree, e.g. > deleting, moveing, copying, renaming pages? There is a folder structure representing your page tree; each non-leaf page is a folder. In those folders, there are the files for the leaf pages. The filename is [version]-[page title].xml, eg. 4-myPage.xml. I have not have a closer look on it, I've just started using it.. Moved pages still have a file/folder at their old location, but also a new one at the new. The version number ist higher at the new one, of cause, so that the most recent version could be identified. There is no auto-versioning, too. That means you have to call kernel persistency snapshot manually. The "recent changes" page does display the changes only up to the last shapshot, when creating a new one, all pages are displayed to be changed at that time. Greets From frank.urbach at schmees.com Wed Aug 2 13:33:59 2006 From: frank.urbach at schmees.com (Frank Urbach) Date: Wed, 2 Aug 2006 11:33:59 +0000 GMT Subject: AW: Re: [Smallwiki] [Pier] State of persistency ? Message-ID: <1988127840-1154518405-cardhu_blackberry.rim.net-4552-@engine22-cell01.bwc.produk.on.blackberry> Hi, >There is no auto-versioning, too. That means >you have to call >kernel persistency snapshot manually. The >"recent changes" page does >display the changes only up to the last >shapshot, when creating a new >one, all pages are displayed to be changed at >that time. Thats not quite true. If you do something like: PRKernel instances first persistency: PRXMLPersistency new. PRKernel persistency snapshot. PRXMLStarter startup. (Workspace instructions given from thomas) for starting the persistency mechanism, the system should save the version of the changed site as you described automatic in the filesystem. Cheers, Frank From ducasse at iam.unibe.ch Wed Aug 2 17:02:06 2006 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Wed, 2 Aug 2006 17:02:06 +0200 Subject: AW: Re: [Smallwiki] [Pier] State of persistency ? In-Reply-To: <1144440303-1154509522-cardhu_blackberry.rim.net-15797-@engine41-cell01.bwc.produk.on.blackberry> References: <1144440303-1154509522-cardhu_blackberry.rim.net-15797-@engine41-cell01.bwc.produk.on.blackberry> Message-ID: Do you know if this is working for Pier? Stef On 2 ao?t 06, at 11:05, Frank Urbach wrote: > Hi all, >> I would love to get a Smallwiki version whose >image could get >> corrupted and that I could reconstruct :) > the persistency based on XML for Pier was made by thomas froeb @ > impara. I use this for my local wiki and the gsug-wiki use it to > AFAIK. And so far it works. After one crash of my own wiki I was > able to restore it with this. Thanks thomas! So I think ask him for > more information about it. > > Cheers, > Frank > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From keith_hodges at yahoo.co.uk Fri Aug 4 16:42:29 2006 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Fri, 04 Aug 2006 15:42:29 +0100 Subject: [Smallwiki] [Pier] State of persistency ? In-Reply-To: <4ECE41B3-F2DB-4DBC-B47F-DCDAB2C7E98E@iam.unibe.ch> References: <44CC8B6D.5060406@laposte.net> <44CD59E3.4010003@yahoo.co.uk> <44CE4824.9070304@laposte.net> <4ECE41B3-F2DB-4DBC-B47F-DCDAB2C7E98E@iam.unibe.ch> Message-ID: <44D35CD5.7090505@yahoo.co.uk> Staring at the code I want to override PRKernel>>critical: PRKernel>>critical: aBlock PRKernel persistency critical: aBlock ---- PRNullPersistency>>critical: aBlock self kernel mutex critical: aBlock ---- so that when I subclass persistency I can nicely inform the database of the changes PRMagmaPersistency>>critical: aBlock session commit: [ self kernel mutex critical: aBlock ] ----- I know there is provision for over riding Persistency>>log: etc. Is my plan ok or would it be considered bad style? Keith ___________________________________________________________ All New Yahoo! Mail ? Tired of Vi at gr@! come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html From keith_hodges at yahoo.co.uk Fri Aug 4 17:16:23 2006 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Fri, 04 Aug 2006 16:16:23 +0100 Subject: [Smallwiki] [Pier] State of persistency ? In-Reply-To: <44D35CD5.7090505@yahoo.co.uk> References: <44CC8B6D.5060406@laposte.net> <44CD59E3.4010003@yahoo.co.uk> <44CE4824.9070304@laposte.net> <4ECE41B3-F2DB-4DBC-B47F-DCDAB2C7E98E@iam.unibe.ch> <44D35CD5.7090505@yahoo.co.uk> Message-ID: <44D364C7.4060806@yahoo.co.uk> I am going for a rewrite of PRCommand>>execute self isView ifTrue: [ self shouldNotImplement ]. self kernel persistency critical: [ "changed to go via persistency" self doValidate; doExecute. self isLogged ifTrue: [ self doPersistency ] ]. self doAnswer PRPersistency>>critical: b kernel critical: b Lukas, is that a change that would make it into the main stream? Keith ___________________________________________________________ Inbox full of spam? Get leading spam protection and 1GB storage with All New Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html From renggli at iam.unibe.ch Fri Aug 4 17:58:27 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 4 Aug 2006 17:58:27 +0200 Subject: [Smallwiki] [Pier] State of persistency ? In-Reply-To: <44D364C7.4060806@yahoo.co.uk> References: <44CC8B6D.5060406@laposte.net> <44CD59E3.4010003@yahoo.co.uk> <44CE4824.9070304@laposte.net> <4ECE41B3-F2DB-4DBC-B47F-DCDAB2C7E98E@iam.unibe.ch> <44D35CD5.7090505@yahoo.co.uk> <44D364C7.4060806@yahoo.co.uk> Message-ID: <6B831EF0-6530-4D40-9A56-C108D1DF2F89@iam.unibe.ch> > Lukas, is that a change that would make it into the main stream? I see, this completely makes sense. Please commit. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From rickf at ca-flower.com Tue Aug 8 02:07:23 2006 From: rickf at ca-flower.com (Rick Flower) Date: Mon, 07 Aug 2006 17:07:23 -0700 Subject: Porting Magritte over to VisualWorks.. In-Reply-To: References: <24C40DFA333DC44882F9FB0115F33D8F499FC4@ARGON.insario.local> <67628d690602091412m3cd20dd9s656d6e4d7cd4de72@mail.gmail.com> <44079BBA.5090403@ca-flower.com> <67628d690603030030p741dd950j86c87f7cd3c5df21@mail.gmail.com> <44806ADB.80505@ca-flower.com> Message-ID: <44D7D5BB.5080801@ca-flower.com> Lukas Renggli wrote: >> (Object #mementoClass - MACheckedMemento is undeclared) >> (Class #defaultContainer - MAPriorityContainer is undeclared) >> (Object class #description - MACachedBuilder is undeclared) >> (BlockContext #asCondition - MAConditionBuilder is undeclared) >> (Magritte.MACachedBuilder #register - SystemChangeNotifier is >> undeclared) >> (Magritte.MAColorDescription #kind - Color - duplicateBindings) >> (Magritte.MAColorDescription #kind - Color is undeclared) >> (Magritte.MADateDescription #kind - Date - duplicateBindings) >> (Magritte.MADateDescription #kind - Date is undeclared) >> (Magritte.MADistribution #publish - HTTPSocket is undeclared) >> (Magritte.MADistribution #zip - ZipArchive is undeclared) >> (Magritte.MADistribution #addPackage: - MCWorkingCopy is undeclared) >> (Magritte.MADistribution #basePackages - MCPackage is undeclared) >> (Magritte.MADistribution #addPackage:workingCopy: - MCVersion is >> undeclared) >> (Magritte.MADurationDescription #kind - Duration is undeclared) >> (Magritte.MADynamicObject #realSubject - UnhandledError is undeclared) >> (Magritte.MATimeDescription #kind - Time - duplicateBindings) >> (Magritte.MATimeDescription #kind - Time is undeclared) >> (Magritte.MATimeStampDescription #kind - TimeStamp is undeclared) > > These should be all dispatched trough the class MACompatiblity, as > these seems to be things that cannot be resolved in VisualWorks > automatically. I guess for most of these problems this is just a > namespace import that is missing. I'm assuming I can look in the MACompatibility class to get an idea of what needs to be done.. correct? >> (Magritte.MACompatibility class #confirm: - PopUpMenu is undeclared) >> (Magritte.MACompatibility class #referenceStream: - ReferenceStream >> is undeclared) >> (Magritte.MACompatibility class #referenceStream: - >> RWBinaryOrTextStream is undeclared) >> (Magritte.MACompatibility class #request:default: - >> FillInTheBlankMorph is undeclared) >> (Magritte.MACompatibility class #request:default: - ActiveHand is >> undeclared) >> (Magritte.MACompatibility class #request:default: - ActiveWorld is >> undeclared) >> (Magritte.MACompatibility class #uuid - UUID is undeclared) > > These are all things that you need to fix manually tough an override > in VisualWorks. It is related to platform dependent code that cannot > be written in a generic way, but the comments should help you > implement those methods easily. Are you indicating that I would need to write the appropriate code to do whatever the squeak versions do? I'm trying to decide whether or not its worth trying to get Magritte ported over to VW or just ditch the idea altogether and roll my own forms/reports, etc for each of my domain objects. I was looking at Mewa which has already been ported to VW, but as someone else indicated on the Seaside list, it has stagnated for several years and may not be the best choice. To that end, if I'm using VW, Seaside & Glorp, can I expect any gotcha's -- probably specific to Glorp + Magritte that would pose any usability problems? Also, how much flexibility can I get with tailoring reports or forms with Magritte and is the output that is generated XHTML compliant like that which Seaside spits out (or is Seaside spitting it out as directed by Magritte)? Thanks.. I need to look at your latest docs for Magritte and perhaps some of this might be obvious from that. Thanks! -- Rick From renggli at iam.unibe.ch Tue Aug 8 09:32:58 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 8 Aug 2006 09:32:58 +0200 Subject: Porting Magritte over to VisualWorks.. In-Reply-To: <44D7D5BB.5080801@ca-flower.com> References: <24C40DFA333DC44882F9FB0115F33D8F499FC4@ARGON.insario.local> <67628d690602091412m3cd20dd9s656d6e4d7cd4de72@mail.gmail.com> <44079BBA.5090403@ca-flower.com> <67628d690603030030p741dd950j86c87f7cd3c5df21@mail.gmail.com> <44806ADB.80505@ca-flower.com> <44D7D5BB.5080801@ca-flower.com> Message-ID: <61BB512D-754B-47BB-A1AD-D9665A5AA3C2@iam.unibe.ch> >>> (Object #mementoClass - MACheckedMemento is undeclared) >>> (Class #defaultContainer - MAPriorityContainer is undeclared) >>> (Object class #description - MACachedBuilder is undeclared) >>> (BlockContext #asCondition - MAConditionBuilder is undeclared) >>> (Magritte.MACachedBuilder #register - SystemChangeNotifier is >>> undeclared) These should work. >>> (Magritte.MAColorDescription #kind - Color - duplicateBindings) >>> (Magritte.MAColorDescription #kind - Color is undeclared) >>> (Magritte.MADateDescription #kind - Date - duplicateBindings) >>> (Magritte.MADateDescription #kind - Date is undeclared) These should work with the right namespace imports to the Squeak compatibility package that Michel did for Seaside. >>> (Magritte.MADistribution #publish - HTTPSocket is undeclared) >>> (Magritte.MADistribution #zip - ZipArchive is undeclared) >>> (Magritte.MADistribution #addPackage: - MCWorkingCopy is undeclared) >>> (Magritte.MADistribution #basePackages - MCPackage is undeclared) >>> (Magritte.MADistribution #addPackage:workingCopy: - MCVersion is >>> undeclared) These are not needed, they are used to build the SqueakMap packages. >>> (Magritte.MADurationDescription #kind - Duration is undeclared) >>> (Magritte.MADynamicObject #realSubject - UnhandledError is >>> undeclared) >>> (Magritte.MATimeDescription #kind - Time - duplicateBindings) >>> (Magritte.MATimeDescription #kind - Time is undeclared) >>> (Magritte.MATimeStampDescription #kind - TimeStamp is undeclared) Again that should work with the right namespace imports. >> These are all things that you need to fix manually tough an override >> in VisualWorks. It is related to platform dependent code that cannot >> be written in a generic way, but the comments should help you >> implement those methods easily. > > Are you indicating that I would need to write the appropriate code > to do > whatever the squeak versions do? Yes, exactly. The tests might also help here. > I'm trying to decide whether or not its worth trying to get Magritte > ported over to VW or just ditch the idea altogether and roll my own > forms/reports, etc for each of my domain objects. I was looking at > Mewa > which has already been ported to VW, but as someone else indicated on > the Seaside list, it has stagnated for several years and may not be > the > best choice. To that end, if I'm using VW, Seaside & Glorp, can I > expect any gotcha's -- probably specific to Glorp + Magritte that > would > pose any usability problems? Mewa does not support to let end users edit the meta-model. Moreover because it makes heavy use of blocks, it does not work if you want to make your meta-model persistent. Though, if you just have a few static forms it might be a good choice, but to give more hints you need to elaborate your requirements. > Also, how much flexibility can I get with tailoring reports or forms > with Magritte and is the output that is generated XHTML compliant like > that which Seaside spits out (or is Seaside spitting it out as > directed > by Magritte)? Yes, it should be XHTML compilant. You can easily plug-in your own renderer and components. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From rickf at ca-flower.com Tue Aug 8 17:52:00 2006 From: rickf at ca-flower.com (Rick Flower) Date: Tue, 08 Aug 2006 08:52:00 -0700 Subject: Porting Magritte over to VisualWorks.. In-Reply-To: <61BB512D-754B-47BB-A1AD-D9665A5AA3C2@iam.unibe.ch> References: <24C40DFA333DC44882F9FB0115F33D8F499FC4@ARGON.insario.local> <67628d690602091412m3cd20dd9s656d6e4d7cd4de72@mail.gmail.com> <44079BBA.5090403@ca-flower.com> <67628d690603030030p741dd950j86c87f7cd3c5df21@mail.gmail.com> <44806ADB.80505@ca-flower.com> <44D7D5BB.5080801@ca-flower.com> <61BB512D-754B-47BB-A1AD-D9665A5AA3C2@iam.unibe.ch> Message-ID: <44D8B320.4060508@ca-flower.com> Lukas Renggli wrote: > Mewa does not support to let end users edit the meta-model. Moreover > because it makes heavy use of blocks, it does not work if you want to > make your meta-model persistent. Though, if you just have a few > static forms it might be a good choice, but to give more hints you > need to elaborate your requirements. I'll have to admit that I'm a bit lost in how to proceed with doing this sort of cross-porting from one variant of ST to another as I'm a relative ST newbie (only using ST for about 6 months). I took a look at this again last night and I'm not convinced I know exactly how to proceed and as to whether or not I could dig my way out of a hole if I needed to (8->. To that end, I guess I'll probably stick with my hand-coding a bit longer until I feel more comfortable w/ ST cross-porting. Thanks again.. -- Rick From bakki.kudva at gmail.com Thu Aug 10 20:53:55 2006 From: bakki.kudva at gmail.com (Bakki Kudva) Date: Thu, 10 Aug 2006 14:53:55 -0400 Subject: [Newbie] pier on Linux vs. OSX problem Message-ID: Hi, I am new to SmallTalk(Squeak) and Seaside/Pier. I am burning the midnight oil and it's like drinking from a fire hose. But I am having fun. :) I have Squeak/Seaside/Magritte/Pier installed on 2 Debian Sarge Linux box (home and work) and also on MacBookPro. I did the following on all 3 machines. I had installed Seaside per the tutorial but I used the new seaside installer again to pull in scriptaculous etc. I wasn't sure if this was kosher but I assumed that the installer might be smart enough to figure out already installed components. But the Magritte also asked if it was ok install a newer Seaside2? On Linux every thing worked just fine but on OSX, Pier (1.0.5-alpha) did not ask about config options such as base url being /seaside/pier etc. So Pier does not work and does not appear in seaside/config either. Can some one explain if I am doing something wrong, or point me in the right direction to configure Pier. Thank you very much. bakki From renggli at iam.unibe.ch Mon Aug 14 09:32:18 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 14 Aug 2006 09:32:18 +0200 Subject: [Newbie] pier on Linux vs. OSX problem In-Reply-To: References: Message-ID: Hi Bakki, > I had sent this msg to the Pier list but see no traffic on that list. > So I am posting it here and hoping it won't be considered too > offtopic. sorry, I must have missed your question over at the Pier mailing list. It's quite calm over there at the moment, but that's not always like this. > I had installed Seaside per the tutorial but I used the new seaside > installer again to pull in scriptaculous etc. I wasn't sure if this > was kosher but I assumed that the installer might be smart enough to > figure out already installed components. But the Magritte also asked > if it was ok install a newer Seaside2? Yes, Magritte/Pier have its own installer and they load exactly the Seaside/Scriptaculous versions I've deployed them with. In this case this is an older version, but actually it shouldn't matter. The installers are simply there to get you a working image, from there you can easily update using Monticello. > On Linux every thing worked just fine but on OSX, Pier (1.0.5-alpha) > did not ask about config options such as base url being /seaside/pier > etc. So Pier does not work and does not appear in seaside/config > either. Very strange, I expected it to be the other way round. I am developing on OS X and I just tried to load it into Squeak3.9g-7054 and it worked fine for me. > Can some one explain if I am doing something wrong, or point me in the > right direction to configure Pier. Thank you very much. Try evaluating "PRPierFrame initialize". Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Mon Aug 14 11:33:30 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 14 Aug 2006 11:33:30 +0200 Subject: Merging In-Reply-To: <4499F111.1090207@yahoo.co.uk> References: <4499EDD3.5080203@yahoo.co.uk> <4499F111.1090207@yahoo.co.uk> Message-ID: <1BADE569-6739-4E4B-B64B-EF269934FAAA@iam.unibe.ch> Hi Keith, I am trying to merge all your changes, though I see some problems in Pier. For Magritte all your code should be merged in now. 1. Pier-Security-kph.40 - Pier-Security-kph.40 adds several cool widgets to Pier to add, create and edit users and groups. I do not properly understand why these are widgets and not commands? This means that I need a special place inside Pier where I add those widgets to be able to use them somewhere protected? Why not transform them into commands, so that they can also be properly logged with the persistency framework? Maybe provide a special Meta-Command that displays a special administrator interface to be able to trigger those commands without cluttering up the command interface with 10 new commands? 2. Your new persistency mechanisms looks cool. Does it work yet? How is the performance? I am especially interested into the Magma implementation. Your changes add a lot of external dependencies, why not put the new persistency mechanisms into their own packages? People could load then Pier-Magma if they want to use Magma or Pier- XML if they want XML persistency. Just my cents ;-) Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Mon Aug 14 13:04:58 2006 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Mon, 14 Aug 2006 12:04:58 +0100 Subject: [Smallwiki] Merging In-Reply-To: <1BADE569-6739-4E4B-B64B-EF269934FAAA@iam.unibe.ch> References: <4499EDD3.5080203@yahoo.co.uk> <4499F111.1090207@yahoo.co.uk> <1BADE569-6739-4E4B-B64B-EF269934FAAA@iam.unibe.ch> Message-ID: <44E058DA.7070909@yahoo.co.uk> Hi Lukas > Hi Keith, > > I am trying to merge all your changes, cool, > though I see some problems in > Pier. For Magritte all your code should be merged in now. > Did I write any magritte code? > 1. Pier-Security-kph.40 - Pier-Security-kph.40 adds several cool > widgets to Pier to add, create and edit users and groups. I do not > properly understand why these are widgets and not commands? Firstly I admit it was a somewhat quick and dirty first attempt. Nevertheless, I do see them as tools associated with a particular task. The idea being that a page may be presented as a task document which may embed the tools for carrying out that task. In this case the page would be within the management area. Certainly I would expect to filter them out of the users widgets list fairly soon. I see commands as universal to their scope, i.e they apply to the universal task, and they lack their own context. For example users have edit view commands that universally apply within their scope and administrators have move/delete commands that are equally universal. What commands dont have is their own 'context', the context that I am calling a 'task'. The commands list provides a user interface to the current context with is the web page in front of you. Managing users and groups is more of an abstract concept and so I feel it needs to be presented within its own context. Hence the widget within a page paradigm. I think that it is simpler too. Just to let you know that I have zope in mind and so there is a fair bit of work to develop the Environment in this direction. I expect to work it so that the environment provides the style for its peers and their sub-trees, but I expect that the environment itself will have its own environment, so that a user editing their environment cant accidentally break the environment. User management may be a candidate for this kind of treatment, whereby a user having responsibility for a sub-tree may put a user manager in place for that subtree only. I beleive that xope does it this way too. Where I used to work they attached the user/groups manager to the global unix users/password server and managed everything globally. > This > means that I need a special place inside Pier where I add those > widgets to be able to use them somewhere protected? Why not transform > them into commands, so that they can also be properly logged with the > persistency framework? Maybe provide a special Meta-Command that > displays a special administrator interface to be able to trigger > those commands without cluttering up the command interface with 10 > new commands? > > I had not thought of the logging issue, though with magma the persistence would be transparent. > 2. Your new persistency mechanisms looks cool. Does it work yet? How > is the performance? I am especially interested into the Magma > implementation. Your changes add a lot of external dependencies, why > not put the new persistency mechanisms into their own packages? > In theory Magma makes very little impact on the running application. I was hoping that magma persistence could make it into the main distribution and so although it may not look like it at this time I have been attempting to minimise those dependancies. If you look at PRMagmaPersistency all but one of the methods on the class side in the category "init repository", I am currently refactoring into the "Magma seaside" package as part of the magma control panel I am working on. This would leave only one real method (#doing:commit:) in PRMagmaPersistency (the others are stubs which could be fleshed out if needed). I suspect it would seem somewhat overkill to have a whole package for one class with one method. The class PRMagmaRoot is a work in progress and at the moment it is looking like it will be a component. I do not think that this will have any hard wired dependencies to the magma package. It will be responsible for managing the link between PRKernel-c-instances and the persisted instances in magmaSession root, i.e. itself. Performance, well I really havent had a chance to assess this yet. Magma has read strategies which could be easily configured to ensure that whole kernels are loaded into memory at once, and so in theory read performance would be uneffected particularly for small kernels. I am still learning stuff, particularly in the seaside domain. thanks for your input, I appreciate your support, I will let you know about magma in the next couple of days. Keith > People could load then Pier-Magma if they want to use Magma or Pier- > XML if they want XML persistency. > > Just my cents ;-) > > Cheers, > Lukas > > ___________________________________________________________ All New Yahoo! Mail ? Tired of Vi at gr@! come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html From keith_hodges at yahoo.co.uk Thu Aug 17 14:52:15 2006 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Thu, 17 Aug 2006 12:52:15 +0000 (GMT) Subject: Magriite-all didnt work for me Message-ID: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> I just tried loading magritte-all latest into a fresh installation of 3.8 with magma + seaside already loaded) and it failed to find its dependencies. Keith -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20060817/49c0bdea/attachment.html From damien.cassou at laposte.net Thu Aug 17 15:17:04 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Thu, 17 Aug 2006 15:17:04 +0200 Subject: Magriite-all didnt work for me In-Reply-To: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> Message-ID: <44E46C50.6010308@laposte.net> Keith Hodges wrote: > I just tried loading magritte-all latest into a fresh installation of > 3.8 with magma + seaside already loaded) and it failed to find its > dependencies. What is the error exactly ? Do you have the latest Seaside version from Monticello and branch 2.6b1 ? If it says that you miss a dependency about VW... you can safely ignore. From cbeler at enit.fr Thu Aug 17 15:46:20 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Thu, 17 Aug 2006 15:46:20 +0200 Subject: Magriite-all didnt work for me In-Reply-To: <44E46C50.6010308@laposte.net> References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> <44E46C50.6010308@laposte.net> Message-ID: <44E4732C.2000407@enit.fr> I had the same problem yesterday... apparently this was the test package that wasn't accessible... I don't remember the package in question... Anyway Keith, try to load manually the different components or you can try a previous Magritte-all package C?drick Damien Cassou a ?crit : > Keith Hodges wrote: > >> I just tried loading magritte-all latest into a fresh installation of >> 3.8 with magma + seaside already loaded) and it failed to find its >> dependencies. >> > > What is the error exactly ? Do you have the latest Seaside version from > Monticello and branch 2.6b1 ? If it says that you miss a dependency > about VW... you can safely ignore. > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > From renggli at iam.unibe.ch Fri Aug 18 09:12:32 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 18 Aug 2006 09:12:32 +0200 Subject: [Smallwiki] Merging In-Reply-To: <44E058DA.7070909@yahoo.co.uk> References: <4499EDD3.5080203@yahoo.co.uk> <4499F111.1090207@yahoo.co.uk> <1BADE569-6739-4E4B-B64B-EF269934FAAA@iam.unibe.ch> <44E058DA.7070909@yahoo.co.uk> Message-ID: Hi Keith, > Did I write any magritte code? mhh, sorry this was someone else. > Nevertheless, I do see them as tools associated with a particular > task. > The idea being that a page may be presented as a task document > which may > embed the tools for carrying out that task. In this case the page > would > be within the management area. Certainly I would expect to filter them > out of the users widgets list fairly soon. I see, sounds like an interesting approach. Looking forward to see an implementation. > I expect to work it so that the environment provides the style for its > peers and their sub-trees, but I expect that the environment itself > will > have its own environment, so that a user editing their environment > cant > accidentally break the environment. Yes, this sounds reasonable, breaking the environment and looking yourself out of the system is too easy. Luckily there is always a working inspector ... > User management may be a candidate for this kind of treatment, > whereby a > user having responsibility for a sub-tree may put a user manager in > place for that subtree only. I beleive that xope does it this way too. Exactly and I think the ACL security of Philippe is doing that as well, at least this was one his of the initial requirements I defined ... >> 2. Your new persistency mechanisms looks cool. Does it work yet? How >> is the performance? I am especially interested into the Magma >> implementation. Your changes add a lot of external dependencies, >> why not put the new persistency mechanisms into their own packages? > > In theory Magma makes very little impact on the running application. I > was hoping that magma persistence could make it into the main > distribution and so although it may not look like it at this time I > have > been attempting to minimise those dependancies. Yes, we can discuss about that. If it is reliable working it might be a good thing in Squeak, though there were interests in porting it to other Smalltalk dialect and a strong dependency to Magma would make a port much harder. > If you look at PRMagmaPersistency all but one of the methods on the > class side in the category "init repository", I am currently > refactoring > into the "Magma seaside" package as part of the magma control panel > I am > working on. Why "Magma Seaside"? Isn't it possible to implement the Magma persistency so that it doesn't depend on Seaside, for example if only the OmniBrowser interface is loaded? Or maybe one using a different Web framework? > This would leave only one real method (#doing:commit:) in > PRMagmaPersistency (the others are stubs which could be fleshed out if > needed). I suspect it would seem somewhat overkill to have a whole > package for one class with one method. Indeed ;-) Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Fri Aug 18 09:13:32 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 18 Aug 2006 09:13:32 +0200 Subject: Magriite-all didnt work for me In-Reply-To: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> Message-ID: <6AB75FDF-851F-4A88-8566-8FD558D39CEF@iam.unibe.ch> > I just tried loading magritte-all latest into a fresh installation > of 3.8 with magma + seaside already loaded) and it failed to find > its dependencies. This is strange, is it the Magritte-VisualWorks dependency that does not work or is there something else? Maybe because I committed the latest version from Squeak 3.9? Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Fri Aug 18 13:40:50 2006 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Fri, 18 Aug 2006 12:40:50 +0100 Subject: [Smallwiki] Re: Magriite-all didnt work for me In-Reply-To: <6AB75FDF-851F-4A88-8566-8FD558D39CEF@iam.unibe.ch> References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> <6AB75FDF-851F-4A88-8566-8FD558D39CEF@iam.unibe.ch> Message-ID: <44E5A742.7010803@yahoo.co.uk> Working from home on my linux machine I began with an image from scratch ( 3.8-6665 ) I loaded Seaside and Magma into this image and the exact details of what I did are in the workspace in that image which I put in preloaded.seasidehosting.st Then I went to my parents house and my dad has a windows machine. I downloaded the image, and attempted to install magritte-all. All dependencies failed to be found. I think that magritte-testing was the first. I thought that this was a symptom of changing machines / os. So I am now at home hand have just tried again on my linux box. Same error. Therefore in theory this is reproducible on both windows and linux using the image Sqk3.8f+magma24+seaside69.image which should be relatively clean. Individual packages work fine. Keith >> I just tried loading magritte-all latest into a fresh installation >> of 3.8 with magma + seaside already loaded) and it failed to find >> its dependencies. >> > > This is strange, is it the Magritte-VisualWorks dependency that does > not work or is there something else? Maybe because I committed the > latest version from Squeak 3.9? > > Lukas > > ___________________________________________________________ All new Yahoo! Mail "The new Interface is stunning in its simplicity and ease of use." - PC Magazine http://uk.docs.yahoo.com/nowyoucan.html From renggli at iam.unibe.ch Fri Aug 18 13:51:49 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 18 Aug 2006 13:51:49 +0200 Subject: [Smallwiki] Re: Magriite-all didnt work for me In-Reply-To: <44E5A742.7010803@yahoo.co.uk> References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> <6AB75FDF-851F-4A88-8566-8FD558D39CEF@iam.unibe.ch> <44E5A742.7010803@yahoo.co.uk> Message-ID: > I thought that this was a symptom of changing machines / os. So I > am now > at home hand have just tried again on my linux box. Same error. But what is this error? Can you provide a call-stack? Lukas -- Lukas Renggli http://www.lukas-renggli.ch From cbeler at enit.fr Fri Aug 18 14:15:52 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Fri, 18 Aug 2006 14:15:52 +0200 Subject: [Smallwiki] Re: Magriite-all didnt work for me In-Reply-To: References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> <6AB75FDF-851F-4A88-8566-8FD558D39CEF@iam.unibe.ch> <44E5A742.7010803@yahoo.co.uk> Message-ID: <44E5AF78.1050506@enit.fr> When I try to load Magritte-All (in a fresh seaside image based on 7054), I get the message 'data was late' in the Transcript... This is not the first time I have this problem. But once Magritte is installed (previoous version or SM version), I can use the -all package without problem. If I interupt the process, I have the following stack: Semaphore>>waitTimeoutMSecs: Receiver: a Semaphore() Arguments and temporary variables: anInteger: 5000 waitingProcess: a Process in Semaphore>>waitTimeoutMSecs: wakeupProcess: a Process in Process>>terminate Receiver's instance variables: firstLink: nil lastLink: nil excessSignals: 1 HTTPSocket(OldSocket)>>waitForDataUntil: Receiver: a HTTPSocket[connected] Arguments and temporary variables: deadline: 219428 dataArrived: false Receiver's instance variables: semaphore: a Semaphore() socketHandle: a ByteArray(163 69 233 70 0 0 0 0 152 166 21 8) readSemaphore: a Semaphore() writeSemaphore: a Semaphore() primitiveOnlySupportsOneSemaphore: false buffer: nil bufferPos: nil headerTokens: nil headers: nil responseCode: nil HTTPSocket>>getResponseUpTo:ignoring: Receiver: a HTTPSocket[connected] Arguments and temporary variables: markerString: ' ' ignoreString: ' ' buf: ' From cbeler at enit.fr Fri Aug 18 14:20:05 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Fri, 18 Aug 2006 14:20:05 +0200 Subject: [Smallwiki] Re: Magriite-all didnt work for me In-Reply-To: <44E5AF78.1050506@enit.fr> References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> <6AB75FDF-851F-4A88-8566-8FD558D39CEF@iam.unibe.ch> <44E5A742.7010803@yahoo.co.uk> <44E5AF78.1050506@enit.fr> Message-ID: <44E5B075.8040300@enit.fr> Sorry. Here is the full stack though I'm not sure that will help you ;) Semaphore>>waitTimeoutMSecs: Receiver: a Semaphore() Arguments and temporary variables: anInteger: 5000 waitingProcess: a Process in Semaphore>>waitTimeoutMSecs: wakeupProcess: a Process in Process>>terminate Receiver's instance variables: firstLink: nil lastLink: nil excessSignals: 1 HTTPSocket(OldSocket)>>waitForDataUntil: Receiver: a HTTPSocket[connected] Arguments and temporary variables: deadline: 219428 dataArrived: false Receiver's instance variables: semaphore: a Semaphore() socketHandle: a ByteArray(163 69 233 70 0 0 0 0 152 166 21 8) readSemaphore: a Semaphore() writeSemaphore: a Semaphore() primitiveOnlySupportsOneSemaphore: false buffer: nil bufferPos: nil headerTokens: nil headers: nil responseCode: nil HTTPSocket>>getResponseUpTo:ignoring: Receiver: a HTTPSocket[connected] Arguments and temporary variables: markerString: ' ' ignoreString: ' ' buf: ' response: a WriteStream '' bytesRead: 0 tester: 1 mm: 1 skipped: 0 tt: 1 ttLimiT: 0 Receiver's instance variables: semaphore: a Semaphore() socketHandle: a ByteArray(163 69 233 70 0 0 0 0 152 166 21 8) readSemaphore: a Semaphore() writeSemaphore: a Semaphore() primitiveOnlySupportsOneSemaphore: false buffer: nil bufferPos: nil headerTokens: nil headers: nil responseCode: nil [] in HTTPSocket class>>httpGetDocument:args:accept:request: {[sock := HTTPSocket new. sock connectTo: serverAddr port: connectToPort. (...]} Arguments and temporary variables: url: 'http://modules.squeakfoundation.org/People/gk/?C=M;O=D' args: nil mimeType: '*/*' requestString: 'Authorization: Basic c3F1ZWFrOnNxdWVhaw== ' serverName: 'modules.squeakfoundation.org' serverAddr: a ByteArray(193 50 189 4) port: 80 sock: a HTTPSocket[connected] header: nil length: nil bare: 'modules.squeakfoundation.org/People/gk/?C=M;O=D' page: 'http://modules.squeakfoundation.org:80/People/gk/?C=M;O=D' list: nil firstData: nil aStream: nil index: nil connectToHost: 'telemaque.enit.fr' connectToPort: 3128 type: nil newUrl: nil --- The full stack --- Semaphore>>waitTimeoutMSecs: HTTPSocket(OldSocket)>>waitForDataUntil: HTTPSocket>>getResponseUpTo:ignoring: [] in HTTPSocket class>>httpGetDocument:args:accept:request: {[sock := HTTPSocket new. sock connectTo: serverAddr port: connectToPort. (...]} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - SmallInteger(Integer)>>timesRepeat: HTTPSocket class>>httpGetDocument:args:accept:request: HTTPSocket class>>httpGet:args:accept:request: HTTPSocket class>>httpGet:args:user:passwd: MCHttpRepository>>allFileNames MCHttpRepository(MCFileBasedRepository)>>allFileNamesOrCache MCHttpRepository(MCFileBasedRepository)>>readableFileNames MCHttpRepository(MCFileBasedRepository)>>allFileNamesForVersionNamed: MCHttpRepository(MCFileBasedRepository)>>versionWithInfo:ifAbsent: MCHttpRepository(MCRepository)>>versionWithInfo: [] in MCRepositoryGroup>>versionWithInfo:ifNone: {[:ea | (ea versionWithInfo: aVersionInfo) ifNotNilDo: [:v | ^ v]]} [] in MCRepositoryGroup>>repositoriesDo: {[aBlock value: ea]} BlockContext>>on:do: [] in MCRepositoryGroup>>repositoriesDo: {[:ea | [aBlock value: ea] on: Error do: []]} Array(SequenceableCollection)>>do: MCRepositoryGroup>>repositoriesDo: MCRepositoryGroup>>versionWithInfo:ifNone: [] in MCVersionDependency>>resolve {[MCRepositoryGroup default versionWithInfo: versionInfo ifNone: []]} MCRepositoryGroup>>versionWithInfo:ifNone: MCVersionDependency>>resolve MCVersionLoader>>addDependency: [] in MCVersionLoader>>addVersion: {[:ea | self addDependency: ea]} Array(SequenceableCollection)>>do: MCVersionLoader>>addVersion: MCVersionLoader class>>loadVersion: MCVersion>>load [] in MCFileRepositoryInspector(MCVersionInspector)>>load {[self version load]} BlockContext>>ensure: ...etc... From cbeler at enit.fr Fri Aug 18 14:25:51 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Fri, 18 Aug 2006 14:25:51 +0200 Subject: [Smallwiki] Re: Magriite-all didnt work for me In-Reply-To: <44E5B075.8040300@enit.fr> References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> <6AB75FDF-851F-4A88-8566-8FD558D39CEF@iam.unibe.ch> <44E5A742.7010803@yahoo.co.uk> <44E5AF78.1050506@enit.fr> <44E5B075.8040300@enit.fr> Message-ID: <44E5B1CF.7010405@enit.fr> and if I leave the proccess end by itself, after a long list of 'data was late' in the Transcript, I get a popo-up saying: 'Can't find dependency Magritte-Tests-lr.94. Ignore ?' From renggli at iam.unibe.ch Fri Aug 18 14:49:17 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 18 Aug 2006 14:49:17 +0200 Subject: [Smallwiki] Re: Magriite-all didnt work for me In-Reply-To: <44E5B075.8040300@enit.fr> References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> <6AB75FDF-851F-4A88-8566-8FD558D39CEF@iam.unibe.ch> <44E5A742.7010803@yahoo.co.uk> <44E5AF78.1050506@enit.fr> <44E5B075.8040300@enit.fr> Message-ID: <3F02A52E-AAFB-44D7-BA99-549EB34418E2@iam.unibe.ch> > url: 'http://modules.squeakfoundation.org/People/gk/? > C=M;O=D' This is odd, you are trying to access the SqueakSource server of SqueakFoundation, there is certainly no Magritte/Pier code on there. Why the heck is Monticello trying to access this repository? :-/ Cheers, Lukas On 18 Aug 2006, at 14:20, C?drick B?ler wrote: > Sorry. Here is the full stack > though I'm not sure that will help you ;) > > > Semaphore>>waitTimeoutMSecs: > Receiver: a Semaphore() > Arguments and temporary variables: > anInteger: 5000 > waitingProcess: a Process in Semaphore>>waitTimeoutMSecs: > wakeupProcess: a Process in Process>>terminate > Receiver's instance variables: > firstLink: nil > lastLink: nil > excessSignals: 1 > > HTTPSocket(OldSocket)>>waitForDataUntil: > Receiver: a HTTPSocket[connected] > Arguments and temporary variables: > deadline: 219428 > dataArrived: false > Receiver's instance variables: > semaphore: a Semaphore() > socketHandle: a ByteArray(163 69 233 70 0 0 0 0 152 166 > 21 8) > readSemaphore: a Semaphore() > writeSemaphore: a Semaphore() > primitiveOnlySupportsOneSemaphore: false > buffer: nil > bufferPos: nil > headerTokens: nil > headers: nil > responseCode: nil > > HTTPSocket>>getResponseUpTo:ignoring: > Receiver: a HTTPSocket[connected] > Arguments and temporary variables: > markerString: ' > > > > ' > ignoreString: ' > ' > buf: ' > response: a WriteStream '' > bytesRead: 0 > tester: 1 > mm: 1 > skipped: 0 > tt: 1 > ttLimiT: 0 > Receiver's instance variables: > semaphore: a Semaphore() > socketHandle: a ByteArray(163 69 233 70 0 0 0 0 152 166 > 21 8) > readSemaphore: a Semaphore() > writeSemaphore: a Semaphore() > primitiveOnlySupportsOneSemaphore: false > buffer: nil > bufferPos: nil > headerTokens: nil > headers: nil > responseCode: nil > > [] in HTTPSocket class>>httpGetDocument:args:accept:request: {[sock := > HTTPSocket new. sock connectTo: serverAddr port: connectToPort. > (...]} > Arguments and temporary variables: > url: 'http://modules.squeakfoundation.org/People/gk/? > C=M;O=D' > args: nil > mimeType: '*/*' > requestString: 'Authorization: Basic c3F1ZWFrOnNxdWVhaw== > > ' > serverName: 'modules.squeakfoundation.org' > serverAddr: a ByteArray(193 50 189 4) > port: 80 > sock: a HTTPSocket[connected] > header: nil > length: nil > bare: 'modules.squeakfoundation.org/People/gk/?C=M;O=D' > page: > 'http://modules.squeakfoundation.org:80/People/gk/?C=M;O=D' > list: nil > firstData: nil > aStream: nil > index: nil > connectToHost: 'telemaque.enit.fr' > connectToPort: 3128 > type: nil > newUrl: nil > > > --- The full stack --- > Semaphore>>waitTimeoutMSecs: > HTTPSocket(OldSocket)>>waitForDataUntil: > HTTPSocket>>getResponseUpTo:ignoring: > [] in HTTPSocket class>>httpGetDocument:args:accept:request: {[sock := > HTTPSocket new. sock connectTo: serverAddr port: connectToPort. > (...]} > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > SmallInteger(Integer)>>timesRepeat: > HTTPSocket class>>httpGetDocument:args:accept:request: > HTTPSocket class>>httpGet:args:accept:request: > HTTPSocket class>>httpGet:args:user:passwd: > MCHttpRepository>>allFileNames > MCHttpRepository(MCFileBasedRepository)>>allFileNamesOrCache > MCHttpRepository(MCFileBasedRepository)>>readableFileNames > MCHttpRepository(MCFileBasedRepository)>>allFileNamesForVersionNamed: > MCHttpRepository(MCFileBasedRepository)>>versionWithInfo:ifAbsent: > MCHttpRepository(MCRepository)>>versionWithInfo: > [] in MCRepositoryGroup>>versionWithInfo:ifNone: {[:ea | (ea > versionWithInfo: aVersionInfo) ifNotNilDo: [:v | ^ v]]} > [] in MCRepositoryGroup>>repositoriesDo: {[aBlock value: ea]} > BlockContext>>on:do: > [] in MCRepositoryGroup>>repositoriesDo: {[:ea | [aBlock value: ea] > on: Error do: []]} > Array(SequenceableCollection)>>do: > MCRepositoryGroup>>repositoriesDo: > MCRepositoryGroup>>versionWithInfo:ifNone: > [] in MCVersionDependency>>resolve {[MCRepositoryGroup default > versionWithInfo: versionInfo ifNone: []]} > MCRepositoryGroup>>versionWithInfo:ifNone: > MCVersionDependency>>resolve > MCVersionLoader>>addDependency: > [] in MCVersionLoader>>addVersion: {[:ea | self addDependency: ea]} > Array(SequenceableCollection)>>do: > MCVersionLoader>>addVersion: > MCVersionLoader class>>loadVersion: > MCVersion>>load > [] in MCFileRepositoryInspector(MCVersionInspector)>>load {[self > version > load]} > BlockContext>>ensure: > ...etc... > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Fri Aug 18 14:53:21 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 18 Aug 2006 14:53:21 +0200 Subject: some Pier questions In-Reply-To: <44E5A7A2.2000606@seznam.cz> References: <44E5A7A2.2000606@seznam.cz> Message-ID: Hi Victor, > hi, i don't want to spam the mailing lists, so... please post all the questions to the mailing-list, this is much easier for: (1) other people can profit as well (2) the questions are indexed by Google and people not being in the mailing list can read about it as well (3) other people reply and discuss with you, so I don't have to do all by myself ;-) > i want to use Seaside to build my private site (much more for > learning than anything serious) a i'm considering using Pier as the > basis, there are some problems though (i don't exactly know which > of them are Pier-related) -> i've managed to run a Pier app on > gil.seasidehosting.st and set up some (unix) security but there are > still issues: > the running packages are: Seaside2.6b1.pmm-66 merged with .gk-30 (i > really need WAKomEncoded39), Pier-Model.kph-77, Pier-Seaside.lr-75, > Pier-Security.kph-40 - i loaded them via SqueakMap, so there > weren't the Pier-All and Magritte-All packages, and updated some of > them from the mc.lukas-renggli.ch/ repositories (which wasn't such > of a great idea; i already know). I still don't know what the problems are with the latest versions, since I cannot reproduce on my machine, sorry. > 1. i don't see a way to limit regular users to adding a page or > external file, without allowing them to add a component or internal > file. That's currently not possible. The security-model has to be enhanced to allow that kind of fine grained security. > 2. the 'logout' function doesn't bring me to the first page (and i > can't set the 'first' page for a user after logging in) - i think i > can manage this by editing the components in-image, but it would be > nice to have a direct setting possibility. Logout does simply reset the currently logged in user to anonymous, it is not supposed to jump to a specific page. Though you can implement such a logout action easily by subclassing the PULogou command. > 3. the image keeps growing slowly, even if i do a 'cleanup' before > each save (MCFileBasedRepository flushAllCaches. WARegistry > clearAllHandlers. WAHalo initialize. Smalltalk garbageCollect). If you add contents it naturally grows. Are you using a persistency strategy? > 4. if i break something in the image (or even load a slightly > different version of Pier/Magritte), i don't see a way to migrate > the Pier kernel to another version or constructing a new kernel > with the contents of the old one (pages, components, users&groups, > environments). Really? That shouldn't happen. Can you elaborate? I am using the same image for over a year now and nothing broke. The model of Pier and Magritte didn't changed much in the past. > 5. the 'add' command is kind-of broken: if the operation (add > external file) breaks, there is a entry poit to the new structure > without it actually present - so any acces attempt results in a > walkback and there is no possibility to remove the faulty structure > at all. I don't understand. What is the operation 'add external file'? I don't have such a thing in my image. > 6. the 'remove' command seems not to work (i didn't manage to > remove anything). It works for me, so the question is: do the tests run in your image? > i will be grateful for any advices (even if it'll be along the > lines "throw away the image/pier-kernel and start in a more sane > way")... Feel free to ask as many questions as you like. If you find bugs that you can fix yourself, just commit to the repository. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From cbeler at enit.fr Fri Aug 18 15:20:18 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Fri, 18 Aug 2006 15:20:18 +0200 Subject: [Smallwiki] Re: Magriite-all didnt work for me In-Reply-To: <3F02A52E-AAFB-44D7-BA99-549EB34418E2@iam.unibe.ch> References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> <6AB75FDF-851F-4A88-8566-8FD558D39CEF@iam.unibe.ch> <44E5A742.7010803@yahoo.co.uk> <44E5AF78.1050506@enit.fr> <44E5B075.8040300@enit.fr> <3F02A52E-AAFB-44D7-BA99-549EB34418E2@iam.unibe.ch> Message-ID: <44E5BE92.8050205@enit.fr> Lukas, The new version (Magritte-All-lr.168) you released fixes the problem :) Lukas Renggli a ?crit : >> url: 'http://modules.squeakfoundation.org/People/gk/? >> C=M;O=D' >> > > This is odd, you are trying to access the SqueakSource server of > SqueakFoundation, there is certainly no Magritte/Pier code on there. > Why the heck is Monticello trying to access this repository? :-/ strange anyway :s can you tell me how to make a *-all package that load others ? did you change something ? C?drick From philippe.marschall at gmail.com Fri Aug 18 15:39:22 2006 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Fri, 18 Aug 2006 15:39:22 +0200 Subject: [Smallwiki] Merging In-Reply-To: References: <4499EDD3.5080203@yahoo.co.uk> <4499F111.1090207@yahoo.co.uk> <1BADE569-6739-4E4B-B64B-EF269934FAAA@iam.unibe.ch> <44E058DA.7070909@yahoo.co.uk> Message-ID: <66666f210608180639t583586eey3a4f239c93669b51@mail.gmail.com> rking inspector ... > > > User management may be a candidate for this kind of treatment, > > whereby a > > user having responsibility for a sub-tree may put a user manager in > > place for that subtree only. I beleive that xope does it this way too. > > Exactly and I think the ACL security of Philippe is doing that as > well, at least this was one his of the initial requirements I > defined ... Oh well, no, that's still not implemented yet ;). Yes it sounds compelling a first but we really couldn't come up with good semantics. Also there are no bit Pier installations deployed yet, so there's no imminent need for that. But once it's needed it should not be too hard to implement if you have come up with semantics first. One of the things I learned is "do it the Pier way". That means everything should be a structure, described by Magritte. Try to use as much of the Pier/Magritte infrastructure as possible. This has two advantages: - You have to change less code to remain compatible with the latest versions of Pier. Believe me, I've been doing this for over a year. - You are more compatible with the rest of the Pier stuff out there. Persistence, refactoring, .... So by continuing this, users should be normal structures, editing a user is just an edit command on a user, adding a user is just an add command. See the following example: http://spielverderber.seasidehosting.st/management/users (password for the root user is 'chamdoow') We had it otherwise before and it's really much better now. Less code, easier to maintain, ... you name it. Philippe From cbeler at enit.fr Fri Aug 18 16:38:07 2006 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Fri, 18 Aug 2006 16:38:07 +0200 Subject: [Smallwiki] Re: Magriite-all didnt work for me In-Reply-To: <44E5BE92.8050205@enit.fr> References: <20060817125215.30005.qmail@web86910.mail.ukl.yahoo.com> <6AB75FDF-851F-4A88-8566-8FD558D39CEF@iam.unibe.ch> <44E5A742.7010803@yahoo.co.uk> <44E5AF78.1050506@enit.fr> <44E5B075.8040300@enit.fr> <3F02A52E-AAFB-44D7-BA99-549EB34418E2@iam.unibe.ch> <44E5BE92.8050205@enit.fr> Message-ID: <44E5D0CF.7070902@enit.fr> My problem of 'data was late' is solved now... It seems that loading for the first time a package with dependencies couldn't find the proper repositoty (!) and it was blocking on http://modules.squeakfoundation.org/People/gk/ (I use 3.9g-7054). And as this repo was very slow to respond, it was blocking the loading of Magritte and Pier. I just removed it (anyway it is empty) as Lukas suggested me and now all works... Don't know more ! C?drick From keith.hodges at warwick.ac.uk Thu Aug 24 13:43:07 2006 From: keith.hodges at warwick.ac.uk (keith hodges) Date: Thu, 24 Aug 2006 12:43:07 +0100 Subject: Magma-Seaside-Pier intregration Message-ID: <44ED90CB.6040109@warwick.ac.uk> I have uploaded a couple of packages to the MagmaTester repository and to the Pier repository. I havent tested them in a fresh image yet. Seaside-Examples-Store-Magma - contains the store example with a new control panel for the store repository. Magma seaside - provides a control panel for initializing repositories and some status information. Pier-Model - my latest provided PRMagmaPersistecny and PRMagmaRepository Pier-Seaside - control panel for PRMagmaRepository to select kernels for making persistent. I am away for a few days so really verify that everything works as planned. I havent quite got pier working yet, but I am not sure why not. Perhaps it would be worth chris having a look Keith ___________________________________________________________ All New Yahoo! Mail ? Tired of Vi at gr@! come-ons? Let our SpamGuard protect you. http://uk.docs.yahoo.com/nowyoucan.html From damien.cassou at laposte.net Sat Aug 26 15:39:34 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Sat, 26 Aug 2006 15:39:34 +0200 Subject: No free space in set In-Reply-To: <448ECA08.9090307@yahoo.co.uk> References: <448ECA08.9090307@yahoo.co.uk> Message-ID: <44F04F16.7050502@laposte.net> Keith Hodges wrote: > (sorry wrong thread) > > Error: There is no free space in this set! > > > I got this error when attempting to add a page > > any ideas? Exactly same problem for me today with a new image From damien.cassou at laposte.net Sat Aug 26 15:42:53 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Sat, 26 Aug 2006 15:42:53 +0200 Subject: No free space in set In-Reply-To: <44F04F16.7050502@laposte.net> References: <448ECA08.9090307@yahoo.co.uk> <44F04F16.7050502@laposte.net> Message-ID: <44F04FDD.10003@laposte.net> VM: unix - a SmalltalkImage Image: Squeak3.9gamma [latest update: #7051] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /home/cassou/Documents/squeak/image/victaid Trusted Dir /home/cassou/Documents/squeak/image/victaid/secure Untrusted Dir /home/cassou/Documents/squeak/image/victaid/My Squeak Set(Object)>>error: Receiver: a Set(a PRPage name: 'syntax' a PRPage name: 'pier') Arguments and temporary variables: aString: 'There is no free space in this set!' Receiver's instance variables: tally: 2 array: an Array(a PRPage name: 'syntax' a PRPage name: 'pier') Set>>findElementOrNil: Receiver: a Set(a PRPage name: 'syntax' a PRPage name: 'pier') Arguments and temporary variables: anObject: a PRPage name: 'information' index: 0 Receiver's instance variables: tally: 2 array: an Array(a PRPage name: 'syntax' a PRPage name: 'pier') Set>>noCheckAdd: Receiver: a Set(a PRPage name: 'syntax' a PRPage name: 'pier') Arguments and temporary variables: anObject: a PRPage name: 'information' Receiver's instance variables: tally: 2 array: an Array(a PRPage name: 'syntax' a PRPage name: 'pier') [] in Set>>rehash {[:each | newSelf noCheckAdd: each]} Arguments and temporary variables: newSelf: a Set(a PRPage name: 'syntax' a PRPage name: 'pier') each: a PRPage name: 'information' --- The full stack --- Set(Object)>>error: Set>>findElementOrNil: Set>>noCheckAdd: [] in Set>>rehash {[:each | newSelf noCheckAdd: each]} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Set>>do: Set>>rehash Set(Object)>>veryDeepCopyWith: WeakKeyAssociation(Object)>>veryDeepCopyWith: Array(Object)>>veryDeepCopyWith: WeakIdentityKeyDictionary(Object)>>veryDeepCopyWith: ValueHolder(Object)>>veryDeepCopyWith: Array(Object)>>veryDeepCopyWith: ResponseContinuation(Object)>>veryDeepCopyWith: Association(Object)>>veryDeepCopyWith: Array(Object)>>veryDeepCopyWith: Dictionary(Object)>>veryDeepCopyWith: WALRUCache(Object)>>veryDeepCopyWith: WASession(Object)>>veryDeepCopyWith: Association(Object)>>veryDeepCopyWith: Array(Object)>>veryDeepCopyWith: Dictionary(Object)>>veryDeepCopyWith: WAApplication(Object)>>veryDeepCopyWith: Association(Object)>>veryDeepCopyWith: Array(Object)>>veryDeepCopyWith: Dictionary(Object)>>veryDeepCopyWith: WADispatcher(Object)>>veryDeepCopyWith: WAKom(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: BlockContext(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: BlockContext(Object)>>veryDeepCopyWith: Process(Object)>>veryDeepCopyWith: Semaphore(Object)>>veryDeepCopyWith: WAProcessMonitor(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: BlockContext(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: BlockContext(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: BlockContext(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: BlockContext(Object)>>veryDeepCopyWith: MethodContext(Object)>>veryDeepCopyWith: MessageNotUnderstood(Object)>>veryDeepCopyWith: WAWalkback(Object)>>veryDeepCopyWith: BlockContext(Object)>>veryDeepCopyWith: WAAnswerHandler(Object)>>veryDeepCopyWith: WAStateHolder(Object)>>veryDeepCopyWith: WeakKeyAssociation(Object)>>veryDeepCopyWith: Array(Object)>>veryDeepCopyWith: WeakIdentityKeyDictionary(Object)>>veryDeepCopyWith: WAStateRegistry(Object)>>veryDeepCopyWith: WASession(Object)>>veryDeepCopyWith: Association(Object)>>veryDeepCopyWith: Array(Object)>>veryDeepCopyWith: Dictionary(Object)>>veryDeepCopyWith: -- and more not shown -- From damien.cassou at laposte.net Mon Aug 28 19:39:26 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Mon, 28 Aug 2006 19:39:26 +0200 Subject: [Pier] TreeView is not sorted Message-ID: <44F32A4E.3080807@laposte.net> Hi, PRTreeView display sub items using the order of the children dictionary. A dictionary has no order, therefore items are shuffled. I would like to have sub items in the order in which I added them or, better, having a component to let me give my order. What is the best solution ? I thought of a 'priority' property for structures. This priority would then be used to sort the elements. From renggli at iam.unibe.ch Mon Aug 28 19:59:34 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 28 Aug 2006 19:59:34 +0200 Subject: [Pier] TreeView is not sorted In-Reply-To: <44F32A4E.3080807@laposte.net> References: <44F32A4E.3080807@laposte.net> Message-ID: <5958495D-AB2C-4A45-BAA4-F76D932BA786@iam.unibe.ch> > PRTreeView display sub items using the order of the children > dictionary. > A dictionary has no order, therefore items are shuffled. I would > like to > have sub items in the order in which I added them or, better, having a > component to let me give my order. > > What is the best solution ? Load the latest version of Pier, I fixed that yesterday :-) > I thought of a 'priority' property for structures. This priority > would then be used to sort the elements. The enhanced children visitor would allow to do exactly that. You just have to redefine the default sort-block in the default context used for new sessions. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From damien.cassou at laposte.net Mon Aug 28 20:54:18 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Mon, 28 Aug 2006 20:54:18 +0200 Subject: [Pier] TreeView is not sorted In-Reply-To: <5958495D-AB2C-4A45-BAA4-F76D932BA786@iam.unibe.ch> References: <44F32A4E.3080807@laposte.net> <5958495D-AB2C-4A45-BAA4-F76D932BA786@iam.unibe.ch> Message-ID: <44F33BDA.7010108@laposte.net> Lukas Renggli wrote: >> PRTreeView display sub items using the order of the children >> dictionary. >> A dictionary has no order, therefore items are shuffled. I would >> like to >> have sub items in the order in which I added them or, better, having a >> component to let me give my order. >> >> What is the best solution ? > > Load the latest version of Pier, I fixed that yesterday :-) What a synchronisation :-) >> I thought of a 'priority' property for structures. This priority >> would then be used to sort the elements. > > The enhanced children visitor would allow to do exactly that. You > just have to redefine the default sort-block in the default context > used for new sessions. Ok, but I need something to base the order on if I want to sort by creation time for exemple. In this case, I would need to modify ChildrenDecoration>>#add: to add an index, or Structure>>initialize to add a timestamp property. What do you think ? From renggli at iam.unibe.ch Mon Aug 28 21:14:13 2006 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 28 Aug 2006 21:14:13 +0200 Subject: [Pier] TreeView is not sorted In-Reply-To: <44F33BDA.7010108@laposte.net> References: <44F32A4E.3080807@laposte.net> <5958495D-AB2C-4A45-BAA4-F76D932BA786@iam.unibe.ch> <44F33BDA.7010108@laposte.net> Message-ID: >>> I thought of a 'priority' property for structures. This priority >>> would then be used to sort the elements. >> >> The enhanced children visitor would allow to do exactly that. You >> just have to redefine the default sort-block in the default context >> used for new sessions. > > Ok, but I need something to base the order on if I want to sort by > creation time for exemple. In this case, I would need to modify > ChildrenDecoration>>#add: to add an index, or Structure>>initialize to > add a timestamp property. What do you think ? There are other possibilities: - Put the new value into a property and initialize it lazily. - Use the hook method that is called on the class-side of all concrete decorations when a structure is added to initialize a property. You don't need the decoration in this case, just the hook. Hope this helps, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From damien.cassou at laposte.net Mon Aug 28 21:18:07 2006 From: damien.cassou at laposte.net (Damien Cassou) Date: Mon, 28 Aug 2006 21:18:07 +0200 Subject: [Pier] TreeView is not sorted In-Reply-To: References: <44F32A4E.3080807@laposte.net> <5958495D-AB2C-4A45-BAA4-F76D932BA786@iam.unibe.ch> <44F33BDA.7010108@laposte.net> Message-ID: <44F3416F.1060503@laposte.net> Lukas Renggli wrote: >>>> I thought of a 'priority' property for structures. This priority >>>> would then be used to sort the elements. >>> The enhanced children visitor would allow to do exactly that. You >>> just have to redefine the default sort-block in the default context >>> used for new sessions. >> Ok, but I need something to base the order on if I want to sort by >> creation time for exemple. In this case, I would need to modify >> ChildrenDecoration>>#add: to add an index, or Structure>>initialize to >> add a timestamp property. What do you think ? > > There are other possibilities: > > - Put the new value into a property and initialize it lazily. > > - Use the hook method that is called on the class-side of all > concrete decorations when a structure is added to initialize a > property. You don't need the decoration in this case, just the hook. Thank you Lukas