- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Congratulation Doru Tudor GÃ®rba!

by Max Leske

Congratulations Doru! Well deserved! On 10.04.2014, at 16:57, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Dear colleges and friends, > > It is a great pleasure for me to send this email. > A couple of days ago AITO officially announced that the junior prize of the AITO Dahl-Nygaard Prize Winners is given to Doru, Tudor GÃ®rba. The award will be given at the ECOOP conference, this year, in Uppsala, Sweden. AITO is the non-profit organization who is behind ECOOP. > > The prestigious Dahl-Nygaard award is given to "individuals that have made significant technical contributions to the field of Object-Orientationâ. ECOOP is the high-caliber European conference on object-orientation. The European version of OOPSLA. > > I have known Doru for year, when we were doing our PhD in Bern under the supervision of StÃ©phane Ducasse and Oscar Nierstrasz. Doruâs work and ideas have had a great impact on the Pharo and Smalltalk community. > > Doru is member of the Pharo board. Doru authored Glamour, GTToolKit and many more applications. Doru is not only a great researcher, a great engineer or a great speaker. He is also a great leader. Doru is the main architect of the Moose effort, and a great coordinator in the Moose and Pharo communities. Doru authored Humane Assessment, "the method for making software engineering decisions". > > Doruâs work has had a great impact on my personal work. Roassal is an extension of the ideas first presented in Mondrian, which was first authored by Doru and his student around 2005. Without Doru, Moose would not be as it is now. > > Doru, we are happy to have you with us! This international recognition will drag up all of us. > > Links: > http://www.tudorgirba.com > http://www.humane-assessment.com > http://www.aito.org/Dahl-Nygaard/2014.html > > Big big clap! > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

April 10, 2014

Congratulation Doru Tudor GÃ®rba!

by Alexandre Bergel

Dear colleges and friends, It is a great pleasure for me to send this email. A couple of days ago AITO officially announced that the junior prize of the AITO Dahl-Nygaard Prize Winners is given to Doru, Tudor GÃ®rba. The award will be given at the ECOOP conference, this year, in Uppsala, Sweden. AITO is the non-profit organization who is behind ECOOP. The prestigious Dahl-Nygaard award is given to "individuals that have made significant technical contributions to the field of Object-Orientationâ. ECOOP is the high-caliber European conference on object-orientation. The European version of OOPSLA. I have known Doru for year, when we were doing our PhD in Bern under the supervision of StÃ©phane Ducasse and Oscar Nierstrasz. Doruâs work and ideas have had a great impact on the Pharo and Smalltalk community. Doru is member of the Pharo board. Doru authored Glamour, GTToolKit and many more applications. Doru is not only a great researcher, a great engineer or a great speaker. He is also a great leader. Doru is the main architect of the Moose effort, and a great coordinator in the Moose and Pharo communities. Doru authored Humane Assessment, "the method for making software engineering decisions". Doruâs work has had a great impact on my personal work. Roassal is an extension of the ideas first presented in Mondrian, which was first authored by Doru and his student around 2005. Without Doru, Moose would not be as it is now. Doru, we are happy to have you with us! This international recognition will drag up all of us. Links: http://www.tudorgirba.com http://www.humane-assessment.com http://www.aito.org/Dahl-Nygaard/2014.html Big big clap! Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 10, 2014

Re: [Pharo-dev] SqNumberParser and PGConnection in Pharo 3

by Sven Van Caekenberghe

And you are in DBXTalk now On 10 Apr 2014, at 16:15, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > I'm emaringolo@* :D > > Regards! > > Esteban A. Maringolo > > > 2014-04-10 11:13 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: >> >> On 10 Apr 2014, at 16:08, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >>> Can we coordinate efforts here? >>> Can I at least have writing rights to GlorpDBX and PostgresV2 repos? :) >> >> What is your StHub username ? >> I can add you to DBXTalk I think. >> >

April 10, 2014

Re: [Pharo-dev] SqNumberParser and PGConnection in Pharo 3

by Esteban A. Maringolo

I'm emaringolo@* :D Regards! Esteban A. Maringolo 2014-04-10 11:13 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 10 Apr 2014, at 16:08, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > >> Can we coordinate efforts here? >> Can I at least have writing rights to GlorpDBX and PostgresV2 repos? :) > > What is your StHub username ? > I can add you to DBXTalk I think. >

April 10, 2014

Re: [Pharo-dev] SqNumberParser and PGConnection in Pharo 3

by Sven Van Caekenberghe

On 10 Apr 2014, at 16:08, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: > Can we coordinate efforts here? > Can I at least have writing rights to GlorpDBX and PostgresV2 repos? :) What is your StHub username ? I can add you to DBXTalk I think.

April 10, 2014

Re: [Pharo-dev] SqNumberParser and PGConnection in Pharo 3

by Esteban A. Maringolo

Thanks for the translation Sven :) Can we coordinate efforts here? Can I at least have writing rights to GlorpDBX and PostgresV2 repos? :) Regards! Esteban A. Maringolo 2014-04-10 4:28 GMT-03:00 Sven Van Caekenberghe <sven(a)stfx.eu>: > > On 10 Apr 2014, at 09:08, Marcus Denker <marcus.denker(a)inria.fr> wrote: > >> >> On 09 Apr 2014, at 22:49, Esteban A. Maringolo <emaringolo(a)gmail.com> wrote: >> >>> So SqNumberParser is gone in Pharo 3. >>> >>> And the nextDateAndTimeFrom: in PGConnection refers to it... I >>> replaced it by plain NumberParser and it seems to continue working. >>> >>> What is the approach here to have a "squeak compatible" PGConnection? >>> Add an empty SqNumberClass as subclass NumberParser? >>> >>> >> what even is PGConnection? >> >> Marcus > > It is part of the native Postgresql driver (PostgresV2). > > His question comes down to: if I change it this way, it will break for Squeak, what should I do ? > > In this case, a common code base would be preferred I guess, but we'll need platform specific stuff that was not needed up to now. > > Svenk

April 10, 2014

Re: [Pharo-dev] ghost windows

by Johan Brichau

Thanks Carlo, that works very well indeed. Johan On 07 Apr 2014, at 22:25, Carlo <snoobabk(a)gmail.com> wrote: > Hi > > Try holding down shift and then right click on the world (or in a workspace execute: âWorld findWindow: nil.â). A âfind windowâ pop-up should appear. Look through the PanelMorphs by selecting each one and the haloâs should appear. If you find the correct one then delete it and it should be removed. > > Tested in Pharo1.3 and Pharo3 and works for me. > Cheers > Carlo > > > On 07 Apr 2014, at 2:28 PM, Ben Coman <btc(a)openInWorld.com> wrote: > > I has this happen to me quite a while ago. > http://forum.world.st/old-windows-in-image-not-responding-td3922341.html > > As well as the suggestion there, you might also try... > SystemWindows allInstances [ :w | w delete ]. > > cheers -ben > > Johan Brichau wrote: >> Hi there, >> >> I often get in a situation where 'ghost windows' remain in the Pharo window (see screenshot). >> These windows are closed (see taskbar) and I cannot select nor click these ghost windows to remove them. >> >> Is there a way to remove them programmatically? >> They cause visual clutter when working with multiple real windows and I do not want to rebuild an entire development image each time this occurs. >> >> Though this is in Pharo3, I think I occassionally had these in Pharo1.4 as well. >> >> cheers >> Johan >> >> > >

April 10, 2014

Re: [Pharo-dev] Absolute and relative directories

by Esteban Lorenzano

is probably there, along with the fix (but not sure) On 10 Apr 2014, at 15:32, Torsten Bergmann <astares(a)gmx.de> wrote: > At least we should add a testcase. Shouldnt we? > >> Gesendet: Donnerstag, 10. April 2014 um 15:15 Uhr >> Von: "Damien Cassou" <damien.cassou(a)gmail.com> >> An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Betreff: Re: [Pharo-dev] Absolute and relative directories >> >> sorry, I was using a very old version >> >> >> On Thu, Apr 10, 2014 at 10:19 AM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: >>> on Mac OS >>> >>> '.' asFileReference absolutePath isAbsolute -> true >>> >>> >>> '.' asFileReference absolutePath isAbsolute >>> >>> >>> On 10 Apr 2014, at 09:59, Nicolai Hess <nicolaihess(a)web.de> wrote: >>> >>> Which OS? >>> >>> for windows: >>> '.' asFileReference absolutePath isAbsolute -> true >>> >>> >>> >>> 2014-04-10 9:44 GMT+02:00 Damien Cassou <damien.cassou(a)gmail.com>: >>>> >>>> '.' asFileReference absolutePath isAbsolute ===> false >>>> >>>> >>>> Is that desirable? It seems wrong to me. >>>> >>>> -- >>>> Damien Cassou >>>> http://damiencassou.seasidehosting.st >>>> >>>> "Success is the ability to go from one failure to another without >>>> losing enthusiasm." >>>> Winston Churchill >>>> >>> >>> >> >> >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> >> >

April 10, 2014

Re: [Pharo-dev] FileSystem-Git status update 3

by Henrik Johansen

On 10 Apr 2014, at 3:27 , Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > > On 10 Apr 2014, at 2:29 , Igor Stasenko <siguctua(a)gmail.com> wrote: > >> >> >> >> On 10 April 2014 13:35, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >> >> On 10 Apr 2014, at 1:18 , Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> >>> >>> >>> On 10 April 2014 11:44, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: >>> >>> On 09 Apr 2014, at 5:30 , Max Leske <maxleske(a)gmail.com> wrote: >>> >>> > >>> > On 09.04.2014, at 17:25, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>> > >>> >> Max Leske wrote >>> >>>> In NB, how do I pass NULL into a function call without modifying the >>> >>>> argument type? e.g. my argument has type String. passing something like >>> >>>> `NBExternalAddress null` will be converted into a C string instead of >>> >>>> being passed through (I know, that seems to be the point in this case but >>> >>>> I couldn't find any other way to create NULL). Any suggestions? >>> >> >>> >> I think you just pass nil, no? >>> > >>> > One would think so, but noâ¦ :) >>> > NB will signal an exception because UndefinedObject is not of the expected type. >>> >>> I remember an optCoerceNilToNull, but that seems to >>> 1) Only apply to pointer types (which could mean having to use char *, not String, and thus need to do encoding/decoding manually) >>> 2) Be scoped to entire call, not single parameter (may or may not be more than a philosophical objection) >>> >>> Might be worth a shot though? >>> >>> - optCoerceNilToNull is for pointers >>> >>> for strings, there's an option: >>> - optStringOrNull >>> >>> which, if enabled, adds additional check for nil in generated marshaller code, >>> so that by passing nil it will pass NULL to calling function. >> >> Would probably aid discoverability quite a bit if optionAt: was used consistently, and (at least the convenient-for-implementing-not-so-convenient-for-using option handling in) NBNativeCodeGen >> #doesNotUnderstand: removedâ¦ >> >> removed? nope >> >> doesNotUnderstand: message >> >> (message selector isUnary and: [ message selector beginsWith: 'opt'] ) >> ifTrue: [ ^ options includes: message selector ]. >> >> ^ super doesNotUnderstand: message >> >> The finder is unable to point me to users of optStringOrNull even when I know the selector, and the defaultOptions method (which was the first place I found with a list of options) contains far from a complete set of the total available options, it seemsâ¦ >> >> >> My rationale behind it: >> - there is no fixed list of options.. they can be introduced/removed depending from the place they actually used - most of the times this is in marshalling code.. and so best way to figure out is to see what marshaller does and expecting (NBExternalType subclasses). >> >> To find out what marshaller behind specific type, one can use following expression: >> >> NBFFICallout new resolveType: typename. >> >> where type name is a string or symbol.. >> like that: >> >> NBFFICallout new resolveType: #String >> >> gives >> >> NBExternalString >> >> and inspecting it further you can see what options there. >> >> I'd like to point out that the complete set of options depends from implementation of various marshalling code. >> >> i am open for any suggestions which could make options more accessible. >> >> For example, >> >> NativeBoost class >> allCalloutOptions >> | symbols options package | >> symbols := Symbol allSubInstances select: [ :ea | ea beginsWith: 'opt' ]. >> >> options := Set new. >> package := self package. >> >> symbols do: [ :symbol | >> | senders | >> senders := SystemNavigation default allSendersOf: symbol. >> (senders anySatisfy: [ :ea | ea methodClass package = package ]) ifTrue: [ options add: symbol ]. >> ]. >> ^ options >> >> gives: >> a Set(#optProxyLabels #optAllowByteArraysPtr #optReturnNullAsNil #optCoerceNilToNull #optUseStackPointer #optStdcall #optStringOrNull #optCheckFailOnEveryArgument #optDebug #optAllowExternalAddressPtr #optDirectProxyFnAddress #options: #optEmitCall #optCdecl #optFailOnReturnNull #optCheckIndirectArgBounds #optReserveCallgateSpace #optNoCleanup #optMayGC #optNoAlignment #optNonMovable #optReturnPtrAsInt #optReturnPtrAsExternalAddress) > > > Something that is possible to find using references/senders/implementers starting from some related place you know about/stumble across in the code is what I call accessible in a Smalltalk-context. > > In this case, I already knew it was possible to provide options that modifies the way calls are built, so my starting point was NBFFICallout, where I quickly found the options inst var. > Going from there, to how the options are actually used, and who were using it, was (at least to me) close to impossible using those three tools, the way itâs implemented. > > Requiring use of optionAt: would cut that down to a three-step process: > - References to options instvar > - Senders of optionAt: > - Voila! > > Cheers, > Henry In other words, it would allow me to keep a small fact in my head: âI can modify the way callouts are builtâ, and easily get from there to finding the details about implementation/use when I need it just using standard tools and reading some code. Thatâs just not possible when you use doesNotUnderstand: / symbolic performs to do the job, and no amount of external documentation will lessen (at least my) frustration at trying to gain understanding. Cheers, Henry

April 10, 2014

Re: [Pharo-dev] Absolute and relative directories

by Torsten Bergmann

At least we should add a testcase. Shouldnt we? > Gesendet: Donnerstag, 10. April 2014 um 15:15 Uhr > Von: "Damien Cassou" <damien.cassou(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] Absolute and relative directories > > sorry, I was using a very old version > > > On Thu, Apr 10, 2014 at 10:19 AM, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > > on Mac OS > > > > '.' asFileReference absolutePath isAbsolute -> true > > > > > > '.' asFileReference absolutePath isAbsolute > > > > > > On 10 Apr 2014, at 09:59, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > > Which OS? > > > > for windows: > > '.' asFileReference absolutePath isAbsolute -> true > > > > > > > > 2014-04-10 9:44 GMT+02:00 Damien Cassou <damien.cassou(a)gmail.com>: > >> > >> '.' asFileReference absolutePath isAbsolute ===> false > >> > >> > >> Is that desirable? It seems wrong to me. > >> > >> -- > >> Damien Cassou > >> http://damiencassou.seasidehosting.st > >> > >> "Success is the ability to go from one failure to another without > >> losing enthusiasm." > >> Winston Churchill > >> > > > > > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

April 10, 2014