May 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] shortcut change in pharo 50075

by Nicolai Hess

2015-05-31 10:43 GMT+02:00 Mark Rizun <mrizun(a)gmail.com>: > Hi, > > Tested in image: 50077 (hope it's not very critical to test on 50075) > OS: Win 7 > Thank you for your feedback > > This change is not yet visible, although I defined a postload >> you will see the change only after >> TextEditor/SmalltalkEditior initialize >> >> > Ok, I did TextEditor/SmalltalkEditior initialize. > > >> (all alt+ shortcut are removed now, only the >> ctrl+ shortcuts should work) >> >> alt+space / ctrl+space -> select word >> alt+b/ctrl+b browseIt >> alt+c/ctrl+c copy >> alt+x/ctrl+x cut >> alt+v/ctrl+v paste >> alt+f/ctrl+f find >> >> > In playground for me all of the above alt shortcuts work. As well as ctr. > In system browser it's different: > > - alt-space, alt-b, alt-f does not work > - all the others work (c, v, x) > - all of above ctr shortcuts work > Yes, rubrics text components using their own shortcut/action maps.

May 31, 2015

Re: [Pharo-dev] About category

by Sergio Fedi

Does this mean that a class from a Package will be able to have multiple Tags? The first time I saw Packages + Tags I tried to use multiple tags: Example of my initial impression: *Class -> Tags* Car -> Model CarTest -> Model, Tests CarFactory -> Factories CarFactoryTest -> Factories, Tests

May 31, 2015

Re: [Pharo-dev] Probably Metacello sucksâ¦

by Yuriy Tymchuk

> On 31 May 2015, at 13:29, stepharo <stepharo(a)free.fr> wrote: > > >> Hi, >> >> this is an observation on usage of Metacello. I guess that metacello is too complicated to be used. For example I was using the `jenkins` version of Woden configuration, but now itâs broken. > > How? >> And when you look at the Woden repo[1] it says that the way to load it is: >> >> Gofer new smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; package: 'ConfigurationOfNBOpenGL'; load. ((Smalltalk at: #ConfigurationOfNBOpenGL) project version: '3.0') load. Gofer new smalltalkhubUser: 'Pharo' project: 'OSWindow'; package: 'ConfigurationOfOSWindow'; load. (Smalltalk at: #ConfigurationOfOSWindow) loadBleedingEdge. Gofer new smalltalkhubUser: 'ronsaldo' project: 'Woden'; package: 'ConfigurationOfWoden'; load. (Smalltalk at: #ConfigurationOfWoden) loadBleedingEdge >> >> Maybe instead of depending on the configuration of Woden, and saying that to load my project, people should just use a stable version of my configuration, I should copy the script from Woden repo, add some more lines to load the other projects I depend on and ask people to run a half page script in order to use my tools? >> >> What do you think? it looks like an easier solution. > > I do not understand your problem. > I know that jb produced a new configuration for Woden. > And it should work. But it doesnât ;). The script loads everything, while the configuration says: "Error: Name not found: WithOpenGLAndExamplesâ. > Every project should have a configuration. But it should be a responsibility of the owner, not JBâ¦ > > Stef >

May 31, 2015

Re: [Pharo-dev] Probably Metacello sucksâ¦

by stepharo

> Hi, > > this is an observation on usage of Metacello. I guess that metacello > is too complicated to be used. For example I was using the `jenkins` > version of Woden configuration, but now itâs broken. How? > And when you look at the Woden repo[1] it says that the way to load it is: > > Gofer new smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; > package: 'ConfigurationOfNBOpenGL'; load. ((Smalltalk at: > #ConfigurationOfNBOpenGL) project version: '3.0') load. Gofer new > smalltalkhubUser: 'Pharo' project: 'OSWindow'; package: > 'ConfigurationOfOSWindow'; load. (Smalltalk at: > #ConfigurationOfOSWindow) loadBleedingEdge. Gofer new > smalltalkhubUser: 'ronsaldo' project: 'Woden'; package: > 'ConfigurationOfWoden'; load. (Smalltalk at: #ConfigurationOfWoden) > loadBleedingEdge > > Maybe instead of depending on the configuration of Woden, and saying > that to load my project, people should just use a stable version of my > configuration, I should copy the script from Woden repo, add some more > lines to load the other projects I depend on and ask people to run a > half page script in order to use my tools? > > What do you think? it looks like an easier solution. I do not understand your problem. I know that jb produced a new configuration for Woden. And it should work. Every project should have a configuration. Stef

May 31, 2015

Probably Metacello sucksâ¦

by Yuriy Tymchuk

Hi, this is an observation on usage of Metacello. I guess that metacello is too complicated to be used. For example I was using the `jenkins` version of Woden configuration, but now itâs broken. And when you look at the Woden repo[1] it says that the way to load it is: Gofer new smalltalkhubUser: 'PharoExtras' project: 'NBOpenGL'; package: 'ConfigurationOfNBOpenGL'; load. ((Smalltalk at: #ConfigurationOfNBOpenGL) project version: '3.0') load. Gofer new smalltalkhubUser: 'Pharo' project: 'OSWindow'; package: 'ConfigurationOfOSWindow'; load. (Smalltalk at: #ConfigurationOfOSWindow) loadBleedingEdge. Gofer new smalltalkhubUser: 'ronsaldo' project: 'Woden'; package: 'ConfigurationOfWoden'; load. (Smalltalk at: #ConfigurationOfWoden) loadBleedingEdge Maybe instead of depending on the configuration of Woden, and saying that to load my project, people should just use a stable version of my configuration, I should copy the script from Woden repo, add some more lines to load the other projects I depend on and ask people to run a half page script in order to use my tools? What do you think? it looks like an easier solution. Uko [1]: http://smalltalkhub.com/#!/~ronsaldo/Woden

May 31, 2015

Re: [Pharo-dev] Libgit2 and Windows vm build

by Max Leske

Iâm working on that. Itâs really hard to get an evironment set up that actully builds the VM in the first place... > On 31 May 2015, at 00:57, Nicolai Hess <nicolaihess(a)web.de> wrote: > > Latest change for libgit2 makes the Windows vm bulid failing. (See Jenkins job) >

May 31, 2015

Re: [Pharo-dev] DebugAction >> category

by Ben Coman

On Sun, May 31, 2015 at 1:47 PM, stepharo <stepharo(a)free.fr> wrote: > Oki > > You see when you browse the code you wonder if you should pass a class tag > or a method protocol. So I will update the comment. > To me category is a bit too much overloaded. There are 848 methods containing the string 'category', some of which are not related to cleaning packages. So I'm curious what sort of general approaches might be useful to scope this cleaning: * manually identify by looking through code * rename all methods to something like #packageTag, and leave halt in the place of the old #category method, to fail-early for external users of #category. * add MetaLinks to 'category' methods which look back through a couple of stack levels to search for parameters that are strings matching package names. cheers -ben > > Stef > > Le 31/5/15 07:35, Tudor Girba a Ã©crit : > > Hi, > > This is not dead code, only the default Pharo debugger does not make use of > it. > > It is used in the GTDebugger for helping group actions by their category. > The terminology is taken from Glamour (GLMAction>>#category). > > Cheers, > Doru > > On Sun, May 31, 2015 at 7:24 AM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi andrei and others >> >> we have >> >> DebugAction>>category >> >> ^ category ifNil: [ self defaultCategory ] >> >> DebugAction>>defaultCategory >> >> ^ nil >> >> And I tried to browse the senders by scoping the search to the Debugger* >> packages >> and I got no sender. >> >> I have no direct user either. >> So do you know if this is deadcode? >> >> Stef >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" > >

May 31, 2015

Re: [Pharo-dev] shortcut change in pharo 50075

by Mark Rizun

Hi, Tested in image: 50077 (hope it's not very critical to test on 50075) OS: Win 7 This change is not yet visible, although I defined a postload > you will see the change only after > TextEditor/SmalltalkEditior initialize > > Ok, I did TextEditor/SmalltalkEditior initialize. > (all alt+ shortcut are removed now, only the > ctrl+ shortcuts should work) > > alt+space / ctrl+space -> select word > alt+b/ctrl+b browseIt > alt+c/ctrl+c copy > alt+x/ctrl+x cut > alt+v/ctrl+v paste > alt+f/ctrl+f find > > In playground for me all of the above alt shortcuts work. As well as ctr. In system browser it's different: - alt-space, alt-b, alt-f does not work - all the others work (c, v, x) - all of above ctr shortcuts work Some "duplicate" shortcuts weren't removed because the shortcut > defined with the keymap pragma don't work (at least on windows). > > For example: > > ctrl+a/alt+a defined with the action map > and ctrl+a defined by keymap pragam > this wasn't remove, because ctrl+a does not work on windows vm > > ctrl+m/alt+m defined by the action map > ctrl+m defined by keymap pragma > this wasn't remove, because ctrl+m does not work on windows vm > > True, ctr-m does not work on win. Thanks for your work Nicolai. Best, Mark

May 31, 2015

I need reviewer of https://pharo.fogbugz.com/default.asp?15646

by stepharo

Hi I continued to clean that classes have categories and method protocols because it was not finished. This entry is just adding protocol in the classes that were missing it, adding comments, and fixing some local senders It does not remove the category API but puts it in a accessing-backward protocol and in a second step I will fix all the senders I can (ie not Metacello for example). Category is really overloaded and we get lost when trying to understand code. I want to rename RBRule 'category' into 'kind' for this reason. Stef

May 31, 2015

Re: [Pharo-dev] monticello problems

by stepharo

When I merge a slice I get broken information = different from the merge of the slice elements merge. Stef Le 30/5/15 12:07, Esteban Lorenzano a Ã©crit : > Hi, > > Iâm having a lot of problems with monticello lately. > And it is not just the change of MCLazyVersionInfo (that affects just > the history). > > Now, looks like packages are keeping their own private list of > repositories. Look at the example: > > > > > Notice the âAllâ selection. Now see with âPackageâ selected: > > > And it is breaking not just my nerves, but a lot of tools, etc. > > So, I donât know it this was on purpose to avoid repositories > pollutionâ¦ but this is a bug or a bad change :) > > Can you confirm the problem? > > Esteban

May 31, 2015