- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] bbbbf7: 50531

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: bbbbf73528ac0063263b314f8060ed6cfd7ae15d https://github.com/pharo-project/pharo-core/commit/bbbbf73528ac0063263b314f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-18 (Mon, 18 Jan 2016) Changed paths: A Athens-Cairo.package/AthensCairoCanvas.class/instance/as yet unclassified/setAlpha_.st M FuelTools-Debugger.package/FuelOutStackDebugAction.class/class/serialization/serializeTestFailureContext_toFileNamed_.st M Kernel.package/Character.class/instance/converting/asUnicode.st M Kernel.package/Process.class/instance/debugging/debug_title_full_.st M Manifest-Core.package/TheManifestBuilder.class/instance/private/unwrap_.st A Manifest-Core.package/extension/RGPackage/class/manifestReadOn_.st A Manifest-Core.package/extension/RGPackage/instance/arrayStringForManifest.st A Polymorph-Widgets.package/MorphicUIManager.class/instance/debug/debugProcess_context_label_fullView_notification_.st R Polymorph-Widgets.package/MorphicUIManager.class/instance/debug/openDebuggerOn_context_label_fullView_notification_.st A Polymorph-Widgets.package/MorphicUIManager.class/instance/error handling/handleError_log_.st M Polymorph-Widgets.package/MorphicUIManager.class/instance/ui requests/warningDefaultAction_.st A Refactoring-Critics.package/RBDefineBasickCheckRule.class/README.md A Refactoring-Critics.package/RBDefineBasickCheckRule.class/class/accessing/uniqueIdentifierName.st A Refactoring-Critics.package/RBDefineBasickCheckRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBDefineBasickCheckRule.class/definition.st A Refactoring-Critics.package/RBDefineBasickCheckRule.class/instance/accessing/group.st A Refactoring-Critics.package/RBDefineBasickCheckRule.class/instance/accessing/name.st A Refactoring-Critics.package/RBDefineBasickCheckRule.class/instance/accessing/resultClass.st A Refactoring-Critics.package/RBDefineBasickCheckRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBDefineBasickCheckRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/README.md A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/class/accessing/uniqueIdentifierName.st A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/class/testing/checksClass.st A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/definition.st A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/instance/accessing/group.st A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/instance/accessing/name.st A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/instance/accessing/rationale.st A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/instance/accessing/resultClass.st A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/instance/properties/complianceMethods.st A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBDefineEntityComplianceCheckRule.class/instance/running/checkClass_.st A Refactoring-Critics.package/RBLintRule.class/class/testing/checksPackage.st A Refactoring-Critics.package/RBPharoBootstrapRule.class/class/testing/checksPackage.st M Refactoring-Critics.package/RBPharoBootstrapRule.class/definition.st R Refactoring-Critics.package/RBPharoBootstrapRule.class/instance/checking/assertNoNewExternalDependency.st R Refactoring-Critics.package/RBPharoBootstrapRule.class/instance/checking/checkPackage_.st A Refactoring-Critics.package/RBPharoBootstrapRule.class/instance/instance creation/newExternalDependencyExistFor_.st A Refactoring-Critics.package/RBPharoBootstrapRule.class/instance/running/basicCheck_.st A Refactoring-Critics.package/RBPharoBootstrapRule.class/instance/running/checkPackage_.st A Ring-Core-Containers.package/RGPackage.class/instance/accessing/realPackage.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50530.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50531.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50530.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50531.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A UIManager.package/CommandLineUIManager.class/class/testing/isValidForCurrentSystemConfiguration.st A UIManager.package/CommandLineUIManager.class/instance/debug/debugProcess_context_label_fullView_notification_.st R UIManager.package/CommandLineUIManager.class/instance/debug/openDebuggerOn_context_label_fullView_notification_.st A UIManager.package/CommandLineUIManager.class/instance/error handling/handleError_log_.st A UIManager.package/DummyUIManager.class/instance/as yet unclassified/handleError_log_.st A UIManager.package/DummyUIManager.class/instance/debug/debugProcess_context_label_fullView_notification_.st R UIManager.package/DummyUIManager.class/instance/debug/openDebuggerOn_context_label_fullView_notification_.st A UIManager.package/NonInteractiveUIManager.class/class/testing/isValidForCurrentSystemConfiguration.st A UIManager.package/NonInteractiveUIManager.class/instance/debug/debugProcess_context_label_fullView_notification_.st R UIManager.package/NonInteractiveUIManager.class/instance/debug/openDebuggerOn_context_label_fullView_notification_.st A UIManager.package/StartupUIManager.class/class/testing/isValidForCurrentSystemConfiguration.st A UIManager.package/StartupUIManager.class/instance/error handling/handleError_log_.st M UIManager.package/StartupUIManager.class/instance/ui requests/inform_.st A UIManager.package/UIManager.class/class/initialization/forCurrentSystemConfiguration.st A UIManager.package/UIManager.class/class/testing/isValidForCurrentSystemConfiguration.st A UIManager.package/UIManager.class/instance/debug/debugProcess_context_label_fullView_.st A UIManager.package/UIManager.class/instance/debug/debugProcess_context_label_fullView_notification_.st R UIManager.package/UIManager.class/instance/debug/openDebuggerOn_context_label_fullView_.st R UIManager.package/UIManager.class/instance/debug/openDebuggerOn_context_label_fullView_notification_.st A UIManager.package/UIManager.class/instance/error handling/handleError_.st A UIManager.package/UIManager.class/instance/error handling/handleError_log_.st A UIManager.package/UIManager.class/instance/error handling/logError_.st Log Message: ----------- 50531 17393 prepare integration of session manager https://pharo.fogbugz.com/f/cases/17393 17383 Allow banning packages in Manifest https://pharo.fogbugz.com/f/cases/17383 17382 Add rules to check for a new rule design guidelines https://pharo.fogbugz.com/f/cases/17382 17411 AthensCairoCanvas lacks a nbcall to cairo_paint_with_alpha https://pharo.fogbugz.com/f/cases/17411 http://files.pharo.org/image/50/50531.zip

Jan. 18, 2016

[pharo-project/pharo-core]

by GitHub

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

Jan. 18, 2016

[pharo-project/pharo-core] bdb8a7: 50530

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: bdb8a76d3dab61fc9e485b5a684be29f02a91776 https://github.com/pharo-project/pharo-core/commit/bdb8a76d3dab61fc9e485b5a… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-18 (Mon, 18 Jan 2016) Changed paths: M ConfigurationOfGTDebugger.package/ConfigurationOfGTDebugger.class/instance/symbolic versions/stable_.st A ConfigurationOfGTDebugger.package/ConfigurationOfGTDebugger.class/instance/versions/version14_.st M ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version26_.st A ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version27_.st M ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version27_.st A ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version28_.st M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version110_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version19_.st M ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version37_.st A ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version38_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version38_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version39_.st M GT-Debugger.package/extension/Object/instance/gtDebuggerEvaluatorIn_.st R GT-Debugger.package/extension/Object/instance/gtDebuggerPresentationsIn_inContext_.st M GT-Debugger.package/extension/Object/instance/gtDebuggerStateIn_.st A GT-Debugger.package/extension/ProtoObject/instance/gtDebuggerEvaluatorIn_.st A GT-Debugger.package/extension/ProtoObject/instance/gtDebuggerPresentationsIn_inContext_.st A GT-Debugger.package/extension/ProtoObject/instance/gtDebuggerStateIn_.st M GT-Inspector.package/GTRawObjectVariablesBrowser.class/instance/private building/evaluatorIn_.st M GT-Inspector.package/extension/ProtoObject/instance/gtInspectorActions.st A GT-Inspector.package/extension/ProtoObject/instance/gtInspectorPresentationsFromPragmas_In_inContext_.st M GT-Inspector.package/extension/ProtoObject/instance/gtInspectorPresentationsIn_inContext_.st A GT-InspectorExtensions-Core.package/extension/MetacelloVersion/instance/gtInspectorActionLoad.st M GT-Playground.package/GTPlayground.class/instance/building/codeIn_.st M GT-SpotterExtensions-Core.package/extension/GTSpotter/instance/spotterForReferencesFor_.st M Glamour-Morphic-Widgets.package/GLMRubricTextModel.class/README.md M Glamour-Morphic-Widgets.package/GLMRubricTextModel.class/definition.st R Glamour-Morphic-Widgets.package/GLMRubricTextModel.class/instance/accessing/announcer.st R Glamour-Morphic-Widgets.package/GLMRubricTextModel.class/instance/accessing/announcer_.st A Glamour-Morphic-Widgets.package/GLMRubricTextModel.class/instance/accessing/hasUnacceptedEdits.st A Glamour-Morphic-Widgets.package/GLMRubricTextModel.class/instance/accessing/hasUnacceptedEdits_.st A Glamour-Morphic-Widgets.package/GLMRubricTextModel.class/instance/text managing/clearUserEdits.st A Glamour-Rubric-Presentations.package/GLMRubricTextPresentation.class/instance/actions text/clearUserEdits.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50529.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50530.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50529.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50530.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50530 17395 Integrate GTools 3.8 https://pharo.fogbugz.com/f/cases/17395 http://files.pharo.org/image/50/50530.zip

Jan. 18, 2016

[pharo-project/pharo-core]

by GitHub

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

Jan. 18, 2016

Re: [Pharo-dev] [Moose-dev] roassal2 seems to work well now

by Johan Fabry

If Esteban says there are problems, there are problems. (And he did say so.) > On Jan 17, 2016, at 22:43, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Johan? > > Does the image still crash? > > Alexandre > > >> On Jan 17, 2016, at 2:02 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> Hi, >> >> With the latest development, Roassal2 seems to work well. >> >> For example, the rendering of the logical view of Glamour browsers was broken, and now it works well. This is great news. >> >> <Inspector on a GLMSystemWindow(771559424).png> >> >> Is this just my impression? Do we know if there are still open issues with the FFI in this area? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Every thing should have the right to be different." >> >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev > ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Jan. 18, 2016

Re: [Pharo-dev] [Moose-dev] roassal2 seems to work well now

by Alexandre Bergel

Johan? Does the image still crash? Alexandre > On Jan 17, 2016, at 2:02 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > With the latest development, Roassal2 seems to work well. > > For example, the rendering of the logical view of Glamour browsers was broken, and now it works well. This is great news. > > <Inspector on a GLMSystemWindow(771559424).png> > > Is this just my impression? Do we know if there are still open issues with the FFI in this area? > > Cheers, > Doru > > -- > www.tudorgirba.com > www.feenk.com > > "Every thing should have the right to be different." > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 18, 2016

Re: [Pharo-dev] [Pharo-users] [Moose-dev] [ann] gtdebugger in pharo 5.0

by Nicolai Hess

2016-01-17 22:09 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > > On Jan 17, 2016, at 7:56 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > > > [â¦] > > > > - I really miss the "List Methods using 'varname'/List Methods storing > into âvarname' > > > > Please open an issue for this. > > > > This issue is one year old: > > 14583 inspector and instvars : list methods storing into/using > > > > Ok. Thanks. Fixed. > > Thanks Doru, I commented on the bug report. Will this be included in the (left most) inspector pane in the debugger? (this is difficult to use in the "State"-pane, because as soon as you try to bring up the popup-menu, the pane "slides away"). nicolai > -- > www.tudorgirba.com > www.feenk.com > > "To utilize feedback, you first have to acquire it." > > >

Jan. 17, 2016

Re: [Pharo-dev] [Pharo-users] [Moose-dev] [ann] gtdebugger in pharo 5.0

by Tudor Girba

Hi, > On Jan 17, 2016, at 7:56 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > [â¦] > > - I really miss the "List Methods using 'varname'/List Methods storing into âvarname' > > Please open an issue for this. > > This issue is one year old: > 14583 inspector and instvars : list methods storing into/using > Ok. Thanks. Fixed. > [â¦] > > (since when do we put buttons in the title pane? > > Since Glamour makes it easy to have them there :). The GTPlayground and GTInspector have them, too. > > still I don't think this is a good idea. What is the difference between action buttons in the title pane > and the other one. We have now moved the accept and cancel to the contextual menu for now. However, the longer term goal is to change this pattern. Here is a longer explanation. We think of the IDE like terms an object-oriented system built using a language. From this point of view, an action is put in the context that provides enough information to trigger it. So, for actions that do not rely on the selection, or on the cursor position, we can safely put them in the toolbar of the presentation. For global actions (like refreshing the whole inspector), we put them all the way in the title bar. For example: - "Do Itâ depends on the selection or cursor, and thus it is added to the context menu - âAccept" is not specific to the current location of the cursor or of the selection and can be made presentation specific (added to the toolbar of the presentation). - Switching the whole debugger to a âBytecodeâ one is global for the whole debugger, and it is added to the top of the visual hierarchy. This choice also documents the scope of an action. For example, imagine having a global toolbar with actions that only do something in a certain pane (out of possible many). How will you know before triggering what is the effect going to be? But, if you always put the action to the scope that it affects, there is a more clear connection because cause and effect. And there is yet another advantage. When you stick with this design, you get potentially reusable components. This does require some getting used to. And this design will not necessarily work for general UIs. But, an IDE is not a general UI. It is made for programmers, and in our case, it is made for object-oriented programmers, and we can use the abilities of such programmers in our designs. Does this explanation make more sense? Cheers, Doru -- www.tudorgirba.com www.feenk.com "To utilize feedback, you first have to acquire it."

Jan. 17, 2016

Re: [Pharo-dev] [squeak-dev] [Pharo-project] [Vm-dev] Re: Can OSProcess functionality be implemented using FFI instead of plugin?

by Eliot Miranda

On Sun, Jan 17, 2016 at 12:13 PM, stephane ducasse < stephane.ducasse(a)gmail.com> wrote: > > > On 17 Jan 2016, at 18:04, Eliot Miranda <eliot.miranda(a)gmail.com> wrote: > > So this year I hope we will have an excellent high performance FFI. > > > this will be an exciting year. > BTW when ronie will arrive here we will plan some skype session with you. > Yes, if we're to pull this off we have all to be working with a coherent shared plan and to keep in communication. This is exciting. I've been dreaming of this FFI for a while now :-). _,,,^..^,,,_ best, Eliot

Jan. 17, 2016

Re: [Pharo-dev] gtdebugger in pharo 5.0

by David Allouche

> On 17 Jan 2016, at 16:52, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > >> On Jan 17, 2016, at 1:18 PM, David Allouche <david(a)allouche.net> wrote: >> >> Cool. While you are there, could provide a way to separate instance variables from local variables (and class shared variables too, maybe)? >> It could be different columns, filtering, tabs, I do not really care. Currently, when debugging classes with lots of instance variables (like morphic stuff) it's quite painful to find the one local variable of interest. > > > The tags to the left of each variable can be used to filter the list of variables. Nice, but: It's not an obvious, standard UI behaviour In a complex class, you still need to hunt through the list to find the first local variable, that's frustrating. You cannot even use incremental search there. That should probably be a wishlist item on the bug tracker. > >> Also, could the scroll position in the variable be preserved while stepping? > > I am not sure what you refer to. The currently selected variable is preserved both when you step, and it is even preserved when you switch back and forth through the stack. > > What am I missing? The selected variable is preserved, but if ones scroll the variable list using the mouse wheel, the scroll position changes but not the selection. Stepping resets the scroll position to show the selected variable, which is "self" by default. I would like the scroll position for the variable list to be remembered by the debugger in each object. Or maybe the right granularity is concrete class, I am not sure. >> Unfortunately, Pharo does not appear to receive ctrl-tab keydown events, so I need to reach for the mouse to move the focus out of any text areaâ¦ > > Indeed, this does not work. I already reported that before on the mailing list, and I have tracked it down to ctrl-tab keydown not even reaching Sensor. The corresponding keyup are correctly detected. So I guess it might be a vm issue. I should probably file a proper bug report.

Jan. 17, 2016