September 2015 - Pharo-users

Re: [Pharo-users] Rectangle center rounding

by Peter UhnÃ¡k

On Mon, Sep 21, 2015 at 11:07 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > Any program on that front? > There was no progress on this and I don't think that from our (me and Jan) perspective this is even direction we should go. (Jan is probably enjoying summer so I don't know when or even if he will work on this.) As far as I'm concerned I'm moving towards integer coordinates (because it's nicer) and trying to make things behave in Roassal... ... such as my work on RTDraggableSnapToGrid some time ago. [[[ v := RTView new. s := RTBox new size: 25; color: (Color blue alpha: 0.3). es := s elementsOn: (1 to: 10). v addAll: es. RTGridLayout on: es. es @ RTDraggableSnapToGrid. v ]]] Peter

Sept. 21, 2015

Re: [Pharo-users] Rectangle center rounding

by Alexandre Bergel

Hi! Any program on that front? Alexandre > On Jul 23, 2015, at 10:32 AM, Jan BlizniÄenko <bliznjan(a)fit.cvut.cz> wrote: > > As far as I looked, only two rounding methods are center and aboveCenter > (which has no senders in my image by the way and I do not even see purpose > of it)... all other (like leftCenter) are getting value from mentioned self > center. > > So, the easiest way seems to subclass Rectangle and make something like > Precise/Float/NotRounded/I'mNotVeryGoodAtNaming Rectangle > which will have just these two methods different, so there will be also this > PreciseRectangle which is not rounding down, but original one stays > unchanged. > > However, the rounding seems to me like an extension/addition/subtype of > general rectangle and I think that it should not be default behavior of > something called just Rectangle, it should be more like Rectangle (not > rounded) with subclass IntegerRectangle or something like that. I know, > there are many senders right now which are dependent on the rounding, but I > just think it should not be like that, or should it? > > Jan > > > abergel wrote >> Maybe we can introduce a new rectangle class. > > > > > > -- > View this message in context: http://forum.world.st/Rectangle-center-rounding-tp4837980p4838853.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 21, 2015

Re: [Pharo-users] How to read the first line of content from a Playground?

by Esteban Lorenzano

> On 21 Sep 2015, at 21:54, phil(a)highoctane.be wrote: > > In the old workspace it was possible to ask for the first line of contents (to show it in a list). the first line of contents of what? can you share a snippet so I can understand your problem? cheers! Esteban > > With a playground it seems harder... Lots of entries in there. > > Is there any short way to get that done? > > TIA > Phil

Sept. 21, 2015

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

by Johan Fabry

I understand the problem, but could you update the development version so that it loads the latest version that does work in Pharo 4? Switching to Pharo 5 is not an option for me right now, and I fear the stable version of Roassal2 is much too old to be useful for me. > On Sep 21, 2015, at 16:38, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > Doru is right. Roassal2 depends on GT-Inspector to visualize views and the example finding. > Currently, GT-Inspector does not load in Pharo 4. Apparently due to Rubric. > > Apparently, time is to move to Pharo 5. > > Alexandre > >> On Sep 21, 2015, at 4:25 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> >> 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" > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > ---> 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 phil＠highoctane.be

On Mon, Sep 21, 2015 at 9:32 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > On Mon, Sep 21, 2015 at 9:05 PM, Andrew Glynn <aglynn42(a)gmail.com> wrote: > > 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. > > Perhaps you need to widen your perspective. > Just because there are fundamentalists on one side doesn't mean that > you have to became fundamentalist on the other side to balance it > out... > > Pharo is full of shortcuts, because they are very useful. (And if you > are not using them you are only hurting yourself.) > The point is not to take everything to extreme, but to see what's > valuable and explore. > The main issue is that the shortcuts aren't consistent across platforms (or sometimes just conflict or do not work). Like in Pharo 5/Windows, some things are okay with Ctl-key, and not Alt-key (they were in the past). And some Alt-key works in specific contexts. Or in Linux, some things are giving problems. I like the new $r command | $r control | ... scheme. Much cleaner. What is not nice is that GTInspector isn't picking up the new combos as it displays the KM class and not the shortcut. Back to keyboard, the TilingWindowManager (working back on that atm) has potential. I am a vim and tmux user, and Ctl-W hjkl is really useful, as is Ctl-PgUp/PgDown, Or Ctl-z etc. One of the features I am going to add is that Ctl-W hjkl window selection as it is too good to pass. I am mousing a lot in Pharo (even if I know about the shortcuts). It is nice to be able to search around by point and click. Now, we need to rationalize some wordings, especially "Users of X", "References to X". Confuses people. With such keyboard movements, the desktop manager, a good TWM, and spotter, that's a great thing. Playground needs to be integrated closer with spotter. I want to launch a playground from there, using what I typed as a command (yes, I know there were discussions for/against that one. Still, I find myself retyping into Playground what typed into Spotter. Frustrating.) There is a lot of power in Pharo keybindings, we need to streamline this. What an awesome tool we have here! Excited by Pharo more than ever. Phil > > Peter > > >

Sept. 21, 2015

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

by Peter UhnÃ¡k

Hmm, > 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. I thought that I don't need to describe FAMIX models with magritte, because it is autogenerated from <MSEProperty: #someSelector type: #SomeClass>. So I must describe it myself? > What would you expect to get for declaredType? Well the descriptions of it... so in a single form I would have all the descriptions. If I do it with my own descriptions... e.g. FAMIXBehavioralEntity>>descriptionDeclaredType <magritteDescription> ^ MAToOneRelationDescription new selectorAccessor: #declaredType; label: 'Declared Type'; yourself Then I at least get buttons for it (I didn't manage to achieve this with the autogenerated descriptions) â However I would still like the option to specify whether I want a new window to show up or let it be embedded in a single form. I managed to track down something like MAInternalEditorMorph which maybe should do what I want but if I apply it it has no effect... so maybe it's broken or I don't know how to use it. Thanks, Peter On Mon, Sep 21, 2015 at 9:31 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > 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

How to read the first line of content from a Playground?

by phil＠highoctane.be

In the old workspace it was possible to ask for the first line of contents (to show it in a list). With a playground it seems harder... Lots of entries in there. Is there any short way to get that done? TIA Phil

Sept. 21, 2015

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

by Alexandre Bergel

Doru is right. Roassal2 depends on GT-Inspector to visualize views and the example finding. Currently, GT-Inspector does not load in Pharo 4. Apparently due to Rubric. Apparently, time is to move to Pharo 5. Alexandre > On Sep 21, 2015, at 4:25 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > 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" -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 21, 2015

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

by Peter UhnÃ¡k

> I do not think this is possible. The development of Roassal2 happens in Pharo 5. It's missing GTExampleFinder even in Pharo5, because the development happens in Moose ;) (Unless Pharo 5 has been updated in the meantime and the problem fixed itself.) In any case, this just breaks Roassal examples, so if you continue with the installation it should work (in theory). http://forum.world.st/Roassal-where-is-GTExampleFinder-td4851101.html Peter

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 9:05 PM, Andrew Glynn <aglynn42(a)gmail.com> wrote: > 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. Perhaps you need to widen your perspective. Just because there are fundamentalists on one side doesn't mean that you have to became fundamentalist on the other side to balance it out... Pharo is full of shortcuts, because they are very useful. (And if you are not using them you are only hurting yourself.) The point is not to take everything to extreme, but to see what's valuable and explore. Peter

Sept. 21, 2015