- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Browse anObject?

by Ben Coman

Sean P. DeNigris wrote: > 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 I thought more on this during the day and came to the conclusion that the least surprising would be... Object>>#browseClass ^ self systemNavigation browseClass: self class Object>>#browse self browseClass but its just a passing thought, and not a big deal. cheers -ben

Nov. 5, 2014

Re: [Pharo-dev] pane for repositories in the Configuration Browser

by Sven Van Caekenberghe

> On 05 Nov 2014, at 11:46, Stephan Eggermont <stephan(a)stack.nl> wrote: > > Hmm. It solves the problem I definitely don't have with the configuration browser. > It is supposed to be helpful and provide simple and working configurations. > That doesn't work as the configurations are not composable > (loading magritte and then loading seaside misses magritte-seaside). That is a totally different problem, unrelated to the subject. It seems legit, but even more a problem of Metacello than of the Configuration Browser. Are groups advertised/available in a config ? How would you even implement what you want ? > As a new user, I don't want to know about multiple locations for repositories. > If I have to, I don't want them to take up half the size of the window, and simultaneously > I don't want them hidden behind a context menu. Why not use a simple drop-down select > for the five repositories? That is a good alternative. > And don't use the full url as a selection name as that doesn't fit. > Just add the full url on hover Yes, good idea. > Can we target the configuration browser please? So no possibility to add your own > metarepo, just a tool that helps people getting started? > > Stephan For me, it solves the limited visibility. The other aspects are worth discussing too. Sven

Nov. 5, 2014

Re: [Pharo-dev] pane for repositories in the Configuration Browser

by kilon alios

I agree with both of you. I think what the Configuration Browser needs is a description pane that first of all gives information about the project and possible sources of documentaion and also has some advanced info for example its main repo, OS supported and Pharo versions supported. Obviously such pane could be made collapsable but on the other hand I find it very hard to believe that a new user wont need at least some basic info about the packages he tried to install. On Wed, Nov 5, 2014 at 12:46 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Hmm. It solves the problem I definitely don't have with the configuration > browser. > It is supposed to be helpful and provide simple and working configurations. > That doesn't work as the configurations are not composable > (loading magritte and then loading seaside misses magritte-seaside). > > As a new user, I don't want to know about multiple locations for > repositories. > If I have to, I don't want them to take up half the size of the window, > and simultaneously > I don't want them hidden behind a context menu. Why not use a simple > drop-down select > for the five repositories? And don't use the full url as a selection name > as that doesn't fit. > Just add the full url on hover > > Can we target the configuration browser please? So no possibility to add > your own > metarepo, just a tool that helps people getting started? > > Stephan >

Nov. 5, 2014

Re: [Pharo-dev] pane for repositories in the Configuration Browser

by Stephan Eggermont

Hmm. It solves the problem I definitely don't have with the configuration browser. It is supposed to be helpful and provide simple and working configurations. That doesn't work as the configurations are not composable (loading magritte and then loading seaside misses magritte-seaside). As a new user, I don't want to know about multiple locations for repositories. If I have to, I don't want them to take up half the size of the window, and simultaneously I don't want them hidden behind a context menu. Why not use a simple drop-down select for the five repositories? And don't use the full url as a selection name as that doesn't fit. Just add the full url on hover Can we target the configuration browser please? So no possibility to add your own metarepo, just a tool that helps people getting started? Stephan

Nov. 5, 2014

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