June 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GT-Spotter dive in shortcut

by Nicolai Hess

Am 07.06.2016 1:56 nachm. schrieb "Henrik Nergaard" <henrik.nergaard(a)uia.no >: > > IIRC the shortcut is not changed, it still is meta+right(+shift). Only the tooltip was changed to display the system specific key instead of âcmdâ so for Windows/Linux this would be âctrlâ. No, it changed > > > > Best regards, > > Henrik > > > > From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Nicolai Hess > Sent: Tuesday, June 7, 2016 12:56 PM > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Subject: [Pharo-dev] GT-Spotter dive in shortcut > > > > Why did the shortcut for dive-in element/category changed from > > cmd+right > > cmd+shift+right > > to > > ctrl+right > ctrl+shift+right > > I know there were some discussions about this and that the behavior changed some > > time ago, but I don't know the rational behind this. > > thanks > > nicolai > >

June 7, 2016

Re: [Pharo-dev] GT-Spotter dive in shortcut

by Henrik Nergaard

IIRC the shortcut is not changed, it still is meta+right(+shift). Only the tooltip was changed to display the system specific key instead of âcmdâ so for Windows/Linux this would be âctrlâ. Best regards, Henrik From: Pharo-dev [mailto:pharo-dev-bounces@lists.pharo.org] On Behalf Of Nicolai Hess Sent: Tuesday, June 7, 2016 12:56 PM To: Pharo Development List <pharo-dev(a)lists.pharo.org> Subject: [Pharo-dev] GT-Spotter dive in shortcut Why did the shortcut for dive-in element/category changed from cmd+right cmd+shift+right to ctrl+right ctrl+shift+right I know there were some discussions about this and that the behavior changed some time ago, but I don't know the rational behind this. thanks nicolai

June 7, 2016

Re: [Pharo-dev] GT-Spotter dive in shortcut

by Esteban Lorenzano

is most probably an error :S > On 07 Jun 2016, at 12:55, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > Why did the shortcut for dive-in element/category changed from > cmd+right > cmd+shift+right > > to > > ctrl+right > ctrl+shift+right > > I know there were some discussions about this and that the behavior changed some > time ago, but I don't know the rational behind this. > > > thanks > nicolai > >

June 7, 2016

Re: [Pharo-dev] Playground and text evaluation printing result default.

by Ben Coman

On Tue, Jun 7, 2016 at 2:09 PM, stepharo <stepharo(a)free.fr> wrote: > > > Le 5/6/16 Ã 23:00, Tudor Girba a Ã©crit : >> >> Hi Stef, >> >> The quotes appear only when you add the result in the playground. > > > No need to explain I'm not idiot and I know it. >> >> The typical use case for this is to keep track of several results. > > No need to explain I'm not idiot and I know it. >> >> In this situation you do not want to modify the code to not affect the >> highlighting and this is why it gets in a comment. > > This is fun because I never ever needed it. But this is probably what > everybody else is doing that since this is the default. > I just write simple code and tests. Indeed I'm not that smart. > > But your tools only embedd your scenario and let the other users forced to > adapt. > > Well you do not want but I do. > I spent my evening removing quotes while writing tests. > > What I hate with the GTTools is that you want to teach me how I should work. > Sorry but good tools do not do that. > Good tools empower the users and not constraint them. > > I work a lot faster when I do not have to remove the wonderful comments or > when I have to copy and paste. > This commenting is breaking the flow of efficient people. May be GT team do > not work write tests in the > debugger but I do most of the time and I'm forced by the environment to > remove quotes all over the places. >> >> If you want to copy the content without quotes, you can do: >> Cmd+p -> popup >> Cmd+c -> selects the current line and copies the text >> Esc >> Cmd+v > > Sorry but I do not want. > I just want to print and modify directly. > 7 keystrokes vs 2 >> >> Perhaps we can add another keybinding like Shift+Enter for adding the text >> without quotes. I just had a play with this, and another option might be <ctrl-enter>, since the <ctrl> key is still selection from doing <ctrl-P> so there is not much difference in hand movements between <enter> and <ctrl-enter> cheers -ben > > And why not the inverse. > By default printing is printing and if you want to do something else then > you have a special binding. > Now I'm upset with this general attitude (Oh I will teach how you can be a > nice user) that I will turn them off > or go and hack my own settings. Still I'm amazingly sad about this state of > affair. > All these story about GT is hurting me because of this attitude: we are so > smart and we thought a lot and we will teach you > how you should work... and at the end I the end-user has to adapt. > Look at the Spotter discussions: you looked for the graal and I was just > telling to you that I cannot find > simple information such as class refs! > > So what saddens me the most is that > - you pretend to have end-user trying your tools but I have impression > that they are not real power users > or this is yourself and it means that you are never exposed to other > people. > I can still not use Spotter because the way I put my hand on my > keyboard. So should change > - 1 my hands > - 2 my brain > - 3 my keyboard > - 4 do not use the tools? > - funnily enough if I would not have complain aggressively then it looks > like we would have the same than before. > > Your flow is not mine and I go faster my way but your tools force me to get > slow. > I do not have the time to produce a video but I would even if it would give > a bad press to Pharo. > I will do a presentation in the rmod team. Because people do not watch > themselves why acting. > > Good tools empower the users not constraint them. > > GTTools feel often like an overengineer guitar that would have hampered > Jimmy Hendrix to do crazy solos. > >> >> Cheers, >> Doru >> >> >> >>> On Jun 5, 2016, at 10:20 PM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Hi >>> >>> I would like to know if there is a setting to remove the "" when printing >>> the result of an expression. >>> >>> I know that playground has been thought to help me, but today I watched >>> myself removing the comments >>> >>> code so often that I would like to get a setting because such wrapping of >>> results is really boring for me. >>> >>> I'm spending my time removing them and I start to wonder why they are any >>> useful. >>> >>> I would help me to write fast tests for example in the debugger. >>> >>> Stef >>> >>> >>> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "What we can governs what we wish." >> >> >> >> >> >> > >

June 7, 2016

GT-Spotter dive in shortcut

by Nicolai Hess

Why did the shortcut for dive-in element/category changed from cmd+right cmd+shift+right to ctrl+right ctrl+shift+right I know there were some discussions about this and that the behavior changed some time ago, but I don't know the rational behind this. thanks nicolai

June 7, 2016

[pharo-project/pharo-core]

by GitHub

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

June 7, 2016

[pharo-project/pharo-core] 092dbb: 60067

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 092dbb81541495f197593e5877cd011ea655c6c1 https://github.com/pharo-project/pharo-core/commit/092dbb81541495f197593e58… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-06-07 (Tue, 07 Jun 2016) Changed paths: M ConfigurationOfGTEventRecorder.package/ConfigurationOfGTEventRecorder.class/instance/symbolic versions/stable_.st A ConfigurationOfGTEventRecorder.package/ConfigurationOfGTEventRecorder.class/instance/versions/version017_.st M ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version313_.st M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version211_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/baselines/baseline33_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version416_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60066.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60067.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60066.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60067.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60067 18403 ConfigurationOfGTInspectorCore needs update versions of dependencies https://pharo.fogbugz.com/f/cases/18403 18423 Fix Glamour-Tests-Core extensions capitalization https://pharo.fogbugz.com/f/cases/18423 18402 ConfigurationOfGTSpotter needs update versions of dependencies https://pharo.fogbugz.com/f/cases/18402 http://files.pharo.org/image/60/60067.zip

June 7, 2016

Re: [Pharo-dev] Privacy sendDiagnosticsAndUsageData should be ternary, not binary

by Andrei Chis

Hi Peter, On Tue, Jun 7, 2016 at 12:05 AM, Peter Uhnak <i.uhnak(a)gmail.com> wrote: > Hi, > > Privacy>>sendDiagnosticsAndUsageData should be ternary, not binary. > > Because right now if I refuse sending the data I will be asked again every > single time. > Indeed right now, at least in Spotter, the notification is shown every time it is opened in a new image, even if the setting was explicitly set. It was done like this as a reminder, especially if you have the setting set to true. > > So the proper behavior (imho) should be: > > ask Privacy for the settingâ¦ if the setting is not defined, then show a > popup. > If the setting is defined then respect it and do not show another popup. > The current behaviour with showing the notification in Spotter and Nautilus should be a temporary one. Ideally we just need a single uniform way of showing this notification plus the option to control and see the data that each tool wants to record at a fined-grained level. > > Also it would be nice to know what happens with the data. > We store it on a server and use it for various analyses. It is also publicly available: GTEventTool default download. > I mean my projects are open source so "sendSourceCode" shouldn't be an > issueâ¦ but what you can possibly learn from it? > Why not just analyze the content of SmalltalkHub/GitHub? > Because if you have the setting enabled it does not always work to map different actions that with the code that you are working on. Cheers, Andrei > > Peter > >

June 7, 2016

[ANN] Ephemeron Support is Ready

by Guille Polito

Hi All, Since this morning, in Pharo #60065, Ephemeron support is in the image. Most of the changes are infrastructural, so far transparent for the users. It is important to notice that even while the support is there, it is not enabled by default. Also, this required changes in the virtual machine that are not yet distributed everywhere. For the ones that would like more detail, I invite you to read the following :) * On the infrastructure side - There is support to create Ephemeric classes and load them from monticello - There is a new finalization mechanism (by default disabled) that will process Ephemerons using a finalization queue. This will avoid scanning collections in look for weak objects to finalize ,as it happens now with the WeakDependent mechanism in WeakArray. - System-Finalization features two new classes *Ephemeron* and *EphemeronRegistry*. For the ones that want more details on Ephemerons, you can read the associated paper [1], or the class comment of Ephemeron: I represent ephemeric key-value objects. Ephemerons are key-value objects (subclasses of Association) with special semantics during garbage collection. My special behavior can resumed as follows: - The garbage collection will iterate my instances only if the key is not referenced strongly by another object. - Then, if no strong references to the key are found, then the values of this ephemeron are hold weakly. - Otherwise, the values are hold strongly. In this implementation, an Ephemeron can hold more than one value, which are all treated in the same manner. This ephemeron instance knows its container, which allows the ephemeron to remove itself from a container (such as a Dictionary) upon finalization. !! Example usages In general terms, do not use myself directly. Use instead an Ephemeric container like EphemeronRegistry. An Ephemeron registry will guarantee the collection of keys and values of the object inside the Ephemeron. Otherwise, if you want to use it, you can create an Ephemeron as any association: ephemeron := Ephemeron key: aKey value: aValue. ephemeron container: aContainer. !! Ephemeron Finalization When an ephemeron's key is hold strongly just by the ephemeron itself, the Ephemeron will be mourned (finalized). That means that the VM will: - put the Ephemeron in the mourning queue waiting for the image to take care of mourning - make the Ephemeron non ephemeric. That is, the ephemeron instance cannot be reused. On the image side, the finalization process will send the message #mourn to an Ephemeron. #mourn will #finalize the Ephemeron's key, and remove the Ephemeron from it's container to allow its collection during a subsequent garbage collection. !! More Documentation You can read the associated paper to understand better the semantics of ephemerons: [1]Ephemerons: A New Finalization Mechanism. Barry Hayes. OOPSLA '97 - WARNING: to be able to use ephemerons, you need to use the *latestVm* that has several fixes for making ephemerons work, and you need to enable ephemerons on the image side by evaluating: Smalltalk supportsQueueingFinalization: true. - With latest vm and ephemerons enabled, tests should be green, otherwise they are skipped * From the user point of view: - The Weak registries were not yet migrated to the new finalization mechanism. - We expect nothing will change from the user point of view. Just less memory leaks. * Next steps (in order) 1) Bless the latest vm as stable 2) Enable queueing finalization by default 3) Replace Weak Registry by Ephemeron Registry. Informed by: Guille

June 7, 2016

[pharo-project/pharo-core]

by GitHub

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

June 7, 2016