January 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Can we remove Arc, Circle and Spline ?

by StÃ©phane Ducasse

Hi mariano I think that for now they are easy to fix in case of problem. I suggest that we concentrate efforts on some ugly one like project and deepInner.... FileDirectory.... Stef On Jan 19, 2010, at 11:20 AM, Mariano Martinez Peck wrote: > Maybe I even would like to remove the whole package 'ST80-Paths'.....but, going step by step, I would remove Arc, Circle and Spline. As far as I could see, they don't have more senders than their own examples. And they are not even working. For example, Arc and Circule shows the same. Evaluate: > > Arc example > Circle example > Spline example > > So, what do you think? We break everything if we do this? opinions? > > Maybe we can put them in PharoMorphicExtras :) > > Cheers > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 19, 2010

Re: [Pharo-project] [update 1.1] #11164

by StÃ©phane Ducasse

IsolationLayer is a left over of project saving one cs per world and been able to revoke it on project leave. apparently somebody reintroduces some old code. Stef On Jan 19, 2010, at 3:49 PM, Henrik Johansen wrote: > The hardcoded debugger change causes the "Debug it" command to fail. > > What is the extra isolationHead: parameter for anyways? > > Cheers, > Henry > > On Jan 16, 2010, at 9:26 55PM, Marcus Denker wrote: > >> 11164 >> ----- >> >> Issue 441: Hardcoded debugger >> Issue 1828: testAnnotationPane >> Issue 1819: 1.1: some packages have no repository >> >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> _______________________________________________ >> 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

Jan. 19, 2010

Re: [Pharo-project] Polymorph final

by Gary Chambers

P.S. I am on the pharo IRC for the next few hours for more immediate responses. Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 19, 2010 5:31 PM Subject: Re: [Pharo-project] Polymorph final > Ok I will do an integration pass later today :) > > Stef > > On Jan 19, 2010, at 6:01 PM, Gary Chambers wrote: > >> Nearly the last version on SqueakSource. Polymorph-Widgets-gvc.101.mcz. >> I seem to have lost some fixes for multiFormFillStyle (oddity with >> pressed control buttons...). >> >> Let me know if there are any merge problems. >> >> Adds OverflowRowMorph to browser switches/button-bar. >> >> Regards, Gary >> _______________________________________________ >> 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

Jan. 19, 2010

Re: [Pharo-project] worldMenu

by StÃ©phane Ducasse

would be lovely What I would love to have and I failed trying is to have a trait based morphic. Stef On Jan 19, 2010, at 12:30 PM, Fernando olivero wrote: > what about a PasteUp behavior as a Trait? > > That could be attached to any morph that wants PasteUp behavior. > > Fernando > > On Jan 19, 2010, at 1:57 AM, Francisco Ortiz PeÃ±aloza wrote: > >> I totally agree! Another thought is that there isn't currently other >> use cases for a PasteUpMorph besides World. >> >> I would love to have a simple solution or a solution at all rather >> than my just my opinion. >> >> Best Regards, >> Francisco >> >> On Mon, Jan 18, 2010 at 6:57 PM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> >>> On Jan 18, 2010, at 4:34 PM, Francisco Ortiz PeÃ±aloza wrote: >>> >>>> i know but not every PasteUpMorph has to be the World... >>>> >>>> from PasteUpMorph comments >>>> "A morph whose submorphs comprise a paste-up of rectangular subparts >>>> which "show through". Anything called a 'Playfield' is a >>>> PasteUpMorph." >>>> >>>> i'm just saying that anything related to the world concept >>>> semantically doesnt belong to what i understand for PasteUpMorph. >>> >>> >>> I do not understand PasteUpMorph (no pun intended). >>> Seems to me that it was playing too many roles (I happy that we removed a couple of tenth of methods from it). >>> >>> Stef >>>>>>> >>> >>> _______________________________________________ >>> 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 19, 2010

Re: [Pharo-project] Polymorph final

by Gary Chambers

Might be worth merging the TaskbarIcons too. Ignore any warnings (UniverseBrowser etc.). Should just load the valid bits. Just a nicety, taskbar icons/window icons (for supporting themes) etc. Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Tuesday, January 19, 2010 5:31 PM Subject: Re: [Pharo-project] Polymorph final > Ok I will do an integration pass later today :) > > Stef > > On Jan 19, 2010, at 6:01 PM, Gary Chambers wrote: > >> Nearly the last version on SqueakSource. Polymorph-Widgets-gvc.101.mcz. >> I seem to have lost some fixes for multiFormFillStyle (oddity with >> pressed control buttons...). >> >> Let me know if there are any merge problems. >> >> Adds OverflowRowMorph to browser switches/button-bar. >> >> Regards, Gary >> _______________________________________________ >> 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

Jan. 19, 2010

Re: [Pharo-project] We remove CodeLoader ?? [WAS] Presenter and Project will die aren't they ?

by StÃ©phane Ducasse

the loading script on the command line should be cleaned and this is really important. On Jan 19, 2010, at 6:12 PM, Michael Roberts wrote: > we can remove it but we need to keep the ability to load scripts from > the command line. > > so, your code is fine but you can't zap CodeLoader since it's still > referenced for the load. It would be easier just to make a new class > that only loads scripts from the command line, and zap the rest. > > cheers > Mike > > 2010/1/19 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> So....we will remove CodeLoader then ? This is the moment to speak :) >> >> I ask about this because I am trying to analize who uses ImageSegments and >> all that stuff in the code and see how easily or good is to remove >> ImageSegment to a separate package. And, CodeLoader uses ImageSegment. >> >> As far as I looked, the only user or CodeLoader, as Michael said is >> ProjectLauncher >> startUpAfterLogin >> Which....I think it will also die in a moment if Project will die too.... >> >> Anyway, but do you think about changing startUpAfterLogin to this: >> >> startUpAfterLogin >> | scriptName loader isUrl | >> self readDocumentAtStartup ifTrue: [ >> scriptName := (SmalltalkImage current getSystemAttribute: 2) >> ifNil:['']. >> scriptName := scriptName convertFromSystemString. >> scriptName isEmpty ifFalse:[ >> "figure out if script name is a URL by itself" >> isUrl := (scriptName asLowercase beginsWith:'http://') or:[ >> (scriptName asLowercase beginsWith:'file://') or:[ >> (scriptName asLowercase beginsWith:'ftp://')]]. >> isUrl ifFalse:[scriptName := 'file:',scriptName]]. >> . ] >> ifFalse: [ scriptName := '' ]. >> >> scriptName isEmptyOrNil >> ifTrue:[^ self]. >> loader := CodeLoader new. >> loader loadSourceFiles: (Array with: scriptName). >> loader installSourceFiles. >> >> >> >> On Tue, Jan 12, 2010 at 9:56 AM, StÃ©phane Ducasse >> <stephane.ducasse(a)inria.fr> wrote: >>> >>> ok we got convinced :) >>> >>> On Jan 12, 2010, at 8:20 AM, John M McIntosh wrote: >>> >>>> Ah well yes Michael suffered thru managing, testing, and working with >>>> all those browsers & plugins. >>>> I suffered thru trying to figure out how it all worked... At least on >>>> the mac. >>>> >>>> Here's the current issue, because: >>>> >>>> Microsoft shafted netscape by abandoning the netscape API, then shafted >>>> apple by not providing an alternative >>>> we had the strange mixture of a solution for os-x, windows, X11. Then >>>> of course Microsoft IE on macintosh >>>> would change behaviour from version to version to screw with FireFox & >>>> Mozilla etc. Let alone worrying about Opera which >>>> kinda worked. Fortunately Microsoft abandon the Mac browser market, >>>> and Apple introduced Safari which again was slightly different. >>>> >>>> Now on 10.6 we had this problem an abandon API for plugins, that needed >>>> to move forward, also into the 64bit world. >>>> So Apple changed things again to either let you run Safari in 32bit >>>> using old plugins (busted), or using a modified 64bit plugins api, but >>>> not both at the same time. >>>> >>>> The words busted, non-existant, abandon, (implied ugly), appear quite a >>>> few times in the sentences above. Also on every >>>> browser version change, or operating system major version change >>>> something was just slightly funky enough to bring down >>>> the house of cards. >>>> >>>> So, time is better spent in getting 64bit squeak working, since there is >>>> plenty of hours still needed to fixup all the plugins, >>>> and check that the VM is actually sane... >>>> >>>> >>>> On 2010-01-11, at 1:59 PM, Michael Rueger wrote: >>>> >>>>> On 1/11/2010 10:58 PM, Michael Rueger wrote: >>>>> >>>>>> forget squeak/pharo in the browser. >>>>> >>>>> for those not in the know: >>>>> I'm one of the poor guys who actually spent a *lot* of time making it >>>>> possible ;-) >>>>> >>>>> Michael >>>>> >>>>> _______________________________________________ >>>>> 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 >>>> >>>> =========================================================================== >>>> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> 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 >> >> >> _______________________________________________ >> 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

Jan. 19, 2010

Re: [Pharo-project] AddMethodRefactoring>>preconditions

by Lukas Renggli

Hi Fernando, > Lukas, i stumbled upon a strange behavior using the refactoring engine. > > When adding a method, the precondition checks if the class or any super class defines the method to be added. > > It must only ask if the class directly defines it. > > AddMethodRefactoring>>preconditions > Â Â Â Â | selector method | > Â Â Â Â method := RBParser parseMethod: source > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â onError: > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â [:string :position | > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â ^RBCondition > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â withBlock: [self refactoringError: 'The sources could not be parsed']]. > Â Â Â Â selector := method selector. > Â Â Â Â selector isNil ifTrue: [self refactoringError: 'Invalid source.']. > Â Â Â Â ^(RBCondition definesSelector: aSelector in: aClass : selector in: class) I don't think this is a correct change, because with this modification the AddMethodRefactoring is not a refactoring anymore. You can only add a method to a class without changing the behavior if that selector is not defined in the hierarchy. Furthermore your change breaks the unit tests, namely RBAddMethodTest. I don't know why you think this is a bug? If you use the refactoring engine to generate code then you shouldn't use the AddMethodRefactoring, but the AddMethodChange. For example to add some arbitrary methods to an arbitrary class you could use (and this is obviously not a refactoring, but some random change): | model | model := RBNamespace new. (model classNamed: #Morph) compile: 'asMorph ^ nil' classified: #(accessing). model changes open In the above example the call to #compile:classified: creates the AddMethodChange object that you then see when you open the changes log. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Jan. 19, 2010

Re: [Pharo-project] Polymorph final

by StÃ©phane Ducasse

Ok I will do an integration pass later today :) Stef On Jan 19, 2010, at 6:01 PM, Gary Chambers wrote: > Nearly the last version on SqueakSource. Polymorph-Widgets-gvc.101.mcz. > I seem to have lost some fixes for multiFormFillStyle (oddity with pressed control buttons...). > > Let me know if there are any merge problems. > > Adds OverflowRowMorph to browser switches/button-bar. > > Regards, Gary > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 19, 2010

Re: [Pharo-project] We remove CodeLoader ?? [WAS] Presenter and Project will die aren't they ?

by Michael Roberts

we can remove it but we need to keep the ability to load scripts from the command line. so, your code is fine but you can't zap CodeLoader since it's still referenced for the load. It would be easier just to make a new class that only loads scripts from the command line, and zap the rest. cheers Mike 2010/1/19 Mariano Martinez Peck <marianopeck(a)gmail.com>: > So....we will remove CodeLoader then ?Â Â This is the moment to speak :) > > I ask about this because I am trying to analize who uses ImageSegments and > all that stuff in the code and see how easily or good is to remove > ImageSegment to a separate package. And, CodeLoader uses ImageSegment. > > As far as I looked, the only user or CodeLoader, as Michael said is > ProjectLauncher >> startUpAfterLogin > Which....I think it will also die in a moment if Project will die too.... > > Anyway, but do you think about changing startUpAfterLoginÂ to this: > > startUpAfterLogin > Â Â Â | scriptName loader isUrl | > Â Â Â self readDocumentAtStartup ifTrue: [ > Â Â Â Â Â Â scriptName := (SmalltalkImage current getSystemAttribute: 2) > ifNil:['']. > Â Â Â Â Â Â scriptName := scriptName convertFromSystemString. > Â Â Â Â Â Â scriptName isEmpty ifFalse:[ > Â Â Â Â Â Â Â Â Â "figure out if script name is a URL by itself" > Â Â Â Â Â Â Â Â Â isUrl := (scriptName asLowercase beginsWith:'http://') or:[ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â (scriptName asLowercase beginsWith:'file://') or:[ > Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â (scriptName asLowercase beginsWith:'ftp://')]]. > Â Â Â Â Â Â Â Â Â isUrl ifFalse:[scriptName := 'file:',scriptName]]. > Â Â Â Â Â Â . ] > Â Â Â ifFalse: [ scriptName := '' ]. > > Â Â Â scriptName isEmptyOrNil > Â Â Â Â Â Â ifTrue:[^ self]. > Â Â Â loader := CodeLoader new. > Â Â Â loader loadSourceFiles: (Array with: scriptName). > Â Â Â loader installSourceFiles. > > > > On Tue, Jan 12, 2010 at 9:56 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> ok we got convinced :) >> >> On Jan 12, 2010, at 8:20 AM, John M McIntosh wrote: >> >> > Ah well yes Michael suffered thru managing, testing, and working with >> > all those browsers Â & plugins. >> > I suffered thru trying to figure out how it all worked... Â At least on >> > the mac. >> > >> > Here's the current issue, because: >> > >> > Microsoft shafted netscape by abandoning the netscape API, then shafted >> > apple by not providing an alternative >> > we had the strange mixture of Â a solution for os-x, windows, X11. Then >> > of course Microsoft IE on macintosh >> > would change behaviour from version to version to screw with FireFox & >> > Mozilla etc. Â Let alone worrying about Opera which >> > kinda worked. Â Fortunately Microsoft abandon the Mac browser market, >> > Â and Apple introduced Safari which again was slightly different. >> > >> > Now on 10.6 we had this problem an abandon API for plugins, that needed >> > to move forward, also into the 64bit world. >> > So Apple changed things again to either let you run Safari in 32bit >> > using old plugins (busted), or using a modified 64bit plugins api, but >> > not both at the same time. >> > >> > The words busted, non-existant, abandon, (implied ugly), Â appear quite a >> > few times in the sentences above. Also on every >> > browser version change, or operating system major version change >> > something was just slightly funky Â enough to bring down >> > the house of cards. >> > >> > So, time is better spent in getting 64bit squeak working, since there is >> > plenty of hours still needed to fixup all the plugins, >> > and check that the VM is actually sane... >> > >> > >> > On 2010-01-11, at 1:59 PM, Michael Rueger wrote: >> > >> >> On 1/11/2010 10:58 PM, Michael Rueger wrote: >> >> >> >>> forget squeak/pharo in the browser. >> >> >> >> for those not in the know: >> >> I'm one of the poor guys who actually spent a *lot* of time making it >> >> possible ;-) >> >> >> >> Michael >> >> >> >> _______________________________________________ >> >> 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 >> > >> > =========================================================================== >> > >> > >> > >> > >> > >> > _______________________________________________ >> > 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 19, 2010

Re: [Pharo-project] After OB, compare to current version uses old diff

by Gary Chambers

Unless code has changed then the setting for "Use Polymorph difference tools" should do. I expect some code regression may have happened though. Regards, Gary ----- Original Message ----- From: Mariano Martinez Peck To: Pharo-project(a)lists.gforge.inria.fr Sent: Tuesday, January 19, 2010 4:35 PM Subject: Re: [Pharo-project] After OB,compare to current version uses old diff On Tue, Jan 19, 2010 at 5:22 PM, Henrik Johansen <henrik.s.johansen(a)veloxit.no> wrote: Preferences >> useNewDiffToolsForMC? I tried this before sending the email, but not. I didn't work :( There was some discussion some time back, I believe Lukas stated he liked the old tools better. Ok..didn't know. Can't say I blame him, I'm never quite sure if I'm installing new one or keeping old when merging from MC until after the fact when I use the Polymorph tools ... I can blame him at all. He is helping us a lot maintaining OB a lot. If we use his OB repository, then we should adapt to him. I don't pretend he change his default values or preferences. I just want to know how to set up again the new diff :) Cheers Mariano Cheers, Henry On Jan 19, 2010, at 5:05 26PM, Mariano Martinez Peck wrote: > Hi: If you take a PharoCore image, and browse the editions of a class, then select an older one, and then select "compare to current", you see the differences using the "new" diff, the same that we use in MC. > > However, after installing OB in a core image, it uses the "old" version. I am not sure that change is due to OB, but at least it seems. I checked in Preferences but I didn't find anything. > > Any hint how to put new diff again after installing OB ? > > Thanks! > > Mariano > _______________________________________________ > 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 ------------------------------------------------------------------------------ _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 19, 2010