- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core] 233d1c: 50529

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 233d1c603f211e85b5f990a062f4977faad8a57d https://github.com/pharo-project/pharo-core/commit/233d1c603f211e85b5f990a0… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-16 (Sat, 16 Jan 2016) Changed paths: M Rubric.package/RubScrolledTextMorph.class/instance/model protocol/drawHighlightsOn_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50528.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50529.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50528.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50529.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50529 17201 Marking Diffs broken in Pharo5 https://pharo.fogbugz.com/f/cases/17201 http://files.pharo.org/image/50/50529.zip

Jan. 16, 2016

[pharo-project/pharo-core]

by GitHub

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

Jan. 16, 2016

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

by Mariano Martinez Peck

On Sat, Jan 16, 2016 at 5:15 AM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > 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. OK. > > > 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. > > OK... but let me confirm... with metadata-less gitfiletree, would I still benefit from https://github.com/ThierryGoubier/GitFileTree-MergeDriver to minimize conflicts? Or that was when you were having filetree with metadata? > 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. > > OK. I prefer git to see it as a merge. But thanks anyway. > Thierry > > > Any pointer is appreciated. >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > -- Mariano http://marianopeck.wordpress.com

Jan. 16, 2016

Can't gdb VM crash

by Mariano Martinez Peck

Hi guys, I build a Spur VM for debug, I tried to run an image that is crashing me on startup but all I get from gdb is: [Inferior 1 (process 1358) exited with code 01] (gdb) call printAllStacks() You can't do that without a process to debug. mmm I was always able to see stack traces. No I cannot do anything. Any ideas what could be wrong? I have no clue why it is failing at startup and I need to know it. Thanks in advance, -- Mariano http://marianopeck.wordpress.com

Jan. 16, 2016

Re: [Pharo-dev] Contributing to Pharo

by Stephan Eggermont

On 16-01-16 12:25, David Allouche wrote: > That does not make sense to me. I guess it will, when I understand Monticello better. Ideally, you start with the fresh, latest clean Pharo image to start working on an issue and make the changes in one go to create a slice. Then you only have to select the dirty packages. If the changes you are making risk killing the image, or there are simply a lot of them, you might commit intermediate steps where you detail your thought process/assumptions. The slice for the issue then can consist of packages that are already committed. Stephan

Jan. 16, 2016

Re: [Pharo-dev] Contributing to Pharo

by Ben Coman

On Sat, Jan 16, 2016 at 7:25 PM, David Allouche <david(a)allouche.net> wrote: > >> On 16 Jan 2016, at 12:14, stepharo <stepharo(a)free.fr> wrote: >> >> Le 16/1/16 09:59, David Allouche a Ã©crit : >>> >>> But, really, this "list of dirty packages" should really only list dirty packages. What is the use case for selecting a non-dirty package? >> >> because you never know >> Sometimes you save a package then you do a slice and you should be able to decide. > > That does not make sense to me. I guess it will, when I understand Monticello better. > > Its a very corner case. I've had to do it on occasion but I can't exactly remember the circumstance. Now what might be useful is a checkbox for displaying non-dirty packages - so we only display the short list in the usual case. (??) cheers -ben

Jan. 16, 2016

Re: [Pharo-dev] Growl setting name

by Ferlicot D. Cyril

Le 16/01/2016 09:18, Dimitris Chloupis a Ã©crit : > 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 ? > I don't want to rename Growl, just to change the name of the setting. The setting should not depend of the implementation of the notification system. We can name the setting "Notifier Popup" and behind use a GrowlMorph, a NotifierBloc, a PopupBrickâ¦ The common developer doesn't care. When we want to use a Growl we just call #inform:, not #growl: or "Growl new inform:". As you said 30% of people can understand what Growl is about. Almost everyone can understand that "Notifier Popup" is about a little popup that give us informations. Should we ignore the 70% of people that don't use mac ? And when Pharo will be use by more industry than search lab there will be less than 30% of mac I think. If the community don't want to rename this setting it's your choice, but that will be 70% of newcomers that will be frustrating when they will try to customize the appearance of there Pharo. > 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. > > > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 16, 2016

Re: [Pharo-dev] Growl setting name

by Ferlicot D. Cyril

Le 16/01/2016 09:12, stepharo a Ã©crit : > Finally > > "Growl is a global notification system and pop-up notification > implementation for the Mac OS X and Windows[1] operating systems. " > > So? > Growl can be downloaded on Windows but almost no Windows user know this name and can understand what it means. -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Jan. 16, 2016

Re: [Pharo-dev] Color yzw

by Marcus Denker

> On 16 Jan 2016, at 13:26, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-01-16 10:11 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>>: > >>> anyone an idea? >>> >> I'm trying to think. >> Looks like it would be good to be able to make a distinction between symbols and selectors (selectors installed >> in method dictionaries) >> > > yes, this would improve code completion a bit, too, as there are more symbols than symbols that are actually names > of methods. > > The data could be created per environment (Smalltalk globals) the first time and then cached till shutdown. > (it would be an array of size 46451, pointing to existing symbols). > > The environment could cache sent selectors, tooâ¦ pablo did an experiment with that. > > Marcus > > > How about a new SymbolTable "SelectorTable" that gets new entries on every method compilation ? maybe better when a method is added to a Method Dictionary? This way even adding things the strange way would work... > > I hacked a simple experimental version. > But I don't yet understand the workflow for initialisation of the Symbol class (with rehash, interned, and compacting). > If we hook into adding methods, then compactSymbolTable and rehash could just reset the SelectorTable and fill it after by going over all methodsâ¦ Marcus

Jan. 16, 2016

Re: [Pharo-dev] Color yzw

by Nicolai Hess

2016-01-16 10:11 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > anyone an idea? > > I'm trying to think. > Looks like it would be good to be able to make a distinction between > symbols and selectors (selectors installed > in method dictionaries) > > > yes, this would improve code completion a bit, too, as there are more > symbols than symbols that are actually names > of methods. > > The data could be created per environment (Smalltalk globals) the first > time and then cached till shutdown. > (it would be an array of size 46451, pointing to existing symbols). > > The environment could cache sent selectors, tooâ¦ pablo did an experiment > with that. > > Marcus > > How about a new SymbolTable "SelectorTable" that gets new entries on every method compilation ? I hacked a simple experimental version. But I don't yet understand the workflow for initialisation of the Symbol class (with rehash, interned, and compacting).

Jan. 16, 2016