March 2009 - Pharo-dev - lists.pharo.org

[Pharo-project] Fwd: [SoC] Wanted: Google Summer of Code 2009 Mentors and Projects

by StÃ©phane Ducasse

> >> From: "Aik-Siong Koh" <askoh(a)askoh.com> >> Date: March 9, 2009 5:00:35 AM CEST >> To: soc(a)lists.squeakfoundation.org >> Subject: [SoC] Wanted: Google Summer of Code 2009 Mentors and >> Projects >> Reply-To: askoh(a)askoh.com, Squeak Summer of Code mailing list <soc(a)lists.squeakfoundation.org >> > >> >> It is time for us to apply for Google Summer of Code 2009 (Mar >> 9-13th). In >> order to be successful we need to show that we have lots of mentors >> and >> projects. Please visit >> http://wiki.squeak.org/squeak/6118 >> and put your name as mentor and post your projects. Also join the SoC >> mailing list. GSOC has been very good to the Squeak community in >> the past >> two years. >> >> Thanks, >> Aik-Siong Koh >> GSOC 2009 admin

March 9, 2009

Re: [Pharo-project] loading ClosureBootstrap-08-11-14 in Pharo.

by Rob Rothwell

I'm not an expert at MC and script loader, but as a "newbie" I have spent more time building images than actually programming, so I would be happy to help try things out if you need volunteers. I am actually running the current pharo image with the new VM already just because I was wondering if it would work! Rob On Mon, Mar 9, 2009 at 2:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Hi guys > > Here is an email of John related to closure for pharo. > We (the core) believe that it would be good to integrate really fast the > closure. > Now we need help > - we need to know if the vm are available and people can take care > of that > - we need some volunteer knowing MC and our script loader (lukas) > to check whether > (1) load the code > (2) publish package > (3) reload them > > Any suggestion how we could also proceed once the changes are pushed in the > stream > because the VM will not work. > > Stef > > Ok, attached is a testing 4.0.0b1 macintosh carbon vm. It is not for >> public use yet because I've not included all the plugins and I need to cross >> check things >> for sanity. However you can use it to make a Pharo image with closure. >> >> To do this you need the hackstogettoclosure which gets you around some >> changes from squeak 3.9 to pharo. I've also altered the attached >> ClosureBootstrap-08-11-14-John-M-McIntosh-ALTERED.tar.zip a which is changed >> a bit from Eliot's version to remove some referrals to Morphic classes you >> have deleted in Pharo. >> >> If you follow the read me you should be able to take a Pharo0.1Core-10243 >> >> and end up with one complaint about TranslatedMethod being put in >> Undeclared, and 3 obsolete block contexts. and 3 Unbound Methods. >> >> If you can't get that far let me know. >> >> Obviously this is just a hack to see how far I could get, I'll assume >> you'll peer deeper because many of the change sets update code I'm sure >> you've altered for Pharo. >> >> >> >> >> >> > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 9, 2009

[Pharo-project] loading ClosureBootstrap-08-11-14 in Pharo.

by StÃ©phane Ducasse

Hi guys Here is an email of John related to closure for pharo. We (the core) believe that it would be good to integrate really fast the closure. Now we need help - we need to know if the vm are available and people can take care of that - we need some volunteer knowing MC and our script loader (lukas) to check whether (1) load the code (2) publish package (3) reload them Any suggestion how we could also proceed once the changes are pushed in the stream because the VM will not work. Stef > Ok, attached is a testing 4.0.0b1 macintosh carbon vm. It is not for > public use yet because I've not included all the plugins and I need > to cross check things > for sanity. However you can use it to make a Pharo image with closure. > > To do this you need the hackstogettoclosure which gets you around > some changes from squeak 3.9 to pharo. I've also altered the > attached ClosureBootstrap-08-11-14-John-M-McIntosh-ALTERED.tar.zip a > which is changed a bit from Eliot's version to remove some referrals > to Morphic classes you have deleted in Pharo. > > If you follow the read me you should be able to take a > Pharo0.1Core-10243 > > and end up with one complaint about TranslatedMethod being put in > Undeclared, and 3 obsolete block contexts. and 3 Unbound Methods. > > If you can't get that far let me know. > > Obviously this is just a hack to see how far I could get, I'll > assume you'll peer deeper because many of the change sets update > code I'm sure you've altered for Pharo. > > > > >

March 9, 2009

Re: [Pharo-project] How to copy to clipboard a wallback ?

by Dale Henrichs

----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | Hi guys! That's all I need to know right now :) | | Thanks in advance, | | Mariano | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project Mariano, With the OB Debugger, there is an error report menu item that brings up an inspector on the error report, which has a stack embedded in it. Dale

March 9, 2009

Re: [Pharo-project] How to copy to clipboard a wallback ?

by Adrian Lienhard

In the directory where your Pharo image is located, a file named SqueakDebug.log with the walkback is created. HTH, Adrian ___________________ http://www.adrian-lienhard.ch/ On Mar 9, 2009, at 15:40 , Mariano Martinez Peck wrote: > Hi guys! That's all I need to know right now :) > > Thanks in advance, > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 9, 2009

[Pharo-project] How to copy to clipboard a wallback ?

by Mariano Martinez Peck

Hi guys! That's all I need to know right now :) Thanks in advance, Mariano

March 9, 2009

[Pharo-project] Blocked while merging

by StÃ©phane Ducasse

Hi all I wanted to merge and I tried with the new Diff tools and I got a selector DNU, so I switched back to the old merge tool but I got the following bugs - click on an item bring the menu revertSelection -> DNU diff -> DNU install crahsed. Does anybody get the same, I'm using pharo 10248 Stef

March 9, 2009

[Pharo-project] [BUG] Merging Tool UndefinedObject(Object)>>doesNotUnderstand: #selector

by stephane.ducasse＠inria.fr

I pressed on next conflict. Stef 9 March 2009 1:45:36 pm VM: Mac OS - a SmalltalkImage Image: Pharo0.1 [Latest update: #10248] SecurityManager state: Restricted: false FileAccess: true SocketAccess: true Working Dir /Users/ducasse/Workspace/FirstCircle/ActiveResearch/Pharo/Pharo Trusted Dir /foobar/tooBar/forSqueak/bogus Untrusted Dir /Users/ducasse/Library/Preferences/Squeak/Internet/My Squeak UndefinedObject(Object)>>doesNotUnderstand: #selector Receiver: nil Arguments and temporary variables: aMessage: selector exception: MessageNotUnderstood: UndefinedObject>>selector resumeValue: nil Receiver's instance variables: nil PSMCMergePatchMorph>>selectNextConflict Receiver: a PSMCMergePatchMorph(2798) Arguments and temporary variables: next: a MCConflict Receiver's instance variables: bounds: 39@77 corner: 1651@564 owner: a PSMCMergeMorph(3639) submorphs: an Array(a ProportionalSplitterMorph(3787) a MergeDiffMorph(3261) a ...etc... fullBounds: 39@77 corner: 1651@564 color: Color transparent extension: a MorphExtension (1779) [other: (myDependents -> a DependentsArray(...etc... borderWidth: 0 borderColor: #inset model: an OrderedCollection(a MCModification a MCModification a MCAddition a MC...etc... slotName: nil open: false diffMorph: a MergeDiffMorph(3261) changeTree: a TreeListMorph(2496) selectedChangeWrapper: a PSMCConflictWrapper PSMCMergeMorph>>selectNextConflict Receiver: a PSMCMergeMorph(3639) Arguments and temporary variables: Receiver's instance variables: bounds: 39@77 corner: 1651@889 owner: a StandardWindow(1034) submorphs: an Array(a ProportionalSplitterMorph(2834) a PanelMorph(1565) a Plug...etc... fullBounds: 39@77 corner: 1651@889 color: Color white extension: a MorphExtension (2299) [locked] [other: (myDependents -> a Depend...etc... borderWidth: 0 borderColor: (Color r: 0.667 g: 0.667 b: 0.667) model: a MCThreeWayMerger slotName: nil open: false patchMorph: a PSMCMergePatchMorph(2798) codeMorph: a PluggableTextEditorMorph(3583) merged: false PluggableButtonMorphPlus(PluggableButtonMorph)>>performAction Receiver: a PluggableButtonMorphPlus(3905) Arguments and temporary variables: Receiver's instance variables: bounds: 43@861 corner: 121@885 owner: a PanelMorph(1565) submorphs: an Array(an AlignmentMorph(1769)) fullBounds: 43@861 corner: 121@885 color: (Color r: 0.827 g: 0.827 b: 0.827) extension: a MorphExtension (1467) [balloonText] [other: (layoutPolicy -> a T...etc... borderWidth: 0 borderColor: Color transparent model: a PSMCMergeMorph(3639) label: '5 conflicts' getStateSelector: nil actionSelector: #selectNextConflict getLabelSelector: #conflictCountString getMenuSelector: nil shortcutCharacter: nil askBeforeChanging: false triggerOnMouseDown: false offColor: nil onColor: nil feedbackColor: nil showSelectionFeedback: false allButtons: nil arguments: #() argumentsProvider: nil argumentsSelector: nil enabled: true action: nil getColorSelector: nil getEnabledSelector: #notAllConflictsResolved --- The full stack --- UndefinedObject(Object)>>doesNotUnderstand: #selector PSMCMergePatchMorph>>selectNextConflict PSMCMergeMorph>>selectNextConflict PluggableButtonMorphPlus(PluggableButtonMorph)>>performAction - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - PluggableButtonMorphPlus>>performAction [] in PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: {[:m | (m containsPoint: evt cursorPoint) ifTrue: [m performAction]]} Array(SequenceableCollection)>>do: PluggableButtonMorphPlus(PluggableButtonMorph)>>mouseUp: PluggableButtonMorphPlus>>mouseUp: PluggableButtonMorphPlus(Morph)>>handleMouseUp: MouseButtonEvent>>sentTo: PluggableButtonMorphPlus(Morph)>>handleEvent: PluggableButtonMorphPlus(Morph)>>handleFocusEvent: [] in HandMorph>>sendFocusEvent:to:clear: {[ActiveHand := self. ActiveEvent := anEvent. result := focusHolder han...]} [] in PasteUpMorph>>becomeActiveDuring: {[aBlock value]} BlockContext>>on:do: PasteUpMorph>>becomeActiveDuring: HandMorph>>sendFocusEvent:to:clear: HandMorph>>sendEvent:focus:clear: HandMorph>>sendMouseEvent: HandMorph>>handleEvent: HandMorph>>processEvents [] in WorldState>>doOneCycleNowFor: {[:h | ActiveHand := h. h processEvents. ActiveHand := nil]} ...etc...

March 9, 2009

Re: [Pharo-project] soap and Pharo

by CÃ©drick BÃ©ler

depends, XMLSuport is maybe clearer to newcomers... and I don't particularly find XML fun ;) 2009/3/8 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > would be nice to rename the category and package as Yaxo (much more > fun than XMLSupport). > > On Mar 5, 2009, at 6:45 PM, Michael Rueger wrote: > >> CÃ©drick BÃ©ler wrote: >>> Do you know if soap(core) load in Pharo ? >>> >>> There's a dependancy on Yaxo which doesn't load because of some >>> mimetype problem. >>> Maybe I'm wrong but there is already xml support in Pharo but not >>> trough Yaxo... ? >> >> Oh, Yaxo needs to work on Pharo, need to check. >> >> Michael >> >> _______________________________________________ >> 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 > -- CÃ©drick

March 9, 2009

Re: [Pharo-project] Pharo

by Gary Chambers

Trust a Frenchman to describe things as sexy! Love you to Stef! Regards, Gary ----- Original Message ----- From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> To: <Pharo-project(a)lists.gforge.inria.fr> Sent: Sunday, March 08, 2009 9:30 PM Subject: Re: [Pharo-project] Pharo > tx! > For the looking and feeling I'm not involved :) but indeed we are > going in the right direction. > >> Pharo is looking good, feeling good and getting good. >> Glad to be involved with the dynamic team. > > Thanks we are a nice team without you pharo would be less sexy. > >> >> 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

March 9, 2009