- Pharo-dev - lists.pharo.org

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

by Esteban Lorenzano

> On 02 Aug 2016, at 08:59, stepharo <stepharo(a)free.fr> wrote: > > Hi esteban > > It looks cool. For the error could you use a different one because I cannot read it. > Else when I tried to use the same way than Setting to manage skins it did not work > because theming is a lot of things: - a skin - a color palette - etc. for now, I would be happy with extract the color palette into a âStyleSheetâ objectâ¦ this could be modified in settings (while a complete skin not). Esteban > because a skin is not just color it can be behavior and you have to attach it somewhere. > Now in bloc 2 :) > > you can the look (that can be expressed with CSS) > > and you have skins (the behavior: a date can be displayed as a calendar vs. a roller). > In this model a theme (color) will just be similar to applying a new CSS. > Stef > > Le 1/8/16 Ã 11:13, Esteban Lorenzano a Ã©crit : >> 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 >> >> >> <Mail Attachment.png> >

Aug. 2, 2016

Re: [Pharo-dev] Odd Commits to Soup Repo

by Cyril Ferlicot Delbecque

On 02/08/2016 09:03, stepharo wrote: > Hi Paul > > It never works with me. Did you check that the file is really not there > after. > Hi, Since I am a little scatterbrained it happen to me all the time to commit in the wrong repo, so I delete those wrong .mcz and it works fine. > Stef > > -- Cyril Ferlicot http://www.synectique.eu 165 Avenue Bretagne Lille 59000 France

Aug. 2, 2016

Re: [Pharo-dev] Odd Commits to Soup Repo

by stepharo

Hi Paul It never works with me. Did you check that the file is really not there after. Stef Le 28/7/16 Ã 22:26, Paul DeBruicker a Ã©crit : > Sure you can delete mcz from Smalltalkhub. Or at least the Web UI offers a > 'Delete .mcz' button, which appears to work. > > Sign in > Navigate to the project > Click on Commits > Find the MCZ you want to delete > Click the name of the MCZ > Click the "Delete .mcz" button > > > It should then be deleted. > > As a test I deleted > ConfigurationOfAutomaticMethodCategorizer-StephaneDucasse.4, > Pharo-Launcher-Core-DamienCassou.21, and > ConfigurationOfPharoLauncher-DamienCassou.9 from the PharoExtras/Soup repo > > Or did you mean something else? > > > > > Hope this helps > > > Paul > > > > > > stepharo wrote >> Yes but we cannot remove file in Smalltalkhub repo. >> >> >> Stef >> >> >> Le 28/7/16 Ã 18:47, Sean P. DeNigris a Ã©crit : >>> I found ConfigurationOfPharoLauncher-DamienCassou.9 & >>> Pharo-Launcher-Core-DamienCassou.21 there. I assume they were uploaded by >>> mistake... >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: >>> http://forum.world.st/Odd-Commits-to-Soup-Repo-tp4908492.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> >>> > > > > > -- > View this message in context: http://forum.world.st/Odd-Commits-to-Soup-Repo-tp4908492p4908538.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

Aug. 2, 2016

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

by stepharo

> > One good thing about Pharo is that one can make the environment one's > own. > But most of the time, this starts with the colors, and one hits a > brick wall. > > I just can't help thinking about pieces of software like WinAmp where > one could do theming easily, adding plugins with ease etc. > > A lot of editors these days do it all with CSS and similar tech, > blowing us out of the water on that front. Yes this is what Bloc2 does too. > Generally speaking, with the new Pharo (like 4.x, 5,x, 6,x), I face a > more difficult system to get into (despite all the cool things Spotter > allows). > > Somedays, I am wondering if we aren't actively keeping people out. You mean over engineering I'm fighting against it. > > Phil > > > On Mon, Aug 1, 2016 at 11:13 AM, Esteban Lorenzano > <estebanlm(a)gmail.com <mailto:estebanlm@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 > > >

Aug. 2, 2016

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

by stepharo

Hi esteban It looks cool. For the error could you use a different one because I cannot read it. Else when I tried to use the same way than Setting to manage skins it did not work because a skin is not just color it can be behavior and you have to attach it somewhere. Now in bloc 2 :) you can the look (that can be expressed with CSS) and you have skins (the behavior: a date can be displayed as a calendar vs. a roller). In this model a theme (color) will just be similar to applying a new CSS. Stef Le 1/8/16 Ã 11:13, Esteban Lorenzano a Ã©crit : > 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 > >

Aug. 2, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60160 Home: https://github.com/pharo-project/pharo-core

Aug. 1, 2016

[pharo-project/pharo-core] 0187fe: 60160

by GitHub

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 0187fe5e3366dd78edbbe4178e655dca0c1b5366 https://github.com/pharo-project/pharo-core/commit/0187fe5e3366dd78edbbe417… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-08-01 (Mon, 01 Aug 2016) Changed paths: M Metacello-MC.package/MetacelloPackageSpec.class/instance/gofer/workingCopyNameFor_.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60159.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60160.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60159.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60160.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Examples.package/ApplicationWithToolbar.class/README.md A Spec-Examples.package/ApplicationWithToolbar.class/class/example/example.st M Spec-Examples.package/CheckBoxExample.class/README.md M Spec-Examples.package/CheckBoxExample.class/class/example/example.st A Spec-Examples.package/CheckBoxExample.class/class/specs/defaultSpec3.st M Spec-Examples.package/CheckBoxExample.class/instance/initialization/setGroup.st M Spec-Examples.package/ClassMethodBrowser.class/README.md M Spec-Examples.package/ClassMethodBrowser.class/class/example/example.st M Spec-Examples.package/ClassMethodBrowser.class/instance/initialization/initializeWidgets.st M Spec-Examples.package/CustomerStatisfaction.class/class/example/example.st M Spec-Examples.package/CustomerStatisfaction.class/class/example/exampleDialog.st M Spec-Examples.package/CustomerStatisfaction.class/class/example/exampleNewLayout.st M Spec-Examples.package/DropListExample.class/README.md M Spec-Examples.package/DropListExample.class/class/example/example.st M Spec-Examples.package/DynamicSpecExample.class/README.md A Spec-Examples.package/DynamicSpecExample.class/class/example/exampleInt.st A Spec-Examples.package/DynamicSpecExample.class/class/example/exampleNil.st A Spec-Examples.package/DynamicSpecExample.class/class/example/exampleString.st M Spec-Examples.package/DynamicSpecExample.class/definition.st A Spec-Examples.package/DynamicSpecExample.class/instance/protocol/openOnInteger_.st M Spec-Examples.package/DynamicSpecExample.class/instance/protocol/openOnNil.st A Spec-Examples.package/DynamicSpecExample.class/instance/protocol/openOnString_.st A Spec-Examples.package/DynamicSpecExample.class/instance/protocol/open_.st M Spec-Examples.package/DynamicWidgetChange.class/README.md A Spec-Examples.package/DynamicWidgetChange.class/class/example/example.st M Spec-Examples.package/DynamicalPopup.class/class/example/exampleAlternativeToolbar.st M Spec-Examples.package/DynamicalPopup.class/class/example/exampleDefaultToolbar.st M Spec-Examples.package/ListSelectionModel.class/README.md A Spec-Examples.package/ListSelectionModel.class/class/example/example.st M Spec-Examples.package/MethodBrowser.class/README.md M Spec-Examples.package/MethodBrowser.class/class/example/example.st M Spec-Examples.package/MethodBrowser.class/instance/initialization/initializeWidgets.st M Spec-Examples.package/ModelList.class/README.md A Spec-Examples.package/ModelList.class/class/examples/example.st M Spec-Examples.package/ModelList.class/definition.st A Spec-Examples.package/OpenOnIntExample.class/README.md A Spec-Examples.package/OpenOnIntExample.class/class/examples/example.st A Spec-Examples.package/OpenOnIntExample.class/class/instantiation/new_.st A Spec-Examples.package/OpenOnIntExample.class/class/specs/defaultSpec.st A Spec-Examples.package/OpenOnIntExample.class/definition.st A Spec-Examples.package/OpenOnIntExample.class/instance/accessing/minus.st A Spec-Examples.package/OpenOnIntExample.class/instance/accessing/plus.st A Spec-Examples.package/OpenOnIntExample.class/instance/accessing/text.st A Spec-Examples.package/OpenOnIntExample.class/instance/accessing/title.st A Spec-Examples.package/OpenOnIntExample.class/instance/initialization/initializePresenter.st A Spec-Examples.package/OpenOnIntExample.class/instance/initialization/initializeWidgets.st A Spec-Examples.package/OpenOnIntExample.class/instance/initialization/initialize_.st A Spec-Examples.package/OpenOnNilExample.class/README.md A Spec-Examples.package/OpenOnNilExample.class/class/examples/example.st A Spec-Examples.package/OpenOnNilExample.class/class/specs/defaultSpec.st A Spec-Examples.package/OpenOnNilExample.class/definition.st A Spec-Examples.package/OpenOnNilExample.class/instance/accessing/text.st A Spec-Examples.package/OpenOnNilExample.class/instance/accessing/title.st A Spec-Examples.package/OpenOnNilExample.class/instance/initialization/initializeWidgets.st A Spec-Examples.package/OpenOnNilExample.class/instance/initialization/initialize_.st A Spec-Examples.package/OpenOnStringExample.class/README.md A Spec-Examples.package/OpenOnStringExample.class/class/examples/example.st A Spec-Examples.package/OpenOnStringExample.class/class/instantiation/new_.st A Spec-Examples.package/OpenOnStringExample.class/class/specs/bottomLayout.st A Spec-Examples.package/OpenOnStringExample.class/class/specs/defaultSpec.st A Spec-Examples.package/OpenOnStringExample.class/definition.st A Spec-Examples.package/OpenOnStringExample.class/instance/accessing/button.st A Spec-Examples.package/OpenOnStringExample.class/instance/accessing/check.st A Spec-Examples.package/OpenOnStringExample.class/instance/accessing/input.st A Spec-Examples.package/OpenOnStringExample.class/instance/accessing/label.st A Spec-Examples.package/OpenOnStringExample.class/instance/accessing/textToReset.st A Spec-Examples.package/OpenOnStringExample.class/instance/accessing/title.st A Spec-Examples.package/OpenOnStringExample.class/instance/as yet unclassified/openOnString.st A Spec-Examples.package/OpenOnStringExample.class/instance/initialization/initializePresenter.st A Spec-Examples.package/OpenOnStringExample.class/instance/initialization/initializeWidgets.st A Spec-Examples.package/OpenOnStringExample.class/instance/initialization/initialize_.st M Spec-Examples.package/ProtocolBrowser.class/README.md A Spec-Examples.package/ProtocolBrowser.class/class/examples/example.st M Spec-Examples.package/ProtocolBrowser.class/definition.st M Spec-Examples.package/ProtocolList.class/README.md A Spec-Examples.package/ProtocolList.class/class/examples/example.st M Spec-Examples.package/ProtocolList.class/definition.st M Spec-Examples.package/ProtocolViewer.class/README.md A Spec-Examples.package/ProtocolViewer.class/class/examples/example.st M Spec-Examples.package/ProtocolViewer.class/definition.st M Spec-Examples.package/RadioButtonGroupExample.class/README.md M Spec-Examples.package/RadioButtonGroupExample.class/class/example/example.st M Spec-Examples.package/RadioButtonGroupExample.class/instance/initialization/initializeWidgets.st M Spec-Examples.package/RadioButtonGroupExample.class/instance/initialization/setGroup.st M Spec-Examples.package/ScrollSyncExample.class/README.md M Spec-Examples.package/ScrollSyncExample.class/class/example/example.st M Spec-Examples.package/ScrollSyncExample.class/class/specs/defaultSpec.st M Spec-Examples.package/ScrollSyncExample.class/instance/initialization/initialize.st M Spec-Examples.package/ScrollSyncExample.class/instance/layouts/defaultSpecLayout.st M Spec-Examples.package/ScrollSyncExample.class/instance/private/syncMorphPosition.st M Spec-Examples.package/TabsExample.class/README.md A Spec-Examples.package/TabsExample.class/class/examples/example.st A Spec-Examples.package/TextFieldExample.class/class/example/example.st A Spec-Tests.package/ApplicationWithToolbarTest.class/README.md A Spec-Tests.package/ApplicationWithToolbarTest.class/definition.st A Spec-Tests.package/ApplicationWithToolbarTest.class/instance/running/classToTest.st A Spec-Tests.package/CheckBoxExampleTest.class/README.md A Spec-Tests.package/CheckBoxExampleTest.class/definition.st A Spec-Tests.package/CheckBoxExampleTest.class/instance/running/classToTest.st A Spec-Tests.package/ClassMethodBrowserTest.class/README.md A Spec-Tests.package/ClassMethodBrowserTest.class/definition.st A Spec-Tests.package/ClassMethodBrowserTest.class/instance/running/classToTest.st A Spec-Tests.package/CustomerStatisfactionTest.class/README.md A Spec-Tests.package/CustomerStatisfactionTest.class/definition.st A Spec-Tests.package/CustomerStatisfactionTest.class/instance/running/classToTest.st A Spec-Tests.package/CustomerStatisfactionTest.class/instance/tests/testExampleDialog.st A Spec-Tests.package/CustomerStatisfactionTest.class/instance/tests/testExampleNewLayout.st A Spec-Tests.package/DropListExampleTest.class/README.md A Spec-Tests.package/DropListExampleTest.class/definition.st A Spec-Tests.package/DropListExampleTest.class/instance/running/classToTest.st A Spec-Tests.package/DynamicWidgetChangeTest.class/README.md A Spec-Tests.package/DynamicWidgetChangeTest.class/definition.st A Spec-Tests.package/DynamicWidgetChangeTest.class/instance/running/classToTest.st A Spec-Tests.package/DynamicalPopupTest.class/README.md A Spec-Tests.package/DynamicalPopupTest.class/definition.st A Spec-Tests.package/DynamicalPopupTest.class/instance/running/classToTest.st A Spec-Tests.package/DynamicalPopupTest.class/instance/tests/testExampleAlternativeToolbar.st A Spec-Tests.package/DynamicalPopupTest.class/instance/tests/testExampleDefaultToolbar.st A Spec-Tests.package/ListSelectionModelTest.class/README.md A Spec-Tests.package/ListSelectionModelTest.class/definition.st A Spec-Tests.package/ListSelectionModelTest.class/instance/running/classToTest.st A Spec-Tests.package/MethodBrowserTest.class/README.md A Spec-Tests.package/MethodBrowserTest.class/definition.st A Spec-Tests.package/MethodBrowserTest.class/instance/running/classToTest.st A Spec-Tests.package/ModelListTest.class/README.md A Spec-Tests.package/ModelListTest.class/definition.st A Spec-Tests.package/ModelListTest.class/instance/running/classToTest.st A Spec-Tests.package/OpenOnIntExampleTest.class/README.md A Spec-Tests.package/OpenOnIntExampleTest.class/definition.st A Spec-Tests.package/OpenOnIntExampleTest.class/instance/running/classToTest.st A Spec-Tests.package/OpenOnNilExampleTest.class/README.md A Spec-Tests.package/OpenOnNilExampleTest.class/definition.st A Spec-Tests.package/OpenOnNilExampleTest.class/instance/running/classToTest.st A Spec-Tests.package/OpenOnStringExampleTest.class/README.md A Spec-Tests.package/OpenOnStringExampleTest.class/definition.st A Spec-Tests.package/OpenOnStringExampleTest.class/instance/running/classToTest.st A Spec-Tests.package/ProtocolBrowserTest.class/README.md A Spec-Tests.package/ProtocolBrowserTest.class/definition.st A Spec-Tests.package/ProtocolBrowserTest.class/instance/running/classToTest.st A Spec-Tests.package/ProtocolListTest.class/README.md A Spec-Tests.package/ProtocolListTest.class/definition.st A Spec-Tests.package/ProtocolListTest.class/instance/running/classToTest.st A Spec-Tests.package/ProtocolViewerTest.class/README.md A Spec-Tests.package/ProtocolViewerTest.class/definition.st A Spec-Tests.package/ProtocolViewerTest.class/instance/running/classToTest.st A Spec-Tests.package/RadioButtonGroupExampleTest.class/README.md A Spec-Tests.package/RadioButtonGroupExampleTest.class/definition.st A Spec-Tests.package/RadioButtonGroupExampleTest.class/instance/running/classToTest.st A Spec-Tests.package/ScrollSyncExampleTest.class/README.md A Spec-Tests.package/ScrollSyncExampleTest.class/definition.st A Spec-Tests.package/ScrollSyncExampleTest.class/instance/running/classToTest.st A Spec-Tests.package/TabsExampleTest.class/README.md A Spec-Tests.package/TabsExampleTest.class/definition.st A Spec-Tests.package/TabsExampleTest.class/instance/running/classToTest.st A Spec-Tests.package/TextFieldExampleTest.class/README.md A Spec-Tests.package/TextFieldExampleTest.class/definition.st A Spec-Tests.package/TextFieldExampleTest.class/instance/running/classToTest.st A System-Support.package/SystemNavigation.class/instance/private/allGlobalRefsOn_.st R System-Support.package/SystemNavigation.class/instance/private/classRefsToClassName_.st M System-Support.package/SystemNavigation.class/instance/query/allReferencesTo_.st M Tool-Base.package/extension/SystemNavigation/instance/browseAllSendersOrUsersOf_.st Log Message: ----------- 60160 18840 Cleaning of Spec-example, adding their tests https://pharo.fogbugz.com/f/cases/18840 18848 Traits do not show up when using sendersOfIt https://pharo.fogbugz.com/f/cases/18848 18802 Versionner puts a MCLazyVersionInfo(package name) instead of the package name https://pharo.fogbugz.com/f/cases/18802 http://files.pharo.org/image/60/60160.zip

Aug. 1, 2016

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

by phil＠highoctane.be

This whole theming story is not nice. One good thing about Pharo is that one can make the environment one's own. But most of the time, this starts with the colors, and one hits a brick wall. I just can't help thinking about pieces of software like WinAmp where one could do theming easily, adding plugins with ease etc. A lot of editors these days do it all with CSS and similar tech, blowing us out of the water on that front. Generally speaking, with the new Pharo (like 4.x, 5,x, 6,x), I face a more difficult system to get into (despite all the cool things Spotter allows). Somedays, I am wondering if we aren't actively keeping people out. Phil On Mon, 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 > > >

Aug. 1, 2016

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

by Julien Delplanque

Your new theme looks nice, congratulation! I will probably switch from the dark theme to this one once it will be available. :-) Julien On 01/08/16 11:13, Esteban Lorenzano 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 > >

Aug. 1, 2016

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/60159 Home: https://github.com/pharo-project/pharo-core

Aug. 1, 2016