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

Re: [Pharo-dev] request for improvements in GTInspector or debugger

by Christophe Demarey

Hi, > Le 10 aoÃ»t 2016 Ã 14:11, Tudor Girba <tudor(a)tudorgirba.com> a Ã©crit : > > Hi Stef, > > I agree with what you say in this mail, and I am not sure where this is not the case. By example, it is not available in a String presentation of GTInspector. This one always forces me to go to the raw presentation and use the comment. Would it be possible to use global shortcuts in String presentation (cmd+B, cmd+M, cmd+N, etc.)? Christophe

Aug. 11, 2016

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by stepharo

tx Bernhard. Indeed this is a nice suggestion. Le 10/8/16 Ã 20:41, Bernhard Pieber a Ã©crit : > And this is how it works in VA Smalltalk. The default shortcut to expand the abbreviations used there is Shift-Space. See this excellent video by the late James Robertson: https://www.youtube.com/watch?v=TY_rJ3G0Tn4 > > If the same default abbreviations were used as in VA Smalltalk, this would be even cooler. No need to relearn. > > Cheers, > Bernhard > >> Am 03.08.2016 um 10:56 schrieb Ben Coman <btc(a)openinworld.com>: >> >> On Wed, Aug 3, 2016 at 4:36 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> I will just re-post my first answer: >>> >>> if reintroduce them means reintroduce them hardcoded as before, then Iâm >>> complete against it and I WILL NOT integrate such solution. >>> Iâm sorry for being so strong here, but previous implementation was lame and >>> we need to get rid of them. >>> >>> Now, I understand people are used to use those bindings and also some others >>> (no idea which ones because I never used themâ¦ for me ocompletion is good >>> enoughâ¦ but those are tastes). So I would be very happy to integrate a >>> generic way to define keybindings and outputs (which is already there, with >>> keymapping, but I mean an editor or something), and I would be very happy to >>> integrate a default configuration (which of course, will include >>> #ifTrue:/##ifFalse:) >> I would guess code expansions could be many and varied between >> different individuals, and quickly consume available keyboard >> shortcuts. Perhaps a generic mechanism would be single shortcut for >> "code expansion" which processes the letters preceding the cursor. >> For example, using shortcut <ctrl-e> for code expansion and typing... >> >> itf<ctrl-e> >> >> ==> ifTrue: [ ] ifFalse: [ ] >> >> The could be an interface to define these code expansions - initially >> at least on a purely personal basis. >> >>> And this is not really for adding a new feature. This shortcut already (always :) ) existed >> With a single shortcut for code expansion, perhaps a few other >> existing combinations could be freed up. >> >> cheers -ben >> >>> Esteban >>> >>> On 03 Aug 2016, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >>> >>> >>> 2016-08-03 10:27 GMT+02:00 Guille Polito <guillermopolito(a)gmail.com>: >>>> I'm also against. >>>> >>>> - They take a place in the shortcuts that prevents others to use it >>>> - If lazy people really needs this, the code completion should be >>>> enhanced. This is a code completion concern... >>> >>> +1 >>> >>> > >

Aug. 10, 2016

Re: [Pharo-dev] ifTrue ifFalse shortcuts

by Bernhard Pieber

And this is how it works in VA Smalltalk. The default shortcut to expand the abbreviations used there is Shift-Space. See this excellent video by the late James Robertson: https://www.youtube.com/watch?v=TY_rJ3G0Tn4 If the same default abbreviations were used as in VA Smalltalk, this would be even cooler. No need to relearn. Cheers, Bernhard > Am 03.08.2016 um 10:56 schrieb Ben Coman <btc(a)openinworld.com>: > > On Wed, Aug 3, 2016 at 4:36 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> I will just re-post my first answer: >> >> if reintroduce them means reintroduce them hardcoded as before, then Iâm >> complete against it and I WILL NOT integrate such solution. >> Iâm sorry for being so strong here, but previous implementation was lame and >> we need to get rid of them. >> >> Now, I understand people are used to use those bindings and also some others >> (no idea which ones because I never used themâ¦ for me ocompletion is good >> enoughâ¦ but those are tastes). So I would be very happy to integrate a >> generic way to define keybindings and outputs (which is already there, with >> keymapping, but I mean an editor or something), and I would be very happy to >> integrate a default configuration (which of course, will include >> #ifTrue:/##ifFalse:) > > I would guess code expansions could be many and varied between > different individuals, and quickly consume available keyboard > shortcuts. Perhaps a generic mechanism would be single shortcut for > "code expansion" which processes the letters preceding the cursor. > For example, using shortcut <ctrl-e> for code expansion and typing... > > itf<ctrl-e> > > ==> ifTrue: [ ] ifFalse: [ ] > > The could be an interface to define these code expansions - initially > at least on a purely personal basis. > >> And this is not really for adding a new feature. This shortcut already (always :) ) existed > > With a single shortcut for code expansion, perhaps a few other > existing combinations could be freed up. > > cheers -ben > >> >> Esteban >> >> On 03 Aug 2016, at 10:30, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: >> >> >> 2016-08-03 10:27 GMT+02:00 Guille Polito <guillermopolito(a)gmail.com>: >>> >>> I'm also against. >>> >>> - They take a place in the shortcuts that prevents others to use it >>> - If lazy people really needs this, the code completion should be >>> enhanced. This is a code completion concern... >> >> >> +1 >> >> >

Aug. 10, 2016

Re: [Pharo-dev] GT-Spotter dive in shortcut

by Tudor Girba

Oh man :). Ok I think got it now. Thanks for the patience. I see the confusion: the agreement was that we will override the shortcut in the Spotter text-input. So, letâs go for this. The layering thing was supposed to be a separate issue. Cheers, Doru > On Aug 10, 2016, at 12:05 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-08-09 23:36 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > Hi, > > > On Aug 9, 2016, at 11:31 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > > > > > 2016-08-09 22:53 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > > Hi, > > > > > On Aug 9, 2016, at 10:48 PM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > > > > > > > > > 2016-08-09 18:12 GMT+02:00 Tudor Girba <tudor(a)tudorgirba.com>: > > > Hi, > > > > > > > > > > > Hey Doru, > > > > about what "two issues" are we talking? My only issue for now is, > > > > what shortcut shold we use for moving the cursor forward/backward word. Even if we introduce a new layer, at some point in time you need to > > > > define: If the user types the CTRL+LEFT -key, even if we call it differently, some action happens, dive-out or move-backward-word ? > > > > At the moment (on windows) you can use both to move word-by-word: > > > > ctrl+left/right and alt+left/right, because this is how it is defined in rubrics action/cmdaction map. > > > > > > > > If we want to clean this up and use the kmdispatcher registration, I think we don't want to use both ctr and alt again, right? > > > > So, someone has to take the decision. > > > > I myself would prefer > > > > ctrl+left/right because this is what (all) many other programs are using on windows. Fine. But recently Spotter changed its > > > > dive in / dive out shortcut to use ctrl+left/right. > > > > Therefor I am asking you, why, and whether we want to keep it or not. If we want to keep it, we may > > > > - just overwrite the binding for the textfield -> not good, I think, you wouldn't be able to do word-by-word movements in the textfield anymore > > > > - overwrite the binding and use another binding for word-by-word moving, but just in spotters text field > > > > Or we revert that change and use the old shortcuts again. > > > > (And what to use for mac and linux?) > > > > > > > > but I am getting really tired of asking, and will do something else instead. > > > > > > The short answer: we will override the keybinding in the text morph for now. This will mean that we cannot move word by word in the text field using #control, but it will be consistent with all other platforms. Could you open an issue for this, please? > > > > > > > > > consistens on all platforms may not be the expectation for all users. Some users only working on a windows platform may want to have consistent behavior for all tools (applications). > > > > Well, you wanted a decision :). > > > > > > > On top of that, we will externalize all GTSpotter shortcuts through settings: > > > https://pharo.fogbugz.com/f/cases/18455/Spotter-shortcuts-should-be-externa… > > > > > > I really don't know why that. > > > > Because we do not have a generic KMDispatcher mechanism :). > > > > yes and it does not make much sense as not all shortcuts are handled by the kmdispatcher, thats why cleaning this > > up and I think it would be better to do this instead of implementing yet another only-for-this-tool solution. > > Ok. What should I do? > > > > > We don't need a way to make Spotter shortcuts configurable, but *all* shortcuts. > > > That is why I try to move all shortcut definitions to the kmdispatcher, but it yet again took 2 month just to discuss what shortcut to use for cursor movement. > > > > I am not sure I understand. Was this me that stalled the discussion? If yes, it was not intentional. Is there anything I can do about this subject? > > > > The whole discussion, the me: "hey, what shortcut to use?" you:"hey we have a great idea, just let us add some new layers" :( > > I think I miss something because I do not see how the layers have anything to do with the cursor movement. Or do you mean for diving in Spotter? I still think that the layers idea is a relevant one and does not conflict with anything we talked about here. > > Ok once again. > ctrl+arrow and meta+arrow both do cursor movements in rubrik, but it is registered on the action/cmd-map (RubTextEditor>>defaultCommandKeymapping) > ctrl+arrow do dive-in/dive-out in spotter, this is registered on spotters window, and this takes precedence over rubrics crtrl+Arrow handling because : > > 1. kmdispatcher looks in rubrics editor kmregistry -> no action > 2. kmdispatcher looks in rubrics morph kmregistry -> no action > .... up the morphs owner chain until it reaches spotter > x. kmdispatcher looks in spotters window morph kmregistry -> Action! Dive-in / Dive-out > > Now! If I move ctrl+Arrow shortcut registration for cursor movement from rubrics action/-cmd-map to its kmdispatcher registration, the following happens > 1. kmdispatcher looks in rubrics editor kmregistry -> Action ! move the cursor > > -> no spotter dive-in/dive-out anymore :-( > > two solutions: > use a different shortcut for cursor movement (that is what I aksed in this thread, and why I opened issue 18432) > use a different shortcut for spotter (this is why I started this thread and asked why this was changed at all) > overwrite spotters shortcut registration (just like now, but not on spotters window, but on the text field (I opened now a fogbugz issue 18900)) > > anyway, you said, you want to wait with changing spotters shortcut registration until we have the new layers, therefore I can only wait until that > happens. > > > > > In any case, I did not mean to confuse anyone. Please take the lead concerning the KMDispatcher and I can review if you want. > > Doru > > > > > Cheers, > > Doru > > > > > > > > > > Long answer: As explained before, the shortcut changed in the process of making all shortcuts uniform when Guille introduced #meta instead of #command (like it was before). The thing is that currently: > > > - #command means #alt on Win and #command on Mac, and > > > - #meta means #control on Win and #command on Mac. > > > > > > But, #command should be a low level key, not a portable one. It should not have a meaning on Windows, because the key does not exist on that platform. > > > > > > Moving to make keybindings uniform is a good thing, but only having #meta is not enough for situation like the one you mention. That is why I am proposing to introduce a #secondaryMeta as a platform-independent modifier that would mean #alt on Win and #control on Mac. We could use that one more consistently. Is this a better explanation? > > > > > > Cheers, > > > Doru > > > > > > > > > -- > > > www.tudorgirba.com > > > www.feenk.com > > > > > > "Presenting is storytelling." > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "One cannot do more than one can do." > > -- > www.tudorgirba.com > www.feenk.com > > "When people care, great things can happen." -- www.tudorgirba.com www.feenk.com "Problem solving efficiency grows with the abstractness level of problem understanding."

Aug. 10, 2016

Feedback request: Editor with highlighting message-sends on mouse over

by Nicolai Hess

I opened an issue 18901 <https://pharo.fogbugz.com/f/cases/18901/Highlight-message-send-selector-on-…> Highlight message send selector on mouse over with an experimental implementation. Just load the slice, enable the setting: RubAbstractTextArea highlightMessageSend: true. Now open a code editor (nautilus/MessageBrowser) and move the mouse over a message send. Or evaluate this code, it opens a text editor on a method, where it is difficult to see which part of the code belongs to which method: evaluate: TextModel new beForCode; aboutToStyle:true;behavior: MorphTreeMorph;text:(MorphTreeMorph>>#drawLinesOn:) sourceCode;openWithSpec. feedback welcome. nicolai

Aug. 10, 2016

Re: [Pharo-dev] request for improvements in GTInspector or debugger

by Tudor Girba

Hi Stef, I agree with what you say in this mail, and I am not sure where this is not the case. And I also do not understand how this relates to the previous message which was about manipulating the list of items (I guess in a collection). Nobody argues that you have to go through Spotter if you have what you want in front of you :). Spotter, in its current form, is meant for finding an entry into the system if you do not have it. The end goal is to have as much direct manipulation of objects as possible, and if we find a place where this is not the case, we have to improve it. Could you re-detail the original problem? Cheers, Doru > On Aug 10, 2016, at 9:43 AM, stepharo <stepharo(a)free.fr> wrote: > > Hi sven > > > This is not the same. I do not need a menu or a button. > I took the class of the instance as an example. > Check deeply what I mentioned: > > - you have text > > - what can we do on text usually: edit, change and more important use it to query the system > > hyperfast (and here suddenly we cannot we can select edit the text but not use shortcut to navigate no senders/imp/class). > > > This is a question of interface and the uniformity of the interface (this is like the grab icon in mac for file on the window). > > In Pharo in any text pane of the tools we can query and this is an important property. > For example I can select a comment in the monticello pane and browse look for code - no need for Spotter. > The text is under my nose and I can get to the class instantaneously. > Now if the vision of Pharo is not to follow this tradition to immediate and superclose access to code, let me know > > because this is an important (crucial) aspect for me and I used it all the time. > > Stef > > > Le 9/8/16 Ã 19:44, Sven Van Caekenberghe a Ã©crit : >> You can already do that: click the icon at the top right of the window 'Browse': >> >> <Mail Attachment.png> >>> On 09 Aug 2016, at 19:23, stepharo <stepharo(a)free.fr> wrote: >>> >>> Here is my scenario. >>> >>> I have a field that contains aCZWhatever >>> >>> the inspector shows me a list >>> >>> >>> field aCZWhatever >>> >>> I can edit the aCZWhatever since I can click on it and get an input fiedl (or what I thought is an input field). >>> >>> I can select CZWhatever but I cannot do browse on it. So I have to use Spotter. >>> >>> >>> Stef >>> >>> >> > -- www.tudorgirba.com www.feenk.com "Obvious things are difficult to teach."

Aug. 10, 2016

Re: [Pharo-dev] Iceberg in general

by Nicolas Passerini

Issue #111 <https://github.com/npasserini/iceberg/issues/111> is fixed and included in github://npasserini/iceberg:0.2.1 (or github://npasserini/iceberg:stable). Thanks for reporting it. On Tue, Aug 9, 2016 at 2:34 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: > > I can not tell if it would work on Pharo 5.0. > > I using IceBerg on Pharo 5. > > On Tue, Aug 9, 2016 at 2:10 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > >> I've checked again on pharo6 and get the same error. >> >> - downloaded pharo6 >> >> - Metacello new >> baseline: 'Iceberg'; >> repository: 'github://npasserini/iceberg:stable'; >> load. >> >> - openend UI via tools/Iceberg >> >> - click "Clone new repository" >> >> Same error as in pharo5. Cannot parse URL >> >> I've created an issue >> >> Norbert >> >> Am 09.08.2016 um 14:00 schrieb Nicolas Passerini <npasserini(a)gmail.com>: >> >> Hi Norbert, >> >> Up to date, Iceberg has only been developed/used/tested on Pharo 6.0, >> please look at the prerrequisites in https://github.com/npasserini/ >> iceberg. I can not tell if it would work on Pharo 5.0. >> >> Either way, if you could submit a bug report I will happily pay a look at >> it. >> >> On Tue, Aug 9, 2016 at 1:55 PM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >>> >>> >>> On Tue, Aug 9, 2016 at 1:39 PM, Norbert Hartl <norbert(a)hartl.name> >>> wrote: >>> >>>> I'm using pharo5 and I wonder we is this version marked as stable >>> >>> >>> The readme states: >>> >>> "This is still a prototype and is not yet ready for production, but you >>> are invited to try it and provide feedback. " >>> >>> Note however that I've successfully started using it for smaller >>> project(s) that are hosted on GitHub. Of course there's a lot of issues >>> https://github.com/npasserini/iceberg/issues , but it can be forced to >>> work if you are willing to live on the edge. :) >>> >>> Regarding your error, it would be best to submit a bug report. >>> >>> Peter >>> >> >> >> >

Aug. 10, 2016

Re: [Pharo-dev] request for improvements in GTInspector or debugger

by Sven Van Caekenberghe

I too think that selecting some arbitrary text should make it possible to do useful things with it, like looking it up as class, method, ... - I like Command-Click rather a lot for this. In the last years, some panes where switched away from code panes, maybe that does not help. Apart from that, I think there should be an option to invoke Spotter directly on a selection (or even auto select something and search). > On 10 Aug 2016, at 09:43, stepharo <stepharo(a)free.fr> wrote: > > Hi sven > > > This is not the same. I do not need a menu or a button. > I took the class of the instance as an example. > Check deeply what I mentioned: > > - you have text > > - what can we do on text usually: edit, change and more important use it to query the system > > hyperfast (and here suddenly we cannot we can select edit the text but not use shortcut to navigate no senders/imp/class). > > > This is a question of interface and the uniformity of the interface (this is like the grab icon in mac for file on the window). > > In Pharo in any text pane of the tools we can query and this is an important property. > For example I can select a comment in the monticello pane and browse look for code - no need for Spotter. > The text is under my nose and I can get to the class instantaneously. > Now if the vision of Pharo is not to follow this tradition to immediate and superclose access to code, let me know > > because this is an important (crucial) aspect for me and I used it all the time. > > Stef > > > Le 9/8/16 Ã 19:44, Sven Van Caekenberghe a Ã©crit : >> You can already do that: click the icon at the top right of the window 'Browse': >> >> <Mail Attachment.png> >>> On 09 Aug 2016, at 19:23, stepharo <stepharo(a)free.fr> wrote: >>> >>> Here is my scenario. >>> >>> I have a field that contains aCZWhatever >>> >>> the inspector shows me a list >>> >>> >>> field aCZWhatever >>> >>> I can edit the aCZWhatever since I can click on it and get an input fiedl (or what I thought is an input field). >>> >>> I can select CZWhatever but I cannot do browse on it. So I have to use Spotter. >>> >>> >>> Stef >>> >>> >> >

Aug. 10, 2016

Re: [Pharo-dev] request for improvements in GTInspector or debugger

by stepharo

Hi sven This is not the same. I do not need a menu or a button. I took the class of the instance as an example. Check deeply what I mentioned: - you have text - what can we do on text usually: edit, change and more important use it to query the system hyperfast (and here suddenly we cannot we can select edit the text but not use shortcut to navigate no senders/imp/class). This is a question of interface and the uniformity of the interface (this is like the grab icon in mac for file on the window). In Pharo in any text pane of the tools we can query and this is an important property. For example I can select a comment in the monticello pane and browse look for code - no need for Spotter. The text is under my nose and I can get to the class instantaneously. Now if the vision of Pharo is not to follow this tradition to immediate and superclose access to code, let me know because this is an important (crucial) aspect for me and I used it all the time. Stef Le 9/8/16 Ã 19:44, Sven Van Caekenberghe a Ã©crit : > You can already do that: click the icon at the top right of the window > 'Browse': > > >> On 09 Aug 2016, at 19:23, stepharo <stepharo(a)free.fr >> <mailto:stepharo@free.fr>> wrote: >> >> Here is my scenario. >> >> I have a field that contains aCZWhatever >> >> the inspector shows me a list >> >> >> field aCZWhatever >> >> I can edit the aCZWhatever since I can click on it and get an input >> fiedl (or what I thought is an input field). >> >> I can select CZWhatever but I cannot do browse on it. So I have to >> use Spotter. >> >> >> Stef >> >> >

Aug. 10, 2016

Re: [Pharo-dev] let's talk about themes (and GLMBrickThemer)

by stepharo

Le 9/8/16 Ã 21:15, Tudor Girba a Ã©crit : > Hi, > > We would definitely benefit from a Palette. > > One interesting concepts in Bloc2 is that the concrete values are injected in the widget, instead of having the widget ask for it. This is bit similar to settings. A component should have its settings as variables and values get pushed inside instead of asking a a large facade like systempreferences. > This is quite powerful because it enables a CSS mechanism (or another one), but we also have to see how it works with the requirement of changing these values dynamically. This will certainly be a next step after the core is stable. > > Cheers, > Doru > > >> On Aug 9, 2016, at 3:03 PM, stepharo <stepharo(a)free.fr> wrote: >> >> Hi doru >> >> I think that this is particularly true (having a themer per widget) when the themer is more a skinner (it changes behavior of the widgets), else we could have addressed the problem with a solution close to setting. Two years ago I played with theming and widgets hierarchy and I came to the same conclusion (that your blog entries). >> Do you know how they do it in JavaFX? >> I agree also that we should extract the Palette. >> Now I'm really curious to see the CSS of Glenn in Bloc2. >> Stef >> >> Le 4/8/16 Ã 12:52, Tudor Girba a Ã©crit : >>> Hi Esteban, >>> >>> Sorry for the delayed response. >>> >>> There are two parts in your mail: >>> 1. the decomposition of theme to have one themer per widget >>> 2. a centralized catalog of values >>> >>> I certainly agree with 2. In fact, when I refactored the theme colors a long time ago, I introduced a rudimentary reuse mechanism on the class side of the Theme class. So, now, we should extract those separately. >>> >>> About 1., I have a different opinion. The hierarchy you mention already exists in the Theme class as well, only it is hidden, and it is very hard to see what each methods impacts. >>> >>> Here is how I reached this conclusion. Take a look at this picture I produced before we started with Brick (the one from Morphic). The gray circles are methods in UITheme, and the red circles are typical Morphs (like TextMorph, ListMorph). The gray lines show self calls inside the UITheme, and the red lines shod calls from the morph to the UITheme methods. What you see here is a very strong clustering of the methods around the widgets, and this indicates that having a theme object per widget is appropriate. >>> >>> >>> <Mail Attachment.png> >>> >>> >>> A further constrain is that we want to be able to change the appearance of a widget on an instance basis (that is, overriding the default theme setting), and having a per-widget themer object, we can achieve that as well. >>> >>> A similar design appears in Bloc as well, and I think it is actually more scalable then the current UITheme, provided that you indeed have a way to either centralize the definitions of colors (and other properties), or inject those properties from the outside. >>> >>> All in all, letâs go ahead and extract the palette :). >>> >>> Cheers, >>> Doru >>> >>> >>>> On Aug 1, 2016, at 11:13 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>>> >>>> Hi, >>>> >>>> For one of my side-projects, I made a new theme for Pharo (still no name, I was planing to call it âDark Metalâ or something like that. Is a variation on the Dark Theme but âourâ dark theme is more brown and this one is more blue (see attached)â¦ I wanted to publish it to push it but then I arrived to an unexpected problem: For Spotter and GTTools in general, theming is not done following current theming approach. Instead, they made a full hierarchy of objects. >>>> >>>> IMO this is plain bad. I understand the attempt to decouple, but now that means if I want to create a new theme, I need to create my theme object with colors I want and then also I need to create an undetermined number of classes (at least one for each tool, but there is also a hierarchy of things there)â¦ anyway, this DOES NOT scale. Because each tool will have to have a âtheme classâ for each existing themeâ¦ >>>> How themes (skins, bah) work in all word is to have a color palette and then tools takes them (they can âplayâ a bit with this palette, but need to always respect the palette). >>>> >>>> Then, I will commit a SLICE modifying the âthemerâ classes to take colors from the current theme (instead of have them hardcoded). >>>> But of course, how theme work now is not good because they mix âthemeâ (how they display) and âskinâ (color palette). I will also extract the palette to where should have always been (some kind of a style sheet object)â¦ who also should have been editable in settings so people can tweak their configuration. >>>> >>>> I didnât wanted to touch this before, because this will supposedly change with brick, but honestly this will not be ready for Pharo 6 and this is annoying (also, I want to publish my theme and I do not want to add overrides all around :P) >>>> >>>> cheers, >>>> Esteban >>>> >>>> >>>> <Screen Shot 2016-08-01 at 11.00.15.png> >>> -- >>> www.tudorgirba.com >>> www.feenk.com >>> >>> "Innovation comes in the least expected form. >>> That is, if it is expected, it already happened." >>> > -- > www.tudorgirba.com > www.feenk.com > > "To lead is not to demand things, it is to make them happen." > > > > > >

Aug. 10, 2016