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

Re: [Pharo-dev] GLMAction and PharoShortcut

by Andrei Chis

Hi, Good catch. Indeed GLMAction>>#shortcutAsString should go to the keymap object. Apart from the inconsistencies that you mention, there is in my view another one. For example, in the debugger in the context menu of the stack modifiers are displayed using special characters (at least on mac). In tooltips they are display using Shift, Meta, Ctrl, etc. Right now the logic for printing shortcuts that way is in ToggleMenuItemShortcut>>#owner:keyText: and it's a bit complicated to reuse. See GTSpotterCategoryTitleBrick>>#setShortcutBrickTextFor: for an example. Cheers, Andrei On Sun, Feb 12, 2017 at 11:32 AM, Hilaire <hilaire(a)drgeo.eu> wrote: > Hi, > > While writing these tooltips for the debugger, it seems to me some > refactoring is needed in the use of Pharo shortcut: > https://pharo.fogbugz.com/f/cases/19684/GLMAction-and-PharoShortcut-need-re… > > because the current situation to have Glamour tk rendering short cut as > 'Ctrl-A' then Spec as 'Meta-A' > > Any opinion on the topic. > > Hilaire > > -- > Dr. Geo > http://drgeo.eu > >

Feb. 13, 2017

Re: [Pharo-dev] [QA] Re: GLMAction and PharoShortcut

by stepharong

On Mon, 13 Feb 2017 09:41:26 +0100, Hilaire <hilaire(a)drgeo.eu> wrote: > Ok got it. It will be great to clarify the keymap implementation and > use, both for QA reasons and developers. > > What is the status of the KM hierarchy? we should continue to use and expand it. > > Hilaire > > Le 12/02/2017 Ã 18:51, stepharong a Ã©crit : >> For the record we were discussing with denis to have a hierarchy of >> command each one encapsulating its >> shortcut and other. >> Now it should work for calypso and we will remove Nautilus in 70. But >> the problem is all the places >> where shortcuts are hardcoded and we will have to work on them. >> >> Now I'm not saying that we should not do anything now to fix the current >> problem. >> I just mention our current thoughts. > -- Using Opera's mail client: http://www.opera.com/mail/

Feb. 13, 2017

[pharo-project/pharo-core] f15bc2: 60387

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: f15bc225f2afaff985407a4405312ff603867bcf https://github.com/pharo-project/pharo-core/commit/f15bc225f2afaff985407a44… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-13 (Mon, 13 Feb 2017) Changed paths: M HelpSystem-Core.package/HelpHowToHelpTopics.class/class/pages/page3.st M HelpSystem-Core.package/HelpHowToHelpTopics.class/class/pages/page5.st M HelpSystem-Core.package/HelpHowToHelpTopicsFromCode.class/class/pages/step3.st A HelpSystem-Core.package/HelpTopic.class/class/instance creation/title_iconName_contents_.st M Kernel.package/BlockClosure.class/instance/evaluating/cull_.st M Kernel.package/BlockClosure.class/instance/evaluating/cull_cull_.st M Kernel.package/BlockClosure.class/instance/evaluating/valueWithPossibleArgs_.st M Morphic-Widgets-Tabs.package/TabMorph.class/instance/protocol/softRetrieveMorph.st M Network-UUID.package/UUID.class/README.md M Network-UUID.package/UUID.class/class/instance creation/fromString36_.st M Network-UUID.package/UUID.class/class/instance creation/fromString_.st M Network-UUID.package/UUID.class/class/instance creation/new.st M Network-UUID.package/UUID.class/class/instance creation/nilUUID.st M Network-UUID.package/UUID.class/instance/converting/asString.st M Network-UUID.package/UUID.class/instance/converting/asString36.st R Network-UUID.package/UUID.class/instance/converting/asUUID_.st R Network-UUID.package/UUID.class/instance/converting/printHexAt_to_.st A Network-UUID.package/UUID.class/instance/instance creation/readFrom_.st M Network-UUID.package/UUID.class/instance/printing/printOn_.st M Network-UUID.package/UUID.class/instance/printing/printString.st A Network-UUID.package/UUID.class/instance/private/printHexAt_to_.st A Network-UUID.package/UUID.class/instance/private/readHexFrom_.st M Network-UUID.package/UUID.class/instance/testing/isNilUUID.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60386.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60387.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60386.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60387.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Tests.package/UUIDTest.class/instance/testing/testBasic.st A Tests.package/UUIDTest.class/instance/testing/testNilUUID.st R Tests.package/UUIDTest.class/instance/testing/testPrinting.st A Tests.package/UUIDTest.class/instance/testing/testString.st A Tests.package/UUIDTest.class/instance/testing/testString36.st Log Message: ----------- 60387 19689 Add method comments to cool block messages https://pharo.fogbugz.com/f/cases/19689 19687 Improve UUID documentation, implementation and test coverage https://pharo.fogbugz.com/f/cases/19687 19691 TabMorph background building animation should be in more priority than building process https://pharo.fogbugz.com/f/cases/19691 19690 Help on Help includes examples that are not executable https://pharo.fogbugz.com/f/cases/19690 http://files.pharo.org/image/60/60387.zip

Feb. 13, 2017

[pharo-project/pharo-core]

by GitHub

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

Feb. 13, 2017

Re: [Pharo-dev] Slack, fragmentation and design information

by Esteban A. Maringolo

2017-02-10 21:09 GMT-03:00 Dimitris Chloupis <kilon.alios(a)gmail.com>: > On Sat, Feb 11, 2017 at 1:52 AM phil(a)highoctane.be <phil(a)highoctane.be> > wrote: >> >> Am still finding useful stuff on Squeak wiki, sorry. >> The point of a Wiki is to capture discussions over a given topic and make >> it grow into something more structured over time. Like original c2 wiki. > I fail to see the problem here It's not a problem, it's a dynamics thing. GitHub isn't the same, I haven't seen big wikis hosted there for a long time. In the long run Pareto appears, and only a fraction of the users create most of the content, but it is still useful. In my previous job we used Squeak's Swiki for years and then we migrated it to Atlassian's Confluence (due to better user support), and it is amazing how powerful and undervalued a wiki is. If haven't used the c2 wiki or the squeak wiki then you haven't experienced what it meant, at that time, to find everything there, or expand articles with your own content. It was really useful, c2 still is. Wiki's value is like compound interest, you only perceive the benefits in the mid to long term. Regards, Esteban A. Maringolo

Feb. 13, 2017

Re: [Pharo-dev] Working with critiques in Calypso

by Denis Kudriashov

I commit new stable version. Now browser plugins can decorate any tool (which can be created by other plugins). I found that annotating text by class or package takes too long time. So I disable it. Look at implementors of #annotateTextWithCritiquesOf: to enable it and to see the problem. QA plugin morph still not works when it is built in background. (it hangs on "updating critiquies") 2017-01-31 9:52 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > 2017-01-30 15:29 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> You will see new Calypso-Plugins-Critic-Browser package. I add decorators >> support to TextEditorTool. And critic plugin just adds CriticDecorator into >> required tools. >> Sadly it is not working. Critiques are not shown somehow. >> I leave it for you to fix it. Probably reason is that full tool morph is >> prepared in background. So critiques are added when morph is not in World. >> I hope you can find solution. >> > > And to get working critiques disable background tabs: > > ClyBrowserTabTool>>addInto: aBrowser > containerTab := TabMorph > label: self defaultTitle > icon: self defaultIcon > morph: self. > self build. > containerTab when: #tabDeleted send: #tabDeleted to: self. > containerTab model: self. > aBrowser addTab: containerTab > > So question why it is not working when morph is built from background > process? >

Feb. 13, 2017

RGMethodDefinition>>gtInspectorSourceIn: does not refresh on <accept>

by Ben Coman

Anyone know if the following bug has been logged previously? I've had a quick search and not found anything. 1. #hierarchyButtonAction: inspect 2. Select [Implementors] tab. 3. Select [Source tab] 4. Edit method, the yellow dirty mark shows in the corner 5. Accept edit e.g. <Ctrl-S> ==> nothing seems to happen. The method still shows dirty, ==> but if you select [Senders] tab and back to [Source] tab ==> you see the method *was* saved. cheers -ben P.S. Its really cool to be able to edit the method here. I'm using halos to dive into a PluggableToggleButtonMorph (e.g. <Hier>) then selecting the actionSelector > Implementors > Source and insert a halt.

Feb. 13, 2017

Re: [Pharo-dev] FastTableModel switched from default single-select to multi

by Andrei Chis

Is this in the Glamour model or in the Spec one? If it's the glamour one I made some changes to the Glamour one but I don't remember changing the default to multiple selection. Maybe it's a bug :) Cheers, Andrei On Mon, Feb 13, 2017 at 12:38 AM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Breaking all code that expects selectedItem to be not-nil. > Is that wanted behaviour? I noticed it broke SpecGenerator. > I have no strong opinion on this, and welcome all Spec progress. > > Stephan > >

Feb. 13, 2017

Re: [Pharo-dev] inspector performance improvement

by Andrei Chis

On Sun, Feb 12, 2017 at 5:07 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Any chance for this to run on a 5.0? There are two main changes: moved inspector to fast table and some fixes in the glamour renderer. Moving the changes for the glamour renderer should be straightforward. I can point you to the list of relevant commits if you want to make a slice (We'll just need afterwards to also update ConfigurationOfGlamourCore to still work for Pharo 5) The FastTable changes could require more work but that should also be doable. However, now we still have some issues to fix there so that's not done for the moment. Cheers, Andrei > > Phil > > On Sun, Feb 12, 2017 at 3:13 PM, stepharong <stepharong(a)free.fr> wrote: >> >> Great job!!!! >> It feels lot snappier :) >> Now it is a real pleasure to navigate objects. >> This is nice to see that you are paying attention because the engine is >> getting faster and this is important >> that the tools do not eat all the power by accident. >> Tx a lot >> >> >> On Sat, 11 Feb 2017 21:31:56 +0100, Tudor Girba <tudor(a)tudorgirba.com> >> wrote: >> >>> Hi, >>> >>> Andrei and Alex did a great job at improving the performance and >>> scalability of the inspector. >>> >>> There are a couple of main improvements: >>> - Added FastTable support for the Raw presentation for all objects. This >>> implied completing the support for the tree presentation binding to fast >>> table. >>> - Moved the Items presentation for collections to FastTable. >>> - Improved the rendering of Glamour to no longer rely on the default >>> Morph>>#adoptPaneColor. It turns out that using adoptPaneColor triggers a >>> relayout of the morph, even if it is not visible. We extended PanelMorph in >>> the context of Glamour with a less needy logic. >>> >>> I will not tell you how fast it is. I would rather want you to play with >>> it :). >>> >>> The change is already in the Moose image. It is not yet in Pharo, but it >>> will be soon. In the meantime you can be load it in Pharo 6 like this: >>> >>> Gofer new >>> smalltalkhubUser: 'Moose' project: 'GToolkit'; >>> package: 'ConfigurationOfGToolkitCore'; >>> load. >>> (#ConfigurationOfGToolkitCore asClass project version: #stable) >>> load >>> >>> To play with it, try this with both the current version and the new one >>> and the Spec Inspector if you want (just make sure you save the image >>> beforehand): >>> >>> collection := (1 to: 100000000) asArray. >>> [collection inspect] timeToRun. >>> >>> collection := (1 to: 100000000). >>> [collection inspect] timeToRun. >>> >>> (for these two ones notice that Items do not appear at all in the old >>> implementation) >>> >>> [World inspect] timeToRun. >>> >>> >>> There are still a couple of issues open, such as the sorting of the >>> columns. We would need your help with testing this, and report possible >>> missing issues. >>> >>> Cheers, >>> Doru >>> >>> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Obvious things are difficult to teach." >>> >>> >>> >>> >>> >> >> >> -- >> Using Opera's mail client: http://www.opera.com/mail/ >> >

Feb. 13, 2017

Re: [Pharo-dev] Pharo wiki

by Alistair Grant

Hi Stef, On 13 February 2017 at 01:17, stepharong <stepharong(a)free.fr> wrote: > remember that we have this > > http://pharo.gemtalksystems.com > > stef But write access requires an account (according to http://pharo.gemtalksystems.com/book/Contribute/ContributeToPharoBook) I requested an account last year (10 May 2016 to pharo-dev) and didn't get a response. Cheers, Alistair > On Sat, 11 Feb 2017 23:22:11 +0100, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> > wrote: > > I try to use StackOverflow documentation to document some Pharo stuff. Itâs > very limited, but it has all the collaborative stuff from StackOverflow, so > somehow I believe there is less effort needed to manage permissions. > > Uko > > On 10 Feb 2017, at 21:14, philippe.back(a)highoctane.be > <philippe.back(a)gmail.com> wrote: > > I miss the Squeak wiki Pharo style. > > Phil > > Le 10 fÃ©vr. 2017 19:06, "Esteban A. Maringolo" <emaringolo(a)gmail.com> a > Ã©crit : >> >> 2017-02-10 14:59 GMT-03:00 phil(a)highoctane.be <phil(a)highoctane.be>: >> > Mass adoption and hyper reduced friction to get people on board. >> > >> > For me: I have 10+ slack teams in my slack client and there is really no >> > point in having more clients on the desktop. >> >> +1 to this. This is key. >> >> Maybe what we're missing is a simple wiki to collect the shared >> knowledge, recipes, and other stuff. >> >> >> Esteban A. Maringolo

Feb. 13, 2017