- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] need some testers: 15619 cleanup TextEditors shortcut definition

by stepharo

Since we did not port yet spec to use Rubric all the text pane of tools made with spec should use the textEditor. Le 15/8/15 19:58, Nicolai Hess a Ã©crit : > Now I moved all (known?) shortcut definitions from > TextEditor/SmalltalkEditor action-/cmdmap to Keymappings > <keymap>pragma definitions > > slice in inbox for issue 15619 > Postscript: KMRepository reset. > > need some testers. > please report back, what editor (TextEditor/SmalltalkEditor) and your > platform (windows/linux/mac) and the shortcut/keycombination that > did not work (or does work but not as expected). > > This is only for PluggableTextMorph based TextMorphs, > (Not Rubric -> No change for Playground or Nautilus). > > > For testing: > PluggableTextMorph with TextEditor as a editor: > > (Smalltalk ui theme builder newBasicTextEditorFor: Morph getText: > #comment setText: nil) openInWindow. > > > PluggableTextMorph with SmalltalkEditor as a editor: > (Smalltalk ui theme builder newTextEditorFor: (Morph>>#drawOn:) > getText: #sourceCode setText: nil) openInWindow. > > Many shortcuts should work like before. some changes: > some short cuts actions had multiple shortcuts on windows/linux: > alt+key from TextEditors keymap > ctrl+key from the <keymap>-pragma > -> only one should be working now. > > Ctrl+space does not work in current pharo windows vm > escape may not work for all actions > > You can browse all defined shortcuts in the Keymap Browser > (Worldmenu -> System -> Keymap Browser) > > thanks

Aug. 15, 2015

Re: [Pharo-dev] we are running dependencies breaking sprints....

by stepharo

This is easy we are looking at dependencies using the dependency analyzer (available in the catalog) and looking at how to reduce dependencies. Often it is creating a separate package, providing an extension hook... Guille and Christophe started to add fogbugz entries for a first set of problems. Stef Le 15/8/15 16:32, Dimitris Chloupis a Ã©crit : > A "how to help with Pharo Bootstrap" article could help us help you ;) > > On Sat, Aug 15, 2015 at 4:49 PM stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > I forgot to mention that people can help since we added a tahe > pharo-bootstrap. > > Stef > > Le 15/8/15 10:53, Tudor Girba a Ã©crit : >> This is exciting. Thanks a lot for this effort! >> >> Doru >> >> On Sat, Aug 15, 2015 at 10:50 AM, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> Hi guys >> >> just to let you know that we run a dependencies breaking >> sprint yesterday and it was great. >> We will redo one or two. >> Our goal is to minimise the dependencies of adding Monticello >> to the pharo bootstrap. >> What I can tell you is that having a bootstrap is bringing an >> ***AMAZING*** level of cleaner design. >> I suspected it. But when we see the real cases this is >> obvious and really important. >> I will really open a complete new world for Pharo in terms of >> modularity (of course it will take time >> but this is really really cool). >> >> Stef >> >> >> >> >> -- >> www.tudorgirba.com <http://www.tudorgirba.com> >> >> "Every thing has its own flow" >

Aug. 15, 2015

Re: [Pharo-dev] FastTable in Pharo4?

by Esteban Lorenzano

yes just take the configuration from estebanlm/FastTable and load it :) Esteban > On 15 Aug 2015, at 21:05, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi, > > is it possible to load FastTable in Pharo 4? > > Uko >

Aug. 15, 2015

FastTable in Pharo4?

by Yuriy Tymchuk

Hi, is it possible to load FastTable in Pharo 4? Uko

Aug. 15, 2015

Re: [Pharo-dev] Unified property API for code.

by Marcus Denker

> On 15 Aug 2015, at 19:44, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > Can you give a little example of usecase to illustrate how this will be useful please? :) > The reason why I do that now is that I want to be able to put Meta Links on these variables. This means, to âhookâ into all accesses of x in Point, I want to be able to do: metaLink := MetaLink new metaObject: Counter; selector: #inc. (Point slotNamed: #x) link: metaLink. ==> on next call, any method that references the ivar x will be re-compiled just before execution with the Link taken into account. Which means it will insert âCounter incâ before the access. This works, too, on Globals. E.g. you want to #halt next time someone reads the global reference Object? Just do Object binding link: (MetaLink new metaObject: Halt; selector: #now) Lots of possibilitiesâ¦ and even for the raw properties I am sure people can find uses. E.g. the Quality assist system actually annotates methods using properties instead of having internal private data structures. It could attach information to *Variables*, too. Maybe other uses are possible, too. Could one store what we statically know about the classes possible of a variable? Marcus

Aug. 15, 2015

need some testers: 15619 cleanup TextEditors shortcut definition

by Nicolai Hess

Now I moved all (known?) shortcut definitions from TextEditor/SmalltalkEditor action-/cmdmap to Keymappings <keymap>pragma definitions slice in inbox for issue 15619 Postscript: KMRepository reset. need some testers. please report back, what editor (TextEditor/SmalltalkEditor) and your platform (windows/linux/mac) and the shortcut/keycombination that did not work (or does work but not as expected). This is only for PluggableTextMorph based TextMorphs, (Not Rubric -> No change for Playground or Nautilus). For testing: PluggableTextMorph with TextEditor as a editor: (Smalltalk ui theme builder newBasicTextEditorFor: Morph getText: #comment setText: nil) openInWindow. PluggableTextMorph with SmalltalkEditor as a editor: (Smalltalk ui theme builder newTextEditorFor: (Morph>>#drawOn:) getText: #sourceCode setText: nil) openInWindow. Many shortcuts should work like before. some changes: some short cuts actions had multiple shortcuts on windows/linux: alt+key from TextEditors keymap ctrl+key from the <keymap>-pragma -> only one should be working now. Ctrl+space does not work in current pharo windows vm escape may not work for all actions You can browse all defined shortcuts in the Keymap Browser (Worldmenu -> System -> Keymap Browser) thanks

Aug. 15, 2015

Re: [Pharo-dev] Unified property API for code.

by Cyril Ferlicot

Can you give a little example of usecase to illustrate how this will be useful please? :) -- Cyril Le samedi 15 aoÃ»t 2015, Marcus Denker <marcus.denker(a)inria.fr> a Ã©crit : > > On 15 Aug 2015, at 18:38, Marcus Denker <marcus.denker(a)inria.fr > <javascript:_e(%7B%7D,'cvml','marcus.denker(a)inria.fr');>> wrote: > > > On 15 Aug 2015, at 16:48, Marcus Denker <marcus.denker(a)inria.fr > <javascript:_e(%7B%7D,'cvml','marcus.denker(a)inria.fr');>> wrote: > > > On 15 Aug 2015, at 12:56, Marcus Denker <marcus.denker(a)inria.fr > <javascript:_e(%7B%7D,'cvml','marcus.denker(a)inria.fr');>> wrote: > > Ok, what I will do first is to add the API to Variables + Packages using > the propertyAt: format. > > > Done for Globals and ClassVariables: > > https://pharo.fogbugz.com/f/cases/16223/Property-API-for-Globals > > > > in Pharo5 #234. > > TODO > -> properties for Instance Variables > > > https://pharo.fogbugz.com/f/cases/16224/Property-API-for-Slots > > This means that we can now annotate all Instance Variables (Slots) in the > system. E.g. > > > (Point slotNamed: #x) propertyAt: #test put: 5 > > > Marcus > > -- Cheers Cyril Ferlicot

Aug. 15, 2015

Re: [Pharo-dev] Unified property API for code.

by Marcus Denker

> On 15 Aug 2015, at 18:38, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 15 Aug 2015, at 16:48, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> >>> On 15 Aug 2015, at 12:56, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >>> >>> Ok, what I will do first is to add the API to Variables + Packages using the propertyAt: format. >>> >> >> Done for Globals and ClassVariables: >> >> https://pharo.fogbugz.com/f/cases/16223/Property-API-for-Globals <https://pharo.fogbugz.com/f/cases/16223/Property-API-for-Globals> >> >> > > in Pharo5 #234. > > TODO > -> properties for Instance Variables > https://pharo.fogbugz.com/f/cases/16224/Property-API-for-Slots <https://pharo.fogbugz.com/f/cases/16224/Property-API-for-Slots> This means that we can now annotate all Instance Variables (Slots) in the system. E.g. (Point slotNamed: #x) propertyAt: #test put: 5 Marcus

Aug. 15, 2015

Re: [Pharo-dev] Unified property API for code.

by Marcus Denker

> On 15 Aug 2015, at 16:48, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > >> On 15 Aug 2015, at 12:56, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: >> >> Ok, what I will do first is to add the API to Variables + Packages using the propertyAt: format. >> > > Done for Globals and ClassVariables: > > https://pharo.fogbugz.com/f/cases/16223/Property-API-for-Globals <https://pharo.fogbugz.com/f/cases/16223/Property-API-for-Globals> > > in Pharo5 #234. TODO -> properties for Instance Variables -> change #link: to use properties instead of Variable wrappers -> clean up Variable Wrappers (for just adding state) -> implement code generation for MetaLinks on Variables. (same implementation idea as for RB AST Nodes can be used now). Marcus

Aug. 15, 2015

[pharo-project/pharo-core]

by GitHub

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

Aug. 15, 2015