September 2015 - Pharo-users

Re: [Pharo-users] Displaying custom Magritte view on FAMIX model

by Tudor Girba

Hi, Metanool offers you a way to define new properties and edit those. Thus, it works at the FM3 level (which is a meta-model of FAMIX). You seem to want to work directly at FAMIX level. This means that you just have an object, which happens to be a FAMIXClass instance, and want to describe it with Magritte. For example, for adding a Name property, you can add this method: FAMIXClass>>descriptionName <magritteDescription> ^ MAStringDescription new accessor: #name; label: 'Name'; yourself And you get: [image: Inline image 1] [image: Inline image 2] What would you expect to get for declaredType? Cheers, Doru On Mon, Sep 21, 2015 at 5:25 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > Hi, > > I would like to build custom magritte view for a FAMIX model, however > it seems that Fame/Metanool are somehow interfering with it.. > > Imagine a simple model (a class with an attribute): > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > cls := FAMIXClass new name: 'Something'. > > (attr := FAMIXAttribute new) > name: 'myAttribute'; > declaredType: (FAMIXClass new name: 'OtherThing'). > > cls addAttribute: attr. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > now I can open the magritte description > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > attr mooseDescription asMagritteDescription asMagritteMorph openInWindow. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > However this is a meta description, which I don't want... > > So second option was to build it manually; I extract descriptions that > I am interested in.... > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > container := MAContainer new addAll: ({ > attr mooseDescription at: 'name'. > attr mooseDescription at: 'declaredType'. > } collect: #asMagritteDescription). > > (container asMorphOn: attr) openInWindow. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > However the problem with this is, that the declaredType is presented > as TextField, which is not very useful. > > So I'm kind of lost... > > basically what I want to do is to have a MAContainer that contains > both the Attribute's name and #declaredType's name. > > Is this possible? > > Thanks, > Peter > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 21, 2015

Re: [Pharo-users] A keyboard controlled code editor, how difficult would that be?

by Thierry Goubier

Le 21/09/2015 20:57, Stephan Eggermont a Ã©crit : > When experienced (non-smalltalk) developers come to Pharo, they often > complain about the (perceived) lack of keyboard control. Spotter has > made it easy to open new browsers and inspectors, but navigating between > all the open windows is still mostly done with the mouse. > > What would happen if we create an state-full interface, showing code as > cards, and explicitly switch between navigating and editing? > > https://vimeo.com/139960287 > > Drag some methods to the code panel, click on it and start editing. > Esc switches between navigation and editing, when navigating switches > enter between the collapsed and expanded view of a card. The arrow keys > select other cards, and using shift a card can be moved. Interesting. Shows a different side of the code as well, not only keyboard navigation, IMO. Thierry > How much code do we need for that? Well, the prototype fits in 6 columns > on an UHD screen. > > Gofer it > smalltalkhubUser: 'StephanEggermont' project: 'Documentation'; > configurationOf: 'NewUI'; > load. > > CodePanel new openInWindowLabeled: 'CodePanel' > > What needs fixing: navigating over empty columns. > > Stephan > > >

Sept. 21, 2015

Re: [Pharo-users] Problem Loading Roassal 2 development in Pharo 4

by Tudor Girba

I do not think this is possible. The development of Roassal2 happens in Pharo 5. Cheers, Doru On Mon, Sep 21, 2015 at 9:15 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > Hi all, > > I cannot load Roassal2 development in Pharo 4, itâs missing the > GTExampleFinder class (full message below). I can proceed through and still > get a reasonably working version though (I guess without some examples, > have not tried it as I donât need them) > > Would it be possible to fix the development version so that it loads in > Pharo 4? > > > This package depends on the following classes: > GTExampleFinder > You must resolve these dependencies before you will be able to load these > definitions: > RTExampleFinder > gtExampleInstance > class:selector:method:to: > newExample > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD and RyCh labs - Computer Science Department (DCC) - University > of Chile > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 21, 2015

Re: [Pharo-users] A keyboard controlled code editor, how difficult would that be?

by Peter UhnÃ¡k

On Mon, Sep 21, 2015 at 8:57 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > When experienced (non-smalltalk) developers come to Pharo, they often > complain about the (perceived) lack of keyboard control. Spotter has made it > easy to open new browsers and inspectors, but navigating between all the > open windows is still mostly done with the mouse. > At least in Nautilus the problem is more related to inability to break focus out of code pane... because the shortcuts are there, but can't be used when the focus is on code pane. > What would happen if we create an state-full interface, showing code as > cards, and explicitly switch between navigating and editing? > > https://vimeo.com/139960287 > > Drag some methods to the code panel, click on it and start editing. > Esc switches between navigation and editing, when navigating switches enter > between the collapsed and expanded view of a card. The arrow keys select > other cards, and using shift a card can be moved. This is really cool. Because even on my 24" screen I can comfortably have only couple (4) of system browser opened at once (and I am interested only in the method). It would be interesting to integrate it with MessageBrowser and Spotter, so I could (with shift+enter or something) open your card instead of Nautilus. For example I have scoped view of my package and I ctrl+b+n on a selector and it opens cards with the senders. Peter

Sept. 21, 2015

Re: [Pharo-users] Problem Loading Roassal 2 development in Pharo 4

by Stephan Eggermont

On 21-09-15 21:15, Johan Fabry wrote: > Hi all, > > I cannot load Roassal2 development in Pharo 4, itâs missing the GTExampleFinder class (full message below). I can proceed through and still get a reasonably working version though (I guess without some examples, have not tried it as I donât need them) > > Would it be possible to fix the development version so that it loads in Pharo 4? > > > This package depends on the following classes: > GTExampleFinder > You must resolve these dependencies before you will be able to load these definitions: > RTExampleFinder > gtExampleInstance > class:selector:method:to: > newExample In pharo-dev I wrote: Can anyone explain ConfigurationOfRoassal2? Where does that work? stable: spec <symbolicVersion: #'stable'> spec for: #'common' version: '1.11'. spec for: #'pharo4.x' version: '1.13'. spec for: #'pharo3.x' version: '1.6'. development: spec <symbolicVersion: #'development'> spec for: #'common' version: '1.4-baseline'. spec for: #'pharo4.x' version: '1.5-baseline'.

Sept. 21, 2015

Re: [Pharo-users] A keyboard controlled code editor, how difficult would that be?

by Tudor Girba

Very nice experiment. Please, do keep this up. Cheers, Doru On Mon, Sep 21, 2015 at 8:57 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > When experienced (non-smalltalk) developers come to Pharo, they often > complain about the (perceived) lack of keyboard control. Spotter has made > it easy to open new browsers and inspectors, but navigating between all the > open windows is still mostly done with the mouse. > > What would happen if we create an state-full interface, showing code as > cards, and explicitly switch between navigating and editing? > > https://vimeo.com/139960287 > > Drag some methods to the code panel, click on it and start editing. > Esc switches between navigation and editing, when navigating switches > enter between the collapsed and expanded view of a card. The arrow keys > select other cards, and using shift a card can be moved. > > How much code do we need for that? Well, the prototype fits in 6 columns > on an UHD screen. > > Gofer it > smalltalkhubUser: 'StephanEggermont' project: 'Documentation'; > configurationOf: 'NewUI'; > load. > > CodePanel new openInWindowLabeled: 'CodePanel' > > What needs fixing: navigating over empty columns. > > Stephan > > > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 21, 2015

Problem Loading Roassal 2 development in Pharo 4

by Johan Fabry

Hi all, I cannot load Roassal2 development in Pharo 4, itâs missing the GTExampleFinder class (full message below). I can proceed through and still get a reasonably working version though (I guess without some examples, have not tried it as I donât need them) Would it be possible to fix the development version so that it loads in Pharo 4? This package depends on the following classes: GTExampleFinder You must resolve these dependencies before you will be able to load these definitions: RTExampleFinder gtExampleInstance class:selector:method:to: newExample ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD and RyCh labs - Computer Science Department (DCC) - University of Chile

Sept. 21, 2015

Re: [Pharo-users] A keyboard controlled code editor, how difficult would that be?

by Alexandre Bergel

Wow!! This is impressive! Alexandre > On Sep 21, 2015, at 3:57 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > > When experienced (non-smalltalk) developers come to Pharo, they often complain about the (perceived) lack of keyboard control. Spotter has made it easy to open new browsers and inspectors, but navigating between all the open windows is still mostly done with the mouse. > > What would happen if we create an state-full interface, showing code as cards, and explicitly switch between navigating and editing? > > https://vimeo.com/139960287 > > Drag some methods to the code panel, click on it and start editing. > Esc switches between navigation and editing, when navigating switches enter between the collapsed and expanded view of a card. The arrow keys select other cards, and using shift a card can be moved. > > How much code do we need for that? Well, the prototype fits in 6 columns on an UHD screen. > > Gofer it > smalltalkhubUser: 'StephanEggermont' project: 'Documentation'; > configurationOf: 'NewUI'; > load. > > CodePanel new openInWindowLabeled: 'CodePanel' > > What needs fixing: navigating over empty columns. > > Stephan > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 21, 2015

Re: [Pharo-users] A keyboard controlled code editor, how difficult would that be?

by Andrew Glynn

I'm not sure that those developers will ever be happy with Smallltalk. Unless you can do everything in VI and compile on the command line, they feel there's something wrong. On September 21, 2015 08:57:21 PM Stephan Eggermont wrote: > When experienced (non-smalltalk) developers come to Pharo, they often > complain about the (perceived) lack of keyboard control. Spotter has > made it easy to open new browsers and inspectors, but navigating between > all the open windows is still mostly done with the mouse. > > What would happen if we create an state-full interface, showing code as > cards, and explicitly switch between navigating and editing? > > https://vimeo.com/139960287 > > Drag some methods to the code panel, click on it and start editing. > Esc switches between navigation and editing, when navigating switches > enter between the collapsed and expanded view of a card. The arrow keys > select other cards, and using shift a card can be moved. > > How much code do we need for that? Well, the prototype fits in 6 columns > on an UHD screen. > > Gofer it > smalltalkhubUser: 'StephanEggermont' project: 'Documentation'; > configurationOf: 'NewUI'; > load. > > CodePanel new openInWindowLabeled: 'CodePanel' > > What needs fixing: navigating over empty columns. > > Stephan

Sept. 21, 2015

A keyboard controlled code editor, how difficult would that be?

by Stephan Eggermont

When experienced (non-smalltalk) developers come to Pharo, they often complain about the (perceived) lack of keyboard control. Spotter has made it easy to open new browsers and inspectors, but navigating between all the open windows is still mostly done with the mouse. What would happen if we create an state-full interface, showing code as cards, and explicitly switch between navigating and editing? https://vimeo.com/139960287 Drag some methods to the code panel, click on it and start editing. Esc switches between navigation and editing, when navigating switches enter between the collapsed and expanded view of a card. The arrow keys select other cards, and using shift a card can be moved. How much code do we need for that? Well, the prototype fits in 6 columns on an UHD screen. Gofer it smalltalkhubUser: 'StephanEggermont' project: 'Documentation'; configurationOf: 'NewUI'; load. CodePanel new openInWindowLabeled: 'CodePanel' What needs fixing: navigating over empty columns. Stephan

Sept. 21, 2015