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

Re: [Pharo-project] SmalltalkImage vs SystemDictionary

by StÃ©phane Ducasse

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

June 7, 2010

Re: [Pharo-project] GAUCHO 1.0 released!

by StÃ©phane Ducasse

did you use a specific package to bind your keymapping? How do you want to community to give you feedback (for your research papers :))? Stef On Jun 7, 2010, at 12:22 AM, Fernando olivero wrote: > 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

June 7, 2010

Re: [Pharo-project] SmalltalkImage vs SystemDictionary

by Lukas Renggli

> What's involved in the refactoring started long time ago and what's the > motivation for it? To separate the namespace (SmalltalkDictionary) from all the image related tasks (SmalltalkImage). Lukas -- Lukas Renggli www.lukas-renggli.ch

June 7, 2010

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

by Guillermo Polito

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] Keyboard Shortcuts in Pharo?

by Guillermo Polito

Well, some days ago I downloaded the KeyBindings from monticello in a Pharo 1.1 dev image. It downloaded well allowing the _ as assignment. But it didn't work :/. Maybe I just missed something. Thinking about adding nice and configurable shortcuts to Morphic and after reading some mails in this thread, I had some thoughts (I'm just thinking aloud): 1) Maybe a class variable in Morph to share the global shortcuts and an instance class variable to have specific shortcuts could do it. 2) Buuut, maybe there is a shortcut that is shared in a context bigger than a morph and smaller than "all the morphs". And maybe that context is the model of the morph. In that case I think it would be right to delegate the resolution of the shortcut to the model. 3) I've never used emacs :). Does it have "chords" of shortcuts? I call a chord pressing ((ctrl+A) + (ctrl +e)) to make one and only one action. This should make us mantain the state of the pressed keys... I donÂ´t think this will be a performance issue, but we must have it in mind. 4) How should compound Morphs resolve a shortcut? Should the shortcut flow to the parent morph or not? If so, when should it stop flowing :D? I'm thinking in the System Browser, when the focus is on a paragraph editor but you want to do something with the selected class. Mmm, this is related to 2) :). 5) We should have a well ordered plan to introduce this kind of change. We have to analize and remove every replaceable #keyStroke:. And there should be a simple way to deploy the shortcuts for non-core packages :) What do you think? What I am missing? I want to introduce shortcuts at any cost, je (even if lose sleep hours :) ). Cheers, Guille On Sat, May 15, 2010 at 4:50 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > > > > > > I've got all three running in Squeak 4.1 trunk. Loading in Pharo will be > > more complicated due to missing dependencies - maybe not worth it. It > might > > be better to catalogue how they work and come up with something simple > and > > flexible from scratch? > > > > There is a solution brewing in my head that generalizes key bindings to a > > condition and action. So, instead of being restricted to 'when shift and > c > > are pressed' you could say 'when shift and c are pressed and a Workspace > is > > the active morph' > > If I remember (was 8 years ago) the mapping table is shared globally by all > paragraphEditor > and what you want is that potentially each morph can have its own table. > So I would not attach context to a binding. But more the table been > attached to a morph > would be active. But I do not have a definitive answer. > > Now a trick used by the VW parser to have sharing and instance specific > table is the following > The trick to get something cool is to have both a class var and an instance > var that represent > a table: the method only access the table via inst var, at class initialize > the classVar is initialized > then at instance creation the inst var points to the class var. > > => sharing of the class Var > but now on a specific instance you can copy the table and set up to a give > object and > it will be used by the object. while others will share the global table. > > Workspace class could simply have its own specific table for all instances > Roel Wuyts designed the magic shortcut in VW it worked quite well so I > think that it would be worth to have a look > at them. They got integrated in the VW release. > > Stef > > > > > > The only thing that seems like it will be complicated is vi bindings > (don't > > know enough to say about emacs). For instance, I can't see how normal > mode > > could be implemented without changing some existing classes (for example, > > the cursor must change). > > > > Sean > > -- > > View this message in context: > http://forum.world.st/Keyboard-Shortcuts-in-Pharo-tp1298784p2217472.html > > 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 > > > _______________________________________________ > 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] Changes aren't saved in the default (unnamed) changeset on a new image

by Guillermo Polito

Oook, I updated the image and realized that the issue was fixed in a cleaning of ScriptLoader>>cleanUpForRelease. The problem was that the changesets cleaning was duplicated and the second cleaning was in the wrong order. But now, playing with the cleanUpFor Release I noticed that the first time you clean the image, the default changeset keeps dirty because of the changes made in the cleanUp. I set this issue as fixed and opened this new one: http://code.google.com/p/pharo/issues/detail?id=2515&q=changeset&colspec=ID… I found a fix, but I would like someone to reproduce it. Cheers, Guille On Fri, Jun 4, 2010 at 7:21 PM, Guillermo Polito <guillermopolito(a)gmail.com>wrote: > > http://code.google.com/p/pharo/issues/detail?id=2504&colspec=ID%20Type%20St… > > :) > > 2010/6/4 Mariano Martinez Peck <marianopeck(a)gmail.com> > > Hi Guille. I could reproduce the problem. Please create an issue and put >> milestone 1.1. >> >> More investigation: in PharoCore it works perfect, the problem is with >> PharoDev. >> >> More details: the problem is in ScriptLoader >> cleanUpForRelease >> >> This method is being call when the Dev image is created. If you take a >> PharoCore, the changeset are working well. Take that image, and evaluate >> ScriptLoader nwe cleanUpForRelease. After this, it should start the problem >> you mention. Can you reproduce this? >> >> Now, we need to see where the problem is in cleanUpForRelease. We need >> some debugging here. No time now. Maybe it is related to the lines: >> >> ChangeSet removeChangeSetsNamedSuchThat: [ :each | true ]. >> ChangeSet resetCurrentToNewUnnamedChangeSet. >> >> but just a guess. >> >> Cheers >> >> mariano >> >> 2010/6/4 Guillermo Polito <guillermopolito(a)gmail.com> >> >> They are not saved :D, that's what motivated me to send this email :P. >>> >>> I'll open one :) >>> >>> >>> On Fri, Jun 4, 2010 at 1:18 PM, StÃ©phane Ducasse < >>> stephane.ducasse(a)inria.fr> wrote: >>> >>>> where is it saved? >>>> it may be a bug >>>> create a bug entry with a nice description :) >>>> >>>> Stef >>>> On Jun 4, 2010, at 5:23 PM, Guillermo Polito wrote: >>>> >>>> > Hi! >>>> > >>>> > I'm using the develop Pharo-1.1-11367-Beta on windows. >>>> > >>>> > When I make a change with a fresh image, that change isn't saved in >>>> the default changeset :(. In the Core image it's just ok. >>>> > >>>> > Is it a bug or a 'feature'? >>>> > >>>> > Cheers, >>>> > Guille >>>> > _______________________________________________ >>>> > 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 >> > >

June 7, 2010

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

by Sean P. DeNigris

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.

June 7, 2010

[Pharo-project] SmalltalkImage vs SystemDictionary

by GermÃ¡n Leiva

Hi, I have a doubt ... why in Pharo 1.0 Smalltalk class == SystemDictionary and in Pharo 1.1 Smalltalk class == SmalltalkImage? 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 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

June 6, 2010

Re: [Pharo-project] GAUCHO 1.0 released!

by Igor Stasenko

Cool stuff! A fresh different workflow for coding. Time will show, how better it is comparing to traditional one. :) 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 > -- Best regards, Igor Stasenko AKA sig.

June 6, 2010

[Pharo-project] GAUCHO 1.0 released!

by Fernando olivero

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

June 6, 2010