January 2015 - Pharo-users - lists.pharo.org

Question about loading Roassal2 in Pharo4

by Sven Van Caekenberghe

Hi, I just loaded Roassal2 in Pharo4 using the following expression: Gofer it smalltalkhubUser: 'ObjectProfile' project: 'Roassal2'; configurationOf: 'Roassal2'; loadStable. When I try one of the examples I see that I am missing some GT presentations specific to Roassal. How should I load those ? Thx, Sven

Jan. 7, 2015

Re: [Pharo-users] [Moose-dev] [Pharo-dev] Charting graphs

by Alexandre Bergel

Hi Doru, > The API is interesting. As I see it, this will be limited to things like bar, plots or line graphs. For example, a spider chart will not work with this one, but it will use a builder of its own, right? Yes. Currently, spider chart shares very little from what we have. This is why it deserves its own builder. Maybe this will change in the future, but for now it works well. But the way, we call Kiviat what you call Spider chart. Just have a look at RTKiviatBuilder. Here is a screenshot for people who do not understand what we are talking about :-) > Some feedback: > - I would rename Plugin to Decorator. From your statement, "The plugin framework exposes to a plugin all the necessary to define a whole range of decorations" it seems to me that "Decorator" fits better. Yes! Done! > - I would just call the class RTGrapher Yes, done! > - I do not quite understand how to distinguish the difference between DataSet and StackedDataSet. Yeah, not easy to grasp. Consider an histogram and a scatter plot. You will define an histogram as a list of values, e.g,. 4, 5, 6, 7 You will define a scatterplot as a list of points, e.g., 2 @ 3, 5 @ 6, â¦ An histogram is obtained from a list of objects, and a function Y to obtain the values. A scatter plot is obtained from a list of objects, and _two_ functions X and Y to obtain the points. When you do not need to specify an X, e.g., an histogram, then you need a RTStackedDataSet. When you need to specify an X, e.g., a scatter plot, then you need a RTDataSet. Is it clear? Maybe the vocabulary we use is not obvious. Cheers, Alexandre > > Cheers, > Doru > > > > On Mon, Jan 5, 2015 at 12:22 AM, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: > Hi! > > RTGraphBuilder went through major improvements. > - min and max may be specified. > - plugins to add some decoration (average line, standard deviation range, ticks lines, â¦) > > Here are some examples, with some examples, which should illustrate these points: > <Screen Shot 2015-01-04 at 8.08.05 PM.png> > Is obtained with: > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > | b ds | > b := RTGrapherBuilder new. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.1 * x) sin ]. > ds noDot. > ds interaction popupText: 'sinus'. > ds connectColor: Color blue. > b add: ds. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.2 * x) cos * 2 ]. > ds noDot. > ds interaction popupText: 'cosinus'. > ds connectColor: Color red. > b add: ds. > > b minY: -4. > b maxY: 4. > b minX: -25. > > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > > <Screen Shot 2015-01-04 at 8.13.51 PM.png> > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > b := RTGrapherBuilder new. > > ds := RTStackedDataSet new. > ds interaction popup. > ds points: #(600 470 170 430 300). > ds barShape width: 20; color: Color lightGreen. > b add: ds. > > b axisX noLabel; noTick. > b axisY noDecimals. > > b addPlugin: RTMeanDevVarPlugin new. > b build > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > Another example: > <Screen Shot 2015-01-04 at 8.17.51 PM.png> > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > b := RTGrapherBuilder new. > b extent: 300 @ 200. > > 5 timesRepeat: [ > ds := RTStackedDataSet new. > ds noDot. > ds points: ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum. > ds connectColor: Color green. > b add: ds. > ]. > > b addPlugin: RTMeanDevVarPlugin new. > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > The plugin framework exposes to a plugin all the necessary to define a whole range of decorations. For example, variable average lines, linear regression should be trivial to add... > > Happy new year! > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com/> > > "Every thing has its own flow" > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Jan. 6, 2015

Re: [Pharo-users] [Pharo-dev] Charting graphs

by Tudor Girba

Pretty cool. The API is interesting. As I see it, this will be limited to things like bar, plots or line graphs. For example, a spider chart will not work with this one, but it will use a builder of its own, right? Some feedback: - I would rename Plugin to Decorator. From your statement, "The plugin framework exposes to a plugin all the necessary to define a whole range of decorations" it seems to me that "Decorator" fits better. - I would just call the class RTGrapher - I do not quite understand how to distinguish the difference between DataSet and StackedDataSet. Cheers, Doru On Mon, Jan 5, 2015 at 12:22 AM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > RTGraphBuilder went through major improvements. > - min and max may be specified. > - plugins to add some decoration (average line, standard deviation range, > ticks lines, â¦) > > Here are some examples, with some examples, which should illustrate these > points: > Is obtained with: > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > | b ds | > b := RTGrapherBuilder new. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.1 * x) sin ]. > ds noDot. > ds interaction popupText: 'sinus'. > ds connectColor: Color blue. > b add: ds. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.2 * x) cos * 2 ]. > ds noDot. > ds interaction popupText: 'cosinus'. > ds connectColor: Color red. > b add: ds. > > b minY: -4. > b maxY: 4. > b minX: -25. > > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > b := RTGrapherBuilder new. > > ds := RTStackedDataSet new. > ds interaction popup. > ds points: #(600 470 170 430 300). > ds barShape width: 20; color: Color lightGreen. > b add: ds. > > b axisX noLabel; noTick. > b axisY noDecimals. > > b addPlugin: RTMeanDevVarPlugin new. > b build > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > Another example: > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > b := RTGrapherBuilder new. > b extent: 300 @ 200. > > 5 timesRepeat: [ > ds := RTStackedDataSet new. > ds noDot. > ds points: ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum. > ds connectColor: Color green. > b add: ds. > ]. > > b addPlugin: RTMeanDevVarPlugin new. > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > The plugin framework exposes to a plugin all the necessary to define a > whole range of decorations. For example, variable average lines, linear > regression should be trivial to add... > > Happy new year! > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 6, 2015

Re: [Pharo-users] Charting graphs

by Alexandre Bergel

Give me a couple of days, and I will update the Agilevisualization chapter. Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jan 6, 2015, at 2:49 PM, stepharo <stepharo(a)free.fr> wrote: > > Really really nice. > Continue to push Grapher and trying to reproduce "stupid" charts is the way to stress its design! > Do you have this description somewhere so that I can blog on it? > > Stef > > Le 5/1/15 00:22, Alexandre Bergel a Ã©crit : >> Hi! >> >> RTGraphBuilder went through major improvements. >> >> - min and max may be specified. >> >> - plugins to add some decoration (average line, standard deviation range, ticks lines, â¦) >> >> Here are some examples, with some examples, which should illustrate these points: >> <Mail Attachment.png> >> Is obtained with: >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> | b ds | >> b := RTGrapherBuilder new. >> >> ds := RTDataSet new. >> ds points: (0 to: 100 by: 0.1). >> ds y: [ :x | (0.1 * x) sin ]. >> ds noDot. >> ds interaction popupText: 'sinus'. >> ds connectColor: Color blue. >> b add: ds. >> >> ds := RTDataSet new. >> ds points: (0 to: 100 by: 0.1). >> ds y: [ :x | (0.2 * x) cos * 2 ]. >> ds noDot. >> ds interaction popupText: 'cosinus'. >> ds connectColor: Color red. >> b add: ds. >> >> b minY: -4. >> b maxY: 4. >> b minX: -25. >> >> b build. >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> >> <Mail Attachment.png> >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> b := RTGrapherBuilder new. >> >> ds := RTStackedDataSet new. >> ds interaction popup. >> ds points: #(600 470 170 430 300). >> ds barShape width: 20; color: Color lightGreen. >> b add: ds. >> >> b axisX noLabel; noTick. >> b axisY noDecimals. >> >> b addPlugin: RTMeanDevVarPlugin new. >> b build >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> Another example: >> <Mail Attachment.png> >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> b := RTGrapherBuilder new. >> b extent: 300 @ 200. >> >> 5 timesRepeat: [ >> ds := RTStackedDataSet new. >> ds noDot. >> ds points: ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum. >> ds connectColor: Color green. >> b add: ds. >> ]. >> >> b addPlugin: RTMeanDevVarPlugin new. >> b build. >> -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= >> >> The plugin framework exposes to a plugin all the necessary to define a whole range of decorations. For example, variable average lines, linear regression should be trivial to add... >> >> Happy new year! >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >

Jan. 6, 2015

Re: [Pharo-users] Metacello does not load the expected version from ConfigOf

by Dale Henrichs

On 1/6/15 7:16 AM, Usman Bhatti wrote: > Dale, > > I couldn't make it work with the upgraded Metacello and the script you > provided. > > Steps I did: > > 1. Download moose image: > https://ci.inria.fr/moose/job/moose-5.0/ > > 2. Update my Metacello to the 'full' version: > Metacello new > baseline: 'Metacello'; > repository: 'github://dalehenrich/metacello-work:master/repository'; > get. > Metacello new > baseline: 'Metacello'; > repository: 'github://dalehenrich/metacello-work:master/repository'; > onConflict: [:ex | ex allow]; > load > > 3. File in the ConfigurationOfDummyParser (see the first message in > the thread). > > 4. Run this script to downgrade to PetitParser version 1.51 > > Metacello new > configuration: 'DummyParser'; > version: '1.0'; > repository: '???'; > onDowngradeUseIncoming: #('PetitParser'); > load. > > The desired version is still not loaded, am I missing something here? Good question, I don't have a lot of time today to spend time trying to reproduce your problem, but if you send me a copy of the Transcript produced while doing the load I might be able to spot the problem ... > > regards, > > A question: I always use Metacello with ConfigOf and have never used > the scripting API myself or saw it being used elsewhere. > Can you provide a link that describes the use cases for both: ConfigOf > vs. Scripting API? I've noticed the same thing:) My "elevator pitch" for the script api goes like this: 1. The scripting api maintains a registry of the actual project versions loaded into the image, making #currentVersion obsolete. #currentVersion is bad because it does a calculation of the current version that can be very slow and sometimes completely incorrect. 2. The old api has rules that it follows when loading projects (i.e., newer projects always win) and there is no mechanism for altering those rules. The scripting api provides mechanisms for for bending those rules to fit your needs ... like allowing a downgrade of a project. Part of the reason that people haven't changed has to do with how incredibly difficult it is to change the existing inertia. Another part of it is that I continue to support the old way of doing things, so there is no explicit motivation to change. If you look back 2-3 years in the archives of the Metacello mailing list[1] you should be able to find a number of posts where I make a more detailed cases for the scripting api:) At the end of the day, it isn't important to me to "get people to use the scripting api," as I said, I continue to support using the old api. I figure that when enough people start asking questions about how to "bend the Metacello rules" that folks will begin to use the "new" scripting api:) Dale [1] https://groups.google.com/forum/#!forum/metacello

Jan. 6, 2015

Re: [Pharo-users] Charting graphs

by stepharo

Really really nice. Continue to push Grapher and trying to reproduce "stupid" charts is the way to stress its design! Do you have this description somewhere so that I can blog on it? Stef Le 5/1/15 00:22, Alexandre Bergel a Ã©crit : > Hi! > > RTGraphBuilder went through major improvements. > - min and max may be specified. > - plugins to add some decoration (average line, standard deviation > range, ticks lines, â¦) > > Here are some examples, with some examples, which should illustrate > these points: > Is obtained with: > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > | b ds | > b := RTGrapherBuilder new. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.1 * x) sin ]. > ds noDot. > ds interaction popupText: 'sinus'. > ds connectColor: Color blue. > b add: ds. > > ds := RTDataSet new. > ds points: (0 to: 100 by: 0.1). > ds y: [ :x | (0.2 * x) cos * 2 ]. > ds noDot. > ds interaction popupText: 'cosinus'. > ds connectColor: Color red. > b add: ds. > > b minY: -4. > b maxY: 4. > b minX: -25. > > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > b := RTGrapherBuilder new. > > ds := RTStackedDataSet new. > ds interaction popup. > ds points: #(600 470 170 430 300). > ds barShape width: 20; color: Color lightGreen. > b add: ds. > > b axisX noLabel; noTick. > b axisY noDecimals. > > b addPlugin: RTMeanDevVarPlugin new. > b build > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > Another example: > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > b := RTGrapherBuilder new. > b extent: 300 @ 200. > > 5 timesRepeat: [ > ds := RTStackedDataSet new. > ds noDot. > ds points: ((1 to: 500) collect: [ :i | 50 atRandom - 25 ]) cumsum. > ds connectColor: Color green. > b add: ds. > ]. > > b addPlugin: RTMeanDevVarPlugin new. > b build. > -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= -=-=-=-=-=-= > > The plugin framework exposes to a plugin all the necessary to define a > whole range of decorations. For example, variable average lines, > linear regression should be trivial to add... > > Happy new year! > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Jan. 6, 2015

Re: [Pharo-users] Metacello does not load the expected version from ConfigOf

by Usman Bhatti

Dale, I couldn't make it work with the upgraded Metacello and the script you provided. Steps I did: 1. Download moose image: https://ci.inria.fr/moose/job/moose-5.0/ 2. Update my Metacello to the 'full' version: Metacello new baseline: 'Metacello'; repository: 'github://dalehenrich/metacello-work:master/repository'; get. Metacello new baseline: 'Metacello'; repository: 'github://dalehenrich/metacello-work:master/repository'; onConflict: [:ex | ex allow]; load 3. File in the ConfigurationOfDummyParser (see the first message in the thread). 4. Run this script to downgrade to PetitParser version 1.51 Metacello new configuration: 'DummyParser'; version: '1.0'; repository: '???'; onDowngradeUseIncoming: #('PetitParser'); load. The desired version is still not loaded, am I missing something here? regards, A question: I always use Metacello with ConfigOf and have never used the scripting API myself or saw it being used elsewhere. Can you provide a link that describes the use cases for both: ConfigOf vs. Scripting API? On Fri, Jan 2, 2015 at 6:47 PM, Dale Henrichs < dale.henrichs(a)gemtalksystems.com> wrote: > Usman, > > It is likely that Pharo3.0 is not using the latest version of Metacello. > You should be able to upgrade to the latest versions following the install > instructions for Pharo3.0[1]. > > Dale > > [1] https://github.com/dalehenrich/metacello-work#pharo30 > > > On 1/2/15 6:23 AM, Usman Bhatti wrote: > > Dale, > > Thanks for your detailed explanations. > > Metacello class in my image does not seem to define the messages > described in the documentation for handling downgrading and upgrading > conflicts: > > https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… > > I am using Pharo 3.0 with Moose. > > [image: Inline image 1] > > Did I miss something? > > regards, > Usman > > On Fri, Dec 19, 2014 at 7:00 PM, Dale Henrichs < > dale.henrichs(a)gemtalksystems.com> wrote: > >> Usman, >> >> With classic Metacello (using the `(ConfigurationOfxxx project version: >> 'xxx') load` pattern) you can only downgrade via an explicit load of a >> particular version of the project. When loading projects indirectly via a >> project reference from another project Metacello is biased towards upgrade. >> >> With the Metacello Scripting API[1], you may include an >> #onDowngradeUseIncoming: clause to selectively permit downgrades: >> >> Metacello new >> configuration: 'DummyParser'; >> version: '1.0'; >> repository: '???'; >> onDowngradeUseIncoming: #('PetitParser'); >> load. >> >> For additional downgrade options see[2]. >> >> Since you are interested in using a specific version of a project you may >> also be interested in locking the project[3][4]. With a `lock` Metacello >> will not upgrade or downgrade the project but always `honor` the lock >> unless an #onLock: clause is used ... >> >> Note that for `locking` to work, you must use the Metacello Scripting API >> to do all of your project loads ... >> >> Dale >> >> [1] >> https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… >> [2] >> https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… >> [3] >> https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… >> [4] >> https://github.com/dalehenrich/metacello-work/blob/master/docs/LockCommandR… >> >> >> On 12/19/2014 07:44 AM, Usman Bhatti wrote: >> >> Hi all, >> >> I am trying to load a specific version of PetitParser in a Moose image. >> A Moose image comes with the latest development version of PetitParser. So, >> I am trying to downgrade to an older version. So, when I load the version >> manually, older versions of the packages are loaded: >> (ConfigurationOfPetitParser project version: '1.51') load >> >> But when I try to load the same version within my ConfigOf the expected >> packages are not loaded and list of the PetitParser packages loaded remains >> unchanged. Here is how my baseline looks like: >> >> ConfigurationOfDummyParser>>baseline01: spec >> <version: '0.1-baseline'> >> >> spec for: #'common' do: [ >> spec blessing: #'baseline'. >> spec project: 'PetitParser' with: [ >> spec >> className: #ConfigurationOfPetitParser; >> versionString: '1.51'; >> repository: 'http://smalltalkhub.com/mc/Moose/PetitParser/main/' ]. ]. >> >> I also tried creating a version but it didn't help. >> >> ConfigurationOfDummyParser>>version10: spec >> <version: '1.0' imports: #('0.1-baseline' )> >> >> spec for: #'common' do: [ >> spec blessing: #'stable'. >> spec description: 'version 1.0'. >> spec author: 'usmanbhatti'. >> spec timestamp: '12/19/2014 16:35'. >> spec project: 'PetitParser' with: '1.51'. ]. >> >> I also had a look at the package the configuration tries to load and >> the list shows correct packages to be loaded (see screenshot). >> >> Does anyone have an idea what may be problematic in my code or that of >> Metacello? I am attaching the code of my ConfigOf for a Moose image. >> >> Thanks in advance. >> >> Usman[image: Inline image 1] >> >> >> >> >> > >

Jan. 6, 2015

Re: [Pharo-users] Pharo 4: Setting values from within an inspector

by Johan Fabry

(I agree that discoverability of the previous solution was very low.) As is, Iâm happy that it exists. :-) But it does not seem to work for me :-( I tested it in todayâs build (40429). When I do âabcâ asValueHolder and then try to change value (double-click, delete a and b, press enter) nothing seems to happen. If instead of pressing enter, I click outside the edit field, the field shows âcâ, but clicking on self shows that the value is still âabcâ. I also tried Cmd-S but it only makes the orange edit triangle go away. The rest of my comments / requests are more cosmetic and here they are as a bulleted list for convenience. - hitting esc should cancel the edit. - I expect that starting an edit would select the content of the field, like for example when renaming a file in the MacOS Finder. - start an edit and stop it by clicking outside (for example) without making a change and the field still has the orange triangle - the context menu on the field is too big, I would expect only cut/copy/paste > On Jan 5, 2015, at 18:29, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > Hi, > > Yes, something like that is clearly needed (although the discoverability of the previous solution was not at all better). But, I meant except from the discoverability. Could you check and see if the behavior is what you expect? > > Cheers, > Doru > > > On Mon, Jan 5, 2015 at 10:25 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Well, I would say that there is a discoverability issue ;-) How about having some small âeditâ icon-button in the list instead? > > > On Jan 5, 2015, at 17:29, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Hi, > > > > You saw it. How did you discover it? :) > > > > The implementation is still a work in progress, but it already shows the direction. Now that it is out, feedback is welcome. > > > > Cheers, > > Doru ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

Jan. 5, 2015

Re: [Pharo-users] Problem with bugtracker

by Mark Rizun

> > I reviewed some of your changes for that issue, but it was difficult, > because you made > some new changes and it wasn't clear when it is ready or what was the > original error > and if it is solved now. > Yes I know it was a bit messy with this one, sorry for that ;) > > you can set the state to "resolved" again and wait for the monkey to > do the validation again. If there is still, there will be a new > "Issue Validation Failed"-result page. > Thanks, has to try it. Mark 2015-01-05 23:10 GMT+02:00 Nicolai Hess <nicolaihess(a)web.de>: > Hi Mark, > > I reviewed some of your changes for that issue, but it was difficult, > because you made > some new changes and it wasn't clear when it is ready or what was the > original error > and if it is solved now. > > you can set the state to "resolved" again and wait for the monkey to > do the validation again. If there is still, there will be a new > "Issue Validation Failed"-result page. > > > nicolai > > > 2015-01-05 20:10 GMT+01:00 Mark Rizun <mrizun(a)gmail.com>: > >> Hello, >> >> While ago, I've resolved an issue 14254 >> < >> https://pharo.fogbugz.com/f/cases/14254/AST-method-replaceWith-does-not-cha… >> > >> and validation was successful. Since that time, I didn't check this issue >> as >> was busy. Turned out after successful validation, there was a failure, >> which >> I can't take a look at, because it's not found (404 error). Just wanted >> this >> slice to be included in Pharo4. >> >> Best, >> Mark >> >> >> >> -- >> View this message in context: >> http://forum.world.st/Problem-with-bugtracker-tp4797910.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> >

Jan. 5, 2015

Re: [Pharo-users] Pharo 4: Setting values from within an inspector

by Tudor Girba

Hi, Yes, something like that is clearly needed (although the discoverability of the previous solution was not at all better). But, I meant except from the discoverability. Could you check and see if the behavior is what you expect? Cheers, Doru On Mon, Jan 5, 2015 at 10:25 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> wrote: > > Well, I would say that there is a discoverability issue ;-) How about > having some small âeditâ icon-button in the list instead? > > > On Jan 5, 2015, at 17:29, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > > Hi, > > > > You saw it. How did you discover it? :) > > > > The implementation is still a work in progress, but it already shows the > direction. Now that it is out, feedback is welcome. > > > > Cheers, > > Doru > > > > On Mon, Jan 5, 2015 at 8:06 PM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > > Hi, > > > > This is a bit hidden, but you can double click on the value and get an > input field. > > > > On Mon, Jan 5, 2015 at 3:57 PM, Johan Fabry <jfabry(a)dcc.uchile.cl> > wrote: > > Hi all, > > > > there was a cool feature of inspectors in Pharo 3 that seems to be gone > in 4. You could inspect an object, say a ValueHolder, click on a variable, > e.g. value, and that would show the value of the value variable :-P in the > right hand pane. OK nothing fundamentally changed in Pharo 4, that still > happens. But, in Pharo 3, I could enter an expression in that pane, e.g. > âabc', and hit cmd-s (accept). This would *change* the contents of value to > the result of the evaluation, i.e. the string abc. > > > > I donât see how I can do that in Pharo 4, there is no menu item and no > keyboard shortcut. I would really love to have that back, it can be very > useful at times... > > > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > > > Johan Fabry - http://pleiad.cl/~jfabry > > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > > > > > > > > > > > -- > > -- > > Marcus Denker -- denker(a)acm.org > > http://www.marcusdenker.de > > > > > > > > -- > > www.tudorgirba.com > > > > "Every thing has its own flow" > > > > ---> Save our in-boxes! http://emailcharter.org <--- > > Johan Fabry - http://pleiad.cl/~jfabry > PLEIAD lab - Computer Science Department (DCC) - University of Chile > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 5, 2015