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

Re: [Pharo-users] iStoa, some news

by Hilaire Fernandes

Yes right! Once I am motivated enough I will make another snapshot release. In the meantime, I recorded it in a ticket https://bugs.launchpad.net/istoa/+bug/1315110 If you find anything else, please fill a ticket at the same place http://launchpad.net/istoa, it will be easier for me to look at it. Thanks Hilaire Le 30/04/2014 20:06, Alain Busser a Ã©crit : > > I just tested it and I did not win all the games (my score is only > 1700!). For the 3rd game, instead of "select or deselect" maybe you > should write "select and deselect", because if some fruits are not > selected, they are not counted as deselected: -- Dr. Geo http://drgeo.eu

May 1, 2014

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

by stepharo

sweet! Esteban I would put a brighter/warmer color (like shining orange?) for self because it is an important key. Then I loved the light blue scrollbars so may be they work in the dark theme. On 1/5/14 13:24, 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-users] Dynamic example for spec

by stepharo

Please push that :) Stef On 27/4/14 21:27, kmo wrote: > /It was suggested that it would be good to have other examples, > so I decided to try building a more business-application related one. / > > Stephan - > > That's exactly what is needed. It's pet peeve of mine that so many of the > Spec examples tend to be browsers. If Pharo wants to position itself as a > general purpose application development tool then it has to demonstrate that > it can create basic data entry commercial applications. Otherwise we might > as well tell business developers to forget about Spec and Morphic and just > use Seaside. > > Ken > > > > -- > View this message in context: http://forum.world.st/Dynamic-example-for-spec-tp4756370p4756696.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

May 1, 2014

Re: [Pharo-users] Video Tutorials about Pharo

by stepharo

I always wanted to redo my old videos. http://stephane.ducasse.free.fr/Videos/ and this is good that you start. Keep pushing. Stef On 26/4/14 20:16, kilon alios wrote: > Hello pharoers . I have created a playlist in youtube where in the > past few days I am keep adding new tutorials about the basics of Pharo. > > https://www.youtube.com/watch?v=Ol5ivaEATLQ&list=PLqbtQ7OkSta0ULYAd7Qdxof85… > > For now I am focusing on the vary basics. So far the tutorials are > > 1) Why Pharo -> Explaining why I love Pharo and what Pharo is. > 2) Install Pharo > 3) Create a Class > 4) Workspace Variables > 5) Instance Variables > 6) Temporary Variables > > I try to keep the duration at most around 10 minutes , if I can around > 3-4 minutes. My goals is to focus on one or two features per tutorial. > > My focus for now is explaining the basics of Pharo the Language and > Pharo the IDE. I hope however that after that I will have the energy > and time to focus on Pharo libraries, like Nativeboost, Athens, Roosal > , Sockets and many more. > > If my free time holds and I do not run out of steam, I should be able > to produce around 30 - 60 hours per year of Video Tutorials that will > be able to document a ton of Pharo functionality. > > Already the Playlist is over an hour long and I try to keep my > tutorials focused entirely on the practical side. > > Your comments and support is greatly appreciated.

May 1, 2014

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

by Ignacio Sniechowski

This is awesome! Thank's Esteban Best Nacho *Lic. Ignacio Sniechowski, MBA* On Thu, May 1, 2014 at 8:24 AM, 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: > > > 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-users] iStoa, some news

by stepharo

jb is working on a a new build for the android vm. Stef On 30/4/14 20:06, Alain Busser wrote: > Hi, > > I just tested it and I did not win all the games (my score is only > 1700!). For the 3rd game, instead of "select or deselect" maybe you > should write "select and deselect", because if some fruits are not > selected, they are not counted as deselected: > > > â > > I thought that only choosing 4 of the apples would yield a good > result, but it is not the case. > > The second activity reminds me of one that I made, about fractions: > https://dl.dropboxusercontent.com/u/10996692/englishFractions.html > > I plan to transform it into something very similar to yours (but with > CSS effects). > > For this activity at least, an Android version would be great, if you > consider hox easy very young children use a mobile, compared to a > laptop... > > Alain > > > > > > > > > On Sun, Apr 27, 2014 at 10:35 PM, Hilaire Fernandes > <hilaire.fernandes(a)gmail.com <mailto:hilaire.fernandes@gmail.com>> wrote: > > Hi, > > I have been working on iStoa lately (http://launchpad.net/istoa) > Few screenshot enclosed, hope for another alpha release soon. > > Thanks > > Hilaire > > > -- > Dr. Geo http://drgeo.eu > >

May 1, 2014

Re: [Pharo-users] [Pharo-dev] [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-users] [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-users] [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-users] [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