- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

Feb. 21, 2017

[pharo-project/pharo-core] 54984d: 60406

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 54984d819f4c7d14b63fdf7dd0f9927c8c013a63 https://github.com/pharo-project/pharo-core/commit/54984d819f4c7d14b63fdf7d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-21 (Tue, 21 Feb 2017) Changed paths: A Kernel.package/CombinedChar.class/class/initialization/parseCompositionMappingFrom_.st M Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/accessing colors/secondarySelectionColor.st M Rubric.package/RubExtraSelectionDecorator.class/instance/drawing/computeSecondarySelectionShapesFrom_to_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60405.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60406.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60405.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60406.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Traits.package/TClassDescription.class/instance/private/newInstanceFrom_variable_size_.st R Unicode-Initialization.package/extension/CombinedChar/class/parseCompositionMappingFrom_.st Log Message: ----------- 60406 19731 secondary selection color should be not modified https://pharo.fogbugz.com/f/cases/19731 19538 When replacing a slot in class by WeakSlot, it fails to migrate existing instances https://pharo.fogbugz.com/f/cases/19538 19603 composition mapping should be initialized on bootstrapped image https://pharo.fogbugz.com/f/cases/19603 http://files.pharo.org/image/60/60406.zip

Feb. 21, 2017

[pharo-project/pharo-core]

by GitHub

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

Feb. 21, 2017

[pharo-project/pharo-core] 663230: 60405

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 66323053a8e12e95372e9602cc1ee41ccabd9a64 https://github.com/pharo-project/pharo-core/commit/66323053a8e12e95372e9602… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-21 (Tue, 21 Feb 2017) Changed paths: M BaselineOfMorphic.package/BaselineOfMorphic.class/instance/actions/postload_package_.st A Polymorph-Widgets.package/Pharo3DarkTheme.class/instance/accessing colors/lessConspicuousColorFrom_.st M Polymorph-Widgets.package/UITheme.class/class/accessing/current_.st A Polymorph-Widgets.package/UITheme.class/instance/accessing/lessConspicuousColorFrom_.st M Rubric.package/RubPrimarySelectionMorph.class/instance/accessing/selectionColor.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60404.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60405.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60404.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60405.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Shout.package/SHTextStylerST80.class/class/style table/darkStyleTable.st M SublimishTheme.package/SublimishTheme.class/class/settings/newDefaultSettings.st Log Message: ----------- 60405 19730 RubPrimarySelectionMorph>>#selectionColor does not respect theme style https://pharo.fogbugz.com/f/cases/19730 19735 Desktop color issue in the bootstrapped image https://pharo.fogbugz.com/f/cases/19735 19658 Red in Dark Theme is plain bad https://pharo.fogbugz.com/f/cases/19658 19734 Sublimish theme menu text selection should be not black https://pharo.fogbugz.com/f/cases/19734 http://files.pharo.org/image/60/60405.zip

Feb. 21, 2017

Re: [Pharo-dev] ***Important*** Snapcraft pharo package for Pharo 50

by Holger Freyther

> On 19 Jan 2017, at 00:25, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi! > wowâ¦ this is super good, Holger, I want this since ages ! Great. The obs people will create a pharo organization for us. > merge is done. > there are 5 failing tests (and I still do not configure the tests for 64bits)â¦ I will work a bit on this this week, but Iâm finishing 3 things at the same time now (FFI 64bits, iceberg multi-remotes and this) so it will arriveâ¦ anytime soon. What is the state of the unit tests and which tests fail? Are these genuine regressions compared to the Pharo5 VM? > I wouldnât wait until the tests are running :) I am struggling with the squeak-vm build system right now. It is doing so many things in a non-standard way and it is getting more and not less. I am currently struggling with the install part. To illustrate the challenge: * Standard systems would use DESTDIR as variable to not directly install to /usr/bin/foo but $(DESTDIR)/usr/bin/foo. Squeakvm has only "prefix" * There is a script to rename "squeak" to "pharo" after things were installed * It creates a "squeak" shell script that tries to find the real squeak, this will make dual (64bit, 32bit) installation more hard as well... let's see how far I get today holger

Feb. 21, 2017

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

by Denis Kudriashov

Ok. Question was from Martin. What behaviour we want from WeakValueDictionary for garbaged values? dictionary := WeakValueDictionary with: 'hello' -> 'world' copy. > Smalltalk garbageCollect. > { > dictionary values includes: nil. > dictionary at: 'hello'. > dictionary at: 'hello' ifAbsent: [ 'absent' ]. > dictionary at: 'hello' ifAbsentPut: [ 'put' ]. > } > is: > #(true nil nil nil) My opinion is: it should work in same way when 'hello' item is absent. It is intuitive for me and It would be consistent to WeakSet behaviour: set := WeakSet with: Object new. Smalltalk garbageCollect. set includes: nil "=>false" But after writing it I realized how much WeakSet is inconsistent: set := WeakSet with: Object new. Smalltalk garbageCollect. set isEmpty. "=>false" set size. "=>1". set anyOne. "=> nil" set includes: nil. "=>false" set collect: #yourself. "=>a WeakSet()" We definitely have something to improve here. 2017-02-21 13:36 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > Everything has a tradeoff. I do not understand the question. > > On Tue, Feb 21, 2017 at 1:19 PM, Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: > >> >> 2017-02-21 13:07 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: >> >>> But in any case, whatever the alternative you give users, they must >>> understand the tradeoff. If all Weak*Dictionaries were subscribed by >>> default to the weak registry for cleanup, that would provoke a lot of >>> overhead during garbage collection. >>> >> >> So you think my suggestion for implementation will lead to some tradeoff? >> What exactly? (if yes). >> > >

Feb. 21, 2017

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

by Guillermo Polito

Everything has a tradeoff. I do not understand the question. On Tue, Feb 21, 2017 at 1:19 PM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > > 2017-02-21 13:07 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> But in any case, whatever the alternative you give users, they must >> understand the tradeoff. If all Weak*Dictionaries were subscribed by >> default to the weak registry for cleanup, that would provoke a lot of >> overhead during garbage collection. >> > > So you think my suggestion for implementation will lead to some tradeoff? > What exactly? (if yes). >

Feb. 21, 2017

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

by Denis Kudriashov

2017-02-21 13:07 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > But in any case, whatever the alternative you give users, they must > understand the tradeoff. If all Weak*Dictionaries were subscribed by > default to the weak registry for cleanup, that would provoke a lot of > overhead during garbage collection. > So you think my suggestion for implementation will lead to some tradeoff? What exactly? (if yes).

Feb. 21, 2017

Re: [Pharo-dev] WeakValueDictionary: shouldn't be "absent" after GC?

by Guillermo Polito

On Tue, Feb 21, 2017 at 10:37 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > 2017-02-21 9:44 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > >> Hi Dr. Dias, >> >> a WeakValueDictionary get's its values collected if they are not >> referenced strongly. However, the association remains there. This means >> that when you do: >> >> dictionary := WeakValueDictionary with: 'hello' -> nil copy. >> >> You'll have something like this: >> >> WeakValueDictionary { >> WeakValueAssociation { key: 'hello', value: yourObject } >> } >> >> Once you garbage collect, the value is holding yourObject weakly, so >> you'll have: >> >> WeakValueDictionary { >> WeakValueAssociation { key: 'hello', value: nil } >> } >> >> But the WeakValueAssociation will still be there. >> >> > For me what you describe is implementation details and users should not > think about it at all. > Of course it is an implementation detail. I'm just describing how it works (and thus, how it does not work). I never said it was a good or bad approach. I agree ifAbsent~ messages should work with collected values by "absent > branch". It is intuitive. > > To support it correctly we can use approach of Set which uses > #asSetElement to store items. Then we can easily distinguish nil from > absent value. Real nil value will happen only by garbage collection. > But I am wondering WeakSet not uses SetElement approach directly and > instead it uses special flag object. Maybe it should be fixed too. > But in any case, whatever the alternative you give users, they must understand the tradeoff. If all Weak*Dictionaries were subscribed by default to the weak registry for cleanup, that would provoke a lot of overhead during garbage collection. Magic is good in some cases, but when you're dealing with low level stuff explicitly (like instantiating a Weak*Dictionary) I prefer to control some of that magic explicitly.

Feb. 21, 2017

Re: [Pharo-dev] Catalog loading in Spotter

by Torsten Bergmann

As there were no further objections I guess we should do the following steps as a compromise: 1. We switch back to how it was by selecting Solution A as it is the old behavior and the pragmatic approach. This avoids the confusion, allows to quickly search for the catalog items and also renders the videos valid again. 2. Pharo 6 is still not released. People can still be testing and if this really gives trouble again (maybe next time in a reproducible way) we can try to fix it/find another solution. In the worst case we can disable it by disabeling the Catalog setting (not the GT extension itself) so it is not confusing or hidden again in the Pharo settings. I've opened issue https://pharo.fogbugz.com/f/cases/edit/19732 and will fix it. Lets see how it goes. Thanks T. > Gesendet: Montag, 20. Februar 2017 um 11:27 Uhr > Von: "Sven Van Caekenberghe" <sven(a)stfx.eu> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] Catalog loading in Spotter > > > > On 20 Feb 2017, at 10:30, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > > > > > > > > 2017-02-20 10:27 GMT+01:00 Guillermo Polito <guillermopolito(a)gmail.com>: > > As far as I remember, the main problem was not bandwidth but a blocking and non-responsive UI. > > Imagine I'm in the university, or in a company with a proxy. And I forget to set the proxy. Then, while spotter tries to fetch catalog entries, it would block the image and throw a timeout error some minutes after. > > > > So, maybe for the future and besides Ben's C option (which I like) I have a > > > > D) Load catalog entries in background in a non-blocking way > > - and while catalog entries are not yet available, they should not be shown > > > > AFIK the main problem was that there was not possilbe to do it non-blocking way. > > Yes that is true. (It is actually DNS resolving that is blocked in some freak case). > > But the thing is, the problematic situation only occurs for a very small percentage of people, like less than 1%, probably even much less. (Remember, nobody can produce a repeatable case for it). > > So the question is, is that enough reason to act as if we are still in the 90's when internet was a luxury and cut features that depend on it ? If you have no network today, you're in big trouble anyway. (Again, if you turn off your network, no blocking will happen at all, try it). > > So what is more important ? The general functionality of the 99.xxx % or the unreproducible freak case ? > > > -- Pavel > > > > > > Even further, It would make sense a solution that mixes Ben's caching with background loading of the catalog entries... > > > > Guille > > > > On Mon, Feb 20, 2017 at 1:03 AM, Ben Coman <btc(a)openinworld.com> wrote: > > On Mon, Feb 20, 2017 at 4:05 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > > > In the past in Pharo it was possible to open Spotter, type in the name of a framework/project to load > > > from catalog, perform a search and just hit ENTER to easily install the project. > > > > > > This was following the Spotter idea that it is easy to access most informations of Pharo > > > with the Spotter tool. > > > > > > There always was and still is a setting in "Settings" -> "Catalog" -> "Display catalog projects in Spotter". > > > This setting is ENABLED BY DEFAULT but could be switched off in the settings tool or custom preference > > > scripts if this is problematic for someone. > > > > > > > > > Now in Pharo 6 there is an additional class "GTSpotterExtensionSettings" to activate/deactivate > > > Spotter extensions. While nearly all of the Spotter extensions are enabled the one for the catalog > > > integration is DISABLED BY DEFAULT. > > > > > > This leads to several effects: > > > > > > 1. While in the past it was possible in a fresh Pharo image to search and install out of > > > the box it is (as of today in the not yet released Pharo 6) not possible anymore to quickly > > > start by searching and installing from catalog using Spotter. > > > > > > 2. It is very confusing that in the settings "Display catalog projects in Spotter" is enabled but a search > > > in Spotter gives no results. Most people will not not know about the second setting and easily > > > get lost and think this behavior is just broken. > > > Also this second setting for the Spotter extension is much more hidden between all the other > > > Spotter extension enablements very and hard to find. > > > > Generally its not good to have two settings for the one thing. > > > > > > > > 3. Several of my youtube videos demonstrating Goodies like DesktopManager, QuickAccess, > > > MessageFlowBrowser, ... directly start by loading the tools from Spotter. Anyone newbee who will > > > follow these will not only be confused - but also stuck in trying Pharo when he learns > > > from these videos. > > > > UI things do evolve and videos date. But these seem worthwhile to keep current. > > > > > > > > I was asked several times on Slack and via Mail from people who were not able to reproduce ... this > > > is really annyoing. Especially this gives the wrong impression to newbees. Things should be easy > > > not complicated. > > > > > > To my knowledge disabling the Spotter search in Pharo 6 came up due to some Pharo teaching in regions > > > with slow internet connection. > > > > This made sense at the time. It is a worse first impression if UI > > lags when this central part of the UI is interfaced. > > How often would it access the network? Every time? Or did it cache > > the result for a day, etc? > > > > > I understand that we would like to support these Pharo users too as best > > > as possible in their out of the box experience ... but (without being able to prove) I think that 90% or > > > more Pharo users have a regular internet connection. Otherwise it would be hard to work with updates, > > > project loading, PharoLauncher, STHub or Iceberg/GitHub. > > > > > > Also my own personal experience is that even on low bandwidth network this Catalog Spotter search for > > > me was always fast enough (as I often use Pharo in trains with slow connections or on a Pi with slow > > > connections and less processing power). I do not know about all others from the community. > > > > > > I invested hours in the past in developing and introducing the initial configuration browser to Pharo, > > > later improved and helped shaping its replacement CatalogBrowser, also contributed this spotter search > > > for the catalog items so things are more accessible, easy and enjoyable. That's why I also invested > > > hours in udpating configs or pushing you to put things into catalog. > > > > > > Because accessibility is key. Only when things are easy to access and understandable people will > > > enjoy Pharo. > > > > > > Currently in an out-of the box image this easy access to the projects via Spotter is blocked. > > > Additionally I have to explain to anyone who asks me that there is a second non-obvious/more hidden setting > > > leaving an unpleasant feeling how many others unknown to me will struggle with this issue. > > > > > > I see two solutions: > > > > > > A) We enable both settings by DEFAULT to bring back the Spotter search and installation > > > of catalog items - with the clear benefit of having > > > - the previous behavior in Pharo back > > > - the out of the box ability to search for catalog projects in any fresh image > > > - no confusion among the user base anymore regarding the settings > > > - we have unbroken Youtube videos that newbees can continue to follow > > > - if a user asks (like often) how to get Seaside, Artefact, Mongo, Teapot or other projects we can > > > just tell him "search in Spotter and you should be fine" as most of them have a config in > > > the catalog. > > > > > > Remember that not all of us know about all the github pages or nice Metacello expressions. > > > So the easier things are found and accessible the better it is. > > > > > > B) If A is still a "No go" for the community we should at a minimum switch the defaults of > > > the two settings: > > > > > > => we ENABLE the Spotter extension (GTSpotterExtensionSettings perform: #GTSpotter_spotterCatalogProjectsFor: with: true) > > > => we DISABLE the catalog setting (CatalogSettings displayCatalogProjectsInSpotter: false) > > > > > > With this at least we have no confusion among the user base anymore regarding the settings. > > > > C) Could a STON file of the catalog be cached in the zip of > > Image/Changes files? > > That zip might be updated daily to keep it current. > > Then in a fresh image Spotter searches the cached file for a instant response, > > while the Catalog is updated from the network in the background. > > > > Even with fast Internet the Catalog should only need to auto-update once a day, > > with results cached in a common file to be accessed when fresh images > > are started. > > > > The Spotter UI might display the last update date as part of the > > Catalog sub-heading in its results. > > > > cheers -ben > > > > > > > > I would clearly and strongly vote for option A as my preferred one. > > > > > > I agree there are regions/continents with very low bandwidth - but Pharo will rival with state of the art > > > technologies where loading/installation megabytes from the web is often not seen as an issue. There are > > > many package registries out there (from debian packages) up to Maven, npm in JS, ... or look at Docker. > > > Shuffling megabytes around is a reality in todays technologies. > > > > > > So to be honest I never understood this whole "bandwidth" discussion and even if this comes up it could > > > be solved with a note in the download/welcome screen or pointing to a custom preference script for low bandwidth > > > situations. > > > > > > Sorry for having to bring this up again ... but I would like this to be solved BEFORE Pharo 6 will > > > be pushed out of the door. Keeping it like it is without further actions would be really stupid. > > > > > > Thanks for you comments, ideas or votes. > > > > > > Thanks > > > T. > > > > > > > > > > > >

Feb. 21, 2017