- Pharo-dev - lists.pharo.org

Atomic commits
by Nicolas Cellier Jan. 12, 2016

Jan. 12, 2016

Hi, I wish the commits were much more atomic than they currently are... With current practice, reviewing the changes is near to impossible: - it requires far too much concentration - it's just impossible through github web interface For example, I did wander if the structure fields were correclty aligned in: https://github.com/pharo-project/pharo-core/blame/5986a695fb28834247a90dbf8… because I see no code for aligning the offsets... But I cannot even navigate in the history... If I do so, https://github.com/pharo-project/pharo-core/commit/dfd4f3ae0f0b0af7766c1405… the page tells me "Sorry, we could not display the entire diff because too many files (2,121) changed" and I couldn't find a way of displaying the portion of interest. I thus loose the ability to deposit a comment. I can still open a fresh Pharo image and browse and review the whole code snapshot there. Or I can navigate more easily in history with git tools. But if I wanted a lightweight review thru web, focusing on the diffs and navigating a bit in history without replicating the repository, I can't. While ranting, it's nice to have the commits performed by a jenkins server, but how do we track the authors of original modifications? In a normal git based development, there would be feature branches integrated/merged in trunk/master by whatever process. But in current process i fail to capture such information... This gives a taste of under-powered use of the tools, and I wander if being visible in these conditions is a good thing: we don't expose the best practices.

6 6

Understanding Spotter?
by stepharo Jan. 12, 2016

Jan. 12, 2016

Hi Is there a help a student or idiot like me can read about how to find information with Spotter? For example We with luc wanted to find all the senders of variableSubclass: we tried # #senders and more... but gave up. Yesterday I wanted to find all the user of <menu> May be I missed an obvious help that will enlighten me? I hope. Now without such help how can we expect students or users to discover the way we should use the tools? We were planning to do a video to explain Spotter but I'm slowly thinking to discard this video because we do not know. Stef

11 33

[pharo-project/pharo-core] 636bf8: 50521
by GitHub Jan. 11, 2016

Jan. 11, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 636bf89014ff48637130095f2d7835a0e7bc9079 https://github.com/pharo-project/pharo-core/commit/636bf89014ff48637130095f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-10 (Sun, 10 Jan 2016) Changed paths: A Morphic-Base.package/MenuItemMorph.class/instance/counting/countingMenu.st A Morphic-Base.package/MenuItemMorph.class/instance/events/insistMenu.st M Morphic-Base.package/MenuItemMorph.class/instance/events/invokeWithEvent_.st A Morphic-Base.package/MenuItemMorph.class/instance/meta actions/deselectItem.st R Morphic-Base.package/MenuItemMorph.class/instance/nil/deselectItem.st R Morphic-Base.package/MenuItemMorph.class/instance/nil/isEnabled_.st A Morphic-Base.package/MenuItemMorph.class/instance/testing/isEnabled_.st A Morphic-Base.package/ShortcutReminderMorph.class/README.md A Morphic-Base.package/ShortcutReminderMorph.class/class/counting/countingMenu.st A Morphic-Base.package/ShortcutReminderMorph.class/class/initialize/initialize.st A Morphic-Base.package/ShortcutReminderMorph.class/class/instance creation/with_.st A Morphic-Base.package/ShortcutReminderMorph.class/class/settings/enableShortcutReminder.st A Morphic-Base.package/ShortcutReminderMorph.class/class/settings/enableShortcutReminder_.st A Morphic-Base.package/ShortcutReminderMorph.class/class/settings/settingsOn_.st A Morphic-Base.package/ShortcutReminderMorph.class/class/settings/timesShortcutReminder.st A Morphic-Base.package/ShortcutReminderMorph.class/class/settings/timesShortcutReminder_.st A Morphic-Base.package/ShortcutReminderMorph.class/class/startup list/startUp_.st A Morphic-Base.package/ShortcutReminderMorph.class/definition.st A Morphic-Base.package/ShortcutReminderMorph.class/instance/accessing/alpha.st A Morphic-Base.package/ShortcutReminderMorph.class/instance/accessing/text_.st A Morphic-Base.package/ShortcutReminderMorph.class/instance/counting/countingMenu.st A Morphic-Base.package/ShortcutReminderMorph.class/instance/initialize/initialize.st A Morphic-Base.package/ShortcutReminderMorph.class/instance/stepping/alpha_.st A Morphic-Base.package/ShortcutReminderMorph.class/instance/stepping/resetAlpha.st A Morphic-Base.package/ShortcutReminderMorph.class/instance/stepping/step.st A Morphic-Base.package/ShortcutReminderMorph.class/instance/stepping/stepTime.st A Morphic-Base.package/ShortcutReminderMorph.class/instance/stepping/wantsSteps.st M Morphic-Base.package/ToggleMenuItemMorph.class/instance/drawing-private/drawKeyTextOn_.st A Morphic-Base.package/ToggleMenuItemMorph.class/instance/drawing-private/itemShortcut.st M Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/instance/drawing/drawOn_.st A Morphic-Base.package/ToggleMenuItemShortcutWithSymbol.class/instance/drawing/text.st A Morphic-Base.package/ToggleMenuItemShortcutWithText.class/instance/accessing/text.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50520.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50521.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50520.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50521.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50521 17348 Enhance shortcut learnability https://pharo.fogbugz.com/f/cases/17348 http://files.pharo.org/image/50/50521.zip

4 3

Pharo-spur VM builds are back to green
by Esteban Lorenzano Jan. 11, 2016

Jan. 11, 2016

Hi, I restored the pharo spur vm builds. Which means latest vm (from zeroconf of directly downloaded from files.pharo.org <http://files.pharo.org/>) is aligned with latest sources. I know there were a couple of bugs waiting to be testedâ¦ so please, go ahead! Esteban

3 2

[pharo-project/pharo-core] 55d093: 50522
by GitHub Jan. 11, 2016

Jan. 11, 2016

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 55d0938007108f79493d692ffaa0cf2225884655 https://github.com/pharo-project/pharo-core/commit/55d0938007108f79493d692f… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-11 (Mon, 11 Jan 2016) Changed paths: M BaselineOfQualityAssistant.package/BaselineOfQualityAssistant.class/instance/api projectSpec/baseline_.st M ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/symbolic versions/stable_.st A ConfigurationOfQualityAssistant.package/ConfigurationOfQualityAssistant.class/instance/versions/v2%5F2%5F1_.st M ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/symbolic versions/stable_.st A ConfigurationOfRenraku.package/ConfigurationOfRenraku.class/instance/versions/v0%5F9%5F2_.st M Nautilus.package/extension/Class/instance/definitionForNautilus.st R QualityAssistantRecording.package/QAEventCollector.class/class/accessing/uniqueInstance.st R QualityAssistantRecording.package/QAEventCollector.class/class/class initialization/initialize.st R QualityAssistantRecording.package/QAEventCollector.class/class/initialize-release/unload.st A QualityAssistantRecording.package/QAEventCollector.class/instance/configuration/defaultCategory.st R QualityAssistantRecording.package/QAEventCollector.class/instance/initialization/initialize.st A QualityAssistantRecording.package/QAEventCollector.class/instance/initialization/linkToReSystemAnnouncer_.st A Renraku.package/ReSystemAnnouncer.class/class/cleanup/cleanUp.st M Renraku.package/ReSystemAnnouncer.class/class/instance creation/uniqueInstance.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50521.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50522.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50521.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50522.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A Traits.package/TClassDescription.class/instance/slots/usesSpecialClassVariables.st M Traits.package/TClassDescription.class/instance/slots/usesSpecialSlot.st M Traits.package/TClassDescription.class/instance/slots/usesSpecialVariables.st Log Message: ----------- 50522 17356 QualityAssistant v2.2.1 https://pharo.fogbugz.com/f/cases/17356 17300 Class slots are not persisted in Monticello https://pharo.fogbugz.com/f/cases/17300 http://files.pharo.org/image/50/50522.zip

1 0

[pharo-project/pharo-core]
by GitHub Jan. 11, 2016

Jan. 11, 2016

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

1 0

[ANN] Pharo Consortium New Gold Member: Synectique
by Marcus Denker Jan. 11, 2016

Jan. 11, 2016

The Pharo Consortium is very happy to announce that Synectique has joined the Consortium as an Gold Member. About - Synectique: http://www.synectique.eu/ <http://www.synectique.eu/> - Pharo Consortium: http://consortium.pharo.org <http://consortium.pharo.org/> The goal of the Pharo Consortium is to allow companies and institutions to support the ongoing development and future of Pharo. Individuals can support Pharo via the Pharo Association: http://association.pharo.org <http://association.pharo.org/>

4 3

gtdebugger - icons with text and a couple of others
by Tudor Girba Jan. 11, 2016

Jan. 11, 2016

Hi, Andrei and I took your feedback into account, and now we have this in the last version: - actions have text (this is a feature introduced in Glamour now) - the order of the code actions is better (accept is next to cancel) On top of that, there are a couple of extra features that we did not talk about until now: - whenever there is another kind of debugger available, a new button appears on the top right. When the Bytecode Debugger is loaded, you can always switch to it. Or, when you get in a situation in which the SUnit is available, you can switch to it. - the selection from the inspector is preserved when you move back and forth in the stack. - the panes in the inspector can be closed - stack highlighting is not on by default (it never was actually) - if you âInspect and Goâ, you inspect in place instead of the inspector at the bottom (no extra window) There are probably still glitches, but we think they are fixable. We still would like to add a couple of more features if there is time: - having a table in the stack to show class / method / package - having multiple inspectors in tabs when you inspect in place to not remove the original inspector Please let us know what you think. Cheers, Doru -- www.tudorgirba.com www.feenk.com "Every thing has its own flow."

2 1

Re: [Pharo-dev] [Moose-dev] Re: gtdebugger in pharo 5.0
by Sven Van Caekenberghe Jan. 10, 2016

Jan. 10, 2016

> On 10 Jan 2016, at 21:14, Ferlicot D. Cyril <cyril.ferlicot(a)gmail.com> wrote: > > Le 08/01/2016 12:07, Tudor Girba a Ã©crit : >> Hi, >> >> We are about to integrate in Pharo a new member of the Glamorous >> Toolkit: the GTDebugger. As this is a significant change that might >> affect your workflow, here is some background information to help you >> deal with the change. >> >> First, you should know that the change is not irreversible and it is >> easily possible to disabled the new debugger through a setting. However, >> please do take the time to provide us feedback if something does >> not work out for you. We want to know what can be improved and we try to >> react as fast as we can. >> >> A practical change comes from the fact that the variables are >> manipulated through a GTInspector, which makes it cheaper to maintain in >> the longer run. >> >> While the first thing that will capture the attention is the default >> generic interface, the real power comes from the moldable nature of the >> debugger. Like all other GT tools, GTDebugger is also moldable by >> design. This means that we can construct custom debuggers for specific >> libraries at small costs (often measured in a couple of hundred lines of >> code). >> >> For example, the core configuration includes also the SUnit and the >> bytecode debugger. These are around 150 lines of code. Here is how the >> bytecode debugger looks like: >> >> >> >> You can find more information in an introductory overview blog post that >> also includes some links for further reading: >> http://www.humane-assessment.com/blog/gtdebugger-in-pharo/ >> >> Please let us know what you think. >> >> Cheers, >> Doru >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com> >> www.feenk.com >> >> "What is more important: To be happy, or to make happy?" >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev >> > > Hi, > > An other thing that came in my mind is that, for now, GTDebugger lack > documentation. > Some classes have no documentation and the class with a comment only > have 1 line and don't follow the template. > > It's good that people takes time to add documentation but if the new > classes that Pharo include does not have a proper documentation (class > doc + comments in complex methods) we will never be able to have a > version of Pharo with a good documentation. > > I think that we should not integrate new classes if they don't have a > class comment that follow the template. +100 I can understand that when prototype, hacking, being generally productive inside Pharo, you don't write comments at first. But once you go public, after some iterations, and especially if you want to be integrated into Pharo itself, there is no excuse. We need proper class comments, and comments for the main non-trivial public methods. Sven > -- > Cyril Ferlicot > > http://www.synectique.eu > > 165 Avenue Bretagne > Lille 59000 France > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

3 3

[pharo-project/pharo-core]
by GitHub Jan. 10, 2016

Jan. 10, 2016

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

1 0