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

Re: [Pharo-dev] Recent changes in Bloc, no more BlMorph

by Aliaksei Syrel

> > What changed recently in Bloc? Shortly saying, everything :) Root element is BlElement. No more BlView. Added BlShape and BlPath. New layout strategies (old were removed). Cheers, Alex On Fri, Feb 5, 2016 at 10:46 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > What changed recently in Bloc? > In Bloc-Core-AliakseiSyrel.733, BlMorph was removed > > Stephan > > >

Feb. 5, 2016

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

by Blondeau Vincent

Take an image, load Epicea, launch the tests; they should pass. Save and quit the image. Relaunch the image, launch the tests, some was red. Vincent De : Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] De la part de Martin Dias EnvoyÃ© : vendredi 5 fÃ©vrier 2016 08:22 Ã : Pharo Development List Objet : Re: [Pharo-dev] Epicea tests failure under Windows (WAS: RE: [ANN] We are in "code freeze" for Pharo 5) IÂ´ve just released a new version and updated the fogbugz case. I hoep it works now. How did you repdoruce the error Vincent? Martin On Thu, Feb 4, 2016 at 6:24 PM, stepharo <stepharo(a)free.fr<mailto:stepharo@free.fr>> wrote: Thanks vincent!!!!! Le 4/2/16 16:25, Blondeau Vincent a Ã©crit : 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<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<mailto:damien.cassou@inria.fr>> wrote: Esteban Lorenzano <estebanlm(a)gmail.com<mailto:estebanlm@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. ________________________________ 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. 5, 2016

Recent changes in Bloc, no more BlMorph

by Stephan Eggermont

What changed recently in Bloc? In Bloc-Core-AliakseiSyrel.733, BlMorph was removed Stephan

Feb. 5, 2016

Re: [Pharo-dev] [ANN] Pomodoro for Pharo 2.0

by Torsten Bergmann

The Pomodoro timer is a morph on the screen. The easiest way is to open the morphs Halo and just delete it. You can also run the following expression in a playground: PomodoroMorph allInstancesDo: [:each | each delete ] I would recommend to read one of the introduction books to get familiar with Pharo and its concepts. See the PDF's at [1] and [2] Bye T. [1] https://github.com/SquareBracketAssociates/UpdatedPharoByExample [2] http://pharo.pharocloud.com/pharobooks > Gesendet: Donnerstag, 04. Februar 2016 um 19:12 Uhr > Von: ipstone <isaacpei(a)gmail.com> > An: pharo-dev(a)lists.pharo.org > Betreff: Re: [Pharo-dev] [ANN] Pomodoro for Pharo 2.0 > > Hello, > > First time user of Pharo - I just got pomodoro up running, but how to close > it? > > Thanks! > -- Ipstone > > > > -- > View this message in context: http://forum.world.st/ANN-Pomodoro-for-Pharo-2-0-tp4678427p4875915.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Feb. 5, 2016

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

by Esteban Lorenzano

In this case traits would pollute as much as global variables (or more). Take a look at TEasilyThemed ands its usersâ¦ Esteban > On 05 Feb 2016, at 03:08, Ben Coman <btc(a)openInWorld.com> wrote: > > On Fri, Feb 5, 2016 at 5:21 AM, stepharo <stepharo(a)free.fr> wrote: >> Hi guys >> >> I do not have the answer but I hate such patterns >> >> Smalltalk ui icons iconNamed: #protocolExtension. >> >> To me a tools using an icon should declare the icons as a ***local*** >> ressources. > > +100. At a minimum this should probably be... > self iconNamed: #protocolExtension. > > maybe supplied by a trait. > Initially this might be... > TGlobalIcons>>iconNamed: symbol > ^ Smalltalk ui icons iconNamed: symbol > > but later be replaced by... > TClassIcons>>iconNamed: symbol > ^ IconContainer at: symbol > > and the tools would know how to work with those traits, e.g. in > GTExplorer, a tab displaying the icons for a class. But IIUC traits > can't add variables, but did I hear any object can be annotated? So > could TClassIcons store a dictionary holding the icons as an > annotation on the class? But we would need some way to store such > resources with the package, in Monticello or otherwise. > > cheers -ben > >> We could imagine that there is a IconContainer and that as a tool I declare >> that I want an icons and I install it on myself. >> >> | t | >> t := Tool new. >> ic := IconContainer for: #darkTheme. >> t askAninnstallIcon: ic iconFor: #button. >> >> Then if the IconContainer changes, then it can notify its users to ask for a >> new version of the icon. >> >> ic broadcastNewIcon: #button >> >> This way >> >> t does not have to use a plain bad global variable and does not care >> about the global namespace. >> t should only use local resources held in classVar for example. >> >> >> Such Smalltalk ui icons is a dynamic global variable! >> >> Stef >> >> >> >> >> >> Le 4/2/16 17:00, Esteban Lorenzano a Ã©crit : >> >> 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) 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. 5, 2016

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

by Esteban Lorenzano

of course, but since we have not implemented such mechanism, we need to go one step at a timeâ¦ first step is *not to have* everything as static as it was before. then we need to think on skins, injection, etc. Esteban > On 04 Feb 2016, at 22:21, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > I do not have the answer but I hate such patterns > > Smalltalk ui icons iconNamed: #protocolExtension. > > To me a tools using an icon should declare the icons as a ***local*** ressources. > We could imagine that there is a IconContainer and that as a tool I declare that I want an > icons and I install it on myself. > > | t | > t := Tool new. > ic := IconContainer for: #darkTheme. > t askAninnstallIcon: ic iconFor: #button. > > Then if the IconContainer changes, then it can notify its users to ask for a new version of the icon. > > ic broadcastNewIcon: #button > > This way > > t does not have to use a plain bad global variable and does not care about the global namespace. > t should only use local resources held in classVar for example. > > > Such Smalltalk ui icons is a dynamic global variable! > > Stef > > > > > > Le 4/2/16 17:00, Esteban Lorenzano a Ã©crit : >> 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 < <mailto:alex.syrel@gmail.com>alex.syrel(a)gmail.com <mailto:alex.syrel@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 <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. 5, 2016

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

by Nicolai Hess

2016-02-04 12:21 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > 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 :( ) > > I would like to finish my work on shortcuts / keymapping cleanup (remove Smalltalk/RubSmalltalk editor maps in favor of KMDispatcher). But I am waiting for changes on the windows vm (it was included in the pre-spur vm but it isn't in spur). And there is a lot to be done for menus in our tools that now using rubric instead of PluggableText, Are these considered a bug fixes ? Or should I stop and continue later in pharo 6? > cheers, > Esteban >

Feb. 5, 2016

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

by Martin Dias

IÂ´ve just released a new version and updated the fogbugz case. I hoep it works now. How did you repdoruce the error Vincent? Martin On Thu, Feb 4, 2016 at 6:24 PM, stepharo <stepharo(a)free.fr> wrote: > Thanks vincent!!!!! > > Le 4/2/16 16:25, Blondeau Vincent a Ã©crit : > > 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. 5, 2016

Re: [Pharo-dev] pharo-minimal-vm

by ClÃ©ment Bera

One thing you can do is to compile the VM without the external plugins as they are optional. It disables some features (git, Cairo, SDL, ...) but it decreases the memory footprint. This can also be done after the compilation by removing the plugins in the VM folder. In addition you can use a stack VM instead of a cog VM, which removes the code related to the JIt and the machine code zone. 2016-02-05 5:08 GMT+01:00 Ben Coman <btc(a)openinworld.com>: > Is there a minimal-VM that can be used to run the minimal-IMAGE [1] ? > It would be nice for [1] to include an a step.... > PharoVMBuilder buildUnix32minimal. > since the VM is also part of "how small can we go". > > My reason for asking is that also less generated VM code might shorten > the edit-compile-run loop when I try porting the VM to a Xen Rump > kernel > > Also nice would be an example of how to invoke the tests in a minimal > image from the commandline. > > cheers -ben > > [1] https://github.com/pharo-project/pharo-minimal-scripts > >

Feb. 5, 2016

pharo-minimal-vm

by Ben Coman

Is there a minimal-VM that can be used to run the minimal-IMAGE [1] ? It would be nice for [1] to include an a step.... PharoVMBuilder buildUnix32minimal. since the VM is also part of "how small can we go". My reason for asking is that also less generated VM code might shorten the edit-compile-run loop when I try porting the VM to a Xen Rump kernel Also nice would be an example of how to invoke the tests in a minimal image from the commandline. cheers -ben [1] https://github.com/pharo-project/pharo-minimal-scripts

Feb. 5, 2016