May 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available

by Sergi Reyner

Likey!! Now to find some time to actually install it and see if it works for me :) Cheers, Sergi 2014-05-01 12:47 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > ahhhâ¦ forget to say. There will be missing changes (my workflow is > covered, but that does not means all Pharo). > Please, report it and I will fix it as soon as I can. > > cheers, > Esteban > > 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

ahhhâ¦ forget to say. There will be missing changes (my workflow is covered, but that does not means all Pharo). Please, report it and I will fix it as soon as I can. cheers, Esteban 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 Nicolas Petton

Very well done! Nico Esteban Lorenzano writes: > 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 -- Nicolas Petton http://nicolas-petton.fr

May 1, 2014

Re: [Pharo-dev] [ANN] Pharo3 Dark Theme is available

by Esteban Lorenzano

â¦ and I made a blog post with it :P http://smallworks.eu/web/blog/2014-05-01-dark-theme-for-pharo 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

[ANN] Pharo3 Dark Theme is available

by Esteban Lorenzano

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] Pharo 3.0 / Roassal2 / Ubuntu

by Alexandre Bergel

> Yes yes yes ... it works. I quickly jumped through some examples. Roassal2 looks so nice. Thank you. Let me know how it goes. Documentation is missing, but we have many many examplesâ¦ The chapter in Deep into Pharo (www.deepintopharo.com) contains a documentation about Roassal1 and the Mondrian builder, written on top of the core of Roassal. Roassal2 is largely compatible with Roassal1. When it is not, then small changes have to be made. Alexandre > > > > Am 01.05.2014 03:31, schrieb Alexandre Bergel: >> Hi Volkert, >> >> You need to install the true type font. Unfortunately, Pharo3 does not do it for you. I guess this will be fixed in the next release of Pharo. >> >> I have made a very short video on how to install Roassal2 from scratch: >> https://dl.dropboxusercontent.com/u/31543901/TMP/InstallingTrueTypeFont.mov >> >> Let us know how it goes. >> >> Alexandre >> >> >> On Apr 30, 2014, at 2:53 PM, volkert(a)nivoba.de wrote: >> >>> Dear all, >>> >>> i just downloaded Pharo 3.0 and installed Roassal2 via Configuration Manager (Stable Version). >>> When trying the "Roassal examples" (from Tool-Menu) i got an red screen. >>> >>> Platform Ubuntu 14.04LTS >>> Pharo3.0 Latest update: #30846 >>> >>> Need some help :-) >>> >>> BW, >>> Volkert >>> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 1, 2014

Re: [Pharo-dev] Pharo 3.0 / Roassal2 / Ubuntu

by Alexandre Bergel

Thanks Marcus, Alexandre On May 1, 2014, at 5:07 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 01 May 2014, at 09:36, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > >> Nice, let's copy that to the Pharo YouTube channelâ¦ >> > Done: > > https://www.youtube.com/watch?v=8wQjFzy8tj0 > > >> On 01 May 2014, at 03:31, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> >>> Hi Volkert, >>> >>> You need to install the true type font. Unfortunately, Pharo3 does not do it for you. I guess this will be fixed in the next release of Pharo. >>> >>> I have made a very short video on how to install Roassal2 from scratch: >>> https://dl.dropboxusercontent.com/u/31543901/TMP/InstallingTrueTypeFont.mov >>> >>> Let us know how it goes. >>> >>> Alexandre >>> >>> >>> On Apr 30, 2014, at 2:53 PM, volkert(a)nivoba.de wrote: >>> >>>> Dear all, >>>> >>>> i just downloaded Pharo 3.0 and installed Roassal2 via Configuration Manager (Stable Version). >>>> When trying the "Roassal examples" (from Tool-Menu) i got an red screen. >>>> >>>> Platform Ubuntu 14.04LTS >>>> Pharo3.0 Latest update: #30846 >>>> >>>> Need some help :-) >>>> >>>> BW, >>>> Volkert >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

May 1, 2014

Re: [Pharo-dev] Pharo is Smalltalkâ¦ and Not

by S Krish

+1 I understand the part about making Pharo appeal more to the wider audience in this decade and ahead.... Let me put in the effort in making that happen, before I say another word on this. Making a platform that I can be most productive in be the most accepted one across the industry is a big win for me... On Thu, May 1, 2014 at 2:20 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > Here's my musings about how we integrate the two motives - to acknowledge > our > heritage /and/ break out of our pigeon hole. My key point here is to > gradually introduce the Smalltalk part after people are deep enough to have > gotten excited about the ideas without dismissing them because of cultural > baggage... > > Drilling down: > 1. Sound bite: "Pharo - The immersive programming experience" > 2. Why Pharo: (about a paragraph, like the one on the site now, "Pharo > gives > you immediate and total control over your programming experience..." > 3. What is it. Here we can accurately paint the nuanced picture, > distinguishing Smalltalk as an idea based on design principles vs. > Smalltalk-80. If "Smalltalk" more exactly means an environment + libraries > + > a language (I think that order is important - the syntax was always the > least interesting thing about Smalltalk). What we might really say if we > had > the time to go beyond an initial sound bite is: > Pharo is: > - a [pick 2 or 3 of: dynamic, open, immersive, live] environment > (like an > IDE and OS rolled into one) > - beautifully designed core libraries including a web > client/server, FFI, > Y, Z... > - a dialect of the Smalltalk programming language > > For #1, the inspiration is most accurately the Dynabook > For #2, IMHO enough components have been rewritten to stand on it's own > For #3, this is where we are most obviously a Smalltalk, and should be > clear > about it > > And in an FAQ answer any common objections people might have: > Q: Is Pharo Smalltalk? > A: When most people hear "Smalltalk", they think of Smalltalk-80, which > Pharo is not. However, Smalltalk is really an idea... the lineage of which > Pharo is a proud member > Q: Can I talk to the world outside the environment? > A: Yes! While the original Smalltalk was quite insulated, now you can > [interact on the command line](link to unix command line examples e.g. the > very Ruby-like pharo [image filename] -e "self inform: 'hello world'"), > [talk to C libraries](link to native boost), etc. > yada yada yada > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Pharo-is-Smalltalk-and-Not-tp4757342p4757348.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

May 1, 2014

New Proposal for new Pharo website - About page (with example website)

by kilon alios

I don't like the about page. Its still unclear what Pharo is and I have to agree with the complains we are getting at reddit. So instead of starting a long conversation about how I would want it done , I sat my ass down and made a draft of it so you can see it directly. Please bare in mind this is draft , I just wanted to show you my idea for an About page. You can find the draft here http://thekilon.wix.com/pharo-about I think contributors should go to a seperate page called "Credit" I am open to comments and suggestions.

May 1, 2014

Re: [Pharo-dev] Pharo renamed to "MuchTalk"

by Sven Van Caekenberghe

https://pharo.fogbugz.com/f/cases/13237/Pharo-Zen-values-should-be-in-the-i… On 01 May 2014, at 00:05, kilon alios <kilon.alios(a)gmail.com> wrote: > yeap definitely sounds a like a good idea to me :) > > > On Thu, May 1, 2014 at 12:52 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > We have that list too: > > Page 3 of http://www.pharo-project.org/download/pictures/be/j32hajf3kjdbsebqo0a9zc5tk… > > Or this version: > > http://lists.pharo.org/pipermail/pharo-users_lists.pharo.org/2012-May/00405… > > Now that I see this list again, I feel that it should be part of the image. > > On 30 Apr 2014, at 23:33, kilon alios <kilon.alios(a)gmail.com> wrote: > > > Personally I am very interested to see how developers see Pharo, because the way they see it is also the future of Pharo the directions it is going. So while some may find these type of discussion derailing its very important for the direction of Pharo. > > > > Even though its very important to add code to Pharo and enhance and bug fix, its also very important to have a clear vision that the community agrees on. > > > > The discussion also has raised some important issues of how Pharo is promoted, obviously Promotion of Pharo is a rather huge deal for Pharo future. I see these Emails as the start of a very long process in the future of Pharo where the community tries to feel in the dark its path and the values it represents. Its also important to get the message (Pharo is all about messages afterall) loud and clear to newcomers or people considering giving Pharo a try. > > > > Sean I am definitely interested in the discussion and your opinion, I have very little to contribute to it, but its great to hear the opinion of people that have very large experience of Smalltalk. > > > > Some say "opinions are like assholes everyone has one" (no intention to be rude) but my belief is opinions however wrong they may be, do matter because they reveal personal needs , desires and dreams. Pharo like every other product out there is made to please people and accommodate for these things. > > > > Also these discussions are far from exclusive to Pharo. I am coming from Python there there is the Zen of Pharo. > > > > " > > â¢ Beautiful is better than ugly. > > â¢ Explicit is better than implicit. > > â¢ Simple is better than complex. > > â¢ Complex is better than complicated. > > â¢ Flat is better than nested. > > â¢ Sparse is better than dense. > > â¢ Readability counts. > > â¢ Special cases aren't special enough to break the rules. > > â¢ Although practicality beats purity. > > â¢ Errors should never pass silently. > > â¢ Unless explicitly silenced. > > â¢ In the face of ambiguity, refuse the temptation to guess. > > â¢ There should be one-- and preferably only one --obvious way to do it. > > â¢ Although that way may not be obvious at first unless you're Dutch. > > â¢ Now is better than never. > > â¢ Although never is often better than right now. > > â¢ If the implementation is hard to explain, it's a bad idea. > > â¢ If the implementation is easy to explain, it may be a good idea. > > â¢ NameSpaces are one honking great idea -- let's do more of those! > > > > â¢ " > > This started as a joke from a single guy. Then it was included as a module in python standard library , the moment you import the module it executes a method that prints this text. The joke became something very serious, it is something that many python library authors take as a guide for designing their libraries. This piece of joke has become so serious that currently python libraries uses this set of principles and libraries that don't are labeled by python coders as "unpythonic" which is considered a bad thing. > > > > For me this indicates that a community has chosen a path and most importantly a path they have chosen to walk together as one unit. I don't think there is anything stronger than that. > > > > > > On Wed, Apr 30, 2014 at 11:52 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > onierstrasz wrote > > > 117 emails since I checked a few hours ago? > > > > 110 of those were mine, sorry :-P > > Signing off for today... > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: http://forum.world.st/Pharo-renamed-to-MuchTalk-tp4757347p4757349.html > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > > > >

May 1, 2014