Re: [Pharo-users] iStoa, some news

[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

Re: [Pharo-users] Dynamic example for spec

[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.

Re: [Pharo-users] Video Tutorials about Pharo

[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=PLqbtQ7OkSta0ULYAd7Qdxof851ybh-_m_

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.

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

[Esteban Lorenzano]

On 01 May 2014, at 14:07, Sven Van Caekenberghe  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 :
> 
> 
> 
> 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  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 
>> 
> 

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

[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  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 
> 

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

[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

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

[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  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 
> 

Re: [Pharo-users] Pharo 3.0 Released!

[Robert Shiplett]

and congrat's on 3.0 release !  Now to get to work on my app !


On 1 May 2014 04:20, Marcus Denker  wrote:

>
> On 30 Apr 2014, at 22:57, Tudor Girba  wrote:
>
> Hi,
>
> It means that we are so happy that CodeCity is
>
>
> Maybe we should have added a link to the code city page (it kind of
> crossed my mind, but then there where so many things to do
> that I forgot it…)
>
> built in Pharo and that we can draw Pharo so beautifully from within
> Pharo. The same applies for Roassal :)
>
> Doru
>
>
> On Wed, Apr 30, 2014 at 5:51 PM, Richard Wettel  wrote:
>
>> Congratulations to the big Pharo family!
>> Ricky
>> P.S. What does "built with Pharo for Pharo" mean?
>> —
>> Sent from Mailbox 
>>
>>
>> On Wed, Apr 30, 2014 at 4:02 PM, Esteban Lorenzano 
>> wrote:
>>
>>> Dear World,
>>>
>>> Pharo 3.0 (http://www.pharo.org) is here.
>>>
>>> 
>>>
>>> The past year seemed short as we got busy building more than usual. Many
>>> things have changed in Pharo. Here are the highlights:
>>> - The new modular Opal compiler is now the default compiler used in the
>>> system.
>>> - The Athens vector graphics canvas is now integrated and it supports
>>> Cairo rendering on all platforms.
>>> - Many tools have been rewritten using Spec, a new framework for
>>> building user interfaces.
>>>  - Versionner and Kommiter are two of the new development tools.
>>> - RPackage, a new package mechanism got enhanced with tags and is fully
>>> integrated in the system.
>>> - The debugger model was rewritten to become modular, the inspector
>>> received a bump to support multiple views, and the Nautilus code browser
>>> supports tags, search and lot more improvements.
>>> - Morphic has seen many cleanings and improvements and the visual theme
>>> has been revamped.
>>>
>>> These are just the more prominent highlights, but the details are just
>>> as important. We have closed 2364 issues in Pharo 3 (compared with 1727
>>> issues in Pharo 2). Take a moment to go through a more detailed recount of
>>> the progress:
>>>
>>>
>>> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md
>>>
>>> Pharo is improving on many fronts. Just take a look at the code city of
>>> Pharo (built with Pharo for Pharo). Every building is a class, and the red
>>> bricks represent the modified methods in Pharo 3.
>>>
>>> 
>>>
>>> Many things are changing but the system gets more stable. Moving from
>>> Pharo 2 to Pharo 3 is almost a matter of just loading the code.
>>>
>>> Remember that Pharo is your platform. We thank all the contributors of
>>> this release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, Clément
>>> Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau,
>>> Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe,
>>> Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo
>>> Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del
>>> Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker,
>>> Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo
>>> Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo
>>> Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale
>>> Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante,
>>> Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek,
>>> Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego
>>> Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto
>>> Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas
>>> Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa Peña, Nicolas
>>> Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Jochen Rick,
>>> Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval
>>> Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel,
>>> Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan
>>> Wilkinson.
>>> And many many more who contributed indirectly, by reporting bugs,
>>> participating in discussion threads, providing feedback...
>>>
>>> Pharo 3.0 is the largest step we took since we started. Yet, it’s just a
>>> step. Expect more. Much more.
>>>
>>> Enjoy!
>>> The Pharo Team
>>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>

Re: [Pharo-users] Pharo 3 minor issue

[giorgio ferraris]

it usually happens that way. You test everything and miss something
obvious...

ciao

giorgio


On Thu, May 1, 2014 at 9:24 AM, Esteban Lorenzano wrote:

> thanks for reporting, I will look at it (super weird that it did not arise
> before :( )
>
> Esteban
>
> On 30 Apr 2014, at 20:54, giorgio ferraris 
> wrote:
>
> > Hi,
> >
> > started looking at Pharo after many years.
> > First of all, you all did an awesome works, thank you!
> > There is a small problems on System Browser
> >  open image
> > open system browser
> > choose one class
> > select group
> > The class side checkbox is enabled, if you check it, you get a wall bak .
> > Giorgio
> >
> > 
>
>
>

Re: [Pharo-users] Pharo 3.0 Released!

[Richard Wettel]

On Thu, May 1, 2014 at 9:20 AM, Marcus Denker wrote:

>
> On 30 Apr 2014, at 22:57, Tudor Girba  wrote:
>
> Hi,
>
> It means that we are so happy that CodeCity is
>
>
> Maybe we should have added a link to the code city page (it kind of
> crossed my mind, but then there where so many things to do
> that I forgot it…)
>

That's fine, Marcus. Actually, I don't think that this announcement, which
celebrates a new milestone in the life of Pharo, really needs any links to
singular tools.


>
> built in Pharo and that we can draw Pharo so beautifully from within
> Pharo. The same applies for Roassal :)
>
> Doru
>
>
> On Wed, Apr 30, 2014 at 5:51 PM, Richard Wettel  wrote:
>
>> Congratulations to the big Pharo family!
>> Ricky
>> P.S. What does "built with Pharo for Pharo" mean?
>> —
>> Sent from Mailbox 
>>
>>
>> On Wed, Apr 30, 2014 at 4:02 PM, Esteban Lorenzano 
>> wrote:
>>
>>> Dear World,
>>>
>>> Pharo 3.0 (http://www.pharo.org) is here.
>>>
>>> 
>>>
>>> The past year seemed short as we got busy building more than usual. Many
>>> things have changed in Pharo. Here are the highlights:
>>> - The new modular Opal compiler is now the default compiler used in the
>>> system.
>>> - The Athens vector graphics canvas is now integrated and it supports
>>> Cairo rendering on all platforms.
>>> - Many tools have been rewritten using Spec, a new framework for
>>> building user interfaces.
>>>  - Versionner and Kommiter are two of the new development tools.
>>> - RPackage, a new package mechanism got enhanced with tags and is fully
>>> integrated in the system.
>>> - The debugger model was rewritten to become modular, the inspector
>>> received a bump to support multiple views, and the Nautilus code browser
>>> supports tags, search and lot more improvements.
>>> - Morphic has seen many cleanings and improvements and the visual theme
>>> has been revamped.
>>>
>>> These are just the more prominent highlights, but the details are just
>>> as important. We have closed 2364 issues in Pharo 3 (compared with 1727
>>> issues in Pharo 2). Take a moment to go through a more detailed recount of
>>> the progress:
>>>
>>>
>>> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md
>>>
>>> Pharo is improving on many fronts. Just take a look at the code city of
>>> Pharo (built with Pharo for Pharo). Every building is a class, and the red
>>> bricks represent the modified methods in Pharo 3.
>>>
>>> 
>>>
>>> Many things are changing but the system gets more stable. Moving from
>>> Pharo 2 to Pharo 3 is almost a matter of just loading the code.
>>>
>>> Remember that Pharo is your platform. We thank all the contributors of
>>> this release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, Clément
>>> Bera, Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau,
>>> Noury Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe,
>>> Damien Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo
>>> Contreras, Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del
>>> Sasso, Gisela Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker,
>>> Martin Dias, Erwan Douaille, Stephane Ducasse, Stephan Eggermont, Pablo
>>> Estefo, Luc Fabresse, Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo
>>> Gassman, Lucas Giudice, Tudor Girba, Thierry Goubier, Norbert Hartl, Dale
>>> Henrichs, Pablo Herrero, Nicolai Hess, Andre Hora, Alejandro Infante,
>>> Ricardo Jacas, Henrik Sperre Johansen, Denis Kudryashov, Pavel Krivanek,
>>> Juraj Kubelka, Laurent Laffont, Jannik Laval, Max Leske, David Lewis, Diego
>>> Lont, Esteban Lorenzano, Stefan Marr, Mariano Martinez Peck, Roberto
>>> Minelli, Hernan Morales Durand, Eliot Miranda, Fernando Olivero, Nicolas
>>> Papagna Maldonado, Nick Papoylias, Nicolas Passerini, Vanessa Peña, Nicolas
>>> Petton, Alain Plantec, Guillermo Polito, Damien Pollet, Jochen Rick,
>>> Benjamin Van Ryseghem, Ronie Salgado, Camille Teruel, Juan Pablo Sandoval
>>> Alcocer, Samir Saleh, Frank Shearar, Igor Stasenko, Aliaksei Syrel,
>>> Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, Martin Walk, Hernan
>>> Wilkinson.
>>> And many many more who contributed indirectly, by reporting bugs,
>>> participating in discussion threads, providing feedback...
>>>
>>> Pharo 3.0 is the largest step we took since we started. Yet, it’s just a
>>> step. Expect more. Much more.
>>>
>>> Enjoy!
>>> The Pharo Team
>>>
>>
>>
>
>
> --
> www.tudorgirba.com
>
> "Every thing has its own flow"
>
>
>

Re: [Pharo-users] Pharo 3.0 Released!

[kmo]

A brilliant achievement and the new website is great too!



--
View this message in context: 
http://forum.world.st/Pharo-3-0-Released-tp4757227p4757398.html
Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

Re: [Pharo-users] Pharo 3 minor issue

[Esteban Lorenzano]

thanks for reporting, I will look at it (super weird that it did not arise 
before :( )

Esteban

On 30 Apr 2014, at 20:54, giorgio ferraris  wrote:

> Hi, 
> 
> started looking at Pharo after many years.
> First of all, you all did an awesome works, thank you! 
> There is a small problems on System Browser
>  open image
> open system browser
> choose one class 
> select group
> The class side checkbox is enabled, if you check it, you get a wall bak .
> Giorgio
> 
> 

Re: [Pharo-users] Pharo 3.0 Released!

[Marcus Denker]

On 30 Apr 2014, at 22:57, Tudor Girba  wrote:

> Hi,
> 
> It means that we are so happy that CodeCity is

Maybe we should have added a link to the code city page (it kind of crossed my 
mind, but then there where so many things to do
that I forgot it…)

> built in Pharo and that we can draw Pharo so beautifully from within Pharo. 
> The same applies for Roassal :)
> 
> Doru
> 
> 
> On Wed, Apr 30, 2014 at 5:51 PM, Richard Wettel  wrote:
> Congratulations to the big Pharo family!
> Ricky
> P.S. What does "built with Pharo for Pharo" mean?
> —
> Sent from Mailbox
> 
> 
> On Wed, Apr 30, 2014 at 4:02 PM, Esteban Lorenzano  
> wrote:
> 
> Dear World,
> 
> Pharo 3.0 (http://www.pharo.org) is here.
> 
> 
> 
> The past year seemed short as we got busy building more than usual. Many 
> things have changed in Pharo. Here are the highlights:
> - The new modular Opal compiler is now the default compiler used in the 
> system.
> - The Athens vector graphics canvas is now integrated and it supports Cairo 
> rendering on all platforms.
> - Many tools have been rewritten using Spec, a new framework for building 
> user interfaces.
> - Versionner and Kommiter are two of the new development tools.
> - RPackage, a new package mechanism got enhanced with tags and is fully 
> integrated in the system.
> - The debugger model was rewritten to become modular, the inspector received 
> a bump to support multiple views, and the Nautilus code browser supports 
> tags, search and lot more improvements.
> - Morphic has seen many cleanings and improvements and the visual theme has 
> been revamped.
> 
> These are just the more prominent highlights, but the details are just as 
> important. We have closed 2364 issues in Pharo 3 (compared with 1727 issues 
> in Pharo 2). Take a moment to go through a more detailed recount of the 
> progress:
> 
> https://github.com/pharo-project/ChangeLogs/blob/master/Pharo30ChangeLogs.md
> 
> Pharo is improving on many fronts. Just take a look at the code city of Pharo 
> (built with Pharo for Pharo). Every building is a class, and the red bricks 
> represent the modified methods in Pharo 3. 
> 
> 
> 
> Many things are changing but the system gets more stable. Moving from Pharo 2 
> to Pharo 3 is almost a matter of just loading the code.
> 
> Remember that Pharo is your platform. We thank all the contributors of this 
> release: Jean-Baptiste Arnaud, Simon Allier, Philippe Back, Clément Bera, 
> Alexandre Bergel, Torsten Bergmann, Usman Bhatti, Vincent Blondeau, Noury 
> Bouraqadi, Johan Brichau, Camillo Bruni, Sven Van Caekenberghe, Damien 
> Cassou, Nicolas Cellier, Guido Chari, Dimitris Chloupis, Bernardo Contreras, 
> Ben Coman, Gabriel Omar Cotelli, Jordi Delgado, Tommaso Del Sasso, Gisela 
> Decuzzi, Christophe Demarey, Sean DeNigris, Marcus Denker, Martin Dias, Erwan 
> Douaille, Stephane Ducasse, Stephan Eggermont, Pablo Estefo, Luc Fabresse, 
> Johan Fabry, Hilaire Fernandes, Nahuel Garbezza, Leo Gassman, Lucas Giudice, 
> Tudor Girba, Thierry Goubier, Norbert Hartl, Dale Henrichs, Pablo Herrero, 
> Nicolai Hess, Andre Hora, Alejandro Infante, Ricardo Jacas, Henrik Sperre 
> Johansen, Denis Kudryashov, Pavel Krivanek, Juraj Kubelka, Laurent Laffont, 
> Jannik Laval, Max Leske, David Lewis, Diego Lont, Esteban Lorenzano, Stefan 
> Marr, Mariano Martinez Peck, Roberto Minelli, Hernan Morales Durand, Eliot 
> Miranda, Fernando Olivero, Nicolas Papagna Maldonado, Nick Papoylias, Nicolas 
> Passerini, Vanessa Peña, Nicolas Petton, Alain Plantec, Guillermo Polito, 
> Damien Pollet, Jochen Rick, Benjamin Van Ryseghem, Ronie Salgado, Camille 
> Teruel, Juan Pablo Sandoval Alcocer, Samir Saleh, Frank Shearar, Igor 
> Stasenko, Aliaksei Syrel, Sebastian Tleye, Yuriy Tymchuk, Andres Valloud, 
> Martin Walk, Hernan Wilkinson. 
> And many many more who contributed indirectly, by reporting bugs, 
> participating in discussion threads, providing feedback...
> 
> Pharo 3.0 is the largest step we took since we started. Yet, it’s just a 
> step. Expect more. Much more.
> 
> Enjoy!
> The Pharo Team
> 
> 
> 
> 
> -- 
> www.tudorgirba.com
> 
> "Every thing has its own flow"