- Pharo-users - lists.pharo.org

Re: [Pharo-users] Should I be reporting bugs in Pharo 3.0?

by Tim Mackinnon

Thanks Marcus - I will use it carefully and try and improve anything I find as I relearn things. -- View this message in context: http://forum.world.st/Should-I-be-reporting-bugs-in-Pharo-3-0-tp4767284p476… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 16, 2014

How do I get a halo on a specific UI object in Pharo 3/4?

by Tim Mackinnon

In older versions of Squeak pharo - I think alt-click would cycle you through halos on objects in the UI. I have noticed in Pharo 3/4 - if I ctrl+shift click I get a menu that has many options, one of which is "add halo" - but how do I control which UI element I will get a halo on? Similarly - there is "inspect" in this menu, and it does give me a list of widgets (saying deepest first) - however I can't easily see which element corresponds with what is in the list? I know the old squeak halo system wasn't favoured - but now I try and find things in Pharo 3/4 - I miss the ability to visually cycle through items to understand what I can inspect? Is there no way to do this now? It was very useful. Tim -- View this message in context: http://forum.world.st/How-do-I-get-a-halo-on-a-specific-UI-object-in-Pharo-… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 16, 2014

Re: [Pharo-users] Advice on making a first contribution

by Tim Mackinnon

I think I've figured out what I need to know by watching the video on the Pharo fogbugz page here - https://pharo.fogbugz.com/default.asp?W68 So I guess I will try that and see what feedback I get. Tim -- View this message in context: http://forum.world.st/Advice-on-making-a-first-contribution-tp4767806p47680… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

July 16, 2014

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

by Camille Teruel

On 16 juil. 2014, at 11:12, Max Bareis <info(a)derverkoster.de> wrote: > The misunderstanding her is based in the error message of the ui. > when you write > ^ - self width. > and save, the UI writes this text into the code: > ^ only numbers may be negated ->- self width. > > More helpful would have been something like: âonly literals may be negated with - use <object> negated insteadâ. > I was irritated and on the wrong track because I was absolutely sure that self width is a number. You are right, the error message should be better. I opened a bug entry and submitted a slice with the new error message: "The '-' prefix works only for literal numbers (use #negated instead)". https://pharo.fogbugz.com/f/cases/13568/Better-error-message-when-using-pre… > Regards > > Max > > Am 16.07.2014 um 10:44 schrieb Alain Busser <alain.busser(a)gmail.com>: > >> That's where the Inspector comes in: >> >> To debug, it is good to insert a self width inspect so that the inspector opens up and reveals what exactly the width is. OK, it is a number; then open the browser and look at the number's methods; or in the finder, try 2 . -2 in the examples... >> >> Pharo is excellent at debugging, that is why I choosed it for my Ontology project, the browser shows welle what is a number, what kind of numbers there are, and why a complex number is not a number... >> >> Alain >> >> >> On Wed, Jul 16, 2014 at 2:59 AM, Verkoster Info <info(a)derverkoster.de> wrote: >> It definitely is, >> >> >> >> >> thanks for all your answersâ¦ >> >> Regards >> >> Max >> >> Am 16.07.2014 um 00:56 schrieb Camille Teruel <camille.teruel(a)gmail.com>: >> >>> I've been overtaken :) >>> Isn't that an active mailing list ? >>> >>> >>> On 16 juil. 2014, at 00:53, Camille Teruel <camille.teruel(a)gmail.com> wrote: >>> >>>> Hi Max, >>>> >>>> Pharo doesn't have syntax for prefix operator like "-". >>>> The parser does accepts a "-" before literal numbers but it's not possible for arbitrary expressions. >>>> However you have the message #negated . >>>> >>>> negatedWidth >>>> ^ self width negated >>>> >>>> Cheers, >>>> Camille >>>> >>>> On 16 juil. 2014, at 00:16, Verkoster Info <info(a)derVerkoster.de> wrote: >>>> >>>>> 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 16, 2014

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

by Alain Busser

Then the browser had helped you, as you would have found that the "-" is a method for subtraction only. But it takes more time to look inside this browser... The reward is that you find gold nuggets here and there; for example, when I saw that there were a "asRomanLitteral" for the integers, I was astonished and pleased at the same time. On Wed, Jul 16, 2014 at 1:12 PM, Max Bareis <info(a)derverkoster.de> wrote: > The misunderstanding her is based in the error message of the ui. > when you write > ^ - self width. > and save, the UI writes this text into the code: > ^ only numbers may be negated ->- self width. > > More helpful would have been something like: âonly literals may be negated > with - use <object> negated insteadâ. > > I was irritated and on the wrong track because I was absolutely sure that > self width is a number. > > Regards > > Max > > Am 16.07.2014 um 10:44 schrieb Alain Busser <alain.busser(a)gmail.com>: > > That's where the Inspector comes in: > > To debug, it is good to insert a self width inspect so that the inspector > opens up and reveals what exactly the width is. OK, it is a number; then > open the browser and look at the number's methods; or in the finder, try 2 > . -2 in the examples... > > Pharo is excellent at debugging, that is why I choosed it for my Ontology > project, the browser shows welle what is a number, what kind of numbers > there are, and why a complex number is not a number... > > Alain > > > On Wed, Jul 16, 2014 at 2:59 AM, Verkoster Info <info(a)derverkoster.de> > wrote: > >> It definitely is, >> >> >> >> thanks for all your answersâ¦ >> >> Regards >> >> Max >> >> Am 16.07.2014 um 00:56 schrieb Camille Teruel <camille.teruel(a)gmail.com >> >: >> >> I've been overtaken :) >> Isn't that an active mailing list ? >> >> >> On 16 juil. 2014, at 00:53, Camille Teruel <camille.teruel(a)gmail.com> >> wrote: >> >> Hi Max, >> >> Pharo doesn't have syntax for prefix operator like "-". >> The parser does accepts a "-" before literal numbers but it's not >> possible for arbitrary expressions. >> However you have the message #negated . >> >> negatedWidth >> ^ self width negated >> >> Cheers, >> Camille >> >> On 16 juil. 2014, at 00:16, Verkoster Info <info(a)derVerkoster.de> wrote: >> >> 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 16, 2014

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

by Norbert Hartl

Am 16.07.2014 um 11:12 schrieb Max Bareis <info(a)derverkoster.de>: > The misunderstanding her is based in the error message of the ui. > when you write > ^ - self width. > and save, the UI writes this text into the code: > ^ only numbers may be negated ->- self width. > > More helpful would have been something like: âonly literals may be negated with - use <object> negated insteadâ. Then it needs to be "only number literalsâ¦" > > I was irritated and on the wrong track because I was absolutely sure that self width is a number. > There is a difference between an object and the way you can instantiate it. The minus sign relates to the fact that smalltalk has syntax for numbers and the minus sign is part of that syntax enabling you to instantiate negated numbers. As soon as the object is created you can only send messages. Norbert > Am 16.07.2014 um 10:44 schrieb Alain Busser <alain.busser(a)gmail.com>: > >> That's where the Inspector comes in: >> >> To debug, it is good to insert a self width inspect so that the inspector opens up and reveals what exactly the width is. OK, it is a number; then open the browser and look at the number's methods; or in the finder, try 2 . -2 in the examples... >> >> Pharo is excellent at debugging, that is why I choosed it for my Ontology project, the browser shows welle what is a number, what kind of numbers there are, and why a complex number is not a number... >> >> Alain >> >> >> On Wed, Jul 16, 2014 at 2:59 AM, Verkoster Info <info(a)derverkoster.de> wrote: >> It definitely is, >> >> >> >> >> thanks for all your answersâ¦ >> >> Regards >> >> Max >> >> Am 16.07.2014 um 00:56 schrieb Camille Teruel <camille.teruel(a)gmail.com>: >> >>> I've been overtaken :) >>> Isn't that an active mailing list ? >>> >>> >>> On 16 juil. 2014, at 00:53, Camille Teruel <camille.teruel(a)gmail.com> wrote: >>> >>>> Hi Max, >>>> >>>> Pharo doesn't have syntax for prefix operator like "-". >>>> The parser does accepts a "-" before literal numbers but it's not possible for arbitrary expressions. >>>> However you have the message #negated . >>>> >>>> negatedWidth >>>> ^ self width negated >>>> >>>> Cheers, >>>> Camille >>>> >>>> On 16 juil. 2014, at 00:16, Verkoster Info <info(a)derVerkoster.de> wrote: >>>> >>>>> 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 16, 2014

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

by Max Bareis

The misunderstanding her is based in the error message of the ui. when you write ^ - self width. and save, the UI writes this text into the code: ^ only numbers may be negated ->- self width. More helpful would have been something like: âonly literals may be negated with - use <object> negated insteadâ. I was irritated and on the wrong track because I was absolutely sure that self width is a number. Regards Max Am 16.07.2014 um 10:44 schrieb Alain Busser <alain.busser(a)gmail.com>: > That's where the Inspector comes in: > > To debug, it is good to insert a self width inspect so that the inspector opens up and reveals what exactly the width is. OK, it is a number; then open the browser and look at the number's methods; or in the finder, try 2 . -2 in the examples... > > Pharo is excellent at debugging, that is why I choosed it for my Ontology project, the browser shows welle what is a number, what kind of numbers there are, and why a complex number is not a number... > > Alain > > > On Wed, Jul 16, 2014 at 2:59 AM, Verkoster Info <info(a)derverkoster.de> wrote: > It definitely is, > > > > > thanks for all your answersâ¦ > > Regards > > Max > > Am 16.07.2014 um 00:56 schrieb Camille Teruel <camille.teruel(a)gmail.com>: > >> I've been overtaken :) >> Isn't that an active mailing list ? >> >> >> On 16 juil. 2014, at 00:53, Camille Teruel <camille.teruel(a)gmail.com> wrote: >> >>> Hi Max, >>> >>> Pharo doesn't have syntax for prefix operator like "-". >>> The parser does accepts a "-" before literal numbers but it's not possible for arbitrary expressions. >>> However you have the message #negated . >>> >>> negatedWidth >>> ^ self width negated >>> >>> Cheers, >>> Camille >>> >>> On 16 juil. 2014, at 00:16, Verkoster Info <info(a)derVerkoster.de> wrote: >>> >>>> 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 16, 2014

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

by Alain Busser

That's where the Inspector comes in: To debug, it is good to insert a self width inspect so that the inspector opens up and reveals what exactly the width is. OK, it is a number; then open the browser and look at the number's methods; or in the finder, try 2 . -2 in the examples... Pharo is excellent at debugging, that is why I choosed it for my Ontology project, the browser shows welle what is a number, what kind of numbers there are, and why a complex number is not a number... Alain On Wed, Jul 16, 2014 at 2:59 AM, Verkoster Info <info(a)derverkoster.de> wrote: > It definitely is, > > > > > thanks for all your answersâ¦ > > Regards > > Max > > Am 16.07.2014 um 00:56 schrieb Camille Teruel <camille.teruel(a)gmail.com>: > > I've been overtaken :) > Isn't that an active mailing list ? > > > On 16 juil. 2014, at 00:53, Camille Teruel <camille.teruel(a)gmail.com> > wrote: > > Hi Max, > > Pharo doesn't have syntax for prefix operator like "-". > The parser does accepts a "-" before literal numbers but it's not possible > for arbitrary expressions. > However you have the message #negated . > > negatedWidth > ^ self width negated > > Cheers, > Camille > > On 16 juil. 2014, at 00:16, Verkoster Info <info(a)derVerkoster.de> wrote: > > 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 16, 2014

Re: [Pharo-users] Should I be reporting bugs in Pharo 3.0?

by Marcus Denker

On 15 Jul 2014, at 11:50, Tim Mackinnon <tamackinnon(a)gmail.com> wrote: > Thanks for the tip Ben - yes Cases xxx looks like what I wanted (and I just > tried it). Its a bit difficult to know this is available so I wanted to add > it to the Pharo Fogbugz wiki but I can't edit that (it also looks like there > are other variants too: > http://help.fogcreek.com/7772/link-fogbugz-cases-to-changesetscommits-in-ki…) > I changed the config so that you can edit the Wiki. Marcus

July 16, 2014

Re: [Pharo-users] Roassal2 Composite Shape

by Juraj Kubelka

Just an idea: the svg path shape would not solve your needs? Maybe improving trachel svg path and then use it for any desired shape, e.g., rectangles with round corner? Does it have sense? Cheers, Jura -- Juraj Kubelka > El 15/07/2014, a las 03:24, Peter UhnÃ¡k <i.uhnak(a)gmail.com> escribiÃ³: > > 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 16, 2014