+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 <[email protected]>: > > … 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 <[email protected]> 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" <[email protected]> wrote: >>> >>>> On 6 Mar 2017, at 07:17, Esteban Lorenzano <[email protected]> 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 >>> >
