- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] TWM - Shortcuts - Fixed.

by Laurent

Oups, sorry, I want to say it is actually WORKING for me (I'm not totally awake :). thanks a lot ! Laurent Le jeu. 11 sept. 2014 Ã 10:40, Laurent <laurent.laffont(a)gmail.com> a Ã©crit : > Hi Phil, > > not working for me, yes really frustrating. Did not manage to fix it > last time I tried :( > > Laurent > > Le mer. 10 sept. 2014 Ã 16:48, phil(a)highoctane.be > <phil(a)highoctane.be> a Ã©crit : >> I was frustrated by being unable to have the Tiling Window Manager >> shortcuts not working properly in 3.0 >> >> This is now fixed by registering the category as a global one. >> >> Sean, Laurent, is this working for you? >> >> Phil

Sept. 11, 2014

Re: [Pharo-dev] TWM - Shortcuts - Fixed.

by Laurent

Hi Phil, not working for me, yes really frustrating. Did not manage to fix it last time I tried :( Laurent Le mer. 10 sept. 2014 Ã 16:48, phil(a)highoctane.be <phil(a)highoctane.be> a Ã©crit : > I was frustrated by being unable to have the Tiling Window Manager > shortcuts not working properly in 3.0 > > This is now fixed by registering the category as a global one. > > Sean, Laurent, is this working for you? > > Phil

Sept. 11, 2014

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/40218 Home: https://github.com/pharo-project/pharo-core

Sept. 11, 2014

[pharo-project/pharo-core] 4fd357: 40218

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 4fd35771a9b42416a5d42e5d89e85fc35fd77a2f https://github.com/pharo-project/pharo-core/commit/4fd35771a9b42416a5d42e5d… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-09-11 (Thu, 11 Sep 2014) Changed paths: M Gofer-Core.package/Gofer.class/class/private/upgrade.st M Gofer-Core.package/GoferLoad.class/instance/private/addResolved_.st M Gofer-Core.package/GoferRevert.class/instance/private/referenceFor_.st M MonticelloGUI.package/MCSaveVersionDialog.class/instance/morphic ui/setDefaultFocus.st M OpalCompiler-Core.package/OCUndeclaredVariableWarning.class/instance/correcting/declareTempAndPaste_.st R Polymorph-Widgets.package/TextEditorDialogWindow.class/class/accessing/autoAccept.st R Polymorph-Widgets.package/TextEditorDialogWindow.class/class/accessing/autoAccept_.st R Polymorph-Widgets.package/TextEditorDialogWindow.class/class/settings/settingsOn_.st R Polymorph-Widgets.package/TextEditorDialogWindow.class/instance/accessing/autoAccept.st M Polymorph-Widgets.package/TextEditorDialogWindow.class/instance/accessing/entryText_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script218.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40218.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40218 13205 Temporary variable declaration in blocks https://pharo.fogbugz.com/f/cases/13205 13989 Temporary variables not read and writen in Gofer-Core https://pharo.fogbugz.com/f/cases/13989 13837 remove TextEditorDialogWindow autoaccept preference https://pharo.fogbugz.com/f/cases/13837 13987 remove empty package Settings-Tools https://pharo.fogbugz.com/f/cases/13987 http://files.pharo.org/image/40/40218.zip

Sept. 11, 2014

Re: [Pharo-dev] Last Pharo VM on mac os x 10.6.8

by Stephan Eggermont

Just copy the libcairo.2.dylib (in Contents/MacOS/Plugins when you do Show Package Contents on the vm app) from the 18 september 2013 vm. Stephan

Sept. 10, 2014

Re: [Pharo-dev] Class names and special names for special things.

by phil＠highoctane.be

Something along the lines of: Proc register pattern: 'open {parm}' action: [ :parm | <do something with parm> ]. and we register a couple snippets who get recognized. Or we can go the full interpreter route. Ah, we're back to Tcl! http://wiki.tcl.tk/463 Phil On Wed, Sep 10, 2014 at 11:29 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > no my idea is to not affect Pharo internals at all, and instead the parser > maps to regular existing pharo messages of existing pharo classes. No need > to create new classes and new method just create your pharo shortcut and > map it to a specific method. I am also interested to mapping several > shortcuts to a single method so you can send the message different ways. > Probably they end up inside a dictionary or something. > > The same way you have shortcuts for files. You dont need to create a new > folder for them you just create the shortcut directly and like shortcuts > can mix with other files, so pharo shortcuts should mix with pharo code > without having to switch syntax. Let the secondary parser parse the > shortucts to pharo syntax and then let pharo do its own thing. > > By the way the idea of petitparser is probably one of the best, I have > only played with regular expression but this will need something as > powerful as pettitparser. I have read the chapter in Deep Into Pharo , its > time to put it to good use :) > > On Wed, Sep 10, 2014 at 6:42 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> Alternative would be that each open, print etc is an object of class >> Command with some methods. >> Le 10 sept. 2014 17:32, "phil(a)highoctane.be" <phil(a)highoctane.be> a >> Ã©crit : >> >> A >>> Le 10 sept. 2014 17:21, "kilon alios" <kilon.alios(a)gmail.com> a Ã©crit : >>> > >>> > how about introducing a secondary parser on top of the code editor >>> that you can enable disable at will and can create "code shortcuts" using >>> such symbols ? it will then store them as regular pharo syntax without >>> affecting the pharo system. Its an idea I am thinking playing with but not >>> so much for special class names but rather omitting the class names >>> altogether and create shorter version of calling a method that is more >>> English like, like : >>> > >>> > open "mydoc.pdf" in documents. >>> > display pdf. >>> > go to page 4. >>> > print page >>> >>> I would do that with a dedicated petit parser grammar. >>> >>> As for highlighthing the styler stuff is unknown territory for me. >>> >>> In the GT doc / pillar stuff, I saw Interesting stuff going on on Doru's >>> blog. >>> >>> Phil >>> > >>> > >>> > On Wed, Sep 10, 2014 at 6:13 PM, phil(a)highoctane.be < >>> phil(a)highoctane.be> wrote: >>> >> >>> >> Of course. But there are some other things that are available. >>> >> >>> >> Â§, `, ? comes to mind. >>> >> >>> >> Phil >>> >> >>> >> >>> >> >>> >> >>> >> On Wed, Sep 10, 2014 at 4:59 PM, Marcus Denker < >>> marcus.denker(a)inria.fr> wrote: >>> >>> >>> >>> >>> >>> On 10 Sep 2014, at 16:38, phil(a)highoctane.be wrote: >>> >>> >>> >>> > I was playing around with the idea of using stuff like in jQuery, >>> where we do have the '$' function that would do a lot of things. >>> >>> > >>> >>> > But one cannot create such elements as >>> >>> > >>> >>> > SlotClassBuilder>>validateClassName >>> >>> > "Validate the new class name. Raise warning if invalid." >>> >>> > >>> >>> > name >>> >>> > detect: [ :c | (c isAlphaNumeric or: [ c = $_ ]) not >>> ] >>> >>> > ifFound: [ :c | InvalidGlobalName signal: 'Invalid >>> character: ''' , c printString , '''' for: name ]. >>> >>> > name first canBeGlobalVarInitial >>> >>> > ifFalse: [ InvalidGlobalName signal: 'Class name >>> does not start with a valid Global Var Initial' for: name ] >>> >>> > >>> >>> > doesn't let us. >>> >>> > >>> >>> > Is there a reason for that (ok, we have $ for chars, and #, ... >>> and other things but still). >>> >>> > >>> >>> >>> >>> The problem is that $ is part of the smalltalk grammar for symbols, >>> $ can not be a variable name. >>> >>> >>> >>> $asdasd >>> >>> >>> >>> is parsed as a message send to the character a, for example. >>> >>> >>> >>> Marcus >>> >> >>> >> >>> > >>> >> >

Sept. 10, 2014

Re: [Pharo-dev] Class names and special names for special things.

by kilon alios

no my idea is to not affect Pharo internals at all, and instead the parser maps to regular existing pharo messages of existing pharo classes. No need to create new classes and new method just create your pharo shortcut and map it to a specific method. I am also interested to mapping several shortcuts to a single method so you can send the message different ways. Probably they end up inside a dictionary or something. The same way you have shortcuts for files. You dont need to create a new folder for them you just create the shortcut directly and like shortcuts can mix with other files, so pharo shortcuts should mix with pharo code without having to switch syntax. Let the secondary parser parse the shortucts to pharo syntax and then let pharo do its own thing. By the way the idea of petitparser is probably one of the best, I have only played with regular expression but this will need something as powerful as pettitparser. I have read the chapter in Deep Into Pharo , its time to put it to good use :) On Wed, Sep 10, 2014 at 6:42 PM, phil(a)highoctane.be <phil(a)highoctane.be> wrote: > Alternative would be that each open, print etc is an object of class > Command with some methods. > Le 10 sept. 2014 17:32, "phil(a)highoctane.be" <phil(a)highoctane.be> a Ã©crit > : > > A >> Le 10 sept. 2014 17:21, "kilon alios" <kilon.alios(a)gmail.com> a Ã©crit : >> > >> > how about introducing a secondary parser on top of the code editor that >> you can enable disable at will and can create "code shortcuts" using such >> symbols ? it will then store them as regular pharo syntax without affecting >> the pharo system. Its an idea I am thinking playing with but not so much >> for special class names but rather omitting the class names altogether and >> create shorter version of calling a method that is more English like, like : >> > >> > open "mydoc.pdf" in documents. >> > display pdf. >> > go to page 4. >> > print page >> >> I would do that with a dedicated petit parser grammar. >> >> As for highlighthing the styler stuff is unknown territory for me. >> >> In the GT doc / pillar stuff, I saw Interesting stuff going on on Doru's >> blog. >> >> Phil >> > >> > >> > On Wed, Sep 10, 2014 at 6:13 PM, phil(a)highoctane.be <phil(a)highoctane.be> >> wrote: >> >> >> >> Of course. But there are some other things that are available. >> >> >> >> Â§, `, ? comes to mind. >> >> >> >> Phil >> >> >> >> >> >> >> >> >> >> On Wed, Sep 10, 2014 at 4:59 PM, Marcus Denker <marcus.denker(a)inria.fr> >> wrote: >> >>> >> >>> >> >>> On 10 Sep 2014, at 16:38, phil(a)highoctane.be wrote: >> >>> >> >>> > I was playing around with the idea of using stuff like in jQuery, >> where we do have the '$' function that would do a lot of things. >> >>> > >> >>> > But one cannot create such elements as >> >>> > >> >>> > SlotClassBuilder>>validateClassName >> >>> > "Validate the new class name. Raise warning if invalid." >> >>> > >> >>> > name >> >>> > detect: [ :c | (c isAlphaNumeric or: [ c = $_ ]) not ] >> >>> > ifFound: [ :c | InvalidGlobalName signal: 'Invalid >> character: ''' , c printString , '''' for: name ]. >> >>> > name first canBeGlobalVarInitial >> >>> > ifFalse: [ InvalidGlobalName signal: 'Class name does >> not start with a valid Global Var Initial' for: name ] >> >>> > >> >>> > doesn't let us. >> >>> > >> >>> > Is there a reason for that (ok, we have $ for chars, and #, ... and >> other things but still). >> >>> > >> >>> >> >>> The problem is that $ is part of the smalltalk grammar for symbols, $ >> can not be a variable name. >> >>> >> >>> $asdasd >> >>> >> >>> is parsed as a message send to the character a, for example. >> >>> >> >>> Marcus >> >> >> >> >> > >> >

Sept. 10, 2014

Re: [Pharo-dev] PharoLauncher mac download not the latest version

by kilon alios

will do, my pleasure On Wed, Sep 10, 2014 at 7:30 PM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > On Wed, Sep 10, 2014 at 5:13 PM, kilon alios <kilon.alios(a)gmail.com> > wrote: > > I could do it, if you want me to include specific version from packages > . Or > > if you want some versioning scheme. For example what version you want > this > > stable release to be ? > > > 0.2.0 (totally random). I'm waiting for input from the Pharo board > before releasing 1.0. > > > We keep the bleeding edge for latest stuff like my > > progress bar and as soon as things work without problem we integrate them > > into the next version ? > > > yes > > > You have any guidelines you want me to follow ? > > use the workflow of versionner. > > Thank you Kilon > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill > >

Sept. 10, 2014

Re: [Pharo-dev] PharoLauncher mac download not the latest version

by Damien Cassou

On Wed, Sep 10, 2014 at 5:13 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > I could do it, if you want me to include specific version from packages . Or > if you want some versioning scheme. For example what version you want this > stable release to be ? 0.2.0 (totally random). I'm waiting for input from the Pharo board before releasing 1.0. > We keep the bleeding edge for latest stuff like my > progress bar and as soon as things work without problem we integrate them > into the next version ? yes > You have any guidelines you want me to follow ? use the workflow of versionner. Thank you Kilon -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Sept. 10, 2014

Re: [Pharo-dev] Class names and special names for special things.

by phil＠highoctane.be

Alternative would be that each open, print etc is an object of class Command with some methods. Le 10 sept. 2014 17:32, "phil(a)highoctane.be" <phil(a)highoctane.be> a Ã©crit : > A > Le 10 sept. 2014 17:21, "kilon alios" <kilon.alios(a)gmail.com> a Ã©crit : > > > > how about introducing a secondary parser on top of the code editor that > you can enable disable at will and can create "code shortcuts" using such > symbols ? it will then store them as regular pharo syntax without affecting > the pharo system. Its an idea I am thinking playing with but not so much > for special class names but rather omitting the class names altogether and > create shorter version of calling a method that is more English like, like : > > > > open "mydoc.pdf" in documents. > > display pdf. > > go to page 4. > > print page > > I would do that with a dedicated petit parser grammar. > > As for highlighthing the styler stuff is unknown territory for me. > > In the GT doc / pillar stuff, I saw Interesting stuff going on on Doru's > blog. > > Phil > > > > > > On Wed, Sep 10, 2014 at 6:13 PM, phil(a)highoctane.be <phil(a)highoctane.be> > wrote: > >> > >> Of course. But there are some other things that are available. > >> > >> Â§, `, ? comes to mind. > >> > >> Phil > >> > >> > >> > >> > >> On Wed, Sep 10, 2014 at 4:59 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >>> > >>> > >>> On 10 Sep 2014, at 16:38, phil(a)highoctane.be wrote: > >>> > >>> > I was playing around with the idea of using stuff like in jQuery, > where we do have the '$' function that would do a lot of things. > >>> > > >>> > But one cannot create such elements as > >>> > > >>> > SlotClassBuilder>>validateClassName > >>> > "Validate the new class name. Raise warning if invalid." > >>> > > >>> > name > >>> > detect: [ :c | (c isAlphaNumeric or: [ c = $_ ]) not ] > >>> > ifFound: [ :c | InvalidGlobalName signal: 'Invalid > character: ''' , c printString , '''' for: name ]. > >>> > name first canBeGlobalVarInitial > >>> > ifFalse: [ InvalidGlobalName signal: 'Class name does > not start with a valid Global Var Initial' for: name ] > >>> > > >>> > doesn't let us. > >>> > > >>> > Is there a reason for that (ok, we have $ for chars, and #, ... and > other things but still). > >>> > > >>> > >>> The problem is that $ is part of the smalltalk grammar for symbols, $ > can not be a variable name. > >>> > >>> $asdasd > >>> > >>> is parsed as a message send to the character a, for example. > >>> > >>> Marcus > >> > >> > > >

Sept. 10, 2014