Pharo-dev
By thread
pharo-dev@lists.pharo.org
By month
Messages by month
- ----- 2026 -----
- July
- June
- May
- April
- March
- February
- January
- ----- 2025 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2024 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2023 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2022 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2021 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2020 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2019 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2018 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2017 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2016 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2015 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2014 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2013 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2012 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2011 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2010 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2009 -----
- December
- November
- October
- September
- August
- July
- June
- May
- April
- March
- February
- January
- ----- 2008 -----
- December
- November
- October
- September
- August
- July
- June
- May
May 2014
- 1104 messages
Re: [Pharo-dev] Pharo crashes
by stepharo
> And please don't take this as a criticism. It's more my anxiety.
I appreciate it :)
May 1, 2014
Re: [Pharo-dev] [ANN]: Little NeoJSON Helper
by stepharo
sean
May be we can add that to the JSOn chapter.
Are you interested?
Stef
On 30/4/14 16:28, Sean P. DeNigris wrote:
> Okay, here is version 0.1 - the most basic useful functionality to aid in
> writing mappings.
>
> "Assuming Neo-JSON-Core is loaded"
> Gofer it
> smalltalkhubUser: 'SeanDeNigris' project: 'SeansPlayground';
> package: 'Neo-JSON-Utilities';
> load.
>
> Now if you:
> reader := NeoJSONReader on: entity contents readStream.
> reader nextAs: MyClass "(that does not implement MyClass
> class>>#neoJsonMapping:)".
>
> You will get a debugger (which you probably want to close because the new
> mappings we create will not be activated as the helper hook is cached in the
> mappings) and a tree inspector on a NeoJSON model that you can customize,
> where:
> - a NeoJSONObject represents each JSON dictionary; for the enclosing object,
> the schema is already set to MyClass (i.e. the argument to #nextAs:)
> - a NeoJSONList represents each JSON list
> - a NeoJSONValue represents all other values e.g. bools, nil, strings,
> numbers
>
> Some useful things to do:
> - For each NeoJSONObject that you want to map to a class, select it in the
> explorer and:
> self schema: MyOtherClass.
> self generateInstVars. "self explanatory?"
> self mappingSourceCode inspect. "see the neoJsonMapping: source that would
> be generated"
> self generateMapping. "compile class-side neoJsonMapping:"
> - Select any field inside a NeoJSONObject that you want to map to an inst
> var with a different name and:
> self instVarName: #isSaved "(e.g. to map JSON fields_with_underscores to
> camelCase var names)"
> - Specify the element type of a list by selecting it and:
> self elementSchema: MyListReturnType. "This will automatically set the
> schema to #ArrayOfMyListReturnType, but you can change that manually if you
> want by sending #schema:)
>
> After customizing, sending #generateMapping to a NeoJSONObject should
> generate something like:
> neoJsonMapping: mapper
> mapper for: self do: [ :mapping |
> mapping mapInstVars: #(notes id).
> (mapping mapInstVar: #day) valueSchema: Date.
> (mapping mapInstVar: #events) valueSchema: #ArrayOfMyEvent.
> mapping mapInstVar: #isSaved to: #is_saved.
> (mapping mapInstVar: #timeSaved) valueSchema: DateAndTime ].
>
> mapper for: Date customDo: [ :mapping | ]. "now you specify how to convert
> the string to a Date"
> mapper for: #ArrayOfMyEvent customDo: [ :mapping |
> mapping listOfElementSchema: MyEvent ].
> mapper for: DateAndTime customDo: [ :mapping | ]. "same as Date above"
>
> This started as a tiny little personal experiment that got away from me, ha
> ha, so there is no UI, tests, or doc (except for this post). MIT of course.
> Enjoy!
>
>
May 1, 2014
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
by Jimmie Houchin
Awesome!
Thanks.
On 05/01/2014 06:24 AM, Esteban Lorenzano wrote:
> Dark Theme for Pharo 3
> ==================
>
> So, I finally took some time and hacked a Dark Theme for Pharo 3:
>
>
> How you install it? You need to execute this script:
>
> â1. You need this because otherwise Gofer merge becomes dumb :P"
> MCRepositoryGroup default
> addRepository: (MCSmalltalkhubRepository
> owner: 'estebanlm'
> project: 'Pharo3DarkTheme').
> â2. Now we can actually MERGE the project"
> Gofer it
> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme';
> package: 'Pharo3DarkTheme';
> merge.
> â3. And then install it"
> Pharo3DarkTheme installFullTheme.
>
>
> *WARNING 1:* You need to do a merge (notice the script)
> *WARNING 2:* Yes, this is a HACK (also: an ugly hack). See below for
> details.
> *WARNING 3:* This changes something in the Pharo3Theme too... so you
> can go back after installing, but not completely :)
>
> Considerations
> --------------
>
> It can look like an easy task, to make a theme over a non native GUI
> like Pharo, but let me tell you: It is not. There are a lot of
> glitches and errors of design you have to overcome to get a working
> version of a theme. This is a pitty because we claim that our system
> is clean (or should be clean) and easy to understand.
>
> But all the Morphic implementation is a hack over a hack, with
> preconcepts and hardcodes everywhere, up to a point that to make the
> smallest change is an incredibly annoying task.
>
> Then... I added ""yet another hack"" to this infinite list. I made it
> because we need something like this, even if not a good solution. And
> I also made it to start a debate into our community. I truly believe
> that Morphic was a great idea, but I also believe that current
> implementation is doomed. I would like to discuss a new
> implementation, with a good design (for example I believe it should be
> a clear separation between a morph and it's skin, making easy the
> actual-hard task of changing a colorset).
> I also believe there will be a clear separation between what is a
> Morph (a graphical unit) and a Widget (who at the time should use
> morphs, but that's another story).
> Etc., etc., etc.
>
> So, will we start the longtime postponed effort of effectively replace
> current Morphic?
>
> In the mean time, enjoy the theme. Is so cool that I'm considering
> making it my default theme :P
>
> Esteban
>
May 1, 2014
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
by Esteban Lorenzano
On 01 May 2014, at 14:51, kilon alios <kilon.alios(a)gmail.com> wrote:
> Esteban you are awesome, VIP of Pharo :)
>
> If there was one thing of Pharo that got in my nerves it was the white theme. So tiring to my eyes it was the No 1 for me.
>
> What I can say about this dark theme, its amazing. The colors are right, I love the syntax highlighting colors , I love it , love and love it.
>
> I have installed , I see no problems so far, I will keep using it from now on a report back any problems. The thing I see is that class icons contain some white in their edges which of course does not fit with the theme, but for a hack its still awesome.
>
> Thank you , thank you and thank you.
>
> At last I can clearly see the scroll bars.
>
> Hm i found a problem, tried to open the help browser it asked for my name but the input box is white and so i could not see what i was typing.
thanks, Iâm very glad you enjoy it :)
yes. Pavel told me that⦠think is that I always set the author in preferences, so I never see that dialog (and therefore, I do not change it).
I will fix it :)
Esteban
>
>
> On Thu, May 1, 2014 at 3:29 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
>
> On 01 May 2014, at 14:23, phil(a)highoctane.be wrote:
>
>> Yesssssssss!!!!!!
>>
>> Esteban, you really made my day on this one.
>>
>
> you are welcome :)
>> The good thing is also that with your changes we can spot where to look for changing all we want now.
>>
>
> yes, the idea was to make a dark theme possible by removing hardcoded colorisation and dumb things (I like current one, but the most important is that now *it is* possible to play with themes for real).
>
> now, we need to think how we can actually integrate the changes to the image (I suppose not in the way it is done now, as I said⦠it is mostly a hack).
>
> Esteban
>
>> Thanks again.
>>
>> Phil
>>
>> Le 1 mai 2014 14:08, "Sven Van Caekenberghe" <sven(a)stfx.eu> a écrit :
>> >
>> > Wow!
>> >
>> > This will make a couple of people very happy, and it is quite impressive.
>> >
>> > Seriously, you found time to finish this while labouring during days on the Pharo 3 release, are you sure you are not extra-terrestial ?
>> >
>> > Works like a charm :
>> >
>> >
>> > Thanks.
>> >
>> > Sven
>> >
>> > PS: Yes, we should do the effort to make it possible to do this for real (clean).
>> >
>> > On 01 May 2014, at 13:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
>> >
>> >> Dark Theme for Pharo 3
>> >> ==================
>> >>
>> >> So, I finally took some time and hacked a Dark Theme for Pharo 3:
>> >>
>> >> <Screen Shot 2014-05-01 at 13.11.57.png>
>> >>
>> >> How you install it? You need to execute this script:
>> >>
>> >> â1. You need this because otherwise Gofer merge becomes dumb :P"
>> >> MCRepositoryGroup default
>> >> addRepository: (MCSmalltalkhubRepository
>> >> owner: 'estebanlm'
>> >> project: 'Pharo3DarkTheme').
>> >> â2. Now we can actually MERGE the project"
>> >> Gofer it
>> >> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme';
>> >> package: 'Pharo3DarkTheme';
>> >> merge.
>> >> â3. And then install it"
>> >> Pharo3DarkTheme installFullTheme.
>> >>
>> >> WARNING 1: You need to do a merge (notice the script)
>> >> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details.
>> >> WARNING 3: This changes something in the Pharo3Theme too... so you can go back after installing, but not completely :)
>> >>
>> >> Considerations
>> >> --------------
>> >>
>> >> It can look like an easy task, to make a theme over a non native GUI like Pharo, but let me tell you: It is not. There are a lot of glitches and errors of design you have to overcome to get a working version of a theme. This is a pitty because we claim that our system is clean (or should be clean) and easy to understand.
>> >>
>> >> But all the Morphic implementation is a hack over a hack, with preconcepts and hardcodes everywhere, up to a point that to make the smallest change is an incredibly annoying task.
>> >>
>> >> Then... I added ""yet another hack"" to this infinite list. I made it because we need something like this, even if not a good solution. And I also made it to start a debate into our community. I truly believe that Morphic was a great idea, but I also believe that current implementation is doomed. I would like to discuss a new implementation, with a good design (for example I believe it should be a clear separation between a morph and it's skin, making easy the actual-hard task of changing a colorset).
>> >> I also believe there will be a clear separation between what is a Morph (a graphical unit) and a Widget (who at the time should use morphs, but that's another story).
>> >> Etc., etc., etc.
>> >>
>> >> So, will we start the longtime postponed effort of effectively replace current Morphic?
>> >>
>> >> In the mean time, enjoy the theme. Is so cool that I'm considering making it my default theme :P
>> >>
>> >> Esteban
>> >>
>> >
>
>
May 1, 2014
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
by kilon alios
Esteban you are awesome, VIP of Pharo :)
If there was one thing of Pharo that got in my nerves it was the white
theme. So tiring to my eyes it was the No 1 for me.
What I can say about this dark theme, its amazing. The colors are right, I
love the syntax highlighting colors , I love it , love and love it.
I have installed , I see no problems so far, I will keep using it from now
on a report back any problems. The thing I see is that class icons contain
some white in their edges which of course does not fit with the theme, but
for a hack its still awesome.
Thank you , thank you and thank you.
At last I can clearly see the scroll bars.
Hm i found a problem, tried to open the help browser it asked for my name
but the input box is white and so i could not see what i was typing.
On Thu, May 1, 2014 at 3:29 PM, Esteban Lorenzano <estebanlm(a)gmail.com>wrote:
>
> On 01 May 2014, at 14:23, phil(a)highoctane.be wrote:
>
> Yesssssssss!!!!!!
>
> Esteban, you really made my day on this one.
>
> you are welcome :)
>
> The good thing is also that with your changes we can spot where to look
> for changing all we want now.
>
> yes, the idea was to make a dark theme possible by removing hardcoded
> colorisation and dumb things (I like current one, but the most important is
> that now *it is* possible to play with themes for real).
>
> now, we need to think how we can actually integrate the changes to the
> image (I suppose not in the way it is done now, as I said⦠it is mostly a
> hack).
>
> Esteban
>
> Thanks again.
>
> Phil
>
> Le 1 mai 2014 14:08, "Sven Van Caekenberghe" <sven(a)stfx.eu> a écrit :
> >
> > Wow!
> >
> > This will make a couple of people very happy, and it is quite impressive.
> >
> > Seriously, you found time to finish this while labouring during days on
> the Pharo 3 release, are you sure you are not extra-terrestial ?
> >
> > Works like a charm :
> >
> >
> > Thanks.
> >
> > Sven
> >
> > PS: Yes, we should do the effort to make it possible to do this for real
> (clean).
> >
> > On 01 May 2014, at 13:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
> >
> >> Dark Theme for Pharo 3
> >> ==================
> >>
> >> So, I finally took some time and hacked a Dark Theme for Pharo 3:
> >>
> >> <Screen Shot 2014-05-01 at 13.11.57.png>
> >>
> >> How you install it? You need to execute this script:
> >>
> >> â1. You need this because otherwise Gofer merge becomes dumb :P"
> >> MCRepositoryGroup default
> >> addRepository: (MCSmalltalkhubRepository
> >> owner: 'estebanlm'
> >> project: 'Pharo3DarkTheme').
> >> â2. Now we can actually MERGE the project"
> >> Gofer it
> >> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme';
> >> package: 'Pharo3DarkTheme';
> >> merge.
> >> â3. And then install it"
> >> Pharo3DarkTheme installFullTheme.
> >>
> >> WARNING 1: You need to do a merge (notice the script)
> >> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for
> details.
> >> WARNING 3: This changes something in the Pharo3Theme too... so you can
> go back after installing, but not completely :)
> >>
> >> Considerations
> >> --------------
> >>
> >> It can look like an easy task, to make a theme over a non native GUI
> like Pharo, but let me tell you: It is not. There are a lot of glitches and
> errors of design you have to overcome to get a working version of a theme.
> This is a pitty because we claim that our system is clean (or should be
> clean) and easy to understand.
> >>
> >> But all the Morphic implementation is a hack over a hack, with
> preconcepts and hardcodes everywhere, up to a point that to make the
> smallest change is an incredibly annoying task.
> >>
> >> Then... I added ""yet another hack"" to this infinite list. I made it
> because we need something like this, even if not a good solution. And I
> also made it to start a debate into our community. I truly believe
> that Morphic was a great idea, but I also believe that current
> implementation is doomed. I would like to discuss a new implementation,
> with a good design (for example I believe it should be a clear
> separation between a morph and it's skin, making easy the actual-hard task
> of changing a colorset).
> >> I also believe there will be a clear separation between what is a Morph
> (a graphical unit) and a Widget (who at the time should use morphs, but
> that's another story).
> >> Etc., etc., etc.
> >>
> >> So, will we start the longtime postponed effort of effectively replace
> current Morphic?
> >>
> >> In the mean time, enjoy the theme. Is so cool that I'm considering
> making it my default theme :P
> >>
> >> Esteban
> >>
> >
>
>
>
May 1, 2014
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
by Esteban Lorenzano
On 01 May 2014, at 14:23, phil(a)highoctane.be wrote:
> Yesssssssss!!!!!!
>
> Esteban, you really made my day on this one.
>
you are welcome :)
> The good thing is also that with your changes we can spot where to look for changing all we want now.
>
yes, the idea was to make a dark theme possible by removing hardcoded colorisation and dumb things (I like current one, but the most important is that now *it is* possible to play with themes for real).
now, we need to think how we can actually integrate the changes to the image (I suppose not in the way it is done now, as I said⦠it is mostly a hack).
Esteban
> Thanks again.
>
> Phil
>
> Le 1 mai 2014 14:08, "Sven Van Caekenberghe" <sven(a)stfx.eu> a écrit :
> >
> > Wow!
> >
> > This will make a couple of people very happy, and it is quite impressive.
> >
> > Seriously, you found time to finish this while labouring during days on the Pharo 3 release, are you sure you are not extra-terrestial ?
> >
> > Works like a charm :
> >
> >
> > Thanks.
> >
> > Sven
> >
> > PS: Yes, we should do the effort to make it possible to do this for real (clean).
> >
> > On 01 May 2014, at 13:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
> >
> >> Dark Theme for Pharo 3
> >> ==================
> >>
> >> So, I finally took some time and hacked a Dark Theme for Pharo 3:
> >>
> >> <Screen Shot 2014-05-01 at 13.11.57.png>
> >>
> >> How you install it? You need to execute this script:
> >>
> >> â1. You need this because otherwise Gofer merge becomes dumb :P"
> >> MCRepositoryGroup default
> >> addRepository: (MCSmalltalkhubRepository
> >> owner: 'estebanlm'
> >> project: 'Pharo3DarkTheme').
> >> â2. Now we can actually MERGE the project"
> >> Gofer it
> >> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme';
> >> package: 'Pharo3DarkTheme';
> >> merge.
> >> â3. And then install it"
> >> Pharo3DarkTheme installFullTheme.
> >>
> >> WARNING 1: You need to do a merge (notice the script)
> >> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details.
> >> WARNING 3: This changes something in the Pharo3Theme too... so you can go back after installing, but not completely :)
> >>
> >> Considerations
> >> --------------
> >>
> >> It can look like an easy task, to make a theme over a non native GUI like Pharo, but let me tell you: It is not. There are a lot of glitches and errors of design you have to overcome to get a working version of a theme. This is a pitty because we claim that our system is clean (or should be clean) and easy to understand.
> >>
> >> But all the Morphic implementation is a hack over a hack, with preconcepts and hardcodes everywhere, up to a point that to make the smallest change is an incredibly annoying task.
> >>
> >> Then... I added ""yet another hack"" to this infinite list. I made it because we need something like this, even if not a good solution. And I also made it to start a debate into our community. I truly believe that Morphic was a great idea, but I also believe that current implementation is doomed. I would like to discuss a new implementation, with a good design (for example I believe it should be a clear separation between a morph and it's skin, making easy the actual-hard task of changing a colorset).
> >> I also believe there will be a clear separation between what is a Morph (a graphical unit) and a Widget (who at the time should use morphs, but that's another story).
> >> Etc., etc., etc.
> >>
> >> So, will we start the longtime postponed effort of effectively replace current Morphic?
> >>
> >> In the mean time, enjoy the theme. Is so cool that I'm considering making it my default theme :P
> >>
> >> Esteban
> >>
> >
May 1, 2014
Re: [Pharo-dev] [Pharo-users] [ANN] Pharo3 Dark Theme is available
by Esteban Lorenzano
On 01 May 2014, at 14:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote:
> Wow!
>
> This will make a couple of people very happy, and it is quite impressive.
thanks!
yes I made it for Phil and Yuriy :)
>
> Seriously, you found time to finish this while labouring during days on the Pharo 3 release, are you sure you are not extra-terrestial ?
well.. there were some dead moments while waiting for things to be ready (but I wasnât able to work on more complicated things, I needed to keep my concentration on the release)⦠and then I have insomnia :P
Esteban
>
> Works like a charm :
>
> <Screen Shot 2014-05-01 at 14.03.07.png>
>
> Thanks.
>
> Sven
>
> PS: Yes, we should do the effort to make it possible to do this for real (clean).
>
> On 01 May 2014, at 13:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
>
>> Dark Theme for Pharo 3
>> ==================
>>
>> So, I finally took some time and hacked a Dark Theme for Pharo 3:
>>
>> <Screen Shot 2014-05-01 at 13.11.57.png>
>>
>> How you install it? You need to execute this script:
>>
>> â1. You need this because otherwise Gofer merge becomes dumb :P"
>> MCRepositoryGroup default
>> addRepository: (MCSmalltalkhubRepository
>> owner: 'estebanlm'
>> project: 'Pharo3DarkTheme').
>> â2. Now we can actually MERGE the project"
>> Gofer it
>> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme';
>> package: 'Pharo3DarkTheme';
>> merge.
>> â3. And then install it"
>> Pharo3DarkTheme installFullTheme.
>>
>> WARNING 1: You need to do a merge (notice the script)
>> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details.
>> WARNING 3: This changes something in the Pharo3Theme too... so you can go back after installing, but not completely :)
>>
>> Considerations
>> --------------
>>
>> It can look like an easy task, to make a theme over a non native GUI like Pharo, but let me tell you: It is not. There are a lot of glitches and errors of design you have to overcome to get a working version of a theme. This is a pitty because we claim that our system is clean (or should be clean) and easy to understand.
>>
>> But all the Morphic implementation is a hack over a hack, with preconcepts and hardcodes everywhere, up to a point that to make the smallest change is an incredibly annoying task.
>>
>> Then... I added ""yet another hack"" to this infinite list. I made it because we need something like this, even if not a good solution. And I also made it to start a debate into our community. I truly believe that Morphic was a great idea, but I also believe that current implementation is doomed. I would like to discuss a new implementation, with a good design (for example I believe it should be a clear separation between a morph and it's skin, making easy the actual-hard task of changing a colorset).
>> I also believe there will be a clear separation between what is a Morph (a graphical unit) and a Widget (who at the time should use morphs, but that's another story).
>> Etc., etc., etc.
>>
>> So, will we start the longtime postponed effort of effectively replace current Morphic?
>>
>> In the mean time, enjoy the theme. Is so cool that I'm considering making it my default theme :P
>>
>> Esteban
>>
>
May 1, 2014
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
by phil@highoctane.be
Yesssssssss!!!!!!
Esteban, you really made my day on this one.
The good thing is also that with your changes we can spot where to look for
changing all we want now.
Thanks again.
Phil
Le 1 mai 2014 14:08, "Sven Van Caekenberghe" <sven(a)stfx.eu> a écrit :
>
> Wow!
>
> This will make a couple of people very happy, and it is quite impressive.
>
> Seriously, you found time to finish this while labouring during days on
the Pharo 3 release, are you sure you are not extra-terrestial ?
>
> Works like a charm :
>
>
> Thanks.
>
> Sven
>
> PS: Yes, we should do the effort to make it possible to do this for real
(clean).
>
> On 01 May 2014, at 13:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
>
>> Dark Theme for Pharo 3
>> ==================
>>
>> So, I finally took some time and hacked a Dark Theme for Pharo 3:
>>
>> <Screen Shot 2014-05-01 at 13.11.57.png>
>>
>> How you install it? You need to execute this script:
>>
>> â1. You need this because otherwise Gofer merge becomes dumb :P"
>> MCRepositoryGroup default
>> addRepository: (MCSmalltalkhubRepository
>> owner: 'estebanlm'
>> project: 'Pharo3DarkTheme').
>> â2. Now we can actually MERGE the project"
>> Gofer it
>> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme';
>> package: 'Pharo3DarkTheme';
>> merge.
>> â3. And then install it"
>> Pharo3DarkTheme installFullTheme.
>>
>> WARNING 1: You need to do a merge (notice the script)
>> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for
details.
>> WARNING 3: This changes something in the Pharo3Theme too... so you can
go back after installing, but not completely :)
>>
>> Considerations
>> --------------
>>
>> It can look like an easy task, to make a theme over a non native GUI
like Pharo, but let me tell you: It is not. There are a lot of glitches and
errors of design you have to overcome to get a working version of a theme.
This is a pitty because we claim that our system is clean (or should be
clean) and easy to understand.
>>
>> But all the Morphic implementation is a hack over a hack, with
preconcepts and hardcodes everywhere, up to a point that to make the
smallest change is an incredibly annoying task.
>>
>> Then... I added ""yet another hack"" to this infinite list. I made it
because we need something like this, even if not a good solution. And I
also made it to start a debate into our community. I truly believe
that Morphic was a great idea, but I also believe that current
implementation is doomed. I would like to discuss a new implementation,
with a good design (for example I believe it should be a clear
separation between a morph and it's skin, making easy the actual-hard task
of changing a colorset).
>> I also believe there will be a clear separation between what is a Morph
(a graphical unit) and a Widget (who at the time should use morphs, but
that's another story).
>> Etc., etc., etc.
>>
>> So, will we start the longtime postponed effort of effectively replace
current Morphic?
>>
>> In the mean time, enjoy the theme. Is so cool that I'm considering
making it my default theme :P
>>
>> Esteban
>>
>
May 1, 2014
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
by Sven Van Caekenberghe
Wow!
This will make a couple of people very happy, and it is quite impressive.
Seriously, you found time to finish this while labouring during days on the Pharo 3 release, are you sure you are not extra-terrestial ?
Works like a charm :
Thanks.
Sven
PS: Yes, we should do the effort to make it possible to do this for real (clean).
On 01 May 2014, at 13:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
> Dark Theme for Pharo 3
> ==================
>
> So, I finally took some time and hacked a Dark Theme for Pharo 3:
>
> <Screen Shot 2014-05-01 at 13.11.57.png>
>
> How you install it? You need to execute this script:
>
> â1. You need this because otherwise Gofer merge becomes dumb :P"
> MCRepositoryGroup default
> addRepository: (MCSmalltalkhubRepository
> owner: 'estebanlm'
> project: 'Pharo3DarkTheme').
> â2. Now we can actually MERGE the project"
> Gofer it
> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme';
> package: 'Pharo3DarkTheme';
> merge.
> â3. And then install it"
> Pharo3DarkTheme installFullTheme.
>
> WARNING 1: You need to do a merge (notice the script)
> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details.
> WARNING 3: This changes something in the Pharo3Theme too... so you can go back after installing, but not completely :)
>
> Considerations
> --------------
>
> It can look like an easy task, to make a theme over a non native GUI like Pharo, but let me tell you: It is not. There are a lot of glitches and errors of design you have to overcome to get a working version of a theme. This is a pitty because we claim that our system is clean (or should be clean) and easy to understand.
>
> But all the Morphic implementation is a hack over a hack, with preconcepts and hardcodes everywhere, up to a point that to make the smallest change is an incredibly annoying task.
>
> Then... I added ""yet another hack"" to this infinite list. I made it because we need something like this, even if not a good solution. And I also made it to start a debate into our community. I truly believe that Morphic was a great idea, but I also believe that current implementation is doomed. I would like to discuss a new implementation, with a good design (for example I believe it should be a clear separation between a morph and it's skin, making easy the actual-hard task of changing a colorset).
> I also believe there will be a clear separation between what is a Morph (a graphical unit) and a Widget (who at the time should use morphs, but that's another story).
> Etc., etc., etc.
>
> So, will we start the longtime postponed effort of effectively replace current Morphic?
>
> In the mean time, enjoy the theme. Is so cool that I'm considering making it my default theme :P
>
> Esteban
>
May 1, 2014
Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available
by Yuriy Tymchuk
Very cool. Thank you, Esteban!
Uko
On 01 May 2014, at 13:24, Esteban Lorenzano <estebanlm(a)gmail.com> wrote:
> Dark Theme for Pharo 3
> ==================
>
> So, I finally took some time and hacked a Dark Theme for Pharo 3:
>
> <Screen Shot 2014-05-01 at 13.11.57.png>
>
> How you install it? You need to execute this script:
>
> â1. You need this because otherwise Gofer merge becomes dumb :P"
> MCRepositoryGroup default
> addRepository: (MCSmalltalkhubRepository
> owner: 'estebanlm'
> project: 'Pharo3DarkTheme').
> â2. Now we can actually MERGE the project"
> Gofer it
> smalltalkhubUser: 'estebanlm' project: 'Pharo3DarkTheme';
> package: 'Pharo3DarkTheme';
> merge.
> â3. And then install it"
> Pharo3DarkTheme installFullTheme.
>
> WARNING 1: You need to do a merge (notice the script)
> WARNING 2: Yes, this is a HACK (also: an ugly hack). See below for details.
> WARNING 3: This changes something in the Pharo3Theme too... so you can go back after installing, but not completely :)
>
> Considerations
> --------------
>
> It can look like an easy task, to make a theme over a non native GUI like Pharo, but let me tell you: It is not. There are a lot of glitches and errors of design you have to overcome to get a working version of a theme. This is a pitty because we claim that our system is clean (or should be clean) and easy to understand.
>
> But all the Morphic implementation is a hack over a hack, with preconcepts and hardcodes everywhere, up to a point that to make the smallest change is an incredibly annoying task.
>
> Then... I added ""yet another hack"" to this infinite list. I made it because we need something like this, even if not a good solution. And I also made it to start a debate into our community. I truly believe that Morphic was a great idea, but I also believe that current implementation is doomed. I would like to discuss a new implementation, with a good design (for example I believe it should be a clear separation between a morph and it's skin, making easy the actual-hard task of changing a colorset).
> I also believe there will be a clear separation between what is a Morph (a graphical unit) and a Widget (who at the time should use morphs, but that's another story).
> Etc., etc., etc.
>
> So, will we start the longtime postponed effort of effectively replace current Morphic?
>
> In the mean time, enjoy the theme. Is so cool that I'm considering making it my default theme :P
>
> Esteban
>
May 1, 2014