August 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] cleanup rubric

by Alain Plantec

Hello all, Yes we have both PluggableTextMorph and Rubric so it is a mess. Yes Rubric was a fork, so a lot of code is duplicated. I would say just wait that all PluggableTextMorph uses are removed then we will be able to clean-up things. Now, remember that I was not so excited by Rubric as the default editor. Rubric is the past, It should be removed asap with all the crap that it duplicates. I would not invest to much time in cleaning and commenting it. Instead, clean, document and implement tests for TxText. Cheers Alain > On 01 Aug 2015, at 11:22, stepharo <stepharo(a)free.fr> wrote: > > Yes the situation with rubric is a real mess :( > Ideally I would like to throw away text and rub altogether. > Now I would like to understand what is a good path that minimise > duplication. > > In addition I do not understand why certain class extensions are not the same in both packages. > So I will try to get some time to read code and come with a list of actions. > If you have some ideas I'm interested. > > Stef > >>> Maybe I am wrong, but it looks like there are many >>> classes and code in rubric that are the same as in the old Text classes. >> >> Yes never said that Rubric is the future. He just improved a bit >> >>> Rub is used in GT and now in the Core image. Shouldn't we clean this up >>> before it used everywhere? >>> >>> Some examples: >>> >>> All TextLink classes looks the same (TextClassLink <-> RubTextClassLink) >>> >>> MorphAnnouncement subclass: #RubMorphAnnouncement >>> RubMorphAnnouncment adds nothing >>> >>> FindReplaceService <-> RubFindReplaceService >>> They look very similar, I don't understand why so much code is >>> just the same in both, why not extract that into a base class? >>> (and the same for RubFindReplaceDialogWindow/ FindReplaceDialogWindow >>> and some many too) >>> >>> RubEditingState / EditingState. >>> >>> What this makes it even worse, Rubs class comment doesn't indicate how >>> they differ from the old other one. >> True. >>> It is really difficult to understand, >>> - which (Rub)classes were created just because the old TextApi has them, but aren't actually used in the current Rubric framework. >>> - wich classes are used but could be replaced with the existing one (TextLink for example) >>> - which classes had to be changed, and therefore only the Rub-classes can work with rubric. >>> - which classes are similiar named like the old Text classes and share some code but may work >>> totally different. >>> >>> (For example TextEditor vs. RubTextEditor there are some methods in both that aren't used >>> anywhere, it looks like RubTextEditor is just >>> - a copy from TextEditor, >>> - changed where it was needed >>> - unchanged otherwise >> Yes. I think that alain did it like that. He just wanted to offer some behavior for the Moosers. >>> Rubric really adds some great new things and if you look at where it is used, it >>> is really a great step forward, but the code is in a bad state. >>> This needs to be cleaned up. >> Definitively. >> Nicolai >> do you have a list of actions? >> because I would like to do some of them. >> We could remove the duplicate. This is what we started to do with PluggableTextMorph. >> >> > >

Aug. 2, 2015

Re: [Pharo-dev] [Moose-dev] Re: GanttChartMorph openOn: aCollectionOfActivities ?

by Alexandre Bergel

Sure, this is easy. Axis supports a method called #labelConversion: [ :aNumericalValue | â¦ ] You need to provide a bloc that returns a string. For example: | data b s | data := #(#(c1 0 5) #(c1 6 8) #(c2 0 5) #(c2 8 10) #(c3 0 10) #(c4 5 10) #(c5 5 8)). b := RTTimeline new. s := RTTimelineSet new. s objects: data. s lineIdentifier: #first. s start: #second. s end: #third. b add: s. b axisY title: 'Task'. b axisX numberOfLabels: 10; title: 'Week day'; labelConversion: [ :v | v \\ 7 + 1 ]. b build. ^ b view Does this help? Cheers, Alexandre > On Aug 1, 2015, at 12:48 AM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: > > The SVG export accessible through the '...' menu works fine. > > A new question regarding the labeling of the x-axis. > > How do I specify that I want to see months > > 8 9 10 11 12 > > only? > > data := #( #(WP1 8 12) #(WP2 8 10) #(WP3 10 11) > #(WP4 11 12) > > > > And is something like this possible? > > > 8 9 10 11 12 1 2 3 4 > > > --Hannes > > > On 7/31/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> The ââ¦â button, top right of a GTInspector that is showing a Roassal >> visualization. >> >> https://dl.dropboxusercontent.com/u/31543901/TMP/Screen%20Shot%202015-07-30… >> >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On Jul 30, 2015, at 2:25 PM, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>> >>> Which menu? Could you describe it verbally please where to click? The >>> picture did not come through. >>> >>> --Hannes >>> >>> On 7/30/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>> Simply use the menu: >>>> >>>> >>>> Cheers, >>>> Alexandre >>>> >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> Alexandre Bergel http://www.bergel.eu >>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>> >>>> >>>> >>>>> On Jul 30, 2015, at 11:59 AM, H. Hirzel <hannes.hirzel(a)gmail.com> >>>>> wrote: >>>>> >>>>> Alexandre, >>>>> >>>>> This is really agile ... version 1005 of Roassal loaded and version >>>>> 305 of Trachel :-) >>>>> >>>>> The GANTT chart works fine, see screen shot. >>>>> >>>>> How do I export it as SVG code in Roassal? >>>>> >>>>> --Hannes >>>>> >>>>> On 7/29/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>>> Pure agile development: the latest version is the one that count. >>>>>> You need to update two packages: Roassal2 and Trachel. >>>>>> >>>>>> Cheers, >>>>>> Alexandre >>>>>> -- >>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>> Alexandre Bergel http://www.bergel.eu >>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>> >>>>>> >>>>>> >>>>>>> On Jul 29, 2015, at 3:24 PM, H. Hirzel <hannes.hirzel(a)gmail.com> >>>>>>> wrote: >>>>>>> >>>>>>> Or a configuration? Which one? >>>>>>> >>>>>>> --HH >>>>>>> >>>>>>> On 7/29/15, H. Hirzel <hannes.hirzel(a)gmail.com> wrote: >>>>>>>> Thanks for the updated GANTT script. >>>>>>>> >>>>>>>> My question was about the version of Roassal to load. >>>>>>>> >>>>>>>> Which one? >>>>>>>> I just go for version 1000? >>>>>>>> >>>>>>>> See screenshot. >>>>>>>> >>>>>>>> --Hannes >>>>>>>> >>>>>>>> On 7/29/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>>>>>>>> You should load the latest Roassal. >>>>>>>>>> >>>>>>>>>> How do I do that? I just loaded Roassal into a fresh Pharo4.0 >>>>>>>>>> image >>>>>>>>>> and RTTimeLine is not included. >>>>>>>>> >>>>>>>>> We did some refactoring. >>>>>>>>> Instead, you should do: >>>>>>>>> >>>>>>>>> -=-=-=-=-=-=-=-= >>>>>>>>> data := #(#(WP1 0 5) #(WP2 5 8) #(WP3 7 10)). >>>>>>>>> >>>>>>>>> b := RTTimeline new. >>>>>>>>> >>>>>>>>> s := RTTimelineSet new. >>>>>>>>> s objects: data. >>>>>>>>> s lineIdentifier: #first. >>>>>>>>> s start: #second. >>>>>>>>> s end: #third. >>>>>>>>> b add: s. >>>>>>>>> >>>>>>>>> b axisX >>>>>>>>> numberOfLabels: 5; >>>>>>>>> labelRotation: -45; >>>>>>>>> labelConversion: [ :v | Date year: 2015 day: v ]. >>>>>>>>> >>>>>>>>> d := RTVerticalTickLineDecorator new. >>>>>>>>> d shape line color: Color white. >>>>>>>>> b addDecorator: d. >>>>>>>>> b >>>>>>>>> -=-=-=-=-=-=-=-= >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> The class RTTimelineExample contains many examples >>>>>>>>> >>>>>>>>> Let us know how it goes >>>>>>>>> >>>>>>>>> Alexandre >>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>>> Alexandre >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> Le 9 mai 2015 Ã 19:06, H. Hirzel <hannes.hirzel(a)gmail.com> a >>>>>>>>>>>> Ã©crit >>>>>>>>>>>> : >>>>>>>>>>>> >>>>>>>>>>>> Thank you for the examples, Alexandre! >>>>>>>>>>>> >>>>>>>>>>>> I have Pharo 4.0 with Roassal 2.0 installed >>>>>>>>>>>> (AlexandreBergel.718) >>>>>>>>>>>> >>>>>>>>>>>> I paste the following into a 'Playground' window and 'do it'. >>>>>>>>>>>> >>>>>>>>>>>> b := RTTimeLine new. >>>>>>>>>>>> >>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; >>>>>>>>>>>> end: >>>>>>>>>>>> 5). >>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; >>>>>>>>>>>> end: >>>>>>>>>>>> 8). >>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; >>>>>>>>>>>> end: >>>>>>>>>>>> 10). >>>>>>>>>>>> >>>>>>>>>>>> b axisX numberOfLabels: 5. >>>>>>>>>>>> b >>>>>>>>>>>> >>>>>>>>>>>> I get the error message that RTTimeLine is not known. >>>>>>>>>>>> >>>>>>>>>>>> What am I missing? >>>>>>>>>>>> >>>>>>>>>>>> --Hannes >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> On 5/8/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>>>>>>>>>>>> Hi Hannes! >>>>>>>>>>>>> >>>>>>>>>>>>> Here is a first shoot paired-programmed with Juraj using >>>>>>>>>>>>> Roassal: >>>>>>>>>>>>> >>>>>>>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-= >>>>>>>>>>>>> b := RTTimeLine new. >>>>>>>>>>>>> >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP1; start: 0; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 5). >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP2; start: 5; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 8). >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #WP3; start: 7; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 10). >>>>>>>>>>>>> >>>>>>>>>>>>> b axisX numberOfLabels: 5. >>>>>>>>>>>>> b >>>>>>>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-= >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Here some slightly more elaborated example: >>>>>>>>>>>>> >>>>>>>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-= >>>>>>>>>>>>> âOne color per entry" >>>>>>>>>>>>> | b d | >>>>>>>>>>>>> b := RTTimeLine new. >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 5). >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 8). >>>>>>>>>>>>> >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 5). >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 10). >>>>>>>>>>>>> >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 10). >>>>>>>>>>>>> >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 10). >>>>>>>>>>>>> >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 8). >>>>>>>>>>>>> >>>>>>>>>>>>> d := RTVerticalTickLineDecorator new. >>>>>>>>>>>>> d shape line color: Color white. >>>>>>>>>>>>> b addDecorator: d. >>>>>>>>>>>>> b axisX >>>>>>>>>>>>> numberOfLabels: 5; >>>>>>>>>>>>> labelRotation: -45; >>>>>>>>>>>>> labelConversion: [ :v | Date year: 2015 day: v ]. >>>>>>>>>>>>> >>>>>>>>>>>>> b shape color: (RTMultiLinearColorForIdentity new objects: b >>>>>>>>>>>>> entries). >>>>>>>>>>>>> b >>>>>>>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-= >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> One color per timeline >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-= >>>>>>>>>>>>> | b | >>>>>>>>>>>>> b := RTTimeLine new. >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 0; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 5). >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c1; start: 6; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 8). >>>>>>>>>>>>> >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 0; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 5). >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c2; start: 8; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 10). >>>>>>>>>>>>> >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c3; start: 0; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 10). >>>>>>>>>>>>> >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c4; start: 5; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 10). >>>>>>>>>>>>> >>>>>>>>>>>>> b addEntry: (RTTimeLineEntry new identifier: #c5; start: 5; >>>>>>>>>>>>> end: >>>>>>>>>>>>> 8). >>>>>>>>>>>>> >>>>>>>>>>>>> d := RTVerticalTickLineDecorator new. >>>>>>>>>>>>> d shape line color: Color white. >>>>>>>>>>>>> b addDecorator: d. >>>>>>>>>>>>> b axisX >>>>>>>>>>>>> numberOfLabels: 5; >>>>>>>>>>>>> labelRotation: -45; >>>>>>>>>>>>> labelConversion: [ :v | Date year: 2015 day: v ]. >>>>>>>>>>>>> >>>>>>>>>>>>> b shape color: (RTMultiLinearColorForIdentity new command: >>>>>>>>>>>>> #identifier; >>>>>>>>>>>>> objects: #(c1 c2 c3 c4 c5)). >>>>>>>>>>>>> b >>>>>>>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-= >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Age of some classes: >>>>>>>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-= >>>>>>>>>>>>> | b | >>>>>>>>>>>>> b := RTTimeLine new. >>>>>>>>>>>>> b extent: 500 @ 500. >>>>>>>>>>>>> ((RTShape withAllSubclasses sortedAs: #ageInDaysRounded) >>>>>>>>>>>>> select: >>>>>>>>>>>>> #hasMethods) >>>>>>>>>>>>> do: [ :cls | >>>>>>>>>>>>> e := RTTimeLineEntry new. >>>>>>>>>>>>> e identifier: cls. >>>>>>>>>>>>> e start: cls computeYoungestMethod ageInDays. >>>>>>>>>>>>> e end: cls computeOldestMethod ageInDays. >>>>>>>>>>>>> b addEntry: e ]. >>>>>>>>>>>>> b >>>>>>>>>>>>> -=-=-=-=-=-=-=-=-=-=-=-= >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> All these examples are in the Roassal time line example menu. >>>>>>>>>>>>> >>>>>>>>>>>>> This is still an early version. Let us know how it goes! >>>>>>>>>>>>> https://www.facebook.com/ObjectProfile/posts/840542572699008 >>>>>>>>>>>>> >>>>>>>>>>>>> Cheers, >>>>>>>>>>>>> Alexandre >>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>>>>>>>>>>> Alexandre Bergel http://www.bergel.eu >>>>>>>>>>>>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>>> On May 7, 2015, at 4:25 PM, H. Hirzel >>>>>>>>>>>>>> <hannes.hirzel(a)gmail.com> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hello >>>>>>>>>>>>>> >>>>>>>>>>>>>> Has somebody done a GANTT chart? >>>>>>>>>>>>>> >>>>>>>>>>>>>> GanttChartMorph openOn: aCollectionOfActivities >>>>>>>>>>>>>> >>>>>>>>>>>>>> ? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Activities have >>>>>>>>>>>>>> - id >>>>>>>>>>>>>> - description >>>>>>>>>>>>>> - start date >>>>>>>>>>>>>> - end date >>>>>>>>>>>>>> ? >>>>>>>>>>>>>> >>>>>>>>>>>>>> Regards >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hannes >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Moose-dev mailing list >>>>>>>>>>>> Moose-dev(a)iam.unibe.ch >>>>>>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Moose-dev mailing list >>>>>>>>>> Moose-dev(a)iam.unibe.ch >>>>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> <Roassal2_configurations_Screenshot from 2015-07-29 >>>>>>> 18:23:50.png>_______________________________________________ >>>>>>> Moose-dev mailing list >>>>>>> Moose-dev(a)iam.unibe.ch >>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >>>>>> >>>>>> >>>>> <Pharo_Roassal_GANTT_chart_Screenshot from 2015-07-30 14:55:31.png> >>>> >>>> >>> >> >> >> > <Roassal_timeline_x_axis_question_Screenshot from 2015-08-01.png> -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 1, 2015

deprecation and unit testing?

by Alexandre Bergel

Hi! Apparently deprecated methods called within unit test do not make test fail. Anyone experienced this already? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 1, 2015

Re: [Pharo-dev] why do I get a slice when I just want to commit package with versioner?

by Sean P. DeNigris

stepharo wrote > (there is only slice in the combo box choice). IIRC this happens when Versionner can't find a repository common to all packages. I guess it's a result of Komitter being used outside its originally intended context... ----- Cheers, Sean -- View this message in context: http://forum.world.st/why-do-I-get-a-slice-when-I-just-want-to-commit-packa… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 1, 2015

Re: [Pharo-dev] Using Kommiter I got a problem with diff morph and rubric

by Franck Warlouzet

Right I forgot to call scrollPane on the morph before scroller in this method. I did not see it because I do not use Komitter. Fixed here: https://pharo.fogbugz.com/f/cases/16088/Fix-DiffMorph-when-called-from-Komi… Franck > Date: Sat, 1 Aug 2015 22:05:15 +0200 > From: stepharo(a)free.fr > To: pharo-dev(a)lists.pharo.org > Subject: [Pharo-dev] Using Kommiter I got a problem with diff morph and rubric > > Hi frank > > when I tried to save a project, Kommiter is invoked and I got > > calibrateScrollbar > "Set the scrollbar parameters to match the texts." > > | maxY range delta innerH | > self fullBounds. > maxY := self srcMorph extent y max: self dstMorph extent y. > innerH := self dstMorph innerBounds height. > delta := 91. "self dstMorph textMorph defaultLineHeight" > range := maxY - innerH max: 0. > range = 0 > ifTrue: [ > ^ self scrollbarMorph > scrollDelta: 0.02 pageDelta: 0.2; > interval: 1.0; > setValue: 0.0 ]. > self scrollbarMorph > scrollDelta: (delta / range) asFloat pageDelta: ((innerH - > delta) / range) asFloat; > interval: (innerH / maxY) asFloat; > setValue: > ((self srcMorph scroller offset y max: self dstMorph > scroller offset y) / range min: 1.0) asFloat > > ^^^^^^^ > > where srcMoirph is a RubScrolledTextMorph > > Stef >

Aug. 1, 2015

Re: [Pharo-dev] Nautilus new buttons not buttons?

by Peter UhnÃ¡k

On Sat, Aug 1, 2015 at 10:10 PM, stepharo <stepharo(a)free.fr> wrote: > > > Le 1/8/15 13:54, Esteban Lorenzano a Ã©crit : > > > On 01 Aug 2015, at 13:25, Franck Warlouzet <franck.warlouzet(a)hotmail.fr> > wrote: > > Hello, > > Yes it looks a little bit 'lite' but we did not want to have 2 buttons > with the same look but two different kinds of actions. Hierarchy button > changes the window itself and variable and scoped open a new menu or window. > > > > but they are buttons, then they should look like one. > alsoâ¦ âVariablesâ (button or whatever) there just do not make sense (since > is a âclassâ related action)â¦ it increases confusion instead solving a > problem. > we need a better general approach for those actions, maybe a toolbar or > something like thatâ¦ but as it is now it does not work. > > > Yes we know. > Now there is a difference between a button popping something and one just > acting on the default browser. > But does there need to be a distinction? If I DON'T know what the button does, then distinction, unless it is well known, will not help me, because I will not know what the distinction means. And if I DO know what it does, then I don't care about the distinction anymore. So if you want to visualize it, then it must be something that is well known. For example "Print ..." (dotdotdot) means "Clicking on this will not print immediately, but will open a new window with some more stuff.", or the V triangle down signifies that it will open a dropdown menu. And even with these minor UI/UX details, most people don't even realize it's there and will just memorize and internalize the process, Peter

Aug. 1, 2015

Re: [Pharo-dev] why do I get a slice when I just want to commit package with versioner?

by HernÃ¡n Morales Durand

Yes I experimented that one too, it's a classic :) To fix I used to close versioner, add the repository to package in the monticello, then open versioner again. HernÃ¡n 2015-08-01 17:08 GMT-03:00 stepharo <stepharo(a)free.fr>: > Hi > > I just wanted to save a configuration with versioner and now I'm asked > about a slice??? > No idea what this is and why I get that question (there is only slice in > the combo box choice). > > It would be good that we stabilise the tools. > > Stef > >

Aug. 1, 2015

Re: [Pharo-dev] Nautilus new buttons not buttons?

by stepharo

Le 1/8/15 13:54, Esteban Lorenzano a Ã©crit : > >> On 01 Aug 2015, at 13:25, Franck Warlouzet >> <franck.warlouzet(a)hotmail.fr <mailto:franck.warlouzet@hotmail.fr>> wrote: >> >> Hello, >> >> Yes it looks a little bit 'lite' but we did not want to have 2 >> buttons with the same look but two different kinds of actions. >> Hierarchy button changes the window itself and variable and scoped >> open a new menu or window. > > but they are buttons, then they should look like one. > alsoâ¦ âVariablesâ (button or whatever) there just do not make sense > (since is a âclassâ related action)â¦ it increases confusion instead > solving a problem. > we need a better general approach for those actions, maybe a toolbar > or something like thatâ¦ but as it is now it does not work. Yes we know. Now there is a difference between a button popping something and one just acting on the default browser. > > Esteban > >> >> I agree about the class side button. >> >> Franck >> >> ------------------------------------------------------------------------ >> Date: Sat, 1 Aug 2015 12:26:02 +0200 >> From:i.uhnak@gmail.com <mailto:i.uhnak@gmail.com> >> To:pharo-dev@lists.pharo.org <mailto:pharo-dev@lists.pharo.org> >> Subject: Re: [Pharo-dev] Nautilus new buttons not buttons? >> >> Speaking of buttons... The Hierarchy/Flat button and [] Class side >> isn't entirely consistent either. >> And since everyone is used to it by now nobody will want to change it. :) >> >> >> On Sat, Aug 1, 2015 at 12:21 PM, Peter UhnÃ¡k<i.uhnak(a)gmail.com >> <mailto:i.uhnak@gmail.com>>wrote: >> >> Hi, >> >> why are the new nautilus buttons not buttons? >> >> <2015-08-01_122023.png> >> â >> They look like labels which is confusing. >> >> Peter >> >

Aug. 1, 2015

why do I get a slice when I just want to commit package with versioner?

by stepharo

Hi I just wanted to save a configuration with versioner and now I'm asked about a slice??? No idea what this is and why I get that question (there is only slice in the combo box choice). It would be good that we stabilise the tools. Stef

Aug. 1, 2015

Using Kommiter I got a problem with diff morph and rubric

by stepharo

Hi frank when I tried to save a project, Kommiter is invoked and I got calibrateScrollbar "Set the scrollbar parameters to match the texts." | maxY range delta innerH | self fullBounds. maxY := self srcMorph extent y max: self dstMorph extent y. innerH := self dstMorph innerBounds height. delta := 91. "self dstMorph textMorph defaultLineHeight" range := maxY - innerH max: 0. range = 0 ifTrue: [ ^ self scrollbarMorph scrollDelta: 0.02 pageDelta: 0.2; interval: 1.0; setValue: 0.0 ]. self scrollbarMorph scrollDelta: (delta / range) asFloat pageDelta: ((innerH - delta) / range) asFloat; interval: (innerH / maxY) asFloat; setValue: ((self srcMorph scroller offset y max: self dstMorph scroller offset y) / range min: 1.0) asFloat ^^^^^^^ where srcMoirph is a RubScrolledTextMorph Stef

Aug. 1, 2015