March 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Frozen is melted (can you guys please be patient?)

by Esteban Lorenzano

> On 6 Mar 2017, at 07:57, phil(a)highoctane.be wrote: > > https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator-simple/7294/artifac… <https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator-simple/7294/artifac…> is not integrated for some Monkey reason anyway - still should b/c if you put sublimish, you need a decent matching Spotter. > > Also, I see https://pharo.fogbugz.com/f/cases/19796/Remove-duplicate-code-from-Sublimis… <https://pharo.fogbugz.com/f/cases/19796/Remove-duplicate-code-from-Sublimis…> on 5/3. If this moves forward, why not the other one? > > BTW Sublimish was an extra thing. Who got that in image? I donât know. It shouldnât :) What we should do is to create a page for themes and links to it (and they should be in catalog) :) Esteban > > Phil > > On Mon, Mar 6, 2017 at 7:43 AM, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: > >> On 6 Mar 2017, at 07:17, Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>> wrote: >> >> Hi, >> >> First, let me be clear: I *like* sublimish theme (not for my use, but I like it), and I like (a lot) the windows list on spotter, and I like in general all this new additions. > > By the way, even if I like it, I would not have integrated SublimishTheme. For same reason I didnât integrated DarkMetalTheme: My idea is to have just two themes *in image*: one white, one dark, and allow people to install other themes from catalog. > > Why? Because each class inside image becomes our responsibility and then a maintainability issue. With themes in particular already happened that existing themes became abandonware inside the image and we needed to clean up, not without problems. > > cheers, > Esteban > > ps: which means also yes: that issue got integrated because I failed to control the flow of issues... > >> >> And I know, most of those additions are usability enhancements so a good thing. >> >> But can you guys stop pushing new features into a (in theory) frozen version? >> >> Pharo 7 will arrive soonâ¦ *if* we can fix all things missing. If I can suggest an orientation, it would be good, for those that use linux and mac (windows is not ready), to test and help fix 64bits version. >> >> There are still plenty of bugs to fix there, like for example why Spotter does not shows search line. >> >> Last week I added support to Athens and SDL2 in 64bits but that meant: >> >> - some important changes in UFFI >> - discover something that seems is failing on callbacks for Cairo (no idea if it is a callbacks problem or an image problem that causes a callback problem). >> >> I would say all this and the fact we are working on 64bits in general deserves a lot of testing. >> >> I will add links in Pharo page to download 64bits (Iâm at the train now), but in the mean time you can download all from here: >> >> http://files.pharo.org/get-files/60/pharo-64.zip <http://files.pharo.org/get-files/60/pharo-64.zip> >> http://files.pharo.org/get-files/60/pharo64-linux-latest.zip <http://files.pharo.org/get-files/60/pharo64-linux-latest.zip> (linux) >> http://files.pharo.org/get-files/60/pharo64-mac-latest.zip <http://files.pharo.org/get-files/60/pharo64-mac-latest.zip> (mac) >> http://files.pharo.org/get-files/60/sources.zip <http://files.pharo.org/get-files/60/sources.zip> (in case you need them) >> >> cheers, >> Esteban > >

March 6, 2017

Esteban's ChangeLog week of 27 February 2017

by estebanlm＠gmail.com

Hello! This is my weekly ChangeLog, from 27 February 2017 to 5 March 2017. You can see it in a better format by going here: http://log.smallworks.eu/web/search?from=27/2/2017&to=5/3/2017 ChangeLog ========= 3 March 2017: ------------- * And now I made +libssh2.so+ compile on linux too :) I think Iceberg is fixed now for linux, can someone with linux try +vmLatest60+. * I worked on VM for linux, this time fixing dependencies for libgit2: it was not working because it was trying to link libssh2 existing in the system instead the one we provide (a problem with rpath)... I figured out I need to add some CMAKE options: ---- -DCMAKE_SKIP_BUILD_RPATH=FALSE -DCMAKE_INSTALL_RPATH="." ---- otherwise +make install+ was ignoring the +-Wl,rpath,.+ configuration. With this it seems to be working, but now I have a problem with +libssh2+ compilation. I'll see this next. * I took some moments to fix a problem on new UFFI version (0.26): Now, structures use a class variable to keep the offset value of a field. So now, instead having an accessor to a field of the form (for example): ---- MyStructure>>myField ^ handle unsignedLongAt: 42 ---- ... now you have an accessor of the form: ---- MyStructure>>myField ^ handle unsignedLongAt: OFFSET_MYFIELD ---- this is necesary to allow different platforms to use same structures (because sizes of fields, and in consequence of offsets of them inside a stricture are different). This 'offsets' are calculated (as structure compiled specs) at first access to +#compiledSpec+ of structure, which usually happens when you use it first time... but now always, as [case: 19788](https://pharo.fogbugz.com/f/cases/19788) shows. Well, now I fixed that :) 2 March 2017: ------------- * I added a Discord link on [http://pharo.org/community](http://pharo.org/community)... I want to slowly start moving our community there. I know Slack is very popular among us this days but Dicords offers some advantages (like no 10k limit on messages and a powerful search). 1 March 2017: ------------- * ... and now I made the [case:19783](https://pharo.fogbugz.com/f/cases/19783), to make SDL2 work on 64bits (it works!) :) * Yesterday I spent the full day debugging a VM to see why Athens was not working for 64bits and I finally figured out the problem was in image and not in VM :P As a result of the work, I produced this fixes: * [case:19781](https://pharo.fogbugz.com/f/cases/19781) to fix a problem answering pointers on callbacks. * [case:19782](https://pharo.fogbugz.com/f/cases/19782) to actually prepare Athens. With this two cases, Athens works in 64bits (almost) :) Now there is a problem in 64bits callbacks that makes the +VGTigerDemo runDemo+ to fail after some cycles. Since this problem does not happens on 32bits, I assume there is a problem on how callbacks work on 64bits. I'm not working on that (I will work also in migrating SDL2). 27 February 2017: ----------------- * Well, I spend some time trying to blindly figure out why athens may crash time to time when drawing surfaces, basically testing the apprachs [Ronie proposes](http://forum.world.st/Too-frequent-crashes-td4927143i20.html#a4934027). First approach consists on copying data to not rely on a surface at all. Problem with this is that it involves a whole full copy, that causes a lot of GC that pauses a lot the image... so smoothness is gone. Second approach seems a lot more doable, but I still don't know if it works: ---- Form subclass: #AthensCairoSurfaceForm instanceVariableNames: 'surface' classVariableNames: '' package: 'Athens-Cairo' AthensCairoSurfaceForm>>surface ^ surface AthensCairoSurfaceForm>>surface: anObject surface := anObject AthensCairoSurface>>asForm "create a form and copy an image data there" self checkSession. self flush. ^ (AthensCairoSurfaceForm extent: (self width@self height) depth: 32 bits: id) surface: self; yourself ---- this will prevent surfaces to be garbage collected before it's time and seems to be working fine (at least in my machine). cheers! Esteban

March 6, 2017

Re: [Pharo-dev] Frozen is melted (can you guys please be patient?)

by phil＠highoctane.be

https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator-simple/7294/artifac… is not integrated for some Monkey reason anyway - still should b/c if you put sublimish, you need a decent matching Spotter. Also, I see https://pharo.fogbugz.com/f/cases/19796/Remove-duplicate-code-from-Sublimis… on 5/3. If this moves forward, why not the other one? BTW Sublimish was an extra thing. Who got that in image? Phil On Mon, Mar 6, 2017 at 7:43 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On 6 Mar 2017, at 07:17, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > First, let me be clear: I *like* sublimish theme (not for my use, but I > like it), and I like (a lot) the windows list on spotter, and I like in > general all this new additions. > > > By the way, even if I like it, I would not have integrated SublimishTheme. > For same reason I didnât integrated DarkMetalTheme: My idea is to have just > two themes *in image*: one white, one dark, and allow people to install > other themes from catalog. > > Why? Because each class inside image becomes our responsibility and then a > maintainability issue. With themes in particular already happened that > existing themes became abandonware inside the image and we needed to clean > up, not without problems. > > cheers, > Esteban > > ps: which means also yes: that issue got integrated because I failed to > control the flow of issues... > > > And I know, most of those additions are usability enhancements so a good > thing. > > But can you guys stop pushing new features into a (in theory) frozen > version? > > Pharo 7 will arrive soonâ¦ *if* we can fix all things missing. If I can > suggest an orientation, it would be good, for those that use linux and mac > (windows is not ready), to test and help fix 64bits version. > > There are still plenty of bugs to fix there, like for example why Spotter > does not shows search line. > > Last week I added support to Athens and SDL2 in 64bits but that meant: > > - some important changes in UFFI > - discover something that seems is failing on callbacks for Cairo (no idea > if it is a callbacks problem or an image problem that causes a callback > problem). > > I would say all this and the fact we are working on 64bits in general > deserves a lot of testing. > > I will add links in Pharo page to download 64bits (Iâm at the train now), > but in the mean time you can download all from here: > > http://files.pharo.org/get-files/60/pharo-64.zip > http://files.pharo.org/get-files/60/pharo64-linux-latest.zip (linux) > http://files.pharo.org/get-files/60/pharo64-mac-latest.zip (mac) > http://files.pharo.org/get-files/60/sources.zip (in case you need them) > > cheers, > Esteban > > >

March 6, 2017

Re: [Pharo-dev] Frozen is melted (can you guys please be patient?)

by Esteban Lorenzano

> On 6 Mar 2017, at 07:17, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > First, let me be clear: I *like* sublimish theme (not for my use, but I like it), and I like (a lot) the windows list on spotter, and I like in general all this new additions. By the way, even if I like it, I would not have integrated SublimishTheme. For same reason I didnât integrated DarkMetalTheme: My idea is to have just two themes *in image*: one white, one dark, and allow people to install other themes from catalog. Why? Because each class inside image becomes our responsibility and then a maintainability issue. With themes in particular already happened that existing themes became abandonware inside the image and we needed to clean up, not without problems. cheers, Esteban ps: which means also yes: that issue got integrated because I failed to control the flow of issues... > > And I know, most of those additions are usability enhancements so a good thing. > > But can you guys stop pushing new features into a (in theory) frozen version? > > Pharo 7 will arrive soonâ¦ *if* we can fix all things missing. If I can suggest an orientation, it would be good, for those that use linux and mac (windows is not ready), to test and help fix 64bits version. > > There are still plenty of bugs to fix there, like for example why Spotter does not shows search line. > > Last week I added support to Athens and SDL2 in 64bits but that meant: > > - some important changes in UFFI > - discover something that seems is failing on callbacks for Cairo (no idea if it is a callbacks problem or an image problem that causes a callback problem). > > I would say all this and the fact we are working on 64bits in general deserves a lot of testing. > > I will add links in Pharo page to download 64bits (Iâm at the train now), but in the mean time you can download all from here: > > http://files.pharo.org/get-files/60/pharo-64.zip <http://files.pharo.org/get-files/60/pharo-64.zip> > http://files.pharo.org/get-files/60/pharo64-linux-latest.zip <http://files.pharo.org/get-files/60/pharo64-linux-latest.zip> (linux) > http://files.pharo.org/get-files/60/pharo64-mac-latest.zip <http://files.pharo.org/get-files/60/pharo64-mac-latest.zip> (mac) > http://files.pharo.org/get-files/60/sources.zip <http://files.pharo.org/get-files/60/sources.zip> (in case you need them) > > cheers, > Esteban

March 6, 2017

Frozen is melted (can you guys please be patient?)

by Esteban Lorenzano

Hi, First, let me be clear: I *like* sublimish theme (not for my use, but I like it), and I like (a lot) the windows list on spotter, and I like in general all this new additions. And I know, most of those additions are usability enhancements so a good thing. But can you guys stop pushing new features into a (in theory) frozen version? Pharo 7 will arrive soonâ¦ *if* we can fix all things missing. If I can suggest an orientation, it would be good, for those that use linux and mac (windows is not ready), to test and help fix 64bits version. There are still plenty of bugs to fix there, like for example why Spotter does not shows search line. Last week I added support to Athens and SDL2 in 64bits but that meant: - some important changes in UFFI - discover something that seems is failing on callbacks for Cairo (no idea if it is a callbacks problem or an image problem that causes a callback problem). I would say all this and the fact we are working on 64bits in general deserves a lot of testing. I will add links in Pharo page to download 64bits (Iâm at the train now), but in the mean time you can download all from here: http://files.pharo.org/get-files/60/pharo-64.zip <http://files.pharo.org/get-files/60/pharo-64.zip> http://files.pharo.org/get-files/60/pharo64-linux-latest.zip <http://files.pharo.org/get-files/60/pharo64-linux-latest.zip> (linux) http://files.pharo.org/get-files/60/pharo64-mac-latest.zip <http://files.pharo.org/get-files/60/pharo64-mac-latest.zip> (mac) http://files.pharo.org/get-files/60/sources.zip <http://files.pharo.org/get-files/60/sources.zip> (in case you need them) cheers, Esteban

March 6, 2017

Re: [Pharo-dev] running Hapao using 60429 image - Pharo dies

by Alexandre Bergel

Hi Sheridan, I tried to reproduce the problem you have experienced. I could not see the error you faced. I tried on MacOSX however. Hapao does some method instrumentation, and apparently the Windows VM does not like them. You can see the result on: https://dl.dropboxusercontent.com/u/31543901/TMP/CoverageOfString/index.html You can also download the result from: https://dl.dropboxusercontent.com/u/31543901/TMP/CoverageOfString/Archive.z… I do not have a solution for your problem. But I do have a question: do you really need to measure the coverage of String? I am confident that on a less system-critic class Hapao will give you satisfactory result. On a side note, it is interesting to see that String is covered at only 65%. There is a StringTest, but no subclasses, while String has many subclasses. Cheers, Alexandre > On Mar 5, 2017, at 8:14 PM, sheridan(a)sheridan-mahoney.com wrote: > > Hello, > I was working at loading Hapao into the latest Pharo image, and ran into a problem. I started with a brand new download of Pharo 5.0, and got the latest development image and changes for 6.0 (60429). I then ran: > > Gofer it > smalltalkhubUser: 'ObjectProfile' project: 'Spy2'; > configurationOf: 'Spy2'; > loadStable. > > which ran to completion. > > I then went to check the tests in the String class, so I ran: > > > (Hapao2 runTestsForClasses: String withAllSubclasses , StringTest withAllSubclasses) visualize. > > Pharo started running the tests. Then a message from the operating system came up saying, > > "Pharo.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available". > > I tried this twice, and got the same error message each time. > > Is there something I should be doing differently in terms of how I am loading and running Hapao? > > Many thanks, > > and best regards, > > Sheridan > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 6, 2017

running Hapao using 60429 image - Pharo dies

by sheridan＠sheridan-mahoney.com

Hello, I was working at loading Hapao into the latest Pharo image, and ran into a problem. I started with a brand new download of Pharo 5.0, and got the latest development image and changes for 6.0 (60429). I then ran: Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Spy2'; configurationOf: 'Spy2'; loadStable. which ran to completion. I then went to check the tests in the String class, so I ran: (Hapao2 runTestsForClasses: String withAllSubclasses , StringTest withAllSubclasses) visualize. Pharo started running the tests. Then a message from the operating system came up saying, "Pharo.exe has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available". I tried this twice, and got the same error message each time. Is there something I should be doing differently in terms of how I am loading and running Hapao? Many thanks, and best regards, Sheridan

March 5, 2017

Re: [Pharo-dev] Spotter idea - bring existing code windows to front

by Andrei Chis

Nice! On Sun, Mar 5, 2017 at 9:04 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Slice in Pharo60Inbox > > https://pharo.fogbugz.com/f/cases/19798/Make-Spotter-look-for-open-windows > > I got it working properly now. > > [image: Inline image 1] > > Do we want this to come before the search for custom menus? Having another search first would make it more difficult to use Spotter to quickly find items in the world menu. > But how is one to package a Spotter extension in a given package without > having to touch GTSpotter extensions core? > We usually package extensions related to the core parts of the IDE in the GT-SpotterExtensions-Core. Otherwise you can create a dedicated package with extensions for a certain project. > > This is indeed easy to understand once gone through the motions and opens > a lot of doors for open data exploration with custom spotters. > > Question: how can I wire several spotters together? > If you click on the arrow to the right of the selected row (or use Meta+ArrowRight) you will trigger the dive-in action that will open Spotter on the selected object. This will load searches specific to that object. For example if you dive in into a window object you will get a search thorough the submorphs and shortcuts associated with the window. They are defined in the Morph class. If you want to add some specific searches that apply to a window you can add them to the SystemWindow class. Cheers, Andrei > > Phil > > > On Sun, Mar 5, 2017 at 7:15 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Nice one, Phil :) >> >> Doru >> >> >> >> > On Mar 4, 2017, at 7:32 PM, phil(a)highoctane.be wrote: >> > >> > I made a little experiment to get the windows listed in spotter. >> > >> > <image.png> >> > >> > I have still an issue with the activation and some weird windows listed >> but should be able to give you just that in a couple hours. >> > >> > This is a good opportunity for me to jump into spotter extensions, thx >> for the nudge :-) >> > >> > Phil >> > >> > On Sat, Mar 4, 2017 at 4:19 PM, Ben Coman <btc(a)openinworld.com> wrote: >> > A quick note on an idea that strikes me, >> > I often find myself with a large number of windows open and I know I >> have a code window open previously but the task bar is a bit opaque to find >> it, >> > and its so cheap to open a new code window from Spotter, thats what I >> do, >> > and open yet another window, making it harder again to find any >> particular window. >> > You can see the downward spiral here. >> > >> > So apart from more discipline is managing the number of windows I have >> open >> > a passing idea is that for if an existing code window is open, Spotter >> brings that to the front rather than opening another window. Optionally, >> if that code window is dirty, as well as bringing it to the front a fresh >> code window be opened as well, so that the two are immediately comparable. >> > >> > cheers -ben >> > >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Yesterday is a fact. >> Tomorrow is a possibility. >> Today is a challenge." >> >> >> >> >> >> >

March 5, 2017

Re: [Pharo-dev] Spotter idea - bring existing code windows to front

by phil＠highoctane.be

Slice in Pharo60Inbox https://pharo.fogbugz.com/f/cases/19798/Make-Spotter-look-for-open-windows I got it working properly now. [image: Inline image 1] But how is one to package a Spotter extension in a given package without having to touch GTSpotter extensions core? This is indeed easy to understand once gone through the motions and opens a lot of doors for open data exploration with custom spotters. Question: how can I wire several spotters together? Phil On Sun, Mar 5, 2017 at 7:15 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Nice one, Phil :) > > Doru > > > > > On Mar 4, 2017, at 7:32 PM, phil(a)highoctane.be wrote: > > > > I made a little experiment to get the windows listed in spotter. > > > > <image.png> > > > > I have still an issue with the activation and some weird windows listed > but should be able to give you just that in a couple hours. > > > > This is a good opportunity for me to jump into spotter extensions, thx > for the nudge :-) > > > > Phil > > > > On Sat, Mar 4, 2017 at 4:19 PM, Ben Coman <btc(a)openinworld.com> wrote: > > A quick note on an idea that strikes me, > > I often find myself with a large number of windows open and I know I > have a code window open previously but the task bar is a bit opaque to find > it, > > and its so cheap to open a new code window from Spotter, thats what I do, > > and open yet another window, making it harder again to find any > particular window. > > You can see the downward spiral here. > > > > So apart from more discipline is managing the number of windows I have > open > > a passing idea is that for if an existing code window is open, Spotter > brings that to the front rather than opening another window. Optionally, > if that code window is dirty, as well as bringing it to the front a fresh > code window be opened as well, so that the two are immediately comparable. > > > > cheers -ben > > > > -- > www.tudorgirba.com > www.feenk.com > > "Yesterday is a fact. > Tomorrow is a possibility. > Today is a challenge." > > > > > >

March 5, 2017

Re: [Pharo-dev] Spotter idea - bring existing code windows to front

by Tudor Girba

Nice one, Phil :) Doru > On Mar 4, 2017, at 7:32 PM, phil(a)highoctane.be wrote: > > I made a little experiment to get the windows listed in spotter. > > <image.png> > > I have still an issue with the activation and some weird windows listed but should be able to give you just that in a couple hours. > > This is a good opportunity for me to jump into spotter extensions, thx for the nudge :-) > > Phil > > On Sat, Mar 4, 2017 at 4:19 PM, Ben Coman <btc(a)openinworld.com> wrote: > A quick note on an idea that strikes me, > I often find myself with a large number of windows open and I know I have a code window open previously but the task bar is a bit opaque to find it, > and its so cheap to open a new code window from Spotter, thats what I do, > and open yet another window, making it harder again to find any particular window. > You can see the downward spiral here. > > So apart from more discipline is managing the number of windows I have open > a passing idea is that for if an existing code window is open, Spotter brings that to the front rather than opening another window. Optionally, if that code window is dirty, as well as bringing it to the front a fresh code window be opened as well, so that the two are immediately comparable. > > cheers -ben > -- www.tudorgirba.com www.feenk.com "Yesterday is a fact. Tomorrow is a possibility. Today is a challenge."

March 5, 2017