- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Best way to access icons?

by Esteban Lorenzano

Smalltalk ui icons iconNamed: #protocolExtension. Still ugly, but Iâm not happy with the idea of a selector-per-iconâ¦ they will never be enough and wellâ¦ is like a monolithic vision. Not that what we have is much better, but you can consider it an iteration :) Esteban > On 04 Feb 2016, at 16:19, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi > > For ages to access an icon we used: > Smalltalk ui icons protocolPrivateIcon > > Smalltalk ui icons returns an instance of ThemeIcons. > After refactoring (caseÂ https://pharo.fogbugz.com/f/cases/16651 <https://pharo.fogbugz.com/f/cases/16651>) all methods to access icon (for example protocolPrivateIcon) were removed. > > ThemeIcons>>#doesNotUnderstand: aMessage converts message sent to iconNamed: aMessage selector which works. > > BUT we have this all over the image: > <Screen Shot 2016-02-04 at 16.13.03.png> > > So, what is the best practice to access icons to use in application? > > Cheers, > Alex >

Feb. 4, 2016

Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5)

by Blondeau Vincent

I just tried to integrate and the tests are failing when reopening the image. Just added the opening of the session file at the right place and the closing of the file at the end of the critical section. Now, it works fine for me (under W7 of course ;): Name: Ombu-VincentBlondeau.191 Author: VincentBlondeau Time: 4 February 2016, 4:22:48.687273 pm UUID: ebaf974e-9285-e147-bcaa-0049ff093ffe Ancestors: Ombu-MartinDias.190 Vincent > -----Message d'origine----- > De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de > Marcus Denker > EnvoyÃ© : jeudi 4 fÃ©vrier 2016 15:19 > Ã : Pharo Development List > Objet : Re: [Pharo-dev] [ANN] We are in "code freeze" for Pharo 5 > > > > On 04 Feb 2016, at 15:16, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > > > Esteban Lorenzano <estebanlm(a)gmail.com> writes: > > > >> We are on âjust bugfixesâ since some time nowâ¦ I delayed the > announcement because Epicea still needs to enter and we didnât manage to > include it yet. > >> But wellâ¦ with the exception of Epicea, no new features will be included > un Pharo 5â¦ just bugfixes (and we have a lot of bugfixes incomingâ¦ this > release will be hard :( ) > > > > what is Epicea's integration status? > > > We have some strange problem on Windowsâ¦ the test on the build server > fails after integrating it. > > Martin already fixed one problem, but my try yesterday failed again. > > Marcus > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un virus transmis. This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.

Feb. 4, 2016

Best way to access icons?

by Aliaksei Syrel

Hi For ages to access an icon we used: > Smalltalk ui icons protocolPrivateIcon Smalltalk ui icons returns an instance of ThemeIcons. After refactoring (case https://pharo.fogbugz.com/f/cases/16651 <https://pharo.fogbugz.com/f/cases/16651>) all methods to access icon (for example protocolPrivateIcon) were removed. ThemeIcons>>#doesNotUnderstand: aMessage converts message sent to iconNamed: aMessage selector which works. BUT we have this all over the image: [image: Inline image 1] So, what is the best practice to access icons to use in application? Cheers, Alex

Feb. 4, 2016

Re: [Pharo-dev] [ANN] We are in "code freeze" for Pharo 5

by Tudor Girba

Hi, > On Feb 4, 2016, at 3:16 PM, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > Esteban Lorenzano <estebanlm(a)gmail.com> writes: > >> We are on âjust bugfixesâ since some time nowâ¦ I delayed the announcement because Epicea still needs to enter and we didnât manage to include it yet. >> But wellâ¦ with the exception of Epicea, no new features will be included un Pharo 5â¦ just bugfixes (and we have a lot of bugfixes incomingâ¦ this release will be hard :( ) > > what is Epicea's integration status? Not yet integrated :)) Doru > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." --Winston Churchill > -- www.tudorgirba.com www.feenk.com "Beauty is where we see it."

Feb. 4, 2016

Re: [Pharo-dev] [ANN] We are in "code freeze" for Pharo 5

by Marcus Denker

> On 04 Feb 2016, at 15:16, Damien Cassou <damien.cassou(a)inria.fr> wrote: > > Esteban Lorenzano <estebanlm(a)gmail.com> writes: > >> We are on âjust bugfixesâ since some time nowâ¦ I delayed the announcement because Epicea still needs to enter and we didnât manage to include it yet. >> But wellâ¦ with the exception of Epicea, no new features will be included un Pharo 5â¦ just bugfixes (and we have a lot of bugfixes incomingâ¦ this release will be hard :( ) > > what is Epicea's integration status? > We have some strange problem on Windowsâ¦ the test on the build server fails after integrating it. Martin already fixed one problem, but my try yesterday failed again. Marcus

Feb. 4, 2016

Re: [Pharo-dev] [ANN] We are in "code freeze" for Pharo 5

by Damien Cassou

Esteban Lorenzano <estebanlm(a)gmail.com> writes: > We are on âjust bugfixesâ since some time nowâ¦ I delayed the announcement because Epicea still needs to enter and we didnât manage to include it yet. > But wellâ¦ with the exception of Epicea, no new features will be included un Pharo 5â¦ just bugfixes (and we have a lot of bugfixes incomingâ¦ this release will be hard :( ) what is Epicea's integration status? -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Feb. 4, 2016

Re: [Pharo-dev] [Need help with Monkey] Removing Object>>name

by Damien Cassou

Guille Polito <guillermopolito(a)gmail.com> writes: > And yes, linux VM's are not shipped with the UUID plugin... at least not > since 2014/2013... if you tell me what to change, I can release new VM sources in http://files.pharo.org/vm/src/vm-unix-sources/ -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Feb. 4, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50566 Home: https://github.com/pharo-project/pharo-core

Feb. 4, 2016

[pharo-project/pharo-core] 3fac82: 50566

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 3fac822ec0bd8a92bc78c3f7e731559c26079de8 https://github.com/pharo-project/pharo-core/commit/3fac822ec0bd8a92bc78c3f7… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-04 (Thu, 04 Feb 2016) Changed paths: A Collections-Strings.package/String.class/instance/ToRemove/adaptToNumber_andSend_.st R Collections-Strings.package/String.class/instance/as yet unclassified/adaptToNumber_andSend_.st R Kernel.package/Behavior.class/instance/as yet unclassified/basicIdentityHash.st R Kernel.package/Behavior.class/instance/as yet unclassified/shouldNotBeRedefined.st A Kernel.package/Behavior.class/instance/reflective operations/basicIdentityHash.st A Kernel.package/Behavior.class/instance/testing/shouldNotBeRedefined.st R Kernel.package/Object.class/instance/as yet unclassified/clone.st A Kernel.package/Object.class/instance/copying/clone.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50565.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50566.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50565.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50566.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50566 17521 recategorizing uncategorised method https://pharo.fogbugz.com/f/cases/17521 17522 Failing test: ReleaseTest>>#testInstalledMethodsWithIncorrectTrailerKind https://pharo.fogbugz.com/f/cases/17522 17479 Interval class comment mixes step/stop when explaining Instance Variables https://pharo.fogbugz.com/f/cases/17479 http://files.pharo.org/image/50/50566.zip

Feb. 4, 2016

Re: [Pharo-dev] [Need help with Monkey] Removing Object>>name

by Sven Van Caekenberghe

> On 04 Feb 2016, at 14:02, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: > >> >> On 04 Feb 2016, at 12:52 , Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> On 04 Feb 2016, at 11:55, Guille Polito <guillermopolito(a)gmail.com> wrote: >>> >>> Good news, so far, installing NeoUUID and replacing UUID class >> new by: >>> >>> UUID class >> new >>> ^NeoUUIDGenerator new next >>> >>> seems to work. At it looks that I can trust again my commits. >>> >>> Thanks Sven :) >> >> OK. >> >> Now, the idea is that one instance of the generator is kept around, this is way more efficient, but also more correct, as the random generator should not be created anew each time. >> >>> Now I do not know how this should be solved, nor if this is reproducible in a machine other than mine... >> >> I seriously doubt the plugin is better (more random, more unique) then anything that we can do in Pharo itself. I like Pharo code way better, because we all see what it does. >> >> Anyone else with an opinion ? > > More random for certain, at least much faster than we could do in Pharo, is certainly possible with a plugin. > More unique... well, depends on whether you can trust the source RNG (seeded from data with enough entropy, period much greater than 2^128, etc). > > A single next:into:startingAt: primitive filling random data (obtained using platform primitives and/or RDRAND/RDSEED) into a buffer would be much nicer/more flexible than the current UUID primitive though. (the linked UUID library is basically just a thin wrapper around the platform primitives, plus setting variant/version bits in the returned UUID bytes) > > As a stopgap, one could instead use another, more general primitive (but with a less flexible api than next:into:startingAt:) in an otherwise unrelated plugin (but that is built internal to all Cog VM's, at least): > rand: aBuffer > <primitive: 'primitiveGatherEntropy' module: 'CroquetPlugin'> > ^self primitiveFail > > (which, iirc, resolves to the same platform primitives as UUID lib) > > Also, the meaning of different UUID versions are well defined in the RFC, marking NeoUUID's as being a version 4 UUID seems somewhat ... disingenuous. Yes, but to 99.99% of developers, a UUID is something special/magic where some effort was made to generate something as unique as possible. If we insist on it being just 128 random bits, then why all the fuss ? Why do we even need so called standards ? Why do we need a plugin, an implementation even ? It makes no sense. Just read 16 bytes from /dev/[u]random, or the equivalent use of a RNG and be done with it. But if you tell developers that their database IDs are just plain random numbers, they will probably feels less good about them. To me UUID is a specific concept: << The intent of UUIDs is to enable distributed systems to uniquely identify information without significant central coordination. In this context the word unique should be taken to mean "practically unique" rather than "guaranteed unique". >> Not including any 'node' information (identifying process, image, VM, machine, network endpoint), nor 'counter' does not feel right. > Cheers, > Henry

Feb. 4, 2016