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

[pharo-project/pharo-core]

by GitHub

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

March 6, 2017

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

by phil＠highoctane.be

On Mon, Mar 6, 2017 at 9:42 AM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > 2017-03-06 9:29 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> On 6 Mar 2017, at 09:22, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >> >> >> >> 2017-03-06 8:20 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: >> >>> >>> On 6 Mar 2017, at 07:57, phil(a)highoctane.be wrote: >>> >>> https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator-simp >>> le/7294/artifact/report.html 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-SublimishTheme 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) :) >>> >> >> Well, it was me who proposed the slice and yes, I was aware of the fact >> that I should not do it because of code freeze (I was not aware of the two >> themes policy). >> >> >> it is not a policy, it is just the idea I have :) >> >> >> We can remove it again, I will prepare a slice. >> >> >> problem with it is that is makes ripples. >> If community want it (is nice), we can include it, but I would wait for >> P7, yes. >> > > https://pharo.fogbugz.com/f/cases/19801/Remove-SublimishTheme > At least it was an advertisement for this theme that moved it forward and > the integration of it helped to improve the dark theme too. And showed > again how much we need the concept of palettes used strictly in the system. > Ah ah, yeah, I had a ThemePalette thing but resisted rewiring everything. Jokes aside, yes, this is much needed as the current intent based colors with lighter/darker/lighter lighter and other tricks should in fact go into a true palette. I think that we should at least cover this: https://en.wikipedia.org/wiki/ANSI_escape_code#Colors The 16 and 256 versions. As Pharo on the CLI is becoming a thing, that will be helpful there. There are also tons of palettes in Roassal but not to the same purpose. Along with some of these in spirit: http://www.pawelporwisz.pl/winamp/winamp_color_themes_en.php http://customize.org/winamp3/help/How_To_Create_Winamp_Skins We can learn from http://www.skinconsortium.com/ (yeah I like Winamp, old me). Pharo with such a look, oh yeah. One thing I would love to have in the theme is the notion of an 'accent', like they do in MS products. The current DarkTheme has a blue tint, but if we could easily switch that to orange/purple/green/... it would be awesome. I learned a few things digging into Sublimish and GT, so, I think I can tweak Sublimish to have 2 things: a PharoAccentDarkTheme and a SublimishTheme that comes as a subclass of it. Same with GT. Tell me what you think. Phil > > -- Pavel > > > >> >> Esteban >> >> >> -- Pavel >> >> >> >> >> >>> >>> Esteban >>> >>> >>> 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] running Hapao using 60429 image - Pharo dies

by Ben Coman

On Mon, Mar 6, 2017 at 7:14 AM, <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 > > Hi Sheridan, Just as a matter of procedure, could you try 60429 with each of these VMs... http://files.pharo.org/vm/pharo-spur32/win/stable-20170222.zip http://files.pharo.org/vm/pharo-spur32/win/pharo-win-i386-201703031554-13cc… cheers -ben

March 6, 2017

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

by Pavel Krivanek

2017-03-06 9:29 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 6 Mar 2017, at 09:22, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > > 2017-03-06 8:20 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> >> On 6 Mar 2017, at 07:57, phil(a)highoctane.be wrote: >> >> https://ci.inria.fr/pharo/job/Pharo-6.0-Issue-Validator-simp >> le/7294/artifact/report.html 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-SublimishTheme 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) :) >> > > Well, it was me who proposed the slice and yes, I was aware of the fact > that I should not do it because of code freeze (I was not aware of the two > themes policy). > > > it is not a policy, it is just the idea I have :) > > > We can remove it again, I will prepare a slice. > > > problem with it is that is makes ripples. > If community want it (is nice), we can include it, but I would wait for > P7, yes. > https://pharo.fogbugz.com/f/cases/19801/Remove-SublimishTheme At least it was an advertisement for this theme that moved it forward and the integration of it helped to improve the dark theme too. And showed again how much we need the concept of palettes used strictly in the system. -- Pavel > > Esteban > > > -- Pavel > > > > > >> >> Esteban >> >> >> 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 denker

On the other hand: it is better to comb through the *many* issues very hard and close many, even some that might not be just bug fixes than the other alternative: Just let the issue tracker rot âbecause we are in freezeâ. I feel *much* better now about the state of the issue tracker than 3 weeks ago. Now we are seeing light, while before it just god worse and worse and worseâ¦ If adding some ânon fixesâ is the price for that, I am willing to pay for it. If people want to be more strict: We are *really* looking for feedback on issues. Any feedback, even âplease postponeâ. Right now we do not have enough people to do this job and e.g. I can not reject everything. I just do not have the energy for that, as it kills all the (little) fun of what is there in that job. Marcus > On 6 Mar 2017, at 09:28, Norbert Hartl <norbert(a)hartl.name> wrote: > > +1 > > Always true, always sad. But most changes for the good do something bad that is recognized after release. > > Norbert > > Am 06.03.2017 um 08:24 schrieb Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > >> â¦ and this is why even small additions should not be included in frozen versionsâ¦ you never know how it will impact othersâ¦ and suddenly you have a full chain of changes with unpredictable impacts. >> >> Esteban >> >>> On 6 Mar 2017, at 08:20, Aliaksei Syrel <alex.syrel(a)gmail.com <mailto:alex.syrel@gmail.com>> wrote: >>> >>> Hi, >>> >>> In order to make Sublimish theme possible there are some important changes to gt morphic brick themer, spotter and probably other gt tools. Hardcoded color and style values were already considered as a serious issue and a bug. >>> >>> Imho, we should integrate at least fixes on GT side :) >>> >>> Thanks, Phil! Great job :) >>> Alex >>> >>> On Mar 6, 2017 07:46, "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

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

by Esteban Lorenzano

> On 6 Mar 2017, at 09:22, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > > 2017-03-06 8:20 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > >> On 6 Mar 2017, at 07:57, phil(a)highoctane.be <mailto:phil@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) :) > > Well, it was me who proposed the slice and yes, I was aware of the fact that I should not do it because of code freeze (I was not aware of the two themes policy). it is not a policy, it is just the idea I have :) > > We can remove it again, I will prepare a slice. problem with it is that is makes ripples. If community want it (is nice), we can include it, but I would wait for P7, yes. Esteban > > -- Pavel > > > > > > 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

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

by Norbert Hartl

+1 Always true, always sad. But most changes for the good do something bad that is recognized after release. Norbert > Am 06.03.2017 um 08:24 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > > â¦ and this is why even small additions should not be included in frozen versionsâ¦ you never know how it will impact othersâ¦ and suddenly you have a full chain of changes with unpredictable impacts. > > Esteban > >> On 6 Mar 2017, at 08:20, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: >> >> Hi, >> >> In order to make Sublimish theme possible there are some important changes to gt morphic brick themer, spotter and probably other gt tools. Hardcoded color and style values were already considered as a serious issue and a bug. >> >> Imho, we should integrate at least fixes on GT side :) >> >> Thanks, Phil! Great job :) >> Alex >> >>> On Mar 6, 2017 07:46, "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 Pavel Krivanek

2017-03-06 8:20 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > 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/artifact/report.html 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-SublimishTheme 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) :) > Well, it was me who proposed the slice and yes, I was aware of the fact that I should not do it because of code freeze (I was not aware of the two themes policy). We can remove it again, I will prepare a slice. -- Pavel > > Esteban > > > 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

â¦ and this is why even small additions should not be included in frozen versionsâ¦ you never know how it will impact othersâ¦ and suddenly you have a full chain of changes with unpredictable impacts. Esteban > On 6 Mar 2017, at 08:20, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > > Hi, > > In order to make Sublimish theme possible there are some important changes to gt morphic brick themer, spotter and probably other gt tools. Hardcoded color and style values were already considered as a serious issue and a bug. > > Imho, we should integrate at least fixes on GT side :) > > Thanks, Phil! Great job :) > Alex > > On Mar 6, 2017 07:46, "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

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

by Aliaksei Syrel

Hi, In order to make Sublimish theme possible there are some important changes to gt morphic brick themer, spotter and probably other gt tools. Hardcoded color and style values were already considered as a serious issue and a bug. Imho, we should integrate at least fixes on GT side :) Thanks, Phil! Great job :) Alex On Mar 6, 2017 07:46, "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