From rdrvr.biz at gmail.com Sun Mar 1 01:28:34 2009 From: rdrvr.biz at gmail.com (David Farber) Date: Sat, 28 Feb 2009 17:28:34 -0700 Subject: Direct login Message-ID: I would like to have a static link that points directly to a login page (i.e. http://mydomain.com/login). How can I make a url execute a command (in this case PRLogin) directly? Thanks, David ---- 1 Squeak/Seaside/Pier site deployed From v.krishnakumar at gmail.com Sun Mar 1 03:46:45 2009 From: v.krishnakumar at gmail.com (Krishna) Date: Sun, 1 Mar 2009 08:16:45 +0530 Subject: do you have a pier? In-Reply-To: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch> References: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch> Message-ID: Hi, http://scriptek.co.in Cheers, --Krishna On Sun, Mar 1, 2009 at 12:59 AM, Tudor Girba wrote: > > Hi, > > We would like to fill the list of Pier installations from: > http://www.piercms.com/seaside/doc/examples > > Thus, we kindly ask you to let us know if you have Pier installation somewhere publicly so that we can link to it. > > Thanks, > Doru > > -- > www.tudorgirba.com > > "Problem solving should be concentrated on describing > the problem in a way that is relevant for the solution." > > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- I love deadlines. I like the whooshing sound they make as they fly by. ? ?-- Douglas Adams From renggli at gmail.com Sun Mar 1 08:43:37 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 1 Mar 2009 08:43:37 +0100 Subject: Direct login In-Reply-To: References: Message-ID: <67628d690902282343k6b34e270uee39ff02111d12ed@mail.gmail.com> > I would like to have a static link that points directly to a login page > (i.e. http://mydomain.com/login). ?How can I make a url execute a command > (in this case PRLogin) directly? http://mydomain.com/?command=PULogin Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch From girba at iam.unibe.ch Sun Mar 1 09:43:25 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Sun, 1 Mar 2009 09:43:25 +0100 Subject: do you have a pier? In-Reply-To: References: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch> Message-ID: <002722F9-93F5-4F64-B665-59F8C1C3D4F7@iam.unibe.ch> Thanks. I added it to our list. Cheers, Doru On 1 Mar 2009, at 03:46, Krishna wrote: > Hi, > > http://scriptek.co.in > > Cheers, > --Krishna > > On Sun, Mar 1, 2009 at 12:59 AM, Tudor Girba > wrote: >> >> Hi, >> >> We would like to fill the list of Pier installations from: >> http://www.piercms.com/seaside/doc/examples >> >> Thus, we kindly ask you to let us know if you have Pier >> installation somewhere publicly so that we can link to it. >> >> Thanks, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Problem solving should be concentrated on describing >> the problem in a way that is relevant for the solution." >> >> >> >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > -- > I love deadlines. I like the whooshing sound > they make as they fly by. > -- Douglas Adams > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- www.tudorgirba.com "When people care, great things can happen." From norbert at hartl.name Sun Mar 1 14:23:49 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 01 Mar 2009 14:23:49 +0100 Subject: CSS namespaces In-Reply-To: References: <1235840376.15861.7.camel@cineflux> Message-ID: <1235913829.29544.14.camel@cineflux> On Sat, 2009-02-28 at 20:25 +0100, Tudor Girba wrote: > Hi Norbert, > > The default look and feel is based on the blueprint css framework. > This is provided via the PRBlueprintLibrary library. This framework is > a generic one and it mostly provides css classes for laying out the > pages into columns. It also provides some default styles for basic > html tags like textarea or input which is what gets eventually used > for editing pier. See the project page for more details: > http://code.google.com/p/blueprintcss/ > > The CSS that is specific to the look and feel of the default webpage > is available to you via the Edit Design command. This is where .footer > and .header is defined. So, you have complete control over the look > and feel without removing the libraries. The provided css features > some commented to point out where the large parts out. So, all you > have to replace the Pier css (or part of it) with your css in the > provided area and to modify the template accordingly. > > Is this helpful? Not really. I have to investigate this somewhat deeper. I understand what you are trying to say. But in my case it is different. If I have the libraries loaded and in "edit design" the css removed completely the design of my page is broken. So there are things that conflict. I'm not that good in css but I hope I'll be able to figure it out. I even did a dummy component inside the page that does updateRoot: to be sure mine is the last loaded. Btw. some trivial things to note: If you try to remove the css in "edit design" completely you get an MessageNotUnderstood: UndefinedObject>>asByteArray And you have to make sure that SULibrary is added before PRJavascriptSupport. Norbert > > On 28 Feb 2009, at 17:59, Norbert Hartl wrote: > > > While testing how hard it will be to bring my site > > into pier I discovered some css class clashes. For > > people it is quite normal to assign classes like > > header, footer and the like. > > > > In my opinion a cms like pier should try to step > > out of the way of any usage conflict. Therefor I > > would propose to namespace the css classes. A > > pr_header, pr_footer will do I think. > > > > Or do I missunderstand something completely? For me > > it was not possible to reconstruct our layout without > > haveing to remove all librares for the application. But > > then it is tedious to work with pier as the edit boxes > > and stuff are too small. > > > > What is the best approach to bring in the own developed > > design and having pier still functioning? > > > > thanks, > > > > Norbert > > > > > > > > _______________________________________________ > > SmallWiki, Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > -- > www.tudorgirba.com > > "Being happy is a matter of choice." > > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From girba at iam.unibe.ch Sun Mar 1 16:37:19 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Sun, 1 Mar 2009 16:37:19 +0100 Subject: CSS namespaces In-Reply-To: <1235913829.29544.14.camel@cineflux> References: <1235840376.15861.7.camel@cineflux> <1235913829.29544.14.camel@cineflux> Message-ID: Hi Norbert, My answers are inlined below. >> The default look and feel is based on the blueprint css framework. >> This is provided via the PRBlueprintLibrary library. This framework >> is >> a generic one and it mostly provides css classes for laying out the >> pages into columns. It also provides some default styles for basic >> html tags like textarea or input which is what gets eventually used >> for editing pier. See the project page for more details: >> http://code.google.com/p/blueprintcss/ >> >> The CSS that is specific to the look and feel of the default webpage >> is available to you via the Edit Design command. This is >> where .footer >> and .header is defined. So, you have complete control over the look >> and feel without removing the libraries. The provided css features >> some commented to point out where the large parts out. So, all you >> have to replace the Pier css (or part of it) with your css in the >> provided area and to modify the template accordingly. >> >> Is this helpful? > > Not really. I have to investigate this somewhat deeper. I understand > what you are trying to say. But in my case it is different. If I > have the libraries loaded and in "edit design" the css removed > completely the design of my page is broken. So there are things that > conflict. I'm not that good in css but I hope I'll be able to figure > it out. I even did a dummy component inside the page that does > updateRoot: to be sure mine is the last loaded. Hmm, then it seems I do not understand your situation. Let's try to clarify it a bit. When you say broken, what exactly do you mean? Of course that the layout and colors are not going to be the same, but the forms will still have proper dimensions, which is what seemed to have spawned the first problem. The last to get loaded is the css in Edit Design. So, why is it not enough to add your definitions at the end of that file? Usually a css comes with an html template. In this case, you would have to also change the structure of your environment anyway, and then it would fit with your custom css definition. And as the basic functionality of Pier does not depend on the css that is in Edit Design, you should not have a problem with that. > Btw. some trivial things to note: > > If you try to remove the css in "edit design" completely you get an > MessageNotUnderstood: UndefinedObject>>asByteArray Thanks for reporting, I added an issue here: http://code.google.com/p/pier/issues/detail?id=79 > And you have to make sure that SULibrary is added before > PRJavascriptSupport. I am not sure I understand this. Why do we have to make this sure? In fact, you do not need SULibrary at all, except for debugging seaside behavior. As for PRJavascriptSupport, Lukas has removed all dependencies to the Prototype and Scriptaculous, so this Library will not be needed either. Cheers, Doru > Norbert > >> >> On 28 Feb 2009, at 17:59, Norbert Hartl wrote: >> >>> While testing how hard it will be to bring my site >>> into pier I discovered some css class clashes. For >>> people it is quite normal to assign classes like >>> header, footer and the like. >>> >>> In my opinion a cms like pier should try to step >>> out of the way of any usage conflict. Therefor I >>> would propose to namespace the css classes. A >>> pr_header, pr_footer will do I think. >>> >>> Or do I missunderstand something completely? For me >>> it was not possible to reconstruct our layout without >>> haveing to remove all librares for the application. But >>> then it is tedious to work with pier as the edit boxes >>> and stuff are too small. >>> >>> What is the best approach to bring in the own developed >>> design and having pier still functioning? >>> >>> thanks, >>> >>> Norbert >>> >>> >>> >>> _______________________________________________ >>> SmallWiki, Magritte, Pier and Related Tools ... >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> >> -- >> www.tudorgirba.com >> >> "Being happy is a matter of choice." >> >> >> >> >> _______________________________________________ >> 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 -- www.tudorgirba.com "Obvious things are difficult to teach." From norbert at hartl.name Sun Mar 1 16:55:33 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 01 Mar 2009 16:55:33 +0100 Subject: CSS namespaces In-Reply-To: References: <1235840376.15861.7.camel@cineflux> <1235913829.29544.14.camel@cineflux> Message-ID: <1235922933.29544.44.camel@cineflux> On Sun, 2009-03-01 at 16:37 +0100, Tudor Girba wrote: > Hi Norbert, > > My answers are inlined below. > > >> The default look and feel is based on the blueprint css framework. > >> This is provided via the PRBlueprintLibrary library. This framework > >> is > >> a generic one and it mostly provides css classes for laying out the > >> pages into columns. It also provides some default styles for basic > >> html tags like textarea or input which is what gets eventually used > >> for editing pier. See the project page for more details: > >> http://code.google.com/p/blueprintcss/ > >> > >> The CSS that is specific to the look and feel of the default webpage > >> is available to you via the Edit Design command. This is > >> where .footer > >> and .header is defined. So, you have complete control over the look > >> and feel without removing the libraries. The provided css features > >> some commented to point out where the large parts out. So, all you > >> have to replace the Pier css (or part of it) with your css in the > >> provided area and to modify the template accordingly. > >> > >> Is this helpful? > > > > Not really. I have to investigate this somewhat deeper. I understand > > what you are trying to say. But in my case it is different. If I > > have the libraries loaded and in "edit design" the css removed > > completely the design of my page is broken. So there are things that > > conflict. I'm not that good in css but I hope I'll be able to figure > > it out. I even did a dummy component inside the page that does > > updateRoot: to be sure mine is the last loaded. > > Hmm, then it seems I do not understand your situation. Let's try to > clarify it a bit. > > When you say broken, what exactly do you mean? Of course that the > layout and colors are not going to be the same, but the forms will > still have proper dimensions, which is what seemed to have spawned the > first problem. We have a layout that displays green header that spawns the whole browser width. In the header there is from left to right: a logo, navigation links, an orange box and a search field. As soon as I include the blueprint stuff the header gets a vertical offset (there is white space between the browser top and the header). The logo and navigation links are displayed correct but the orange box and search field are displayed below the header. So I'm not sure if blueprint does some global stuff that interferes our layout. And I don't know what can be the cause of this. > > The last to get loaded is the css in Edit Design. So, why is it not > enough to add your definitions at the end of that file? > > Usually a css comes with an html template. In this case, you would > have to also change the structure of your environment anyway, and then > it would fit with your custom css definition. And as the basic > functionality of Pier does not depend on the css that is in Edit > Design, you should not have a problem with that. > I tested all of this by changing the enviroment to include only my stuff and the css as well. I checked with the current markup we produce in the standalone application. Beside the css classes pier puts in the body element it is the same. Only the existance of blueprint changes the effect. But I think I have to boil this down myself. > > > Btw. some trivial things to note: > > > > If you try to remove the css in "edit design" completely you get an > > MessageNotUnderstood: UndefinedObject>>asByteArray > > Thanks for reporting, I added an issue here: > http://code.google.com/p/pier/issues/detail?id=79 > > > And you have to make sure that SULibrary is added before > > PRJavascriptSupport. > > I am not sure I understand this. Why do we have to make this sure? In > fact, you do not need SULibrary at all, except for debugging seaside > behavior. As for PRJavascriptSupport, Lukas has removed all > dependencies to the Prototype and Scriptaculous, so this Library will > not be needed either. > Well, line 1 of PRJavascriptSupport>>pierJs says Event.observe(window, "load", function() { So I get an Event.observe is not a function if the SULibrary is not preceeding the PRJavascriptSupport in the application settings. Norbert > > > Norbert > > > >> > >> On 28 Feb 2009, at 17:59, Norbert Hartl wrote: > >> > >>> While testing how hard it will be to bring my site > >>> into pier I discovered some css class clashes. For > >>> people it is quite normal to assign classes like > >>> header, footer and the like. > >>> > >>> In my opinion a cms like pier should try to step > >>> out of the way of any usage conflict. Therefor I > >>> would propose to namespace the css classes. A > >>> pr_header, pr_footer will do I think. > >>> > >>> Or do I missunderstand something completely? For me > >>> it was not possible to reconstruct our layout without > >>> haveing to remove all librares for the application. But > >>> then it is tedious to work with pier as the edit boxes > >>> and stuff are too small. > >>> > >>> What is the best approach to bring in the own developed > >>> design and having pier still functioning? > >>> > >>> thanks, > >>> > >>> Norbert > >>> > >>> > >>> > >>> _______________________________________________ > >>> SmallWiki, Magritte, Pier and Related Tools ... > >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > >> > >> -- > >> www.tudorgirba.com > >> > >> "Being happy is a matter of choice." > >> > >> > >> > >> > >> _______________________________________________ > >> 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 > > -- > www.tudorgirba.com > > "Obvious things are difficult to teach." > > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at gmail.com Sun Mar 1 17:55:13 2009 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 1 Mar 2009 17:55:13 +0100 Subject: CSS namespaces In-Reply-To: <1235922933.29544.44.camel@cineflux> References: <1235840376.15861.7.camel@cineflux> <1235913829.29544.14.camel@cineflux> <1235922933.29544.44.camel@cineflux> Message-ID: <67628d690903010855k2dff9083yed390c85e69607d8@mail.gmail.com> > Well, line 1 of PRJavascriptSupport>>pierJs says > > Event.observe(window, "load", function() { > > So I get an Event.observe is not a function if the SULibrary is > not preceeding the PRJavascriptSupport in the application settings. Load the latest version of Pier-Seaside and Pier-EditorEnh, they do not depend on the Prototype and script.aculo.us JavaScript libraries anymore. The only thing that requires SULibrary is the autocompleted search widget. If you don't use it, you don't need to include those large libraries anymore. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From norbert at hartl.name Sun Mar 1 18:31:06 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 01 Mar 2009 18:31:06 +0100 Subject: CSS namespaces In-Reply-To: References: <1235840376.15861.7.camel@cineflux> <1235913829.29544.14.camel@cineflux> Message-ID: <1235928666.29544.53.camel@cineflux> On Sun, 2009-03-01 at 16:37 +0100, Tudor Girba wrote: > Hi Norbert, > > My answers are inlined below. > > >> The default look and feel is based on the blueprint css framework. > >> This is provided via the PRBlueprintLibrary library. This framework > >> is > >> a generic one and it mostly provides css classes for laying out the > >> pages into columns. It also provides some default styles for basic > >> html tags like textarea or input which is what gets eventually used > >> for editing pier. See the project page for more details: > >> http://code.google.com/p/blueprintcss/ > >> > >> The CSS that is specific to the look and feel of the default webpage > >> is available to you via the Edit Design command. This is > >> where .footer > >> and .header is defined. So, you have complete control over the look > >> and feel without removing the libraries. The provided css features > >> some commented to point out where the large parts out. So, all you > >> have to replace the Pier css (or part of it) with your css in the > >> provided area and to modify the template accordingly. > >> > >> Is this helpful? > > > > Not really. I have to investigate this somewhat deeper. I understand > > what you are trying to say. But in my case it is different. If I > > have the libraries loaded and in "edit design" the css removed > > completely the design of my page is broken. So there are things that > > conflict. I'm not that good in css but I hope I'll be able to figure > > it out. I even did a dummy component inside the page that does > > updateRoot: to be sure mine is the last loaded. > > Hmm, then it seems I do not understand your situation. Let's try to > clarify it a bit. > > When you say broken, what exactly do you mean? Of course that the > layout and colors are not going to be the same, but the forms will > still have proper dimensions, which is what seemed to have spawned the > first problem. > Hi Tudor, I think I found the cause of the problem. It has to do with the precedence of css selectors. We had some styles like * { margin: 0px; } which is really not a good idea. Any other that does the same a little more precise will win out. So we are the root cause of the problem. But then I also do not understand why blueprint is defining globals, e.g. body { line-height: 1.5; } I find this too general. But thanks for your help, Norbert From keith_hodges at yahoo.co.uk Sun Mar 1 18:39:55 2009 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Sun, 01 Mar 2009 17:39:55 +0000 Subject: CSS namespaces In-Reply-To: <1235928666.29544.53.camel@cineflux> References: <1235840376.15861.7.camel@cineflux> <1235913829.29544.14.camel@cineflux> <1235928666.29544.53.camel@cineflux> Message-ID: <49AAC86B.2050408@yahoo.co.uk> > > which is really not a good idea. Any other that does the same a little > more precise will win out. So we are the root cause of the problem. > But then I also do not understand why blueprint is defining globals, > e.g. > > body { > line-height: 1.5; > } > Blueprint is simply trying to set a common baselie between browsers Keith From p3anoman at gmail.com Sun Mar 1 18:57:36 2009 From: p3anoman at gmail.com (John M) Date: Sun, 1 Mar 2009 12:57:36 -0500 Subject: CSS namespaces In-Reply-To: <49AAC86B.2050408@yahoo.co.uk> References: <1235840376.15861.7.camel@cineflux> <1235913829.29544.14.camel@cineflux> <1235928666.29544.53.camel@cineflux> <49AAC86B.2050408@yahoo.co.uk> Message-ID: <40f637ec0903010957ge7637fcv52b110418372606a@mail.gmail.com> You can always edit blueprint.css in the image. I changed mine to 1.25em On Sun, Mar 1, 2009 at 12:39 PM, Keith Hodges wrote: > > > > > which is really not a good idea. Any other that does the same a little > > more precise will win out. So we are the root cause of the problem. > > But then I also do not understand why blueprint is defining globals, > > e.g. > > > > body { > > line-height: 1.5; > > } > > > Blueprint is simply trying to set a common baselie between browsers > > Keith > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From girba at iam.unibe.ch Sun Mar 1 20:24:01 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Sun, 1 Mar 2009 20:24:01 +0100 Subject: CSS namespaces In-Reply-To: <40f637ec0903010957ge7637fcv52b110418372606a@mail.gmail.com> References: <1235840376.15861.7.camel@cineflux> <1235913829.29544.14.camel@cineflux> <1235928666.29544.53.camel@cineflux> <49AAC86B.2050408@yahoo.co.uk> <40f637ec0903010957ge7637fcv52b110418372606a@mail.gmail.com> Message-ID: <52C1D9A6-AEE2-4FD3-A41E-46027C635FD9@iam.unibe.ch> Hi, Changing the default blueprint library is not the best way. It's better to create your own library and load this after the blueprint, or directly add your definitions to the css in Pier. Like this, you can update to the latest Pier code without needing to change anything. Cheers, Doru On 1 Mar 2009, at 18:57, John M wrote: > You can always edit blueprint.css in the image. I changed mine to > 1.25em > > On Sun, Mar 1, 2009 at 12:39 PM, Keith Hodges > wrote: > > > > > which is really not a good idea. Any other that does the same a > little > > more precise will win out. So we are the root cause of the problem. > > But then I also do not understand why blueprint is defining globals, > > e.g. > > > > body { > > line-height: 1.5; > > } > > > Blueprint is simply trying to set a common baselie between browsers > > Keith > > > _______________________________________________ > 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 -- www.tudorgirba.com "Sometimes the best solution is not the best solution." From p3anoman at gmail.com Sun Mar 1 20:31:04 2009 From: p3anoman at gmail.com (John M) Date: Sun, 1 Mar 2009 14:31:04 -0500 Subject: CSS namespaces In-Reply-To: <52C1D9A6-AEE2-4FD3-A41E-46027C635FD9@iam.unibe.ch> References: <1235840376.15861.7.camel@cineflux> <1235913829.29544.14.camel@cineflux> <1235928666.29544.53.camel@cineflux> <49AAC86B.2050408@yahoo.co.uk> <40f637ec0903010957ge7637fcv52b110418372606a@mail.gmail.com> <52C1D9A6-AEE2-4FD3-A41E-46027C635FD9@iam.unibe.ch> Message-ID: <40f637ec0903011131l1bc8d133k436743527f007c37@mail.gmail.com> Good advice, thank you Doru I have also used the other two methods you mention. BTW EXCELLENT video at ESUG 2008. It made everything clear to me! I wish I would have noticed it a month ago when it was posted. Thanks also to James Robertson for providing the service. I highly recommend that you give this video prominence on the Pier site. John On Sun, Mar 1, 2009 at 2:24 PM, Tudor Girba wrote: > Hi, > > Changing the default blueprint library is not the best way. It's better to > create your own library and load this after the blueprint, or directly add > your definitions to the css in Pier. Like this, you can update to the latest > Pier code without needing to change anything. > > Cheers, > Doru > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From norbert at hartl.name Sun Mar 1 22:42:29 2009 From: norbert at hartl.name (Norbert Hartl) Date: Sun, 01 Mar 2009 22:42:29 +0100 Subject: Structure title and model acquirement Message-ID: <1235943750.29544.78.camel@cineflux> My pier setup stabilizes a bit. I was able to reproduce a few page layouts of our project and integrated some components. At the moment I really love it as most of the things I wanted worked out today. One thing that I want to change is the title of a structure. I don't want to have it as not all pages have titles and the others deal differently with something like a title. So why is the title mandatory for a structure? Is there an easy way to get rid of it? Navigating to a page, pressing edit and just integrate a component by doing +...+ is really great! But I'm asking myself what is the best way to acquire the data the component needs. As an example I have a user and the user has a list of images. I have a component that takes a list of images and displays them. In my current approach these are connected via Announcements. Whenever the user changes the image list component gets his model set to the new list of images. What is the best way to decorate a component with some functionality? thanks in advance, Norbert From keith_hodges at yahoo.co.uk Sun Mar 1 22:49:07 2009 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Sun, 01 Mar 2009 21:49:07 +0000 Subject: CSS namespaces In-Reply-To: <40f637ec0903011131l1bc8d133k436743527f007c37@mail.gmail.com> References: <1235840376.15861.7.camel@cineflux> <1235913829.29544.14.camel@cineflux> <1235928666.29544.53.camel@cineflux> <49AAC86B.2050408@yahoo.co.uk> <40f637ec0903010957ge7637fcv52b110418372606a@mail.gmail.com> <52C1D9A6-AEE2-4FD3-A41E-46027C635FD9@iam.unibe.ch> <40f637ec0903011131l1bc8d133k436743527f007c37@mail.gmail.com> Message-ID: <49AB02D3.2030402@yahoo.co.uk> John M wrote: > Good advice, thank you Doru > I have also used the other two methods you mention. > > BTW EXCELLENT video at ESUG 2008. It made everything clear to me! I > wish I would have noticed it a month ago when it was posted. > Thanks also to James Robertson for providing the service. I highly > recommend that you give this video prominence on the Pier site. > John > I am using the content with style framework myself. Keith From rdrvr.biz at gmail.com Mon Mar 2 04:00:10 2009 From: rdrvr.biz at gmail.com (David Farber) Date: Sun, 1 Mar 2009 20:00:10 -0700 Subject: Direct login In-Reply-To: <67628d690902282343k6b34e270uee39ff02111d12ed@mail.gmail.com> References: <67628d690902282343k6b34e270uee39ff02111d12ed@mail.gmail.com> Message-ID: <336FF00E-3E32-4B06-A606-66740E3DFEDB@gmail.com> On Mar 1, 2009, at 12:43 AM, Lukas Renggli wrote: >> I would like to have a static link that points directly to a login >> page >> (i.e. http://mydomain.com/login). How can I make a url execute a >> command >> (in this case PRLogin) directly? > > http://mydomain.com/?command=PULogin Yes, I know I can do that but I would really rather be able to map login (or, for that matter, potentially any command) to an arbitrary URL. David ---- 1 Squeak/Seaside/Pier site deployed From renggli at gmail.com Mon Mar 2 08:21:21 2009 From: renggli at gmail.com (Lukas Renggli) Date: Mon, 2 Mar 2009 08:21:21 +0100 Subject: Direct login In-Reply-To: <336FF00E-3E32-4B06-A606-66740E3DFEDB@gmail.com> References: <67628d690902282343k6b34e270uee39ff02111d12ed@mail.gmail.com> <336FF00E-3E32-4B06-A606-66740E3DFEDB@gmail.com> Message-ID: <67628d690903012321w64d70303w7ede237d956ba422@mail.gmail.com> >> http://mydomain.com/?command=PULogin > > Yes, I know I can do that but I would really rather be able to map login > (or, for that matter, potentially any command) to an arbitrary URL. That works on an arbitrary Pier URL, not just on the root. You just have to add '?command=PULogin'. Or do I misunderstand your question? Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at gmail.com Mon Mar 2 08:30:01 2009 From: renggli at gmail.com (Lukas Renggli) Date: Mon, 2 Mar 2009 08:30:01 +0100 Subject: Structure title and model acquirement In-Reply-To: <1235943750.29544.78.camel@cineflux> References: <1235943750.29544.78.camel@cineflux> Message-ID: <67628d690903012330n18c5c7beme5080087006ec9f4@mail.gmail.com> > One thing that I want to change is the title of a structure. > I don't want to have it as not all pages have titles and the > others deal differently with something like a title. So why > is the title mandatory for a structure? Is there an easy way > to get rid of it? Simply not displaying the title can be achieved by chaining the environment. You can also try to change the description of the title in PRStructure, but that might break parts of Pier that depend on the fact that every structure has a title. - If you want to change, replace or remove the title for your own subclasses override #descriptionTitle on the class side. - If you want to change, replace or remove the title from all structures add a class side extension method like #descriptionTitle: (that shares the same prefix, but with one argument). This method is automatically called by Magritte and allows you to change (return a modified description), replace (return a new description) or remove (return nil) the description. > Navigating to a page, pressing edit and just integrate a > component by doing +...+ is really great! But I'm asking myself > what is the best way to acquire the data the component needs. > As an example I have a user and the user has a list of images. > I have a component that takes a list of images and displays them. > In my current approach these are connected via Announcements. > Whenever the user changes the image list component gets his model > set to the new list of images. What is the best way to decorate a > component with some functionality? The settings of that component? Lukas -- Lukas Renggli http://www.lukas-renggli.ch From norbert at hartl.name Mon Mar 2 09:58:10 2009 From: norbert at hartl.name (Norbert Hartl) Date: Mon, 02 Mar 2009 09:58:10 +0100 Subject: Structure title and model acquirement In-Reply-To: <67628d690903012330n18c5c7beme5080087006ec9f4@mail.gmail.com> References: <1235943750.29544.78.camel@cineflux> <67628d690903012330n18c5c7beme5080087006ec9f4@mail.gmail.com> Message-ID: <1235984290.6197.6.camel@cineflux> On Mon, 2009-03-02 at 08:30 +0100, Lukas Renggli wrote: > > One thing that I want to change is the title of a structure. > > I don't want to have it as not all pages have titles and the > > others deal differently with something like a title. So why > > is the title mandatory for a structure? Is there an easy way > > to get rid of it? > > Simply not displaying the title can be achieved by chaining the environment. > Can you please elaborate on that? > You can also try to change the description of the title in > PRStructure, but that might break parts of Pier that depend on the > fact that every structure has a title. > > - If you want to change, replace or remove the title for your own > subclasses override #descriptionTitle on the class side. > > - If you want to change, replace or remove the title from all > structures add a class side extension method like #descriptionTitle: > (that shares the same prefix, but with one argument). This method is > automatically called by Magritte and allows you to change (return a > modified description), replace (return a new description) or remove > (return nil) the description. > I don't understand what title is used for. What is the reason that _every_ structure has to have a title? Is pier doing something special with it? Beside that I don't really care if the title is there or not as long as I'm not forced to use it. And altering pier so that it doesn't display the title is a weak option. But I'll have a look into it. Or is there a better option when I want to have a page that contains only three components without an displayed title? > > Navigating to a page, pressing edit and just integrate a > > component by doing +...+ is really great! But I'm asking myself > > what is the best way to acquire the data the component needs. > > As an example I have a user and the user has a list of images. > > I have a component that takes a list of images and displays them. > > In my current approach these are connected via Announcements. > > Whenever the user changes the image list component gets his model > > set to the new list of images. What is the best way to decorate a > > component with some functionality? > > The settings of that component? Yes, the setting that whenever something happens the component gets its model set again. I could do this with asking inside the component self session context owner images But then I'm starting bring a lot of knowledge from the outside into the component. I would rather have some glue code anywhere that does this. thanks, Norbert From renggli at gmail.com Mon Mar 2 10:49:03 2009 From: renggli at gmail.com (Lukas Renggli) Date: Mon, 2 Mar 2009 10:49:03 +0100 Subject: Structure title and model acquirement In-Reply-To: <1235984290.6197.6.camel@cineflux> References: <1235943750.29544.78.camel@cineflux> <67628d690903012330n18c5c7beme5080087006ec9f4@mail.gmail.com> <1235984290.6197.6.camel@cineflux> Message-ID: <67628d690903020149u2d1a73f8h84b719f107abee01@mail.gmail.com> >> Simply not displaying the title can be achieved by chaining the environment. >> > Can you please elaborate on that? If you use the latest template from Doru then the line

+value:structure+

adds the title. Older versions of Pier displayed the page title through the setting "Heading" in the content widget. Simply leave that empty to not emit the title. > I don't understand what title is used for. What is the reason that > _every_ structure has to have a title? Is pier doing something > special with it? Have a look at the senders of #title in Pier-Model. It is probably not essential, but there are quite a few users. > Beside that I don't really care if the title is there or not as long > as I'm not forced to use it. And altering pier so that it doesn't > display the title is a weak option. But I'll have a look into it. What I suggested does not alter Pier, it just alters the meta-model. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From rdrvr.biz at gmail.com Mon Mar 2 19:33:09 2009 From: rdrvr.biz at gmail.com (David Farber) Date: Mon, 2 Mar 2009 11:33:09 -0700 Subject: Direct login In-Reply-To: <67628d690903012321w64d70303w7ede237d956ba422@mail.gmail.com> References: <67628d690902282343k6b34e270uee39ff02111d12ed@mail.gmail.com> <336FF00E-3E32-4B06-A606-66740E3DFEDB@gmail.com> <67628d690903012321w64d70303w7ede237d956ba422@mail.gmail.com> Message-ID: On Mar 2, 2009, at 12:21 AM, Lukas Renggli wrote: >>> http://mydomain.com/?command=PULogin >> >> Yes, I know I can do that but I would really rather be able to map >> login >> (or, for that matter, potentially any command) to an arbitrary URL. > > That works on an arbitrary Pier URL, not just on the root. You just > have to add '?command=PULogin'. > > Or do I misunderstand your question? I specifically do *not* want to add '?command=PULogin' to the url. For the Pier sites that I am deploying, I do not want there to be a login link on any of the pages. There is no functionality (like wiki pages) for normal users. Only two or three administrators have logins (i.e. >0.1% of people accessing the site). Since there is no login link, I need to be able to give them a URL to be able to login and I want to give them as simple a URL as possible. In fact, the URL right now is /site/login and I have been thinking about adding an Apache rewrite rule to have /login redirect to /site/login. Does that better explain what I am trying to accomplish? Now that I'm writing this email I realize that I could just use a rewrite rule to add '?command=PULogin'--which I might go ahead and do-- but it still seems to me that it would be useful to map an arbitrary URL to a command without the '?command=' and without having to resort to Apache rewrite rules. And while we are on the subject of commands and rewrite rules, I've noticed that commands post to '/' even if they are part of a longer URL (like mydomain.com/site/login). This behavior is slightly problematic given that the default page for one of my sites is not '/' and I have a rewrite rule to redirect '/' to that default page. I had to add a 'RewriteCond %{REQUEST_METHOD} !POST' test to my rewrite rule. It would be nice if commands posted to the URL they were called from. David ---- 1 Squeak/Seaside/Pier site deployed From renggli at gmail.com Mon Mar 2 20:13:56 2009 From: renggli at gmail.com (Lukas Renggli) Date: Mon, 2 Mar 2009 20:13:56 +0100 Subject: Direct login In-Reply-To: References: <67628d690902282343k6b34e270uee39ff02111d12ed@mail.gmail.com> <336FF00E-3E32-4B06-A606-66740E3DFEDB@gmail.com> <67628d690903012321w64d70303w7ede237d956ba422@mail.gmail.com> Message-ID: <67628d690903021113v7235c7b3k22c96c57d34e319c@mail.gmail.com> > I specifically do *not* want to add '?command=PULogin' to the url. > > For the Pier sites that I am deploying, I do not want there to be a login > link on any of the pages. There is no functionality (like wiki pages) for > normal users. Only two or three administrators have logins (i.e. >0.1% of > people accessing the site). Since there is no login link, I need to be able > to give them a URL to be able to login and I want to give them as simple a > URL as possible. In fact, the URL right now is /site/login and I have been > thinking about adding an Apache rewrite rule to have /login redirect to > /site/login. > > Does that better explain what I am trying to accomplish? Yes, you could add a rewrite rule to do that. On my pages I usually use a hidden login link, so editors just have to press Ctrl+L to get to the login page (http://www.piercms.com/doc/shortcuts). If desired the login page can also be bookmarked. > Now that I'm writing this email I realize that I could just use a rewrite > rule to add '?command=PULogin'--which I might go ahead and do--but it still > seems to me that it would be useful to map an arbitrary URL to a command > without the '?command=' and without having to resort to Apache rewrite > rules. The difference between '?command=PULogin' and '/login' is minimal, but also makes other things more difficult. If commands look the same as pages, validation of page names becomes difficult and extensibility is at risk. > And while we are on the subject of commands and rewrite rules, I've noticed > that commands post to '/' even if they are part of a longer URL (like > mydomain.com/site/login). This behavior is slightly problematic given that > the default page for one of my sites is not '/' and I have a rewrite rule to > redirect '/' to that default page. I had to add a 'RewriteCond > %{REQUEST_METHOD} !POST' test to my rewrite rule. It would be nice if > commands posted to the URL they were called from. I guess there is something wrong with your Seaside setup, that's not what is normally happening. You can check that on seaside.st for example. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From p3anoman at gmail.com Mon Mar 2 21:29:22 2009 From: p3anoman at gmail.com (John M) Date: Mon, 2 Mar 2009 15:29:22 -0500 Subject: Pier sites on seasidehosting Message-ID: <40f637ec0903021229p72936e15k950838c0c122ac1c@mail.gmail.com> Is there a problem hosting a pier website on seasidehosting? Or are there special considerations of which I am unaware? Thanks in advance John -------------- next part -------------- An HTML attachment was scrubbed... URL: From girba at iam.unibe.ch Mon Mar 2 21:34:37 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Mon, 2 Mar 2009 21:34:37 +0100 Subject: Pier sites on seasidehosting In-Reply-To: <40f637ec0903021229p72936e15k950838c0c122ac1c@mail.gmail.com> References: <40f637ec0903021229p72936e15k950838c0c122ac1c@mail.gmail.com> Message-ID: <7830ECC7-D936-4B13-80FC-2B8642EE5341@iam.unibe.ch> Hi, Indeed, there seems that version 1.1.1. has a problem with seasidehosting. It appears that the problem is related to the fonts that Pharo initializes on startup. The Pharo people said to work on it. Cheers, Doru On 2 Mar 2009, at 21:29, John M wrote: > Is there a problem hosting a pier website on seasidehosting? Or are > there special considerations of which I am unaware? > Thanks in advance > John > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Obvious things are difficult to teach." From rdrvr.biz at gmail.com Mon Mar 2 21:36:03 2009 From: rdrvr.biz at gmail.com (David Farber) Date: Mon, 2 Mar 2009 13:36:03 -0700 Subject: Direct login In-Reply-To: <67628d690903021113v7235c7b3k22c96c57d34e319c@mail.gmail.com> References: <67628d690902282343k6b34e270uee39ff02111d12ed@mail.gmail.com> <336FF00E-3E32-4B06-A606-66740E3DFEDB@gmail.com> <67628d690903012321w64d70303w7ede237d956ba422@mail.gmail.com> <67628d690903021113v7235c7b3k22c96c57d34e319c@mail.gmail.com> Message-ID: <6FB3F012-90BD-4AA1-B2AB-4CA0F3CDE4FA@gmail.com> On Mar 2, 2009, at 12:13 PM, Lukas Renggli wrote: >> On my pages I usually use a hidden login link, so editors just have >> to > press Ctrl+L to get to the login page > (http://www.piercms.com/doc/shortcuts). If desired the login page can > also be bookmarked. Ctrl+L is nice--I'll use that now that I know about it--but isn't good enough for non-technical users. I want /login. > The difference between '?command=PULogin' and '/login' is minimal, but > also makes other things more difficult. If commands look the same as > pages, validation of page names becomes difficult and extensibility is > at risk. For what I have in mind, that seems like an odd reply. Maybe I am not expressing myself very well. Perhaps I should just mess around in the code a bit and see what I can come up with. >> And while we are on the subject of commands and rewrite rules, I've >> noticed >> that commands post to '/' even if they are part of a longer URL (like >> mydomain.com/site/login). This behavior is slightly problematic >> given that >> the default page for one of my sites is not '/' and I have a >> rewrite rule to >> redirect '/' to that default page. I had to add a 'RewriteCond >> %{REQUEST_METHOD} !POST' test to my rewrite rule. It would be nice >> if >> commands posted to the URL they were called from. > > I guess there is something wrong with your Seaside setup, that's not > what is normally happening. You can check that on seaside.st for > example. Hmm. Yes. I can see that it is not doing this in the default Pier image. I'll have to look in to this some more. (Maybe it has to do with setting Server Hostname and/or Server Path?) David ---- 1 Squeak/Seaside/Pier site deployed From p3anoman at gmail.com Mon Mar 2 22:47:49 2009 From: p3anoman at gmail.com (John M) Date: Mon, 2 Mar 2009 16:47:49 -0500 Subject: Pier sites on seasidehosting In-Reply-To: <7830ECC7-D936-4B13-80FC-2B8642EE5341@iam.unibe.ch> References: <40f637ec0903021229p72936e15k950838c0c122ac1c@mail.gmail.com> <7830ECC7-D936-4B13-80FC-2B8642EE5341@iam.unibe.ch> Message-ID: <40f637ec0903021347u3a3b3889t77bf4dff06e62fac@mail.gmail.com> I have attempted Export the 1.1.1 kernel and import it into a 1.1 image I still have hanging around. After a fair bit of package loading (SiteMap, Google, DesignCommand etc) I get a message "Unable to import: Instances of Timestamp are not indexable" Any idea how I can get past that? On Mon, Mar 2, 2009 at 3:34 PM, Tudor Girba wrote: > Hi, > > Indeed, there seems that version 1.1.1. has a problem with seasidehosting. > It appears that the problem is related to the fonts that Pharo initializes > on startup. The Pharo people said to work on it. > > Cheers, > Doru > > > > On 2 Mar 2009, at 21:29, John M wrote: > > Is there a problem hosting a pier website on seasidehosting? Or are there >> special considerations of which I am unaware? >> Thanks in advance >> John >> >> _______________________________________________ >> SmallWiki, Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > -- > www.tudorgirba.com > > "Obvious things are difficult to teach." > > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From evaklo at gmail.com Tue Mar 3 04:33:59 2009 From: evaklo at gmail.com (=?ISO-8859-1?Q?Lautaro_Fern=E1ndez?=) Date: Tue, 3 Mar 2009 01:33:59 -0200 Subject: Pier on Visualworks In-Reply-To: <84f77e270811150616g17ecffd0wffa1086858f02bfa@mail.gmail.com> References: <491E4DAA.9070503@shaw.ca> <67628d690811142349p4ae81314h11cec3352f11124d@mail.gmail.com> <84f77e270811150616g17ecffd0wffa1086858f02bfa@mail.gmail.com> Message-ID: <36ce93cf0903021933v6b0d34cch6797bf4d36cd14c@mail.gmail.com> I've recently tested Pier (the version which is in Cincom repository) with 7.6 and 7.7 images. I can fix the actual errors and republish the conflicted packages. If I'm not mistaken there are 2 problems with some string messages that aren't in the image, and as Dennis said, if you do some *magic* in the PRKernel>> initialize things will be working ok. So, if it's ok with you, I can republish the packages without those problems. Bye :) Lautaro Fern?ndez 2008/11/15 Dennis Schetinin > > 2008/11/15 Lukas Renggli > >> Magritte is definitely a prerequisite for Pier. Very likely you also >> need Seaside too. There should be no other dependencies. I don't know >> the details for VisualWorks though. If I remember correctly Michel >> Bany and Niall Ross both worked on the port, maybe they can help? >> >> Lukas >> >> On Sat, Nov 15, 2008 at 5:18 AM, Dick Smit wrote: >> > I am excited about trying Pier, but I have a bit of an investment in >> > code I have written in Visualworks 7.6 versus Squeak. >> > >> > I tried loading the Pier bundle from the Cincom public repository, but >> > got lots of errors. >> > >> > I found that if I pre-loaded Magritte, things went a little better, but >> > I am still getting errors. >> > >> > Is the Visualworks version of Pier a dead end? Am I missing some >> > dependencies? Should I use an older version of Visualworks? Should I >> > just port my code over to Squeak? >> > >> > If the Pier bundle on the Cincom public repository is good, then let me >> > know and I'll post my specific errors to try to work through it. >> > > I don't remember if I had any problems loading Magritte, but there's small > issue with Pier in VW. > BTW, the order was: Seaside, then Magritte, then Pier (if I remember > correctly). > > So, the problem: there's reference to *SeasideInstallationOptions* in *Pier.PRPierFrame > class>>initialize*. But there's no *SeasideInstallationOptions* in VW port > of Seaside (anymore?). > > Actually the correspoding error during installation can be just ignored > (using "Jump To Caret" option in debugger for example) followed by "manual" > registration of Pier thereafter (e.g. using * > self registerAsApplication: 'pier' kernel: (PRKernel named: > 'Pier')* > for default values). > > Anyway, it would be nice to have recent versions of Pier in VW (the one in > Cincom Public Repository is more than a year old)... :) > > > -- > Dennis Schetinin > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Luke LAut SkyFernadezWalker -------------- next part -------------- An HTML attachment was scrubbed... URL: From girba at iam.unibe.ch Tue Mar 3 19:13:09 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Tue, 3 Mar 2009 19:13:09 +0100 Subject: CSS namespaces In-Reply-To: <40f637ec0903011131l1bc8d133k436743527f007c37@mail.gmail.com> References: <1235840376.15861.7.camel@cineflux> <1235913829.29544.14.camel@cineflux> <1235928666.29544.53.camel@cineflux> <49AAC86B.2050408@yahoo.co.uk> <40f637ec0903010957ge7637fcv52b110418372606a@mail.gmail.com> <52C1D9A6-AEE2-4FD3-A41E-46027C635FD9@iam.unibe.ch> <40f637ec0903011131l1bc8d133k436743527f007c37@mail.gmail.com> Message-ID: <464A4619-7C2A-4A1E-A402-C0643D46481E@iam.unibe.ch> Thanks for the feedback. I am happy that you found the talk useful. My problem with it is that it is too long. I now added it here: http://www.piercms.com/doc/screencasts Cheers, Doru On 1 Mar 2009, at 20:31, John M wrote: > Good advice, thank you Doru > I have also used the other two methods you mention. > > BTW EXCELLENT video at ESUG 2008. It made everything clear to me! I > wish I would have noticed it a month ago when it was posted. > Thanks also to James Robertson for providing the service. I highly > recommend that you give this video prominence on the Pier site. > John > > > On Sun, Mar 1, 2009 at 2:24 PM, Tudor Girba > wrote: > Hi, > > Changing the default blueprint library is not the best way. It's > better to create your own library and load this after the blueprint, > or directly add your definitions to the css in Pier. Like this, you > can update to the latest Pier code without needing to change anything. > > Cheers, > Doru > > > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower." From joel at ardishealth.com Tue Mar 3 22:04:42 2009 From: joel at ardishealth.com (Joel Turnbull) Date: Tue, 03 Mar 2009 16:04:42 -0500 Subject: a context for testing Message-ID: <49AD9B6A.8000306@ardishealth.com> I have a PRWidget that initializes a report based on whether self context user isNil. I'm attempting to do unit tests on the widget using SeasideTesting, but when setUp initializes the widget, it has no context. Is there a simple way to create a test context? I don't quite understand the pieces of a context ( kernel, structure, command ) well enough to create one from scratch at this point. Joel -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/x-pkcs7-signature Size: 5145 bytes Desc: S/MIME Cryptographic Signature URL: From keith_hodges at yahoo.co.uk Tue Mar 3 23:38:18 2009 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Tue, 03 Mar 2009 22:38:18 +0000 Subject: Corrupt component Message-ID: <49ADB15A.1090904@yahoo.co.uk> I accidentally added a seaside component that doesnt render to the pier environment in a fresh 1.1. I tried removing it from the document heirarchy but to no avail, any ideas? Keith From renggli at gmail.com Wed Mar 4 07:59:21 2009 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 4 Mar 2009 07:59:21 +0100 Subject: a context for testing In-Reply-To: <49AD9B6A.8000306@ardishealth.com> References: <49AD9B6A.8000306@ardishealth.com> Message-ID: <67628d690903032259l243d60d2xafacd2b992fd4423@mail.gmail.com> > I have a PRWidget that initializes a report based on whether self context > user isNil. I'm attempting to do unit tests on the widget using > SeasideTesting, but when setUp initializes the widget, it has no context. Is > there a simple way to create a test context? Have a look at the references to PRContext in Pier-Testing there are a few examples. For a basic example PRContext kernel: (PRKernel new root: (PRPage named: 'Root')) should give you a valid context on a temporary kernel with a single root page. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From renggli at gmail.com Wed Mar 4 09:43:08 2009 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 4 Mar 2009 09:43:08 +0100 Subject: Corrupt component In-Reply-To: <49ADB15A.1090904@yahoo.co.uk> References: <49ADB15A.1090904@yahoo.co.uk> Message-ID: <67628d690903040043r48a9096ar93c239211f19a541@mail.gmail.com> > I tried removing it from the document heirarchy but to no avail, any ideas? An easy fix is to use the back button and change the component to a different one that is known to work. Another possibility is to open the 'browse' view on the parent and trigger the remove command from there. If everything else fails, the inspector is yet another possibility. Navigate to the structure and send #remove to get rid of it. Lukas -- Lukas Renggli http://www.lukas-renggli.ch From keith_hodges at yahoo.co.uk Wed Mar 4 14:16:10 2009 From: keith_hodges at yahoo.co.uk (Keith Hodges) Date: Wed, 04 Mar 2009 13:16:10 +0000 Subject: Corrupt component In-Reply-To: <67628d690903040043r48a9096ar93c239211f19a541@mail.gmail.com> References: <49ADB15A.1090904@yahoo.co.uk> <67628d690903040043r48a9096ar93c239211f19a541@mail.gmail.com> Message-ID: <49AE7F1A.10708@yahoo.co.uk> Lukas Renggli wrote: >> I tried removing it from the document heirarchy but to no avail, any ideas? >> > > An easy fix is to use the back button and change the component to a > different one that is known to work. > > Another possibility is to open the 'browse' view on the parent and > trigger the remove command from there. > > If everything else fails, the inspector is yet another possibility. > Navigate to the structure and send #remove to get rid of it. > > Lukas > Navigate? It cant even render anything. In the end I fixed it by repairing the component, and then removing it. The irony if this is that I was adding a random component in order to test the "PRRemoveChildren command" which is for just this eventuality. Btw the component I randomly added, and which doesnt work was RRDemo, which I didnt even know I had installed, so my curiosity was raised. thanks for the tips for the future Keith From dassi at mindclue.ch Thu Mar 5 10:24:12 2009 From: dassi at mindclue.ch (Andreas Brodbeck) Date: Thu, 05 Mar 2009 10:24:12 +0100 Subject: do you have a pier? References: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch> Message-ID: In article <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3 at iam.unibe.ch>, Tudor Girba wrote: > Hi, > > We would like to fill the list of Pier installations from: > http://www.piercms.com/seaside/doc/examples > > Thus, we kindly ask you to let us know if you have Pier installation > somewhere publicly so that we can link to it. Just born some days ago: http://andreas.mindclue.ch/blog Greetings, Andreas From girba at iam.unibe.ch Thu Mar 5 11:06:59 2009 From: girba at iam.unibe.ch (Tudor Girba) Date: Thu, 5 Mar 2009 11:06:59 +0100 Subject: do you have a pier? In-Reply-To: References: <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3@iam.unibe.ch> Message-ID: Thank you. I added it to the list. Cheers, Doru On 5 Mar 2009, at 10:24, Andreas Brodbeck wrote: > In article <4E3B1F54-582F-41D4-96EA-65CE9D59E1F3 at iam.unibe.ch>, > Tudor Girba wrote: > >> Hi, >> >> We would like to fill the list of Pier installations from: >> http://www.piercms.com/seaside/doc/examples >> >> Thus, we kindly ask you to let us know if you have Pier installation >> somewhere publicly so that we can link to it. > > Just born some days ago: > > http://andreas.mindclue.ch/blog > > Greetings, Andreas > > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Every now and then stop and ask yourself if the war you're fighting is the right one." From damien.cassou at gmail.com Thu Mar 5 14:54:12 2009 From: damien.cassou at gmail.com (Damien Cassou) Date: Thu, 5 Mar 2009 14:54:12 +0100 Subject: Colourizing parts of a preformatted text Message-ID: <6ac749c10903050554m3790ee04ob350d73a29c9a6db@mail.gmail.com> Hi, for my Pier website, I have implemented a pier plugin to pretty-print code depending on a particular syntax: https://diaspec.bordeaux.inria.fr/pier/Samples/Air+conditioning This is interesting but requires some work. What's the easiest solution to colourize a preformatted text? Is it possible to make a particular (instance of a) word appear in a different color? Bye -- Damien Cassou http://damiencassou.seasidehosting.st From renggli at gmail.com Thu Mar 5 15:21:56 2009 From: renggli at gmail.com (Lukas Renggli) Date: Thu, 5 Mar 2009 15:21:56 +0100 Subject: Colourizing parts of a preformatted text In-Reply-To: <6ac749c10903050554m3790ee04ob350d73a29c9a6db@mail.gmail.com> References: <6ac749c10903050554m3790ee04ob350d73a29c9a6db@mail.gmail.com> Message-ID: <67628d690903050621q2b43a6e4pa072b008eff22a8@mail.gmail.com> > This is interesting but requires some work. What's the easiest > solution to colourize a preformatted text? Is it possible to make a > particular (instance of a) word appear in a different color? I am sure you know ShoutPier from seaside.st and my blog, they both use Shout to highlight Smalltalk code. It would be easy to add pretty-printing too, if that would be a requirement. There are several JavaScript libraries available that do syntax-highlighting on the client-side. I've never tried to integrate one of these libraries, but that should be easily possible. http://shjs.sourceforge.net/ http://softwaremaniacs.org/soft/highlight/en/ http://mihai.bazon.net/projects/javascript-syntax-highlighting-engine Lukas -- Lukas Renggli http://www.lukas-renggli.ch From evaklo at gmail.com Thu Mar 5 15:52:25 2009 From: evaklo at gmail.com (=?ISO-8859-1?Q?Lautaro_Fern=E1ndez?=) Date: Thu, 5 Mar 2009 12:52:25 -0200 Subject: Colourizing parts of a preformatted text In-Reply-To: <6ac749c10903050554m3790ee04ob350d73a29c9a6db@mail.gmail.com> References: <6ac749c10903050554m3790ee04ob350d73a29c9a6db@mail.gmail.com> Message-ID: <36ce93cf0903050652o1a8e1687j339d42d63180296e@mail.gmail.com> Some days ago, I've finished to bind a package that adds 2 brushes into the html (WARenderCanvas). To use it you have to add a SHLibrary into your web site, and then doing something like: renderContentOn: html html smalltalkCode: ' message = '' ifTrue: [html div with: message] ifFalse: [html smalltalkCode: message]' Other brushes(for instance, SQL, Java, CSS, C, etc etc...) can be added quite easily (really, it's easy) but I didn't need it, so I didn't added. I've also implemented another package that binds Pier with this package. And allows you to do in an editor page the following: [|] message = '' [|] ifTrue: [html div with: message] [|] ifFalse: [html smalltalkCode: message] and the output will be the same as the #renderContentOn: If you want the code, I can give it to you(or anyone). I've tested both only on VisualWorks, but I think it will run on other dialects too. the JS is from: http://alexgorbatchev.com/wiki/SyntaxHighlighter if you download that JS it won't have the Smalltalk parser, because I did it and it will be published in the following version (that was what Alex told me). Hope this helps. Lautaro Fern?ndez 2009/3/5 Damien Cassou > Hi, > > for my Pier website, I have implemented a pier plugin to pretty-print > code depending on a particular syntax: > > https://diaspec.bordeaux.inria.fr/pier/Samples/Air+conditioning > > This is interesting but requires some work. What's the easiest > solution to colourize a preformatted text? Is it possible to make a > particular (instance of a) word appear in a different color? > > Bye > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > _______________________________________________ > SmallWiki, Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Luke LAut SkyFernadezWalker -------------- next part -------------- An HTML attachment was scrubbed... URL: From norbert at hartl.name Fri Mar 6 14:55:18 2009 From: norbert at hartl.name (Norbert Hartl) Date: Fri, 06 Mar 2009 14:55:18 +0100 Subject: resolve description from assigned name value Message-ID: <1236347718.6697.38.camel@cineflux> Hi, I'm trying to align my tests a little bit more at the moment. I'm using seaside testing for the tests and magritte for most of the model objects. Whenever a model asComponent is rendered every individual MAElementComponent is rendered with an automatically assigned name attribute. Is it hard to resolve the description by this name value? This way it would be possible to set values in a form input fields. This is quite tedious at the moment. The fields that use