- Pharo-dev - lists.pharo.org

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

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