February 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] shorten petitparser expressions

by Frank Shearar

On 28 February 2012 16:50, Fabrizio Perin <fabrizio.perin(a)gmail.com> wrote: > Hi, > I think the reason is for consistency. > If fact I like as it is now for that reason. > > $a asParser / $b asParser / #foo asParser "It looks clear to me and is > consistent." > > a asParser / $b / #foo "it looks odd because it is inconsistent." > > Anyway, for such simple parsers you loose consistency and you don't gain > much. If you have to deal with longer statements, if you have to make your > parsers reusable or simply to make your simple example cleaner for real, you > should have separate methods: > a > ^$a asParser > > b > ^$b asParser > > foo > ^#foo asParser > > a / b / foo " this is cleaner and consistent" > > I hope I made my point. > > Cheers, > Fabrizio > > "Consistency, Consistency, Consistency" I've often used #anyOf: - anyOf: someTokens "Writing without a compiler; may actually still work!" ^ someTokens allButFirst inject: someTokens first into: [:acc :each | acc / each asParser] self anyOf: #($a $b #foo). frank > 2012/2/28 Igor Stasenko <siguctua(a)gmail.com> >> >> Why i need to put #asParser everywhere? >> >> $a asParser / $b asParser / #foo asParser >> >> >> a proper implementation of #/ makes the above to just: >> >> $a asParser / $b / #foo >> >> which is much more cleaner and convenient. >> >> Or, is there a reason to not send #asParser to every argument where >> parser expected? >> >> >> -- >> Best regards, >> Igor Stasenko. >> >

Feb. 28, 2012

Re: [Pharo-project] shorten petitparser expressions

by Fabrizio Perin

Hi, I think the reason is for consistency. If fact I like as it is now for that reason. $a asParser / $b asParser / #foo asParser "It looks clear to me and is consistent." a asParser / $b / #foo "it looks odd because it is inconsistent." Anyway, for such simple parsers you loose consistency and you don't gain much. If you have to deal with longer statements, if you have to make your parsers reusable or simply to make your simple example cleaner for real, you should have separate methods: a ^$a asParser b ^$b asParser foo ^#foo asParser a / b / foo " this is cleaner and consistent" I hope I made my point. Cheers, Fabrizio "Consistency, Consistency, Consistency" 2012/2/28 Igor Stasenko <siguctua(a)gmail.com> > Why i need to put #asParser everywhere? > > $a asParser / $b asParser / #foo asParser > > > a proper implementation of #/ makes the above to just: > > $a asParser / $b / #foo > > which is much more cleaner and convenient. > > Or, is there a reason to not send #asParser to every argument where > parser expected? > > > -- > Best regards, > Igor Stasenko. > >

Feb. 28, 2012

Re: [Pharo-project] [Pharo-users] Who is using Fuel?

by Norbert Hartl

Am 28.02.2012 um 17:23 schrieb Mariano Martinez Peck: > > > On Tue, Feb 28, 2012 at 5:03 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 28.02.2012 um 16:41 schrieb Mariano Martinez Peck: > >> Of course, not the fuel you use to go to work every day ;) I am talking about Fuel serializer. >> In particular, I wonder if our page deserves an update: rmod.lille.inria.fr/web/pier/software/Fuel/Software-using-Fuel >> >> Let me know if there is something I should add. >> > We are using it in > > http://www.2denker.de/product/apitester > > I first used image persistence but the image grow to large. Then I added fuel as journal to be written before image save in order to be able to recover from an emergency. > > I didn't undersantd this one. What is what you are serializing that you want to be able to recover in case of an emergency? All of my data. An account can log in and configure the service. The service collects data. All of these modifications should be persisted. I experience image corruption with big images. Every week or so the vm just didn't start the images anymore because it stated "premature end of image file". So I write down all my objects via fuel to disk before I save the image. In case of an emergency (image corruption) I take a fresh image and load back the saved fuel graph. And within 2 minutes I'm once read to go. Now the big parts of the data are in mongo so I don't expect it to happen real soon again. > > Now we redo the persistence part. An account object graph is dissected into configuration part and payload part. The payload is written directly to mongo db in a Json format. The configuration part will be written as fuel blob to mongo. Planned is that at startup a configured amount of account fuel blobs are loaded and started. Those configurations have their own processes that write back payload to mongo. Etc. > > > Just in case you want to know :) > > > Interested indeed :) I added it under "Custom applications" > thanks, Norbert

Feb. 28, 2012

Re: [Pharo-project] [Pharo-users] Who is using Fuel?

by Sven Van Caekenberghe

On 28 Feb 2012, at 17:03, Norbert Hartl wrote: > Am 28.02.2012 um 16:41 schrieb Mariano Martinez Peck: > >> Of course, not the fuel you use to go to work every day ;) I am talking about Fuel serializer. >> In particular, I wonder if our page deserves an update: rmod.lille.inria.fr/web/pier/software/Fuel/Software-using-Fuel >> >> Let me know if there is something I should add. >> > We are using it in > > http://www.2denker.de/product/apitester > > I first used image persistence but the image grow to large. Then I added fuel as journal to be written before image save in order to be able to recover from an emergency. > Now we redo the persistence part. An account object graph is dissected into configuration part and payload part. The payload is written directly to mongo db in a Json format. The configuration part will be written as fuel blob to mongo. Planned is that at startup a configured amount of account fuel blobs are loaded and started. Those configurations have their own processes that write back payload to mongo. Etc. > > Just in case you want to know :) > > Norbert Cool and interesting. Yes, we want to know about stuff like that ! Sven

Feb. 28, 2012

Re: [Pharo-project] [Pharo-users] Who is using Fuel?

by Mariano Martinez Peck

On Tue, Feb 28, 2012 at 5:03 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > > Am 28.02.2012 um 16:41 schrieb Mariano Martinez Peck: > > Of course, not the fuel you use to go to work every day ;) I am talking > about Fuel serializer. > In particular, I wonder if our page deserves an update: > rmod.lille.inria.fr/web/pier/software/Fuel/Software-using-Fuel > > Let me know if there is something I should add. > > We are using it in > > http://www.2denker.de/product/apitester > > I first used image persistence but the image grow to large. Then I added > fuel as journal to be written before image save in order to be able to > recover from an emergency. > I didn't undersantd this one. What is what you are serializing that you want to be able to recover in case of an emergency? > Now we redo the persistence part. An account object graph is dissected > into configuration part and payload part. The payload is written directly > to mongo db in a Json format. The configuration part will be written as > fuel blob to mongo. Planned is that at startup a configured amount of > account fuel blobs are loaded and started. Those configurations have their > own processes that write back payload to mongo. Etc. > > > Just in case you want to know :) > > Interested indeed :) I added it under "Custom applications" Thanks! -- Mariano http://marianopeck.wordpress.com

Feb. 28, 2012

Re: [Pharo-project] [Pharo-users] Who is using Fuel?

by Norbert Hartl

Am 28.02.2012 um 16:41 schrieb Mariano Martinez Peck: > Of course, not the fuel you use to go to work every day ;) I am talking about Fuel serializer. > In particular, I wonder if our page deserves an update: rmod.lille.inria.fr/web/pier/software/Fuel/Software-using-Fuel > > Let me know if there is something I should add. > We are using it in http://www.2denker.de/product/apitester I first used image persistence but the image grow to large. Then I added fuel as journal to be written before image save in order to be able to recover from an emergency. Now we redo the persistence part. An account object graph is dissected into configuration part and payload part. The payload is written directly to mongo db in a Json format. The configuration part will be written as fuel blob to mongo. Planned is that at startup a configured amount of account fuel blobs are loaded and started. Those configurations have their own processes that write back payload to mongo. Etc. Just in case you want to know :) Norbert

Feb. 28, 2012

[Pharo-project] Who is using Fuel?

by Mariano Martinez Peck

Of course, not the fuel you use to go to work every day ;) I am talking about Fuel serializer. In particular, I wonder if our page deserves an update: rmod.lille.inria.fr/web/pier/software/Fuel/Software-using-Fuel Let me know if there is something I should add. Thanks, -- Mariano http://marianopeck.wordpress.com

Feb. 28, 2012

Re: [Pharo-project] [squeak-dev] can this be done via modification to the Squeak/Pharo IDE?

by Dave Mason

I was wondering exactly the same thing! On 2012-Feb-27, at 18:46 , Lawson English wrote: > http://vimeo.com/36579366

Feb. 28, 2012

Re: [Pharo-project] VNC client

by Norbert Hartl

Am 28.02.2012 um 15:30 schrieb Andreas Wacknitz: > > Am 28.02.2012 um 14:06 schrieb Norbert Hartl: > >> I wonder what vnc client do you use if you use pharo + RFB? I had a running via macports. Now that I'm about to switch to homebrew I have problems finding a working one. Be it in brew or app store, etc. >> >> thanks, >> >> Norbert > Norbert, > > there is a free VNC client coming with every Mac OS X. It's hidden in the folder /System/Library/CoreServices. > The name is "Screen Sharing.app" (or with German localisation: "Bildschirmfreigabe"). > Nowadays I am using Remote Desktop application (64â¬ in AppStore). > I don't know whether it's working with RFB, though. > Nope, it isn't working. That was the first one I tried. Norbert

Feb. 28, 2012

Re: [Pharo-project] VNC client

by Andreas Wacknitz

Am 28.02.2012 um 14:06 schrieb Norbert Hartl: > I wonder what vnc client do you use if you use pharo + RFB? I had a running via macports. Now that I'm about to switch to homebrew I have problems finding a working one. Be it in brew or app store, etc. > > thanks, > > Norbert Norbert, there is a free VNC client coming with every Mac OS X. It's hidden in the folder /System/Library/CoreServices. The name is "Screen Sharing.app" (or with German localisation: "Bildschirmfreigabe"). Nowadays I am using Remote Desktop application (64â¬ in AppStore). I don't know whether it's working with RFB, though. Regards, Andreas

Feb. 28, 2012