- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Growl setting name

by Dimitris Chloupis

Personally I dont see the point of a rename, we got like 30% of people coming from macos that will be familiar with the name Growl, 0% that will be familiar with any other name. So you take a name that is very popular and change it to something none knows, how is that an improvement ? What notification morph, or notification popup even means ? Is it a window ? is it a right click menu popup ? Only the time having to port everything to the new name does not make it worth it. On Sat, Jan 16, 2016 at 10:12 AM stepharo <stepharo(a)free.fr> wrote: > So if you want to change (and some tools should not hardcode access to > GrowlMorph) > a better name would be NotifierPopup > > Le 16/1/16 09:03, stepharo a Ã©crit : > > but notificationPopup is misleading because this is not a Notification > > (Exception). > > > > Stef > > > > Le 15/1/16 23:36, Ferlicot D. Cyril a Ã©crit : > >> Le 15/01/2016 22:51, Mariano Martinez Peck a Ã©crit : > >>> I clearly would use Notification as part of the name, and not Growl. > >>> NotificationPopup? > >>> > >> I love this one! > >> > >>> -- > >>> Mariano > >>> http://marianopeck.wordpress.com > >> > > > > > > > > >

Jan. 16, 2016

Re: [Pharo-dev] How do you normally merge Git branches with Metadata-less GitFileTree?

by Thierry Goubier

Le 16/01/2016 03:23, Mariano Martinez Peck a Ã©crit : > Hi guys, > > First, let me say that I found very cool that I can do a "git checkout > X" from command line, and from Pharo, opening the MC browser detects I > am in another branch and everything seems to work. So I guess that's the > way I manage branches? Simply "git checkout X" and then go to MC , and > do a "load" of the last version of the repo? (or another image, whatever). Yes, exactly. > The problem is now with merging. Not necessary about the metadata ( I > guess we have less metadata conflicts with Metadata-less GitFileTree > right???) , but real code changes conflicts between branches. How do you > manage this? You manage everything at Git level using git and text editors? yes, or with git gui tools, or with the github interface (if there is no conflict). The only thing a bit problematic are the eventual conflicts, but, in that metadata-less format, they are less frequent and easier to solve. > I cannot think how to do that from MC browser "Merge" because MC sees > only one repo associated to one current branch. It is possible to do the merge in MC (think of merging your current working copy and the top of the branch) but they won't be recorded in the git log as a merge. Thierry > Any pointer is appreciated. > > > -- > Mariano > http://marianopeck.wordpress.com

Jan. 16, 2016

Re: [Pharo-dev] Growl setting name

by stepharo

Finally "Growl is a global notification system and pop-up notification implementation for the Mac OS X and Windows[1] operating systems. " So?

Jan. 16, 2016

Re: [Pharo-dev] Growl setting name

by stepharo

So if you want to change (and some tools should not hardcode access to GrowlMorph) a better name would be NotifierPopup Le 16/1/16 09:03, stepharo a Ã©crit : > but notificationPopup is misleading because this is not a Notification > (Exception). > > Stef > > Le 15/1/16 23:36, Ferlicot D. Cyril a Ã©crit : >> Le 15/01/2016 22:51, Mariano Martinez Peck a Ã©crit : >>> I clearly would use Notification as part of the name, and not Growl. >>> NotificationPopup? >>> >> I love this one! >> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >> > > >

Jan. 16, 2016

Re: [Pharo-dev] Growl setting name

by stepharo

but notificationPopup is misleading because this is not a Notification (Exception). Stef Le 15/1/16 23:36, Ferlicot D. Cyril a Ã©crit : > Le 15/01/2016 22:51, Mariano Martinez Peck a Ã©crit : >> I clearly would use Notification as part of the name, and not Growl. >> NotificationPopup? >> > I love this one! > >> -- >> Mariano >> http://marianopeck.wordpress.com >

Jan. 16, 2016

Re: [Pharo-dev] Contributing to Pharo

by Ben Coman

On Sat, Jan 16, 2016 at 9:42 AM, Ben Coman <btc(a)openinworld.com> wrote: > On Sat, Jan 16, 2016 at 6:57 AM, David Allouche <david(a)allouche.net> wrote: >> >> On 15 Jan 2016, at 23:49, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >> >> 2016-01-15 23:33 GMT+01:00 David Allouche <david(a)allouche.net>: >>> >>> >>> So yes, it's broken, but maybe it's something else entirely, I get new >>> reproducible errors every few minutes: errors when activating pretty >>> printing in the diff viewer in Monticello, >> >> >> this is a known error from the "recent" change for rubric text component >> >>> >>> unexpected contextual menu showing up when I do Cmd-T in the debugger, >> >> >> known ( from the recent changes for debugger :) ) >> >>> >>> infinite recursions when trying to debug through the >>> MonticelloRepositoryBrowser... >> >> >> I don't know this error. But I don't think "this" >> MonticelloRepositoryBrowser is actually used. >> >> >> I think that was actually a bug in the debugger, or inspector, not in >> MonticelloRepositoryBrowser. >> >> And yes, this appear to be dead code. I found it before finding the actual >> browser, and thought it might be a good place to start exploring Monticello. >> >> I tried the old debugger in my new latest image (in the hope that syntax >> highlighting would not be broken there), but I realised it advertised no >> keyboard shortcut for stepping through the codeâ¦ >> >> Starting to wonder if I should go back to spending my evenings playing Elite >> Dangerous, and come back in a few weeks when stuff is hopefully less buggy >> everywhere :-( > > Generally I'm impressed at Pharo's stability given depth of the > surgery that is sometimes done on it - but after all it is bleeding > edge and sometimes things get in a bind. Since all the tools are > built and run inside the Image, sometimes its a bit like changing the > tyres on a moving car - but there is the advantage that we are > *always* eating our own dogfood. > > So if occasionally if everything seems against you, after trying a > fresh Image as you already did, slide back to the last build that > worked for you (I don't think the issues you experience are Spur > related, but 50496 might be a good fallback as Pre-Spur and Whoops. That should be 50495. > Pre-GTDebugger). Then create a fresh Image from the latest build to > test your Slice and in that time maybe the other issues have gone. > > cheers -ben

Jan. 16, 2016

How do you normally merge Git branches with Metadata-less GitFileTree?

by Mariano Martinez Peck

Hi guys, First, let me say that I found very cool that I can do a "git checkout X" from command line, and from Pharo, opening the MC browser detects I am in another branch and everything seems to work. So I guess that's the way I manage branches? Simply "git checkout X" and then go to MC , and do a "load" of the last version of the repo? (or another image, whatever). The problem is now with merging. Not necessary about the metadata ( I guess we have less metadata conflicts with Metadata-less GitFileTree right???) , but real code changes conflicts between branches. How do you manage this? You manage everything at Git level using git and text editors? I cannot think how to do that from MC browser "Merge" because MC sees only one repo associated to one current branch. Any pointer is appreciated. -- Mariano http://marianopeck.wordpress.com

Jan. 16, 2016

Re: [Pharo-dev] Contributing to Pharo

by Ben Coman

On Sat, Jan 16, 2016 at 6:57 AM, David Allouche <david(a)allouche.net> wrote: > > On 15 Jan 2016, at 23:49, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > 2016-01-15 23:33 GMT+01:00 David Allouche <david(a)allouche.net>: >> >> >> So yes, it's broken, but maybe it's something else entirely, I get new >> reproducible errors every few minutes: errors when activating pretty >> printing in the diff viewer in Monticello, > > > this is a known error from the "recent" change for rubric text component > >> >> unexpected contextual menu showing up when I do Cmd-T in the debugger, > > > known ( from the recent changes for debugger :) ) > >> >> infinite recursions when trying to debug through the >> MonticelloRepositoryBrowser... > > > I don't know this error. But I don't think "this" > MonticelloRepositoryBrowser is actually used. > > > I think that was actually a bug in the debugger, or inspector, not in > MonticelloRepositoryBrowser. > > And yes, this appear to be dead code. I found it before finding the actual > browser, and thought it might be a good place to start exploring Monticello. > > I tried the old debugger in my new latest image (in the hope that syntax > highlighting would not be broken there), but I realised it advertised no > keyboard shortcut for stepping through the codeâ¦ > > Starting to wonder if I should go back to spending my evenings playing Elite > Dangerous, and come back in a few weeks when stuff is hopefully less buggy > everywhere :-( Generally I'm impressed at Pharo's stability given depth of the surgery that is sometimes done on it - but after all it is bleeding edge and sometimes things get in a bind. Since all the tools are built and run inside the Image, sometimes its a bit like changing the tyres on a moving car - but there is the advantage that we are *always* eating our own dogfood. So if occasionally if everything seems against you, after trying a fresh Image as you already did, slide back to the last build that worked for you (I don't think the issues you experience are Spur related, but 50496 might be a good fallback as Pre-Spur and Pre-GTDebugger). Then create a fresh Image from the latest build to test your Slice and in that time maybe the other issues have gone. cheers -ben

Jan. 16, 2016

Re: [Pharo-dev] Contributing to Pharo

by Ben Coman

On Sat, Jan 16, 2016 at 3:45 AM, David Allouche <david(a)allouche.net> wrote: > Hello, > > I believe the Contributing to Pharo page > http://pharo.org/contribute-propose-fix > is out of date. > > I found a bug > > https://pharo.fogbugz.com/f/cases/17396/MonticelloRepositoryBrowser-example… > > and a made a fix in in a clean image (50525), created by the newly fixed > PharoLauncher. > > Then I followed the instruction on the page. > > > - Create a slice (group of packages): > - Open the Monticello Browser. > - Open the Slice Maker by clicking the "Slice" button. > - In Slice Maker enter the Fogbugz issue number and "grab" the > issue summary. > - Select all dirty packages affected by your bug fix. > > I have no idea how the "list of dirty packages" is generated, but > > 1. it shows a bunch of packages I have not touched > 2. it does not show the package that contains my fix (Spec-Tools) > > I am curious on item 2. Was this just because the dirty package was sorted to the top of the list (per Nicolai's snapshots)? > I looked in the world menu, and I found this menu item called "Komitter". > That sounded like a good candidate. > I see how the term "Commit" is misleading here without context. Probably "Press the <Save> button to commit your slice to the inbox repository" would probably be better. > > Now, I guess I should select Pharo50Inbox as the Remote, write a commit > message, click Ok and hope for the best. > > Is that right? > > I guess contributors are expected to use a recent image. So I think it > would be good that someone updates the documentation. Or fix the slice > maker. Or both. > https://pharo.fogbugz.com/default.asp?17398 cheers -ben

Jan. 16, 2016

Re: [Pharo-dev] Contributing to Pharo

by Henrik Sperre Johansen

Or, try a stable release. Whenever I try developing on the latest version, I end up getting disrupted by bugs in the core tools 70-80% of the time. For released versions, in 1.4 it was maybe 5%, in 2.0 40%, in 3.0 20%, in 4.0 10% So at least it's been trending downwards, though I expect a totally new debugger, image format, RBParser unification and new FFI in 5.0 will keep causing problems for a quite a while. Cheers, Henry On Fri, Jan 15, 2016 at 11:57 PM, David Allouche <david(a)allouche.net> wrote: > > On 15 Jan 2016, at 23:49, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > 2016-01-15 23:33 GMT+01:00 David Allouche <david(a)allouche.net>: > >> >> So yes, it's broken, but maybe it's something else entirely, I get new >> reproducible errors every few minutes: errors when activating pretty >> printing in the diff viewer in Monticello, >> > > this is a known error from the "recent" change for rubric text component > > >> unexpected contextual menu showing up when I do Cmd-T in the debugger, >> > > known ( from the recent changes for debugger :) ) > > >> infinite recursions when trying to debug through the >> MonticelloRepositoryBrowser... >> > > I don't know this error. But I don't think "this" > MonticelloRepositoryBrowser is actually used. > > > I think that was actually a bug in the debugger, or inspector, not in > MonticelloRepositoryBrowser. > > And yes, this appear to be dead code. I found it before finding the actual > browser, and thought it might be a good place to start exploring Monticello. > > I tried the old debugger in my new latest image (in the hope that syntax > highlighting would not be broken there), but I realised it advertised no > keyboard shortcut for stepping through the codeâ¦ > > Starting to wonder if I should go back to spending my evenings playing > Elite Dangerous, and come back in a few weeks when stuff is hopefully less > buggy everywhere :-( >

Jan. 15, 2016