- Pharo-dev - lists.pharo.org

Re: [Pharo-project] request for the new merge tool :)

by StÃ©phane Ducasse

would be great. Send code :) On Sep 8, 2009, at 4:24 PM, rkrock(a)locksleycreeksoftware.com wrote: >>>> Yes, this is what the History button is supposed to do, display the >>>> diff between two arbitrary versions. >>> >>> What about backport? >>> http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/08209… >> >> That works in the wrong direction for me. I prefer to load changes >> into my working copy instead of having to load the other code and >> "backporting" my changes into their code. >> >> Lukas >> > > What about an option for go forward or backward. It really on which > fork > of the code is considered the 'root' and that is often in the eyes > of the > beholder. > >> -- >> Lukas Renggli >> http://www.lukas-renggli.ch >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 8, 2009

Re: [Pharo-project] request for the new merge tool :)

by StÃ©phane Ducasse

On Sep 8, 2009, at 2:38 PM, Lukas Renggli wrote: >> may be the first step would be to add back the install menu items. > > These are definitely crucial for being able to cherry pick changes > from different versions. yessssss so may be we should add it :) > >> Now for browsing the changes in the squeak trunk we should find a way >> to select >> only change between two versions and even using the history button I >> could not exactly get what >> I wanted. Lukas did you succeed to do this kind of operation? > > Yes, this is what the History button is supposed to do, display the > diff between two arbitrary versions. > > The Changes button displays the diff between the image and the > selected version. > > Lukas > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 8, 2009

Re: [Pharo-project] dnu - isScarySelector not found

by StÃ©phane Ducasse

oops strange then. Did he remove that from his OB version? Stef On Sep 8, 2009, at 2:35 PM, Lukas Renggli wrote: > I am using the code of Colin and there are no senders to > #isScarySelector, so I don't understand why there is a problem? > > Lukas

Sept. 8, 2009

Re: [Pharo-project] request for the new merge tool :)

by rkrock＠locksleycreeksoftware.com

>>> Yes, this is what the History button is supposed to do, display the >>> diff between two arbitrary versions. >> >> What about backport? >> http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/08209… > > That works in the wrong direction for me. I prefer to load changes > into my working copy instead of having to load the other code and > "backporting" my changes into their code. > > Lukas > What about an option for go forward or backward. It really on which fork of the code is considered the 'root' and that is often in the eyes of the beholder. > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 8, 2009

[Pharo-project] Cleanup of Deprecation

by Andrew P. Black

I just committed (with much help from StÃ©phane) my first contribution to Pharo! Cleanup of Deprecation Status: Fixed Owner: ---- Milestone-1.0 Submitted a bunch of small fixes that make the use of deprecation uniform across Pharo. The changes are mostly to the wording of the deprecation message. They also restore the previous behavior of the exception handler so that the notifier says that something has been deprecated. The package is Slice-CleaningDeprecation-AndrewBlack.1

Sept. 8, 2009

Re: [Pharo-project] Lumiere 1.0

by Fernando olivero

Please load Lumiere in a fresh image, this is an Alien related problem. When you try to load Alien twice you get this error, because loading Alien increases the size of the Smalltalk objects array by two. I'm going to fix this now, for the AlienOpenGL loader to not try to load Alien if is already present in the image. Fernando Il giorno Sep 8, 2009, alle ore 3:59 PM, Lawson English ha scritto: > Tried to load Lumier again. This time the error was : Error: THis > version of ALIEN assumes a size of 50 in the array of special objects. > If loaded, woud cause the image to crash! Please contact the Alien > package developer... > > > Fernando olivero wrote: >> Thanks for all the comments. >> >> In John's web page there's a link for accessing the FTP folder where >> he put the plugins and vm he releases. ftp://ftp.smalltalkconsulting.com. >> Sorry for not clarifying this sooner. I'll upload the plugin to the >> home page now, a more direct download. >> >> And yes, i forgot to put the Read acces! Done now. Thanks for the >> advice! >> >> Regarding the license, its free. I put the MIT license now. >> >> Fernando >> >

Sept. 8, 2009

Re: [Pharo-project] Lumiere 1.0

by Lawson English

Tried to load Lumier again. This time the error was : Error: THis version of ALIEN assumes a size of 50 in the array of special objects. If loaded, woud cause the image to crash! Please contact the Alien package developer... Fernando olivero wrote: > Thanks for all the comments. > > In John's web page there's a link for accessing the FTP folder where > he put the plugins and vm he releases. ftp://ftp.smalltalkconsulting.com. > Sorry for not clarifying this sooner. I'll upload the plugin to the > home page now, a more direct download. > > And yes, i forgot to put the Read acces! Done now. Thanks for the advice! > > Regarding the license, its free. I put the MIT license now. > > Fernando >

Sept. 8, 2009

Re: [Pharo-project] Author reset at each image startup issue 1134

by John M McIntosh

Frankly we should consider if the ProjectLauncher stuff should run at all at startup Go look at what it does then consider AutoStart deinstall. and decide if Pharo users/developers need all that to run everytime they start the image. If you do, then why you should manually configure it, a perference perhaps, because likely you are the 1% that has special needs. On 8-Sep-09, at 2:32 PM, Miguel Enrique CobÃ¡ Martinez wrote: > Issue 1134: Repeated Author Initials Inquiry > > Confirmed. > > Tracked down to > > ProjectLauncher>>startUp > World ifNotNil: [World install]. > Author fullName: ''. > ^self startUpAfterLogin. > > That is invoked on image startUp by > > AutoStart>>startUp: resuming > > that itself uses the class var InstalledLaunchers that contains: > > ProjectLauncher. > > So at each image startup the fullName is reset to ''. > > What should we do. What is the purpouse of ProjectLauncher startUp. > > The versions windows of ProjectLauncher>>startUp shows: > > markus.denker 8/18/2008 21:35 ProjectLauncher startUp {running} > > Should the line: > > Author fullName: ''. > > be deleted from ProjectLauncher startUp > > or should ProjectLauncher be deleted from InstalledLaunchers on > AutoStart? > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

Sept. 8, 2009

[Pharo-project] Author reset at each image startup issue 1134

by Miguel Enrique CobÃ¡ Martinez

Issue 1134: Repeated Author Initials Inquiry Confirmed. Tracked down to ProjectLauncher>>startUp World ifNotNil: [World install]. Author fullName: ''. ^self startUpAfterLogin. That is invoked on image startUp by AutoStart>>startUp: resuming that itself uses the class var InstalledLaunchers that contains: ProjectLauncher. So at each image startup the fullName is reset to ''. What should we do. What is the purpouse of ProjectLauncher startUp. The versions windows of ProjectLauncher>>startUp shows: markus.denker 8/18/2008 21:35 ProjectLauncher startUp {running} Should the line: Author fullName: ''. be deleted from ProjectLauncher startUp or should ProjectLauncher be deleted from InstalledLaunchers on AutoStart? -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Sept. 8, 2009

Re: [Pharo-project] request for the new merge tool :)

by Lukas Renggli

>> Yes, this is what the History button is supposed to do, display the >> diff between two arbitrary versions. > > What about backport? > http://lists.squeakfoundation.org/pipermail/squeak-dev/2004-September/08209… That works in the wrong direction for me. I prefer to load changes into my working copy instead of having to load the other code and "backporting" my changes into their code. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Sept. 8, 2009