- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GTPlayground Play Button Semantics

by Esteban Lorenzano

and btw, what about remap cmd+o to cmd+e (like âexecuteâ) ? Esteban > On 01 Oct 2014, at 16:05, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei(a)gmail.com <mailto:chisvasileandrei@gmail.com>> wrote: > >> >> >> On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> Was it a conscious decision to make the GTPlayground Play button act as 'play all' (evaluate the whole workspace contents) ? >> >> If so, why ? >> >> I find it quite limiting that I cannot select some expression and 'play it'. A workspace/playground is like a notebook containing lots of different things. >> >> >> Yes, it is like this by design. The Play button at the top evaluates the entire content of the workspace. >> >> To evaluate just an expression you can select it and choose 'Open' from the context menu, or use CMD+o. >> Just right now CMD+o is still broken due to the global shortcuts from opening tools. >> >> The Play button at the top works like that as we tried to have in the toolbar only global actions that apply on the entire presentations and not only on the selection. >> Those that apply on the selection go in the context menu and should have keybindings >> >> Does this seem ok to you? > > Ah, I thought the open menu action worked like the inspect it menu action. > OK, that works for me. > > Thanks. > >> Cheers, >> Andrei >> >> >> Sven

Oct. 1, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by Sven Van Caekenberghe

On 01 Oct 2014, at 16:00, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > > > On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Was it a conscious decision to make the GTPlayground Play button act as 'play all' (evaluate the whole workspace contents) ? > > If so, why ? > > I find it quite limiting that I cannot select some expression and 'play it'. A workspace/playground is like a notebook containing lots of different things. > > > Yes, it is like this by design. The Play button at the top evaluates the entire content of the workspace. > > To evaluate just an expression you can select it and choose 'Open' from the context menu, or use CMD+o. > Just right now CMD+o is still broken due to the global shortcuts from opening tools. > > The Play button at the top works like that as we tried to have in the toolbar only global actions that apply on the entire presentations and not only on the selection. > Those that apply on the selection go in the context menu and should have keybindings > > Does this seem ok to you? Ah, I thought the open menu action worked like the inspect it menu action. OK, that works for me. Thanks. > Cheers, > Andrei > > > Sven > > >

Oct. 1, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by Damien Cassou

On Wed, Oct 1, 2014 at 4:00 PM, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > Does this seem ok to you? makes perfect sense to me. Toolbar is for global stuff, context menu for contextual stuff. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Oct. 1, 2014

Re: [Pharo-dev] Confused about the GTInspector State Tab

by Sven Van Caekenberghe

But we cannot all start doing different things, right ? There should be some design and structure, that is why I am asking. On 01 Oct 2014, at 15:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > cool thing of this new inspector is that is super easy to extend with what you want > So wouldnât be complicated to add that functionality :) > > Esteban > > >> On 01 Oct 2014, at 15:51, Ben Coman <btc(a)openInWorld.com> wrote: >> >> Sven Van Caekenberghe wrote: >>> I am confused about the GTInspector State tab. What is its definition ? >>> I would say that it shows the raw, fundamental, implementation form of the object, in essence what EyeBasicInspector showed. And that additional tabs offer alternative, more user friendly views. >>> Why then does it not show all variable content and only named variables ? >>> Try inspecting a [Byte]String or [Byte]Array. The State view is useless, it just shows self. Some of these have an items view, but not all. >>> How can I inspect an individual character of a String ? Or an individual byte ? >>> Consider a Float. The State view should show the two (meaningless) slots because that is how Floats are (currently) implemented, and then another tab should show the sign, mantissa, exponent view. >>> In the Eye inspectors we also confused these two aspects in a single view, which is wrong in hindsight, IMHO. It should be crystal clear for a user whether a slot is real or an alternative view of describing the same thing. >>> I could propose changes or a slice, but I think we should agree on the definition of 'State' first. >>> Sven >> >> If its a raw slots view you want, >> maybe that tab should be called 'Slots' ? >> cheers -ben >> > >

Oct. 1, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by Andrei Chis

On Wed, Oct 1, 2014 at 3:14 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Was it a conscious decision to make the GTPlayground Play button act as > 'play all' (evaluate the whole workspace contents) ? > > If so, why ? > > I find it quite limiting that I cannot select some expression and 'play > it'. A workspace/playground is like a notebook containing lots of different > things. > Yes, it is like this by design. The Play button at the top evaluates the entire content of the workspace. To evaluate just an expression you can select it and choose 'Open' from the context menu, or use CMD+o. Just right now CMD+o is still broken due to the global shortcuts from opening tools. The Play button at the top works like that as we tried to have in the toolbar only global actions that apply on the entire presentations and not only on the selection. Those that apply on the selection go in the context menu and should have keybindings Does this seem ok to you? Cheers, Andrei > > Sven > > >

Oct. 1, 2014

Re: [Pharo-dev] Confused about the GTInspector State Tab

by Esteban Lorenzano

cool thing of this new inspector is that is super easy to extend with what you want So wouldnât be complicated to add that functionality :) Esteban > On 01 Oct 2014, at 15:51, Ben Coman <btc(a)openInWorld.com> wrote: > > Sven Van Caekenberghe wrote: >> I am confused about the GTInspector State tab. What is its definition ? >> I would say that it shows the raw, fundamental, implementation form of the object, in essence what EyeBasicInspector showed. And that additional tabs offer alternative, more user friendly views. >> Why then does it not show all variable content and only named variables ? >> Try inspecting a [Byte]String or [Byte]Array. The State view is useless, it just shows self. Some of these have an items view, but not all. >> How can I inspect an individual character of a String ? Or an individual byte ? >> Consider a Float. The State view should show the two (meaningless) slots because that is how Floats are (currently) implemented, and then another tab should show the sign, mantissa, exponent view. >> In the Eye inspectors we also confused these two aspects in a single view, which is wrong in hindsight, IMHO. It should be crystal clear for a user whether a slot is real or an alternative view of describing the same thing. >> I could propose changes or a slice, but I think we should agree on the definition of 'State' first. >> Sven > > If its a raw slots view you want, > maybe that tab should be called 'Slots' ? > cheers -ben >

Oct. 1, 2014

Re: [Pharo-dev] Confused about the GTInspector State Tab

by Ben Coman

Sven Van Caekenberghe wrote: > I am confused about the GTInspector State tab. What is its definition ? > > I would say that it shows the raw, fundamental, implementation form of the object, in essence what EyeBasicInspector showed. And that additional tabs offer alternative, more user friendly views. > > Why then does it not show all variable content and only named variables ? > > Try inspecting a [Byte]String or [Byte]Array. The State view is useless, it just shows self. Some of these have an items view, but not all. > > How can I inspect an individual character of a String ? Or an individual byte ? > > Consider a Float. The State view should show the two (meaningless) slots because that is how Floats are (currently) implemented, and then another tab should show the sign, mantissa, exponent view. > > In the Eye inspectors we also confused these two aspects in a single view, which is wrong in hindsight, IMHO. It should be crystal clear for a user whether a slot is real or an alternative view of describing the same thing. > > I could propose changes or a slice, but I think we should agree on the definition of 'State' first. > > Sven > > > If its a raw slots view you want, maybe that tab should be called 'Slots' ? cheers -ben

Oct. 1, 2014

[pharo-project/pharo-core] 6d0d66: 40276

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 6d0d667c65fb0ff32cad8d3e06f8614ab93d1543 https://github.com/pharo-project/pharo-core/commit/6d0d667c65fb0ff32cad8d3e… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-01 (Wed, 01 Oct 2014) Changed paths: A ConfigurationOfGTInspector.package/ConfigurationOfGTInspector.class/instance/versions/version103_.st A ConfigurationOfGTPlayground.package/ConfigurationOfGTPlayground.class/instance/versions/version103_.st A ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version272_.st A ConfigurationOfRubric.package/ConfigurationOfRubric.class/instance/versions/version121_.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoCodeRenderer.class/instance/callbacks/evaluateAndPopPrintSelection.st R Glamour-Morphic-Renderer.package/GLMMorphicRenderer.class/instance/rendering presentations/renderRubricSmalltalkCodePresentation_.st R Glamour-Morphic-Renderer.package/GLMMorphicRubricSmalltalkCodeRenderer.class/README.md R Glamour-Morphic-Renderer.package/GLMMorphicRubricSmalltalkCodeRenderer.class/definition.st R Glamour-Morphic-Renderer.package/GLMMorphicRubricSmalltalkCodeRenderer.class/instance/rendering/morph.st M Glamour-Morphic-Widgets.package/GLMErrorPopper.class/README.md A Glamour-Morphic-Widgets.package/GLMErrorPopper.class/class/examples/simpleErrorPopper.st M Glamour-Morphic-Widgets.package/GLMPopper.class/README.md A Glamour-Morphic-Widgets.package/GLMPopper.class/class/utils/installAlarmFor_.st M Glamour-Morphic-Widgets.package/GLMPopper.class/instance/private/updateWithString_from_.st M Glamour-Morphic-Widgets.package/GLMPopperNotificationStrategy.class/README.md M Glamour-Morphic-Widgets.package/GLMPopperNotificationStrategy.class/instance/as yet unclassified/notify_at_in_.st M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/README.md A Glamour-Morphic-Widgets.package/GLMPrintPopper.class/class/examples/selectionEvaluationPopper.st A Glamour-Morphic-Widgets.package/GLMPrintPopper.class/class/examples/simpleObjectPopper.st M Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/public/evaluateAndOpenFromRubric_.st A Glamour-Morphic-Widgets.package/GLMPrintPopper.class/instance/public/openFromRubric_withResult_.st M Glamour-Presentations.package/GLMPrintSelection.class/README.md R Glamour-Rubric-Presentations.package/GLMNewSmalltalkCodePresentation.class/README.md R Glamour-Rubric-Presentations.package/GLMNewSmalltalkCodePresentation.class/definition.st R Glamour-Rubric-Presentations.package/GLMNewSmalltalkCodePresentation.class/instance/actions/compileTextIn_from_andDo_.st R Glamour-Rubric-Presentations.package/GLMNewSmalltalkCodePresentation.class/instance/actions/debugSelection.st R Glamour-Rubric-Presentations.package/GLMNewSmalltalkCodePresentation.class/instance/actions/evaluateSelection.st R Glamour-Rubric-Presentations.package/GLMNewSmalltalkCodePresentation.class/instance/actions/evaluateSelectionAndDo_.st R Glamour-Rubric-Presentations.package/GLMNewSmalltalkCodePresentation.class/instance/actions/printSelection.st R Glamour-Rubric-Presentations.package/GLMNewSmalltalkCodePresentation.class/instance/actions/profileSelection.st R Glamour-Rubric-Presentations.package/GLMNewSmalltalkCodePresentation.class/instance/rendering/defaultSelectionActions.st R Glamour-Rubric-Presentations.package/GLMNewSmalltalkCodePresentation.class/instance/rendering/installDefaultSelectionActions.st M Glamour-Rubric-Presentations.package/GLMPharoMethodPresentation.class/README.md A Glamour-Rubric-Presentations.package/GLMPharoMethodPresentation.class/class/examples/pharoMethodPresentationExample.st M Glamour-Rubric-Presentations.package/GLMPharoMethodPresentation.class/definition.st M Glamour-Rubric-Presentations.package/GLMPharoPlaygroundPresentation.class/README.md A Glamour-Rubric-Presentations.package/GLMPharoPlaygroundPresentation.class/class/examples/pharoPlaygroundPresentationExample.st M Glamour-Rubric-Presentations.package/GLMPharoPlaygroundPresentation.class/definition.st M Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/README.md A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/actions/compileTextIn_from_andDo_.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/actions/debugSelection.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/actions/evaluateSelection.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/actions/evaluateSelectionAndDo_.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/actions/printSelection.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/actions/profileSelection.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/rendering/defaultSelectionActions.st A Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/rendering/installDefaultSelectionActions.st R Glamour-Rubric-Presentations.package/GLMRubricSmalltalkCodePresentation.class/instance/rendering/renderGlamorouslyOn_.st M Glamour-Rubric-Presentations.package/GLMRubricTextPresentation.class/README.md R Glamour-Rubric-Presentations.package/extension/GLMCompositePresentation/instance/rubricSmalltalkCode.st R Keys.package/Key.class/README.md R Keys.package/Key.class/class/class initialization/initialize.st R Keys.package/Key.class/class/instance creation/value_.st R Keys.package/Key.class/class/key table/initializeKeyTable.st R Keys.package/Key.class/class/macos/initializeMacOSVirtualKeyTable.st R Keys.package/Key.class/class/macos/macOSVirtualKeyTable.st R Keys.package/Key.class/class/macos/valueForMacOSXPlatform_.st R Keys.package/Key.class/class/unix/initializeUnixVirtualKeyTable.st R Keys.package/Key.class/class/unix/unixVirtualKeyTable.st R Keys.package/Key.class/class/unix/valueForUnixPlatform_.st R Keys.package/Key.class/class/unknownKeys/unknownKeyName.st R Keys.package/Key.class/class/windows/initializeWindowsVirtualKeyTable.st R Keys.package/Key.class/class/windows/valueForWindowsPlatform_.st R Keys.package/Key.class/class/windows/windowsVirtualKeyTable.st R Keys.package/Key.class/definition.st R Keys.package/Key.class/instance/accessing/name.st R Keys.package/Key.class/instance/initialize-release/withValue_.st R Keys.package/Key.class/instance/initialize-release/withValue_andName_.st R Keys.package/Key.class/instance/printing/printOn_.st R Keys.package/Key.class/instance/testing/isUnkownKey.st R Keys.package/KeyPrinterMorph.class/README.md R Keys.package/KeyPrinterMorph.class/definition.st R Keys.package/KeyPrinterMorph.class/instance/event handling/handlesKeyboard_.st R Keys.package/KeyPrinterMorph.class/instance/event handling/handlesMouseDown_.st R Keys.package/KeyPrinterMorph.class/instance/event handling/keyDown_.st R Keys.package/KeyPrinterMorph.class/instance/event handling/mouseDown_.st R Keys.package/KeyPrinterMorph.class/instance/initialize/openInWorld.st R Keys.package/extension/KeyboardEvent/instance/key.st R Keys.package/extension/MacOSPlatform/instance/keyForValue_.st R Keys.package/extension/UnixPlatform/instance/keyForValue_.st R Keys.package/extension/Win32Platform/instance/keyForValue_.st M Rubric.package/RubNotificationStrategy.class/README.md M Rubric.package/RubTextInsertionStrategy.class/README.md A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script276.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40276.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40276 14128 "Print it" from Playground menu does not work https://pharo.fogbugz.com/f/cases/14128 14117 merge menuSpec and menuItemSpec https://pharo.fogbugz.com/f/cases/14117 14113 WorldSate stepList not properly cleaned when a morph is deleted https://pharo.fogbugz.com/f/cases/14113 13641 Merge Package Key into package System-Platforms https://pharo.fogbugz.com/f/cases/13641 14099 SmalllintManifestChecker duplicates RBSmalllintChecker>>#run https://pharo.fogbugz.com/f/cases/14099 http://files.pharo.org/image/40/40276.zip

Oct. 1, 2014

[pharo-project/pharo-core]

by GitHub

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

Oct. 1, 2014

Re: [Pharo-dev] GTPlayground Play Button Semantics

by Bernardo Ezequiel Contreras

+1 On Wed, Oct 1, 2014 at 10:14 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Was it a conscious decision to make the GTPlayground Play button act as > 'play all' (evaluate the whole workspace contents) ? > > If so, why ? > > I find it quite limiting that I cannot select some expression and 'play > it'. A workspace/playground is like a notebook containing lots of different > things. > > Sven > > > -- Bernardo E.C. Sent from a cheap desktop computer in South America.

Oct. 1, 2014