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

Re: [Pharo-project] Issue 2451: Make Algernon work in Pharo 1.1

by Mariano Martinez Peck

Hi Guille. Yes, some months ago I discovered that changeset. I separated it, saved into a .ch, loaded it into a PharoCore clean image and I tried to understood it. My knoweldege about Morhpic is very limited, but the changed looked of for me. What would be cool is to commit to inbox such changes. Create an issue like "*support various focus holders for **HandMorph *" Then, send a separated mail about this changes and get feedback. If agree, we can integrate it in the core. With this, at least Algernon doesn't have to do such hack. I also asked this to Romian as he was developing WorkingSet and the problem was that you couldn't have both at the same time because of the shortcuts. These changes may solve that. Although he didn't have time to look at it. Cheers Mariano On Mon, Jun 7, 2010 at 5:54 AM, Guillermo Polito <guillermopolito(a)gmail.com>wrote: > Hi, i was looking at this issue and I have some questions :): > > - There are some changes to HandMorph in a changeset hardcoded in the > ConfigurationOfAlgernon. As Mariano said here ( > http://forum.world.st/Putting-Algernon-and-WorkingSet-in-a-Dev-image-td1295…) > "The main change does the simples modifications to HandMorph for it to > support various focus holders". Is it safe to integrate it in Pharo? If > so, should it be integrated in the core Morph package? The changeset is > the following: > > * '''From Squeak3.7gamma of ''''17 July 2004'''' [latest update: #5985] on > 9 August 2004 at 7:56:10 pm''! > "Change Set: MultipleFocusHolder-hpt > Date: 9 August 2004 > Author: Hernan Tylim > > This changesets does the simplest modifications to HandMorph for it to > support various focus holders. > > The important changes are: > > * addiionalKeyboardFocuses instance variable was added with its getter and > setter methods. > > * HandMorph>>sendKeyboardEvent: was changed to traverse the list of > keyboard focus holders and call HandMorph>>sendEvent:focus:clear: to each > one of them. > > * HandMorph>>sendEvent:focus:clear: was changed to preserve the > ''wasHandled'' status of the event, before that info were lost because the > Event instance were copied before passed to the Morph. > "! > > Morph subclass: #HandMorph > instanceVariableNames: ''mouseFocus keyboardFocus eventListeners > mouseListeners keyboardListeners mouseClickState mouseOverHandler > lastMouseEvent targetOffset damageRecorder cacheCanvas cachedCanvasHasHoles > temporaryCursor temporaryCursorOffset hasChanged savedPatch userInitials > lastEventBuffer genieGestureProcessor additionalKeyboardFocuses '' > classVariableNames: ''DoubleClickTime EventStats NewEventRules > NormalCursor PasteBuffer ShowEvents '' > poolDictionaries: ''EventSensorConstants'' > category: ''Morphic-Kernel''! > > !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/8/2004 01:52''! > addAdditionalKeyboardFocus: aMorph > (self additionalKeyboardFocuses includes: aMorph) > ifFalse: [self additionalKeyboardFocuses addFirst: aMorph]! ! > > !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/7/2004 23:47''! > additionalKeyboardFocuses > ^additionalKeyboardFocuses ifNil: [additionalKeyboardFocuses _ > OrderedCollection new].! ! > > !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/8/2004 00:12''! > clearFocusHolder: aMorph > self keyboardFocus == aMorph > ifTrue: [^self keyboardFocus: nil]. > (self additionalKeyboardFocuses includes: aMorph) > ifTrue: [self removeAdditionalKeyboardFocus: aMorph].! ! > > !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/7/2004 23:48''! > fullKeyboardFocuses > ^self additionalKeyboardFocuses copyWith: self keyboardFocus.! ! > > !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/7/2004 23:43''! > keyboardFocuses > keyboardFocuses ifNil: [keyboardFocuses := OrderedCollection new]. > ^keyboardFocuses! ! > > !HandMorph methodsFor: ''focus handling'' stamp: ''hpt 8/7/2004 23:49''! > removeAdditionalKeyboardFocus: aMorph > self additionalKeyboardFocuses remove: aMorph! ! > > !HandMorph methodsFor: ''private events'' stamp: ''hpt 8/8/2004 01:18''! > sendFocusEvent: anEvent to: focusHolder clear: aBlock > "Send the event to the morph currently holding the focus" > | result w e | > w _ focusHolder world ifNil:[^ aBlock value]. > w becomeActiveDuring:[ > ActiveHand _ self. > ActiveEvent _ anEvent. > e _ (anEvent transformedBy: (focusHolder transformedFrom: self)). > result _ focusHolder handleFocusEvent: e . > anEvent wasHandled: e wasHandled. > ]. > ^result! ! > > !HandMorph methodsFor: ''private events'' stamp: ''hpt 8/8/2004 01:09''! > sendKeyboardEvent: anEvent > "Send the event to the morph currently holding the focus, or if none to > the owner of the hand." > > self fullKeyboardFocuses do: [:focusHolder | > "(anEvent keyCharacter = $\) ifTrue: [self halt]." > anEvent wasHandled > ifFalse: [self sendEvent: anEvent focus: focusHolder > clear:[self clearFocusHolder: focusHolder]]].! ! > > Morph subclass: #HandMorph > instanceVariableNames: ''mouseFocus keyboardFocus eventListeners > mouseListeners keyboardListeners mouseClickState mouseOverHandler > lastMouseEvent targetOffset damageRecorder cacheCanvas cachedCanvasHasHoles > temporaryCursor temporaryCursorOffset hasChanged savedPatch userInitials > lastEventBuffer genieGestureProcessor additionalKeyboardFocuses'' > classVariableNames: ''DoubleClickTime EventStats NewEventRules > NormalCursor PasteBuffer ShowEvents'' > poolDictionaries: ''EventSensorConstants'' > category: ''Morphic-Kernel''! > *' > > It should be nice someone who knows well morphic checks it. > > Cheers, > Guille >

June 7, 2010

Re: [Pharo-project] pharo smalltalk for an usb stick

by Tudor Girba

Yes. You have several options (I would suggest the first one): 1. The Moose 4.0 (based on Pharo 1.0) one-click image: http://moosetechnology.org/res/download/moose-suite-4_0.app.zip 2. Load the 4.0 in a Pharo 1.0 image: Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadRelease40 3. Load the latest development version in Pharo 1.1 dev image: Gofer new squeaksource: 'Moose'; package: 'ConfigurationOfMoose'; load. (Smalltalk at: #ConfigurationOfMoose) perform: #loadDefault Cheers, Doru On 6 Jun 2010, at 21:15, Hilaire Fernandes wrote: > Is Moosse directly usable once installed in a Pharo image? > > Hilaire > > Tudor Girba a Ã©crit : >> Maybe Moose could be of interest: >> http://www.moosetechnology.org/download > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "When people care, great things can happen."

June 7, 2010

Re: [Pharo-project] GAUCHO 1.0 released!

by Lukas Renggli

Hi Fernando Very cool. I want to try but run into several problems: http://code.google.com/p/gauchoenvironment/issues/detail?id=1 http://code.google.com/p/gauchoenvironment/issues/detail?id=2 It would be cool if you could provide a ready-made image, or even a one-click download. Lukas 2010/6/7 Fernando olivero <oliverof(a)lu.unisi.ch>: > Hi Pharo programmers! > We are Â happy to announce that Gaucho 1.0 is released. > Gaucho is a direct manipulation environment for software. > If you want to try it out go to http://gaucho.inf.usi.ch/ . > Gaucho1.0 works in Pharo1.0. > In the releases section you'll find the installation script , and a > description of all the features of Gaucho1.0. > Any Â feedback you are willing to provide is welcomed! > In the website you will find a bug issue tracker and the mailing list > description. > Or you can also send us an email for any other purpose, such as demo-request > or inquiries about the Gaucho project. > > Hope you enjoy using it as much as we do! > Fernando Olivero > University Of Lugano > > pd: Â Be ready for the next version, with many improvements and added > features! Soon to come. > pd2: (Extract from the web page) > -------------------------------------------------- > Version:Â 1.0 > Features included in this version: > > Direct manipulation of Classes, methods and packages > Easily perform rename refactorings of classes and methods > Draggable arrows for manipulating the inheritance relationships between > classes > Creating and runing tests for all the classes in the system > Creating workspaces for taking snapshots of the current pampas > Smart searching for any object in the system > Keyboard shortcuts associated to the most important operations > Logging all the changes to the system > Saving/Loading developers and workspaces to the default local directory > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

June 7, 2010

Re: [Pharo-project] ISSUE 2514

by Adrian Lienhard

Hi Fernando, Thanks for the fix. Now there is a new failing test: #testAcceptConcents (at least I don't remember that we saw this failing before). Can you check? Cheers, Adrian On Jun 6, 2010, at 20:04 , StÃ©phane Ducasse wrote: > THANKS!!! > > Stef > > On Jun 6, 2010, at 7:16 PM, Jorge Ressia wrote: > >> Hi, >> >> Thanks Fernando! >> >> Adrian, Stef this is the fix required for fixing one of the remanning >> failing tests in Pharo 1.1 >> >> Cheers, >> >> Jorge >> >> On Sun, Jun 6, 2010 at 4:28 PM, Fernando olivero <oliverof(a)lu.unisi.ch> wrote: >>> SLICE-NewTextMorph-acceptContents-FernandoOlivero.1 >>> >>> >>> >>> ISSUE 2514 >>> NewTextMorph does not accept on cmd-s. >>> NewTextMorph>>example1 is not working. >>> >>> Fixed this issue, made a test and aslo fixed #testFittingParagraph >>> >>> >>> _______________________________________________ >>> 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

June 7, 2010

Re: [Pharo-project] SmalltalkImage vs SystemDictionary

by Lukas Renggli

To separate the namespace (SmalltalkDictionary) from all the image related tasks (SmalltalkImage). On Monday, June 7, 2010, GermÃ¡n Leiva <leivagerman(a)gmail.com> wrote: > I expected that but what's the reason behind that change? > > The entry is http://code.google.com/p/pharo/issues/detail?id=2136 > > 2010/6/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > > On Jun 7, 2010, at 1:32 AM, GermÃ¡n Leiva wrote: > >> Hi, >> >> I have a doubt ... >> >> why in Pharo 1.0 >> >> Smalltalk class == SystemDictionary >> >> and in Pharo 1.1 >> >> Smalltalk class == SmalltalkImage? > > Yes this is normal > > now Smalltalk globals class == SystemDictionary > >> Â Looking at the issue tracker (thanks Carla): >> We should make >> >> - Smalltalk pointing to SmalltalkImage current >> - have SystemDictionary only having classbindings management. >> and Smalltalk globals pointing to SystemDictionary instance. > > this is done. > which entry is that? >> >> This way we finish the refactoring started long time ago. >> We should have a look at the way this was done in Squeak so that we get the same >> compatible for now solution. >> >> What's involved in the refactoring started long time ago and what's the motivation for it? >> >> Cheers >> -- >> GermÃ¡n Leiva >> LeivaGerman(a)gmail.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 > > > -- > GermÃ¡n Leiva > LeivaGerman(a)gmail.com > -- Lukas Renggli www.lukas-renggli.ch

June 7, 2010

Re: [Pharo-project] SmalltalkImage vs SystemDictionary

by Nicolas Cellier

Search in squeak-dev archive around 14 July 2009 [squeak-dev] Smalltalk vs SmalltalkImage current woes Also in February and March 2010 in squeak-devand Pharo mailing lists. Long, several month span, multithreaded discussions... As I said before, it would be good to have a rationale summarized in a wiki or somehere. Nicolas 2010/6/7 GermÃ¡n Leiva <leivagerman(a)gmail.com>: > I expected that but what's the reason behind that change? > > The entry is http://code.google.com/p/pharo/issues/detail?id=2136 > 2010/6/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> >> >> On Jun 7, 2010, at 1:32 AM, GermÃ¡n Leiva wrote: >> >> > Hi, >> > >> > I have a doubt ... >> > >> > why in Pharo 1.0 >> > >> > Smalltalk class == SystemDictionary >> > >> > and in Pharo 1.1 >> > >> > Smalltalk class == SmalltalkImage? >> >> Yes this is normal >> >> now Smalltalk globals class == SystemDictionary >> >> > Â Looking at the issue tracker (thanks Carla): >> > We should make >> > >> > - Smalltalk pointing to SmalltalkImage current >> > - have SystemDictionary only having classbindings management. >> > and Smalltalk globals pointing to SystemDictionary instance. >> >> this is done. >> which entry is that? >> > >> > This way we finish the refactoring started long time ago. >> > We should have a look at the way this was done in Squeak so that we get >> > the same >> > compatible for now solution. >> > >> > What's involved in the refactoring started long time ago and what's the >> > motivation for it? >> > >> > Cheers >> > -- >> > GermÃ¡n Leiva >> > LeivaGerman(a)gmail.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 > > > > -- > GermÃ¡n Leiva > LeivaGerman(a)gmail.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 7, 2010

Re: [Pharo-project] SmalltalkImage vs SystemDictionary

by GermÃ¡n Leiva

I expected that but what's the reason behind that change? The entry is http://code.google.com/p/pharo/issues/detail?id=2136 2010/6/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Jun 7, 2010, at 1:32 AM, GermÃ¡n Leiva wrote: > > > Hi, > > > > I have a doubt ... > > > > why in Pharo 1.0 > > > > Smalltalk class == SystemDictionary > > > > and in Pharo 1.1 > > > > Smalltalk class == SmalltalkImage? > > Yes this is normal > > now Smalltalk globals class == SystemDictionary > > > Looking at the issue tracker (thanks Carla): > > We should make > > > > - Smalltalk pointing to SmalltalkImage current > > - have SystemDictionary only having classbindings management. > > and Smalltalk globals pointing to SystemDictionary instance. > > this is done. > which entry is that? > > > > This way we finish the refactoring started long time ago. > > We should have a look at the way this was done in Squeak so that we get > the same > > compatible for now solution. > > > > What's involved in the refactoring started long time ago and what's the > motivation for it? > > > > Cheers > > -- > > GermÃ¡n Leiva > > LeivaGerman(a)gmail.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 > -- GermÃ¡n Leiva LeivaGerman(a)gmail.com

June 7, 2010

Re: [Pharo-project] Pharocasts: GUI - Proportional layout

by laurent laffont

On Mon, Jun 7, 2010 at 3:00 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > > Another awesome screencast! I really like the subtitles. > > Two things: > > 1. It would be awesome to link to the ScriptManager workspaces from the web > page. I just played around in ScriptMan and found you can export to a file > - right click in top left pane, select export. > At first I wanted to show it, but the import function needs some work (open a file manager). > 2. The part in the screencast that says "then offsets move the top-left and > bottom-right corner inward a specified number of pixels" (2:48). It seems > the word "inward" should be removed. This is something it took me a while > to get as I've learned about layouts - because the extent is set to 0@0, > these offsets are from there; saying "inward" makes it sound like they're > applied relative to the edge of the owner morph, which is a natural - and > wrong - assumption. The general point here is that fractions are applied > and then offsets are applied relative to that transformation. > Could you write a sentence to replace it ? I may regenerate subtitles / video as I received several suggestions for subtitles. Thank you for feedback. Laurent > > Thanks. > Sean > -- > View this message in context: > http://forum.world.st/Pharocasts-GUI-Proportional-layout-tp2245223p2245385.… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 7, 2010

Re: [Pharo-project] GAUCHO 1.0 released!

by laurent laffont

2010/6/7 Fernando olivero <oliverof(a)lu.unisi.ch> > Hi Pharo programmers! > > We are happy to announce that Gaucho 1.0 is released. > > Gaucho is a direct manipulation environment for software. > > If you want to try it out go to http://gaucho.inf.usi.ch/ . > > Gaucho1.0 works in Pharo1.0. > > In the releases section you'll find the installation script , and a > description of all the features of Gaucho1.0. > > Any feedback you are willing to provide is welcomed! > In the website you will find a bug issue tracker and the mailing list > description. > Or you can also send us an email for any other purpose, such as > demo-request or inquiries about the Gaucho project. > > > Hope you enjoy using it as much as we do! > > Fernando Olivero > University Of Lugano > Hi, I suggest you put the screencasts on Vimeo as the quality is far better than YouTube. That's what I use for Pharocasts, IMHO it's really important that we can read the text. Also note some people prefer to download the screencasts, can you put a link to original videos ? Gaucho looks great. Marketing is really important too :) Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ > > > pd: Be ready for the next version, with many improvements and added > features! Soon to come. > > pd2: (Extract from the web page) > > -------------------------------------------------- > *Version: 1.0* > * > * > *Features included in this version:* > > - *Direct manipulation of Classes, methods and packages* > - *Easily perform rename refactorings of classes and methods* > - *Draggable arrows for manipulating the inheritance relationships > between classes* > - *Creating and runing tests for all the classes in the system* > - *Creating workspaces for taking snapshots of the current pampas* > - *Smart searching for any object in the system* > - *Keyboard shortcuts associated to the most important operations* > - *Logging all the changes to the system* > - *Saving/Loading developers and workspaces to the default local > directory* > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 7, 2010

Re: [Pharo-project] Pharocasts: GUI - Proportional layout

by StÃ©phane Ducasse

may be having more white space under the subtitles would make sure that you can read them well. On Jun 7, 2010, at 3:00 AM, Sean P. DeNigris wrote: > > Another awesome screencast! I really like the subtitles. > > Two things: > > 1. It would be awesome to link to the ScriptManager workspaces from the web > page. I just played around in ScriptMan and found you can export to a file > - right click in top left pane, select export. > > 2. The part in the screencast that says "then offsets move the top-left and > bottom-right corner inward a specified number of pixels" (2:48). It seems > the word "inward" should be removed. This is something it took me a while > to get as I've learned about layouts - because the extent is set to 0@0, > these offsets are from there; saying "inward" makes it sound like they're > applied relative to the edge of the owner morph, which is a natural - and > wrong - assumption. The general point here is that fractions are applied > and then offsets are applied relative to that transformation. > > Thanks. > Sean > -- > View this message in context: http://forum.world.st/Pharocasts-GUI-Proportional-layout-tp2245223p2245385.… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 7, 2010