}}}' then it creates PRDocument PRParagraph PRVerbatim I like to avoid creating a paragraph which has a big influence on styles. If I'm not misled by firebug etc. than the verbatim is created after the paragraph leaving an empty paragraph right before the verbatim. Is this possible easily? thanks, Norbert From nick.ager at gmail.com Wed Feb 16 01:15:05 2011 From: nick.ager at gmail.com (Nick Ager) Date: Wed, 16 Feb 2011 00:15:05 +0000 Subject: How to prevent the creation of paragraphs while parsing? In-Reply-To: <81C77D8B-A050-4EF9-B201-7CE60D816F63@hartl.name> References: <81C77D8B-A050-4EF9-B201-7CE60D816F63@hartl.name> Message-ID: Hi Norbert, I like to avoid creating a paragraph which has a big influence on styles. If > I'm not misled by firebug etc. than the verbatim is created after the > paragraph leaving an empty paragraph right before the verbatim. Is this > possible easily? I was holding off replying in case someone else came up with a better suggestion as I'm not terribly proud of the solution I came up with. For what it's worth, I've derived from PRPage (#IZPageWithoutEnclosingParagraph) and implemented #document: as: --- document: aDocument (aDocument hasChildren and: [ aDocument children size = 1 ]) ifTrue: [ | outerParagraph | outerParagraph := aDocument children first. outerParagraph class name = #PRParagraph ifTrue: [ "remove the enclosing paragraph" document := PRDocument withAll: outerParagraph children ] ]. document isNil ifTrue: [ document := aDocument ] ifFalse: [ document owner: self ] --- I'm sure there's a more elegant way.... Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From lenglish5 at cox.net Thu Feb 17 00:21:41 2011 From: lenglish5 at cox.net (Lawson English) Date: Wed, 16 Feb 2011 16:21:41 -0700 Subject: Discussion forums In-Reply-To: References: <4D5335A1.1050704@cox.net> Message-ID: <4D5C5C05.5010709@cox.net> Just uploaded Pier-Discussion-LDE57 to MCHttpRepository location "http://www.squeaksource.com/DiscussionInPier" user: '' password: '' Minimalist changes to make a very minimalist Pier-based discussion forum work with later versions of Squeak. Lawson. On 2/10/11 2:39 AM, Nick Ager wrote: > Thanks I'd be very interested to see that. > > On 10 February 2011 00:47, Lawson English > wrote: > > There's some old code in squeaksource that I managed to update to > work with the latest version of pier. I'll load the update later > today. > > Its very minimal, but lets you start a topic and add comments and > so on. > > > Lawson > > > > On 2/9/11 6:22 AM, Nick Ager wrote: >> Hi, >> >> Does anyone know of any discussion forum type functionality that >> has been developed for Pier or Seaside? If not, do you think Pier >> be a suitable framework, or would it make more sense to try to >> integrate forum software from another platform? >> >> Thanks >> >> Nick >> >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -------------- next part -------------- An HTML attachment was scrubbed... URL: From norbert at hartl.name Fri Feb 18 08:30:31 2011 From: norbert at hartl.name (Norbert Hartl) Date: Fri, 18 Feb 2011 08:30:31 +0100 Subject: How to prevent the creation of paragraphs while parsing? In-Reply-To: References: <81C77D8B-A050-4EF9-B201-7CE60D816F63@hartl.name> Message-ID: <6E15FC8D-6AE0-4C40-B9D3-73EE185B1A72@hartl.name> On 16.02.2011, at 01:15, Nick Ager wrote: > Hi Norbert, > > I like to avoid creating a paragraph which has a big influence on styles. If I'm not misled by firebug etc. than the verbatim is created after the paragraph leaving an empty paragraph right before the verbatim. Is this possible easily? > > I was holding off replying in case someone else came up with a better suggestion as I'm not terribly proud of the solution I came up with. For what it's worth, I've derived from PRPage (#IZPageWithoutEnclosingParagraph) and implemented #document: as: > > --- > > document: aDocument > (aDocument hasChildren and: [ aDocument children size = 1 ]) > ifTrue: [ > | outerParagraph | > outerParagraph := aDocument children first. > outerParagraph class name = #PRParagraph > ifTrue: [ > "remove the enclosing paragraph" > document := PRDocument withAll: outerParagraph children ] ]. > document isNil > ifTrue: [ document := aDocument ] > ifFalse: [ document owner: self ] > > --- > > I'm sure there's a more elegant way.... > Thanks. I hope there is a more elegant way. My way at the moment is to do css display: none ;) Norbert -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.marschall at gmail.com Sat Feb 19 10:24:29 2011 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Sat, 19 Feb 2011 10:24:29 +0100 Subject: [Seaside] Re: Loading seaside into Pharo core (stable) In-Reply-To: <1297703488610-3305378.post@n4.nabble.com> References:

<1297703488610-3305378.post@n4.nabble.com> Message-ID: 2011/2/14 pablo : > > Thanks Philippe Marschall, > it seems that all the applications are disabled by default and it is ok for > a production environment. > > But I want to enable a Pier Blog, How could I do that? Best ask on smallwiki at iam.unibe.ch [1] http://www.piercms.com/contact Cheers Philippe From rafael.luque.leiva at gmail.com Sat Feb 19 20:54:56 2011 From: rafael.luque.leiva at gmail.com (Rafael Luque) Date: Sat, 19 Feb 2011 20:54:56 +0100 Subject: How to run Pier2 with PharoCore 1.2 Message-ID: Hi all, I've been testing Pier2 using the One-Click image, but i would like to be able to run it using the PharoCore 1.2 download. I've evaluated the following code (as it appears in the ConfigurationOfSeaside>>workspace comments): Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfSeaside'; load. (ConfigurationOfSeaside project version: '1.0.7') load: #('Seaside 3.0' 'Magritte2 Tests' 'Pier2 Tests' 'Pier2 AddOns'). Then I start the Seaside server with: (Smalltalk at: #WAKom) startOn: 8080. The Seaside responds successfully in the 8080 port but the pier application is not configured, how should I configure it? Thank you, Rafael Luque -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick.ager at gmail.com Mon Feb 21 15:38:15 2011 From: nick.ager at gmail.com (Nick Ager) Date: Mon, 21 Feb 2011 14:38:15 +0000 Subject: How to run Pier2 with PharoCore 1.2 In-Reply-To: References: Message-ID: Hi, Try the following: Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPierAddOns2'; load. (Smalltalk at: #ConfigurationOfPierAddOns2) project latestVersion load: 'ALL'. you can then register a dispatcher with: PRDistribution register. On 19 February 2011 19:54, Rafael Luque wrote: > > Hi all, > > I've been testing Pier2 using the One-Click image, but i would like to be > able to run it using the PharoCore 1.2 download. > > I've evaluated the following code (as it appears in the > ConfigurationOfSeaside>>workspace comments): > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSeaside'; > load. > > (ConfigurationOfSeaside project version: '1.0.7') > load: #('Seaside 3.0' 'Magritte2 Tests' 'Pier2 Tests' 'Pier2 AddOns'). > > Then I start the Seaside server with: > > (Smalltalk at: #WAKom) startOn: 8080. > > The Seaside responds successfully in the 8080 port but the pier application > is not configured, how should I configure it? > > Thank you, > > Rafael Luque > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick.ager at gmail.com Mon Feb 21 20:42:23 2011 From: nick.ager at gmail.com (Nick Ager) Date: Mon, 21 Feb 2011 19:42:23 +0000 Subject: logging from a location other than root doesn't keep you logged in Message-ID: I've created an issue: http://code.google.com/p/pier/issues/detail?id=131with an associated fix: Name: Pier-Security-NickAger.174 Author: NickAger Time: 21 February 2011, 7:39:09 pm UUID: 7a2e62e8-276f-452c-8f4e-407f23e52121 Ancestors: Pier-Security-lr.173 Hope that makes sense Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From jetkoten at gmail.com Wed Feb 23 03:02:03 2011 From: jetkoten at gmail.com (JETkoten) Date: Tue, 22 Feb 2011 21:02:03 -0500 Subject: Moving and adding chapters in "book" Message-ID: <4D646A9B.9060408@gmail.com> Hi, I'm working with the built-in book in Pier to put together an outline of an online book. Great software, one of the best online book formats I've seen. My problem is, the only way I can find to make a new chapter after trying for about an hour is to copy "1 Introduction". When I do this, the copied chapters go down below the Keywords Index in the Table of Contents, thus spoiling the layout in my opinion. So now it's: 1 Introduction 1.1 Section Keyword index 2 Intro-2 2.1 Section 2 [...] How can I move the Keywords Index down the list to be the final item in Table of Contents please? I want: 1 Introduction 1.1 Section 2 Intro-2 2.1 Section 2 3 3.1 4 4.1 5 5.1 6 6.1 7 [...] Keyword index Also, is there a better way to make new chapters than to just keep copying? I couldn't find any kind of page (while doing Add from various pages) that had Chapter as a type or that would give it a number and line it up with 1 Introuction. Thanks in advance. From renggli at gmail.com Wed Feb 23 07:34:26 2011 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 23 Feb 2011 07:34:26 +0100 Subject: Moving and adding chapters in "book" In-Reply-To: <4D646A9B.9060408@gmail.com> References: <4D646A9B.9060408@gmail.com> Message-ID: All pages of a book are called "Book Portion". Go to the parent where you want to add a new page and select "add". Depending on the type of the parent the child becomes a "part", "chapter", "section" or "subsection". In case the new page is a child of the root you can choose if you want it to be a "part" or a "chapter" (along the lines of LaTeX). To reorder the children use the "order" command (again in the parent, if I understand your example correctly that would be the book). To change the parent use the "move" command and the type of the page will automatically adapt to the new parent. Lukas On 23 February 2011 03:02, JETkoten wrote: > Hi, > > I'm working with the built-in book in Pier to put together an outline of an > online book. Great software, one of the best online book formats I've seen. > > My problem is, the only way I can find to make a new chapter after trying > for about an hour is to copy "1 Introduction". When I do this, the copied > chapters go down below the Keywords Index in the Table of Contents, thus > spoiling the layout in my opinion. > > So now it's: > > 1 ? ? ? ? Introduction > 1.1 ? ? ? ? ?Section > ? ? ? ? ?Keyword index > 2 ? ? ? ? Intro-2 > 2.1 ? ? ? ? Section 2 > [...] > > How can I move the Keywords Index down the list to be the final item in > Table of Contents please? > > I want: > > 1 ? ? ? ? Introduction > 1.1 ? ? ? ? ?Section > 2 ? ? ? ? Intro-2 > 2.1 ? ? ? ? Section 2 > 3 > 3.1 > 4 > 4.1 > 5 > 5.1 > 6 > 6.1 > 7 > [...] > ? ? ? ? ?Keyword index > > Also, is there a better way to make new chapters than to just keep copying? > I couldn't find any kind of page (while doing Add from various pages) that > had Chapter as a type or that would give it a number and line it up with 1 > Introuction. > > Thanks in advance. > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli www.lukas-renggli.ch From jetkoten at gmail.com Wed Feb 23 21:59:08 2011 From: jetkoten at gmail.com (JETkoten) Date: Wed, 23 Feb 2011 15:59:08 -0500 Subject: Moving and adding chapters in "book" In-Reply-To: References: <4D646A9B.9060408@gmail.com> Message-ID: <4D65751C.90109@gmail.com> Thanks for your time and explanation, Lukas. I've got it the way I want it now. On 2/23/11 1:34 AM, Lukas Renggli wrote: > All pages of a book are called "Book Portion". Go to the parent where > you want to add a new page and select "add". Depending on the type of > the parent the child becomes a "part", "chapter", "section" or > "subsection". In case the new page is a child of the root you can > choose if you want it to be a "part" or a "chapter" (along the lines > of LaTeX). To reorder the children use the "order" command (again in > the parent, if I understand your example correctly that would be the > book). To change the parent use the "move" command and the type of the > page will automatically adapt to the new parent. > > Lukas > > On 23 February 2011 03:02, JETkoten wrote: >> Hi, >> >> I'm working with the built-in book in Pier to put together an outline of an >> online book. Great software, one of the best online book formats I've seen. >> >> My problem is, the only way I can find to make a new chapter after trying >> for about an hour is to copy "1 Introduction". When I do this, the copied >> chapters go down below the Keywords Index in the Table of Contents, thus >> spoiling the layout in my opinion. >> >> So now it's: >> >> 1 Introduction >> 1.1 Section >> Keyword index >> 2 Intro-2 >> 2.1 Section 2 >> [...] >> >> How can I move the Keywords Index down the list to be the final item in >> Table of Contents please? >> >> I want: >> >> 1 Introduction >> 1.1 Section >> 2 Intro-2 >> 2.1 Section 2 >> 3 >> 3.1 >> 4 >> 4.1 >> 5 >> 5.1 >> 6 >> 6.1 >> 7 >> [...] >> Keyword index >> >> Also, is there a better way to make new chapters than to just keep copying? >> I couldn't find any kind of page (while doing Add from various pages) that >> had Chapter as a type or that would give it a number and line it up with 1 >> Introuction. >> >> Thanks in advance. >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > From nick.ager at gmail.com Sat Feb 26 16:50:17 2011 From: nick.ager at gmail.com (Nick Ager) Date: Sat, 26 Feb 2011 15:50:17 +0000 Subject: Enabling cookies causes callback links to incorrectly redirect in Firefox Message-ID: I've logged a bug: http://code.google.com/p/pier/issues/detail?id=132 The text of the bug is: Steps to recreate the bug: 1) Download the recent build of Pier 2 - http://hudson.lukas-renggli.ch/job/Pier%202/ - this bug is not present in Pier with Seaside 2.8 2) In a workspace execute the following: PREventDistribution register. WAAdmin defaultDispatcher defaultHandler preferenceAt: #useCookies put: true. (PRPathLookup start: (PRKernel instances anyOne) root path: '/call') contents: 'In Firefox, try clicking on the counter +counter+'. (PRPathLookup start: (PRKernel instances anyOne) root path: '/call') addChild: ( (PRComponent named: 'counter') componentClass: WACounter; yourself) 3) Within Firefox (I'm using 3.16.13) browse to http://localhost:8080/pier/call - you should be on the "Call for Contributions" page into which the above script embeds the standard Seaside counter component in the page. 4) Try clicking on the "++" or "--" links a couple of times and you'll find yourself taken to http://localhost:8080/pier/dates and rather than modifying the counter value. Here's my understanding of the bug: 1) Amongst other metadata Pier adds the following to the header: 2) In Firefox when cookies are enabled, the causes firefox to issue at least two requests for each page; the first request for the url specified, the second for the url specified in the href of the . Note this second request is not visible in firebug (I added request logging to WAComancheRequestConverter). In Safari or Chrome, I haven't seen any additional requests and so the problem does not appear. 3) The second request confuses the callback hander Unfortunately my understanding of how the callback handler should work is limiting my ability to fix the bug. Any thoughts? From nick.ager at gmail.com Sun Feb 27 14:16:01 2011 From: nick.ager at gmail.com (Nick Ager) Date: Sun, 27 Feb 2011 13:16:01 +0000 Subject: Enabling cookies causes callback links to incorrectly redirect in Firefox In-Reply-To: References: Message-ID: I've uploaded an image which demonstration the issue: http://getitmade.com/static/Pier-2.zip Download and browse to http://localhost:8080/pier/call Click on the "++" or "--" links of the WACounter instance twice in Firefox. Notice that only in Firefox the second click of the callback take you to http://localhost:8080/pier/dates rather than incrementing the counter. On 26 February 2011 15:50, Nick Ager wrote: > I've logged a bug: http://code.google.com/p/pier/issues/detail?id=132 > > The text of the bug is: > > > Steps to recreate the bug: > 1) Download the recent build of Pier 2 - > http://hudson.lukas-renggli.ch/job/Pier%202/ - this bug is not present > in Pier with Seaside 2.8 > 2) In a workspace execute the following: > > PREventDistribution register. > WAAdmin defaultDispatcher defaultHandler preferenceAt: #useCookies put: true. > (PRPathLookup start: (PRKernel instances anyOne) root path: '/call') > contents: 'In Firefox, try clicking on the counter > > +counter+'. > (PRPathLookup start: (PRKernel instances anyOne) root path: '/call') addChild: ( > (PRComponent named: 'counter') componentClass: WACounter; yourself) > > 3) Within Firefox (I'm using 3.16.13) browse to > http://localhost:8080/pier/call - you should be on the "Call for > Contributions" page into which the above script embeds the standard > Seaside counter component in the page. > 4) Try clicking on the "++" or "--" links a couple of times and you'll > find yourself taken to http://localhost:8080/pier/dates and rather > than modifying the counter value. > > Here's my understanding of the bug: > > 1) Amongst other metadata Pier adds the following to the header: href="/pier/dates" rel="next"> > 2) In Firefox when cookies are enabled, the causes > firefox to issue at least two requests for each page; the first > request for the url specified, the second for the url specified in the > href of the . Note this second request is not visible > in firebug (I added request logging to WAComancheRequestConverter). In > Safari or Chrome, I haven't seen any additional requests and so the > problem does not appear. > 3) The second request confuses the callback hander > > Unfortunately my understanding of how the callback handler should work > is limiting my ability to fix the bug. Any thoughts? >