July 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Number is not accepted by UI

by Esteban A. Maringolo

You can only put the minus sign ("-") before a literal number. Ej -12, - 4.4, -2/3, etc. But not in front of any other "non number" object (from the parser point of view): Ej: - #() size "only numbers may be negated" What you want to do can be performed sending the message #negated to the object returned by #width. So #negatedWidth would be: negatedWidth: ^self width negated Regards! Esteban A. Maringolo 2014-07-15 19:16 GMT-03:00 Verkoster Info <info(a)derverkoster.de>: > Hi, > > I am using latest Pharo 3.0 + vm. > > I have a method width with > width > > ^ 115 * self ratio. > in my understanding it returns a Number. > > When I try to create a method > negatedWidth > > ^ - (self width). > > the UI tells me that only Numbers may be negated. I am not able to save the > method. Am I on a wrong path or should that work and if how can I avoid the > UI error message? > > Regards > > Max >

July 15, 2014

Number is not accepted by UI

by Verkoster Info

Hi, I am using latest Pharo 3.0 + vm. I have a method width with width ^ 115 * self ratio. in my understanding it returns a Number. When I try to create a method negatedWidth ^ - (self width). the UI tells me that only Numbers may be negated. I am not able to save the method. Am I on a wrong path or should that work and if how can I avoid the UI error message? Regards Max

July 15, 2014

export roassal views

by rosariosm

Hi, I have the following problem when i try to export a view into a png file. I use a RTMapBuilder as an example: b := RTMapBuilder new. b countries: RTMapBuilder countries. b view canvas buildMorph *extent: view view canvas camera encompassingRectangle extent ;* exportAsPNG. if i don't specify the rectangle extent (bold line), i can export without problem but i cant see the complete image. on the other hand, if a specify the rectangle extent, an error occurs. see both examples: 1) without extent <http://forum.world.st/file/n4767944/prueba2.png> 2) with extent <http://forum.world.st/file/n4767944/prueba.png> Anyone knows what is happenning?? Thanks, Rosario -- View this message in context: http://forum.world.st/export-roassal-views-tp4767944.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 15, 2014

Re: [Pharo-users] Refactoring project moving forward :)

by kilon alios

"nice" is understatement for anyone doing debugger coding with pharo . The lack of refactoring tools was a main reason I am not coding solely inside the Debugger so its definitely great news. My thought about Pharo is two sided one "Modularisation" and "Documentation" . I can think of no more important coding concepts. In the case of refactoring tools, it would be nice if refactoring tools could define a common "protocol" that any IDE tool could use to take advantage for them, so one would not need to hard code them inside the individual tools. Maybe that is already possible to an extend I have not looked into the code. If memory serves me correctly Debugger was modularised separating its GUI side from its core model. Personally I find Pharo extremely powerful when it comes to refactoring already. The one thing I would change is make the menus more intelligent, right now you can do illegal actions on selections for example I can inspect part of a message which of course it returns an error, it would be nice if the menu entries were disabled , grey out or removed in case of a bad selection, or ideally auto-correct the selection so the menu command can work. On Tue, Jul 15, 2014 at 5:17 PM, Ben Coman <btc(a)openinworld.com> wrote: > Mark Rizun wrote: > >> Hi, everyone! >> >> The project is developing: small changes, enhancements and fixes are made. >> You can read about it on my blog <http://myfuncoding.blogspot.com> . >> Everything is (or will be) included in recent versions of Pharo40. >> Please be free to introduce your thoughts and ideas about what should be >> done, or maybe what shouldn't. >> So, feedback is welcome. >> >> Best, >> Mark >> >> >> >> -- >> View this message in context: http://forum.world.st/ >> Refactoring-project-moving-forward-tp4767798.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >> >> > Didn't quite until I read the blog. Having refactoring in the debugger > will be nice. > cheers -ben > >

July 15, 2014

Re: [Pharo-users] I've raised a bug that the Pharo website has a missing video

by stepharo

> FYI - I've raised a bug that the pharo website doesn't have a video showing > how to report bugs anymore. > > 13553 - Reporting issues video on Pharo website reports "Does not exist" Yes we saw that and we fixed it. We do not have the video and we may redo one in the future for now there is a description. > > Not sure if it's right to raise an issue - but thought it made sense (and > given I can't watch the video... ;) > > Tim > > > > -- > View this message in context: http://forum.world.st/I-ve-raised-a-bug-that-the-Pharo-website-has-a-missin… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

July 15, 2014

Re: [Pharo-users] Refactoring project moving forward :)

by Ben Coman

Mark Rizun wrote: > Hi, everyone! > > The project is developing: small changes, enhancements and fixes are made. > You can read about it on my blog <http://myfuncoding.blogspot.com> . > Everything is (or will be) included in recent versions of Pharo40. > Please be free to introduce your thoughts and ideas about what should be > done, or maybe what shouldn't. > So, feedback is welcome. > > Best, > Mark > > > > -- > View this message in context: http://forum.world.st/Refactoring-project-moving-forward-tp4767798.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > > > Didn't quite until I read the blog. Having refactoring in the debugger will be nice. cheers -ben

July 15, 2014

Re: [Pharo-users] Roassal2 Composite Shape

by Alexandre Bergel

Thanks Ben for your nice words Alexandre > On 15 Jul 2014, at 08:09, Ben Coman <btc(a)openInWorld.com> wrote: > > Peter UhnÃ¡k wrote: >> >> Well in the long run I will probably need much more shapes that are currently present so I will probably end up making both TRShape and RTShape anyway. As far as contribution goes, I'd be happy to contribute but I'm still quite new to both Pharo and Smalltalk so I'm quite skeptical about the code quality. >> >> I've actually already made both shapes for rounded box but it will need some testing first; so I'll keep you posted. >> >> Peter > > Alexandre was always receptive of my rough contributions, and I learnt a lot about improving code quality from him. So I'd encourage you to give it a go. > cheers -ben > >> >> >>> On Mon, Jul 14, 2014 at 10:47 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Indeed, Roassal does not have a rectangle with rounded corner. Having it in Roassal means you need a new TRShape and a new RTShape. >>> >>> I could easily do the RTShape. But we need the TRShape first. Do you feel like doing it? This will be a valuable addition to Roassal. >>> >>> Cheers, >>> Alexandre >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>>> On Jul 13, 2014, at 9:57 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>> >>>> Thank you, the example now works. However as I've mentioned in >>>> previous post I'm not sure about the rest of the shapes posted in the >>>> attachment. E.g. I haven't seen any notion of "box with rounded >>>> corners". I could compose it from four RTArc nad four RTLine but it >>>> seems to me overly complex compared to creating new Trachert/Roassal >>>> classes. The same would go for the other shapes. What are your >>>> thoughts/recommendations on that? >>>> >>>> Peter >>>> >>>> On Sun, Jul 13, 2014 at 3:25 PM, Alexandre Bergel >>>> <alexandre.bergel(a)me.com> wrote: >>>>> Sorry, the version was not properly saved in SmalltalkHub. If you update Roassal2 and Trachel, you should be able to execute the code snippet Iâve sent you. Maybe you want to add âv openâ at the end. If you are using GTInspector, this is not necessary. >>>>> >>>>> As far as I understand your description of the problem, you do not need to create your own shape. >>>>> >>>>> Let me know how it goes. >>>>> >>>>> Cheers, >>>>> Alexandre >>>>> >>>>> >>>>> On Jul 13, 2014, at 10:38 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>>> >>>>>> Thank you both for suggestions. >>>>>> >>>>>> According to Monticello I have latest Roassal2 and yet I don't see RTMultiCompositeShape, but I would assume it should be what I was looking for originally. >>>>>> >>>>>> In the meantime I chose to do it manually - creating a custom shape in both Roassal and Trachert: >>>>>> I've done it in a single path because it seems that having multiple separate paths just creates more trouble. >>>>>> ======== >>>>>> computePath >>>>>> canvas ifNil: [ ^ self ]. >>>>>> path := self athensCanvas >>>>>> createPath: [ :builder | >>>>>> builder absolute. >>>>>> self ccwCirclePath: builder radius: 0.5. "building circular path with specified radius" >>>>>> self cwCirclePath: builder radius: 0.48. >>>>>> self ccwCirclePath: builder radius: 0.4 ] >>>>>> ======== >>>>>> >>>>>> But even if I could manage to do this with MultiCompositeShape I'm not sure about the rest of the shapes (see attachment). >>>>>> >>>>>> Peter >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> On Sun, Jul 13, 2014 at 1:18 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>>> Hi Peter, >>>>>> >>>>>> I am not sure what you try to do. Having two ellipses with the same center? But different radius? >>>>>> >>>>>> Something like that maybe: >>>>>> -=-=-=-=-=-=-=-=-= >>>>>> | v | >>>>>> v := RTView new. >>>>>> v @ RTDraggableView. >>>>>> >>>>>> shape := RTMultiCompositeShape new. >>>>>> shape add: (RTEllipse new color: (Color yellow alpha: 0.3); size: [:c | c numberOfMethods sqrt * 10 ]). >>>>>> shape add: (RTEllipse new color: (Color green alpha: 0.3); size: [:c | c numberOfLinesOfCode sqrt * 10 ]). >>>>>> >>>>>> v addAll: (shape elementsOn: RTShape withAllSubclasses). >>>>>> RTFlowLayout on: v elements. >>>>>> >>>>>> v >>>>>> -=-=-=-=-=-=-=-=-= >>>>>> >>>>>> <Screen Shot 2014-07-13 at 1.18.36 AM.png> >>>>>> >>>>>> Alexandre >>>>>> >>>>>> >>>>>> On Jul 11, 2014, at 11:05 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>>>> >>>>>>> Hi >>>>>>> >>>>>>> I'm trying to draw an ellipse inside another ellipse but to no avail. I've tried using RTCompositeShape but that just expands the size of the smaller shape. Is there something else I'm missing (like fixing dimensions so they won't get updated) or should I subclass RTAbstractCompositeShape and try to make something on my own? >>>>>>> >>>>>>> Thanks, >>>>>>> Peter >>>>>> >>>>>> -- >>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>> Alexandre Bergel http://www.bergel.eu >>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> <shapes.png> >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >

July 15, 2014

Re: [Pharo-users] Roassal2 Composite Shape

by Alexandre Bergel

Defining new shapes is not complicated at all, and we will review your code. The first thing is to define a trshape, you just have to override how you compute the path, and checking for point inclusion (I.e., is a point inside the shape or not). But beside that, this is all trivial. Let us know how it goes. Alexandre > On 15 Jul 2014, at 03:24, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > Well in the long run I will probably need much more shapes that are currently present so I will probably end up making both TRShape and RTShape anyway. As far as contribution goes, I'd be happy to contribute but I'm still quite new to both Pharo and Smalltalk so I'm quite skeptical about the code quality. > > I've actually already made both shapes for rounded box but it will need some testing first; so I'll keep you posted. > > Peter > > >> On Mon, Jul 14, 2014 at 10:47 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Indeed, Roassal does not have a rectangle with rounded corner. Having it in Roassal means you need a new TRShape and a new RTShape. >> >> I could easily do the RTShape. But we need the TRShape first. Do you feel like doing it? This will be a valuable addition to Roassal. >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On Jul 13, 2014, at 9:57 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> >>> Thank you, the example now works. However as I've mentioned in >>> previous post I'm not sure about the rest of the shapes posted in the >>> attachment. E.g. I haven't seen any notion of "box with rounded >>> corners". I could compose it from four RTArc nad four RTLine but it >>> seems to me overly complex compared to creating new Trachert/Roassal >>> classes. The same would go for the other shapes. What are your >>> thoughts/recommendations on that? >>> >>> Peter >>> >>> On Sun, Jul 13, 2014 at 3:25 PM, Alexandre Bergel >>> <alexandre.bergel(a)me.com> wrote: >>>> Sorry, the version was not properly saved in SmalltalkHub. If you update Roassal2 and Trachel, you should be able to execute the code snippet Iâve sent you. Maybe you want to add âv openâ at the end. If you are using GTInspector, this is not necessary. >>>> >>>> As far as I understand your description of the problem, you do not need to create your own shape. >>>> >>>> Let me know how it goes. >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> >>>>> On Jul 13, 2014, at 10:38 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>>> >>>>> Thank you both for suggestions. >>>>> >>>>> According to Monticello I have latest Roassal2 and yet I don't see RTMultiCompositeShape, but I would assume it should be what I was looking for originally. >>>>> >>>>> In the meantime I chose to do it manually - creating a custom shape in both Roassal and Trachert: >>>>> I've done it in a single path because it seems that having multiple separate paths just creates more trouble. >>>>> ======== >>>>> computePath >>>>> canvas ifNil: [ ^ self ]. >>>>> path := self athensCanvas >>>>> createPath: [ :builder | >>>>> builder absolute. >>>>> self ccwCirclePath: builder radius: 0.5. "building circular path with specified radius" >>>>> self cwCirclePath: builder radius: 0.48. >>>>> self ccwCirclePath: builder radius: 0.4 ] >>>>> ======== >>>>> >>>>> But even if I could manage to do this with MultiCompositeShape I'm not sure about the rest of the shapes (see attachment). >>>>> >>>>> Peter >>>>> >>>>> >>>>> >>>>> >>>>> On Sun, Jul 13, 2014 at 1:18 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>> Hi Peter, >>>>> >>>>> I am not sure what you try to do. Having two ellipses with the same center? But different radius? >>>>> >>>>> Something like that maybe: >>>>> -=-=-=-=-=-=-=-=-= >>>>> | v | >>>>> v := RTView new. >>>>> v @ RTDraggableView. >>>>> >>>>> shape := RTMultiCompositeShape new. >>>>> shape add: (RTEllipse new color: (Color yellow alpha: 0.3); size: [:c | c numberOfMethods sqrt * 10 ]). >>>>> shape add: (RTEllipse new color: (Color green alpha: 0.3); size: [:c | c numberOfLinesOfCode sqrt * 10 ]). >>>>> >>>>> v addAll: (shape elementsOn: RTShape withAllSubclasses). >>>>> RTFlowLayout on: v elements. >>>>> >>>>> v >>>>> -=-=-=-=-=-=-=-=-= >>>>> >>>>> <Screen Shot 2014-07-13 at 1.18.36 AM.png> >>>>> >>>>> Alexandre >>>>> >>>>> >>>>>> On Jul 11, 2014, at 11:05 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>>>>> >>>>>> Hi >>>>>> >>>>>> I'm trying to draw an ellipse inside another ellipse but to no avail. I've tried using RTCompositeShape but that just expands the size of the smaller shape. Is there something else I'm missing (like fixing dimensions so they won't get updated) or should I subclass RTAbstractCompositeShape and try to make something on my own? >>>>>> >>>>>> Thanks, >>>>>> Peter >>>>> >>>>> -- >>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>> Alexandre Bergel http://www.bergel.eu >>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>> >>>>> >>>>> >>>>> >>>>> <shapes.png> >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>> >>> >> >

July 15, 2014

Re: [Pharo-users] Roassal2 Composite Shape

by Ben Coman

July 15, 2014

Advice on making a first contribution

by Tim Mackinnon

Hi guys - I've decided to try and use moments of spare time to see if I can contribute in small ways (and I'm sorry I can't contribute in big ways - but maybe I will get up to that point). Anyway - I've thought it would be handy to improve the help text in Pharo - as this it where I first looked to find out a few things about the new environment, and discovered that the help doesn't really provide help on the environment. So having scouted around and looked at the help engine - it seemed like easiest way was to use the WikiHelp support, and put a pragma in a suitable place (initially I subclassed CustomHelp - but I think that is for more sophisticated uses than just documenting some basic help). Anyway - I created a package called "Pharo-Help" - and so my first question is: Are there names I should avoid, or conventions I should follow for good package names? I've then created a class "PharoEnvironmentHelp" with a class method #wikiStyleHelp (which is a convention I've seen in other places) - and it reads the class comment so it's easy to edit. However - should I use a separate class for this? It does keep it out of the way - but it ends up not being a class that does anything - so I could put this text on something else that represents "Pharo" - or is this fine? I've also given it the name "? Pharo Help" so it appears at the top of the list - my thinking being that new users would probably expect intro help at the top and the "?" does this. Finally - how do I submit it? (and I'm happy to read up on this, if there is something that has it nicely documented). Tim -- View this message in context: http://forum.world.st/Advice-on-making-a-first-contribution-tp4767806.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 15, 2014