November 2013 - Pharo-users

Re: [Pharo-users] Any configuration file parsing library

by StÃ©phane Ducasse

Use Ston it is cool and simple. Stef On Nov 28, 2013, at 3:10 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Thu, Nov 28, 2013 at 2:39 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> I'm looking for a library to parse configuration files. > > > My colleagues thought using STON could be a good idea. Would you use > STON to write a configuration file? > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Nov. 29, 2013

Re: [Pharo-users] reporting bugs

by StÃ©phane Ducasse

***EXCELLENT*** On Nov 28, 2013, at 11:13 AM, phil(a)highoctane.be wrote: > Due to the somewhat unclear process, I updated the issue tracking page with some details about registration along with pictures. > > http://www.pharo-project.org/community/issue-tracking > > Tell me if you see things that aren't right. > > Phil > > > > > On Thu, Nov 28, 2013 at 10:42 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > On 28 Nov 2013, at 10:28, Nicolai Hess <nicolaihess(a)web.de> wrote: > >> Thank you all for your help. >> I already tried http://bugs.pharo.org/issues/register (month ago and now again),but nothing happened. >> I missed that part where I have to use "forgot password" to even get an initial password. >> Can you write this important part right on the initial fogbugz page. For those people who don't >> watch tutorial videos :-) > > Yes, also I couldnât make my me.com mail to work. I hope that soon we will have normal bug tracker :) > > Uko > >> >> >> >> >> 2013/11/28 Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> >> There is also this perm link :) >> >> http://bugs.pharo.org/issues/register >> >> Ben >> >> On 28 Nov 2013, at 09:45, phil(a)highoctane.be wrote: >> >>> http://bugs.pharo.org/issues/ >>> >>> Register link on top: You can register to the FogBugz issue tracker here. >>> >>> Enjoy, >>> >>> --- >>> Philippe Back >>> Dramatic Performance Improvements >>> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 >>> Mail:phil@highoctane.be | Web: http://philippeback.eu >>> Blog: http://philippeback.be | Twitter: @philippeback >>> Youtube: http://www.youtube.com/user/philippeback/videos >>> >>> High Octane SPRL >>> rue cour Boisacq 101 | 1301 Bierges | Belgium >>> >>> Pharo Consortium Member - http://consortium.pharo.org/ >>> Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com >>> Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller >>> >>> >>> >>> >>> On Thu, Nov 28, 2013 at 9:19 AM, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> What do I have to do for getting access to pharo.fogbugz.com for bug reporting? >>> >>> regards >>> Nicolai >>> >>> >> >> > >

Nov. 29, 2013

Finalization

by Sean P. DeNigris

I found the following list threads... http://forum.world.st/Finalization-question-td1300962.html mentions #beFinalizable, which doesn't seem to exist. I guess it was just an example, but seems like it should be added, no? In http://forum.world.st/object-finalization-td3771196.html Igor suggested that the key is to do: WeakRegistry default add: obj. This guarantees? that #finalize will be called when the object is garbage collected. I'm asking regarding my recent work wrapping the FMOD sound library with NativeBoost. I'm thinking my NBExternalObjects should release their resources when no longer referenced. I want to say: FmodSound>>#finalize self primReleaseSound: handle. So I've pieced together that I would have to also write: FmodSound>>new instance := super new whatever; beFinalizable; yourself. Object>>#beFinalizable WeakRegistry default add: self. Am I correct that: 1. The above code would cause the resource to be safely released when the sound object was garbage collected? 2. This approach would be a good way to manage these types of resources? Any hints would be appreciated as to the best way to accomplish managing these... Thanks! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Finalization-tp4726046.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Nov. 29, 2013

Re: [Pharo-users] Snap4Arduino pre-alpha release

by Bernat Romagosa

Thanks Phil! Weird about the mailto link, it does work for me both on Chrome and FF... I'll take a look! :) And about the manual, I didn't even know the link was there! This comes straight from Snap!, but I guess I'd better override it too! Glad you like it! 2013/11/28 phil(a)highoctane.be <phil(a)highoctane.be> > Just note that the bug reporting is broken on the web page... > > It tries to reach > mailto:scratch@citilab.eu?subject=Snap4Arduino%20Bug%20Report&body=Operating%20System:%0D%0AWeb%20Browser,%20and%20version:%0D%0ASnap4Arduino%20version:%0D%0ASteps%20to%20follow%20in%20order%20to%20reproduce%20the%20problem:%0D%0AAdditional%20notes:<scratch@citilab.eu?subject=Snap4Arduino%20Bug%20Report&body=Operating%20System:%0D%0AWeb%20Browser,%20and%20version:%0D%0ASnap4Arduino%20version:%0D%0ASteps%20to%20follow%20in%20order%20to%20reproduce%20the%20problem:%0D%0AAdditional%20notes:> > > which doesn't work. (Chrome here). > > Also, reference manual is missing: > http://localhost:8080/help/SnapManual.pdf not fouind. > > Other than that, sweet stuff. I like the traybar thing :-) > > Phil > > > On Thu, Nov 28, 2013 at 6:01 PM, Bernat Romagosa < > tibabenfortlapalanca(a)gmail.com> wrote: > >> Hi list! >> >> I know people don't usually make announcements of this kind here, but >> I've gotten much help from this list on SerialPlugin and NativeBoost >> questions, so I wanted to let you know I've managed to release the >> pre-alpha version of Snap4Arduino. >> >> Snap! is a Scratch reimplementation written in Javascript by Jens MÃ¶nig >> and Brian Harvey, with advanced programming concepts such as first order >> functions, closures or continuations. As Brian Harvey puts it: >> >> *In the glory days of the MIT Logo Lab, we used to say, âLogo is Lisp >>> disguised as BASIC.â Now, with its first class procedures, lexical scope, >>> and first class continuations, Snap! is Scheme disguised as Scratch.* >> >> >> Snap4Arduino is a modification of Snap! plus a server written in Pharo >> that allow you to live-program Arduino boards very easily. >> >> http://s4a.cat/snap >> >> I've used Zinc as a web and websockets server, and the Arduino package to >> achieve communication with the board. >> >> I've decided to not wait for the MacOS CogVM serial port bugfix because I >> really wanted to release something before the end of November, but >> everything else is in place, so once the VM is fixed, it'll be just plug >> and release! :) >> >> Thanks a lot for your help! >> >> -- >> Bernat Romagosa. >> > > -- Bernat Romagosa.

Nov. 28, 2013

Re: [Pharo-users] Snap4Arduino pre-alpha release

by phil＠highoctane.be

Just note that the bug reporting is broken on the web page... It tries to reach mailto:scratch@citilab.eu?subject=Snap4Arduino%20Bug%20Report&body=Operating%20System:%0D%0AWeb%20Browser,%20and%20version:%0D%0ASnap4Arduino%20version:%0D%0ASteps%20to%20follow%20in%20order%20to%20reproduce%20the%20problem:%0D%0AAdditional%20notes:<scratch@citilab.eu?subject=Snap4Arduino%20Bug%20Report&body=Operating%20System:%0D%0AWeb%20Browser,%20and%20version:%0D%0ASnap4Arduino%20version:%0D%0ASteps%20to%20follow%20in%20order%20to%20reproduce%20the%20problem:%0D%0AAdditional%20notes:> which doesn't work. (Chrome here). Also, reference manual is missing: http://localhost:8080/help/SnapManual.pdf not fouind. Other than that, sweet stuff. I like the traybar thing :-) Phil On Thu, Nov 28, 2013 at 6:01 PM, Bernat Romagosa < tibabenfortlapalanca(a)gmail.com> wrote: > Hi list! > > I know people don't usually make announcements of this kind here, but I've > gotten much help from this list on SerialPlugin and NativeBoost questions, > so I wanted to let you know I've managed to release the pre-alpha version > of Snap4Arduino. > > Snap! is a Scratch reimplementation written in Javascript by Jens MÃ¶nig > and Brian Harvey, with advanced programming concepts such as first order > functions, closures or continuations. As Brian Harvey puts it: > > *In the glory days of the MIT Logo Lab, we used to say, âLogo is Lisp >> disguised as BASIC.â Now, with its first class procedures, lexical scope, >> and first class continuations, Snap! is Scheme disguised as Scratch.* > > > Snap4Arduino is a modification of Snap! plus a server written in Pharo > that allow you to live-program Arduino boards very easily. > > http://s4a.cat/snap > > I've used Zinc as a web and websockets server, and the Arduino package to > achieve communication with the board. > > I've decided to not wait for the MacOS CogVM serial port bugfix because I > really wanted to release something before the end of November, but > everything else is in place, so once the VM is fixed, it'll be just plug > and release! :) > > Thanks a lot for your help! > > -- > Bernat Romagosa. >

Nov. 28, 2013

Re: [Pharo-users] Snap4Arduino pre-alpha release

by Bernat Romagosa

Nice! :) Feedback will be very much appreciated! (Please note you need to install Standard Firmata into your board first) 2013/11/28 phil(a)highoctane.be <phil(a)highoctane.be> > Hey cool. > > I'll try that with my board. (Arduino Uno). > > Phil > > > > On Thu, Nov 28, 2013 at 6:01 PM, Bernat Romagosa < > tibabenfortlapalanca(a)gmail.com> wrote: > >> Hi list! >> >> I know people don't usually make announcements of this kind here, but >> I've gotten much help from this list on SerialPlugin and NativeBoost >> questions, so I wanted to let you know I've managed to release the >> pre-alpha version of Snap4Arduino. >> >> Snap! is a Scratch reimplementation written in Javascript by Jens MÃ¶nig >> and Brian Harvey, with advanced programming concepts such as first order >> functions, closures or continuations. As Brian Harvey puts it: >> >> *In the glory days of the MIT Logo Lab, we used to say, âLogo is Lisp >>> disguised as BASIC.â Now, with its first class procedures, lexical scope, >>> and first class continuations, Snap! is Scheme disguised as Scratch.* >> >> >> Snap4Arduino is a modification of Snap! plus a server written in Pharo >> that allow you to live-program Arduino boards very easily. >> >> http://s4a.cat/snap >> >> I've used Zinc as a web and websockets server, and the Arduino package to >> achieve communication with the board. >> >> I've decided to not wait for the MacOS CogVM serial port bugfix because I >> really wanted to release something before the end of November, but >> everything else is in place, so once the VM is fixed, it'll be just plug >> and release! :) >> >> Thanks a lot for your help! >> >> -- >> Bernat Romagosa. >> > > -- Bernat Romagosa.

Nov. 28, 2013

Re: [Pharo-users] Snap4Arduino pre-alpha release

by phil＠highoctane.be

Hey cool. I'll try that with my board. (Arduino Uno). Phil On Thu, Nov 28, 2013 at 6:01 PM, Bernat Romagosa < tibabenfortlapalanca(a)gmail.com> wrote: > Hi list! > > I know people don't usually make announcements of this kind here, but I've > gotten much help from this list on SerialPlugin and NativeBoost questions, > so I wanted to let you know I've managed to release the pre-alpha version > of Snap4Arduino. > > Snap! is a Scratch reimplementation written in Javascript by Jens MÃ¶nig > and Brian Harvey, with advanced programming concepts such as first order > functions, closures or continuations. As Brian Harvey puts it: > > *In the glory days of the MIT Logo Lab, we used to say, âLogo is Lisp >> disguised as BASIC.â Now, with its first class procedures, lexical scope, >> and first class continuations, Snap! is Scheme disguised as Scratch.* > > > Snap4Arduino is a modification of Snap! plus a server written in Pharo > that allow you to live-program Arduino boards very easily. > > http://s4a.cat/snap > > I've used Zinc as a web and websockets server, and the Arduino package to > achieve communication with the board. > > I've decided to not wait for the MacOS CogVM serial port bugfix because I > really wanted to release something before the end of November, but > everything else is in place, so once the VM is fixed, it'll be just plug > and release! :) > > Thanks a lot for your help! > > -- > Bernat Romagosa. >

Nov. 28, 2013

Snap4Arduino pre-alpha release

by Bernat Romagosa

Hi list! I know people don't usually make announcements of this kind here, but I've gotten much help from this list on SerialPlugin and NativeBoost questions, so I wanted to let you know I've managed to release the pre-alpha version of Snap4Arduino. Snap! is a Scratch reimplementation written in Javascript by Jens MÃ¶nig and Brian Harvey, with advanced programming concepts such as first order functions, closures or continuations. As Brian Harvey puts it: *In the glory days of the MIT Logo Lab, we used to say, âLogo is Lisp > disguised as BASIC.â Now, with its first class procedures, lexical scope, > and first class continuations, Snap! is Scheme disguised as Scratch.* Snap4Arduino is a modification of Snap! plus a server written in Pharo that allow you to live-program Arduino boards very easily. http://s4a.cat/snap I've used Zinc as a web and websockets server, and the Arduino package to achieve communication with the board. I've decided to not wait for the MacOS CogVM serial port bugfix because I really wanted to release something before the end of November, but everything else is in place, so once the VM is fixed, it'll be just plug and release! :) Thanks a lot for your help! -- Bernat Romagosa.

Nov. 28, 2013

Re: [Pharo-users] Any configuration file parsing library

by GÃ¶ran Krampe

On 11/28/2013 04:37 PM, Esteban A. Maringolo wrote: > Why not a simple JSON file? > > It's utter simple to parse. That was already mentioned :) Although in many cases an ini file is easier for non-devs than a JSON file. No, really, it is. Really. :) regards, GÃ¶ran

Nov. 28, 2013

Re: [Pharo-users] Any configuration file parsing library

by Esteban A. Maringolo

Why not a simple JSON file? It's utter simple to parse. Esteban A. Maringolo 2013/11/28 GÃ¶ran Krampe <goran(a)krampe.se> > Hi! > > > On 11/28/2013 02:39 PM, Damien Cassou wrote: > >> Hi, >> >> I'm looking for a library to parse configuration files. I have no >> configuration format yet so I'm open. I was thinking of a typical INI >> format: >> >> [section1] >> param1=value1 >> param2=value2 >> >> [section2] >> param1=value3 >> ... >> > > In Gjallar we used the ini format and it often works just fine for > "settings". :) > > But just to throw in something from the sideline, Tirade is also quite > nifty: > > "Section 1" > param1: 'value1'. > param2: 123. > > "Section 2" > blabla: $a. > > > ...as you can see it is "just Smalltalk messages". One disadvantage of > Tirade > would be that you need to remember the "." at the end of each message. > > An advantage is that you don't need to "parse it", you just implement the > messages in some class and then you can use the the reader in Tirade to > just "feed" those messages to that object. > > More info: http://goran.krampe.se/category/tirade/ > > regards, GÃ¶ran > > > >

Nov. 28, 2013