From ducasse at iam.unibe.ch Thu Feb 1 14:11:07 2007 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Thu, 1 Feb 2007 14:11:07 +0100 Subject: Examples of Pier Sites In-Reply-To: <41B98270-8675-4716-9024-CB46E0AF5AA9@iam.unibe.ch> References: <45BF76E1.7020001@sonaural.com> <45BF7863.1050709@sonaural.com> <66666f210701300924k3c09a0a1lf9338a81c9cf2d21@mail.gmail.com> <41B98270-8675-4716-9024-CB46E0AF5AA9@iam.unibe.ch> Message-ID: <283DA213-9D55-4A85-A92F-DC6D8CE8D533@iam.unibe.ch> David rotlisberge did SmallBB in VisualWorks (I do not remember whether it is in Seaside). But we could give it if people are interested. Stef On 30 janv. 07, at 19:06, Lukas Renggli wrote: >>> I was going to send an email about Pier and I couldn't come up >>> with any >>> example sites. Can anyone reply with some links that I can use? >> >> http://www.lukas-renggli.ch/ >> http://swiki.gsug.org/ > > http://ese.unibe.ch > http://spielverderber.seasidehosting.st/ > http://create.seasidehosting.st/ > >>> oh... another question. Anyone run a "forum" in Pier? >> >> I know of no forum add-on for Pier. > > An early version of Pier (SmallWiki) had a forum component. I don't > know if it still works on the latest version, probably not. I'll > forward this mail to the developer of the code, maybe he can give you > some pointers on how to get at least the version ... > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From brad at sonaural.com Thu Feb 1 17:04:09 2007 From: brad at sonaural.com (Brad Fuller) Date: Thu, 01 Feb 2007 08:04:09 -0800 Subject: Examples of Pier Sites In-Reply-To: <283DA213-9D55-4A85-A92F-DC6D8CE8D533@iam.unibe.ch> References: <45BF76E1.7020001@sonaural.com> <45BF7863.1050709@sonaural.com> <66666f210701300924k3c09a0a1lf9338a81c9cf2d21@mail.gmail.com> <41B98270-8675-4716-9024-CB46E0AF5AA9@iam.unibe.ch> <283DA213-9D55-4A85-A92F-DC6D8CE8D533@iam.unibe.ch> Message-ID: <45C20F79.7070902@sonaural.com> st?phane ducasse wrote: > David rotlisberge did SmallBB in VisualWorks (I do not remember > whether it is in Seaside). > But we could give it if people are interested. Thanks, Stef. I relayed the information to the person requesting. He hasn't responded so maybe he's not interested in pursuing seaside/pier/forum. I'll keep trying ;-) Thanks! brad > > Stef > On 30 janv. 07, at 19:06, Lukas Renggli wrote: > >>>> I was going to send an email about Pier and I couldn't come up >>>> with any >>>> example sites. Can anyone reply with some links that I can use? >>> http://www.lukas-renggli.ch/ >>> http://swiki.gsug.org/ >> http://ese.unibe.ch >> http://spielverderber.seasidehosting.st/ >> http://create.seasidehosting.st/ >> >>>> oh... another question. Anyone run a "forum" in Pier? >>> I know of no forum add-on for Pier. >> An early version of Pier (SmallWiki) had a forum component. I don't >> know if it still works on the latest version, probably not. I'll >> forward this mail to the developer of the code, maybe he can give you >> some pointers on how to get at least the version ... >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From squeak at c3com.ch Fri Feb 2 22:47:57 2007 From: squeak at c3com.ch (=?ISO-8859-1?Q?David_R=F6thlisberger?=) Date: Fri, 02 Feb 2007 22:47:57 +0100 Subject: Examples of Pier Sites In-Reply-To: <41B98270-8675-4716-9024-CB46E0AF5AA9@iam.unibe.ch> References: <45BF76E1.7020001@sonaural.com> <45BF7863.1050709@sonaural.com> <66666f210701300924k3c09a0a1lf9338a81c9cf2d21@mail.gmail.com> <41B98270-8675-4716-9024-CB46E0AF5AA9@iam.unibe.ch> Message-ID: <45C3B18D.3030209@c3com.ch> >>> oh... another question. Anyone run a "forum" in Pier? >>> >> I know of no forum add-on for Pier. >> > > An early version of Pier (SmallWiki) had a forum component. I don't > know if it still works on the latest version, probably not. I'll > forward this mail to the developer of the code, maybe he can give you > some pointers on how to get at least the version ... SmallBB isn't really a forum component for SmallWiki 1. The very first version was designed like that, but then we decided to make SmallBB independent of SmallWiki by using Seaside as its backend instead of SmallWiki 1. So you can use SmallBB independently of SmallWiki 1 (and of course Pier), but you cannot directly use this forum as a component for SmallWiki 1 or Pier. SmallBB is available for VisualWorks on the public Cincom Store, there's no version available for Squeak. It's also based on an older version of Seaside, so a migration to Squeak and to current Seaside would require some work. Even more work is required to implement SmallBB as a forum component for Pier. If someone wants to do that, I'm willing to help, but I don't have any plans to do such an implementation myself. Kind regards, David From renggli at iam.unibe.ch Fri Feb 2 23:00:38 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 2 Feb 2007 23:00:38 +0100 Subject: Examples of Pier Sites In-Reply-To: <45C3B18D.3030209@c3com.ch> References: <45BF76E1.7020001@sonaural.com> <45BF7863.1050709@sonaural.com> <66666f210701300924k3c09a0a1lf9338a81c9cf2d21@mail.gmail.com> <41B98270-8675-4716-9024-CB46E0AF5AA9@iam.unibe.ch> <45C3B18D.3030209@c3com.ch> Message-ID: > SmallBB is available for VisualWorks on the public Cincom Store, > there's > no version available for Squeak. It's also based on an older > version of > Seaside, so a migration to Squeak and to current Seaside would require > some work. Even more work is required to implement SmallBB as a forum > component for Pier. Excellent. Since Pier is based on Seaside this should work out of the box. As long as a Seaside application doesn't require any special setup it can just be plugged into Pier from the web interface. > If someone wants to do that, I'm willing to help, but I don't have any > plans to do such an implementation myself. The only problem is that Pier currently doesn't run on VisualWorks. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Fri Feb 2 23:06:40 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 2 Feb 2007 23:06:40 +0100 Subject: Magritte Bug In-Reply-To: <4cb10a4f0702021351i6ee59c03wc734d201e3c2dde@mail.gmail.com> References: <4cb10a4f0702021351i6ee59c03wc734d201e3c2dde@mail.gmail.com> Message-ID: > Lukas, I've run into a minor anomaly in MAReport from Magritte lr. > 187. Have a look at this method: > > renderTableCaptionOn: html > self description caption ifNotNilDo: [ :value | > html > tag: 'caption' > do: self description caption ] > > The problem is that #caption isn't implemented in any object that > would conceivably used in this context. I leave it to you to sort > this one out. That's odd. The code in my image looks completely different: MAReport>>renderTableCaptionOn: html (html tag: 'caption') with: self tableCaption Are you talking about Magritte-All.lr.187? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sat Feb 3 19:36:23 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 3 Feb 2007 19:36:23 +0100 Subject: Status of Pier (Update) In-Reply-To: <1A70C3DE-47FD-4CC3-A2D6-B8E0A3AB3F26@iam.unibe.ch> References: <1A70C3DE-47FD-4CC3-A2D6-B8E0A3AB3F26@iam.unibe.ch> Message-ID: <701A11E5-3765-474B-8970-41106C63D6B3@iam.unibe.ch> >> Second, is there any plan to expand on the RESTfulness of Pier? I >> mean, I'm not a die-hard REST person or anything, but there are >> times it would be nice to use URL's. I think the above suggested >> handling would probably be enough. > > Yep, that's a requirement. Thanks that you reported this, I probably > wouldn't have noticed it myself. > >> One thing that makes me want this is the difficulty of pointing to >> another page in your Pier site from a custom component. I know you >> have the #goto: message on anchor, but (1) I need it anywhere a URL >> could be used, since I am using "html tag:" to do some tags not in >> seaside (an HTML image map to be specific). And (2) the #goto: >> message expects a structure that can be tough to get a hold of >> sometimes. The easiest thing for me would be if I could simply >> point my image map at the URL as a string, since that part is >> public and I don't care if the user is logged in or not. > > Glad that you ask. For the blog component I also felt the need to > have just the url and not only an anchor. I think I will need to add > that sooner or later. Shouldn't be too difficult though. The Pier context object (representing the current browsing context of the user) has now two additional methods: - #url returns a REST-full instance of WAUrl. All session information will is discarded when using this URL, but the current structure and command and view are preserved. It is save to bookmark this URL and to give it to your friends. - #urlOn: what returns a Seaside URL triggering an action callback that sets the receiving context. This URL can also be bookmarked but should not be passed to your friends. As long as your Seaside session is valid, it will remember all the state. After the Seaside session expired the URL has the same effect as #url. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From azreal1977 at hotmail.com Sat Feb 3 20:57:27 2007 From: azreal1977 at hotmail.com (J J) Date: Sat, 03 Feb 2007 19:57:27 +0000 Subject: Status of Pier (Update) In-Reply-To: <701A11E5-3765-474B-8970-41106C63D6B3@iam.unibe.ch> Message-ID: Ausome, that's great. Pier is really getting solid. >From: Lukas Renggli >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Status of Pier (Update) >Date: Sat, 3 Feb 2007 19:36:23 +0100 > > >> Second, is there any plan to expand on the RESTfulness of Pier? I > >> mean, I'm not a die-hard REST person or anything, but there are > >> times it would be nice to use URL's. I think the above suggested > >> handling would probably be enough. > > > > Yep, that's a requirement. Thanks that you reported this, I probably > > wouldn't have noticed it myself. > > > >> One thing that makes me want this is the difficulty of pointing to > >> another page in your Pier site from a custom component. I know you > >> have the #goto: message on anchor, but (1) I need it anywhere a URL > >> could be used, since I am using "html tag:" to do some tags not in > >> seaside (an HTML image map to be specific). And (2) the #goto: > >> message expects a structure that can be tough to get a hold of > >> sometimes. The easiest thing for me would be if I could simply > >> point my image map at the URL as a string, since that part is > >> public and I don't care if the user is logged in or not. > > > > Glad that you ask. For the blog component I also felt the need to > > have just the url and not only an anchor. I think I will need to add > > that sooner or later. Shouldn't be too difficult though. > >The Pier context object (representing the current browsing context of >the user) has now two additional methods: > >- #url returns a REST-full instance of WAUrl. All session information >will is discarded when using this URL, but the current structure and >command and view are preserved. It is save to bookmark this URL and >to give it to your friends. > >- #urlOn: what returns a Seaside URL triggering an action callback >that sets the receiving context. This URL can also be bookmarked but >should not be passed to your friends. As long as your Seaside session >is valid, it will remember all the state. After the Seaside session >expired the URL has the same effect as #url. > >Cheers, >Lukas > >-- >Lukas Renggli >http://www.lukas-renggli.ch > > > >_______________________________________________ >SmallWiki, Magritte, Pier and Related Tools ... >https://www.iam.unibe.ch/mailman/listinfo/smallwiki _________________________________________________________________ Laugh, share and connect with Windows Live Messenger http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=hmtagline From tblanchard at mac.com Sat Feb 3 21:16:13 2007 From: tblanchard at mac.com (Todd Blanchard) Date: Sat, 3 Feb 2007 12:16:13 -0800 Subject: Starting the tutorial Message-ID: <9D2CA34F-642E-447C-AA22-0E7C37F44650@mac.com> I just installed magritte into a 3.8 image that already had seaside. It was tricky as it kept freezing post installation in WeakArray finalization code. Several tries and some playing with the process browser allowed me to suspend/lower the priority, and kill the errant process. So I have it. Nifty. I'm working through the tutorial and the very first item - add a text area called 'comment' to person is a puzzler. I hunt down the MATextAreaComponent thinking I'll use a StringDescription but give it a componentClass of MATextAreaComponent. But then I read the comment: I display an html text area for the magritte MATextAreaDescription. So I go looking for that and the class does not exist. I found MAMemoDescription because of the exception I got about lineCount not being implemented on MAStringDescription. So you should probably fix that comment or change the name of the class back or something. Otherwise, I think I like what I see so far. -Todd Blanchard From tblanchard at mac.com Sat Feb 3 21:24:53 2007 From: tblanchard at mac.com (Todd Blanchard) Date: Sat, 3 Feb 2007 12:24:53 -0800 Subject: Labels Message-ID: <52ADE81B-DE4B-4D82-B13C-62448EAA48D1@mac.com> I find having to provide the label for every attribute tedious. In the application I am considering porting to Magritte, I infer the label from the selector nearly all of the time. The code I use for this is: selector asString withSpacesBeforeCapitalLetters capitalized works pretty well. -Todd Blanchard From philippe.marschall at gmail.com Sat Feb 3 23:05:56 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Sat, 3 Feb 2007 23:05:56 +0100 Subject: Status of Pier (Update) In-Reply-To: <701A11E5-3765-474B-8970-41106C63D6B3@iam.unibe.ch> References: <1A70C3DE-47FD-4CC3-A2D6-B8E0A3AB3F26@iam.unibe.ch> <701A11E5-3765-474B-8970-41106C63D6B3@iam.unibe.ch> Message-ID: <66666f210702031405s768fdb9br5d43b695c7f3a894@mail.gmail.com> 2007/2/3, Lukas Renggli : > >> Second, is there any plan to expand on the RESTfulness of Pier? I > >> mean, I'm not a die-hard REST person or anything, but there are > >> times it would be nice to use URL's. I think the above suggested > >> handling would probably be enough. > > > > Yep, that's a requirement. Thanks that you reported this, I probably > > wouldn't have noticed it myself. > > > >> One thing that makes me want this is the difficulty of pointing to > >> another page in your Pier site from a custom component. I know you > >> have the #goto: message on anchor, but (1) I need it anywhere a URL > >> could be used, since I am using "html tag:" to do some tags not in > >> seaside (an HTML image map to be specific). And (2) the #goto: > >> message expects a structure that can be tough to get a hold of > >> sometimes. The easiest thing for me would be if I could simply > >> point my image map at the URL as a string, since that part is > >> public and I don't care if the user is logged in or not. > > > > Glad that you ask. For the blog component I also felt the need to > > have just the url and not only an anchor. I think I will need to add > > that sooner or later. Shouldn't be too difficult though. > > The Pier context object (representing the current browsing context of > the user) has now two additional methods: > > - #url returns a REST-full instance of WAUrl. All session information > will is discarded when using this URL, but the current structure and > command and view are preserved. It is save to bookmark this URL and > to give it to your friends. > > - #urlOn: what returns a Seaside URL triggering an action callback > that sets the receiving context. This URL can also be bookmarked but > should not be passed to your friends. As long as your Seaside session > is valid, it will remember all the state. After the Seaside session > expired the URL has the same effect as #url. Was about time ;) Now I need to update my plug-ins :( Philippe From renggli at iam.unibe.ch Sat Feb 3 23:07:00 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 3 Feb 2007 23:07:00 +0100 Subject: Labels In-Reply-To: <52ADE81B-DE4B-4D82-B13C-62448EAA48D1@mac.com> References: <52ADE81B-DE4B-4D82-B13C-62448EAA48D1@mac.com> Message-ID: <2E64F4F4-D846-426B-BEE7-6A10DC12CAFD@iam.unibe.ch> > I find having to provide the label for every attribute tedious. In > the application I am considering porting to Magritte, I infer the > label from the selector nearly all of the time. The code I use for > this is: > > selector asString withSpacesBeforeCapitalLetters capitalized > > works pretty well. Unfortunately that doesn't work for people living outside english speaking countries. Most applications we commercially write do not have english labels, some are even translated to multiple languages. I understand that it is maybe strange to have the label in the constructor already. After all there are may descriptions that never appear in a user-interface. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sat Feb 3 23:13:30 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 3 Feb 2007 23:13:30 +0100 Subject: Starting the tutorial In-Reply-To: <9D2CA34F-642E-447C-AA22-0E7C37F44650@mac.com> References: <9D2CA34F-642E-447C-AA22-0E7C37F44650@mac.com> Message-ID: <08A49489-D161-49B8-8E15-F167A5E51DE9@iam.unibe.ch> > I just installed magritte into a 3.8 image that already had seaside. > It was tricky as it kept freezing post installation in WeakArray > finalization code. Several tries and some playing with the process > browser allowed me to suspend/lower the priority, and kill the errant > process. So I have it. Nifty. Older versions of Seaside used WeakArrays. Unfortunately WeakArrays do not work in Squeak and were therefor removed from Seaside. > I'm working through the tutorial and the very first item - add a text > area called 'comment' to person is a puzzler. I hunt down the > MATextAreaComponent thinking I'll use a StringDescription but give > it a componentClass of MATextAreaComponent. The MAMemoDescription is for multiline text. > But then I read the comment: > I display an html text area for the magritte MATextAreaDescription. Comments are cool, but it is always a pain to write and update. Magritte-Seaside-lr.211 fixes this issue. Thanks for reporting. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sun Feb 4 21:30:48 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 4 Feb 2007 21:30:48 +0100 Subject: Status of Pier In-Reply-To: References: Message-ID: <50A3D044-825C-42E2-95B8-2DD630BB3109@iam.unibe.ch> > (PRCompatibility confirm: 'Would you like to create a Seaside > application for Pier?') > ifTrue: [^ self]. > > This seems to cause the application to not create a Pier > application if you say yes, so I clicked no and sure enough, it > built everything. I could fix it, but I thought I would check with > you first. Ohh yeah, this is a bug. I just recently re-factored this method and introduced this error. The latest version fixes this issue. Lukas > > Thanks, > Jason > > >> From: Lukas Renggli >> Reply-To: "Magritte, Pier and Related Tools ..." >> >> To: "Magritte, Pier and Related Tools ..." >> Subject: Re: Status of Pier >> Date: Tue, 30 Jan 2007 23:27:30 +0100 >> >> > First, in my image, if you go to a page and then go to lunch, come >> > back and hour later and click a link you get dropped back to the >> > front page because your session has expired. But I thought Pier >> > used the URL to be able bookmark, surf the side via URL etc. In >> > fact, I thought it even worked this way before I put the security >> > package in. >> >> Yes, it should work and remember the page even if the session >> expired. >> >> > Has this been fixed? It seems like if you click on a link that has >> > a URL, but an old session Pier could just make a new session and >> > apply that to the page the user is trying to go to. If the user is >> > not allowed to see that resource with the blank session then kick >> > them back to the front like now, but if the page is not restricted >> > they should see it. >> >> This is a bug in Seaside. I fixed it, and the scenario you describe >> works when you load the latest version: >> >> Name: Seaside2.7a1-lr.162 >> Author: lr >> Time: 30 January 2007, 11:23:44 pm >> UUID: b22fe0c4-77c1-4e3d-99f7-331a368c4337 >> Ancestors: Seaside2.7a1-pmm.161 >> >> > Second, is there any plan to expand on the RESTfulness of Pier? I >> > mean, I'm not a die-hard REST person or anything, but there are >> > times it would be nice to use URL's. I think the above suggested >> > handling would probably be enough. >> >> Yep, that's a requirement. Thanks that you reported this, I probably >> wouldn't have noticed it myself. >> >> > One thing that makes me want this is the difficulty of pointing to >> > another page in your Pier site from a custom component. I know you >> > have the #goto: message on anchor, but (1) I need it anywhere a URL >> > could be used, since I am using "html tag:" to do some tags not in >> > seaside (an HTML image map to be specific). And (2) the #goto: >> > message expects a structure that can be tough to get a hold of >> > sometimes. The easiest thing for me would be if I could simply >> > point my image map at the URL as a string, since that part is >> > public and I don't care if the user is logged in or not. >> >> Glad that you ask. For the blog component I also felt the need to >> have just the url and not only an anchor. I think I will need to add >> that sooner or later. Shouldn't be too difficult though. >> >> > And lastly, I have had some users complain about the ugly URL's. I >> > know you can say that they shouldn't look at the URL, etc. etc., >> > but if we can make this better why not? >> > >> > What I was thinking was, how hard would it be to change Pier so >> > that the URL part stays, but at least the session (and maybe the >> > command and view fields as well) could optionally be cookies. And >> > this could even be something configured in the /seaside/config/pier >> > page. >> >> Go to the Seaside configuration page and enable 'Use Session >> Cookies'. This will put the session key into a cookie, if possible. >> >> > Thanks in advance. You may have ways to do all these things by >> > now, but I thought I would check. >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > _________________________________________________________________ > Talk now to your Hotmail contacts with Windows Live Messenger. > http://get.live.com/messenger/overview > -- Lukas Renggli http://www.lukas-renggli.ch From azreal1977 at hotmail.com Sun Feb 4 21:44:24 2007 From: azreal1977 at hotmail.com (J J) Date: Sun, 04 Feb 2007 20:44:24 +0000 Subject: Status of Pier In-Reply-To: <50A3D044-825C-42E2-95B8-2DD630BB3109@iam.unibe.ch> Message-ID: Fast work! :) I just upgraded everything (seaside from 2.6, pier, magritte) in my working image and now seaside doesn't want to display my Pier app anymore. I tried removing it and recreating it. I have my own kernel and I can see in the image that everything is still there, I just don't know how to force seaside to show it again. The normal Pier app is still there, and everything else looks just fine. When I try to access mine, it just says the default "/seaside/yourPierApp not found". Is there any Pier registerMyAppAgain or something you know of? :) Thanks, Jason >From: Lukas Renggli >To: J J >CC: Magritte Mailing List >Subject: Re: Status of Pier >Date: Sun, 4 Feb 2007 21:30:48 +0100 > >>(PRCompatibility confirm: 'Would you like to create a Seaside application >>for Pier?') >> ifTrue: [^ self]. >> >>This seems to cause the application to not create a Pier application if >>you say yes, so I clicked no and sure enough, it built everything. I >>could fix it, but I thought I would check with you first. > >Ohh yeah, this is a bug. I just recently re-factored this method and >introduced this error. The latest version fixes this issue. > >Lukas > >> >>Thanks, >>Jason >> >> >>>From: Lukas Renggli >>>Reply-To: "Magritte, Pier and Related Tools ..." >>> >>>To: "Magritte, Pier and Related Tools ..." >>>Subject: Re: Status of Pier >>>Date: Tue, 30 Jan 2007 23:27:30 +0100 >>> >>> > First, in my image, if you go to a page and then go to lunch, come >>> > back and hour later and click a link you get dropped back to the >>> > front page because your session has expired. But I thought Pier >>> > used the URL to be able bookmark, surf the side via URL etc. In >>> > fact, I thought it even worked this way before I put the security >>> > package in. >>> >>>Yes, it should work and remember the page even if the session expired. >>> >>> > Has this been fixed? It seems like if you click on a link that has >>> > a URL, but an old session Pier could just make a new session and >>> > apply that to the page the user is trying to go to. If the user is >>> > not allowed to see that resource with the blank session then kick >>> > them back to the front like now, but if the page is not restricted >>> > they should see it. >>> >>>This is a bug in Seaside. I fixed it, and the scenario you describe >>>works when you load the latest version: >>> >>> Name: Seaside2.7a1-lr.162 >>> Author: lr >>> Time: 30 January 2007, 11:23:44 pm >>> UUID: b22fe0c4-77c1-4e3d-99f7-331a368c4337 >>> Ancestors: Seaside2.7a1-pmm.161 >>> >>> > Second, is there any plan to expand on the RESTfulness of Pier? I >>> > mean, I'm not a die-hard REST person or anything, but there are >>> > times it would be nice to use URL's. I think the above suggested >>> > handling would probably be enough. >>> >>>Yep, that's a requirement. Thanks that you reported this, I probably >>>wouldn't have noticed it myself. >>> >>> > One thing that makes me want this is the difficulty of pointing to >>> > another page in your Pier site from a custom component. I know you >>> > have the #goto: message on anchor, but (1) I need it anywhere a URL >>> > could be used, since I am using "html tag:" to do some tags not in >>> > seaside (an HTML image map to be specific). And (2) the #goto: >>> > message expects a structure that can be tough to get a hold of >>> > sometimes. The easiest thing for me would be if I could simply >>> > point my image map at the URL as a string, since that part is >>> > public and I don't care if the user is logged in or not. >>> >>>Glad that you ask. For the blog component I also felt the need to >>>have just the url and not only an anchor. I think I will need to add >>>that sooner or later. Shouldn't be too difficult though. >>> >>> > And lastly, I have had some users complain about the ugly URL's. I >>> > know you can say that they shouldn't look at the URL, etc. etc., >>> > but if we can make this better why not? >>> > >>> > What I was thinking was, how hard would it be to change Pier so >>> > that the URL part stays, but at least the session (and maybe the >>> > command and view fields as well) could optionally be cookies. And >>> > this could even be something configured in the /seaside/config/pier >>> > page. >>> >>>Go to the Seaside configuration page and enable 'Use Session >>>Cookies'. This will put the session key into a cookie, if possible. >>> >>> > Thanks in advance. You may have ways to do all these things by >>> > now, but I thought I would check. >>> >>>Cheers, >>>Lukas >>> >>>-- >>>Lukas Renggli >>>http://www.lukas-renggli.ch >>> >>> >>> >>>_______________________________________________ >>>SmallWiki, Magritte, Pier and Related Tools ... >>>https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >>_________________________________________________________________ >>Talk now to your Hotmail contacts with Windows Live Messenger. >>http://get.live.com/messenger/overview >> > >-- >Lukas Renggli >http://www.lukas-renggli.ch > > _________________________________________________________________ >From predictions to trailers, check out the MSN Entertainment Guide to the Academy Awards® http://movies.msn.com/movies/oscars2007/?icid=ncoscartagline1 From renggli at iam.unibe.ch Sun Feb 4 22:57:45 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 4 Feb 2007 22:57:45 +0100 Subject: Status of Pier In-Reply-To: References: Message-ID: > I just upgraded everything (seaside from 2.6, pier, magritte) in my > working image and now seaside doesn't want to display my Pier app > anymore. Only the very latest version of Seaside 2.7a works. This is a requirement for Magritte and Pier. > Is there any Pier registerMyAppAgain or something you know of? :) To re-register the Pier kernel with Seaside you might want to execute "PRPierFrame initialize" again. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From azreal1977 at hotmail.com Sun Feb 4 23:00:38 2007 From: azreal1977 at hotmail.com (J J) Date: Sun, 04 Feb 2007 22:00:38 +0000 Subject: Status of Pier In-Reply-To: Message-ID: Oh, I picked the latest seaside. I only meant to say that I was comming from seaside 2.6. I think I found the problem. Seaside doesn't seem to like directories anymore. I had my application in: /seaside/jbj/myApp and I had to move it to the top level to get it to work. >From: Lukas Renggli >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Status of Pier >Date: Sun, 4 Feb 2007 22:57:45 +0100 > > > I just upgraded everything (seaside from 2.6, pier, magritte) in my > > working image and now seaside doesn't want to display my Pier app > > anymore. > >Only the very latest version of Seaside 2.7a works. This is a >requirement for Magritte and Pier. > > > Is there any Pier registerMyAppAgain or something you know of? :) > >To re-register the Pier kernel with Seaside you might want to execute >"PRPierFrame initialize" again. > >Cheers, >Lukas > >-- >Lukas Renggli >http://www.lukas-renggli.ch > > > >_______________________________________________ >SmallWiki, Magritte, Pier and Related Tools ... >https://www.iam.unibe.ch/mailman/listinfo/smallwiki _________________________________________________________________ Laugh, share and connect with Windows Live Messenger http://clk.atdmt.com/MSN/go/msnnkwme0020000001msn/direct/01/?href=http://imagine-msn.com/messenger/launch80/default.aspx?locale=en-us&source=hmtagline From tblanchard at mac.com Sun Feb 4 23:04:31 2007 From: tblanchard at mac.com (Todd Blanchard) Date: Sun, 4 Feb 2007 14:04:31 -0800 Subject: Another tutorial bug Message-ID: <0D91F67D-DFB9-49AE-B8A9-31980ABE0235@mac.com> It looks like MAScaffolder has been renamed MAAdaptiveModel? - the tutorial should probably be updated to reflect this. From azreal1977 at hotmail.com Sun Feb 4 23:11:53 2007 From: azreal1977 at hotmail.com (J J) Date: Sun, 04 Feb 2007 22:11:53 +0000 Subject: Another bug :) (was Re: Status of Pier) In-Reply-To: <1A70C3DE-47FD-4CC3-A2D6-B8E0A3AB3F26@iam.unibe.ch> Message-ID: I use a login and no persistency at the moment, so when I tried to log in I got a DNU on #critical. PULogin tries to call #execute: in the perstistancy which calls #critical on it's mutex, but since PRNullPersistancy doesn't have a mutex (it is nil), I get a DNU. I just did an override in PRNullPersistancy for #execute: to simply call #apply: to get it working for me. >From: Lukas Renggli >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Status of Pier >Date: Tue, 30 Jan 2007 23:27:30 +0100 > > > First, in my image, if you go to a page and then go to lunch, come > > back and hour later and click a link you get dropped back to the > > front page because your session has expired. But I thought Pier > > used the URL to be able bookmark, surf the side via URL etc. In > > fact, I thought it even worked this way before I put the security > > package in. > >Yes, it should work and remember the page even if the session expired. > > > Has this been fixed? It seems like if you click on a link that has > > a URL, but an old session Pier could just make a new session and > > apply that to the page the user is trying to go to. If the user is > > not allowed to see that resource with the blank session then kick > > them back to the front like now, but if the page is not restricted > > they should see it. > >This is a bug in Seaside. I fixed it, and the scenario you describe >works when you load the latest version: > > Name: Seaside2.7a1-lr.162 > Author: lr > Time: 30 January 2007, 11:23:44 pm > UUID: b22fe0c4-77c1-4e3d-99f7-331a368c4337 > Ancestors: Seaside2.7a1-pmm.161 > > > Second, is there any plan to expand on the RESTfulness of Pier? I > > mean, I'm not a die-hard REST person or anything, but there are > > times it would be nice to use URL's. I think the above suggested > > handling would probably be enough. > >Yep, that's a requirement. Thanks that you reported this, I probably >wouldn't have noticed it myself. > > > One thing that makes me want this is the difficulty of pointing to > > another page in your Pier site from a custom component. I know you > > have the #goto: message on anchor, but (1) I need it anywhere a URL > > could be used, since I am using "html tag:" to do some tags not in > > seaside (an HTML image map to be specific). And (2) the #goto: > > message expects a structure that can be tough to get a hold of > > sometimes. The easiest thing for me would be if I could simply > > point my image map at the URL as a string, since that part is > > public and I don't care if the user is logged in or not. > >Glad that you ask. For the blog component I also felt the need to >have just the url and not only an anchor. I think I will need to add >that sooner or later. Shouldn't be too difficult though. > > > And lastly, I have had some users complain about the ugly URL's. I > > know you can say that they shouldn't look at the URL, etc. etc., > > but if we can make this better why not? > > > > What I was thinking was, how hard would it be to change Pier so > > that the URL part stays, but at least the session (and maybe the > > command and view fields as well) could optionally be cookies. And > > this could even be something configured in the /seaside/config/pier > > page. > >Go to the Seaside configuration page and enable 'Use Session >Cookies'. This will put the session key into a cookie, if possible. > > > Thanks in advance. You may have ways to do all these things by > > now, but I thought I would check. > >Cheers, >Lukas > >-- >Lukas Renggli >http://www.lukas-renggli.ch > > > >_______________________________________________ >SmallWiki, Magritte, Pier and Related Tools ... >https://www.iam.unibe.ch/mailman/listinfo/smallwiki _________________________________________________________________ Check out all that glitters with the MSN Entertainment Guide to the Academy Awards® http://movies.msn.com/movies/oscars2007/?icid=ncoscartagline2 From billksun at yahoo.com Mon Feb 5 06:44:31 2007 From: billksun at yahoo.com (Bill Sun) Date: Sun, 4 Feb 2007 21:44:31 -0800 (PST) Subject: Pier Blog bug Message-ID: <20070205054431.7196.qmail@web53309.mail.yahoo.com> Hi, I was trying out the Blog component and it doesn't seem to work for me. After adding the Blog component, I get this error: WARenderedHtmlRoot(Object)>>doesNotUnderstand: #rss Surely enough I can't find any implementors of #rss in Seaside or Pier. The following method is the one that's sending #rss to a WARenderedHtmlRoot object. PRRecentView(PRBlogView)>>updateRoot: aHtmlRoot super updateRoot: aHtmlRoot. aHtmlRoot rss title: self blog feedTitle; url: self subscriptionUrl Since the Blog component works in your screencast, I guess you might be missing an update to the to repository (Seaside?) somewhere. I am using Pier-All-lr.151, Pier-Blog-lr.29, and Seaside2.7a1-lr.166. -Bill ____________________________________________________________________________________ No need to miss a message. Get email on-the-go with Yahoo! Mail for Mobile. Get started. http://mobile.yahoo.com/mail -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070205/3bc723c8/attachment.html From renggli at iam.unibe.ch Mon Feb 5 07:19:00 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 5 Feb 2007 07:19:00 +0100 Subject: Pier Blog bug In-Reply-To: <20070205054431.7196.qmail@web53309.mail.yahoo.com> References: <20070205054431.7196.qmail@web53309.mail.yahoo.com> Message-ID: > I was trying out the Blog component and it doesn't seem to work for > me. After adding the Blog component, I get this error: > > WARenderedHtmlRoot(Object)>>doesNotUnderstand: #rss You need the RSRSS package of Philippe Marshall from SqueakSource. MCHttpRepository location: 'http://www.squeaksource.com/rsrss' user: '' password: '' > I am using Pier-All-lr.151, Pier-Blog-lr.29, and Seaside2.7a1-lr.166. That should be fine, it is the same as in my image. Sorry that I forgot to mention the prerequisites. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Mon Feb 5 07:22:53 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 5 Feb 2007 07:22:53 +0100 Subject: Another bug :) (was Re: Status of Pier) In-Reply-To: References: Message-ID: <7533F6F3-2EDC-43F7-AE00-DBFBD6F2505E@iam.unibe.ch> > I use a login and no persistency at the moment, so when I tried to > log in I got a DNU on #critical. PULogin tries to call #execute: > in the perstistancy which calls #critical on it's mutex, but since > PRNullPersistancy doesn't have a mutex (it is nil), I get a DNU. I > just did an override in PRNullPersistancy for #execute: to simply > call #apply: to get it working for me. I guess you have to re-initialize the persistency in the kernel. I just recently moved the session mutex from the kernel to the place where it really belongs, the persistency. PRKernel instances do: [ :each | each persistency: PRNullPersistency new ] After that everything should work without modifying PRNullPersistency. The Semaphore is important in PRNullPersistency, as this ensures that the model does not get corrupted by concurrent modifications. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Mon Feb 5 07:23:26 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 5 Feb 2007 07:23:26 +0100 Subject: Another tutorial bug In-Reply-To: <0D91F67D-DFB9-49AE-B8A9-31980ABE0235@mac.com> References: <0D91F67D-DFB9-49AE-B8A9-31980ABE0235@mac.com> Message-ID: <1D634449-9AA3-458E-9101-2C950252786E@iam.unibe.ch> > It looks like MAScaffolder has been renamed MAAdaptiveModel? - the > tutorial should probably be updated to reflect this. Thanks for reporting, I' ll change that. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From azreal1977 at hotmail.com Mon Feb 5 07:31:44 2007 From: azreal1977 at hotmail.com (J J) Date: Mon, 05 Feb 2007 06:31:44 +0000 Subject: Another bug :) (was Re: Status of Pier) In-Reply-To: <7533F6F3-2EDC-43F7-AE00-DBFBD6F2505E@iam.unibe.ch> Message-ID: Ah ok, done. Thanks. In testing this, I just noticed that when I come back to a session that is old and expired and do login I get a DNU on nil again. This time it looks like PULogin is calling anscestor and there is nothing there. >From: Lukas Renggli >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Another bug :) (was Re: Status of Pier) >Date: Mon, 5 Feb 2007 07:22:53 +0100 > > > I use a login and no persistency at the moment, so when I tried to > > log in I got a DNU on #critical. PULogin tries to call #execute: > > in the perstistancy which calls #critical on it's mutex, but since > > PRNullPersistancy doesn't have a mutex (it is nil), I get a DNU. I > > just did an override in PRNullPersistancy for #execute: to simply > > call #apply: to get it working for me. > >I guess you have to re-initialize the persistency in the kernel. I >just recently moved the session mutex from the kernel to the place >where it really belongs, the persistency. > > PRKernel instances do: [ :each | > each persistency: PRNullPersistency new ] > >After that everything should work without modifying PRNullPersistency. > >The Semaphore is important in PRNullPersistency, as this ensures that >the model does not get corrupted by concurrent modifications. > >Cheers, >Lukas > >-- >Lukas Renggli >http://www.lukas-renggli.ch > > > >_______________________________________________ >SmallWiki, Magritte, Pier and Related Tools ... >https://www.iam.unibe.ch/mailman/listinfo/smallwiki _________________________________________________________________ Invite your Hotmail contacts to join your friends list with Windows Live Spaces http://clk.atdmt.com/MSN/go/msnnkwsp0070000001msn/direct/01/?href=http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mkt=en-us From renggli at iam.unibe.ch Mon Feb 5 08:21:29 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 5 Feb 2007 08:21:29 +0100 Subject: Another bug :) (was Re: Status of Pier) In-Reply-To: References: Message-ID: <90EFAA46-69E4-498C-9A58-AC794D03F495@iam.unibe.ch> > In testing this, I just noticed that when I come back to a session > that is > old and expired and do login I get a DNU on nil again. This time > it looks > like PULogin is calling anscestor and there is nothing there. Nice catch. It is fixed in: Name: Pier-Security-lr.68 Author: lr Time: 5 February 2007, 8:19:33 am UUID: 0ba0f70b-1f5f-4592-b314-878fdb10c9dd Ancestors: Pier-Security-lr.67 Thanks for reporting! Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From koubo2006 at yengawa.jpn.org Mon Feb 5 10:56:32 2007 From: koubo2006 at yengawa.jpn.org (Koji Yokokawa) Date: Mon, 05 Feb 2007 18:56:32 +0900 Subject: Report all pages for any user? Message-ID: <20070205181930.03A9.KOUBO2006@yengawa.jpn.org> Hi, I have a question about PRReportView. In Pier-Seaside-lr.125, PRReportView reveals all contents for any user. PRReportView>>buildStructures ^ self context enumerator all contents I think that the pages which are prohibited for the user should not be reported. So that, the code will be modifyed like this. PRReportView>>buildStructures ^ Array streamContents: [:stream | self context structure enumerator all do: [:each | (each isValidCommand: self context command class in: self context) ifTrue: [stream nextPut: each]]] -- ! Koji Yokokawa http://yengawa.com/ ^self new! From renggli at iam.unibe.ch Mon Feb 5 11:18:54 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 5 Feb 2007 11:18:54 +0100 Subject: Report all pages for any user? In-Reply-To: <20070205181930.03A9.KOUBO2006@yengawa.jpn.org> References: <20070205181930.03A9.KOUBO2006@yengawa.jpn.org> Message-ID: > PRReportView>>buildStructures > ^ Array > streamContents: [:stream | self context structure enumerator all > do: [:each | (each isValidCommand: self context command class > in: self context) > ifTrue: [stream nextPut: each]]] Thanks for reporting. This is fixed in the latest version. The same items are also filtered now in the browse-view. Name: Pier-All-lr.152 Author: lr Time: 5 February 2007, 11:15:43 am UUID: 8190db74-61fa-45fb-9eec-3a22a451ee64 Ancestors: Pier-All-lr.151 Dependencies: Pier-Model-lr.119, Pier-Tests-lr.56, Pier-Seaside-lr. 126, Pier-OmniBrowser-lr.22, Pier-Security-lr.69 Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From azreal1977 at hotmail.com Mon Feb 5 19:58:28 2007 From: azreal1977 at hotmail.com (J J) Date: Mon, 05 Feb 2007 18:58:28 +0000 Subject: Another bug :) (was Re: Status of Pier) In-Reply-To: <90EFAA46-69E4-498C-9A58-AC794D03F495@iam.unibe.ch> Message-ID: Thanks for the fix! My site is pretty well perfect at this point. >From: Lukas Renggli >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Another bug :) (was Re: Status of Pier) >Date: Mon, 5 Feb 2007 08:21:29 +0100 > > > In testing this, I just noticed that when I come back to a session > > that is > > old and expired and do login I get a DNU on nil again. This time > > it looks > > like PULogin is calling anscestor and there is nothing there. > >Nice catch. It is fixed in: > > Name: Pier-Security-lr.68 > Author: lr > Time: 5 February 2007, 8:19:33 am > UUID: 0ba0f70b-1f5f-4592-b314-878fdb10c9dd > Ancestors: Pier-Security-lr.67 > >Thanks for reporting! > >Cheers, >Lukas > >-- >Lukas Renggli >http://www.lukas-renggli.ch > > > >_______________________________________________ >SmallWiki, Magritte, Pier and Related Tools ... >https://www.iam.unibe.ch/mailman/listinfo/smallwiki _________________________________________________________________ FREE online classifieds from Windows Live Expo – buy and sell with people you know http://clk.atdmt.com/MSN/go/msnnkwex0010000001msn/direct/01/?href=http://expo.live.com?s_cid=Hotmail_tagline_12/06 From tblanchard at mac.com Tue Feb 6 07:48:25 2007 From: tblanchard at mac.com (Todd Blanchard) Date: Mon, 5 Feb 2007 22:48:25 -0800 Subject: Magritte #description Message-ID: <8B843730-88BB-4D69-A742-2099D6C31EDF@mac.com> I'm playing with porting an existing model driven application to magritte and I'm hitting very frequent conflicts on the method name #description. I would urge you to change this in the future to something less generic like modelDescription. Just sharing my pain. :-) -Todd Blanchard From renggli at iam.unibe.ch Tue Feb 6 07:59:43 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 6 Feb 2007 07:59:43 +0100 Subject: Magritte #description In-Reply-To: <8B843730-88BB-4D69-A742-2099D6C31EDF@mac.com> References: <8B843730-88BB-4D69-A742-2099D6C31EDF@mac.com> Message-ID: <3E298C9F-B832-4667-902B-A34E15712CCB@iam.unibe.ch> > I'm playing with porting an existing model driven application to > magritte and I'm hitting very frequent conflicts on the method name > #description. I would urge you to change this in the future to > something less generic like modelDescription. Yep, that has been discussed several times already. I've got a list of many other selectors, that would be less likely to conflict. My favorite one is still #descriptor. What hinders me to change it right now is that there are many big (commercial) projects relying on Magritte. It will be certainly changed in the next big version, but probably not today or tomorrow. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Thu Feb 8 21:06:50 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 8 Feb 2007 21:06:50 +0100 Subject: Pier... safe usage. In-Reply-To: References: Message-ID: Hi Eric, > I am looking into using Pier just so that I can use a wiki based on > Smalltalk and get more experience with it (Pier and Smalltalk). My > question is based on the persistence... it seems all of the data is > being saved in the image. Is there any 'safe usage' suggestions? > Or do I just save the image from time to time? I noticed there was > a magma backend, and I was curious as to whether one could start > out with using the image for persistence and later move to magma? > I'm thinking of this, as I just don't want to start with magma > (yet). One step at a time. Do you have any suggestions or tips > for persisting the data safely? (Just don't want to lose > everything I put in it) please check the mailing list archive, there has been a lot of discussion on this topic. Personally I use the image persistency for all my running instances, and it works well so far. Of course there is also a certain danger, if you don't have backups and screw up your image. With OSProcess loaded the snapshots are taken in a forked instance of the vm, doing the whole thing transparently in the background. The magma persistency is certainly very interesting, but I don't know if it works with the latest version of Pier. As far as I know the Magma persistency can be activated later on as well, but you have to ask Keith, the author of this plug-in. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Thu Feb 8 21:26:55 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Thu, 8 Feb 2007 21:26:55 +0100 Subject: Pier... safe usage. In-Reply-To: References: Message-ID: > What are the odds of getting the code you use for doing the image > persistancy with OSProcess? (Or is that already in Pier) Yes, it is already in Pier. You just have to load OSProcess from SqueakMap and use an Unix VM. Cheers, Lukas > > :-) > > Cheers, > > Brian > > On Feb 8, 2007, at 1:06 PM, Lukas Renggli wrote: > >> Hi Eric, >> >>> I am looking into using Pier just so that I can use a wiki based on >>> Smalltalk and get more experience with it (Pier and Smalltalk). My >>> question is based on the persistence... it seems all of the data is >>> being saved in the image. Is there any 'safe usage' suggestions? >>> Or do I just save the image from time to time? I noticed there was >>> a magma backend, and I was curious as to whether one could start >>> out with using the image for persistence and later move to magma? >>> I'm thinking of this, as I just don't want to start with magma >>> (yet). One step at a time. Do you have any suggestions or tips >>> for persisting the data safely? (Just don't want to lose >>> everything I put in it) >> >> please check the mailing list archive, there has been a lot of >> discussion on this topic. >> >> Personally I use the image persistency for all my running instances, >> and it works well so far. Of course there is also a certain danger, >> if you don't have backups and screw up your image. With OSProcess >> loaded the snapshots are taken in a forked instance of the vm, doing >> the whole thing transparently in the background. >> >> The magma persistency is certainly very interesting, but I don't know >> if it works with the latest version of Pier. As far as I know the >> Magma persistency can be activated later on as well, but you have to >> ask Keith, the author of this plug-in. >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Thu Feb 8 22:36:57 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Thu, 08 Feb 2007 21:36:57 +0000 Subject: Pier... safe usage. In-Reply-To: References: Message-ID: <45CB97F9.8040502@yahoo.co.uk> Yes dont worry about starting with an image and migrating to magma later on. There is even a half way option, which keeps your data in the image, but backs up any changes made to the in image data to the magma database as you go. There is a little bit of further integration work to go in supporting magma and the latest pier, but when the time comes, dont worry turning Magma on is virtually transparent Keith > > if it works with the latest version of Pier. As far as I know the > Magma persistency can be activated later on as well, but you have to > ask Keith, the author of this plug-in. > > Cheers, > Lukas > > ___________________________________________________________ Now you can scan emails quickly with a reading pane. Get the new Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html From sebjulliand at gmail.com Sun Feb 11 11:15:37 2007 From: sebjulliand at gmail.com (=?ISO-8859-1?Q?S=E9bastien_Julliand?=) Date: Sun, 11 Feb 2007 11:15:37 +0100 Subject: Content enumeration Message-ID: <4f6c865a0702110215k34abeda5naf261cba1db9a9e2@mail.gmail.com> Hello everyone, I'm working on a widget that could display the complete structure of Pier (actually based on something like PRTreeWidget). The widget is here for displaying purpose and it instanciates a visitor which walk over the structure and gather the information. I assume that I need this visitor if I want to achieve my goal but a question remains: what if I want to list every piece of content like images,...? For example, I have a page with an image and my widget shows: a PRDocument PRInternalLink PRText How can I know if there is an image here? In other words how could I display more details? Cheers, S?bastien -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070211/5f5b405f/attachment.html From ducasse at iam.unibe.ch Sun Feb 11 11:29:54 2007 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 11 Feb 2007 11:29:54 +0100 Subject: Content enumeration In-Reply-To: <4f6c865a0702110215k34abeda5naf261cba1db9a9e2@mail.gmail.com> References: <4f6c865a0702110215k34abeda5naf261cba1db9a9e2@mail.gmail.com> Message-ID: <7C49190C-49A3-48E3-BE17-D1DD74F5AA6F@iam.unibe.ch> Sebastien I was thinking that you could have a widget acting as an inspector (not showing complete tree) Did you look at the way joomla does it to let the end user select where an information should be displayed they have something like -----all -----none -----section -----page ------section1 and you can move a kind of cursor to say what you select stef On 11 f?vr. 07, at 11:15, S?bastien Julliand wrote: > Hello everyone, > > I'm working on a widget that could display the complete structure > of Pier (actually based on something like PRTreeWidget). The widget > is here for displaying purpose and it instanciates a visitor which > walk over the structure and gather the information. I assume that I > need this visitor if I want to achieve my goal but a question > remains: what if I want to list every piece of content like > images,...? > > For example, I have a page with an image and my widget shows: > > a PRDocument > PRInternalLink > PRText > > How can I know if there is an image here? In other words how could > I display more details? > > Cheers, > S?bastien > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at iam.unibe.ch Sun Feb 11 11:35:09 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 11 Feb 2007 11:35:09 +0100 Subject: Content enumeration In-Reply-To: <4f6c865a0702110215k34abeda5naf261cba1db9a9e2@mail.gmail.com> References: <4f6c865a0702110215k34abeda5naf261cba1db9a9e2@mail.gmail.com> Message-ID: <0A1BDB42-7E37-4975-932B-948E193B6CE7@iam.unibe.ch> Hi S?bastien, > Pier (actually based on something like PRTreeWidget). The widget is > here for displaying purpose and it instanciates a visitor which > walk over the structure and gather the information. I assume that I > need this visitor if I want to achieve my goal but a question > remains: what if I want to list every piece of content like > images,...? visitors can walk over structures and contents. The only thing you have to do is to start visiting the document when you encounter a structure. As most visitors don't visit structures *and* documents (there are still a few that do), this connection is not made by default. > How can I know if there is an image here? In other words how could > I display more details? Visit the document and collect all the entries that you are interested in ;-) Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From norbert at hartl.name Tue Feb 13 15:05:24 2007 From: norbert at hartl.name (Norbert Hartl) Date: Tue, 13 Feb 2007 15:05:24 +0100 Subject: Infinite recursion with Magritte Message-ID: <1171375525.31439.63.camel@localhost> Hi, I have a problem with infinite recursion in Magritte. This problem was discussed on this list before. The problem is having circular dependencies in descriptions. I tried to utilize the hints from Lukas to use reference: (MADynamicObject on: (MyObject descriptionsWithoutReferences)) Having a descriptionsWithoutReferences introduces an infinite loop by itself. So I changed it to getDescriptionsWithoutReferences. This prevents the infinite recursion but doesn't work really well with the ActiveRecord implementation from Ramon (at least in my case). So I decided to change Magritte not to do infinite recursion. I changed MADescriptionBuilder>>for: anObject ^ cache at: anObject ifAbsent: [ cache at: anObject put: true. cache at: anObject put: (self build: anObject). ]. I know this looks very ugly but I don't have an idea how to do this more elegant. My question is if this change introduces problems elsewhere in Magritte? I don't like to fix one problem by creating another one :) thanks, Norbert From renggli at iam.unibe.ch Tue Feb 13 22:24:20 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 13 Feb 2007 22:24:20 +0100 Subject: Infinite recursion with Magritte In-Reply-To: <1171375525.31439.63.camel@localhost> References: <1171375525.31439.63.camel@localhost> Message-ID: <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> > So I decided to change Magritte not to do infinite recursion. I > changed > > MADescriptionBuilder>>for: anObject > ^ cache at: anObject ifAbsent: [ > cache at: anObject put: true. > cache at: anObject put: (self build: anObject). > ]. Looks like an interesting trick, but don't you then end up with the value true in some of your meta-models? Wouldn't it make more sense to use nil instead? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From akuhn at gmx.ch Tue Feb 13 22:30:13 2007 From: akuhn at gmx.ch (Adrian Kuhn) Date: Tue, 13 Feb 2007 22:30:13 +0100 Subject: Resource links not rendered Message-ID: <600F98F2-95DA-4709-8C9E-387D99F49F6A@gmx.ch> Hi Lukas, Please have a look at http://smallwiki.unibe.ch/moose/mseformat/ there are three links on resources which are not rendered as HTML links. For each link an MSE file has been uploaded, but after successful upload the link just showed up as text. cheers, -- Adrian From renggli at iam.unibe.ch Tue Feb 13 22:43:02 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 13 Feb 2007 22:43:02 +0100 Subject: Resource links not rendered In-Reply-To: <600F98F2-95DA-4709-8C9E-387D99F49F6A@gmx.ch> References: <600F98F2-95DA-4709-8C9E-387D99F49F6A@gmx.ch> Message-ID: <5F58F713-2037-4260-9E7B-9AF5457EFF5B@iam.unibe.ch> Hi Adrian, > Please have a look at > > http://smallwiki.unibe.ch/moose/mseformat/ > > there are three links on resources which are not rendered as HTML > links. For each link an MSE file has been uploaded, but after > successful upload the link just showed up as text. I don't exactly know what happened here, but obviously SmallWiki got the mime-type wrong. As far as I remember it uses a database of file extensions, so the next time you upload such a file give it a .txt ending. I manually fixed the mime-types and the links do appear correctly now. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From akuhn at gmx.ch Tue Feb 13 22:42:53 2007 From: akuhn at gmx.ch (Adrian Kuhn) Date: Tue, 13 Feb 2007 22:42:53 +0100 Subject: Infinite recursion with Magritte In-Reply-To: <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> Message-ID: <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> Better put a placeholder in the cache and then do a oneWayBecome afterwards. cache at: key ifAbsent: [ cache at: key put: (placeholder := Object new). cache at: key put: (newValue := (self build: anObject)). placeholder oneWayBecome: newValue ]. And if you want it bullet proof, you use Meta's MessageRecorder :) cheers, -- Adrian On 13 Feb 2007, at 22:24 , Lukas Renggli wrote: >> So I decided to change Magritte not to do infinite recursion. I >> changed >> >> MADescriptionBuilder>>for: anObject >> ^ cache at: anObject ifAbsent: [ >> cache at: anObject put: true. >> cache at: anObject put: (self build: anObject). >> ]. > > Looks like an interesting trick, but don't you then end up with the > value true in some of your meta-models? Wouldn't it make more sense > to use nil instead? > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From akuhn at gmx.ch Tue Feb 13 22:50:28 2007 From: akuhn at gmx.ch (Adrian Kuhn) Date: Tue, 13 Feb 2007 22:50:28 +0100 Subject: Resource links not rendered In-Reply-To: <5F58F713-2037-4260-9E7B-9AF5457EFF5B@iam.unibe.ch> References: <600F98F2-95DA-4709-8C9E-387D99F49F6A@gmx.ch> <5F58F713-2037-4260-9E7B-9AF5457EFF5B@iam.unibe.ch> Message-ID: Thanks! Is there a way (be it image hacking, I don't mind) to add MSE to the file list? We might use this file extension more often in the future. -- Adrian On 13 Feb 2007, at 22:43 , Lukas Renggli wrote: > Hi Adrian, > >> Please have a look at >> >> http://smallwiki.unibe.ch/moose/mseformat/ >> >> there are three links on resources which are not rendered as HTML >> links. For each link an MSE file has been uploaded, but after >> successful upload the link just showed up as text. > > I don't exactly know what happened here, but obviously SmallWiki got > the mime-type wrong. As far as I remember it uses a database of file > extensions, so the next time you upload such a file give it a .txt > ending. I manually fixed the mime-types and the links do appear > correctly now. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at iam.unibe.ch Tue Feb 13 23:03:51 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 13 Feb 2007 23:03:51 +0100 Subject: Resource links not rendered In-Reply-To: References: <600F98F2-95DA-4709-8C9E-387D99F49F6A@gmx.ch> <5F58F713-2037-4260-9E7B-9AF5457EFF5B@iam.unibe.ch> Message-ID: <5E047B8D-B999-4D2B-83C1-75F3A0E5D0FF@iam.unibe.ch> > Is there a way (be it image hacking, I don't mind) to add MSE to > the file list? We might use this file extension more often in the > future. That should be fixed for further uploads, and if my small hack did not help please shout again. Cheers, Lukas > > -- Adrian > > On 13 Feb 2007, at 22:43 , Lukas Renggli wrote: > >> Hi Adrian, >> >>> Please have a look at >>> >>> http://smallwiki.unibe.ch/moose/mseformat/ >>> >>> there are three links on resources which are not rendered as HTML >>> links. For each link an MSE file has been uploaded, but after >>> successful upload the link just showed up as text. >> >> I don't exactly know what happened here, but obviously SmallWiki got >> the mime-type wrong. As far as I remember it uses a database of file >> extensions, so the next time you upload such a file give it a .txt >> ending. I manually fixed the mime-types and the links do appear >> correctly now. >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From norbert at hartl.name Wed Feb 14 00:36:01 2007 From: norbert at hartl.name (Norbert Hartl) Date: Wed, 14 Feb 2007 00:36:01 +0100 Subject: Infinite recursion with Magritte In-Reply-To: <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> Message-ID: <1171409761.24859.21.camel@localhost> On Tue, 2007-02-13 at 22:24 +0100, Lukas Renggli wrote: > > So I decided to change Magritte not to do infinite recursion. I > > changed > > > > MADescriptionBuilder>>for: anObject > > ^ cache at: anObject ifAbsent: [ > > cache at: anObject put: true. > > cache at: anObject put: (self build: anObject). > > ]. > > Looks like an interesting trick, but don't you then end up with the > value true in some of your meta-models? Wouldn't it make more sense > to use nil instead? > Hmmm, I don't know if I got your point. The value at: anObject gets discarded after self build returns (If I understand IdentityDictionary the right way). So there is no difference between true and nil. I just didn't spend a second thinking about what to put as a placeholder. Now I can see the problem if there is a second invocation with the same object before the placeholder gets exchanged. Do you mean this? Norbert From norbert at hartl.name Wed Feb 14 00:41:56 2007 From: norbert at hartl.name (Norbert Hartl) Date: Wed, 14 Feb 2007 00:41:56 +0100 Subject: Infinite recursion with Magritte In-Reply-To: <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> Message-ID: <1171410116.24859.28.camel@localhost> On Tue, 2007-02-13 at 22:42 +0100, Adrian Kuhn wrote: > Better put a placeholder in the cache and then do a oneWayBecome > afterwards. > > cache at: key ifAbsent: [ > cache at: key put: (placeholder := Object new). > cache at: key put: (newValue := (self build: anObject)). > placeholder oneWayBecome: newValue ]. > > And if you want it bullet proof, you use Meta's MessageRecorder :) > Hmmm, I don't have a oneWayBecome: in my image. But I like the idea if I understand you correct. But wouldn't cache at: key ifAbsent: [ cache at: key put: (placeholder := Object new). placeholder oneWayBecome: self build: anObject ]. perfectly sufficient? (Ok, if I had a oneWayBecome ;) ). Is this something totally different to protoobjects become: ??? very curious, Norbert From norbert at hartl.name Wed Feb 14 00:42:51 2007 From: norbert at hartl.name (Norbert Hartl) Date: Wed, 14 Feb 2007 00:42:51 +0100 Subject: Infinite recursion with Magritte In-Reply-To: <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> Message-ID: <1171410171.24859.30.camel@localhost> > And if you want it bullet proof, you use Meta's MessageRecorder :) > Oh, btw. _what_ is Meta's MessageRecorder? Norbert From akuhn at gmx.ch Wed Feb 14 00:51:43 2007 From: akuhn at gmx.ch (Adrian Kuhn) Date: Wed, 14 Feb 2007 00:51:43 +0100 Subject: Infinite recursion with Magritte In-Reply-To: <1171410171.24859.30.camel@localhost> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> <1171410171.24859.30.camel@localhost> Message-ID: <97AF24F1-F4EF-4F60-9F33-3E4B8A8BE004@gmx.ch> oneWayBecome is a VW method as it seems, but I dont know its Squeakish name. Meta is a meta-description framework for VW, and there I implemented a placeholder that records everything that happens to it, and later on, replays all that on the actual object. -- Adrian On 14 Feb 2007, at 0:42 , Norbert Hartl wrote: > >> And if you want it bullet proof, you use Meta's MessageRecorder :) >> > Oh, btw. _what_ is Meta's MessageRecorder? > > Norbert > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at iam.unibe.ch Wed Feb 14 07:39:50 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 14 Feb 2007 07:39:50 +0100 Subject: Infinite recursion with Magritte In-Reply-To: <97AF24F1-F4EF-4F60-9F33-3E4B8A8BE004@gmx.ch> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> <1171410171.24859.30.camel@localhost> <97AF24F1-F4EF-4F60-9F33-3E4B8A8BE004@gmx.ch> Message-ID: <5B4E97F0-FE08-4F78-80CB-A4D32C734A4D@iam.unibe.ch> > oneWayBecome is a VW method as it seems, but I dont know its > Squeakish name. #becomeForward: > Meta is a meta-description framework for VW, and there I > implemented a placeholder that records everything that happens to > it, and later on, replays all that on the actual object. Due to its use of #doesNotUnderstand: you are screwed up as soon as such an instance ends up in a debugger, database, tires to receive a special selector ... In my opinion #doesNotUnderstand: simply does not scale for most of such things, as I explained when describing MADynamicObject (what is somehow similar, but less sophisticated). Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Wed Feb 14 09:28:18 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 14 Feb 2007 09:28:18 +0100 Subject: Infinite recursion with Magritte In-Reply-To: <5B4E97F0-FE08-4F78-80CB-A4D32C734A4D@iam.unibe.ch> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> <1171410171.24859.30.camel@localhost> <97AF24F1-F4EF-4F60-9F33-3E4B8A8BE004@gmx.ch> <5B4E97F0-FE08-4F78-80CB-A4D32C734A4D@iam.unibe.ch> Message-ID: The latest version of Magritte fixes the reported problem without any #becomeForward: or #doesNotUnderstand: tricks. The idea is simple, it is a two step process: 1. The empty container description is registered in the cache. 2. The element descriptions are added to the container. -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- Name: Magritte-Model-lr.239 Author: lr Time: 14 February 2007, 9:21:13 am UUID: 51418e16-08d2-4a88-8dcb-1d2b6d786282 Ancestors: Magritte-Model-lr.238 - fixed problem with recursion in MADescriptionBuilder -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- Name: Magritte-Tests-lr.104 Author: lr Time: 14 February 2007, 9:21:18 am UUID: 06eff360-a6fe-49d6-9425-dd87f3d83499 Ancestors: Magritte-Tests-lr.103 - fixed problem with recursion in MADescriptionBuilder -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- -+- The tests have been updated as well. Hope this helps for your problem? Now the next step is to get rid of recursion when traversing (e.g. for validation) cyclic graphs, but I'll wait with that until somebody complains ;-) Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From norbert at hartl.name Wed Feb 14 10:46:34 2007 From: norbert at hartl.name (Norbert Hartl) Date: Wed, 14 Feb 2007 10:46:34 +0100 Subject: Infinite recursion with Magritte In-Reply-To: References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> <1171410171.24859.30.camel@localhost> <97AF24F1-F4EF-4F60-9F33-3E4B8A8BE004@gmx.ch> <5B4E97F0-FE08-4F78-80CB-A4D32C734A4D@iam.unibe.ch> Message-ID: <1171446394.24859.35.camel@localhost> On Wed, 2007-02-14 at 09:28 +0100, Lukas Renggli wrote: > The latest version of Magritte fixes the reported problem without any > #becomeForward: or #doesNotUnderstand: tricks. The idea is simple, it > is a two step process: > > 1. The empty container description is registered in the cache. > > 2. The element descriptions are added to the container. > I cannot say I understand your changes completely but they look good and more important they work. > The tests have been updated as well. Hope this helps for your problem? > Yes, it does. Thanks very much. > Now the next step is to get rid of recursion when traversing (e.g. > for validation) cyclic graphs, but I'll wait with that until somebody > complains ;-) > I will :) regards, Norbert From akuhn at gmx.ch Wed Feb 14 12:04:19 2007 From: akuhn at gmx.ch (Adrian Kuhn) Date: Wed, 14 Feb 2007 12:04:19 +0100 Subject: Infinite recursion with Magritte In-Reply-To: <5B4E97F0-FE08-4F78-80CB-A4D32C734A4D@iam.unibe.ch> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> <1171410171.24859.30.camel@localhost> <97AF24F1-F4EF-4F60-9F33-3E4B8A8BE004@gmx.ch> <5B4E97F0-FE08-4F78-80CB-A4D32C734A4D@iam.unibe.ch> Message-ID: <54CBF4AE-1288-4C82-979E-47BBA0B809DE@gmx.ch> > The latest version of Magritte fixes the reported problem without any > #becomeForward: or #doesNotUnderstand: tricks. The idea is simple, it > is a two step process: > > 1. The empty container description is registered in the cache. > > 2. The element descriptions are added to the container. Very nice! >> Meta is a meta-description framework for VW, and there I >> implemented a placeholder that records everything that happens to >> it, and later on, replays all that on the actual object. > > Due to its use of #doesNotUnderstand: you are screwed up as soon as > such an instance ends up in a debugger, database, tires to receive a > special selector ... MessageRecorder requires some attention, but is not that worse. Debugger sessions are fine, they get recorded and replayed later on, but that does not hurt anyone. For persistency, it is very important that MessageRecorders have a clearly defined lifetime in your design. And that you double check if all recorders (including spawned recorders) are stopped and got replaced when leaving the piece of code that used them. The only thing I could not solve, was the case when a spawned recorder is used a receiver of an ifThen. > In my opinion #doesNotUnderstand: simply does not scale for most of > such things, as I explained when describing MADynamicObject (what is > somehow similar, but less sophisticated). It scales IMHO, but has a lot of very nasty pitfall. Therefor only skilled engineers should use DNU or become. > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From keith_hodges at yahoo.co.uk Wed Feb 14 12:37:34 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Wed, 14 Feb 2007 11:37:34 +0000 Subject: Infinite recursion with Magritte In-Reply-To: <54CBF4AE-1288-4C82-979E-47BBA0B809DE@gmx.ch> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> <1171410171.24859.30.camel@localhost> <97AF24F1-F4EF-4F60-9F33-3E4B8A8BE004@gmx.ch> <5B4E97F0-FE08-4F78-80CB-A4D32C734A4D@iam.unibe.ch> <54CBF4AE-1288-4C82-979E-47BBA0B809DE@gmx.ch> Message-ID: <45D2F47E.7030401@yahoo.co.uk> Dear Adrian, > > code that used them. The only thing I could not solve, was the case > when a spawned recorder is used a receiver of an ifThen. > There is a trick that you might be able to use in this case. You can trap this case by implementing #mustBeBooleanIn: context For an example of code which does this, see: http://www.squeaksource.com/Null Keith ___________________________________________________________ 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 akuhn at gmx.ch Wed Feb 14 14:01:42 2007 From: akuhn at gmx.ch (Adrian Kuhn) Date: Wed, 14 Feb 2007 14:01:42 +0100 Subject: Infinite recursion with Magritte In-Reply-To: <45D2F47E.7030401@yahoo.co.uk> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> <1171410171.24859.30.camel@localhost> <97AF24F1-F4EF-4F60-9F33-3E4B8A8BE004@gmx.ch> <5B4E97F0-FE08-4F78-80CB-A4D32C734A4D@iam.unibe.ch> <54CBF4AE-1288-4C82-979E-47BBA0B809DE@gmx.ch> <45D2F47E.7030401@yahoo.co.uk> Message-ID: <119F3642-4289-4F6E-A809-88C7210DFC5C@gmx.ch> Wow, that's cool stuff, Keith! Just read the comment of the Squeak version, where can I get the mentioned VW version? ^^ -- Adrian On 14 Feb 2007, at 12:37 , Keith Hodges wrote: > Dear Adrian, >> >> code that used them. The only thing I could not solve, was the case >> when a spawned recorder is used a receiver of an ifThen. >> > There is a trick that you might be able to use in this case. > > You can trap this case by implementing #mustBeBooleanIn: context > > For an example of code which does this, see: > > http://www.squeaksource.com/Null > > Keith > > > > > ___________________________________________________________ > 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 > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From ducasse at iam.unibe.ch Wed Feb 14 15:36:25 2007 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Wed, 14 Feb 2007 15:36:25 +0100 Subject: Generic object question Message-ID: <44C7E1BA-78A6-4CBF-88B8-5095F2E20D32@iam.unibe.ch> hi in one of my application I have an object that represent a bibliographic entry. I has a set of fields that really depends on the type of the entry. An article will have different fields than a journal.... Now how could I use magritte to describe such object. Should I have a dictionary that returns MAdefinition at the object level (the table could be shared between all the instances of the classes. Stef From renggli at iam.unibe.ch Wed Feb 14 16:04:55 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Wed, 14 Feb 2007 16:04:55 +0100 Subject: Generic object question In-Reply-To: <44C7E1BA-78A6-4CBF-88B8-5095F2E20D32@iam.unibe.ch> References: <44C7E1BA-78A6-4CBF-88B8-5095F2E20D32@iam.unibe.ch> Message-ID: > in one of my application I have an object that represent a > bibliographic entry. > I has a set of fields that really depends on the type of the entry. > An article will have different fields than a journal.... I see, meta described bib-entries ;-) > Now how could I use magritte to describe such object. > Should I have a dictionary that returns MAdefinition at the object > level (the table could be shared between all the instances of the > classes. Why not create subclasses for each type? Each of them would have its own set of descriptions, sharing the ones from the abstract superclass. Another possibility is to use the state pattern and to override #description on the instance side of your object and delegate it to your state objects. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Thu Feb 15 02:06:13 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Thu, 15 Feb 2007 01:06:13 +0000 Subject: Infinite recursion with Magritte In-Reply-To: <119F3642-4289-4F6E-A809-88C7210DFC5C@gmx.ch> References: <1171375525.31439.63.camel@localhost> <02384AEE-64E9-45CF-A43A-C14A3758642B@iam.unibe.ch> <66DA7E75-AEFA-42F4-A247-9D17C7FF758B@gmx.ch> <1171410171.24859.30.camel@localhost> <97AF24F1-F4EF-4F60-9F33-3E4B8A8BE004@gmx.ch> <5B4E97F0-FE08-4F78-80CB-A4D32C734A4D@iam.unibe.ch> <54CBF4AE-1288-4C82-979E-47BBA0B809DE@gmx.ch> <45D2F47E.7030401@yahoo.co.uk> <119F3642-4289-4F6E-A809-88C7210DFC5C@gmx.ch> Message-ID: <45D3B205.1080302@yahoo.co.uk> Adrian Kuhn wrote: > Wow, that's cool stuff, Keith! > Just read the comment of the Squeak version, where can I get the > mentioned VW version? ^^ > > -- Adrian > > The only reference that I could find is a copy of the original paper by Nevin Pratt, which contains code for VW. http://www.diit.unict.it/~acalva/SE/slides/se2/generalized-nullobject.rtf enjoy Keith ___________________________________________________________ The all-new Yahoo! Mail goes wherever you go - free your email address from your Internet provider. http://uk.docs.yahoo.com/nowyoucan.html From Florent.Trolat at etu.univ-savoie.fr Thu Feb 15 15:59:42 2007 From: Florent.Trolat at etu.univ-savoie.fr (florent trolat) Date: Thu, 15 Feb 2007 15:59:42 +0100 Subject: MADateDescription WAMiniCalandar Bug? In-Reply-To: <44C7E1BA-78A6-4CBF-88B8-5095F2E20D32@iam.unibe.ch> References: <44C7E1BA-78A6-4CBF-88B8-5095F2E20D32@iam.unibe.ch> Message-ID: <45D4755E.5000303@etu.univ-savoie.fr> Hi, I try to use MADateDescription but an error occurs in WAMiniCalandar. a fix: --------------------------------- original : 'From Squeak3.9gamma of ''23 July 2006'' [latest update: #7061] on 15 February 2007 at 3:52:53 pm'! !WAMiniCalendar methodsFor: 'rendering' stamp: 'ft 2/15/2007 15:51'! renderRowForWeek: aWeek on: html html tableRow: [ aWeek do: [:ea | self renderCellForDate: ea on: html]. ]! ! ---------------------------- fix : 'From Squeak3.9gamma of ''23 July 2006'' [latest update: #7061] on 15 February 2007 at 3:52:53 pm'! !WAMiniCalendar methodsFor: 'rendering' stamp: 'ft 2/15/2007 15:51'! renderRowForWeek: aWeek on: html html tableRow: [ aWeek every:(Duration days:1) do: [:ea | self renderCellForDate: ea on: html]. ]! ! ------------------------------- maybe I have something wrong with my image / Seaside config! Thanks. From brad at sonaural.com Fri Feb 16 00:57:51 2007 From: brad at sonaural.com (Brad Fuller) Date: Thu, 15 Feb 2007 15:57:51 -0800 Subject: Latest Seaside-Magma-Pier combo Message-ID: <45D4F37F.4030807@sonaural.com> Keith, is this still your latest: http://ftp.squeak.org/various_images/Seaside-Magma-Pier/ Dated in October 06 -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Fri Feb 16 14:42:43 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 16 Feb 2007 14:42:43 +0100 Subject: Magritte-All-lr.192.mcz initialization DNU In-Reply-To: <1829a2ba0702160525i3f0c4a9cs619ad14bedcc882f@mail.gmail.com> References: <1829a2ba0702160525i3f0c4a9cs619ad14bedcc882f@mail.gmail.com> Message-ID: <841B386A-27E6-4821-ADFC-7E6433B0850D@iam.unibe.ch> Hi Pavel, > there are some missing classes in the latest published version of > Magritte. MAUnlimited class >> initialize fails because classes > M2PositiveUnlimited and M2NegativeUnlimited don't exist. thanks for reporting, this issue should be fixed with the latest commit. These changes are not used yet, it is just a first step towards propre multiplicities. The latest commit also contains a change that avoids recursion when validating recursive graphs, however it is untested for now. > If you'll agree, I would like to prepare Magritte and Pier for > translation into other languages. That means mostly simple adding the > #translated messages to string literals but in some cases it will be > more complicated. I don't think that is a good idea for two reasons: 1. The #translated mechanism is specific to Squeak and wouldn't work with the ports to other dialects. 2. The #translated mechanism is global to an image. We have several web applications using Magritte where the language (german, french, italien, english) is defined per session and can be even switched on the fly. I don't see how that would work with #translated? Please correct me if I misunderstood your proposal. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Fri Feb 16 15:46:18 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 16 Feb 2007 15:46:18 +0100 Subject: Magritte-All-lr.192.mcz initialization DNU In-Reply-To: <1829a2ba0702160629n7cfca2bfu4a793f7bc390a6c@mail.gmail.com> References: <1829a2ba0702160525i3f0c4a9cs619ad14bedcc882f@mail.gmail.com> <841B386A-27E6-4821-ADFC-7E6433B0850D@iam.unibe.ch> <1829a2ba0702160629n7cfca2bfu4a793f7bc390a6c@mail.gmail.com> Message-ID: <20E6ABE0-9EF4-4D82-9F77-95A4DE6DCDC4@iam.unibe.ch> Hi Pavel, > Ok. There's the next very strange bug in Magritte. When you try to run > tests, one fails > (MAToManyScalarRelationDescription>>testCopyReference). String > descriptions have different uuids but only for first time. If I try to > evaluate this comparison again, it returns true (Sqeuak 3.9). yes I noticed as well. Maybe Philippe knows more about it, he implemented MAToManyScalarRelationDescription. >> > If you'll agree, I would like to prepare Magritte and Pier for >> > translation into other languages. That means mostly simple >> adding the >> > #translated messages to string literals but in some cases it >> will be >> > more complicated. >> >> I don't think that is a good idea for two reasons: >> >> 1. The #translated mechanism is specific to Squeak and wouldn't work >> with the ports to other dialects. >> >> 2. The #translated mechanism is global to an image. We have several >> web applications using Magritte where the language (german, french, >> italien, english) is defined per session and can be even switched on >> the fly. I don't see how that would work with #translated? >> >> Please correct me if I misunderstood your proposal. > > I used it in ShoreComponents and there were no problem with VW port > (even Michel didn't tell anything against it). On the other hand it > then uses only dummy implementation without translation. How do you scope the language? I don't see that in the implementation in Squeak of System-Localization. To make it even works I have to say that we have even Web application that can have different parts of the same session in different languages ;-) > Per session translation can be done similarly to WADynamicVariable > mechanism. How do you solve translations now? The sending of some > message to string literals is quite general solution. We may name it > for example magritteTranslated but that it will mean that this message > will be part of the Magritte package. At netstyle.ch we use a special object that represent a translated string. This object can be used anywhere as a replacement for a string, as it supports the same protocol. When a string is rendered (#renderOn:) it does the lookup and displays the right translation lazily. The language context is defined using a dynamic variable. > So I think that the standard > #translated message will be the best solution and the final > translation mechanism will be then dependent only on user's choice > (for example user-modified implementation of #translated message). > What do you think? I don't see, but if you change #translated to use a dynamic variable you break all the Squeak tools that use #translated. No? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Fri Feb 16 16:21:02 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 16 Feb 2007 16:21:02 +0100 Subject: Magritte-All-lr.192.mcz initialization DNU In-Reply-To: <66666f210702160719u53a3a3c7u2b3c5e9fcdc8e19d@mail.gmail.com> References: <1829a2ba0702160525i3f0c4a9cs619ad14bedcc882f@mail.gmail.com> <841B386A-27E6-4821-ADFC-7E6433B0850D@iam.unibe.ch> <1829a2ba0702160629n7cfca2bfu4a793f7bc390a6c@mail.gmail.com> <20E6ABE0-9EF4-4D82-9F77-95A4DE6DCDC4@iam.unibe.ch> <66666f210702160719u53a3a3c7u2b3c5e9fcdc8e19d@mail.gmail.com> Message-ID: <15B7EEB1-FCD1-407D-B8C5-2F39F35AF545@iam.unibe.ch> >> yes I noticed as well. Maybe Philippe knows more about it, he >> implemented MAToManyScalarRelationDescription. > > It used to work in: > Magritte-Model-lr.235 > Magritte-Tests-lr.102 > What changed in the mean time that could have caused it? I don't know, nothing really. Have a look it is really strange, it works in the debugger but not if the test is run in the test-runner. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Fri Feb 16 16:32:14 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 16 Feb 2007 16:32:14 +0100 Subject: Magritte-All-lr.192.mcz initialization DNU In-Reply-To: <1829a2ba0702160714n63f1b03fj71bb60d77a59739f@mail.gmail.com> References: <1829a2ba0702160525i3f0c4a9cs619ad14bedcc882f@mail.gmail.com> <841B386A-27E6-4821-ADFC-7E6433B0850D@iam.unibe.ch> <1829a2ba0702160629n7cfca2bfu4a793f7bc390a6c@mail.gmail.com> <20E6ABE0-9EF4-4D82-9F77-95A4DE6DCDC4@iam.unibe.ch> <1829a2ba0702160714n63f1b03fj71bb60d77a59739f@mail.gmail.com> Message-ID: <7C4B7B9E-7BDF-4C39-8E46-92B550FAA20E@iam.unibe.ch> >> How do you scope the language? I don't see that in the implementation >> in Squeak of System-Localization. To make it even works I have to say >> that we have even Web application that can have different parts of >> the same session in different languages ;-) > > In most cases I use only one language so standard Squeak translation > mechanism is OK ;-) But where I need many languages, I use special > "literal" where I define all translations together. It's better for > mainenance. Certainly, I completely agree. What I do not understand is the way how the #translated mechanisme works in Squeak. As far as I can see there is nothing like a dynamic scope but just a global variable, something that certainly does not work in the context of a Web application. >> > So I think that the standard >> > #translated message will be the best solution and the final >> > translation mechanism will be then dependent only on user's choice >> > (for example user-modified implementation of #translated message). >> > What do you think? >> >> I don't see, but if you change #translated to use a dynamic variable >> you break all the Squeak tools that use #translated. No? > > The exception based dynamic variable (for current language) returns > nil in case it is not defined in current stack. So then the default > implementation can be used. Yes, that's what we do in productive applications. In development mode the translated string object can display a red warning and potentially a link to an editor to translate the actual string ;-) > Now the only way how to create localized Magritte and Pier > applications is to modify their source code. We should solve it > somehow. Do you really think so? At least for Magritte there shouldn't be too much hardcoded strings anymore, as I use it in several productive multi-lingual applications. For Pier this is indeed a different story. Unfortunately all the labels and comments in the descriptions are hardcoded, due to the fact that I only used it in english contexts. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Fri Feb 16 17:18:10 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 08:18:10 -0800 Subject: Latest Seaside-Magma-Pier combo In-Reply-To: <45D4F37F.4030807@sonaural.com> References: <45D4F37F.4030807@sonaural.com> Message-ID: <45D5D942.6030808@sonaural.com> Just to let you all know, Keith replied to me that yes, the link from the squeak download page is the latest. However, there have been reports of it not working and both Pier and Magma have been updated since. A new version of the combo from Keith might be in a week or so. Brad Fuller wrote: > Keith, > > is this still your latest: > http://ftp.squeak.org/various_images/Seaside-Magma-Pier/ > > Dated in October 06 > > -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Fri Feb 16 17:54:33 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 08:54:33 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error Message-ID: <45D5E1C9.8090304@sonaural.com> how come when I try to load from http://mc.lukas-renggli.ch/pier for "blog" package I receive "This package depends on the following classes:" and there are many of them. Is there a better way to load Pier packages? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Fri Feb 16 18:03:38 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 09:03:38 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45D5E1C9.8090304@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> Message-ID: <45D5E3EA.8000402@sonaural.com> Brad Fuller wrote: > how come when I try to load from http://mc.lukas-renggli.ch/pier for > "blog" package I receive "This package depends on the following classes:" > > and there are many of them. Is there a better way to load Pier packages? > > Actually, let me ask a better question: what is the best/preferred way of creating a Seaside/Pier/Magma image and bringing it up to date? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Fri Feb 16 18:38:55 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 16 Feb 2007 18:38:55 +0100 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45D5E1C9.8090304@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> Message-ID: > how come when I try to load from http://mc.lukas-renggli.ch/pier for > "blog" package I receive "This package depends on the following > classes:" > > and there are many of them. Is there a better way to load Pier > packages? Load Pier from SqueakMap, then update Magritte and Pier using Monticello from http://mc.lukas-renggli.ch/magritte and http:// mc.lukas-renggli.ch/pier. The Blog package requires the package RsRss from the Seaside repository: http://www.squeaksource.com/Seaside Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Fri Feb 16 18:52:13 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Fri, 16 Feb 2007 17:52:13 +0000 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45D5E3EA.8000402@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D5E3EA.8000402@sonaural.com> Message-ID: <45D5EF4D.10207@yahoo.co.uk> Brad Fuller wrote: > Brad Fuller wrote: > >> how come when I try to load from http://mc.lukas-renggli.ch/pier for >> "blog" package I receive "This package depends on the following classes:" >> >> and there are many of them. Is there a better way to load Pier packages? >> >> >> > Actually, let me ask a better question: > > what is the best/preferred way of creating a Seaside/Pier/Magma image > and bringing it up to date The preferred way to generate my version of the SMP image at the moment is to edit the script on this wiki. Or more importantly fix the packages that this script loads. http://squeak310.pbwiki.com/Seaside-Magma-Pier Then, this image will be automatically generated whenever the http://squeak310.pbwiki.com/Make%20Seaside-Magma-Pier page is updated or the image upon which it depends is updated to be a new release candidate. This final step, the triggering of a build as a dependency is in the process of being debugged. The output will be available in http://squeak.warwick.st/auto-build/output/make/391/NEW_RC/ in folder SMP Nevertheless the script is there for you to see clearly the installing steps if not the configuring steps. I think that you can run it manually like so #squeak Squeak3.9-final-7067.image http://installer.pbwiki.com/f/IBS.st Installer path=http://squeak310.pbwiki.com/ install=From39To391 Installer install=Seaside-Magma-Pier MCWorkingCopy report=workingCopies to="*.txt" SmalltalkImage save=SMP.image +quit but some (hopefully very minor) fixes will be needed Keith ___________________________________________________________ Copy addresses and emails from any email account to Yahoo! Mail - quick, easy and free. http://uk.docs.yahoo.com/trueswitch2.html From brad at sonaural.com Fri Feb 16 19:29:42 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 10:29:42 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45D5EF4D.10207@yahoo.co.uk> References: <45D5E1C9.8090304@sonaural.com> <45D5E3EA.8000402@sonaural.com> <45D5EF4D.10207@yahoo.co.uk> Message-ID: <45D5F816.5070001@sonaural.com> Keith Hodges wrote: > Brad Fuller wrote: >> Brad Fuller wrote: >> >>> how come when I try to load from http://mc.lukas-renggli.ch/pier for >>> "blog" package I receive "This package depends on the following classes:" >>> >>> and there are many of them. Is there a better way to load Pier packages? >>> >>> >>> >> Actually, let me ask a better question: >> >> what is the best/preferred way of creating a Seaside/Pier/Magma image >> and bringing it up to date > The preferred way to generate my version of the SMP image at the moment > is to edit the script on this wiki. Or more importantly fix the packages > that this script loads. > > http://squeak310.pbwiki.com/Seaside-Magma-Pier > > Then, this image will be automatically generated whenever the > > http://squeak310.pbwiki.com/Make%20Seaside-Magma-Pier page is updated or > the image upon which it depends is updated to be a new release candidate. > > This final step, the triggering of a build as a dependency is in the > process of being debugged. > > The output will be available in > > http://squeak.warwick.st/auto-build/output/make/391/NEW_RC/ in folder SMP > > Nevertheless the script is there for you to see clearly the installing > steps if not the configuring steps. > > I think that you can run it manually like so > > #squeak Squeak3.9-final-7067.image http://installer.pbwiki.com/f/IBS.st > Installer path=http://squeak310.pbwiki.com/ install=From39To391 > Installer install=Seaside-Magma-Pier MCWorkingCopy report=workingCopies > to="*.txt" SmalltalkImage save=SMP.image +quit > > but some (hopefully very minor) fixes will be needed thanks Keith. I'll try it manually and see how it goes. From brad at sonaural.com Fri Feb 16 19:30:18 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 10:30:18 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: References: <45D5E1C9.8090304@sonaural.com> Message-ID: <45D5F83A.3090807@sonaural.com> Lukas Renggli wrote: >> how come when I try to load from http://mc.lukas-renggli.ch/pier for >> "blog" package I receive "This package depends on the following >> classes:" >> >> and there are many of them. Is there a better way to load Pier >> packages? > > Load Pier from SqueakMap, then update Magritte and Pier using > Monticello from http://mc.lukas-renggli.ch/magritte and http:// > mc.lukas-renggli.ch/pier. > > The Blog package requires the package RsRss from the Seaside > repository: http://www.squeaksource.com/Seaside ahh... thanks Lukas! -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Fri Feb 16 20:14:18 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 11:14:18 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: References: <45D5E1C9.8090304@sonaural.com> Message-ID: <45D6028A.50605@sonaural.com> Lukas Renggli wrote: >> how come when I try to load from http://mc.lukas-renggli.ch/pier for >> "blog" package I receive "This package depends on the following >> classes:" >> >> and there are many of them. Is there a better way to load Pier >> packages? > > Load Pier from SqueakMap, then update Magritte and Pier using > Monticello from http://mc.lukas-renggli.ch/magritte and http:// > mc.lukas-renggli.ch/pier. > > The Blog package requires the package RsRss from the Seaside > repository: http://www.squeaksource.com/Seaside Lucas, Syntax error when "loading" Pier-All-lr.163: Pier-Seaside-Widgets PRSearchWidget>>go self items in: [ :Name already used in this class ->items | items notEmpty ifTrue: [ self context: (self context structure: items first) ] ] > Cheers, > Lukas > -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Fri Feb 16 20:22:55 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 11:22:55 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45D6028A.50605@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> Message-ID: <45D6048F.4040102@sonaural.com> Brad Fuller wrote: > Lukas Renggli wrote: >>> how come when I try to load from http://mc.lukas-renggli.ch/pier for >>> "blog" package I receive "This package depends on the following >>> classes:" >>> >>> and there are many of them. Is there a better way to load Pier >>> packages? >> Load Pier from SqueakMap, then update Magritte and Pier using >> Monticello from http://mc.lukas-renggli.ch/magritte and http:// >> mc.lukas-renggli.ch/pier. >> >> The Blog package requires the package RsRss from the Seaside >> repository: http://www.squeaksource.com/Seaside > > Lucas, > > Syntax error when "loading" Pier-All-lr.163: > > Pier-Seaside-Widgets > > PRSearchWidget>>go > self items in: [ :Name already used in this class ->items | > items notEmpty ifTrue: [ > self context: (self context structure: items first) ] ] and why do I receive "Error: Could not find version 'Pier-Model-lr.105' when merging Pier-All-lr? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Fri Feb 16 20:56:48 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 16 Feb 2007 20:56:48 +0100 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45D6028A.50605@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> Message-ID: > PRSearchWidget>>go > self items in: [ :Name already used in this class ->items | > items notEmpty ifTrue: [ > self context: (self context structure: items first) ] ] Oh god, that is a long standing bug in Monticello that strikes again: there are some cases when the load order is wrong and causes a compile error. In this case it is the simples just to delete the method and load the package again. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Fri Feb 16 20:59:35 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 16 Feb 2007 20:59:35 +0100 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45D6048F.4040102@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> <45D6048F.4040102@sonaural.com> Message-ID: <84EB7E65-AA15-45D3-8AD2-97B0B965489A@iam.unibe.ch> > and why do I receive > "Error: Could not find version 'Pier-Model-lr.105' > when merging Pier-All-lr? Again probably a bug in Monticello, since I see this version in my repository. Add the repository http://mc.lukas-renggli.ch/pier to all the dependencies of Pier-All, e.g. Pier-Model, Pier-Seaside, ... so that Monticello can find the files to merge. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Fri Feb 16 21:10:01 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 12:10:01 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: References: <45D5E1C9.8090304@sonaural.com> Message-ID: <45D60F99.6060000@sonaural.com> Lukas Renggli wrote: >> how come when I try to load from http://mc.lukas-renggli.ch/pier for >> "blog" package I receive "This package depends on the following >> classes:" >> >> and there are many of them. Is there a better way to load Pier >> packages? > > Load Pier from SqueakMap, then update Magritte and Pier using > Monticello from http://mc.lukas-renggli.ch/magritte and http:// > mc.lukas-renggli.ch/pier. > > The Blog package requires the package RsRss from the Seaside > repository: http://www.squeaksource.com/Seaside Hmm... I don't see a package named RsRss in that repo. -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Fri Feb 16 21:13:25 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 12:13:25 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <84EB7E65-AA15-45D3-8AD2-97B0B965489A@iam.unibe.ch> References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> <45D6048F.4040102@sonaural.com> <84EB7E65-AA15-45D3-8AD2-97B0B965489A@iam.unibe.ch> Message-ID: <45D61065.6070702@sonaural.com> Lukas Renggli wrote: >> and why do I receive >> "Error: Could not find version 'Pier-Model-lr.105' >> when merging Pier-All-lr? > > Again probably a bug in Monticello, since I see this version in my > repository. Add the repository http://mc.lukas-renggli.ch/pier to all > the dependencies of Pier-All, e.g. Pier-Model, Pier-Seaside, ... so > that Monticello can find the files to merge. ok, thanks -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Fri Feb 16 21:30:06 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 12:30:06 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45D60F99.6060000@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D60F99.6060000@sonaural.com> Message-ID: <45D6144E.7090205@sonaural.com> Brad Fuller wrote: > Lukas Renggli wrote: >>> how come when I try to load from http://mc.lukas-renggli.ch/pier for >>> "blog" package I receive "This package depends on the following >>> classes:" >>> >>> and there are many of them. Is there a better way to load Pier >>> packages? >> Load Pier from SqueakMap, then update Magritte and Pier using >> Monticello from http://mc.lukas-renggli.ch/magritte and http:// >> mc.lukas-renggli.ch/pier. >> >> The Blog package requires the package RsRss from the Seaside >> repository: http://www.squeaksource.com/Seaside > > Hmm... I don't see a package named RsRss in that repo. > > just got it from http://www.squeaksource.com/rsrss -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Fri Feb 16 21:34:58 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 12:34:58 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: References: <45D5E1C9.8090304@sonaural.com> Message-ID: <45D61572.9070401@sonaural.com> Lukas Renggli wrote: >> how come when I try to load from http://mc.lukas-renggli.ch/pier for >> "blog" package I receive "This package depends on the following >> classes:" >> >> and there are many of them. Is there a better way to load Pier >> packages? > > Load Pier from SqueakMap, then update Magritte and Pier using > Monticello from http://mc.lukas-renggli.ch/magritte and http:// > mc.lukas-renggli.ch/pier. > > The Blog package requires the package RsRss from the Seaside > repository: http://www.squeaksource.com/Seaside Looks like there is just one more package to go Pier-Magma but I have this problem: This package depends on the following classes: PRPierControlPanel You must resolve these dependencies before you will be able to load these definitions: PRPierControlPanel>>deleteRepositoryKernel: PRPierControlPanel>>renderPRMagmaPersistency:kernel:on: I've loaded all the other pier packages. Do you know where this is? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Fri Feb 16 21:37:14 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 16 Feb 2007 21:37:14 +0100 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45D60F99.6060000@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D60F99.6060000@sonaural.com> Message-ID: <6D58E4C2-13F1-4F48-81AD-CAE178F0BE47@iam.unibe.ch> >> The Blog package requires the package RsRss from the Seaside >> repository: http://www.squeaksource.com/Seaside > > Hmm... I don't see a package named RsRss in that repo. Sorry, it has its own repository on SqueakSource: http://www.squeaksource.com/rsrss Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From private at hans-n-beck.de Fri Feb 16 22:46:39 2007 From: private at hans-n-beck.de (Hans N Beck) Date: Fri, 16 Feb 2007 22:46:39 +0100 Subject: VW Smallwiki problem Message-ID: Hi, my VW Smallwiki (not shure which version, the "stable" release from Bern Store) is running on a Win2k Server. I can connect under localhost:8080, but I can not acces from extern (over the internet). Server host and server baseBath are set to the www adress of my server. What is wondering me is that it works locally but not over internet. Before this, a Squeak Smalltwiki was running successfully with the same configuration. Is there any problem of the VW version ? Regards Hans From renggli at iam.unibe.ch Sat Feb 17 00:19:36 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 17 Feb 2007 00:19:36 +0100 Subject: VW Smallwiki problem In-Reply-To: References: Message-ID: <95B284D8-53C1-4D3A-B7E8-3B2559230A88@iam.unibe.ch> Hi Hans, > my VW Smallwiki (not shure which version, the "stable" release from > Bern Store) is running on a Win2k Server. I can connect under > localhost:8080, but I can not acces from extern (over the internet). > Server host and server baseBath are set to the www adress of my > server. > What is wondering me is that it works locally but not over internet. > Before this, a Squeak Smalltwiki was running successfully with the > same configuration. > > Is there any problem of the VW version ? not that I know of. In Bern we use the same version on VisualWorks 7.4 and it works well internally and externally. Did you check the Server Settings, maybe there is something wrong there? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From private at hans-n-beck.de Sat Feb 17 00:28:26 2007 From: private at hans-n-beck.de (Hans N Beck) Date: Sat, 17 Feb 2007 00:28:26 +0100 Subject: VW Smallwiki problem In-Reply-To: <95B284D8-53C1-4D3A-B7E8-3B2559230A88@iam.unibe.ch> References: <95B284D8-53C1-4D3A-B7E8-3B2559230A88@iam.unibe.ch> Message-ID: <7B2538E5-AD85-4A90-AF06-71AB803B4505@hans-n-beck.de> Hi, Am 17.02.2007 um 00:19 schrieb Lukas Renggli: > Hi Hans, > >> my VW Smallwiki (not shure which version, the "stable" release from >> Bern Store) is running on a Win2k Server. I can connect under >> localhost:8080, but I can not acces from extern (over the internet). >> Server host and server baseBath are set to the www adress of my >> server. >> What is wondering me is that it works locally but not over internet. >> Before this, a Squeak Smalltwiki was running successfully with the >> same configuration. >> >> Is there any problem of the VW version ? > > not that I know of. In Bern we use the same version on VisualWorks > 7.4 and it works well internally and externally. Did you check the > Server Settings, maybe there is something wrong there? Hmm, the question is, what could be wrong. host name and basePath of the server are set (but it seems it does'nt matter - the Squeak Smallwiki hat host = "'localhost' and host 'localhost:8080', and all worked fine). Are there any other critical settings (maybe some which are right by default on Squeak version) ? Greetings Hans > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at iam.unibe.ch Sat Feb 17 00:34:11 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 17 Feb 2007 00:34:11 +0100 Subject: VW Smallwiki problem In-Reply-To: <7B2538E5-AD85-4A90-AF06-71AB803B4505@hans-n-beck.de> References: <95B284D8-53C1-4D3A-B7E8-3B2559230A88@iam.unibe.ch> <7B2538E5-AD85-4A90-AF06-71AB803B4505@hans-n-beck.de> Message-ID: <6212F32D-1478-492B-A2C0-BF56DBCB7C10@iam.unibe.ch> >>> Is there any problem of the VW version ? >> >> not that I know of. In Bern we use the same version on VisualWorks >> 7.4 and it works well internally and externally. Did you check the >> Server Settings, maybe there is something wrong there? > > Hmm, the question is, what could be wrong. host name and basePath of > the server are set (but it seems it does'nt matter - the Squeak > Smallwiki hat host = "'localhost' and host 'localhost:8080', and all > worked fine). > Are there any other critical settings (maybe some which are right by > default on Squeak version) ? I vaguely remember that you had to tell Swazoo somehow to listen on all interfaces. Isn't in the workspace a setting to do exactly that? It should be somehow like Server listen: '*', but this is just a guess I don't have an image at hand. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Sat Feb 17 00:39:04 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Fri, 16 Feb 2007 23:39:04 +0000 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45D61572.9070401@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D61572.9070401@sonaural.com> Message-ID: <45D64098.90709@yahoo.co.uk> Brad Fuller wrote: > Lukas Renggli wrote: > >>> how come when I try to load from http://mc.lukas-renggli.ch/pier for >>> "blog" package I receive "This package depends on the following >>> classes:" >>> >>> and there are many of them. Is there a better way to load Pier >>> packages? >>> >> Load Pier from SqueakMap, then update Magritte and Pier using >> Monticello from http://mc.lukas-renggli.ch/magritte and http:// >> mc.lukas-renggli.ch/pier. >> >> The Blog package requires the package RsRss from the Seaside >> repository: http://www.squeaksource.com/Seaside >> > > Looks like there is just one more package to go > > Pier-Magma > > but I have this problem: > > This package depends on the following classes: > PRPierControlPanel > You must resolve these dependencies before you will be able to load > these definitions: > PRPierControlPanel>>deleteRepositoryKernel: > PRPierControlPanel>>renderPRMagmaPersistency:kernel:on: > > I've loaded all the other pier packages. Do you know where this is? > > It is in Seaside 2.6b branch and I merged it into Seaside 2.7 as well, however for some reason the main seaside practicioners have not got it in their latest. So if you look for my last contribution to Seaside 2.7a it will definitely be there. (kph) This is what I mean by 'small' things to sort out. Keith ___________________________________________________________ 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 brad at sonaural.com Sat Feb 17 08:58:49 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 16 Feb 2007 23:58:49 -0800 Subject: Pier Stylesheets Message-ID: <45D6B5B9.2050706@sonaural.com> Looking through the various Pier documentation, I see that code has changed and thus there are several different explanations of how to change stylesheets. I want to use a different css stylesheets but I can't find out where to change it/them. Isn't there one place to point Pier to one stylesheet? BTW: for some reason, I have no style sheet at all for Pier. I don't know what I did, but I didn't edit any code... I must have loaded a new version of some package. Anyway, unless it stomped on something else, if I can learn where to change the stylesheet pointer, It'd give me a start. thanks, brad -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From billksun at yahoo.com Sat Feb 17 09:20:26 2007 From: billksun at yahoo.com (Bill Sun) Date: Sat, 17 Feb 2007 00:20:26 -0800 (PST) Subject: Pier Stylesheets Message-ID: <508482.53708.qm@web53307.mail.yahoo.com> I think you need to go to the "configure" page for Pier (accessed from the bottom of the Pier pages), and add "PRPierLibrary" as a library, then select "PRPierLibrary" from the File Library pull down under the "Pier" configuration section. -Bill ----- Original Message ---- From: Brad Fuller To: "Magritte, Pier and Related Tools ..." Sent: Friday, February 16, 2007 11:58:49 PM Subject: Pier Stylesheets Looking through the various Pier documentation, I see that code has changed and thus there are several different explanations of how to change stylesheets. I want to use a different css stylesheets but I can't find out where to change it/them. Isn't there one place to point Pier to one stylesheet? BTW: for some reason, I have no style sheet at all for Pier. I don't know what I did, but I didn't edit any code... I must have loaded a new version of some package. Anyway, unless it stomped on something else, if I can learn where to change the stylesheet pointer, It'd give me a start. thanks, brad -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki ____________________________________________________________________________________ Don't get soaked. Take a quick peak at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070217/24facc32/attachment.html From private at hans-n-beck.de Sat Feb 17 09:38:42 2007 From: private at hans-n-beck.de (Hans N Beck) Date: Sat, 17 Feb 2007 09:38:42 +0100 Subject: VW Smallwiki problem In-Reply-To: <6212F32D-1478-492B-A2C0-BF56DBCB7C10@iam.unibe.ch> References: <95B284D8-53C1-4D3A-B7E8-3B2559230A88@iam.unibe.ch> <7B2538E5-AD85-4A90-AF06-71AB803B4505@hans-n-beck.de> <6212F32D-1478-492B-A2C0-BF56DBCB7C10@iam.unibe.ch> Message-ID: <02A93361-8C09-4FF5-9A78-69589CCC3583@hans-n-beck.de> Hi Lukas, Am 17.02.2007 um 00:34 schrieb Lukas Renggli: >>>> Is there any problem of the VW version ? >>> >>> not that I know of. In Bern we use the same version on VisualWorks >>> 7.4 and it works well internally and externally. Did you check the >>> Server Settings, maybe there is something wrong there? >> >> Hmm, the question is, what could be wrong. host name and basePath of >> the server are set (but it seems it does'nt matter - the Squeak >> Smallwiki hat host = "'localhost' and host 'localhost:8080', and all >> worked fine). >> Are there any other critical settings (maybe some which are right by >> default on Squeak version) ? > > I vaguely remember that you had to tell Swazoo somehow to listen on > all interfaces. Isn't in the workspace a setting to do exactly that? > It should be somehow like Server listen: '*', but this is just a > guess I don't have an image at hand. yes, this was the important hint: server ip: '*' does the trick (was given in the Workspace, but it was not hint that this is necessary) Thanks !! Greetings Hans > > Cheers, > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From norbert at hartl.name Sat Feb 17 13:16:55 2007 From: norbert at hartl.name (Norbert Hartl) Date: Sat, 17 Feb 2007 13:16:55 +0100 Subject: Pier Stylesheets In-Reply-To: <45D6B5B9.2050706@sonaural.com> References: <45D6B5B9.2050706@sonaural.com> Message-ID: <1171714615.25510.132.camel@localhost> On Fri, 2007-02-16 at 23:58 -0800, Brad Fuller wrote: > Looking through the various Pier documentation, I see that code has > changed and thus there are several different explanations of how to > change stylesheets. I want to use a different css stylesheets but I > can't find out where to change it/them. Isn't there one place to point > Pier to one stylesheet? > > BTW: for some reason, I have no style sheet at all for Pier. I don't > know what I did, but I didn't edit any code... I must have loaded a new > version of some package. Anyway, unless it stomped on something else, if > I can learn where to change the stylesheet pointer, It'd give me a start. > It is in PRPierLibrary>>style and it is pointing to lukas style sheet on www.lukas-renggli.ch. Norbert From brad at sonaural.com Sat Feb 17 17:42:58 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 17 Feb 2007 08:42:58 -0800 Subject: Pier Stylesheets In-Reply-To: <508482.53708.qm@web53307.mail.yahoo.com> References: <508482.53708.qm@web53307.mail.yahoo.com> Message-ID: <45D73092.5090606@sonaural.com> Bill Sun wrote: > I think you need to go to the "configure" page for Pier (accessed from > the bottom of the Pier pages), and add "PRPierLibrary" as a library, > then select "PRPierLibrary" from the File Library pull down under the > "Pier" configuration section. I don't know how to add a library, but PRPierLibrary is already the library at : File Library: > > -Bill > > ----- Original Message ---- > From: Brad Fuller > To: "Magritte, Pier and Related Tools ..." > Sent: Friday, February 16, 2007 11:58:49 PM > Subject: Pier Stylesheets > > Looking through the various Pier documentation, I see that code has > changed and thus there are several different explanations of how to > change stylesheets. I want to use a different css stylesheets but I > can't find out where to change it/them. Isn't there one place to point > Pier to one stylesheet? > > BTW: for some reason, I have no style sheet at all for Pier. I don't > know what I did, but I didn't edit any code... I must have loaded a new > version of some package. Anyway, unless it stomped on something else, if > I can learn where to change the stylesheet pointer, It'd give me a start. > > thanks, > brad > > -- > brad fuller > http://www.Sonaural.com/ > +1 (408) 799-6124 > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > ------------------------------------------------------------------------ > Everyone is raving about the all-new Yahoo! Mail beta. > > > > ------------------------------------------------------------------------ > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Sat Feb 17 17:48:41 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 17 Feb 2007 08:48:41 -0800 Subject: Pier Stylesheets In-Reply-To: <1171714615.25510.132.camel@localhost> References: <45D6B5B9.2050706@sonaural.com> <1171714615.25510.132.camel@localhost> Message-ID: <45D731E9.4080801@sonaural.com> Norbert Hartl wrote: > On Fri, 2007-02-16 at 23:58 -0800, Brad Fuller wrote: >> Looking through the various Pier documentation, I see that code has >> changed and thus there are several different explanations of how to >> change stylesheets. I want to use a different css stylesheets but I >> can't find out where to change it/them. Isn't there one place to point >> Pier to one stylesheet? >> >> BTW: for some reason, I have no style sheet at all for Pier. I don't >> know what I did, but I didn't edit any code... I must have loaded a new >> version of some package. Anyway, unless it stomped on something else, if >> I can learn where to change the stylesheet pointer, It'd give me a start. >> > It is in PRPierLibrary>>style and it is pointing to lukas style sheet > on www.lukas-renggli.ch. I've seen that in docs/msgs, but I actually don't have PRPierLibrary>>style, it's styleCss. And it not a file pointer but appears to be the content of a css file - with a comment about cc Lukas and import statements like his file: @import url(basic.css) etc.. maybe I need to upgrade? I have Pier-Model-lr.105, Pier-Seaside-lr.108, etc... From brad at sonaural.com Sat Feb 17 21:24:14 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 17 Feb 2007 12:24:14 -0800 Subject: Pier Stylesheets In-Reply-To: <45D731E9.4080801@sonaural.com> References: <45D6B5B9.2050706@sonaural.com> <1171714615.25510.132.camel@localhost> <45D731E9.4080801@sonaural.com> Message-ID: <45D7646E.80404@sonaural.com> Brad Fuller wrote: > Norbert Hartl wrote: >> On Fri, 2007-02-16 at 23:58 -0800, Brad Fuller wrote: >>> Looking through the various Pier documentation, I see that code has >>> changed and thus there are several different explanations of how to >>> change stylesheets. I want to use a different css stylesheets but I >>> can't find out where to change it/them. Isn't there one place to point >>> Pier to one stylesheet? >>> >>> BTW: for some reason, I have no style sheet at all for Pier. I don't >>> know what I did, but I didn't edit any code... I must have loaded a new >>> version of some package. Anyway, unless it stomped on something else, if >>> I can learn where to change the stylesheet pointer, It'd give me a start. >>> >> It is in PRPierLibrary>>style and it is pointing to lukas style sheet >> on www.lukas-renggli.ch. > > I've seen that in docs/msgs, but I actually don't have > PRPierLibrary>>style, it's styleCss. And it not a file pointer but > appears to be the content of a css file - with a comment about cc Lukas > and import statements like his file: > > @import url(basic.css) > etc.. > > maybe I need to upgrade? I have Pier-Model-lr.105, Pier-Seaside-lr.108, > etc... I did upgrade, and it's still the same. So, changed styleCss to: ^ '@import "file://styles/style.css";'. as the styles directory is a subdir of where the image is located. But, no go. (wow, seaside configuration page is a lot different. The dispacher browser selection goes no where - should it?) > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Sun Feb 18 00:07:08 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 17 Feb 2007 15:07:08 -0800 Subject: Pier Stylesheets - Help! In-Reply-To: <45D7646E.80404@sonaural.com> References: <45D6B5B9.2050706@sonaural.com> <1171714615.25510.132.camel@localhost> <45D731E9.4080801@sonaural.com> <45D7646E.80404@sonaural.com> Message-ID: <45D78A9C.2070609@sonaural.com> Brad Fuller wrote: > Brad Fuller wrote: >> Norbert Hartl wrote: >>> On Fri, 2007-02-16 at 23:58 -0800, Brad Fuller wrote: >>>> Looking through the various Pier documentation, I see that code has >>>> changed and thus there are several different explanations of how to >>>> change stylesheets. I want to use a different css stylesheets but I >>>> can't find out where to change it/them. Isn't there one place to point >>>> Pier to one stylesheet? >>>> >>>> BTW: for some reason, I have no style sheet at all for Pier. I don't >>>> know what I did, but I didn't edit any code... I must have loaded a new >>>> version of some package. Anyway, unless it stomped on something else, if >>>> I can learn where to change the stylesheet pointer, It'd give me a start. >>>> >>> It is in PRPierLibrary>>style and it is pointing to lukas style sheet >>> on www.lukas-renggli.ch. >> I've seen that in docs/msgs, but I actually don't have >> PRPierLibrary>>style, it's styleCss. And it not a file pointer but >> appears to be the content of a css file - with a comment about cc Lukas >> and import statements like his file: >> >> @import url(basic.css) >> etc.. >> >> maybe I need to upgrade? I have Pier-Model-lr.105, Pier-Seaside-lr.108, >> etc... > > I did upgrade, and it's still the same. > > So, changed styleCss to: > > ^ '@import "file://styles/style.css";'. > > as the styles directory is a subdir of where the image is located. But, > no go. How come nobody has PRPierLibrary>>styleCss method? This class seems to have all of the default css styles of Pier. Why I get absolutely no stylesheet at all, I don't know. In any case, I've added the style sheet by hand from the "Toggle Halos" in Pier. This works fine, except it doesn't seem to find the png files. I've seen from searching msgs and found that "/seaside" is thought to be the root for pier. So, I changed them to point to the direct path. As example: background: url(/seaside/styles/box-contents.png) but this does not work. I have also tried: background: url(styles/box-contents.png) Any hints you can give me for more searching? This might be a clue: Going to /seaside/config brought up a css with the beautiful seaside logo, etc. Now there is NO css associated, just this: Seaside Seaside2.7a1-lr.185.mcz 16 February 2007 3:36:17 pm /seaside browse Dispatcher Browser examples Directory mmiki Pier tools Directory From renggli at iam.unibe.ch Sun Feb 18 00:17:11 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 18 Feb 2007 00:17:11 +0100 Subject: Pier Stylesheets - Help! In-Reply-To: <45D78A9C.2070609@sonaural.com> References: <45D6B5B9.2050706@sonaural.com> <1171714615.25510.132.camel@localhost> <45D731E9.4080801@sonaural.com> <45D7646E.80404@sonaural.com> <45D78A9C.2070609@sonaural.com> Message-ID: <20FB48BD-A542-4AAC-9D32-B87011EE1D2B@iam.unibe.ch> Hi Brad, > How come nobody has PRPierLibrary>>styleCss method? > This class seems to have all of the default css styles of Pier. Why I > get absolutely no stylesheet at all, I don't know. sorry, I am on a trip and I couldn't replay earlier. I don't exactly understand why the thing with the style are not working. There are I few things that might be the problem: 1. The 2.7 branch of Seaside made some big changes in that area (and there are a few more to expect), they do work fine in my image but they are mostly untested. 2. Pier and Magritte require the latest version of Seaside (I think you use those). Maybe you want to use the version of Pier from SqueakMap, as it builds you an image with the right version of Seaside, Magritte and Pier that is knows to work well together. It is not bleeding edge, but it is fresh and should be fairly easy to update later on. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Sun Feb 18 00:34:32 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 17 Feb 2007 15:34:32 -0800 Subject: Pier Stylesheets - Help! In-Reply-To: <20FB48BD-A542-4AAC-9D32-B87011EE1D2B@iam.unibe.ch> References: <45D6B5B9.2050706@sonaural.com> <1171714615.25510.132.camel@localhost> <45D731E9.4080801@sonaural.com> <45D7646E.80404@sonaural.com> <45D78A9C.2070609@sonaural.com> <20FB48BD-A542-4AAC-9D32-B87011EE1D2B@iam.unibe.ch> Message-ID: <45D79108.4030507@sonaural.com> Lukas Renggli wrote: > Hi Brad, > >> How come nobody has PRPierLibrary>>styleCss method? >> This class seems to have all of the default css styles of Pier. Why I >> get absolutely no stylesheet at all, I don't know. > > sorry, I am on a trip and I couldn't replay earlier. I don't exactly > understand why the thing with the style are not working. > > There are I few things that might be the problem: > > 1. The 2.7 branch of Seaside made some big changes in that area (and > there are a few more to expect), they do work fine in my image but > they are mostly untested. > > 2. Pier and Magritte require the latest version of Seaside (I think > you use those). > > Maybe you want to use the version of Pier from SqueakMap, as it > builds you an image with the right version of Seaside, Magritte and > Pier that is knows to work well together. It is not bleeding edge, > but it is fresh and should be fairly easy to update later on. Hey, thanks for the reply, Lukas. Well. that's where I started ;-) Even at that point, if I remember correctly, I had "styleCss" method and not "style" method that pointed to an actual file (your file, I believe on the Internet.) I really wanted the newest blog plugin and a better way to handle images - which I thought FileLibrary was to do. It would be good if there was a proper way to update. I certainly don't know if that's the problem. That's what Keith seems to be headed for. Well.. I'm almost there... so maybe I can druge along with the member's help and see if I can get this puppy running like it should be! I think I need to find out how FileLibrary works. Or at least, find out how I can serve png files for the css. -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Sun Feb 18 00:57:38 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 17 Feb 2007 15:57:38 -0800 Subject: Pier Stylesheets - Help! In-Reply-To: <20FB48BD-A542-4AAC-9D32-B87011EE1D2B@iam.unibe.ch> References: <45D6B5B9.2050706@sonaural.com> <1171714615.25510.132.camel@localhost> <45D731E9.4080801@sonaural.com> <45D7646E.80404@sonaural.com> <45D78A9C.2070609@sonaural.com> <20FB48BD-A542-4AAC-9D32-B87011EE1D2B@iam.unibe.ch> Message-ID: <45D79672.5090502@sonaural.com> Lukas Renggli wrote: > Hi Brad, > > 1. The 2.7 branch of Seaside made some big changes in that area (and > there are a few more to expect), they do work fine in my image but > they are mostly untested. Ok, let me ask you how you change css? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From keith_hodges at yahoo.co.uk Sun Feb 18 01:52:16 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Sun, 18 Feb 2007 00:52:16 +0000 Subject: Pier Stylesheets - Help! In-Reply-To: <45D79672.5090502@sonaural.com> References: <45D6B5B9.2050706@sonaural.com> <1171714615.25510.132.camel@localhost> <45D731E9.4080801@sonaural.com> <45D7646E.80404@sonaural.com> <45D78A9C.2070609@sonaural.com> <20FB48BD-A542-4AAC-9D32-B87011EE1D2B@iam.unibe.ch> <45D79672.5090502@sonaural.com> Message-ID: <45D7A340.4000906@yahoo.co.uk> Brad Fuller wrote: > Lukas Renggli wrote: > >> Hi Brad, >> >> 1. The 2.7 branch of Seaside made some big changes in that area (and >> there are a few more to expect), they do work fine in my image but >> they are mostly untested. >> > > Ok, let me ask you how you change css? > > > I have an implementation which uses pier itself to edit the style sheet, since a hierarchical collection of pier pages can be rendered into one css file. Pictures are uploaded to pier, and rendered into the css as a url. Any portion of the stylesheet can be pulled out into a page in the tree, for example each reference to a color can be a reference to one page, edit that page and the color changes everywhere that it is referenced. If you would like to take a look at it, though I think it probably needs some work once more, I put the image containing the latest code in http://squeak.warwick.st/pier An earlier version is actually running at www.warwick.st , and you are welcome to have a play with that, but when I last looked there seemed to be a gateway error. best regards Keith ___________________________________________________________ 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 brad at sonaural.com Sun Feb 18 02:12:06 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 17 Feb 2007 17:12:06 -0800 Subject: Pier Stylesheets - Help! In-Reply-To: <45D7A340.4000906@yahoo.co.uk> References: <45D6B5B9.2050706@sonaural.com> <1171714615.25510.132.camel@localhost> <45D731E9.4080801@sonaural.com> <45D7646E.80404@sonaural.com> <45D78A9C.2070609@sonaural.com> <20FB48BD-A542-4AAC-9D32-B87011EE1D2B@iam.unibe.ch> <45D79672.5090502@sonaural.com> <45D7A340.4000906@yahoo.co.uk> Message-ID: <45D7A7E6.7010704@sonaural.com> Keith Hodges wrote: > Brad Fuller wrote: >> Lukas Renggli wrote: >> >>> Hi Brad, >>> >>> 1. The 2.7 branch of Seaside made some big changes in that area (and >>> there are a few more to expect), they do work fine in my image but >>> they are mostly untested. >>> >> Ok, let me ask you how you change css? >> >> >> > I have an implementation which uses pier itself to edit the style sheet, > since a hierarchical collection of pier pages can be rendered into one > css file. Pictures are uploaded to pier, and rendered into the css as a > url. Any portion of the stylesheet can be pulled out into a page in the > tree, for example each reference to a color can be a reference to one > page, edit that page and the color changes everywhere that it is referenced. That would be a bit more convenient than using the Toggle Halos and editing the CSS there. However, I can see the advantage of having it available for css editors that are remote. All they have to do is go to the area in question and edit the css. However, I don't like having the links available on the bottom - users could click and mess things up. > If you would like to take a look at it, though I think it probably needs > some work once more, I put the image containing the latest code in > http://squeak.warwick.st/pier I'm still trying to construct a good seaside-pier-magma image. It's tough! It shouldn't be this tough, should it? > An earlier version is actually running at www.warwick.st , and you are > welcome to have a play with that, but when I last looked there seemed to > be a gateway error. yeah... still there. Thanks From billksun at yahoo.com Sun Feb 18 02:18:25 2007 From: billksun at yahoo.com (Bill Sun) Date: Sat, 17 Feb 2007 17:18:25 -0800 (PST) Subject: Pier Stylesheets - Help! Message-ID: <20070218011825.87733.qmail@web53314.mail.yahoo.com> Brad, Are you even getting the default Pier styles? If not, follow my instructions in my previous email in regards to this matter. That should at least get you the default Pier look and feel. As to using Seaside's FileLibrary for your own style sheets, I haven't figure that one out either. However, I just did a search on the web and came up with this (I haven't tried the instructions in the link, yet, so no guarantees): http://lists.squeakfoundation.org/pipermail/seaside/2006-May/007777.html -Bill ----- Original Message ---- From: Brad Fuller To: "Magritte, Pier and Related Tools ..." Sent: Saturday, February 17, 2007 3:34:32 PM Subject: Re: Pier Stylesheets - Help! Lukas Renggli wrote: > Hi Brad, > >> How come nobody has PRPierLibrary>>styleCss method? >> This class seems to have all of the default css styles of Pier. Why I >> get absolutely no stylesheet at all, I don't know. > > sorry, I am on a trip and I couldn't replay earlier. I don't exactly > understand why the thing with the style are not working. > > There are I few things that might be the problem: > > 1. The 2.7 branch of Seaside made some big changes in that area (and > there are a few more to expect), they do work fine in my image but > they are mostly untested. > > 2. Pier and Magritte require the latest version of Seaside (I think > you use those). > > Maybe you want to use the version of Pier from SqueakMap, as it > builds you an image with the right version of Seaside, Magritte and > Pier that is knows to work well together. It is not bleeding edge, > but it is fresh and should be fairly easy to update later on. Hey, thanks for the reply, Lukas. Well. that's where I started ;-) Even at that point, if I remember correctly, I had "styleCss" method and not "style" method that pointed to an actual file (your file, I believe on the Internet.) I really wanted the newest blog plugin and a better way to handle images - which I thought FileLibrary was to do. It would be good if there was a proper way to update. I certainly don't know if that's the problem. That's what Keith seems to be headed for. Well.. I'm almost there... so maybe I can druge along with the member's help and see if I can get this puppy running like it should be! I think I need to find out how FileLibrary works. Or at least, find out how I can serve png files for the css. -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 _______________________________________________ SmallWiki, Magritte, Pier and Related Tools ... https://www.iam.unibe.ch/mailman/listinfo/smallwiki ____________________________________________________________________________________ Get your own web address. Have a HUGE year through Yahoo! Small Business. http://smallbusiness.yahoo.com/domains/?p=BESTDEAL -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20070218/4f784d2a/attachment.html From brad at sonaural.com Sun Feb 18 02:44:52 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 17 Feb 2007 17:44:52 -0800 Subject: Pier Stylesheets - Help! In-Reply-To: <20070218011825.87733.qmail@web53314.mail.yahoo.com> References: <20070218011825.87733.qmail@web53314.mail.yahoo.com> Message-ID: <45D7AF94.8050700@sonaural.com> Bill Sun wrote: > Brad, > > Are you even getting the default Pier styles? If not, follow my > instructions in my previous email in regards to this matter. That > should at least get you the default Pier look and feel. Hey Bill.. thanks for the msg. I did follow your instructions... it was actually already configured. But it made no difference. I think I have a screwed up installation. I'm starting from scratch and do as Lukas suggested and just use the SqueakMap packages. After I get a reasonable app up, I'll move to Seaside 2.7 and see how that goes. > > As to using Seaside's FileLibrary for your own style sheets, I haven't > figure that one out either. However, I just did a search on the web and > came up with this (I haven't tried the instructions in the link, yet, so > no guarantees): > http://lists.squeakfoundation.org/pipermail/seaside/2006-May/007777.html Yeah, I saw that. One of my problems with this was that my seaside/config went away. It was there for a while and now it doesn't go anywhere. Hence, why I think I have a screwed up installation. Thanks much for this and if you figure out FileLibrary let us all know! brad > > -Bill > > ----- Original Message ---- > From: Brad Fuller > To: "Magritte, Pier and Related Tools ..." > Sent: Saturday, February 17, 2007 3:34:32 PM > Subject: Re: Pier Stylesheets - Help! > > Lukas Renggli wrote: > > Hi Brad, > > > >> How come nobody has PRPierLibrary>>styleCss method? > >> This class seems to have all of the default css styles of Pier. Why I > >> get absolutely no stylesheet at all, I don't know. > > > > sorry, I am on a trip and I couldn't replay earlier. I don't exactly > > understand why the thing with the style are not working. > > > > There are I few things that might be the problem: > > > > 1. The 2.7 branch of Seaside made some big changes in that area (and > > there are a few more to expect), they do work fine in my image but > > they are mostly untested. > > > > 2. Pier and Magritte require the latest version of Seaside (I think > > you use those). > > > > Maybe you want to use the version of Pier from SqueakMap, as it > > builds you an image with the right version of Seaside, Magritte and > > Pier that is knows to work well together. It is not bleeding edge, > > but it is fresh and should be fairly easy to update later on. > > Hey, thanks for the reply, Lukas. > > Well. that's where I started ;-) Even at that point, if I remember > correctly, I had "styleCss" method and not "style" method that pointed > to an actual file (your file, I believe on the Internet.) > > I really wanted the newest blog plugin and a better way to handle images > - which I thought FileLibrary was to do. > > It would be good if there was a proper way to update. I certainly don't > know if that's the problem. That's what Keith seems to be headed for. > > Well.. I'm almost there... so maybe I can druge along with the member's > help and see if I can get this puppy running like it should be! > > I think I need to find out how FileLibrary works. Or at least, find out > how I can serve png files for the css. > > -- > brad fuller > http://www.Sonaural.com/ > +1 (408) 799-6124 > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > ------------------------------------------------------------------------ > Be a PS3 game guru. > Get your game face on with the latest PS3 news and previews at Yahoo! > Games. > > > ------------------------------------------------------------------------ > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From keith_hodges at yahoo.co.uk Sun Feb 18 03:36:07 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Sun, 18 Feb 2007 02:36:07 +0000 Subject: Pier Stylesheets - Help! In-Reply-To: <45D7A7E6.7010704@sonaural.com> References: <45D6B5B9.2050706@sonaural.com> <1171714615.25510.132.camel@localhost> <45D731E9.4080801@sonaural.com> <45D7646E.80404@sonaural.com> <45D78A9C.2070609@sonaural.com> <20FB48BD-A542-4AAC-9D32-B87011EE1D2B@iam.unibe.ch> <45D79672.5090502@sonaural.com> <45D7A340.4000906@yahoo.co.uk> <45D7A7E6.7010704@sonaural.com> Message-ID: <45D7BB97.8030304@yahoo.co.uk> I am not sure what is going on at seaside hosting, but I had a look at another site on there and guess what, it has no style! So it looks like the default pier configuration may be unable to get to the style sheet served by lukas' machine at the moment. This might explain your problem. > > I'm still trying to construct a good seaside-pier-magma image. It's > tough! It shouldn't be this tough, should it? > No it shouldn't, but I recall my initial time with Pier; it took me at least two weeks to get the hang of the packages so that they installed correctly. I had never used MC before, so it took me a while to get used to its quirks. At the moment with pier-magma integration we are in a period of limbo, where things are not actually expected to work out of the box. You see I made some changes to both pier and magma in making the seaside-pier-magma image work. I was waiting for Lukas and Chris to update the mainstream of pier and magma to incorporate my changes. They have both done this now, so it remains for me to review their changes (not all were accepted) and update the pier-magma package. Now that the necessary infrastructure changes (apart from one; I suspect PRKernel realizeKernel may still have to be added) are in both pier and magma, the process should be much smoother. In theory, pier-magma will not have to touch pier or magma to work. The plan is to pull my contribution to Pier-Seaside, including the item that uses the elusive WADispatcherEditorPlugin into a separate package for "persistency management". This is the code and UI that enables switching between persistency schemes on the fly. With this in mind, I will point out that Magma supports pier in an entirely transparent manner. Pier really does nothing special to support Magma. Therefore I can encourage you to get going with Pier, safe in the knowledge that enabling magma persistency requires nothing more than a drop down menu selection. best regards Keith ___________________________________________________________ Now you can scan emails quickly with a reading pane. Get the new Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html From brad at sonaural.com Sun Feb 18 03:42:33 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 17 Feb 2007 18:42:33 -0800 Subject: Pier Stylesheets - Help! In-Reply-To: <45D7BB97.8030304@yahoo.co.uk> References: <45D6B5B9.2050706@sonaural.com> <1171714615.25510.132.camel@localhost> <45D731E9.4080801@sonaural.com> <45D7646E.80404@sonaural.com> <45D78A9C.2070609@sonaural.com> <20FB48BD-A542-4AAC-9D32-B87011EE1D2B@iam.unibe.ch> <45D79672.5090502@sonaural.com> <45D7A340.4000906@yahoo.co.uk> <45D7A7E6.7010704@sonaural.com> <45D7BB97.8030304@yahoo.co.uk> Message-ID: <45D7BD19.7080509@sonaural.com> Keith Hodges wrote: > I am not sure what is going on at seaside hosting, but I had a look at > another site on there and guess what, it has no style! > > So it looks like the default pier configuration may be unable to get to > the style sheet served by lukas' machine at the moment. This might > explain your problem. >> I'm still trying to construct a good seaside-pier-magma image. It's >> tough! It shouldn't be this tough, should it? >> > No it shouldn't, but I recall my initial time with Pier; it took me at > least two weeks to get the hang of the packages so that they installed > correctly. I had never used MC before, so it took me a while to get used > to its quirks. > > At the moment with pier-magma integration we are in a period of limbo, > where things are not actually expected to work out of the box. You see I > made some changes to both pier and magma in making the > seaside-pier-magma image work. I was waiting for Lukas and Chris to > update the mainstream of pier and magma to incorporate my changes. They > have both done this now, so it remains for me to review their changes > (not all were accepted) and update the pier-magma package. > > Now that the necessary infrastructure changes (apart from one; I suspect > PRKernel realizeKernel may still have to be added) are in both pier and > magma, the process should be much smoother. In theory, pier-magma will > not have to touch pier or magma to work. > > The plan is to pull my contribution to Pier-Seaside, including the item > that uses the elusive WADispatcherEditorPlugin into a separate package > for "persistency management". This is the code and UI that enables > switching between persistency schemes on the fly. > > With this in mind, I will point out that Magma supports pier in an > entirely transparent manner. Pier really does nothing special to support > Magma. Therefore I can encourage you to get going with Pier, safe in the > knowledge that enabling magma persistency requires nothing more than a > drop down menu selection. Now, THAT I Like! Thanks for the update and explanation. I've got the "basic" SqueakMap" Pier running so I'm going to start with that. I sure would like to get the new packages merged because from what I've seen, there are some handy features that will make my life easier. thanks again, brad -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From azreal1977 at hotmail.com Sun Feb 18 10:07:03 2007 From: azreal1977 at hotmail.com (J J) Date: Sun, 18 Feb 2007 09:07:03 +0000 Subject: Pier Magritte question In-Reply-To: <45D7BB97.8030304@yahoo.co.uk> Message-ID: Hi, Related to my previous email, I was wondering what happens if I have a seaside component that uses Magritte to display itself (Ramon does this a lot on his blog), and I try to use it in Pier. Will the Pier settings button show the same thing that the main render does? Or does Pier somehow know which are Pier components and which are seaside components? Thanks, Jason _________________________________________________________________ Don’t miss your chance to WIN 10 hours of private jet travel from Microsoft® Office Live http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/ From azreal1977 at hotmail.com Sun Feb 18 10:04:02 2007 From: azreal1977 at hotmail.com (J J) Date: Sun, 18 Feb 2007 09:04:02 +0000 Subject: Pier enhancement idea In-Reply-To: <45D7BB97.8030304@yahoo.co.uk> Message-ID: Joomla has a feature that lets you see and install Joomla components right from the web page. How would it sound to have something like this for Pier? Instead of having to open up the image, download a MC and/or Squeak map thing, you can just go to the "Add" button, and one extra option there would be to add a new component. We could have some special button added on Squeak source to say if a package is a Pier or Seaside component. So what do people think of this idea? Thanks, Jason _________________________________________________________________ Refi Now: Rates near 39yr lows! $430,000 Mortgage for $1,399/mo - Calculate new payment http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-17727&moid=7581 From philippe.marschall at gmail.com Sun Feb 18 10:44:30 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Sun, 18 Feb 2007 10:44:30 +0100 Subject: Pier Stylesheets In-Reply-To: <45D6B5B9.2050706@sonaural.com> References: <45D6B5B9.2050706@sonaural.com> Message-ID: <66666f210702180144k2d61a31fpc7fa7538611d3128@mail.gmail.com> 2007/2/17, Brad Fuller : > Looking through the various Pier documentation, I see that code has > changed and thus there are several different explanations of how to > change stylesheets. I want to use a different css stylesheets but I > can't find out where to change it/them. Isn't there one place to point > Pier to one stylesheet? > > BTW: for some reason, I have no style sheet at all for Pier. I don't > know what I did, but I didn't edit any code... I must have loaded a new > version of some package. Anyway, unless it stomped on something else, if > I can learn where to change the stylesheet pointer, It'd give me a start. Thanks to Christoph Wysseier Pier now supports easy custom styles with FileLibraries. All you need to do is provide your own FileLibrary that implements #styleCss which returns a string that is the main CSS file. You can put all your CSS there, or in other selectors (as PierLibrary does) or in other locations by importing the CSS files you need. For example if #styleCss makes @import url(basic.css); this means #basicCss is imported. Basic FileLibrary stuff. FileLibrary one of the classes that actually have a comment that describes what it does. In the configuration of your pier application under 'Pier' you can select it in 'File Library'. Cheers Philippe > thanks, > brad > > -- > brad fuller > http://www.Sonaural.com/ > +1 (408) 799-6124 > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From philippe.marschall at gmail.com Sun Feb 18 10:51:30 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Sun, 18 Feb 2007 10:51:30 +0100 Subject: Pier enhancement idea In-Reply-To: References: <45D7BB97.8030304@yahoo.co.uk> Message-ID: <66666f210702180151w2399d0cfr8bc54a4883f33e1f@mail.gmail.com> 2007/2/18, J J : > Joomla has a feature that lets you see and install Joomla components right > from the web page. > > How would it sound to have something like this for Pier? Instead of having > to open up the image, download a MC and/or Squeak map thing, you can just go > to the "Add" button, and one extra option there would be to add a new > component. We could have some special button added on Squeak source to say > if a package is a Pier or Seaside component. > > So what do people think of this idea? If Squeak supports sending an url (or loading code) from a webpage to the currently open image .... Philippe > Thanks, > Jason > > _________________________________________________________________ > Refi Now: Rates near 39yr lows! $430,000 Mortgage for $1,399/mo - Calculate > new payment > http://www.lowermybills.com/lre/index.jsp?sourceid=lmb-9632-17727&moid=7581 > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From philippe.marschall at gmail.com Sun Feb 18 10:55:33 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Sun, 18 Feb 2007 10:55:33 +0100 Subject: Pier Magritte question In-Reply-To: References: <45D7BB97.8030304@yahoo.co.uk> Message-ID: <66666f210702180155t5c2510f9n85496de78dc6aaa9@mail.gmail.com> 2007/2/18, J J : > Hi, > > Related to my previous email, I was wondering what happens if I have a > seaside component that uses Magritte to display itself (Ramon does this a > lot on his blog), and I try to use it in Pier. Will the Pier settings > button show the same thing that the main render does? Or does Pier somehow > know which are Pier components and which are seaside components? Can you be a bit more precise? What do you do, add a new metadescribed structure kind to Pier or embed a Seaside application (that uses Magritte somewhere) in Pier? What do you mean with 'Will the Pier settings button show the same thing that the main render does'? Whether it will work on your component class like on other components? Philippe > Thanks, > Jason > > _________________________________________________________________ > Don't miss your chance to WIN 10 hours of private jet travel from Microsoft(r) > Office Live http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/ > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From azreal1977 at hotmail.com Sun Feb 18 11:04:58 2007 From: azreal1977 at hotmail.com (J J) Date: Sun, 18 Feb 2007 10:04:58 +0000 Subject: Pier enhancement idea In-Reply-To: <66666f210702180151w2399d0cfr8bc54a4883f33e1f@mail.gmail.com> Message-ID: >From: "Philippe Marschall" >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Pier enhancement idea >Date: Sun, 18 Feb 2007 10:51:30 +0100 > >If Squeak supports sending an url (or loading code) from a webpage to >the currently open image .... Sorry, I'm confused. Are you pointing out a security issue, or a suggested implementation? I think security is no problem because the "Add" button only looks where we tell it, and if you somehow did download something bad just don't save it. As far as implementation, I'm sure that wont be too hard (and for sure it will be much more clean, elegant and easy to maintain then what Joomla is doing), and I planned on doing it myself once I get through some other tasks. I just thought I would see what others think about it, and see if maybe someone already was working on something similar. Thanks, Jason _________________________________________________________________ The average US Credit Score is 675. The cost to see yours: $0 by Experian. http://www.freecreditreport.com/pm/default.aspx?sc=660600&bcd=EMAILFOOTERAVERAGE From azreal1977 at hotmail.com Sun Feb 18 11:09:07 2007 From: azreal1977 at hotmail.com (J J) Date: Sun, 18 Feb 2007 10:09:07 +0000 Subject: Pier Magritte question In-Reply-To: <66666f210702180155t5c2510f9n85496de78dc6aaa9@mail.gmail.com> Message-ID: Sorry. What I mean is, Ramon has a screencase that shows how to make things in Seaside like, e.g. a Blog. He builds the domain classes and then uses Magritte-Seaside to display it in a web page. I can see a lot of components I would want working this way, but I was wondering if this would cause some strange behavior if these components were used in a Pier page since Pier already uses Magritte to configure components. http://onsmalltalk.com/programming/smalltalk/screencast-how-to-build-a-blog-in-15-minutes-with-seaside/ is the screencase I am talking about. >From: "Philippe Marschall" >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Pier Magritte question >Date: Sun, 18 Feb 2007 10:55:33 +0100 > >2007/2/18, J J : > > Hi, > > > > Related to my previous email, I was wondering what happens if I have a > > seaside component that uses Magritte to display itself (Ramon does this >a > > lot on his blog), and I try to use it in Pier. Will the Pier settings > > button show the same thing that the main render does? Or does Pier >somehow > > know which are Pier components and which are seaside components? > >Can you be a bit more precise? What do you do, add a new metadescribed >structure kind to Pier or embed a Seaside application (that uses >Magritte somewhere) in Pier? What do you mean with 'Will the Pier >settings button show the same thing that the main render does'? >Whether it will work on your component class like on other components? > >Philippe > > > Thanks, > > Jason > > > > _________________________________________________________________ > > Don't miss your chance to WIN 10 hours of private jet travel from >Microsoft(r) > > Office Live http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/ > > > > > > > > _______________________________________________ > > SmallWiki, Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > >_______________________________________________ >SmallWiki, Magritte, Pier and Related Tools ... >https://www.iam.unibe.ch/mailman/listinfo/smallwiki _________________________________________________________________ With tax season right around the corner, make sure to follow these few simple tips. http://articles.moneycentral.msn.com/Taxes/PreparationTips/PreparationTips.aspx?icid=HMFebtagline From philippe.marschall at gmail.com Sun Feb 18 11:15:16 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Sun, 18 Feb 2007 11:15:16 +0100 Subject: Pier Magritte question In-Reply-To: References: <66666f210702180155t5c2510f9n85496de78dc6aaa9@mail.gmail.com> Message-ID: <66666f210702180215j3092a049ibe8cf30fb4e10f2c@mail.gmail.com> 2007/2/18, J J : > Sorry. What I mean is, Ramon has a screencase that shows how to make things > in Seaside like, e.g. a Blog. He builds the domain classes and then uses > Magritte-Seaside to display it in a web page. > > I can see a lot of components I would want working this way, but I was > wondering if this would cause some strange behavior if these components were > used in a Pier page since Pier already uses Magritte to configure > components. No, if it does it is a bug. The only thing to be aware of is that the same style will be applied to Magritte forms whether they come from Pier or your application. The settings command should work on the root component class of your application. Philippe. > http://onsmalltalk.com/programming/smalltalk/screencast-how-to-build-a-blog-in-15-minutes-with-seaside/ > is the screencase I am talking about. > > > >From: "Philippe Marschall" > >Reply-To: "Magritte, Pier and Related Tools ..." > >To: "Magritte, Pier and Related Tools ..." > >Subject: Re: Pier Magritte question > >Date: Sun, 18 Feb 2007 10:55:33 +0100 > > > >2007/2/18, J J : > > > Hi, > > > > > > Related to my previous email, I was wondering what happens if I have a > > > seaside component that uses Magritte to display itself (Ramon does this > >a > > > lot on his blog), and I try to use it in Pier. Will the Pier settings > > > button show the same thing that the main render does? Or does Pier > >somehow > > > know which are Pier components and which are seaside components? > > > >Can you be a bit more precise? What do you do, add a new metadescribed > >structure kind to Pier or embed a Seaside application (that uses > >Magritte somewhere) in Pier? What do you mean with 'Will the Pier > >settings button show the same thing that the main render does'? > >Whether it will work on your component class like on other components? > > > >Philippe > > > > > Thanks, > > > Jason > > > > > > _________________________________________________________________ > > > Don't miss your chance to WIN 10 hours of private jet travel from > >Microsoft(r) > > > Office Live http://clk.atdmt.com/MRT/go/mcrssaub0540002499mrt/direct/01/ > > > > > > > > > > > > _______________________________________________ > > > SmallWiki, Magritte, Pier and Related Tools ... > > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > > > >_______________________________________________ > >SmallWiki, Magritte, Pier and Related Tools ... > >https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > _________________________________________________________________ > With tax season right around the corner, make sure to follow these few > simple tips. > http://articles.moneycentral.msn.com/Taxes/PreparationTips/PreparationTips.aspx?icid=HMFebtagline > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From philippe.marschall at gmail.com Sun Feb 18 11:21:23 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Sun, 18 Feb 2007 11:21:23 +0100 Subject: Pier enhancement idea In-Reply-To: References: <66666f210702180151w2399d0cfr8bc54a4883f33e1f@mail.gmail.com> Message-ID: <66666f210702180221i4fd5b6c3ve3af66d77185de5c@mail.gmail.com> 2007/2/18, J J : > >From: "Philippe Marschall" > >Reply-To: "Magritte, Pier and Related Tools ..." > >To: "Magritte, Pier and Related Tools ..." > >Subject: Re: Pier enhancement idea > >Date: Sun, 18 Feb 2007 10:51:30 +0100 > > > >If Squeak supports sending an url (or loading code) from a webpage to > >the currently open image .... > > Sorry, I'm confused. Are you pointing out a security issue, or a suggested > implementation? > > I think security is no problem because the "Add" button only looks where we > tell it, and if you somehow did download something bad just don't save it. There are a lot of security issues with that since in Smalltalk loading code means executing code (with the access rights of the image). Not saving the image might not help that much if you home directory has just been deleted. But that's not really the issue here. > As far as implementation, I'm sure that wont be too hard Then please show us a prototype. > (and for sure it > will be much more clean, elegant and easy to maintain then what Joomla is > doing), and I planned on doing it myself once I get through some other > tasks. I just thought I would see what others think about it, and see if > maybe someone already was working on something similar. > > Thanks, > Jason > > _________________________________________________________________ > The average US Credit Score is 675. The cost to see yours: $0 by Experian. > http://www.freecreditreport.com/pm/default.aspx?sc=660600&bcd=EMAILFOOTERAVERAGE > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From renggli at iam.unibe.ch Sun Feb 18 11:23:04 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 18 Feb 2007 11:23:04 +0100 Subject: Pier enhancement idea In-Reply-To: References: Message-ID: <4472E63B-B566-49A3-A376-2C6667A1E03C@iam.unibe.ch> > How would it sound to have something like this for Pier? Instead > of having > to open up the image, download a MC and/or Squeak map thing, you > can just go to the "Add" button, and one extra option there would > be to add a new > component. We could have some special button added on Squeak > source to say > if a package is a Pier or Seaside component. > > So what do people think of this idea? Well, you can do this already for quite some time: http://www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov Or do you have something else in mind? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From azreal1977 at hotmail.com Sun Feb 18 11:27:47 2007 From: azreal1977 at hotmail.com (J J) Date: Sun, 18 Feb 2007 10:27:47 +0000 Subject: Pier enhancement idea In-Reply-To: <4472E63B-B566-49A3-A376-2C6667A1E03C@iam.unibe.ch> Message-ID: No, I meant downloading something that wasn't previously in the image. Like your new blog component for example. Right now I have to find out where it is hosted, go there in MC and load it, then go into Pier to use it. In a Joomla system this can all be done from inside the web site, and I don't see why Pier would have to be any different. >From: Lukas Renggli >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Pier enhancement idea >Date: Sun, 18 Feb 2007 11:23:04 +0100 > > > How would it sound to have something like this for Pier? Instead > > of having > > to open up the image, download a MC and/or Squeak map thing, you > > can just go to the "Add" button, and one extra option there would > > be to add a new > > component. We could have some special button added on Squeak > > source to say > > if a package is a Pier or Seaside component. > > > > So what do people think of this idea? > >Well, you can do this already for quite some time: > > http://www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov > >Or do you have something else in mind? > >Cheers, >Lukas > >-- >Lukas Renggli >http://www.lukas-renggli.ch > > > >_______________________________________________ >SmallWiki, Magritte, Pier and Related Tools ... >https://www.iam.unibe.ch/mailman/listinfo/smallwiki _________________________________________________________________ Find what you need at prices you’ll love. Compare products and save at MSN® Shopping. http://shopping.msn.com/default/shp/?ptnrid=37,ptnrdata=24102&tcode=T001MSN20A0701 From renggli at iam.unibe.ch Sun Feb 18 11:31:29 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 18 Feb 2007 11:31:29 +0100 Subject: Pier enhancement idea In-Reply-To: References: Message-ID: <48B6747B-E03E-4598-B0B4-A046F94648DF@iam.unibe.ch> > In a Joomla system this can all be done from inside the web site, > and I don't see why Pier would have to be any different. Ok sure, that should be easily possible. Then we need sort of a database of package URLs that can be automatically loaded into Pier. Or maybe something together with SqueakMap? If we could introduce a Pier-Package tag then a UI could automatically build a list of those packages and offer to install/uninstall them into the running image. Cheers, Lukas > >> From: Lukas Renggli >> Reply-To: "Magritte, Pier and Related Tools ..." >> >> To: "Magritte, Pier and Related Tools ..." >> Subject: Re: Pier enhancement idea >> Date: Sun, 18 Feb 2007 11:23:04 +0100 >> >> > How would it sound to have something like this for Pier? Instead >> > of having >> > to open up the image, download a MC and/or Squeak map thing, you >> > can just go to the "Add" button, and one extra option there would >> > be to add a new >> > component. We could have some special button added on Squeak >> > source to say >> > if a package is a Pier or Seaside component. >> > >> > So what do people think of this idea? >> >> Well, you can do this already for quite some time: >> >> http://www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov >> >> Or do you have something else in mind? >> >> Cheers, >> Lukas >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > _________________________________________________________________ > Find what you need at prices you?ll love. Compare products and save > at MSN? Shopping. http://shopping.msn.com/default/shp/? > ptnrid=37,ptnrdata=24102&tcode=T001MSN20A0701 > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From azreal1977 at hotmail.com Sun Feb 18 11:54:45 2007 From: azreal1977 at hotmail.com (J J) Date: Sun, 18 Feb 2007 10:54:45 +0000 Subject: Pier enhancement idea In-Reply-To: <66666f210702180221i4fd5b6c3ve3af66d77185de5c@mail.gmail.com> Message-ID: >From: "Philippe Marschall" >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Pier enhancement idea >Date: Sun, 18 Feb 2007 11:21:23 +0100 > >There are a lot of security issues with that since in Smalltalk >loading code means executing code (with the access rights of the >image). Not saving the image might not help that much if you home >directory has just been deleted. But that's not really the issue here. Ok, yes that is true. If you download a smalltalk package that is evil it could delete data from your machine. But that is the case with MC, SqueakMap and any other thing. It isn't unique to what I am talking about. > > As far as implementation, I'm sure that wont be too hard > >Then please show us a prototype. You mean of how it should work? Look at Joomla, you go to a component page, say "add a new component" and it gives you a huge list of components people have made. You select one and it gets added to the system. Now it can be place inside pages just other components. Or do you mean how it would be implemented in Squeak? For that it would be much like SqueakMap. Or maybe you are asking me to do the work. If no one else has done it by the time I get to it, then I will. :) I'm just not the fastest implementer since work takes up 14 hours of my day and I have a wife and a new baby. :) _________________________________________________________________ Find a local pizza place, movie theater, and more….then map the best route! http://maps.live.com/?icid=hmtag1&FORM=MGAC01 From azreal1977 at hotmail.com Sun Feb 18 11:57:48 2007 From: azreal1977 at hotmail.com (J J) Date: Sun, 18 Feb 2007 10:57:48 +0000 Subject: Pier enhancement idea In-Reply-To: <48B6747B-E03E-4598-B0B4-A046F94648DF@iam.unibe.ch> Message-ID: Yes, exactly what I was thinking. We would also want Seaside components as well, since they clearly work. We might want to flag the Pier components with some special flag (e.g. a "Pier integrated" symbol) since the Pier components can take special advantage of the Pier system, while the Seaside components can't. >From: Lukas Renggli >Reply-To: "Magritte, Pier and Related Tools ..." >To: "Magritte, Pier and Related Tools ..." >Subject: Re: Pier enhancement idea >Date: Sun, 18 Feb 2007 11:31:29 +0100 > > > In a Joomla system this can all be done from inside the web site, > > and I don't see why Pier would have to be any different. > >Ok sure, that should be easily possible. Then we need sort of a >database of package URLs that can be automatically loaded into Pier. > >Or maybe something together with SqueakMap? If we could introduce a >Pier-Package tag then a UI could automatically build a list of those >packages and offer to install/uninstall them into the running image. > >Cheers, >Lukas > > > > >> From: Lukas Renggli > >> Reply-To: "Magritte, Pier and Related Tools ..." > >> > >> To: "Magritte, Pier and Related Tools ..." > >> Subject: Re: Pier enhancement idea > >> Date: Sun, 18 Feb 2007 11:23:04 +0100 > >> > >> > How would it sound to have something like this for Pier? Instead > >> > of having > >> > to open up the image, download a MC and/or Squeak map thing, you > >> > can just go to the "Add" button, and one extra option there would > >> > be to add a new > >> > component. We could have some special button added on Squeak > >> > source to say > >> > if a package is a Pier or Seaside component. > >> > > >> > So what do people think of this idea? > >> > >> Well, you can do this already for quite some time: > >> > >> http://www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov > >> > >> Or do you have something else in mind? > >> > >> Cheers, > >> Lukas > >> > >> -- > >> Lukas Renggli > >> http://www.lukas-renggli.ch > >> > >> > >> > >> _______________________________________________ > >> SmallWiki, Magritte, Pier and Related Tools ... > >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > _________________________________________________________________ > > Find what you need at prices you’ll love. Compare products and save > > at MSN® Shopping. http://shopping.msn.com/default/shp/? > > ptnrid=37,ptnrdata=24102&tcode=T001MSN20A0701 > > > > > > _______________________________________________ > > SmallWiki, Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > >-- >Lukas Renggli >http://www.lukas-renggli.ch > > > > >_______________________________________________ >SmallWiki, Magritte, Pier and Related Tools ... >https://www.iam.unibe.ch/mailman/listinfo/smallwiki _________________________________________________________________ Play Flexicon: the crossword game that feeds your brain. PLAY now for FREE.  http://zone.msn.com/en/flexicon/default.htm?icid=flexicon_hmtagline From renggli at iam.unibe.ch Sun Feb 18 13:51:17 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 18 Feb 2007 13:51:17 +0100 Subject: Pier Magritte question In-Reply-To: References: Message-ID: > Related to my previous email, I was wondering what happens if I > have a seaside component that uses Magritte to display itself > (Ramon does this a lot on his blog), and I try to use it in Pier. > Will the Pier settings button show the same thing that the main > render does? Or does Pier somehow know which are Pier components > and which are seaside components? Basically Pier doesn't care if it is a Seaside component or a special Pier component. You can add and configure any Seaside component that answers true for #canBeRoot. Now for quite some time Seaside started to use #description to return a descriptive text of the component, what sort of conflicts with Magritte. Cheers, Lukas > > Thanks, > Jason > > _________________________________________________________________ > Don?t miss your chance to WIN 10 hours of private jet travel from > Microsoft? Office Live http://clk.atdmt.com/MRT/go/ > mcrssaub0540002499mrt/direct/01/ > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Sun Feb 18 17:19:33 2007 From: brad at sonaural.com (Brad Fuller) Date: Sun, 18 Feb 2007 08:19:33 -0800 Subject: Pier Stylesheets In-Reply-To: <66666f210702180144k2d61a31fpc7fa7538611d3128@mail.gmail.com> References: <45D6B5B9.2050706@sonaural.com> <66666f210702180144k2d61a31fpc7fa7538611d3128@mail.gmail.com> Message-ID: <45D87C95.5050503@sonaural.com> Philippe Marschall wrote: > 2007/2/17, Brad Fuller : >> Looking through the various Pier documentation, I see that code has >> changed and thus there are several different explanations of how to >> change stylesheets. I want to use a different css stylesheets but I >> can't find out where to change it/them. Isn't there one place to point >> Pier to one stylesheet? >> >> BTW: for some reason, I have no style sheet at all for Pier. I don't >> know what I did, but I didn't edit any code... I must have loaded a new >> version of some package. Anyway, unless it stomped on something else, if >> I can learn where to change the stylesheet pointer, It'd give me a start. > > Thanks to Christoph Wysseier Pier now supports easy custom styles with > FileLibraries. All you need to do is provide your own FileLibrary that > implements #styleCss which returns a string that is the main CSS file. > You can put all your CSS there, or in other selectors (as PierLibrary > does) or in other locations by importing the CSS files you need. > > For example if #styleCss makes > @import url(basic.css); > this means #basicCss is imported. Basic FileLibrary stuff. FileLibrary > one of the classes that actually have a comment that describes what it > does. > > In the configuration of your pier application under 'Pier' you can > select it in 'File Library'. Thanks Philippe. Now that I'm back running to a basic, and slightly older implementation, I'll check it out. From renggli at iam.unibe.ch Sun Feb 18 22:01:18 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 18 Feb 2007 22:01:18 +0100 Subject: mc.lukas-renggli.ch down? In-Reply-To: References: <4CCBA83E-E242-40E7-8FF8-1565D17895A4@inextenso.com> <45353819-63DE-4534-9C5D-13176FC4A239@iam.unibe.ch> Message-ID: >>> Looks like there might be a problem with mc.lukas-renggli.ch (Sat >>> 21:54). >> >> thanks for reporting. It seems to work for me. How did you got >> into this problem? > > Initially by requesting to load the Pier-Blog Module in Squeak (no > load), and then by visiting the website with safari, this over a > period between 1900 and 2200 yesterday. > > So *now* I have the issue that loading Pier-All-lr.162 says: > > This package depends on the following classes: > WAFileLibrary > > How can I do this? Well after loading Pier from SqueakMap you have to update Seaside, Magritte, and Pier to the latest version. Then you have to load the package RSRSS from http://www.squeaksource.com/rsrss and then load the blog plugin. Sorry, it is still a bit complicated and there are still some strange bugs in the blog plugin ... Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at iam.unibe.ch Sun Feb 18 22:07:34 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sun, 18 Feb 2007 22:07:34 +0100 Subject: Pier enhancement idea In-Reply-To: References: Message-ID: > Yes, exactly what I was thinking. We would also want Seaside > components as well, since they clearly work. > > We might want to flag the Pier components with some special flag > (e.g. a "Pier integrated" symbol) since the Pier components can > take special advantage of the Pier system, while the Seaside > components can't. Exactly, maybe we should ask to Goran (I think he is the maintainer of SqueakMap) if we could get those two tags (Seaside, Pier, maybe also Magritte) so that we can query and filter the SqueakMap database from a standard Seaside/Pier component to allow loading extension through the existing SqueakMap interface and reuse all its functionality from there. Cheers, Lukas > >> From: Lukas Renggli >> Reply-To: "Magritte, Pier and Related Tools ..." >> >> To: "Magritte, Pier and Related Tools ..." >> Subject: Re: Pier enhancement idea >> Date: Sun, 18 Feb 2007 11:31:29 +0100 >> >> > In a Joomla system this can all be done from inside the web site, >> > and I don't see why Pier would have to be any different. >> >> Ok sure, that should be easily possible. Then we need sort of a >> database of package URLs that can be automatically loaded into Pier. >> >> Or maybe something together with SqueakMap? If we could introduce a >> Pier-Package tag then a UI could automatically build a list of those >> packages and offer to install/uninstall them into the running image. >> >> Cheers, >> Lukas >> >> > >> >> From: Lukas Renggli >> >> Reply-To: "Magritte, Pier and Related Tools ..." >> >> >> >> To: "Magritte, Pier and Related Tools ..." >> >> >> Subject: Re: Pier enhancement idea >> >> Date: Sun, 18 Feb 2007 11:23:04 +0100 >> >> >> >> > How would it sound to have something like this for Pier? >> Instead >> >> > of having >> >> > to open up the image, download a MC and/or Squeak map thing, you >> >> > can just go to the "Add" button, and one extra option there >> would >> >> > be to add a new >> >> > component. We could have some special button added on Squeak >> >> > source to say >> >> > if a package is a Pier or Seaside component. >> >> > >> >> > So what do people think of this idea? >> >> >> >> Well, you can do this already for quite some time: >> >> >> >> http://www.lukas-renggli.ch/smalltalk/pier/videos/sushi.mov >> >> >> >> Or do you have something else in mind? >> >> >> >> Cheers, >> >> Lukas >> >> >> >> -- >> >> Lukas Renggli >> >> http://www.lukas-renggli.ch >> >> >> >> >> >> >> >> _______________________________________________ >> >> SmallWiki, Magritte, Pier and Related Tools ... >> >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > >> > _________________________________________________________________ >> > Find what you need at prices you?ll love. Compare products and save >> > at MSN? Shopping. http://shopping.msn.com/default/shp/? >> > ptnrid=37,ptnrdata=24102&tcode=T001MSN20A0701 >> > >> > >> > _______________________________________________ >> > SmallWiki, Magritte, Pier and Related Tools ... >> > https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > _________________________________________________________________ > Play Flexicon: the crossword game that feeds your brain. PLAY now > for FREE. http://zone.msn.com/en/flexicon/default.htm? > icid=flexicon_hmtagline > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- Lukas Renggli http://www.lukas-renggli.ch From mathieu.cassonnet at laposte.net Mon Feb 19 16:22:40 2007 From: mathieu.cassonnet at laposte.net (Mathieu Cassonnet) Date: Mon, 19 Feb 2007 16:22:40 +0100 Subject: Page Information Tutorial Message-ID: <45D9C0C0.2030006@laposte.net> Hi, I use the Page Information Tutorial (http://smallwiki.unibe.ch/smallwiki/pier/) of Damien Cassou to add my widget on Pier. But when I want to add my widget to the "Environment" (following chapter 4 and 5) the "Environment" page doesn't appear on the tree! How does this actually work on Pier to add a widget to the "Environment"? (the tutorial seems not up to date) PS: my widget works great it's not the problem :) Regards Mat From chris at wysseier.net Mon Feb 19 16:49:51 2007 From: chris at wysseier.net (Christoph Wysseier) Date: Mon, 19 Feb 2007 16:49:51 +0100 Subject: Pier Stylesheets In-Reply-To: <45D6B5B9.2050706@sonaural.com> References: <45D6B5B9.2050706@sonaural.com> Message-ID: <45D9C71F.5060702@wysseier.net> Brad Fuller schrieb: > Looking through the various Pier documentation, I see that code has > changed and thus there are several different explanations of how to > change stylesheets. I want to use a different css stylesheets but I > can't find out where to change it/them. Isn't there one place to point > Pier to one stylesheet? Here again my mail (26.12.2006) pointing out how to change the stylesheet for different look'n'feel of Pier: Pier is using Seaside File Libraries (PRPierLibrary) to store CSS and images for the look'n'feel. Using a small extension that I just committed it is now very easy to change the look'n'feel by just changing the file library to another one. Name: Pier-Seaside-cw.107 Author: cw Time: 26 December 2006, 12:56:04 pm After loading this patch a variable will be available in the seaside config that allows you to change the default File Library to any other you need to provide before (any subclass of WAFileLibrary is available). This way the look'n'feel may be changed on-the-fly and you may store your own File Library with your CSS and image files in a repository of your choice. Cheers, Chris From cbeler at enit.fr Mon Feb 19 17:00:32 2007 From: cbeler at enit.fr (=?ISO-8859-1?Q?C=E9drick_B=E9ler?=) Date: Mon, 19 Feb 2007 17:00:32 +0100 Subject: Page Information Tutorial In-Reply-To: <45D9C0C0.2030006@laposte.net> References: <45D9C0C0.2030006@laposte.net> Message-ID: <45D9C9A0.1080405@enit.fr> Hi Mathieu Cassonnet a ?crit : > Hi, > > I use the Page Information Tutorial > (http://smallwiki.unibe.ch/smallwiki/pier/) of Damien Cassou to add my > widget on Pier. > But when I want to add my widget to the "Environment" (following chapter > 4 and 5) the "Environment" page doesn't appear on the tree! > You have to login as admin admin:pier and then it should appear... > How does this actually work on Pier to add a widget to the > "Environment"? (the tutorial seems not up to date) > probably ;) > C?drick From renggli at iam.unibe.ch Mon Feb 19 17:35:57 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Mon, 19 Feb 2007 17:35:57 +0100 Subject: Page Information Tutorial In-Reply-To: <45D9C9A0.1080405@enit.fr> References: <45D9C0C0.2030006@laposte.net> <45D9C9A0.1080405@enit.fr> Message-ID: >> I use the Page Information Tutorial >> (http://smallwiki.unibe.ch/smallwiki/pier/) of Damien Cassou to >> add my >> widget on Pier. >> But when I want to add my widget to the "Environment" (following >> chapter >> 4 and 5) the "Environment" page doesn't appear on the tree! >> > You have to login as admin > admin:pier If you haven't loaded a security system then you have to manually type the path to get into the environment as it is hidden by default. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From mathieu.cassonnet at laposte.net Mon Feb 19 18:06:11 2007 From: mathieu.cassonnet at laposte.net (Mathieu Cassonnet) Date: Mon, 19 Feb 2007 18:06:11 +0100 Subject: Page Information Tutorial In-Reply-To: References: <45D9C0C0.2030006@laposte.net> <45D9C9A0.1080405@enit.fr> Message-ID: <45D9D903.5070804@laposte.net> Lukas Renggli a ?crit : >>> I use the Page Information Tutorial >>> (http://smallwiki.unibe.ch/smallwiki/pier/) of Damien Cassou to >>> add my >>> widget on Pier. >>> But when I want to add my widget to the "Environment" (following >>> chapter >>> 4 and 5) the "Environment" page doesn't appear on the tree! >>> >>> >> You have to login as admin >> admin:pier >> > > If you haven't loaded a security system then you have to manually > type the path to get into the environment as it is hidden by default. > > Cheers, > Lukas > > thanks both, it's work. Now I have a mistake with the css I use this class method : PRPageQueryWidget class>>defaultCssClass ? ?box? And when I watch at the css on "http://www.lukas-renggli.ch/smalltalk/pier/style/84/style-box.css" there is a class named 'box' But no box css display on the page! So I use code like that: html div class:'box'; with:[] Is it the good way to proceed? From brad at sonaural.com Tue Feb 20 16:36:12 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 20 Feb 2007 07:36:12 -0800 Subject: [Seaside] ReWrite Rule and css files - what am I doing wrong? In-Reply-To: <67628d690702192308k74f5c51cu5393bd41914d063c@mail.gmail.com> References: <45DA29FF.7050802@sonaural.com> <67628d690702192308k74f5c51cu5393bd41914d063c@mail.gmail.com> Message-ID: <45DB156C.9030604@sonaural.com> Lukas Renggli wrote: >> But, when looking at the apache access log there is: >> >> GET /seaside/files/PRPierLibrary/style.css HTTP/1.1" 404 83 >> >> In the configuration page, PRPierLibary is in the File Library under >> Pier. But I don't know why there is css formating in the direct way >> (http://www.my_domain.org:9999/seaside/pier), and apache is looking for >> a css file in the second (http://www.my_domain.org/). > > That's the new way for Seaside to serve static files. > >> BTW: I did create a sub-directory called: files/PRPierLibrary with the >> default style.css from Lukas under the directory where the image is >> located, but that didn't do anything. >> (I stopped and restarted WAKom just in case.) > > You either need to create a directory seaside/files/PRPierLibrary/ > with your files or add the following rewrite rule right after enabling > the rewrite engine: > > RewriteRule ^/seaside/files/PRPierLibrary/(*.)$ > http://www.my_domain.org:9999//seaside/files/PRPierLibrary/$1 [P,L] (I moved this to the Pier ML as I think it's Pier related, sorry if this is confusing - don't want to bother others) Thanks Lukas. Along those same lines, I'm getting long lines after the domain name when I select a link in Pier. Is this correct? information/license?command=PRViewCommand&view=PRDefaultView&_k=swboZglt&29&_n&_s=MELVlGoXVospTlDw ?command=PRViewCommand&view=PRDefaultView&_k=zYTOouCP&21&_n&_s=MELVlGoXVospTlDw information/license?command=PRViewCommand&view=PRDefaultView&_k=rKYbypAd&25&_n&_s=MELVlGoXVospTlDw seems like it should be shorter.. they are shorter in my other seaside app, although, it's not Pier. From brad at sonaural.com Thu Feb 22 17:32:00 2007 From: brad at sonaural.com (Brad Fuller) Date: Thu, 22 Feb 2007 08:32:00 -0800 Subject: Resizing Photos in Pier Message-ID: <45DDC580.7020101@sonaural.com> Will the seaside location/key of a file that has been uploaded as a "file" in Pier be guaranteed to be static? For instance, can you always be guaranteed that a photograph that was uploaded be guaranteed to be at that address? Example, this is a photo uploaded to pier: http://www./?_s=BGrhMyNQYJbYqctY" Can this link be used to resize the photo and be guaranteed not to change? References: <45D5E1C9.8090304@sonaural.com> <45D61572.9070401@sonaural.com> <45D64098.90709@yahoo.co.uk> Message-ID: <45DE0396.2000204@sonaural.com> Keith Hodges wrote: > Brad Fuller wrote: >> Lukas Renggli wrote: >> >>>> how come when I try to load from http://mc.lukas-renggli.ch/pier for >>>> "blog" package I receive "This package depends on the following >>>> classes:" >>>> >>>> and there are many of them. Is there a better way to load Pier >>>> packages? >>>> >>> Load Pier from SqueakMap, then update Magritte and Pier using >>> Monticello from http://mc.lukas-renggli.ch/magritte and http:// >>> mc.lukas-renggli.ch/pier. >>> >>> The Blog package requires the package RsRss from the Seaside >>> repository: http://www.squeaksource.com/Seaside >>> >> Looks like there is just one more package to go >> >> Pier-Magma >> >> but I have this problem: >> >> This package depends on the following classes: >> PRPierControlPanel >> You must resolve these dependencies before you will be able to load >> these definitions: >> PRPierControlPanel>>deleteRepositoryKernel: >> PRPierControlPanel>>renderPRMagmaPersistency:kernel:on: >> >> I've loaded all the other pier packages. Do you know where this is? >> >> > It is in Seaside 2.6b branch and I merged it into Seaside 2.7 as well, > however for some reason the main seaside practicioners have not got it > in their latest. So if you look for my last contribution to Seaside 2.7a > it will definitely be there. (kph) > > This is what I mean by 'small' things to sort out. Keith, I have the latest Seaside (Seaside2.7a1-pmm.153.mcz in config, but MC says v203... don't know why that is), but I still receive this dependency problem This package depends on the following classes: PRPierControlPanel From philippe.marschall at gmail.com Fri Feb 23 10:52:06 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Fri, 23 Feb 2007 10:52:06 +0100 Subject: Resizing Photos in Pier In-Reply-To: <45DDC580.7020101@sonaural.com> References: <45DDC580.7020101@sonaural.com> Message-ID: <66666f210702230152o39adb212g13aef6954817eea6@mail.gmail.com> 2007/2/22, Brad Fuller : > Will the seaside location/key of a file that has been uploaded as a > "file" in Pier be guaranteed to be static? For instance, can you always > be guaranteed that a photograph that was uploaded be guaranteed to be at > that address? Yes, in the same way that other Pier resouces are static. If you move a structure around, change the Seaside or Apache2 setup or stuff it will break. > Example, this is a photo uploaded to pier: > http://www./?_s=BGrhMyNQYJbYqctY" > > Can this link be used to resize the photo and be guaranteed not to change? No > height="300" Resizing by the browser produces crappy results in every browser but Safari (not sure about Konqueror). > Or, what's the way to resize photos? Currently none. Pier Image Gallery does it but it is not dynamic. Philippe > -- > brad fuller > http://www.Sonaural.com/ > +1 (408) 799-6124 > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From renggli at iam.unibe.ch Fri Feb 23 11:01:59 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Fri, 23 Feb 2007 11:01:59 +0100 Subject: Resizing Photos in Pier In-Reply-To: <66666f210702230152o39adb212g13aef6954817eea6@mail.gmail.com> References: <45DDC580.7020101@sonaural.com> <66666f210702230152o39adb212g13aef6954817eea6@mail.gmail.com> Message-ID: <99A29A19-9A98-47C1-B4EC-8C01A2980BE5@iam.unibe.ch> >> Will the seaside location/key of a file that has been uploaded as a >> "file" in Pier be guaranteed to be static? For instance, can you >> always be guaranteed that a photograph that was uploaded be >> guaranteed to be at that address? > > Yes, in the same way that other Pier resouces are static. If you > move a structure around, change the Seaside or Apache2 setup or > stuff it will break. Pier produces REST-ful and static URLs for all its structures, including resources/files. As long as you don't move the structure it is bookmark-able and you can send the link around. >> Example, this is a photo uploaded to pier: >> http://www./?_s=BGrhMyNQYJbYqctY" >> >> Can this link be used to resize the photo and be guaranteed not to >> change? > > No Pier doesn't resize photos by default. There are extensions, like the mentioned Pier Image Gallery, that provide support for that. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Fri Feb 23 15:24:10 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Fri, 23 Feb 2007 14:24:10 +0000 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45DE0396.2000204@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D61572.9070401@sonaural.com> <45D64098.90709@yahoo.co.uk> <45DE0396.2000204@sonaural.com> Message-ID: <45DEF90A.6090600@yahoo.co.uk> Brad Fuller wrote: > Keith Hodges wrote: > >> Brad Fuller wrote: >> >>> Lukas Renggli wrote: >>> >>> >>>>> how come when I try to load from http://mc.lukas-renggli.ch/pier for >>>>> "blog" package I receive "This package depends on the following >>>>> classes:" >>>>> >>>>> and there are many of them. Is there a better way to load Pier >>>>> packages? >>>>> >>>>> >>>> Load Pier from SqueakMap, then update Magritte and Pier using >>>> Monticello from http://mc.lukas-renggli.ch/magritte and http:// >>>> mc.lukas-renggli.ch/pier. >>>> >>>> The Blog package requires the package RsRss from the Seaside >>>> repository: http://www.squeaksource.com/Seaside >>>> >>>> >>> Looks like there is just one more package to go >>> >>> Pier-Magma >>> >>> but I have this problem: >>> >>> This package depends on the following classes: >>> PRPierControlPanel >>> You must resolve these dependencies before you will be able to load >>> these definitions: >>> PRPierControlPanel>>deleteRepositoryKernel: >>> PRPierControlPanel>>renderPRMagmaPersistency:kernel:on: >>> >>> I've loaded all the other pier packages. Do you know where this is? >>> >>> >>> >> It is in Seaside 2.6b branch and I merged it into Seaside 2.7 as well, >> however for some reason the main seaside practicioners have not got it >> in their latest. So if you look for my last contribution to Seaside 2.7a >> it will definitely be there. (kph) >> >> This is what I mean by 'small' things to sort out. >> > > Keith, > > I have the latest Seaside (Seaside2.7a1-pmm.153.mcz in config, but MC > says v203... don't know why that is), but I still receive this > dependency problem > > This package depends on the following classes: > PRPierControlPanel > Pier Control Panel is in one of my versions of Pier-Seaside, I dont think lukas accepted it into his latest. So after talking with lukas about it I suggested reorganising things to produce a separate Pier_Persistency manager package. I am planning to have a go at this over the weekend. I am very sorry that it has taken me so long to get around to sorting the SMP image out. Keith ___________________________________________________________ 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 brad at sonaural.com Sat Feb 24 02:05:17 2007 From: brad at sonaural.com (Brad Fuller) Date: Fri, 23 Feb 2007 17:05:17 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> Message-ID: <45DF8F4D.2090200@sonaural.com> Lukas Renggli wrote: >> PRSearchWidget>>go >> self items in: [ :Name already used in this class ->items | >> items notEmpty ifTrue: [ >> self context: (self context structure: items first) ] ] > > Oh god, that is a long standing bug in Monticello that strikes again: > there are some cases when the load order is wrong and causes a > compile error. In this case it is the simples just to delete the > method and load the package again. I think _pretty_much_ have the latest Magritte/Pier running. Took me a while. However, I did come across this again while upgrading. I deleted the method PRSearchWidget>>go and upgraded. Now, though, search doesn't work. When I press return, it doesn't do anything. And, when you look at the components list (when adding a component) there are TWO search component. I tried both. The second one behaves as I have described. The first one actual seems to do something (the hourglass goes on like it's "working"). But, it never finds anything. Just to add a bit more mystery: search never worked in the Pier version that was on SqueakMap. It never found any word. Although, the text cursor went away after hitting return. -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Sat Feb 24 08:57:25 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 24 Feb 2007 08:57:25 +0100 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45DF8F4D.2090200@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> <45DF8F4D.2090200@sonaural.com> Message-ID: > However, I did come across this again while upgrading. I deleted the > method PRSearchWidget>>go and upgraded. Now, though, search doesn't > work. When I press return, it doesn't do anything. Do you have the latest version of Pier-Seaside? I just recently fixed this problem. > And, when you look at the components list (when adding a component) > there are TWO search component. I tried both. The second one > behaves as > I have described. The first one actual seems to do something (the > hourglass goes on like it's "working"). But, it never finds anything. Strange, I just have one. What about in your image? Try to display the changes of Pier-Seaside and see if there any load-artifacts left over by Monticello. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Sat Feb 24 18:35:38 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 24 Feb 2007 09:35:38 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> <45DF8F4D.2090200@sonaural.com> Message-ID: <45E0776A.8010107@sonaural.com> Lukas Renggli wrote: >> However, I did come across this again while upgrading. I deleted the >> method PRSearchWidget>>go and upgraded. Now, though, search doesn't >> work. When I press return, it doesn't do anything. > > Do you have the latest version of Pier-Seaside? I just recently fixed > this problem. I have: Pier-Seaside-lr.138.mcz There is one newer version from Pierre, which I just loaded. No change. > >> And, when you look at the components list (when adding a component) >> there are TWO search component. I tried both. The second one >> behaves as >> I have described. The first one actual seems to do something (the >> hourglass goes on like it's "working"). But, it never finds anything. > > Strange, I just have one. What about in your image? Try to display > the changes of Pier-Seaside and see if there any load-artifacts left > over by Monticello. I don't see anything strange. I put in a halt in a couple of methods so I could trace what was happening but it never made it to the methods. (that's when I went back to Pier and saw two components for search.) So those are there in the changes, but those are mine. Hmm, I don't think this is related, but when I updated Pier before I received your instructions on PRPierFrame initialize. I replied to create a new kernel. That gave me two piers with the same name. In the Pier Browser, they are both there. I'd like to get rid of the first one. How can I do that. However, I don't see how this would be related. Thanks for the reply and help, Lukas! brad -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Sat Feb 24 20:27:54 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 24 Feb 2007 20:27:54 +0100 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45E0776A.8010107@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> <45DF8F4D.2090200@sonaural.com> <45E0776A.8010107@sonaural.com> Message-ID: <6FD52F66-5905-4189-8D2E-E5593CF014B6@iam.unibe.ch> >>> However, I did come across this again while upgrading. I deleted the >>> method PRSearchWidget>>go and upgraded. Now, though, search doesn't >>> work. When I press return, it doesn't do anything. >> >> Do you have the latest version of Pier-Seaside? I just recently fixed >> this problem. > > I have: Pier-Seaside-lr.138.mcz > > There is one newer version from Pierre, which I just loaded. No > change. Philippe ;-) >>> And, when you look at the components list (when adding a component) >>> there are TWO search component. I tried both. The second one >>> behaves as >>> I have described. The first one actual seems to do something (the >>> hourglass goes on like it's "working"). But, it never finds >>> anything. >> >> Strange, I just have one. What about in your image? Try to display >> the changes of Pier-Seaside and see if there any load-artifacts left >> over by Monticello. > > I don't see anything strange. I put in a halt in a couple of > methods so > I could trace what was happening but it never made it to the methods. > (that's when I went back to Pier and saw two components for > search.) So > those are there in the changes, but those are mine. The expression used to calculate the list of components is the following: Array streamContents: [ :stream | PRWidget allSubclassesDo: [ :each | each isAbstract ifFalse: [ stream nextPut: each ] ]. WAComponent allSubclassesDo: [ :each | each canBeRoot ifTrue: [ stream nextPut: each ] ] ] In my image this results in: {PRCommandsWidget . PRHeaderWidget . PRNavigationWidget . PRPathWidget . PRReferencesWidget . PRTreeWidget . PRChildrenWidget . PRSearchWidget . PRViewsWidget . PRTocWidget . PUSecurityWidget . PRContentsWidget . PRXHtmlWidget . PUGroupsWidget . PUUsersWidget . PUSystemWidget . PBPostTicker . WACounter . WAExampleBrowser . WAFileLibraryExample . WAAllCanvasTests . WAAllTests . WAMiniCalendar . WAMultiCounter . WAScreenshot . WAStore . WAVNCController . WAVersionUploader . SUAllTests . PRPierFrame . WADispatcherViewer . WADispatcherEditor . RRChangesDemo . RRDemo} Maybe you have some other Seaside/Magritte/Pier code loaded that provides a different search component? > Hmm, I don't think this is related, but when I updated Pier before I > received your instructions on PRPierFrame initialize. I replied to > create a new kernel. That gave me two piers with the same name. In the > Pier Browser, they are both there. I'd like to get rid of the first > one. How can I do that. Evaluate PRKernel instances inspect and then remove the one you don't want anymore. Note that if you have an entry point defined in Seaside using the removed kernel, it won't disappear from the Smalltalk image. > However, I don't see how this would be related. No, that's certainly not the problem for the two search boxes. Note that the Search Widget is one of the Widgets with two lives, one when you have SULibrary (Scriptaculous) in your list of libraries and one if no AJAX support is available. Depending on the mode it behaves different, both modes work for me. Note that you also might want to check the settings of the Search Widget, it might well be that you filter out some types and therefor see no results. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Sat Feb 24 21:07:05 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 24 Feb 2007 12:07:05 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <6FD52F66-5905-4189-8D2E-E5593CF014B6@iam.unibe.ch> References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> <45DF8F4D.2090200@sonaural.com> <45E0776A.8010107@sonaural.com> <6FD52F66-5905-4189-8D2E-E5593CF014B6@iam.unibe.ch> Message-ID: <45E09AE9.1070306@sonaural.com> Lukas Renggli wrote: > > The expression used to calculate the list of components is the > following: > > Array streamContents: [ :stream | > PRWidget allSubclassesDo: [ :each | > each isAbstract > ifFalse: [ stream nextPut: each ] ]. > WAComponent allSubclassesDo: [ :each | > each canBeRoot > ifTrue: [ stream nextPut: each ] ] ] > > In my image this results in: > > {PRCommandsWidget . PRHeaderWidget . PRNavigationWidget . > PRPathWidget . PRReferencesWidget . PRTreeWidget . PRChildrenWidget . > PRSearchWidget . PRViewsWidget . PRTocWidget . PUSecurityWidget . > PRContentsWidget . PRXHtmlWidget . PUGroupsWidget . PUUsersWidget . > PUSystemWidget . PBPostTicker . WACounter . WAExampleBrowser . > WAFileLibraryExample . WAAllCanvasTests . WAAllTests . > WAMiniCalendar . WAMultiCounter . WAScreenshot . WAStore . > WAVNCController . WAVersionUploader . SUAllTests . PRPierFrame . > WADispatcherViewer . WADispatcherEditor . RRChangesDemo . RRDemo} I get pretty much the same thing... a list like this (a bit different) > > Maybe you have some other Seaside/Magritte/Pier code loaded that > provides a different search component? > >> Hmm, I don't think this is related, but when I updated Pier before I >> received your instructions on PRPierFrame initialize. I replied to >> create a new kernel. That gave me two piers with the same name. In the >> Pier Browser, they are both there. I'd like to get rid of the first >> one. How can I do that. > > Evaluate > > PRKernel instances inspect > > and then remove the one you don't want anymore. Note that if you have > an entry point defined in Seaside using the removed kernel, it won't > disappear from the Smalltalk image. > >> However, I don't see how this would be related. > > No, that's certainly not the problem for the two search boxes. > > Note that the Search Widget is one of the Widgets with two lives, one > when you have SULibrary (Scriptaculous) in your list of libraries and > one if no AJAX support is available. Depending on the mode it behaves > different, both modes work for me. I have SULibrary loaded and when I removed it, the search worked! So, progress. I have the latest Scriptaculous installed. Anything special about Pier in regard to this? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Sat Feb 24 21:36:09 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 24 Feb 2007 21:36:09 +0100 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45E09AE9.1070306@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> <45DF8F4D.2090200@sonaural.com> <45E0776A.8010107@sonaural.com> <6FD52F66-5905-4189-8D2E-E5593CF014B6@iam.unibe.ch> <45E09AE9.1070306@sonaural.com> Message-ID: >> {PRCommandsWidget . PRHeaderWidget . PRNavigationWidget . >> PRPathWidget . PRReferencesWidget . PRTreeWidget . PRChildrenWidget . >> PRSearchWidget . PRViewsWidget . PRTocWidget . PUSecurityWidget . >> PRContentsWidget . PRXHtmlWidget . PUGroupsWidget . PUUsersWidget . >> PUSystemWidget . PBPostTicker . WACounter . WAExampleBrowser . >> WAFileLibraryExample . WAAllCanvasTests . WAAllTests . >> WAMiniCalendar . WAMultiCounter . WAScreenshot . WAStore . >> WAVNCController . WAVersionUploader . SUAllTests . PRPierFrame . >> WADispatcherViewer . WADispatcherEditor . RRChangesDemo . RRDemo} > > I get pretty much the same thing... a list like this (a bit different) No obsolete classes in the list? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Sat Feb 24 22:18:28 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 24 Feb 2007 13:18:28 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> <45DF8F4D.2090200@sonaural.com> <45E0776A.8010107@sonaural.com> <6FD52F66-5905-4189-8D2E-E5593CF014B6@iam.unibe.ch> <45E09AE9.1070306@sonaural.com> Message-ID: <45E0ABA4.2080401@sonaural.com> Lukas Renggli wrote: >>> {PRCommandsWidget . PRHeaderWidget . PRNavigationWidget . >>> PRPathWidget . PRReferencesWidget . PRTreeWidget . PRChildrenWidget . >>> PRSearchWidget . PRViewsWidget . PRTocWidget . PUSecurityWidget . >>> PRContentsWidget . PRXHtmlWidget . PUGroupsWidget . PUUsersWidget . >>> PUSystemWidget . PBPostTicker . WACounter . WAExampleBrowser . >>> WAFileLibraryExample . WAAllCanvasTests . WAAllTests . >>> WAMiniCalendar . WAMultiCounter . WAScreenshot . WAStore . >>> WAVNCController . WAVersionUploader . SUAllTests . PRPierFrame . >>> WADispatcherViewer . WADispatcherEditor . RRChangesDemo . RRDemo} >> I get pretty much the same thing... a list like this (a bit different) > > No obsolete classes in the list? No, just two PRSearchWidget From renggli at iam.unibe.ch Sat Feb 24 23:35:52 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Sat, 24 Feb 2007 23:35:52 +0100 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: <45E0ABA4.2080401@sonaural.com> References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> <45DF8F4D.2090200@sonaural.com> <45E0776A.8010107@sonaural.com> <6FD52F66-5905-4189-8D2E-E5593CF014B6@iam.unibe.ch> <45E09AE9.1070306@sonaural.com> <45E0ABA4.2080401@sonaural.com> Message-ID: >>>> {PRCommandsWidget . PRHeaderWidget . PRNavigationWidget . >>>> PRPathWidget . PRReferencesWidget . PRTreeWidget . >>>> PRChildrenWidget . >>>> PRSearchWidget . PRViewsWidget . PRTocWidget . PUSecurityWidget . >>>> PRContentsWidget . PRXHtmlWidget . PUGroupsWidget . PUUsersWidget . >>>> PUSystemWidget . PBPostTicker . WACounter . WAExampleBrowser . >>>> WAFileLibraryExample . WAAllCanvasTests . WAAllTests . >>>> WAMiniCalendar . WAMultiCounter . WAScreenshot . WAStore . >>>> WAVNCController . WAVersionUploader . SUAllTests . PRPierFrame . >>>> WADispatcherViewer . WADispatcherEditor . RRChangesDemo . RRDemo} >>> I get pretty much the same thing... a list like this (a bit >>> different) >> >> No obsolete classes in the list? > > No, just two PRSearchWidget Then your Smalltalk class hierarchy must be corrupt. I don't know exactly how to fix that. Maybe inspect the superclass of PRSearchWidget and see if there is anything wrong with the subclass declaration? Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From brad at sonaural.com Sun Feb 25 00:10:16 2007 From: brad at sonaural.com (Brad Fuller) Date: Sat, 24 Feb 2007 15:10:16 -0800 Subject: loading Pier-Blog-lr.40.mcz in MC - error In-Reply-To: References: <45D5E1C9.8090304@sonaural.com> <45D6028A.50605@sonaural.com> <45DF8F4D.2090200@sonaural.com> <45E0776A.8010107@sonaural.com> <6FD52F66-5905-4189-8D2E-E5593CF014B6@iam.unibe.ch> <45E09AE9.1070306@sonaural.com> <45E0ABA4.2080401@sonaural.com> Message-ID: <45E0C5D8.3070403@sonaural.com> Lukas Renggli wrote: >>> No obsolete classes in the list? >> No, just two PRSearchWidget > > Then your Smalltalk class hierarchy must be corrupt. I don't know > exactly how to fix that. Maybe inspect the superclass of > PRSearchWidget and see if there is anything wrong with the subclass > declaration? If I go up one to it's superclass (PRStructuresWidget) and 'show hierarchy' there are two PRSearchWidget shown: PRSearchWidget #('searchText' 'items') PRSearchWidget #('searchText') somehow PRSearchWidget #('searchText') got in there. I can only assume that it's an older definition. I don't know how to un-reference it (if that's the right term in this case.) -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From damien.cassou at gmail.com Sun Feb 25 14:04:33 2007 From: damien.cassou at gmail.com (Damien Cassou) Date: Sun, 25 Feb 2007 14:04:33 +0100 Subject: Extracting a pier root Message-ID: <6ac749c10702250504w69b523d3s270898822c370879@mail.gmail.com> Hi, what is the best solution to extract a pier website from an image and put the extracted root into another image ? Thanks -- Damien Cassou From philippe.marschall at gmail.com Sun Feb 25 14:15:38 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Sun, 25 Feb 2007 14:15:38 +0100 Subject: Extracting a pier root In-Reply-To: <6ac749c10702250504w69b523d3s270898822c370879@mail.gmail.com> References: <6ac749c10702250504w69b523d3s270898822c370879@mail.gmail.com> Message-ID: <66666f210702250515x125e09ffg9ba49c9748cb835b@mail.gmail.com> 2007/2/25, Damien Cassou : > Hi, > > what is the best solution to extract a pier website from an image and > put the extracted root into another image ? Assuming you don't use magma: I'd say grab the kernel, file it out with ReferenceStream and file it in the other image (you'll have to add it to the instances). Maybe you'll have to nil out the mutex in the persistency instance, you'll find out if filing out will give an error. Cheers Philippe > Thanks > > -- > Damien Cassou > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From keith_hodges at yahoo.co.uk Sun Feb 25 18:00:39 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Sun, 25 Feb 2007 17:00:39 +0000 Subject: Extracting a pier root In-Reply-To: <66666f210702250515x125e09ffg9ba49c9748cb835b@mail.gmail.com> References: <6ac749c10702250504w69b523d3s270898822c370879@mail.gmail.com> <66666f210702250515x125e09ffg9ba49c9748cb835b@mail.gmail.com> Message-ID: <45E1C0B7.4030300@yahoo.co.uk> Assuming you do use magma, Create a repository and switch the persistence mechanism to backup to magma. It will perform the migration of the data into magma and then ask you to confirm. Then closing this image and opening a new image, make a new kernel, switch to PRMagmaPersistency. It will link to the existing persisted kernel and serve from there. Switching from MagmaPersistency to Null Persistency it will perform the migration of the data into memory from magma and then ask you to confirm. I am planning to move this functionality into a separate Persistency manager in the next day or so. best regards keith ___________________________________________________________ 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 norbert at hartl.name Sun Feb 25 19:50:03 2007 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 25 Feb 2007 19:50:03 +0100 Subject: Magritte and two password fields Message-ID: <1172429403.20338.57.camel@localhost> Hi, is there a smart way to have a typical password input (two textfields for comparsion) with magritte without customizing too much? thanks, Norbert From ramon.leon at allresnet.com Sun Feb 25 20:00:30 2007 From: ramon.leon at allresnet.com (Ramon Leon) Date: Sun, 25 Feb 2007 12:00:30 -0700 Subject: Magritte and two password fields In-Reply-To: <1172429403.20338.57.camel@localhost> References: <1172429403.20338.57.camel@localhost> Message-ID: <018301c7590f$387c24f0$9700a8c0@hq.allresnet.com> > Hi, > > is there a smart way to have a typical password input (two > textfields for comparison) with Magritte without customizing too much? > > thanks, > > Norbert Create two descriptions on the class, then add a multi field validation rule to the class with a container description like this... descriptionContainer ^(super descriptionContainer) addCondition: [:value | (value cache at: self descriptionPassword) = (value cache at: self descriptionPasswordMatch)] labelled: 'Passwords must match'; yourself Ramon Leon http://onsmalltalk.com From ducasse at iam.unibe.ch Sun Feb 25 20:38:35 2007 From: ducasse at iam.unibe.ch (=?ISO-8859-1?Q?st=E9phane_ducasse?=) Date: Sun, 25 Feb 2007 20:38:35 +0100 Subject: Extracting a pier root In-Reply-To: <45E1C0B7.4030300@yahoo.co.uk> References: <6ac749c10702250504w69b523d3s270898822c370879@mail.gmail.com> <66666f210702250515x125e09ffg9ba49c9748cb835b@mail.gmail.com> <45E1C0B7.4030300@yahoo.co.uk> Message-ID: Hi keith is magma stable? I got several feedback from people not really happy with magma (path with windows hardcoded, lot of changes....) On the other hand I got people really satisfied so I'm in between. so what is the state of magma dev? Stef On 25 f?vr. 07, at 18:00, Keith Hodges wrote: > Assuming you do use magma, > > Create a repository and switch the persistence mechanism to backup to > magma. It will perform the migration of the data into magma and > then ask > you to confirm. > > Then closing this image and opening a new image, make a new kernel, > switch to PRMagmaPersistency. It will link to the existing persisted > kernel and serve from there. > > Switching from MagmaPersistency to Null Persistency it will perform > the > migration of the data into memory from magma and then ask you to > confirm. > > I am planning to move this functionality into a separate Persistency > manager in the next day or so. > > best regards > > keith > > > > > ___________________________________________________________ > 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 > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From keith_hodges at yahoo.co.uk Mon Feb 26 00:15:38 2007 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Sun, 25 Feb 2007 23:15:38 +0000 Subject: Extracting a pier root In-Reply-To: References: <6ac749c10702250504w69b523d3s270898822c370879@mail.gmail.com> <66666f210702250515x125e09ffg9ba49c9748cb835b@mail.gmail.com> <45E1C0B7.4030300@yahoo.co.uk> Message-ID: <45E2189A.80404@yahoo.co.uk> st?phane ducasse wrote: > Hi keith > > is magma stable? > I got several feedback from people not really happy with magma (path > with windows hardcoded, lot of changes....) > On the other hand I got people really satisfied so I'm in between. > so what is the state of magma dev? > > Stef > Well yes I was transferring my images from windows to linux, and also uploading images to seaside hosting. The requirement to configure magma with a full path was a pain, but relatively easy to fix. Between us Chris and I have now updated magma to allow configuration to use a relative path. I haven't noticed any reliability problems with magma as yet, and my current feeling is that I would be happy to use it with my data. There is a database backup mechanism, or some form of journalling scheme could also be adopted in parallel though nothing of my data is mission critical. Chris is also very responsive to any support queries which is helpful, but it is as well to bear in mind that Magma is relatively new and is probably more subject to modifications than something which has been with us for 15 years. Having said that, now that Magma has a fully functioning query mechanism and is essentially complete in its functionality, I would expect things to have stabilised. best regards Keith ___________________________________________________________ Yahoo! Messenger - with free PC-PC calling and photo sharing. http://uk.messenger.yahoo.com From brad at sonaural.com Tue Feb 27 01:57:07 2007 From: brad at sonaural.com (Brad Fuller) Date: Mon, 26 Feb 2007 16:57:07 -0800 Subject: Pier Stylesheets and File Library Message-ID: <45E381E3.6040806@sonaural.com> Philippe Marschall wrote: > 2007/2/17, Brad Fuller : >> Looking through the various Pier documentation, I see that code has >> changed and thus there are several different explanations of how to >> change stylesheets. I want to use a different css stylesheets but I >> can't find out where to change it/them. Isn't there one place to >> point Pier to one stylesheet? >> >> BTW: for some reason, I have no style sheet at all for Pier. I don't >> know what I did, but I didn't edit any code... I must have loaded a >> new version of some package. Anyway, unless it stomped on something >> else, ifI can learn where to change the stylesheet pointer, It'd >> give me a start. > > Thanks to Christoph Wysseier Pier now supports easy custom styles with > FileLibraries. All you need to do is provide your own FileLibrary that > implements #styleCss which returns a string that is the main CSS file. > You can put all your CSS there, or in other selectors (as PierLibrary > does) or in other locations by importing the CSS files you need. > > For example if #styleCss makes > @import url(basic.css); > this means #basicCss is imported. Basic FileLibrary stuff. FileLibrary > one of the classes that actually have a comment that describes what it > does. > > In the configuration of your pier application under 'Pier' you can > select it in 'File Library'. Thanks, and in my Pier, it's set to PRPierLibrary. I'm still a bit lost about File Library, though. Let's use css as an example. My stylesheets were found only if I redirected, in apache, where seaside retrieved the files: RewriteCond /path/%{REQUEST_FILENAME} !-f RewriteRule ^/(.*)$ http://localhost:9999/seaside/pier/$1 [P,L] If I remove the RewriteCond, stylesheet files are not found, (even though I also placed the same files in a sub dir of the image named seaside/files/PRPierLibrary.) (the access logs say apache is looking in /seaside/files/PRPierLibrary) If I go to seaside/config and select configure for "files" I get the listing of File Libraries, as expected. Selecting PRPierLibary lists files that are all the css files that (I thought) are pointed to. Fine, that seems to work. But, when I uploaded a file (just to see where the file would go) and check the complete server, the file is no where to be found. However, the file is retrievable from the configuration screen. I can only assume that the image swallowed it up. This is confusing. There is a class called PRPierLibrary. PRPierLibrary is also a directory name - evident because apache is looking for that directory. Also, if you go to PRPierLibrary in the configuration, the "files" are not really files. The contents of the files are actually in the methods of PRPierLibrary. So, I'm still lost on exactly where seaside is retrieving files. -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Tue Feb 27 02:05:44 2007 From: brad at sonaural.com (Brad Fuller) Date: Mon, 26 Feb 2007 17:05:44 -0800 Subject: Pier Stylesheets and File Library In-Reply-To: <45E381E3.6040806@sonaural.com> References: <45E381E3.6040806@sonaural.com> Message-ID: <45E383E8.20109@sonaural.com> Brad Fuller wrote: > Philippe Marschall wrote: > > 2007/2/17, Brad Fuller : > >> Looking through the various Pier documentation, I see that code has > >> changed and thus there are several different explanations of how to > >> change stylesheets. I want to use a different css stylesheets but I > >> can't find out where to change it/them. Isn't there one place to > >> point Pier to one stylesheet? > >> > >> BTW: for some reason, I have no style sheet at all for Pier. I don't > >> know what I did, but I didn't edit any code... I must have loaded a > >> new version of some package. Anyway, unless it stomped on something > >> else, ifI can learn where to change the stylesheet pointer, It'd > >> give me a start. > > > > Thanks to Christoph Wysseier Pier now supports easy custom styles with > > FileLibraries. All you need to do is provide your own FileLibrary that > > implements #styleCss which returns a string that is the main CSS file. > > You can put all your CSS there, or in other selectors (as PierLibrary > > does) or in other locations by importing the CSS files you need. > > > > For example if #styleCss makes > > @import url(basic.css); > > this means #basicCss is imported. Basic FileLibrary stuff. FileLibrary > > one of the classes that actually have a comment that describes what it > > does. > > > > In the configuration of your pier application under 'Pier' you can > > select it in 'File Library'. > > Thanks, and in my Pier, it's set to PRPierLibrary. > > I'm still a bit lost about File Library, though. Let's use css as an > example. My stylesheets were found only if I redirected, in apache, > where seaside retrieved the files: > > RewriteCond /path/%{REQUEST_FILENAME} !-f > RewriteRule ^/(.*)$ http://localhost:9999/seaside/pier/$1 [P,L] > > If I remove the RewriteCond, stylesheet files are not found, (even > though I also placed the same files in a sub dir of the image named > seaside/files/PRPierLibrary.) > (the access logs say apache is looking in /seaside/files/PRPierLibrary) > > If I go to seaside/config and select configure for "files" I get the > listing of File Libraries, as expected. Selecting PRPierLibary lists > files that are all the css files that (I thought) are pointed to. Fine, > that seems to work. But, when I uploaded a file (just to see where the > file would go) and check the complete server, the file is no where to be > found. However, the file is retrievable from the configuration screen. I > can only assume that the image swallowed it up. > > This is confusing. There is a class called PRPierLibrary. PRPierLibrary > is also a directory name - evident because apache is looking for that > directory. Also, if you go to PRPierLibrary in the configuration, the > "files" are not really files. The contents of the files are actually in > the methods of PRPierLibrary. > > So, I'm still lost on exactly where seaside is retrieving files. Or, I should say, that I'm lost exactly how I can configure so that files come from a directory. -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From philippe.marschall at gmail.com Tue Feb 27 13:23:44 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Tue, 27 Feb 2007 13:23:44 +0100 Subject: Pier Stylesheets and File Library In-Reply-To: <45E383E8.20109@sonaural.com> References: <45E381E3.6040806@sonaural.com> <45E383E8.20109@sonaural.com> Message-ID: <66666f210702270423w57b79395ofa1a0217bbcb788d@mail.gmail.com> 2007/2/27, Brad Fuller : > Brad Fuller wrote: > > Philippe Marschall wrote: > > > 2007/2/17, Brad Fuller : > > >> Looking through the various Pier documentation, I see that code has > > >> changed and thus there are several different explanations of how to > > >> change stylesheets. I want to use a different css stylesheets but I > > >> can't find out where to change it/them. Isn't there one place to > > >> point Pier to one stylesheet? > > >> > > >> BTW: for some reason, I have no style sheet at all for Pier. I don't > > >> know what I did, but I didn't edit any code... I must have loaded a > > >> new version of some package. Anyway, unless it stomped on something > > >> else, ifI can learn where to change the stylesheet pointer, It'd > > >> give me a start. > > > > > > Thanks to Christoph Wysseier Pier now supports easy custom styles with > > > FileLibraries. All you need to do is provide your own FileLibrary that > > > implements #styleCss which returns a string that is the main CSS file. > > > You can put all your CSS there, or in other selectors (as PierLibrary > > > does) or in other locations by importing the CSS files you need. > > > > > > For example if #styleCss makes > > > @import url(basic.css); > > > this means #basicCss is imported. Basic FileLibrary stuff. FileLibrary > > > one of the classes that actually have a comment that describes what it > > > does. > > > > > > In the configuration of your pier application under 'Pier' you can > > > select it in 'File Library'. > > > > Thanks, and in my Pier, it's set to PRPierLibrary. > > > > I'm still a bit lost about File Library, though. Let's use css as an > > example. My stylesheets were found only if I redirected, in apache, > > where seaside retrieved the files: > > > > RewriteCond /path/%{REQUEST_FILENAME} !-f > > RewriteRule ^/(.*)$ http://localhost:9999/seaside/pier/$1 [P,L] > > > > If I remove the RewriteCond, stylesheet files are not found, (even > > though I also placed the same files in a sub dir of the image named > > seaside/files/PRPierLibrary.) > > (the access logs say apache is looking in /seaside/files/PRPierLibrary) > > > > If I go to seaside/config and select configure for "files" I get the > > listing of File Libraries, as expected. Selecting PRPierLibary lists > > files that are all the css files that (I thought) are pointed to. Fine, > > that seems to work. But, when I uploaded a file (just to see where the > > file would go) and check the complete server, the file is no where to be > > found. However, the file is retrievable from the configuration screen. I > > can only assume that the image swallowed it up. > > > > This is confusing. There is a class called PRPierLibrary. PRPierLibrary > > is also a directory name - evident because apache is looking for that > > directory. Also, if you go to PRPierLibrary in the configuration, the > > "files" are not really files. The contents of the files are actually in > > the methods of PRPierLibrary. > > > > So, I'm still lost on exactly where seaside is retrieving files. > > Or, I should say, that I'm lost exactly how I can configure so that > files come from a directory. Apache a solution for experienced users who know what they are doing. The FileLibrary is a different application that does not have the /seaside/pier/ base path and instead uses /seaside/files/. You have three options: 1. rewrite http://localhost:9999/seaside/files/PRPierLibrary/main.css as well. 2. write you own file library that only contains an import to your real external css mainCss ^'@import url(/path/to/my.css)' 3. Pack all your resources into your own file library either by uploading or using one of the convenience methods in the 'adding-files' protocol on the class side. See the class comment of WAFileLibrary for more information. Cheers Philippe > -- > brad fuller > http://www.Sonaural.com/ > +1 (408) 799-6124 > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From chris at wysseier.net Tue Feb 27 14:01:25 2007 From: chris at wysseier.net (Christoph Wysseier) Date: Tue, 27 Feb 2007 14:01:25 +0100 Subject: Pier Stylesheets and File Library In-Reply-To: <45E381E3.6040806@sonaural.com> References: <45E381E3.6040806@sonaural.com> Message-ID: <45E42BA5.6040807@wysseier.net> > Thanks, and in my Pier, it's set to PRPierLibrary. > > I'm still a bit lost about File Library, though. Let's use css as an > example. My stylesheets were found only if I redirected, in apache, > where seaside retrieved the files: > > RewriteCond /path/%{REQUEST_FILENAME} !-f > RewriteRule ^/(.*)$ http://localhost:9999/seaside/pier/$1 [P,L] > > If I remove the RewriteCond, stylesheet files are not found, (even > though I also placed the same files in a sub dir of the image named > seaside/files/PRPierLibrary.) > (the access logs say apache is looking in /seaside/files/PRPierLibrary) > > If I go to seaside/config and select configure for "files" I get the > listing of File Libraries, as expected. Selecting PRPierLibary lists > files that are all the css files that (I thought) are pointed to. Fine, > that seems to work. But, when I uploaded a file (just to see where the > file would go) and check the complete server, the file is no where to be > found. However, the file is retrievable from the configuration screen. I > can only assume that the image swallowed it up. > > This is confusing. There is a class called PRPierLibrary. PRPierLibrary > is also a directory name - evident because apache is looking for that > directory. Also, if you go to PRPierLibrary in the configuration, the > "files" are not really files. The contents of the files are actually in > the methods of PRPierLibrary. > > So, I'm still lost on exactly where seaside is retrieving files. # PRFileLibrary This is the standard file library of Pier. File libraries can be called using /seaside/files/FileLibraryName (in your case /seaside/files/PRFileLibrary). There is an interface to upload files which are then encoded within the PRFileLibrary class in the image! Like this you static files (css, images) are saved _within_ the image and not on the filesystem. The files are available using /seaside/files/PRFileLibrary/filename.zzz... By the way, if you would like to have your own stylesheets, you should create your own file library (subclass of WAFileLibrary) and upload your files there. Otherwise your changes will be overwritten when loading a new Pier version! # Apache Reverse Proxy You are using Apache as Reverse Proxy using the rewrite engine (mod_rewrite). Every request to apache is processed and if the RewriteCond matches the RewriteRule is executed. Like this, a request is forwarded to the Seaside image which delivers the content back to apache which returns the content to the user. In your example you are rewriting URLs only to /seaside/pier. Everthing else is not rewrited and Apache tries to get it from the standard directory. Like this, /seaside/files (which is part of the seaside image) can never be accessed using the reverse proxy! As an example the following rules may work for you: RewriteCond %{REQUEST_URI} ^/seaside/files/(.*)$ RewriteRule ^/(.*)$ http://localhost:9999/seaside/files/$1 [P,L] RewriteCond %{REQUEST_URI} ^/seaside/pier/(.*)$ RewriteRule ^/(.*)$ http://localhost:9999/seaside/pier/$1 [P,L] Read the manual at apache.org for more informations on Rewrite Rules and Reverse Proxies: http://httpd.apache.org/docs/1.3/mod/mod_rewrite.html http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html http://httpd.apache.org/docs/2.0/mod/mod_proxy.html Cheers, Chris From brad at sonaural.com Tue Feb 27 16:53:39 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 27 Feb 2007 07:53:39 -0800 Subject: Pier Stylesheets and File Library In-Reply-To: <45E42BA5.6040807@wysseier.net> References: <45E381E3.6040806@sonaural.com> <45E42BA5.6040807@wysseier.net> Message-ID: <45E45403.2010901@sonaural.com> Christoph Wysseier wrote: >> Thanks, and in my Pier, it's set to PRPierLibrary. >> >> I'm still a bit lost about File Library, though. Let's use css as an >> example. My stylesheets were found only if I redirected, in apache, >> where seaside retrieved the files: >> >> RewriteCond /path/%{REQUEST_FILENAME} !-f >> RewriteRule ^/(.*)$ http://localhost:9999/seaside/pier/$1 [P,L] > > >> If I remove the RewriteCond, stylesheet files are not found, (even >> though I also placed the same files in a sub dir of the image named >> seaside/files/PRPierLibrary.) >> (the access logs say apache is looking in /seaside/files/PRPierLibrary) >> >> If I go to seaside/config and select configure for "files" I get the >> listing of File Libraries, as expected. Selecting PRPierLibary lists >> files that are all the css files that (I thought) are pointed to. Fine, >> that seems to work. But, when I uploaded a file (just to see where the >> file would go) and check the complete server, the file is no where to be >> found. However, the file is retrievable from the configuration screen. I >> can only assume that the image swallowed it up. >> >> This is confusing. There is a class called PRPierLibrary. PRPierLibrary >> is also a directory name - evident because apache is looking for that >> directory. Also, if you go to PRPierLibrary in the configuration, the >> "files" are not really files. The contents of the files are actually in >> the methods of PRPierLibrary. >> >> So, I'm still lost on exactly where seaside is retrieving files. > > # PRFileLibrary > This is the standard file library of Pier. File libraries can be called > using /seaside/files/FileLibraryName (in your case > /seaside/files/PRFileLibrary). There is an interface to upload files > which are then encoded within the PRFileLibrary class in the image! Like > this you static files (css, images) are saved _within_ the image and not > on the filesystem. The files are available using > /seaside/files/PRFileLibrary/filename.zzz... Yeah... I saw that my images were stuffed into my library I made. The doc should probably be clarified as it says you can upload a file to the directory the user has created using the web interface (by selecting configure by files) > > By the way, if you would like to have your own stylesheets, you should > create your own file library (subclass of WAFileLibrary) and upload your > files there. Otherwise your changes will be overwritten when loading a > new Pier version! > > # Apache Reverse Proxy > You are using Apache as Reverse Proxy using the rewrite engine > (mod_rewrite). Every request to apache is processed and if the > RewriteCond matches the RewriteRule is executed. Like this, a request is > forwarded to the Seaside image which delivers the content back to apache > which returns the content to the user. > In your example you are rewriting URLs only to /seaside/pier. Everthing > else is not rewrited and Apache tries to get it from the standard > directory. Like this, /seaside/files (which is part of the seaside > image) can never be accessed using the reverse proxy! As an example the > following rules may work for you: > > RewriteCond %{REQUEST_URI} ^/seaside/files/(.*)$ > RewriteRule ^/(.*)$ http://localhost:9999/seaside/files/$1 [P,L] > > RewriteCond %{REQUEST_URI} ^/seaside/pier/(.*)$ > RewriteRule ^/(.*)$ http://localhost:9999/seaside/pier/$1 [P,L] > > Read the manual at apache.org for more informations on Rewrite Rules and > Reverse Proxies: > http://httpd.apache.org/docs/1.3/mod/mod_rewrite.html > http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html > http://httpd.apache.org/docs/2.0/mod/mod_proxy.html > > Cheers, Chris Thanks Chris for the help! I appreciate it! brad From brad at sonaural.com Tue Feb 27 16:57:50 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 27 Feb 2007 07:57:50 -0800 Subject: Pier Stylesheets and File Library In-Reply-To: <66666f210702270423w57b79395ofa1a0217bbcb788d@mail.gmail.com> References: <45E381E3.6040806@sonaural.com> <45E383E8.20109@sonaural.com> <66666f210702270423w57b79395ofa1a0217bbcb788d@mail.gmail.com> Message-ID: <45E454FE.6070609@sonaural.com> Philippe Marschall wrote: > 2007/2/27, Brad Fuller : >> Brad Fuller wrote: >>> Philippe Marschall wrote: >>> > 2007/2/17, Brad Fuller : >>> >> Looking through the various Pier documentation, I see that code has >>> >> changed and thus there are several different explanations of how to >>> >> change stylesheets. I want to use a different css stylesheets but I >>> >> can't find out where to change it/them. Isn't there one place to >>> >> point Pier to one stylesheet? >>> >> >>> >> BTW: for some reason, I have no style sheet at all for Pier. I don't >>> >> know what I did, but I didn't edit any code... I must have loaded a >>> >> new version of some package. Anyway, unless it stomped on something >>> >> else, ifI can learn where to change the stylesheet pointer, It'd >>> >> give me a start. >>> > >>> > Thanks to Christoph Wysseier Pier now supports easy custom styles with >>> > FileLibraries. All you need to do is provide your own FileLibrary that >>> > implements #styleCss which returns a string that is the main CSS file. >>> > You can put all your CSS there, or in other selectors (as PierLibrary >>> > does) or in other locations by importing the CSS files you need. >>> > >>> > For example if #styleCss makes >>> > @import url(basic.css); >>> > this means #basicCss is imported. Basic FileLibrary stuff. FileLibrary >>> > one of the classes that actually have a comment that describes what it >>> > does. >>> > >>> > In the configuration of your pier application under 'Pier' you can >>> > select it in 'File Library'. >>> >>> Thanks, and in my Pier, it's set to PRPierLibrary. >>> >>> I'm still a bit lost about File Library, though. Let's use css as an >>> example. My stylesheets were found only if I redirected, in apache, >>> where seaside retrieved the files: >>> >>> RewriteCond /path/%{REQUEST_FILENAME} !-f >>> RewriteRule ^/(.*)$ http://localhost:9999/seaside/pier/$1 [P,L] >>> >>> If I remove the RewriteCond, stylesheet files are not found, (even >>> though I also placed the same files in a sub dir of the image named >>> seaside/files/PRPierLibrary.) >>> (the access logs say apache is looking in /seaside/files/PRPierLibrary) >>> >>> If I go to seaside/config and select configure for "files" I get the >>> listing of File Libraries, as expected. Selecting PRPierLibary lists >>> files that are all the css files that (I thought) are pointed to. Fine, >>> that seems to work. But, when I uploaded a file (just to see where the >>> file would go) and check the complete server, the file is no where to be >>> found. However, the file is retrievable from the configuration screen. I >>> can only assume that the image swallowed it up. >>> >>> This is confusing. There is a class called PRPierLibrary. PRPierLibrary >>> is also a directory name - evident because apache is looking for that >>> directory. Also, if you go to PRPierLibrary in the configuration, the >>> "files" are not really files. The contents of the files are actually in >>> the methods of PRPierLibrary. >>> >>> So, I'm still lost on exactly where seaside is retrieving files. >> Or, I should say, that I'm lost exactly how I can configure so that >> files come from a directory. > > Apache a solution for experienced users who know what they are doing. > > The FileLibrary is a different application that does not have the > /seaside/pier/ base path and instead uses /seaside/files/. Yeah, I understood that. I created my own FileLibrary. > > You have three options: > 1. rewrite http://localhost:9999/seaside/files/PRPierLibrary/main.css as well. > 2. write you own file library that only contains an import to your > real external css > > mainCss > ^'@import url(/path/to/my.css)' That's what I wanted to know! Thanks! > > 3. Pack all your resources into your own file library either by > uploading or using one of the convenience methods in the > 'adding-files' protocol on the class side. See the class comment of > WAFileLibrary for more information. That's one of the problems,the comments were unclear for me. Thanks for your help, Philippe! From brad at sonaural.com Tue Feb 27 21:42:09 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 27 Feb 2007 12:42:09 -0800 Subject: Managing Pier Users Message-ID: <45E497A1.3080309@sonaural.com> I'd like to learn how you manage users in Pier. Since Pier is a Wiki/CMS, allowing users to register, login/logout, and managing their pages/assets is a big part of any Wiki or CMS. My plan was to create a "register" component and a "managing users" component for Pier, but I bet this has already been done - extending the Unix Security component. How do you manage users in Pier? -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From brad at sonaural.com Tue Feb 27 22:05:28 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 27 Feb 2007 13:05:28 -0800 Subject: Pier Configuration Panel changed? Message-ID: <45E49D18.7000504@sonaural.com> I just updated to Lukas latest (you updated the tab for your stylesheet) and now the "File Library" (I think that's what it was called) under Pier in the configuration is gone. This is where the "file library" was set. I had it set to my library. Let me tell you what happens: If I use PRPierLibrary only under "Libraries" (at the top), no problem with css. If I remove PRPierLibrary and use my own MyLibrary (which is just a copy of PRPierLibrary) no css file. This worked before with MyLibrary. -- brad fuller http://www.Sonaural.com/ +1 (408) 799-6124 From renggli at iam.unibe.ch Tue Feb 27 22:09:08 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 27 Feb 2007 22:09:08 +0100 Subject: Managing Pier Users In-Reply-To: <45E497A1.3080309@sonaural.com> References: <45E497A1.3080309@sonaural.com> Message-ID: <8AF78459-8250-434F-8640-039FA7BE8703@iam.unibe.ch> > I'd like to learn how you manage users in Pier. Since Pier is a > Wiki/CMS, allowing users to register, login/logout, and managing > their pages/assets is a big part of any Wiki or CMS. > > My plan was to create a "register" component and a "managing users" > component for Pier, but I bet this has already been done - > extending the Unix Security component. > > How do you manage users in Pier? Yes, there are a couple of components in the Pier Unix Security package that do exactly that. In fact on all my running pier instances I have created a protected page that embeds these components as part of the contents. The wiki syntax of this page looks like: !Users +users+ !Groups +groups+ !System +system+ The resulting page (when logged in as admin) then looks like: http://www.lukas-renggli.ch/dropbox/security.png As you see the functionality is not very sophisticated, but it basically allows to add, edit, remove users and groups. Moreover the component provide access to some other important administrative tasks. I successfully managed with this interface a lecture with 25 students, 3 assistants, and groups of 5 people each. You can see this instance at ese.unibe.ch. Everybody had a personal page (read/write only the personal page, not visible for people outside). Then every group had a page (read/write in the group, visible for people outside). Moreover we had an administrative area (only assistants could read/write) and the exercises for the exercises (read/write for assistants, read-only for students), etc. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From philippe.marschall at gmail.com Tue Feb 27 22:31:46 2007 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Tue, 27 Feb 2007 22:31:46 +0100 Subject: Pier Configuration Panel changed? In-Reply-To: <45E49D18.7000504@sonaural.com> References: <45E49D18.7000504@sonaural.com> Message-ID: <66666f210702271331q5d057ea4g124b2af6666b642a@mail.gmail.com> 2007/2/27, Brad Fuller : > I just updated to Lukas latest (you updated the tab for your stylesheet) > and now the "File Library" (I think that's what it was called) under > Pier in the configuration is gone. This is where the "file library" was > set. I had it set to my library. > > Let me tell you what happens: If I use PRPierLibrary only under > "Libraries" (at the top), no problem with css. If I remove > PRPierLibrary and use my own MyLibrary (which is just a copy of > PRPierLibrary) no css file. > > This worked before with MyLibrary. It looks as this has changed since FileLibrary can now automatically include files. PRPierLibrary is now a library like all the other under the 'Libraries' section, you need to remove it and add your file library. Additionally in your main file library (MyLibrary) you need to add the following method selectorsToInclude ^ #( styleCss ) or alternatively an array of the selectors of your main css files. Cheers Philippe > -- > brad fuller > http://www.Sonaural.com/ > +1 (408) 799-6124 > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > From brad at sonaural.com Tue Feb 27 22:46:40 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 27 Feb 2007 13:46:40 -0800 Subject: Pier Configuration Panel changed? In-Reply-To: <66666f210702271331q5d057ea4g124b2af6666b642a@mail.gmail.com> References: <45E49D18.7000504@sonaural.com> <66666f210702271331q5d057ea4g124b2af6666b642a@mail.gmail.com> Message-ID: <45E4A6C0.1070806@sonaural.com> Philippe Marschall wrote: > 2007/2/27, Brad Fuller : >> I just updated to Lukas latest (you updated the tab for your stylesheet) >> and now the "File Library" (I think that's what it was called) under >> Pier in the configuration is gone. This is where the "file library" was >> set. I had it set to my library. >> >> Let me tell you what happens: If I use PRPierLibrary only under >> "Libraries" (at the top), no problem with css. If I remove >> PRPierLibrary and use my own MyLibrary (which is just a copy of >> PRPierLibrary) no css file. >> >> This worked before with MyLibrary. > > It looks as this has changed since FileLibrary can now automatically > include files. ah... I knew there was a good reason. > PRPierLibrary is now a library like all the other under > the 'Libraries' section, you need to remove it and add your file > library. > > Additionally in your main file library (MyLibrary) you need to add the > following method > selectorsToInclude > ^ #( styleCss ) > > or alternatively an array of the selectors of your main css files. Yay, my styles are back. Much obliged, Philippe! From brad at sonaural.com Tue Feb 27 23:22:00 2007 From: brad at sonaural.com (Brad Fuller) Date: Tue, 27 Feb 2007 14:22:00 -0800 Subject: Managing Pier Users In-Reply-To: <8AF78459-8250-434F-8640-039FA7BE8703@iam.unibe.ch> References: <45E497A1.3080309@sonaural.com> <8AF78459-8250-434F-8640-039FA7BE8703@iam.unibe.ch> Message-ID: <45E4AF08.4080207@sonaural.com> Lukas Renggli wrote: >> I'd like to learn how you manage users in Pier. Since Pier is a >> Wiki/CMS, allowing users to register, login/logout, and managing >> their pages/assets is a big part of any Wiki or CMS. >> >> My plan was to create a "register" component and a "managing users" >> component for Pier, but I bet this has already been done - >> extending the Unix Security component. >> >> How do you manage users in Pier? > > Yes, there are a couple of components in the Pier Unix Security > package that do exactly that. In fact on all my running pier > instances I have created a protected page that embeds these > components as part of the contents. > > The wiki syntax of this page looks like: > > !Users > +users+ > > !Groups > +groups+ > > !System > +system+ > > The resulting page (when logged in as admin) then looks like: > > http://www.lukas-renggli.ch/dropbox/security.png > > As you see the functionality is not very sophisticated, but it > basically allows to add, edit, remove users and groups. Moreover the > component provide access to some other important administrative tasks. > > I successfully managed with this interface a lecture with 25 > students, 3 assistants, and groups of 5 people each. You can see this > instance at ese.unibe.ch. Everybody had a personal page (read/write > only the personal page, not visible for people outside). Then every > group had a page (read/write in the group, visible for people > outside). Moreover we had an administrative area (only assistants > could read/write) and the exercises for the exercises (read/write for > assistants, read-only for students), etc. Thanks for making the time to create the visual. That's very helpful. How about the rest of you? What are you doing for user management and automatically registering users? BTW Lukas, do you manually register users? From renggli at iam.unibe.ch Tue Feb 27 23:25:37 2007 From: renggli at iam.unibe.ch (Lukas Renggli) Date: Tue, 27 Feb 2007 23:25:37 +0100 Subject: Managing Pier Users In-Reply-To: <45E4AF08.4080207@sonaural.com> References: <45E497A1.3080309@sonaural.com> <8AF78459-8250-434F-8640-039FA7BE8703@iam.unibe.ch> <45E4AF08.4080207@sonaural.com> Message-ID: <7EBD9E30-0511-4A86-A809-D01A3DF99741@iam.unibe.ch> > How about the rest of you? What are you doing for user management and > automatically registering users? > > BTW Lukas, do you manually register users? I wrote a little Seaside/Magritte component where the students had to register. This component also created their personal page, subscribed them to the lecture mailing list and collected all the relevant data. The groups were created and managed during the course trough the interface I showed in the screenshot. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch