From rafael.luque.leiva at gmail.com Thu Aug 4 15:50:45 2011 From: rafael.luque.leiva at gmail.com (Rafael Luque) Date: Thu, 4 Aug 2011 15:50:45 +0200 Subject: Pier CMS site is down Message-ID: Hello all, I suppose you are managing this, but I cannot load piercms.com website since yesterday. Rafael Luque -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Fri Aug 5 09:32:25 2011 From: renggli at gmail.com (Lukas Renggli) Date: Fri, 5 Aug 2011 09:32:25 +0200 Subject: Pier CMS site is down In-Reply-To: References: Message-ID: Thanks for reporting, seems to be a DNS problem. Doru is fixing it :-) Lukas On 4 August 2011 15:50, Rafael Luque wrote: > Hello all, > > I suppose you are managing this, but I cannot load piercms.com website since > yesterday. > > Rafael Luque > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli www.lukas-renggli.ch From renggli at gmail.com Sat Aug 6 16:36:31 2011 From: renggli at gmail.com (Lukas Renggli) Date: Sat, 6 Aug 2011 16:36:31 +0200 Subject: Pier CMS site is down In-Reply-To: References: Message-ID: The site (www.pierces.com) should be reachable again. Thanks for reporting, and thanks to Doru for updating the DNS :-) Lukas On 5 August 2011 09:32, Lukas Renggli wrote: > Thanks for reporting, seems to be a DNS problem. Doru is fixing it :-) > > Lukas > > On 4 August 2011 15:50, Rafael Luque wrote: >> Hello all, >> >> I suppose you are managing this, but I cannot load piercms.com website since >> yesterday. >> >> Rafael Luque >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch From renggli at gmail.com Sat Aug 6 16:37:07 2011 From: renggli at gmail.com (Lukas Renggli) Date: Sat, 6 Aug 2011 16:37:07 +0200 Subject: Pier CMS site is down In-Reply-To: References: Message-ID: The domain is piercms.com of course :-) On 6 August 2011 16:36, Lukas Renggli wrote: > The site (www.pierces.com) should be reachable again. Thanks for > reporting, and thanks to Doru for updating the DNS :-) > > Lukas > > On 5 August 2011 09:32, Lukas Renggli wrote: >> Thanks for reporting, seems to be a DNS problem. Doru is fixing it :-) >> >> Lukas >> >> On 4 August 2011 15:50, Rafael Luque wrote: >>> Hello all, >>> >>> I suppose you are managing this, but I cannot load piercms.com website since >>> yesterday. >>> >>> Rafael Luque >>> >>> _______________________________________________ >>> Magritte, Pier and Related Tools ... >>> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >>> >> >> >> >> -- >> Lukas Renggli >> www.lukas-renggli.ch >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > -- Lukas Renggli www.lukas-renggli.ch From nick.ager at gmail.com Mon Aug 8 20:15:25 2011 From: nick.ager at gmail.com (Nick Ager) Date: Mon, 8 Aug 2011 19:15:25 +0100 Subject: Magritte -> Json Message-ID: Hi, I'm experimenting with a JSON converter for objects with Magritte descriptions. So far I've added the following to GRObject: jsonOn: aStream | description | description := self description. description children isEmpty ifFalse: [ | first | first := true. aStream nextPut: ${. description do: [ :each | first ifTrue: [ first := false ] ifFalse: [ aStream nextPut: $, ]. aStream json: each label; nextPut: $:; json: (each accessor read: self) ]. aStream nextPut: $} ] you can then generate JSON from an object, for example: ((PRPage named: 'examplePage') contents: '!!Hello', String crlf, 'Hello ""world"" check') asJson gives: '{"Name":"examplePage","Visibility":false,"Navigation Title":"ExamplePage","Tags":[],"Title":"ExamplePage","Owner":null,"Group":null,"Contents":{},"Plain Text":"Hello\rHello world check","Environment":null,"Style Sheet":null,"Shortcut Icon":null,"CSS Classes":null}' The method fails with recursive structures, but otherwise is appears to work well. Does this look like a sensible approach? Has anyone else implemented anything similar? Thanks Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From jvdsandt at gmail.com Mon Aug 8 22:55:30 2011 From: jvdsandt at gmail.com (Jan van de Sandt) Date: Mon, 8 Aug 2011 22:55:30 +0200 Subject: Magritte -> Json In-Reply-To: References: Message-ID: Hi, There is something simular in the Magritte Add-ons repository: the Magritte-Json package. It's definitely usefull functionality! Jan. On Mon, Aug 8, 2011 at 8:15 PM, Nick Ager wrote: > Hi, > > I'm experimenting with a JSON converter for objects with Magritte > descriptions. So far I've added the following to GRObject: > > jsonOn: aStream > | description | > description := self description. > description children isEmpty ifFalse: [ > | first | > first := true. > aStream nextPut: ${. > description do: [ :each | > first > ifTrue: [ first := false ] > ifFalse: [ aStream nextPut: $, ]. > aStream > json: each label; > nextPut: $:; > json: (each accessor read: self) ]. > aStream nextPut: $} ] > > you can then generate JSON from an object, for example: > > ((PRPage named: 'examplePage') contents: '!!Hello', String crlf, 'Hello > ""world"" check') asJson > > gives: > > '{"Name":"examplePage","Visibility":false,"Navigation > Title":"ExamplePage","Tags":[],"Title":"ExamplePage","Owner":null,"Group":null,"Contents":{},"Plain > Text":"Hello\rHello world check","Environment":null,"Style > Sheet":null,"Shortcut Icon":null,"CSS Classes":null}' > > The method fails with recursive structures, but otherwise is appears to > work well. > > Does this look like a sensible approach? Has anyone else implemented > anything similar? > > Thanks > > Nick > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.marschall at gmail.com Tue Aug 9 06:58:39 2011 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Tue, 9 Aug 2011 06:58:39 +0200 Subject: Magritte -> Json In-Reply-To: References: Message-ID: 2011/8/8 Nick Ager : > Hi, > I'm experimenting with a JSON converter for objects with Magritte > descriptions. So far I've added the following to GRObject: > jsonOn: aStream > | description | > description := self description. > description children isEmpty ifFalse: [ > | first | > first := true. > aStream nextPut: ${. > description do: [ :each | > first > ifTrue: [ first := false ] > ifFalse: [ aStream nextPut: $, ]. > aStream > json: each label; > nextPut: $:; > json: (each accessor read: self) ]. > aStream nextPut: $}?] > you can then generate JSON from an object, for example: > ((PRPage named: 'examplePage') contents: '!!Hello', String crlf, 'Hello > ""world"" check') asJson > gives: > ?'{"Name":"examplePage","Visibility":false,"Navigation > Title":"ExamplePage","Tags":[],"Title":"ExamplePage","Owner":null,"Group":null,"Contents":{},"Plain > Text":"Hello\rHello world check","Environment":null,"Style > Sheet":null,"Shortcut Icon":null,"CSS Classes":null}' > The method fails with recursive structures, but otherwise is appears to work > well. Recursive structures don't work in JSON in general. > Does this look like a sensible approach? Has anyone else implemented > anything similar? There is Magritte-Json in [1]. It gives you more control, you can override the name of a property and choose not to serialize certain objects. I found this necessary when implementing certain predefined APIs. It's a bit more "magritty" in the sense that is uses reader and writer objects. Though it could certainly be improved on. You can find examples in [2]. [1] http://source.lukas-renggli.ch/magritteaddons [2] http://www.squeaksource.com/orion Cheers Philippe From nick.ager at gmail.com Tue Aug 9 12:12:13 2011 From: nick.ager at gmail.com (Nick Ager) Date: Tue, 9 Aug 2011 11:12:13 +0100 Subject: Magritte -> Json In-Reply-To: References: Message-ID: Hi Philippe, There is Magritte-Json in [1]. It gives you more control, you can > override the name of a property and choose not to serialize certain > objects. I found this necessary when implementing certain predefined > APIs. It's a bit more "magritty" in the sense that is uses reader and > writer objects. Though it could certainly be improved on. You can find > examples in [2]. > > [1] http://source.lukas-renggli.ch/magritteaddons > [2] http://www.squeaksource.com/orion It looks good and more comprehensive than my effort. It appears that objects have to be derived from MJObject in order to use the Json conversion. Would there be a problem moving the #javascriptOn: method from MJObject to an extension method on GRObject to allow more objects to gain the Json conversion functionality? (I choose GRObject as WAObject, PRObject & MAObject are all ultimately derived from GRObject). The difference between #asJavascript (with it's accompanying #javascriptOn:), asJson (with it's accompanying #jsonOn:)? It appears that even though #asJavascript and #asJson have largely the same effect, #asJson implements a Json compatible subset of #asJavascript. Would it not make sense to use #asJson instead of #asJavascript and #jsonOn: rather than #javascriptOn:, or have I missed something? Cheers Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From philippe.marschall at gmail.com Tue Aug 9 18:48:32 2011 From: philippe.marschall at gmail.com (Philippe Marschall) Date: Tue, 9 Aug 2011 18:48:32 +0200 Subject: Magritte -> Json In-Reply-To: References: Message-ID: 2011/8/9 Nick Ager : > Hi Philippe, > >> There is Magritte-Json in [1]. It gives you more control, you can >> override the name of a property and choose not to serialize certain >> objects. I found this necessary when implementing certain predefined >> APIs. It's a bit more "magritty" in the sense that is uses reader and >> writer objects. Though it could certainly be improved on. You can find >> examples in [2]. >> >> ?[1] http://source.lukas-renggli.ch/magritteaddons >> ?[2] http://www.squeaksource.com/orion > > It looks good and more comprehensive than my effort. > It appears that objects have to be derived from?MJObject in order to use the > Json conversion. Without being certain I don't think so. It should work with any class that has the same methods. > Would there be a problem moving the #javascriptOn: method > from MJObject to an extension method on GRObject to allow more objects to > gain the Json conversion functionality? (I choose GRObject as WAObject, > PRObject & MAObject are all ultimately derived from GRObject). No. > The difference between #asJavascript (with it's > accompanying?#javascriptOn:),?asJson (with it's accompanying #jsonOn:)? It > appears that even though #asJavascript and #asJson have largely the same > effect, #asJson implements a Json compatible subset of #asJavascript. Would > it not make sense to use #asJson instead of #asJavascript and?#jsonOn: > rather than?#javascriptOn:, Yes. > or have I missed something? No. Feel free to change your proposed changes. I might also make sense to move over some of the orion tests. I hope you don't have to change your slides now ;-) I'm sure you're also aware of Magritte-XMLBinding in the same repository that does XML data binding. Cheers Philippe From nick.ager at gmail.com Wed Aug 10 08:39:12 2011 From: nick.ager at gmail.com (Nick Ager) Date: Wed, 10 Aug 2011 07:39:12 +0100 Subject: Magritte -> Json In-Reply-To: References: Message-ID: Hi Philippe, > Feel free to change your proposed changes. I might also make sense to > move over some of the orion tests. > I've checked in Magritte-Json-NickAger.10 and I've modified Orion, but couldn't check it in (permission issue) so I've attached my changes. Cheers Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Orion-NickAger.18.mcz Type: application/octet-stream Size: 13877 bytes Desc: not available URL: From norbert at hartl.name Sat Aug 13 18:24:05 2011 From: norbert at hartl.name (Norbert Hartl) Date: Sat, 13 Aug 2011 18:24:05 +0200 Subject: Magritte -> Json In-Reply-To: References: Message-ID: Great the magritte json binding exists. I need it and thought I need to build it myself. Can't wait to return from my vacation (ok, not really true) to test it. I will use it together with the conumes (accept-...) feature you added to seaside-rest. That's a nice example on how do multiformat web APIs. Great stuff, Norbert Am 09.08.2011 um 06:58 schrieb Philippe Marschall : > 2011/8/8 Nick Ager : >> Hi, >> I'm experimenting with a JSON converter for objects with Magritte >> descriptions. So far I've added the following to GRObject: >> jsonOn: aStream >> | description | >> description := self description. >> description children isEmpty ifFalse: [ >> | first | >> first := true. >> aStream nextPut: ${. >> description do: [ :each | >> first >> ifTrue: [ first := false ] >> ifFalse: [ aStream nextPut: $, ]. >> aStream >> json: each label; >> nextPut: $:; >> json: (each accessor read: self) ]. >> aStream nextPut: $} ] >> you can then generate JSON from an object, for example: >> ((PRPage named: 'examplePage') contents: '!!Hello', String crlf, 'Hello >> ""world"" check') asJson >> gives: >> '{"Name":"examplePage","Visibility":false,"Navigation >> Title":"ExamplePage","Tags":[],"Title":"ExamplePage","Owner":null,"Group":null,"Contents":{},"Plain >> Text":"Hello\rHello world check","Environment":null,"Style >> Sheet":null,"Shortcut Icon":null,"CSS Classes":null}' >> The method fails with recursive structures, but otherwise is appears to work >> well. > > Recursive structures don't work in JSON in general. > >> Does this look like a sensible approach? Has anyone else implemented >> anything similar? > > There is Magritte-Json in [1]. It gives you more control, you can > override the name of a property and choose not to serialize certain > objects. I found this necessary when implementing certain predefined > APIs. It's a bit more "magritty" in the sense that is uses reader and > writer objects. Though it could certainly be improved on. You can find > examples in [2]. > > [1] http://source.lukas-renggli.ch/magritteaddons > [2] http://www.squeaksource.com/orion > > Cheers > Philippe > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From offray at riseup.net Sun Aug 14 17:28:18 2011 From: offray at riseup.net (=?ISO-8859-1?Q?Offray_Vladimir_Luna_C=E1rdenas?=) Date: Sun, 14 Aug 2011 10:28:18 -0500 Subject: Enabling reStructuredText as a Markup language in Pier Message-ID: <4E47E992.40202@riseup.net> Hi all, It has been really nice my re-encounter with Smalltalk using Pharo, Seaside and Pier, and knowing that there are some important projects to learn like Moose or Aida and Illiad. I want to make my site using Pier, and "consolidate" my on-line presence there. Previously I have used Moin Moin and Tiddlywiki and now I'm writing my thesis using reStructuredText, so would be nice to have a single markup language for all this writing and I think that this one should be reST. So the project is giving Pier the possibility to use this as a Markup language. I have seen that there are some projects like Helvetia and Pettit Parser that, perhaps, may be used in this kind of project, but I really don't know if this is feasible or where to start. So if anyone have some ideas on this I would really like to hear them. Thanks, Offray From renggli at gmail.com Sun Aug 14 18:22:57 2011 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 14 Aug 2011 18:22:57 +0200 Subject: Enabling reStructuredText as a Markup language in Pier In-Reply-To: <4E47E992.40202@riseup.net> References: <4E47E992.40202@riseup.net> Message-ID: Hi Offray, > and Tiddlywiki and now I'm writing my thesis using reStructuredText, so > would be nice to have a single markup language for all this writing and I > think that this one should be reST. So the project is giving Pier the > possibility to use this as a Markup language. I have seen that there are > some projects like Helvetia and Pettit Parser that, perhaps, may be used in > this kind of project, but I really don't know if this is feasible or where > to start. So if anyone have some ideas on this I would really like to hear > them. Helvetia is about embedding languages into Smalltalk, so unless you want to mix reST with Smalltalk Helvetia is probably not much of help for your project. PetitParser (that is also used in Helvetia) is a nice little parser framework that can help you to transform reST to the Pier document AST. For questions about PetitParser best ask in the Pharo or Moose list, most discussion is going on there. To support a new wiki syntax in Pier you need to provide two classes: one converting reST to the Pier document AST, and one converting the Pier document AST to reST. Currently in use are PRDocumentParser and PRWikiWriter, but you can replace them by customizing the Magritte document description. I once tried to implement Creole (a wiki standard) as an alternative syntax, but it didn't work out well because the syntax didn't fit the feature set of Pier (e.g. I needed a way to parametrize links, nested lists, etc). I don't know reST and just wanted to warn you that you check if the syntax really fits Pier before you start :-) Cheers, Lukas -- Lukas Renggli www.lukas-renggli.ch From tudor at tudorgirba.com Sun Aug 14 22:11:14 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Sun, 14 Aug 2011 22:11:14 +0200 Subject: citezen-pier broken Message-ID: Hi, Citezen-Pier does not seem to work anymore. The first thing I noticed is that it still relies on Rio for accessing the bib file. I guess we should update it to work with Filesystem. Anyone happens to have an interest to work on it? Cheers, Doru -- www.tudorgirba.com "Some battles are better lost than fought." From damien.pollet at gmail.com Mon Aug 15 02:39:07 2011 From: damien.pollet at gmail.com (Damien Pollet) Date: Mon, 15 Aug 2011 02:39:07 +0200 Subject: [Pharo-project] citezen-pier broken In-Reply-To: References: Message-ID: Let's have a look during ESUG, it shouldn't be that difficult to fix :) On 14 August 2011 22:11, Tudor Girba wrote: > Hi, > > Citezen-Pier does not seem to work anymore. The first thing I noticed is that it still relies on Rio for accessing the bib file. I guess we should update it to work with Filesystem. > > Anyone happens to have an interest to work on it? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Some battles are better lost than fought." > > > > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet From damien.pollet at gmail.com Mon Aug 15 05:05:06 2011 From: damien.pollet at gmail.com (Damien Pollet) Date: Mon, 15 Aug 2011 05:05:06 +0200 Subject: Enabling reStructuredText as a Markup language in Pier In-Reply-To: References: <4E47E992.40202@riseup.net> Message-ID: On 14 August 2011 18:22, Lukas Renggli wrote: >> and Tiddlywiki and now I'm writing my thesis using reStructuredText, so >> would be nice to have a single markup language for all this writing and I >> think that this one should be reST. FYI, I started writing a markdown parser using PetitParser (not specifically tied to Pier). It's far from finished, but it's a start :) That will probably not be of much help to your particular problem, but having Smalltalk implementations for such popular markup syntaxes would be really nice. -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet From offray at riseup.net Mon Aug 15 14:51:34 2011 From: offray at riseup.net (offray at riseup.net) Date: Mon, 15 Aug 2011 05:51:34 -0700 (PDT) Subject: Enabling reStructuredText as a Markup language in Pier In-Reply-To: References: <4E47E992.40202@riseup.net> Message-ID: Hi, > On 14 August 2011 18:22, Lukas Renggli wrote: >>> and Tiddlywiki and now I'm writing my thesis using reStructuredText, so >>> would be nice to have a single markup language for all this writing and >>> I >>> think that this one should be reST. > > FYI, I started writing a markdown parser using PetitParser (not > specifically tied to Pier). It's far from finished, but it's a start > :) > > That will probably not be of much help to your particular problem, but > having Smalltalk implementations for such popular markup syntaxes > would be really nice. > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet Thanks Damien and Lukas for your feedback and advice. I'm reading the seaside book and the hpi tutorial now trying to prepare myself for Magritte and having much background to acomplish this taks. Meanwhile seems better to start with simpler task like quiting the _s and _k part of the url, because in a content centered site, the produce ugly urls and are not much necesary. I will keep you posted. Cheers, Offray From nick.ager at gmail.com Mon Aug 15 16:27:52 2011 From: nick.ager at gmail.com (Nick Ager) Date: Mon, 15 Aug 2011 15:27:52 +0100 Subject: Enabling reStructuredText as a Markup language in Pier In-Reply-To: References: <4E47E992.40202@riseup.net> Message-ID: > > Meanwhile > seems better to start with simpler task like quiting the _s and _k part of > the url, because in a content centered site, the produce ugly urls and are > not much necesary. I will keep you posted. > you can get rid of the _s by enabling cookies. (app preferenceAt: #useCookies put: true) Pier will also try to remove the _k if possible (for example http://mysite/blog, http://mysite/about etc) -------------- next part -------------- An HTML attachment was scrubbed... URL: From offray at riseup.net Mon Aug 15 19:07:08 2011 From: offray at riseup.net (offray at riseup.net) Date: Mon, 15 Aug 2011 10:07:08 -0700 (PDT) Subject: Enabling reStructuredText as a Markup language in Pier In-Reply-To: References: <4E47E992.40202@riseup.net> Message-ID: Hi, >> >> Meanwhile >> seems better to start with simpler task like quiting the _s and _k part >> of >> the url, because in a content centered site, the produce ugly urls and >> are >> not much necesary. I will keep you posted. >> > > you can get rid of the _s by enabling cookies. (app preferenceAt: > #useCookies put: true) > Pier will also try to remove the _k if possible (for example > http://mysite/blog, http://mysite/about etc) Thanks Nick. I don't know which object should I send that message (how plays the role of "app" in a default pier One Click Experience setup). I'm also taking a look at: http://onsmalltalk.com/clean-urls-in-seaside it seems to work also with the _k part, but just trying to override the messages in methods in Pier gives some error messages. Is Ramon's approach usable at Pier? Cheers, Offray From nick.ager at gmail.com Mon Aug 15 19:27:09 2011 From: nick.ager at gmail.com (Nick Ager) Date: Mon, 15 Aug 2011 18:27:09 +0100 Subject: Enabling reStructuredText as a Markup language in Pier In-Reply-To: References: <4E47E992.40202@riseup.net> Message-ID: > Thanks Nick. I don't know which object should I send that message (how > plays the role of "app" in a default pier One Click Experience setup). in the one click you should be able to get the 'app' through: WADispatcher default handlerAt: 'pier' OR you can navigate to localhost:8080/config click on the pier app and in the 'General' section click on the 'Override' button for the 'Use Cookies' entry the 'apply' button as the bottom of the configuration. > I'm > also taking a look at: > > http://onsmalltalk.com/clean-urls-in-seaside > > it seems to work also with the _k part, but just trying to override the > messages in methods in Pier gives some error messages. Is Ramon's approach > usable at Pier? I think pier already contains much of what Ramon's post discusses; once you enable cookies (it's easier to do than to write about) -------------- next part -------------- An HTML attachment was scrubbed... URL: From offray at riseup.net Mon Aug 15 21:10:24 2011 From: offray at riseup.net (offray at riseup.net) Date: Mon, 15 Aug 2011 12:10:24 -0700 (PDT) Subject: Enabling reStructuredText as a Markup language in Pier In-Reply-To: References: <4E47E992.40202@riseup.net> Message-ID: <842649a04af0708c149e041b34dc9279.squirrel@swift.riseup.net> Hi, :-) >> Thanks Nick. I don't know which object should I send that message (how >> plays the role of "app" in a default pier One Click Experience setup). > > > in the one click you should be able to get the 'app' through: > > WADispatcher default handlerAt: 'pier' > > OR > > you can navigate to localhost:8080/config click on the pier app and in the > 'General' section click on the 'Override' button for the 'Use Cookies' > entry > the 'apply' button as the bottom of the configuration. > > > >> I'm >> also taking a look at: >> >> http://onsmalltalk.com/clean-urls-in-seaside >> >> it seems to work also with the _k part, but just trying to override the >> messages in methods in Pier gives some error messages. Is Ramon's >> approach >> usable at Pier? > > > I think pier already contains much of what Ramon's post discusses; once > you > enable cookies (it's easier to do than to write about) Thanks a lot Nick. It works like a charm. Cheers, Offray From tudor at tudorgirba.com Tue Aug 16 16:11:39 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Tue, 16 Aug 2011 16:11:39 +0200 Subject: jquery-based slideshow? In-Reply-To: References: <3A4EAEB7-2A87-4B54-8796-3E1ACF76A26C@tudorgirba.com> Message-ID: Hi Nick, I finally got around to play with the Cycle plugin and created a small Pier widget for it. The widget works similarly to the old Randomizer in that it takes a source structure as an input and then slideshows the children. I committed a first raw (no cycle-specific settings yet) version in the Pier-JQuery package. Cheers, Doru On 8 Jun 2011, at 17:21, Tudor Girba wrote: > Thanks, Nick. > > I will take a look. > > Cheers, > Doru > > > On 27 May 2011, at 12:54, Nick Ager wrote: > >> I don't know of anything specifically for Pier though I integrated the JQuery cycle (http://jquery.malsup.com/cycle/): >> >> ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) project latestVersion) load: #('JQWidgetBox-Core' 'JQWidgetBox-Dev' 'JQWidgetBox-Cycle-Core' 'JQWidgetBox-Cycle-Dev') >> >> >> On 27 May 2011 10:53, Tudor Girba wrote: >> Hi, >> >> Has anyone produced a JQuery-based slideshow for Pier 2? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "What we can governs what we wish." >> >> >> >> _______________________________________________ >> 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 > > -- > www.tudorgirba.com > > "Value is always contextual." > > > -- www.tudorgirba.com "Presenting is storytelling." From offray at riseup.net Tue Aug 16 22:17:56 2011 From: offray at riseup.net (=?ISO-8859-1?Q?Offray_Vladimir_Luna_C=E1rdenas?=) Date: Tue, 16 Aug 2011 15:17:56 -0500 Subject: Resetting admin passwork from the image Message-ID: <4E4AD074.8010602@riseup.net> Hi all, It seems that I as pretty tired when I made my last changes in the image in the processo to make it ready for a public site and I forgot the admin password. There is any way to reset it from the image (instead of the web interface)? Thanks, Offray From renggli at gmail.com Tue Aug 16 22:23:32 2011 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 16 Aug 2011 22:23:32 +0200 Subject: Resetting admin passwork from the image In-Reply-To: <4E4AD074.8010602@riseup.net> References: <4E4AD074.8010602@riseup.net> Message-ID: You can inspect "PRKernel instances" that contains a list of Pier instances. Navigate to your Pier instance, and then into "properties" and "users". From that list inspect the user you want to change and evaluate "self password: 'password'". Cheers, Lukas On 16 August 2011 22:17, Offray Vladimir Luna C?rdenas wrote: > Hi all, > > It seems that I as pretty tired when I made my last changes in the image in > the processo to make it ready for a public site and I forgot the admin > password. There is any way to reset it from the image (instead of the web > interface)? > > Thanks, > > Offray > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli www.lukas-renggli.ch From offray at riseup.net Tue Aug 16 23:40:26 2011 From: offray at riseup.net (=?ISO-8859-1?Q?Offray_Vladimir_Luna_C=E1rdenas?=) Date: Tue, 16 Aug 2011 16:40:26 -0500 Subject: Resetting admin passwork from the image In-Reply-To: References: <4E4AD074.8010602@riseup.net> Message-ID: <4E4AE3CA.8080707@riseup.net> Hi, El 16/08/11 15:23, Lukas Renggli escribi?: > You can inspect "PRKernel instances" that contains a list of Pier instances. > > Navigate to your Pier instance, and then into "properties" and > "users". From that list inspect the user you want to change and > evaluate "self password: 'password'". > > Cheers, > Lukas Ahhh that's really nice!!! It works so well. I really like the introspective nature of Smalltalk. Cheers, Offray From dhenrich at vmware.com Tue Aug 16 23:37:07 2011 From: dhenrich at vmware.com (Dale Henrichs) Date: Tue, 16 Aug 2011 14:37:07 -0700 (PDT) Subject: Resetting admin passwork from the image In-Reply-To: Message-ID: <1791135395.537231.1313530627517.JavaMail.root@zimbra-prod-mbox-2.vmware.com> I just now had a reason to programmatically change the admin password for pier and here's the expression that I used: (((WADispatcher default handlerAt: 'pier') preferenceAt: #kernel) propertyAt: #adminUser) password: 'newPassword' Tweak the dispatcher lookup to match your pier path... Dale ----- Original Message ----- | From: "Lukas Renggli" | To: "Pier and Related Tools Magritte ..." | Sent: Tuesday, August 16, 2011 1:23:32 PM | Subject: Re: Resetting admin passwork from the image | | You can inspect "PRKernel instances" that contains a list of Pier | instances. | | Navigate to your Pier instance, and then into "properties" and | "users". From that list inspect the user you want to change and | evaluate "self password: 'password'". | | Cheers, | Lukas | | On 16 August 2011 22:17, Offray Vladimir Luna C?rdenas | wrote: | > Hi all, | > | > It seems that I as pretty tired when I made my last changes in the | > image in | > the processo to make it ready for a public site and I forgot the | > admin | > password. There is any way to reset it from the image (instead of | > the web | > interface)? | > | > Thanks, | > | > Offray | > _______________________________________________ | > Magritte, Pier and Related Tools ... | > https://www.iam.unibe.ch/mailman/listinfo/smallwiki | > | | | | -- | Lukas Renggli | www.lukas-renggli.ch | | _______________________________________________ | Magritte, Pier and Related Tools ... | https://www.iam.unibe.ch/mailman/listinfo/smallwiki | From tudor at tudorgirba.com Fri Aug 19 00:49:45 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Fri, 19 Aug 2011 00:49:45 +0200 Subject: trouble rendering widgets Message-ID: <1F92F932-DB1C-4303-B737-ADE5D5A99B6C@tudorgirba.com> Hi, I have a bit of trouble rendering a widget that aims to embed some other structures. Here is the current code: renderContentOn: html html div id: #cycler; script: ((html jQuery: #cycler) cycle fx: 'fade'; timeout: self timeout; delay: self delay; speed: self speed; pager: '#cyclerNav') greaseString; with: [ self sourceChildren do: [:each | html div class: 'cyclerItem'; with: [html rendererInstance visit: each document] ] ]. It seems to work fine when sourceChildren contains only PRPages, but when there is a PRFile inside, it goes strange. For example, if I have three PRFiles in the collection, the rendering looks like:
One
Two
Three What am I doing wrong? Cheers, Doru -- www.tudorgirba.com "Some battles are better lost than fought." From tudor at tudorgirba.com Fri Aug 19 01:01:32 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Fri, 19 Aug 2011 01:01:32 +0200 Subject: book - user comments In-Reply-To: References: <8D6B7F78-C655-4F28-9A8C-6B1F1A491841@tudorgirba.com> <0D42A129-000B-4B1D-AF1D-13599C3D8804@tudorgirba.com> Message-ID: After a long time, thanks :). To make it work properly with a book (not jump to the note form), I added: if (document.forms[0].parentNode.className != "leavecomment" && document.forms[0].parentNode.className !="addnote") { I hope that is Ok. Cheers, Doru On 20 Jun 2011, at 04:31, Johnny wrote: > Hello Doru, > It's in PRJavaScriptLibrary>>pierJs > > if (document.forms[0].parentNode.className != "leavecomment") {...} > > Best, > John > > > On Sun, Jun 19, 2011 at 8:37 PM, Tudor Girba wrote: > Hi again, > > I think I was quite tired this afternoon :). The solution is to add the component Book Notes and embed it in the template. > > Now, the problem is that the input box takes the focus by default. I guess this is the same bug as we used to have in the comments of the blog components. Can anyone remember how to fix that? > > Cheers, > Doru > > > On 19 Jun 2011, at 16:54, Tudor Girba wrote: > > > Hi, > > > > I am trying the book component in the latest Pier and I notice that the user comments component does not seem to appear anymore. Is there something I should do, or is this a bug? > > > > Cheers, > > Doru > > > > > > -- > > www.tudorgirba.com > > > > "It's not what we do that matters most, it's how we do it." > > > > -- > www.tudorgirba.com > > "We are all great at making mistakes." > > > > > > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > -- > http://john-mckeon.us/seaside > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Problem solving should be focused on describing the problem in a way that makes the solution obvious." From renggli at gmail.com Fri Aug 19 07:23:16 2011 From: renggli at gmail.com (Lukas Renggli) Date: Fri, 19 Aug 2011 07:23:16 +0200 Subject: trouble rendering widgets In-Reply-To: <1F92F932-DB1C-4303-B737-ADE5D5A99B6C@tudorgirba.com> References: <1F92F932-DB1C-4303-B737-ADE5D5A99B6C@tudorgirba.com> Message-ID: Are you correctly implementing #children? Also you make sure to use #continue:in:on: instead of #visit: (that's why you get the messed up HTML, your code writes to the wrong renderer). Have a look at PRDocument widget to see an example of how to render other structures within your widgets. Lukas On 19 August 2011 00:49, Tudor Girba wrote: > Hi, > > I have a bit of trouble rendering a widget that aims to embed some other structures. > > Here is the current code: > > renderContentOn: html > ? ? ? ?html div > ? ? ? ? ? ? ? ?id: #cycler; > ? ? ? ? ? ? ? ?script: ((html jQuery: #cycler) cycle fx: 'fade'; timeout: self timeout; delay: self delay; speed: self speed; pager: '#cyclerNav') greaseString; > ? ? ? ? ? ? ? ?with: [ > ? ? ? ? ? ? ? ? ? ? ? ?self sourceChildren do: [:each | > ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?html div class: 'cyclerItem'; with: [html rendererInstance visit: each document] ] ]. > > It seems to work fine when sourceChildren contains only PRPages, but when there is a PRFile inside, it goes strange. For example, if I have three PRFiles in the collection, the rendering looks like: > >
> ? ? ? ?
> ? ? ? ?
One
> ? ? ? ?
Two
>
> Three > > > What am I doing wrong? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Some battles are better lost than fought." > > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli www.lukas-renggli.ch From nick.ager at gmail.com Fri Aug 19 07:39:04 2011 From: nick.ager at gmail.com (Nick Ager) Date: Fri, 19 Aug 2011 06:39:04 +0100 Subject: trouble rendering widgets In-Reply-To: References: <1F92F932-DB1C-4303-B737-ADE5D5A99B6C@tudorgirba.com> Message-ID: > > > > > renderContentOn: html > > html div > > id: #cycler; > > script: ((html jQuery: #cycler) cycle fx: 'fade'; timeout: > self timeout; delay: self delay; speed: self speed; pager: '#cyclerNav') > greaseString; > > with: [ > > self sourceChildren do: [:each | > > html div class: 'cyclerItem'; with: [html > rendererInstance visit: each document] ] ]. > > > Unrelated to your problem, but I don't think you need the call to #greaseString at the end of your script: line. Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From tudor at tudorgirba.com Fri Aug 19 07:43:36 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Fri, 19 Aug 2011 07:43:36 +0200 Subject: trouble rendering widgets In-Reply-To: References: <1F92F932-DB1C-4303-B737-ADE5D5A99B6C@tudorgirba.com> Message-ID: <34983E0E-BE13-4CAF-93C8-2BBD44EB76D7@tudorgirba.com> Hi, On 19 Aug 2011, at 07:23, Lukas Renggli wrote: > Are you correctly implementing #children? Yes. But, in this case, there are no children. > Also you make sure to use #continue:in:on: instead of #visit: (that's > why you get the messed up HTML, your code writes to the wrong > renderer). Thanks. That seems to solve the problem. I am using: html rendererInstance withinContentDo: [ html rendererInstance continue: each document in: self on: html ] Cheers, Doru > Have a look at PRDocument widget to see an example of how to render > other structures within your widgets. > > Lukas > > On 19 August 2011 00:49, Tudor Girba wrote: >> Hi, >> >> I have a bit of trouble rendering a widget that aims to embed some other structures. >> >> Here is the current code: >> >> renderContentOn: html >> html div >> id: #cycler; >> script: ((html jQuery: #cycler) cycle fx: 'fade'; timeout: self timeout; delay: self delay; speed: self speed; pager: '#cyclerNav') greaseString; >> with: [ >> self sourceChildren do: [:each | >> html div class: 'cyclerItem'; with: [html rendererInstance visit: each document] ] ]. >> >> It seems to work fine when sourceChildren contains only PRPages, but when there is a PRFile inside, it goes strange. For example, if I have three PRFiles in the collection, the rendering looks like: >> >>
>>
>>
One
>>
Two
>>
>> Three >> >> >> What am I doing wrong? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "Some battles are better lost than fought." >> >> >> >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge." From renggli at gmail.com Fri Aug 19 08:27:22 2011 From: renggli at gmail.com (Lukas Renggli) Date: Fri, 19 Aug 2011 08:27:22 +0200 Subject: trouble rendering widgets In-Reply-To: <34983E0E-BE13-4CAF-93C8-2BBD44EB76D7@tudorgirba.com> References: <1F92F932-DB1C-4303-B737-ADE5D5A99B6C@tudorgirba.com> <34983E0E-BE13-4CAF-93C8-2BBD44EB76D7@tudorgirba.com> Message-ID: >> Are you correctly implementing #children? > > Yes. But, in this case, there are no children. Rendering a structure might introduce new components (directly or indirectly), so you have to declare #children. Lukas -- Lukas Renggli www.lukas-renggli.ch From tudor at tudorgirba.com Fri Aug 19 12:58:51 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Fri, 19 Aug 2011 12:58:51 +0200 Subject: trouble rendering widgets In-Reply-To: References: <1F92F932-DB1C-4303-B737-ADE5D5A99B6C@tudorgirba.com> <34983E0E-BE13-4CAF-93C8-2BBD44EB76D7@tudorgirba.com> Message-ID: <39DCD11B-A596-4859-A579-70B5E7108FBC@tudorgirba.com> Hi, I know. I declared the children by collecting all the components. I just said that for the test with the files, there were no embedded For reference, this is what I used for the children: children ^ self sourceChildren inject: OrderedCollection new into: [:all :each | all addAll: (each componentsIn: self context)] Cheers, Doru On 19 Aug 2011, at 08:27, Lukas Renggli wrote: >>> Are you correctly implementing #children? >> >> Yes. But, in this case, there are no children. > > Rendering a structure might introduce new components (directly or > indirectly), so you have to declare #children. > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal." From renggli at gmail.com Fri Aug 19 13:25:32 2011 From: renggli at gmail.com (Lukas Renggli) Date: Fri, 19 Aug 2011 13:25:32 +0200 Subject: trouble rendering widgets In-Reply-To: <39DCD11B-A596-4859-A579-70B5E7108FBC@tudorgirba.com> References: <1F92F932-DB1C-4303-B737-ADE5D5A99B6C@tudorgirba.com> <34983E0E-BE13-4CAF-93C8-2BBD44EB76D7@tudorgirba.com> <39DCD11B-A596-4859-A579-70B5E7108FBC@tudorgirba.com> Message-ID: > I know. I declared the children by collecting all the components. I just said that for the test with the files, there were no embedded Sorry, I must have misunderstood then :-) Yes, the files and documents do not create components. You only get components when you embed (directly or indirectly) a PRComponent. Lukas -- Lukas Renggli www.lukas-renggli.ch From tudor at tudorgirba.com Sat Aug 20 13:26:35 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Sat, 20 Aug 2011 13:26:35 +0200 Subject: broken css editing Message-ID: <2C0FDE74-CEF3-44FB-B534-CAF8A5C70DF8@tudorgirba.com> Hi, In the latest Pier, editing the CSS through the design command is no longer possible. It looks like the editor now displays the binary stream of the file instead of the text. Take a look in the attachment. The Pier-Design package did not change, and I am not sure where I should look for this. Could anyone point me into the right direction? Cheers, Doru -- www.tudorgirba.com "Sometimes the best solution is not the best solution." -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: Screen Shot 2011-08-20 at 13.24.24.png Type: image/png Size: 150151 bytes Desc: not available URL: From renggli at gmail.com Sat Aug 20 15:27:25 2011 From: renggli at gmail.com (Lukas Renggli) Date: Sat, 20 Aug 2011 15:27:25 +0200 Subject: broken css editing In-Reply-To: <2C0FDE74-CEF3-44FB-B534-CAF8A5C70DF8@tudorgirba.com> References: <2C0FDE74-CEF3-44FB-B534-CAF8A5C70DF8@tudorgirba.com> Message-ID: Try with Name: Pier-Model-lr.413 Author: lr Time: 20 August 2011, 3:27:02 pm UUID: e39cf892-3c4a-4df6-bc78-456c281e0306 Ancestors: Pier-Model-lr.412 - fix PRFile>>#contents that suddenly returned a #[ ... ] instead of a String this should fix the problem. Lukas On 20 August 2011 13:26, Tudor Girba wrote: > Hi, > > In the latest Pier, editing the CSS through the design command is no longer > possible. It looks like the editor now displays the binary stream of the > file instead of the text. Take a look in the attachment. > > The Pier-Design package did not change, and I am not sure where I should > look for this. Could anyone point me into the right direction? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Sometimes the best solution is not the best solution." > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli www.lukas-renggli.ch -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: image/png Size: 150151 bytes Desc: not available URL: From tudor at tudorgirba.com Sat Aug 20 20:43:02 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Sat, 20 Aug 2011 20:43:02 +0200 Subject: broken css editing In-Reply-To: References: <2C0FDE74-CEF3-44FB-B534-CAF8A5C70DF8@tudorgirba.com> Message-ID: <5E74A423-6228-4043-AAE3-3EE437EDF6EA@tudorgirba.com> Thanks, that worked perfectly. Doru On 20 Aug 2011, at 15:27, Lukas Renggli wrote: > Try with > > Name: Pier-Model-lr.413 > Author: lr > Time: 20 August 2011, 3:27:02 pm > UUID: e39cf892-3c4a-4df6-bc78-456c281e0306 > Ancestors: Pier-Model-lr.412 > > - fix PRFile>>#contents that suddenly returned a #[ ... ] instead of a String > > this should fix the problem. > > Lukas > > On 20 August 2011 13:26, Tudor Girba wrote: > Hi, > > In the latest Pier, editing the CSS through the design command is no longer possible. It looks like the editor now displays the binary stream of the file instead of the text. Take a look in the attachment. > > The Pier-Design package did not change, and I am not sure where I should look for this. Could anyone point me into the right direction? > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Sometimes the best solution is not the best solution." > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > -- > Lukas Renggli > www.lukas-renggli.ch > _______________________________________________ > 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 marianopeck at gmail.com Sun Aug 21 00:05:06 2011 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Sun, 21 Aug 2011 00:05:06 +0200 Subject: Problem serializing graphs with Magritte proxies Message-ID: Hi Lukas. I was serializing Pier kernels with Fuel and I started to face problems with Magritte proxies. Since I have no idea how/why they are use, I need to ask a couple of question. Imagine I want to serialize a graph (like a Pier kernel) that contains instances of MADynamicObject, like MAMultipleOptionDescription new default: [ self defaultViewClasses ] magritteDynamicObject; options: [ self defaultViewClasses ] magritteDynamicObject; .... So the questions are: - When I MATERIALIZE the graph, would you like to a) still have the proxies exactly as it was during serialization ? b) or would you expect that objects refer directly to the target of the proxy (proxies do not even exist) ? If you want a) then there are problems that I have to fix because for example I put objects (proxies) in a IdentitySet/IdenitityDictionary (which of course #== is not intercepted by the proxy) but then when I do #instVarAt: or #basicAt: etc, from the serializer, it intercept the messages and forwards to the target. This makes things complicated in Fuel but we can solve it. b) can be achieved with the hook of a #objectToSerialize where each class can implement such message and not necessary answer self but something different. In this case, the proxy can answer the target. So....depending what is the best scenario for the materialization, I can choose which of the options to do. Thanks in advance, -- Mariano http://marianopeck.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Sun Aug 21 10:32:26 2011 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 21 Aug 2011 10:32:26 +0200 Subject: Problem serializing graphs with Magritte proxies In-Reply-To: References: Message-ID: Hi Mariano, > Hi Lukas. I was serializing Pier kernels with Fuel and I started to face > problems with Magritte proxies. Since I have no idea how/why they are use, I > need to ask a couple of question. Imagine I want to serialize a graph (like > a Pier kernel) that contains instances of MADynamicObject, like > > ?MAMultipleOptionDescription new > ??? ??? default: [ self defaultViewClasses ] magritteDynamicObject; > ??? ??? options: [ self defaultViewClasses ] magritteDynamicObject; > .... The reason to have them is to allow Magritte to cache the description instances, while certain properties can still adapt to the model. > So the questions are: > > - When I MATERIALIZE the graph, would you like to > a) still have the proxies exactly as it was during serialization ? > b) or would you expect that objects refer directly to the target of the > proxy (proxies do not even exist) ? It doesn't really matter because the descriptions that end up part of the model are just there to identify a certain described value. The description itself is not used other than to compare it with other descriptions. So the best is probably if you just nil the proxies on serialization. Lukas -- Lukas Renggli www.lukas-renggli.ch From marianopeck at gmail.com Sun Aug 21 10:42:48 2011 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Sun, 21 Aug 2011 10:42:48 +0200 Subject: Problem serializing graphs with Magritte proxies In-Reply-To: References: Message-ID: On Sun, Aug 21, 2011 at 10:32 AM, Lukas Renggli wrote: > Hi Mariano, > > > Hi Lukas. I was serializing Pier kernels with Fuel and I started to face > > problems with Magritte proxies. Since I have no idea how/why they are > use, I > > need to ask a couple of question. Imagine I want to serialize a graph > (like > > a Pier kernel) that contains instances of MADynamicObject, like > > > > MAMultipleOptionDescription new > > default: [ self defaultViewClasses ] magritteDynamicObject; > > options: [ self defaultViewClasses ] magritteDynamicObject; > > .... > > The reason to have them is to allow Magritte to cache the description > instances, while certain properties can still adapt to the model. > > Ok, I understand. > > So the questions are: > > > > - When I MATERIALIZE the graph, would you like to > > a) still have the proxies exactly as it was during serialization ? > > b) or would you expect that objects refer directly to the target of the > > proxy (proxies do not even exist) ? > > It doesn't really matter because the descriptions that end up part of > the model are just there to identify a certain described value. The > description itself is not used other than to compare it with other > descriptions. So the best is probably if you just nil the proxies on > serialization. > Excellent!!! that worked out of the box with the just developed hook by Martin in Fuel. I can now do: MADynamicObject >> fuelAccept: aVisitor ^ aVisitor visitSubstitution: self MADynamicObject >> fuelSubstitution ^ nil And that's all :) Thanks Lukas. > > Lukas > > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Mariano http://marianopeck.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From marianopeck at gmail.com Sun Aug 21 13:38:34 2011 From: marianopeck at gmail.com (Mariano Martinez Peck) Date: Sun, 21 Aug 2011 13:38:34 +0200 Subject: Pier demo? Message-ID: Hi guys. I am testing a import/export of Pier kernels and I would like to test with a real kernel (not the one included by default in Pier). I want to export such kernel and import it in another image. I have 2 pier images handly but both are quite old (pharo 1.0 and non-cog). I would like a new one based on Cog and Pier 2.0. Of course, the Pier image should be open-source or at least you should not care that I test it. so...someone has a pier image to lend me? Thanks a lot in advance. -- Mariano http://marianopeck.wordpress.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Sun Aug 21 13:53:57 2011 From: renggli at gmail.com (Lukas Renggli) Date: Sun, 21 Aug 2011 13:53:57 +0200 Subject: Pier demo? In-Reply-To: References: Message-ID: Sorry, I don't have any Pier 2 images in production. The Seaside book, the Seaside site, my personal website, ... all run in Squeak 3.9 Kernel images with Pier 1.0 only. What you can try to get a moderately large site with about 160 complex pages is to evaluate the following expression. It adds the class and method documentation of Pier and Magritte to your kernel: PRKernel instances anyOne root addChild: (PRPierFrame pageForClass: PRObject); addChild: (PRPierFrame pageForClass: MAObject) Lukas On 21 August 2011 13:38, Mariano Martinez Peck wrote: > Hi guys. I am testing a import/export of Pier kernels and I would like to > test with a real kernel (not the one included by default in Pier). I want to > export such kernel and import it in another image. > I have 2 pier images handly but both are quite old (pharo 1.0 and non-cog). > I would like a new one based on Cog and Pier 2.0. > > Of course, the Pier image should be open-source or at least you should not > care that I test it. > > so...someone has a pier image to lend me? > > Thanks a lot in advance. > > -- > Mariano > http://marianopeck.wordpress.com > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli www.lukas-renggli.ch From nick.ager at gmail.com Mon Aug 22 12:45:26 2011 From: nick.ager at gmail.com (Nick Ager) Date: Mon, 22 Aug 2011 11:45:26 +0100 Subject: Pier Wysiwyg update. Message-ID: Hi, I've rearranged some of my Wysiwyg Pier code into new repositories: * Pier-FileUpload-Wysiwyg - Wysiwyg editor with file upload support in a standard image * Pier-FileUpload-Common-Wysiwyg * Pier-FileUpload-Nginx-Wysiwyg - Wysiwyg editor with file upload support using the Nginx web-server to stream file directly to disk and provide upload progress support. So the Pier-NginxFileUpload-Wysiwyg repository in http://source.lukas-renggli.ch/pier2addons is now redundant. Any chance someone with admin access could delete all the versions of that package from the repository. The other repositories remain the same: * Pier-Wysiwyg * Pier-Tests-Wysiwyg The Wysiwyg editor is nearly ready for a 1.0 release. It now includes file-upload and a site-map drop-down to provide Wysiwyg support for creating internal links and embedding images. I'll update the ConfigurationOfPierWysiwygEditor and probably ConfigurationOfPierAddOns2 ASAP to make it easy to install. It's probably best to wait for the ConfigurationOfPierXXX updates as there are some tricks for the file-upload support - a WASystemConfiguration derived class and a WARequestFilter. I'd love to try the Wysiwyg editor with a large set of Pier content to test if it's ready for prime-time. Anyone fancy trying it? Cheers Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From tudor at tudorgirba.com Tue Aug 23 19:50:09 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Tue, 23 Aug 2011 19:50:09 +0200 Subject: jquery-based slideshow? In-Reply-To: References: <3A4EAEB7-2A87-4B54-8796-3E1ACF76A26C@tudorgirba.com> Message-ID: <33754F1C-9DA0-4698-9D3C-6E75D8D7198E@tudorgirba.com> Hi, I added more settings to the widget. Furthermore, you can also use parameters when embedding the component to set it up dynamically. For example, you can say: +/system/components/cycler|source=.|timeout=5000|effect=fade+ A live demo of the PQCycler in Pier can be seen at the bottom of: http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk Cheers, Doru On 16 Aug 2011, at 16:11, Tudor Girba wrote: > Hi Nick, > > I finally got around to play with the Cycle plugin and created a small Pier widget for it. The widget works similarly to the old Randomizer in that it takes a source structure as an input and then slideshows the children. > > I committed a first raw (no cycle-specific settings yet) version in the Pier-JQuery package. > > Cheers, > Doru > > > On 8 Jun 2011, at 17:21, Tudor Girba wrote: > >> Thanks, Nick. >> >> I will take a look. >> >> Cheers, >> Doru >> >> >> On 27 May 2011, at 12:54, Nick Ager wrote: >> >>> I don't know of anything specifically for Pier though I integrated the JQuery cycle (http://jquery.malsup.com/cycle/): >>> >>> ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) project latestVersion) load: #('JQWidgetBox-Core' 'JQWidgetBox-Dev' 'JQWidgetBox-Cycle-Core' 'JQWidgetBox-Cycle-Dev') >>> >>> >>> On 27 May 2011 10:53, Tudor Girba wrote: >>> Hi, >>> >>> Has anyone produced a JQuery-based slideshow for Pier 2? >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> >>> "What we can governs what we wish." >>> >>> >>> >>> _______________________________________________ >>> 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 >> >> -- >> www.tudorgirba.com >> >> "Value is always contextual." >> >> >> > > -- > www.tudorgirba.com > > "Presenting is storytelling." > -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef." From tudor at tudorgirba.com Tue Aug 23 19:51:21 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Tue, 23 Aug 2011 19:51:21 +0200 Subject: jquery-based slideshow? In-Reply-To: <33754F1C-9DA0-4698-9D3C-6E75D8D7198E@tudorgirba.com> References: <3A4EAEB7-2A87-4B54-8796-3E1ACF76A26C@tudorgirba.com> <33754F1C-9DA0-4698-9D3C-6E75D8D7198E@tudorgirba.com> Message-ID: One more thing. To get the navigation rendered with bullets, you can use the following CSS: #cyclerNav {text-align: center;} #cyclerNav a { display: inline-block; text-decoration: none; width: 8px; height: 8px; background: #DDDDDD; border-radius: 4px; -webkit-border-radius: 4px; -moz-border-radius: 4px; margin-left: 5px; text-indent: -999em;} #cyclerNav a.activeSlide {background: red;} Cheers, Doru On 23 Aug 2011, at 19:50, Tudor Girba wrote: > Hi, > > I added more settings to the widget. Furthermore, you can also use parameters when embedding the component to set it up dynamically. For example, you can say: > +/system/components/cycler|source=.|timeout=5000|effect=fade+ > > A live demo of the PQCycler in Pier can be seen at the bottom of: > http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk > > Cheers, > Doru > > > On 16 Aug 2011, at 16:11, Tudor Girba wrote: > >> Hi Nick, >> >> I finally got around to play with the Cycle plugin and created a small Pier widget for it. The widget works similarly to the old Randomizer in that it takes a source structure as an input and then slideshows the children. >> >> I committed a first raw (no cycle-specific settings yet) version in the Pier-JQuery package. >> >> Cheers, >> Doru >> >> >> On 8 Jun 2011, at 17:21, Tudor Girba wrote: >> >>> Thanks, Nick. >>> >>> I will take a look. >>> >>> Cheers, >>> Doru >>> >>> >>> On 27 May 2011, at 12:54, Nick Ager wrote: >>> >>>> I don't know of anything specifically for Pier though I integrated the JQuery cycle (http://jquery.malsup.com/cycle/): >>>> >>>> ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) project latestVersion) load: #('JQWidgetBox-Core' 'JQWidgetBox-Dev' 'JQWidgetBox-Cycle-Core' 'JQWidgetBox-Cycle-Dev') >>>> >>>> >>>> On 27 May 2011 10:53, Tudor Girba wrote: >>>> Hi, >>>> >>>> Has anyone produced a JQuery-based slideshow for Pier 2? >>>> >>>> Cheers, >>>> Doru >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "What we can governs what we wish." >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >>> >>> -- >>> www.tudorgirba.com >>> >>> "Value is always contextual." >>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Presenting is storytelling." >> > > -- > www.tudorgirba.com > > "No matter how many recipes we know, we still value a chef." > > > > > > -- www.tudorgirba.com "From an abstract enough point of view, any two things are similar." From renggli at gmail.com Tue Aug 23 20:00:32 2011 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 23 Aug 2011 20:00:32 +0200 Subject: jquery-based slideshow? In-Reply-To: References: <3A4EAEB7-2A87-4B54-8796-3E1ACF76A26C@tudorgirba.com> <33754F1C-9DA0-4698-9D3C-6E75D8D7198E@tudorgirba.com> Message-ID: Very cool with these bullets (works even on the mobile phone). What about a slide left/right animation? Lukas On Tuesday, 23 August 2011, Tudor Girba wrote: > One more thing. To get the navigation rendered with bullets, you can use the following CSS: > > #cyclerNav {text-align: center;} > #cyclerNav a { > display: inline-block; > text-decoration: none; > width: 8px; > height: 8px; > background: #DDDDDD; > border-radius: 4px; > -webkit-border-radius: 4px; > -moz-border-radius: 4px; > margin-left: 5px; > text-indent: -999em;} > #cyclerNav a.activeSlide {background: red;} > > Cheers, > Doru > > > On 23 Aug 2011, at 19:50, Tudor Girba wrote: > >> Hi, >> >> I added more settings to the widget. Furthermore, you can also use parameters when embedding the component to set it up dynamically. For example, you can say: >> +/system/components/cycler|source=.|timeout=5000|effect=fade+ >> >> A live demo of the PQCycler in Pier can be seen at the bottom of: >> http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk >> >> Cheers, >> Doru >> >> >> On 16 Aug 2011, at 16:11, Tudor Girba wrote: >> >>> Hi Nick, >>> >>> I finally got around to play with the Cycle plugin and created a small Pier widget for it. The widget works similarly to the old Randomizer in that it takes a source structure as an input and then slideshows the children. >>> >>> I committed a first raw (no cycle-specific settings yet) version in the Pier-JQuery package. >>> >>> Cheers, >>> Doru >>> >>> >>> On 8 Jun 2011, at 17:21, Tudor Girba wrote: >>> >>>> Thanks, Nick. >>>> >>>> I will take a look. >>>> >>>> Cheers, >>>> Doru >>>> >>>> >>>> On 27 May 2011, at 12:54, Nick Ager wrote: >>>> >>>>> I don't know of anything specifically for Pier though I integrated the JQuery cycle (http://jquery.malsup.com/cycle/): >>>>> >>>>> ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) project latestVersion) load: #('JQWidgetBox-Core' 'JQWidgetBox-Dev' 'JQWidgetBox-Cycle-Core' 'JQWidgetBox-Cycle-Dev') >>>>> >>>>> >>>>> On 27 May 2011 10:53, Tudor Girba wrote: >>>>> Hi, >>>>> >>>>> Has anyone produced a JQuery-based slideshow for Pier 2? >>>>> >>>>> Cheers, >>>>> Doru >>>>> >>>>> -- >>>>> www.tudorgirba.com >>>>> >>>>> "What we can governs what we wish." >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Value is always contextual." >>>> >>>> >>>> >>> >>> -- >>> www.tudorgirba.com >>> >>> "Presenting is storytelling." >>> >> >> -- >> www.tudorgirba.com >> >> "No matter how many recipes we know, we still value a chef." >> >> >> >> >> >> > > -- > www.tudorgirba.com > > "From an abstract enough point of view, any two things are similar." > > > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli www.lukas-renggli.ch -------------- next part -------------- An HTML attachment was scrubbed... URL: From tudor at tudorgirba.com Tue Aug 23 20:07:55 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Tue, 23 Aug 2011 20:07:55 +0200 Subject: jquery-based slideshow? In-Reply-To: References: <3A4EAEB7-2A87-4B54-8796-3E1ACF76A26C@tudorgirba.com> <33754F1C-9DA0-4698-9D3C-6E75D8D7198E@tudorgirba.com> Message-ID: <6662B8B6-C4BD-4497-B1D7-A958F8ECE7E1@tudorgirba.com> The Cycle plugin has this functionality, but it's not yet implemented in the Pier widget. But it would be a cool addition. Cheers, Doru On 23 Aug 2011, at 20:00, Lukas Renggli wrote: > Very cool with these bullets (works even on the mobile phone). What about a slide left/right animation? > > Lukas > > On Tuesday, 23 August 2011, Tudor Girba wrote: > > One more thing. To get the navigation rendered with bullets, you can use the following CSS: > > > > #cyclerNav {text-align: center;} > > #cyclerNav a { > > display: inline-block; > > text-decoration: none; > > width: 8px; > > height: 8px; > > background: #DDDDDD; > > border-radius: 4px; > > -webkit-border-radius: 4px; > > -moz-border-radius: 4px; > > margin-left: 5px; > > text-indent: -999em;} > > #cyclerNav a.activeSlide {background: red;} > > > > Cheers, > > Doru > > > > > > On 23 Aug 2011, at 19:50, Tudor Girba wrote: > > > >> Hi, > >> > >> I added more settings to the widget. Furthermore, you can also use parameters when embedding the component to set it up dynamically. For example, you can say: > >> +/system/components/cycler|source=.|timeout=5000|effect=fade+ > >> > >> A live demo of the PQCycler in Pier can be seen at the bottom of: > >> http://www.humane-assessment.com/blog/glamorous-inspector-for-smalltalk > >> > >> Cheers, > >> Doru > >> > >> > >> On 16 Aug 2011, at 16:11, Tudor Girba wrote: > >> > >>> Hi Nick, > >>> > >>> I finally got around to play with the Cycle plugin and created a small Pier widget for it. The widget works similarly to the old Randomizer in that it takes a source structure as an input and then slideshows the children. > >>> > >>> I committed a first raw (no cycle-specific settings yet) version in the Pier-JQuery package. > >>> > >>> Cheers, > >>> Doru > >>> > >>> > >>> On 8 Jun 2011, at 17:21, Tudor Girba wrote: > >>> > >>>> Thanks, Nick. > >>>> > >>>> I will take a look. > >>>> > >>>> Cheers, > >>>> Doru > >>>> > >>>> > >>>> On 27 May 2011, at 12:54, Nick Ager wrote: > >>>> > >>>>> I don't know of anything specifically for Pier though I integrated the JQuery cycle (http://jquery.malsup.com/cycle/): > >>>>> > >>>>> ((Smalltalk at: #ConfigurationOfJQueryWidgetBox) project latestVersion) load: #('JQWidgetBox-Core' 'JQWidgetBox-Dev' 'JQWidgetBox-Cycle-Core' 'JQWidgetBox-Cycle-Dev') > >>>>> > >>>>> > >>>>> On 27 May 2011 10:53, Tudor Girba wrote: > >>>>> Hi, > >>>>> > >>>>> Has anyone produced a JQuery-based slideshow for Pier 2? > >>>>> > >>>>> Cheers, > >>>>> Doru > >>>>> > >>>>> -- > >>>>> www.tudorgirba.com > >>>>> > >>>>> "What we can governs what we wish." > >>>>> > >>>>> > >>>>> > >>>>> _______________________________________________ > >>>>> 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 > >>>> > >>>> -- > >>>> www.tudorgirba.com > >>>> > >>>> "Value is always contextual." > >>>> > >>>> > >>>> > >>> > >>> -- > >>> www.tudorgirba.com > >>> > >>> "Presenting is storytelling." > >>> > >> > >> -- > >> www.tudorgirba.com > >> > >> "No matter how many recipes we know, we still value a chef." > >> > >> > >> > >> > >> > >> > > > > -- > > www.tudorgirba.com > > > > "From an abstract enough point of view, any two things are similar." > > > > > > > > > > _______________________________________________ > > Magritte, Pier and Related Tools ... > > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > > > > -- > Lukas Renggli > www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Every thing has its own flow." From tudor at tudorgirba.com Wed Aug 24 15:03:51 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Wed, 24 Aug 2011 15:03:51 +0200 Subject: page in latest pier crashes Message-ID: <7AEAC4ED-694E-4D16-8B3B-E4444293B625@tudorgirba.com> Hi, I am having a little problem. I have upgraded humane-assessment.com to the latest Pier/Seaside, but now it crashes constantly. There is no log, it just crashes. I suspect it has something to do with a memory leak. Any idea of what can cause this issue? Or how I could investigate it? Cheers, Doru -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut." From renggli at gmail.com Wed Aug 24 15:14:25 2011 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 24 Aug 2011 15:14:25 +0200 Subject: page in latest pier crashes In-Reply-To: <7AEAC4ED-694E-4D16-8B3B-E4444293B625@tudorgirba.com> References: <7AEAC4ED-694E-4D16-8B3B-E4444293B625@tudorgirba.com> Message-ID: I don't see how a memory leak would lead to a crash, unless your application really consumes a lot of memory (you could observe that with top/htop). Are you using Cog? If so, this VM creates a crash.dmp file containing quite valuable information. Did you try reload all packages and recompile the whole image, just to be sure that all code is in consistent state? What version of Pharo are you on? If you are on Pharo 1.4 (and also to some extent 1.3) you are on untested territories. Lukas On 24 August 2011 15:03, Tudor Girba wrote: > Hi, > > I am having a little problem. I have upgraded humane-assessment.com to the latest Pier/Seaside, but now it crashes constantly. > > There is no log, it just crashes. > > I suspect it has something to do with a memory leak. Any idea of what can cause this issue? Or how I could investigate it? > > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "If you interrupt the barber while he is cutting your hair, > you will end up with a messy haircut." > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli www.lukas-renggli.ch From tudor at tudorgirba.com Wed Aug 24 15:45:03 2011 From: tudor at tudorgirba.com (Tudor Girba) Date: Wed, 24 Aug 2011 15:45:03 +0200 Subject: page in latest pier crashes In-Reply-To: References: <7AEAC4ED-694E-4D16-8B3B-E4444293B625@tudorgirba.com> Message-ID: <1E9085D5-DA56-40F9-A5C0-431520B2C7DD@tudorgirba.com> Hi, On 24 Aug 2011, at 15:14, Lukas Renggli wrote: > I don't see how a memory leak would lead to a crash, unless your > application really consumes a lot of memory (you could observe that > with top/htop). Nothing is observable when it runs. > Are you using Cog? If so, this VM creates a crash.dmp file containing > quite valuable information. I am using Cog for linux: http://www.mirandabanda.org/files/Cog/VM/VM.r2489/ There is no crash.dmp either in the image or in the vm folder. > Did you try reload all packages and recompile the whole image, just to > be sure that all code is in consistent state? No. > What version of Pharo are you on? If you are on Pharo 1.4 (and also to > some extent 1.3) you are on untested territories. At the moment, I am using Pharo 1.2.1 (12345). Cheers, Doru > Lukas > > On 24 August 2011 15:03, Tudor Girba wrote: >> Hi, >> >> I am having a little problem. I have upgraded humane-assessment.com to the latest Pier/Seaside, but now it crashes constantly. >> >> There is no log, it just crashes. >> >> I suspect it has something to do with a memory leak. Any idea of what can cause this issue? Or how I could investigate it? >> >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com >> >> "If you interrupt the barber while he is cutting your hair, >> you will end up with a messy haircut." >> >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki -- www.tudorgirba.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge." From nick.ager at gmail.com Wed Aug 24 17:24:58 2011 From: nick.ager at gmail.com (Nick Ager) Date: Wed, 24 Aug 2011 16:24:58 +0100 Subject: loading Wywsiwyg editor Message-ID: Hi, I've been working on the ConfigurationOfxxx to load the Wysiwyg editor and think I've finally made it. Starting with a clean Pharo1.3 image, I found I first needed to load a recent version of Seaside: Gofer new squeaksource: 'Seaside30'; package: 'ConfigurationOfSeaside30'; load. ConfigurationOfSeaside30 loadLatestVersion. I've added the editor configuration to ConfigurationOfPierAddOns2, so the next step is to load the configuration: Gofer new renggli: 'pier2addons'; package: 'ConfigurationOfPierAddOns2'; load. If you want to test the editor in a minimal configuration, then execute: ((Smalltalk at: #ConfigurationOfPierAddOns2) project version: '2.0.9') load: #('Pier-FileUpload-Wysiwyg'). Or if you want the editor loaded into a more complete "standard" pier installation execute: ((Smalltalk at: #ConfigurationOfPierAddOns2) project version: '2.0.9') load: #('Pier-Setup' 'Pier-FileUpload-Wysiwyg'). The Wysiwyg editor insert image/file upload, functionality requires a filter and configuration to be installed. The magic to do this is in ConfigurationOfPierAddOns2>>#initializeWysiwygEditorFileUpload: ConfigurationOfPierAddOns2>>#initializeWysiwygEditorFileUpload | pierApp | pierApp := WADispatcher default handlers at: 'pier' ifAbsent: [ | distribution | distribution := Smalltalk at: #PRDistribution ifAbsent: [ nil ]. distribution isNil ifTrue: [ (PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel named: 'defaultKernel')) ] ifFalse: [ PRPierFrame registerAsApplication: 'pier' kernel: PRDistribution new kernel ] ]. pierApp filters detect: [ :aFilter | aFilter class name = #NAFileUploadRequestHandler ] ifNone: [ pierApp addFilterFirst: NAFileUploadRequestHandler new ]. pierApp configuration addParent: NAFileUploadConfigurator instance The installation will install the required filter and configuration provided your Pier application is installed at '/pier' Editing a page should now display the Wysiwyg editor. The editor's links dialog should include a Pier site map, allowing you to easily select a link within the site. The insert image, should include a "choose file" button which will upload a file and by default store it in folder based on the location of the page within the pier site-map, by default within a folder - 'uploadedFiles' - in the image folder. The uploaded images folder can be configured within /config in the "File Upload" section. Hope this all makes sense Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick.ager at gmail.com Wed Aug 24 17:32:50 2011 From: nick.ager at gmail.com (Nick Ager) Date: Wed, 24 Aug 2011 16:32:50 +0100 Subject: page in latest pier crashes In-Reply-To: <1E9085D5-DA56-40F9-A5C0-431520B2C7DD@tudorgirba.com> References: <7AEAC4ED-694E-4D16-8B3B-E4444293B625@tudorgirba.com> <1E9085D5-DA56-40F9-A5C0-431520B2C7DD@tudorgirba.com> Message-ID: Hi Doru, I often inadvertantly cause infinite recursion by missing a "^" from one of my methods, which results in the image crashing. Could it be that you've changed some code recently that could be causing a recursion bug? Nick -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Wed Aug 24 17:33:38 2011 From: renggli at gmail.com (Lukas Renggli) Date: Wed, 24 Aug 2011 17:33:38 +0200 Subject: page in latest pier crashes In-Reply-To: <1E9085D5-DA56-40F9-A5C0-431520B2C7DD@tudorgirba.com> References: <7AEAC4ED-694E-4D16-8B3B-E4444293B625@tudorgirba.com> <1E9085D5-DA56-40F9-A5C0-431520B2C7DD@tudorgirba.com> Message-ID: >> Are you using Cog? If so, this VM creates a crash.dmp file containing >> quite valuable information. > > I am using Cog for linux: > http://www.mirandabanda.org/files/Cog/VM/VM.r2489/ The site is down for me right now, but I suspect this is one of the latest? I experienced random crashes (I thought it was related to method wrappers though) in the last few VMs too. So you might want to use an older one, see the thread with the subject " [squeak-dev] new Cog VMs available". >> Did you try reload all packages and recompile the whole image, just to >> be sure that all code is in consistent state? > > No. Do it then :-) Monticello still has bugs related to shuffling around variables. Lukas -- Lukas Renggli www.lukas-renggli.ch From mail.list at ficonab.com Sat Aug 27 17:25:23 2011 From: mail.list at ficonab.com (mail list) Date: Sat, 27 Aug 2011 23:25:23 +0800 Subject: CSS issue for Apache deployments Message-ID: <117217E2-8A3C-4AD2-B757-8D92CDE13B9F@ficonab.com> Aplogies but I am a bit new to pier so please excuse any mistakes in communications. I am using Pharo 1.3 and have pier loaded up on it nicely. (to get it all working nicely i had to install OSP process). It all works well on my local box (styles etc). I then deployed the image to an amazon linux box behind apache 2.2. This is all set up nicely and the mod_proxy and mod_rewrite are working well. The only issue i have is that the default style sheet is not presenting with the proper url. (e.g. I can login/logout of pier, all works well except for the default css style sheet associated with the environment - e.g. I get an error 404 on the default style sheet) First few paragraphs of the html page follows... If you look at the last href you will see that it is missing the http:// (so when the link is presented in the browser the browser tries to connect to: "http://testhelp.sg.estormtech.com/testhelp.sg.estormtech.com/estormhelp/a9/8bwetsf5rctr3kefd2lkty9b5mbkws/style.css" Note the repetition of the domain name due to the lack of http:// in the href Any thoughts or advice? in the pier config pages I have hostname set (test help.sg.estormtech.com) and http and base url and resource url set to / S. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jborden23 at mac.com Sat Aug 27 18:39:44 2011 From: jborden23 at mac.com (John Borden) Date: Sat, 27 Aug 2011 11:39:44 -0500 Subject: Pier demo? In-Reply-To: References: Message-ID: <18754A4B-0340-48D4-AAC0-621AC5A9C7F1@mac.com> Lately, I've been upgrading a pier wiki for my work, it is up to 6k pages, but is inside our intranet. There are some notes on the upgrade here: http://smallwiki2.seasidehosting.st/seaside/seaside/seaside/Smallwiki2/Pier-upgrades/Pier-1.2-to-2.0 Thanks, John On Aug 21, 2011, at 6:53, Lukas Renggli wrote: > Sorry, I don't have any Pier 2 images in production. The Seaside book, > the Seaside site, my personal website, ... all run in Squeak 3.9 > Kernel images with Pier 1.0 only. > > What you can try to get a moderately large site with about 160 complex > pages is to evaluate the following expression. It adds the class and > method documentation of Pier and Magritte to your kernel: > > PRKernel instances anyOne root > addChild: (PRPierFrame pageForClass: PRObject); > addChild: (PRPierFrame pageForClass: MAObject) > > Lukas > > > On 21 August 2011 13:38, Mariano Martinez Peck wrote: >> Hi guys. I am testing a import/export of Pier kernels and I would like to >> test with a real kernel (not the one included by default in Pier). I want to >> export such kernel and import it in another image. >> I have 2 pier images handly but both are quite old (pharo 1.0 and non-cog). >> I would like a new one based on Cog and Pier 2.0. >> >> Of course, the Pier image should be open-source or at least you should not >> care that I test it. >> >> so...someone has a pier image to lend me? >> >> Thanks a lot in advance. >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> >> >> _______________________________________________ >> Magritte, Pier and Related Tools ... >> https://www.iam.unibe.ch/mailman/listinfo/smallwiki >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki From renggli at gmail.com Mon Aug 29 18:50:34 2011 From: renggli at gmail.com (Lukas Renggli) Date: Mon, 29 Aug 2011 18:50:34 +0200 Subject: CSS issue for Apache deployments In-Reply-To: <117217E2-8A3C-4AD2-B757-8D92CDE13B9F@ficonab.com> References: <117217E2-8A3C-4AD2-B757-8D92CDE13B9F@ficonab.com> Message-ID: Hi S, The files of Pier in the directory "files" below the image can be served through Apache (for efficiency reasons), but by default Pier serves these files itself unless you specify a base-URL. Note that this base-URL is not the same as the URL that you specify in the Seaside configuration, it can point somewhere completely different. I suspect that "MAExternalFileModel baseUrl" is pointing to ''testhelp.sg.estormtech.com/estormhelp" in your image, but it should instead point to "http://testhelp.sg.estormtech.com/estormhelp". You can either change this value through an accessor in the workspace (see the methods and comments on the class side of MAExternalFileModel), or use the PRFileSettings widget from in the default setup. L. On 27 August 2011 17:25, mail list wrote: > Aplogies but I am a bit new to pier so please excuse any mistakes in > communications. > I am using Pharo 1.3 and have pier loaded up on it nicely. ?(to get it all > working nicely i had to install OSP process). > It all works well on my local box (styles etc). > I then deployed the image to an amazon linux box behind apache 2.2. ?This is > all set up nicely and the mod_proxy and mod_rewrite are working well. > The only issue i have is that the default style sheet is not presenting with > the proper url. ?(e.g. I can login/logout of pier, all works well except for > ?the default css style sheet associated with the environment ?- e.g. I get > an error 404 on the default style sheet) > First few paragraphs of the html page follows... > > href="http://testhelp.sg.estormtech.com/files/PRBlueprintLibrary/screen.css"/> rel="stylesheet" type="text/css" media="print" > href="http://testhelp.sg.estormtech.com/files/PRBlueprintLibrary/print.css"/> rel="stylesheet" type="text/css" > href="http://testhelp.sg.estormtech.com/files/WADevelopmentFiles/development.css"/> name="generator" content="Pier - Magritte - Seaside"/> type="text/css" > href="testhelp.sg.estormtech.com/estormhelp/a9/8bwetsf5rctr3kefd2lkty9b5mbkws/style.css"/> > If you look at the last href you will see that it is missing the http:// (so > when the link is presented in the browser the browser tries to connect to: > "http://testhelp.sg.estormtech.com/testhelp.sg.estormtech.com/estormhelp/a9/8bwetsf5rctr3kefd2lkty9b5mbkws/style.css" > Note the repetition of the domain name due to the lack of http:// in the > href > Any thoughts or advice? > in the pier config pages I have hostname set (test help.sg.estormtech.com) > and http and base url and resource url set to / > S. > > > _______________________________________________ > Magritte, Pier and Related Tools ... > https://www.iam.unibe.ch/mailman/listinfo/smallwiki > -- Lukas Renggli www.lukas-renggli.ch From nick.ager at gmail.com Tue Aug 30 18:04:13 2011 From: nick.ager at gmail.com (Nick Ager) Date: Tue, 30 Aug 2011 17:04:13 +0100 Subject: loading Wywsiwyg editor In-Reply-To: References: Message-ID: Hi, I've come across some odd behaviour when using the Wysiwyg editor on Pharo when using the Swazoo Adaptor. There are some very strange effects with ajax calls and the Swazoo adaptor which I've yet to characterise. So if you try the Wysiwyg editor with Pharo be sure to use the Comanche Adapter rather than the Swazoo Adapter. Ideally we'd use the Zinc adapter, though I haven't tested with it and I guess we should change the ConfigurationOfSeaside30 to load the Zinc adapter on Pharo 1.3.... There are also various fixes which have been added: - fix to file-uploading paths on Windows (thanks to Bart Veenstra) - improved error reporting for file-upload errors - moved the registration code (for the filter and configuration instance) to class side of PRFileUploadWysiwygEditorBase. see #initializeWysiwygEditorFileUpload* Nick On 24 August 2011 16:24, Nick Ager wrote: > Hi, > > I've been working on the ConfigurationOfxxx to load the Wysiwyg editor and > think I've finally made it. > > Starting with a clean Pharo1.3 image, I found I first needed to load a > recent version of Seaside: > > Gofer new > squeaksource: 'Seaside30'; > package: 'ConfigurationOfSeaside30'; > load. > ConfigurationOfSeaside30 loadLatestVersion. > > > I've added the editor configuration to ConfigurationOfPierAddOns2, so the > next step is to load the configuration: > > Gofer new > renggli: 'pier2addons'; > package: 'ConfigurationOfPierAddOns2'; > load. > > > If you want to test the editor in a minimal configuration, then execute: > > ((Smalltalk at: #ConfigurationOfPierAddOns2) project version: '2.0.9') > load: #('Pier-FileUpload-Wysiwyg'). > > > Or if you want the editor loaded into a more complete "standard" pier > installation execute: > > ((Smalltalk at: #ConfigurationOfPierAddOns2) project version: '2.0.9') > load: #('Pier-Setup' 'Pier-FileUpload-Wysiwyg'). > > > The Wysiwyg editor insert image/file upload, functionality requires a > filter and configuration to be installed. The magic to do this is > in ConfigurationOfPierAddOns2>>#initializeWysiwygEditorFileUpload: > > ConfigurationOfPierAddOns2>>#initializeWysiwygEditorFileUpload > | pierApp | > pierApp := WADispatcher default handlers at: 'pier' ifAbsent: [ > | distribution | > distribution := Smalltalk at: #PRDistribution ifAbsent: [ nil ]. > distribution isNil > ifTrue: [ > (PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel named: > 'defaultKernel')) ] > ifFalse: [ > PRPierFrame registerAsApplication: 'pier' kernel: PRDistribution new kernel > ] ]. > pierApp filters detect: [ :aFilter | aFilter class name = > #NAFileUploadRequestHandler ] ifNone: [ pierApp addFilterFirst: > NAFileUploadRequestHandler new ]. > pierApp configuration addParent: NAFileUploadConfigurator instance > > The installation will install the required filter and configuration > provided your Pier application is installed at '/pier' > > Editing a page should now display the Wysiwyg editor. The editor's links > dialog should include a Pier site map, allowing you to easily select a link > within the site. The insert image, should include a "choose file" button > which will upload a file and by default store it in folder based on the > location of the page within the pier site-map, by default within a folder - > 'uploadedFiles' - in the image folder. The uploaded images folder can be > configured within /config in the "File Upload" section. > > Hope this all makes sense > > Nick > > > > > > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From renggli at gmail.com Tue Aug 30 18:29:52 2011 From: renggli at gmail.com (Lukas Renggli) Date: Tue, 30 Aug 2011 18:29:52 +0200 Subject: loading Wywsiwyg editor In-Reply-To: References: Message-ID: > I've come across some odd behaviour when using the?Wysiwyg editor on Pharo > when using the?Swazoo Adaptor. There are some?very strange effects with ajax > calls and the Swazoo adaptor which I've yet to characterize. I think there were some issues reported with Swazoo (or the Seaside-Swazoo adaptor) that would double encode some URL field. I guess that could lead to strange effects when using AJAX. > So if you try the Wysiwyg editor with Pharo be sure to use the Comanche > Adapter rather than the Swazoo Adapter. > Ideally we'd use the Zinc adapter, though I haven't tested with it and I > guess we should change the ConfigurationOfSeaside30 to load the Zinc adapter > on Pharo 1.3.... Zinc works very well and it is included with Pharo anyway. Lukas -- Lukas Renggli www.lukas-renggli.ch