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

Re: [Pharo-project] [ANN] First release of Keymappings for Pharo

by Francisco Ortiz PeÃ±aloza

Can wait to see it Best regards, Francisco On Fri, Dec 17, 2010 at 9:07 AM, Guillermo Polito <guillermopolito(a)gmail.com > wrote: > Hi! > > I wanted to announce some advances in my work on Keymapping. What I did so > far: > - some refactors and changes. I did them While I learnt the code and how > it worked. There's much cleaning left. > - I added some comments to classes > - added and changed tests > - added a Pragma mecanism to collect the keymappings, like this: > > SomeClass class>>declareKeymappingOn: aBuilder > <keymap> > aBuilder > addKeymap: [ :builder | builder on: '<m-j>' do: [ :m | UIManager > default inform: 'yes!' ] ] on: #Test; > attach: #Test to: SystemWindow. > > > Next things I want to do on it: > - more cleaning > - a little more documentation > - replace the string way of declaring the shortcuts (the '<m-j>') > - add Application specific shortcuts (today shortcuts are attached to > morphs, and it would be good to get them declared in models of those morphs > too) > - build an usable UI (today's UI doesn't reflect the changes I did. BTW, > it is very odd, and I didn't found a way to use it well). > > Well, I just wanted to share it :P. I believe that in the weekend I'll > build a new release ;). > > Cheers! > Guille >

Dec. 17, 2010

[Pharo-project] Issue 3448 in pharo: MorphicUIManager>>chooseFileMatching:label: uses extensions rather than patterns

by pharo＠googlecode.com

Status: Accepted Owner: gazzaguru2 CC: stephane.ducasse Labels: Milestone-1.2 New issue 3448 by gazzaguru2: MorphicUIManager>>chooseFileMatching:label: uses extensions rather than patterns http://code.google.com/p/pharo/issues/detail?id=3448 The provided patterns are passed to the FileDialogWindow (via UITheme) as the extensions to match. Clearly patterns with potential wildcards are desired. Attached CS to fix. Attachments: UIManagerFileChooserFix.1.cs 1.1 KB

Dec. 17, 2010

[Pharo-project] Issue 3449 in pharo: MorphicUIManager>>chooseFileMatching:label: uses extensions rather than patterns

by pharo＠googlecode.com

Status: Accepted Owner: gazzaguru2 CC: stephane.ducasse Labels: Milestone-1.2 New issue 3449 by gazzaguru2: MorphicUIManager>>chooseFileMatching:label: uses extensions rather than patterns http://code.google.com/p/pharo/issues/detail?id=3449 The provided patterns are passed to the FileDialogWindow (via UITheme) as the extensions to match. Clearly patterns with potential wildcards are desired. Attached CS to fix. Attachments: UIManagerFileChooserFix.1.cs 1.1 KB

Dec. 17, 2010

Re: [Pharo-project] Issue 3446 in pharo: VMMakerTool load config buttondoesn't work

by Gary Chambers

It seems the implementation in MorphicUIManager uses the patterns as extensions. So fileResult := UIManager default chooseFileMatching: #('config') label: 'Select VMMaker configuration...'. would work. However, that misses the meaning of patterns. I've raised issue http://code.google.com/p/pharo/issues/detail?id=3449 with change set attached... Regards, Gary ----- Original Message ----- From: <pharo(a)googlecode.com> To: <pharo-project(a)lists.gforge.inria.fr> Sent: Friday, December 17, 2010 4:21 AM Subject: [Pharo-project] Issue 3446 in pharo: VMMakerTool load config buttondoesn't work > Status: New > Owner: ---- > > New issue 3446 by elpochodelagente: VMMakerTool load config button doesn't > work > http://code.google.com/p/pharo/issues/detail?id=3446 > > Pharo image: dev 1.1.1 > Pharo core version: Pharo-1.1-11411 > Virtual machine used: custom linux, allmost latest VMMaker, classic (not > cog) > Class browser used if applicable: OBSystemBrowserAdaptor > > Steps to reproduce: > 1. Load VMMaker with > 2. Open the VMMakerTool with: "VMMakerTool openInWorld" > 3. Push load config button, you get an error message > > The problem is that VMMaker tool makes use of StandardFileDialog, which > isn't present in Pharo anymore. The method that raises the error is > > VMMakerTool>>#loadConfig > | fileResult file | > fileResult := (StandardFileMenu oldFileMenu: FileDirectory default > withPattern: '*.config') startUpWithCaption: 'Select VMMaker > configuration...'. > fileResult > ifNotNil: [ > file := fileResult directory fullNameFor: fileResult name. > [ > vmMaker := VMMaker forConfigurationFile: file. > vmMaker logger: logger. > vmMaker platformDirectory > ] > on: Error > do: [self inform: 'Possible problem with path settings or > platform name?']. > self updateAllViews] > > > Changing > > fileResult := (StandardFileMenu oldFileMenu: FileDirectory default > withPattern: '*.config') startUpWithCaption: 'Select VMMaker > configuration...'. > > for > > fileResult := UIManager default chooseFileMatching: nil label: 'Select > VMMaker configuration...'. > > and > > file := fileResult directory fullNameFor: fileResult name. > > for > > file := fileResult > > Fixes it almost completely. It would be better to use chooseFileMatching: > #('*.config') but it didn't work well. > > >

Dec. 17, 2010

[Pharo-project] [ANN] First release of Keymappings for Pharo

by Guillermo Polito

Hi! I wanted to announce some advances in my work on Keymapping. What I did so far: - some refactors and changes. I did them While I learnt the code and how it worked. There's much cleaning left. - I added some comments to classes - added and changed tests - added a Pragma mecanism to collect the keymappings, like this: SomeClass class>>declareKeymappingOn: aBuilder <keymap> aBuilder addKeymap: [ :builder | builder on: '<m-j>' do: [ :m | UIManager default inform: 'yes!' ] ] on: #Test; attach: #Test to: SystemWindow. Next things I want to do on it: - more cleaning - a little more documentation - replace the string way of declaring the shortcuts (the '<m-j>') - add Application specific shortcuts (today shortcuts are attached to morphs, and it would be good to get them declared in models of those morphs too) - build an usable UI (today's UI doesn't reflect the changes I did. BTW, it is very odd, and I didn't found a way to use it well). Well, I just wanted to share it :P. I believe that in the weekend I'll build a new release ;). Cheers! Guille

Dec. 17, 2010

Re: [Pharo-project] Issue 3447 in pharo: Do we need to menu entry "Shout Workspace"?

by pharo＠googlecode.com

Comment #1 on issue 3447 by marianopeck: Do we need to menu entry "Shout Workspace"? http://code.google.com/p/pharo/issues/detail?id=3447 no, we don't need. The normal workspace entry IS/Has to be a ShoutWorkspace. But the label in the menu should be just Workspace

Dec. 17, 2010

[Pharo-project] Issue 3447 in pharo: Do we need to menu entry "Shout Workspace"?

by pharo＠googlecode.com

Status: Accepted Owner: marcus.denker Labels: Milestone-1.2-DevImage New issue 3447 by marcus.denker: Do we need to menu entry "Shout Workspace"? http://code.google.com/p/pharo/issues/detail?id=3447 The normal workspace seems to have syntax hihjligting alreaday

Dec. 17, 2010

Re: [Pharo-project] Pharo 1.2 - default packages

by laurent laffont

On Fri, Dec 17, 2010 at 9:38 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Hi Laurent. Once I wrote the following email, but you can see the > answers.... > > > http://forum.world.st/Changes-in-external-packages-for-Pharo-1-2-td2551023.… > > > OK Mariano, thanks Indeed there's not a word on Mocketry / XMLSupport / Cryptography. I will split Autotest in 3 packages Core / Help / Tests and update ConfigurationOfAutotest so it will follow convention. You have written: "For any package we include, it would be AWESOME to have: - tests - a Metacello configuration" IMHO for Pharo 1.2 Metacello configurations should be mandatory. Laurent. > On Fri, Dec 17, 2010 at 9:04 AM, laurent laffont < > laurent.laffont(a)gmail.com> wrote: > >> Hi, >> >> >> What do you think about adding these packages as default in Pharo 1.2: >> - ConfigurationOfMocketry >> - ConfigurationOfXMLSupport >> - ConfigurationOfCryptography (does'nt exist yet, planned to be created >> in a local coding-dojo on Tuesday). >> >> Motivations: >> - XMLSupport and Cryptography are often needed to consume web services >> - Mocketry because I want to write tests using Mocks and it's easier to >> work when tools are in standard Pharo (and then newcomers can see Mocketry >> examples). >> >> >> I will update ConfigurationOfPharo 1.2 (beta3 ?) if people agree. >> >> Cheers, >> >> Laurent Laffont >> > >

Dec. 17, 2010

Re: [Pharo-project] Pharo 1.2 - default packages

by Mariano Martinez Peck

Hi Laurent. Once I wrote the following email, but you can see the answers.... http://forum.world.st/Changes-in-external-packages-for-Pharo-1-2-td2551023.… On Fri, Dec 17, 2010 at 9:04 AM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Hi, > > > What do you think about adding these packages as default in Pharo 1.2: > - ConfigurationOfMocketry > - ConfigurationOfXMLSupport > - ConfigurationOfCryptography (does'nt exist yet, planned to be created in > a local coding-dojo on Tuesday). > > Motivations: > - XMLSupport and Cryptography are often needed to consume web services > - Mocketry because I want to write tests using Mocks and it's easier to > work when tools are in standard Pharo (and then newcomers can see Mocketry > examples). > > > I will update ConfigurationOfPharo 1.2 (beta3 ?) if people agree. > > Cheers, > > Laurent Laffont >

Dec. 17, 2010

Re: [Pharo-project] Issue 1213 in pharo: Unable to type some czech characters

by pharo＠googlecode.com

Updates: Labels: -Milestone-1.2 Comment #20 on issue 1213 by marcus.denker: Unable to type some czech characters http://code.google.com/p/pharo/issues/detail?id=1213 (No comment was entered for this change.)

Dec. 17, 2010