- Pharo-dev - lists.pharo.org

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

by H. Hirzel

This worked fine. The code is very readable and easy to adapt once there is an example. Thank you. --Hannes On 8/1/15, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > 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. 3, 2015

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

by Esteban Lorenzano

I just talked with Franck and we agree on trying to move most of those functionality to a toolbarâ¦ letâs hope this solves our small problem :) Esteban > On 03 Aug 2015, at 01:06, Stephan Eggermont <stephan(a)stack.nl> wrote: > > On 01/08/15 13:25, Franck Warlouzet 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. >> >> I agree about the class side button. > > Every button in the Nautilus browser has lots of improvement potential. > > It should be visually clear where a button applies to. Scoped applies to the package pane, Variables to the class pane, Hierarchy/Flat to the class pane, Class side to the methods and methods category pane and comments to the text pane. The location of the buttons could reflect that. > > It should be visually clear if a button represents a direct action, an indirect action, shows a menu, represents a state change action or the current state or opens a menu > > The buttons should have hover texts explaining what the button does and when it is (and not) applicable. > > A button should react to left-click only, not to right-click (or with a menu to right click). > > And then there are also some Rubric widgets in the text pane that behave somewhat like buttons. > > And now for something completely different: > Why are the variables shown in reversed order? I rarely look for > users of DependentFields > > > Stephan > >

Aug. 3, 2015

WhatsUp from: 2015-08-03 until: 2015-08-16

by seaside＠rmod.lille.inria.fr

Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! ### Here's what I've been up to since the last WhatsUp: - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS ### What's next, until 2015-08-16 (*): - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION (*) we'll be expecting results by then ;)

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by Alexandre Bergel

Github is indeed appealing. Cheers, Alexandre > On Aug 2, 2015, at 10:14 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Tudor Girba-2 wrote >> Would you like to help us move the moose-technology project? > > Sure. What do you have in mind? It seems exporting to GitHub is the easiest > option. There are a few limitations, but I've had good experiences... > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 3, 2015

Re: [Pharo-dev] Google Code Shutdown

by Sean P. DeNigris

Tudor Girba-2 wrote > Would you like to help us move the moose-technology project? Sure. What do you have in mind? It seems exporting to GitHub is the easiest option. There are a few limitations, but I've had good experiences... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840733.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 3, 2015

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

by Stephan Eggermont

On 01/08/15 13:25, Franck Warlouzet 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. > > I agree about the class side button. Every button in the Nautilus browser has lots of improvement potential. It should be visually clear where a button applies to. Scoped applies to the package pane, Variables to the class pane, Hierarchy/Flat to the class pane, Class side to the methods and methods category pane and comments to the text pane. The location of the buttons could reflect that. It should be visually clear if a button represents a direct action, an indirect action, shows a menu, represents a state change action or the current state or opens a menu The buttons should have hover texts explaining what the button does and when it is (and not) applicable. A button should react to left-click only, not to right-click (or with a menu to right click). And then there are also some Rubric widgets in the text pane that behave somewhat like buttons. And now for something completely different: Why are the variables shown in reversed order? I rarely look for users of DependentFields Stephan

Aug. 2, 2015

Re: [Pharo-dev] [ann] jdt2famix - an open-source java importer project

by Tudor Girba

Hi (again), The project below is made possible by JNIPort. Thanks, Joachim! Cheers, Doru On Sun, Aug 2, 2015 at 11:26 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I would like to announce the jdt2famix project. This aims to be an > open-source solution for importing Java projects into Moose: > http://www.smalltalkhub.com/#!/~Moose/Jdt2Famix > > The project is based on: > - JDT for raw parsing. This is implemented in Java. > - JNIPort for delegating to Pharo the Java methods that visit the Java AST. > > Installation details can be found on the main project page. > > The current importing logic is rudimentary, but the first goal was to > setup the whole ping-pong between Pharo and Java. This one works, and I am > quite happy about that. You can take a look at the JdtImporterTest. > > CAVEATS: > - Due to a problem in JNIPort, currently, this project only works in Moose > 5.0. > - Also, for now it works out of the box only for Mac OS X. > - And, on top of that, it requires Java 1.6 for now (until we will get the > Spur VM on 64 bits). > > There are still quite some challenges left, but once we get this going, we > would also be able to use deep AST analysis live, and to do incremental > model update when something changes on disk. Furthermore, if it scales, > this would not be based on an intermediary MSE file anymore. > > I would like to ask for help in several directions: > 1. Implement the full model import. This would require diving into JDT and > implementing the corresponding mapping logic. I spent a few days on this. > It is hairy, but it is not that impossible (only it has a ton of edge > cases). This should be test driven, in that, for each case, we need to have > a corresponding sample. > 2. Fix JNIPort to work in Pharo 5. > 3. Get the whole thing to work out of the box for Linux and Windows. > 4. Check scalability. > > Please let me know your opinions, and let me know if you would like to > participate. > > Cheers, > Doru > > -- > www.tudorgirba.com > > "Every thing has its own flow" > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 2, 2015

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

by Esteban Lorenzano

> On 01 Aug 2015, at 22:45, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > > > On Sat, Aug 1, 2015 at 10:10 PM, stepharo <stepharo(a)free.fr <mailto:stepharo@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 <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. > > 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, +1000 is complete non-sense to change form of buttons just because they trigger a different action. basically, all rules of UI design are against it. Every year we have same discussion, and every year I point to the same readings: - âdonât make me thinkâ. https://en.wikipedia.org/wiki/Don%27t_Make_Me_Think <https://en.wikipedia.org/wiki/Don't_Make_Me_Think> - the mac UI design guidelines. https://developer.apple.com/library/mac/documentation/UserExperience/Concep… <https://developer.apple.com/library/mac/documentation/UserExperience/Concep…> there are many papers, research, etc. around this but wellâ¦ here is a *very* simplified summary of principles: http://web.cs.wpi.edu/~matt/courses/cs563/talks/smartin/int_design.html <http://web.cs.wpi.edu/~matt/courses/cs563/talks/smartin/int_design.html> And even more simplified: Coherence (same metaphor), organisation (same layout), uniqueness (same elements) So, a button is a button. If we present them as links, then ALL buttons should be a link. If they are âold-styleâ buttons, then ALL buttons should be old style. Esteban > > Peter

Aug. 2, 2015

Re: [Pharo-dev] Google Code Shutdown

by Tudor Girba

Hi Sean, Would you like to help us move the moose-technology project? Cheers, Doru On Sun, Aug 2, 2015 at 5:19 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Sean P. DeNigris wrote > > In case anyone hasn't heard, Google Code will shut down entirely on > > January 25, 2016. > > UPDATE: Impending Deadline: "Google Code will be turning read-only on > August > 25th" > > Already Moved: > magritte-metamodel > phratch > seaside > metacello > > Unknown: > moose-technology > marsonpharo > nativeboost > squeaksource3 > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Google-Code-Shutdown-tp4814760p4840717.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > -- www.tudorgirba.com "Every thing has its own flow"

Aug. 2, 2015

Re: [Pharo-dev] Google Code Shutdown

by Sean P. DeNigris

Sean P. DeNigris wrote > In case anyone hasn't heard, Google Code will shut down entirely on > January 25, 2016. UPDATE: Impending Deadline: "Google Code will be turning read-only on August 25th" Already Moved: magritte-metamodel phratch seaside metacello Unknown: moose-technology marsonpharo nativeboost squeaksource3 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Google-Code-Shutdown-tp4814760p4840717.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Aug. 2, 2015