November 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Browse anObject?

by kilon alios

No I like it as it is. Simple and straight to the point. And since browse could apply to a variety of things while browseClass is very specific, similarl to what Ben is saying. I would prefer it for example if I wanted to browse the metaclass of Object to have Object class browse while for the instance side a Object browse would do, That gives browse message a context sensitive/dependant meaning which for me is what OO is all about while your browseClass goes against the same principle. On other hand I have an allergy to camel case anyway :D On Tue, Nov 4, 2014 at 8:20 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > This one smells funny to me... > > Object>>#browse > ^ self systemNavigation browseClass: self class > > A less surprising API might be: > - Object>>#browseClass > - and, Class>>#browse as implemented above > > What do you think? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Browse-anObject-tp4788401.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

Nov. 5, 2014

[pharo-project/pharo-core]

by GitHub

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

Nov. 5, 2014

[pharo-project/pharo-core] a0d5c5: 40353

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: a0d5c58e30bae41dca286a154f00a7f62944e9b6 https://github.com/pharo-project/pharo-core/commit/a0d5c58e30bae41dca286a15… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-11-05 (Wed, 05 Nov 2014) Changed paths: M AST-Core.package/RBProgramNode.class/instance/replacing/calculateSourceInterval_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script353.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40353.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Tests.package/ClassRenameFixTest.class/instance/running/setUp.st M Tests.package/SystemAnnouncerTest.class/instance/tests/testProtocolAdded.st M Tests.package/SystemAnnouncerTest.class/instance/tests/testProtocolRemoved.st M Tests.package/SystemAnnouncerTest.class/instance/tests/testSuspendAllWhile.st M Traits.package/TBehaviorCategorization.class/instance/organization/category.st M Traits.package/Trait.class/class/instance creation/named_uses_category_env_.st Log Message: ----------- 40353 14254 AST method replaceWith: does not change source interval https://pharo.fogbugz.com/f/cases/14254 14380 Replace Announcer>>#on:send:to:s senders in Tests https://pharo.fogbugz.com/f/cases/14380 14371 Traits should not be allowed to have nil as their category https://pharo.fogbugz.com/f/cases/14371 http://files.pharo.org/image/40/40353.zip

Nov. 5, 2014

Re: [Pharo-dev] Fix 'Search Code' menu item in Nautilus

by Marcus Denker

In general we need to discuss about Pharo3 non-bug improvementsâ¦ => we need to take care not to overdue it. If we change Pharo3 a lot, this will add a lot of double work and might introduce new bugs. => My personal rule is: even for bug fixes, if they are to be back ported to Pharo3 not just because âit would be niceâ. My personal threshold for that is simple: I will not do it, but if the fix is important enough *for someone else* to back port, than this is of a kind that should be considered. => We need to be cautious with new featuresâ¦ but then there might be cases where it makes sense. > On 04 Nov 2014, at 17:45, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > Thanks for the tip Max. I've uploaded the packages to the Pharo30Inbox repo. > > > > > > Max Leske wrote >> Hi Paul, >> >> You also need to include the two dependencies of the slice, those need to >> be uploaded to the inbox too. >> >> Cheers, >> Max >> >>> On 04.11.2014, at 06:19, Paul DeBruicker < > >> pdebruic@ > >> > wrote: >>> >>> Hi - >>> >>> The attached slice makes the 'Search Code' menu item in Nautilus work >>> like it did prior to the adoption of Nautilus in Pharo 3. I do not have >>> commit rights to Pharo30Inbox but would submit it there if I did. I >>> have not sent the contributor agreement but will tomorrow. >>> >>> >>> The issue in fogbugz is: >>> https://pharo.fogbugz.com/f/cases/14382/Fix-Search-Code-refactoring-menu-it… >>> >>> >>> Paul >>> >>> >> <SLICE-Issue-14382-Fix-Search-Code-refactoring-menu-item-in-Nautilus-PaulDeBruicker.1.mcz> > > > > > > -- > View this message in context: http://forum.world.st/Fix-Search-Code-menu-item-in-Nautilus-tp4788273p47883… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Nov. 5, 2014

Re: [Pharo-dev] fixing 'format on display' and 'format on accept'

by Marcus Denker

> On 04 Nov 2014, at 20:25, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > > Slice is in the Pharo30Inbox > > https://pharo.fogbugz.com/f/cases/14387/ressurrect-format-on-accept-and-for… > > It uses the settings browser as described below and auto-formats methods (on > display or accept or both) in Nautilus and the senders/implementors browser. > Nice! We should forward port that to Pharo4, too. (I cleaned up the setting a lotâ¦ we should not add new dependencies on CodeHolder, and I already merged all the CodeHolderSystemSettings into the classes they where manipulating (or removed them). For Pharo3 I guess it can be ok to reuse the CodeHolder stuff (there are already many dependencies everywhere to it). Marcus

Nov. 5, 2014

Re: [Pharo-dev] Browse anObject?

by Sean P. DeNigris

Ben Coman wrote > I think this shows its fairly well established that 'Browse' on > its own means "view the object's code" I still vote to change it to more clearly reveal the intention. While perhaps not particularly significant in itself, all these little "gotchas" pile up for newbies, and rob mental energy from everyone's creative expression. Alan Kay ballparked Squeak at "Encyclopedia Brittanica" LOC, down from Windows' "Empire State Building" LOC, but IMHO mastering an entire Encyclopedia is hard enough without a lot of special cases. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Browse-anObject-tp4788401p4788460.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Nov. 5, 2014

Re: [Pharo-dev] Browse anObject?

by Ben Coman

Sean P. DeNigris wrote: > This one smells funny to me... > > Object>>#browse > ^ self systemNavigation browseClass: self class > > A less surprising API might be: > - Object>>#browseClass > - and, Class>>#browse as implemented above > > What do you think? > > > > ----- > Cheers, > Sean In GTInspector, right click on an object and you get the option: * Browse which takes you to view the code. In old inspector, right click on an object you get three options: * Browse Full * Browse Class * Browse Hierarchy which takes you to various different code viewers. Together I think this shows its fairly well established that 'Browse' on its own means "view the object's code". Its established that menu options effectively map to messages sent to the object. So then would you need to change the four menu items above to: * Browse Class * Browse Class Full * Browse Class Class * Browse Class Hierarchy. Then I think you'd need to follow through changing all senders of #fullOnClass: from #browse... to #browseClass... Also, is there any foreseeable situation where a "Browse" menu would provide a function that is not code viewing, that Explore and Inspect would not cover? So in this case, because of the paradigm of mapping from menu items to message sends, unless the menu options change to suit, I think the behaviour expected from #browse is reasonably well defined and the implementation is fine. cheers -ben

Nov. 4, 2014

pane for repositories in the Configuration Browser

by Luc Fabresse

Hi, I added a new slice in the inbox for this: https://pharo.fogbugz.com/default.asp?14392 it adds a pane for repositories in the Configuration Browser (cf. screenshot in the bugtracker) be careful, I made it the default Configuration Browser so you may want to deactivate it by default or not integrate it at all ;-) Cheers, #Luc

Nov. 4, 2014

Re: [Pharo-dev] Browse anObject?

by Nicolas Cellier

I guess that the intention was to use it like this Smalltalk browse. World browse. In case you do not know whether a global is a class or not... 2014-11-04 20:43 GMT+01:00 Tudor Girba <tudor(a)tudorgirba.com>: > I agree. > > Doru > > On Tue, Nov 4, 2014 at 7:20 PM, Sean P. DeNigris <sean(a)clipperadams.com> > wrote: > >> This one smells funny to me... >> >> Object>>#browse >> ^ self systemNavigation browseClass: self class >> >> A less surprising API might be: >> - Object>>#browseClass >> - and, Class>>#browse as implemented above >> >> What do you think? >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: >> http://forum.world.st/Browse-anObject-tp4788401.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Nov. 4, 2014

Re: [Pharo-dev] Browse anObject?

by Tudor Girba

I agree. Doru On Tue, Nov 4, 2014 at 7:20 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > This one smells funny to me... > > Object>>#browse > ^ self systemNavigation browseClass: self class > > A less surprising API might be: > - Object>>#browseClass > - and, Class>>#browse as implemented above > > What do you think? > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Browse-anObject-tp4788401.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 4, 2014