- Pharo-dev - lists.pharo.org

[Pharo-project] [ANN] Pharo 2.0

by Marcus Denker

We are proud to announce the release of Pharo 2.0! You can find information about Pharo at: http://www.pharo-project.org About this release ------------------ All in all, there were over 1600 issues treated in the issue tracker and 1350 improvements integrated into 2.0. http://code.google.com/p/pharo/issues/list?can=1&q=Milestone%3D2.0+status%3… Read it again, yes 1350 is huge, take two minutes and have a look at the list of improvements! Now you got the feel of the effort. And this was a true community effort. It is possible because people worldwide helped! We want to deeply thank them. We want to thank Inria for its constant support, in particular for the salary of Igor Stasenko and Esteban Lorenzano, and for the help in the infrastructure. We have accomplished this huge task for a better system because we were together. Do not forget that we are working on a consortium to support our system: - http://consortium.pharo.org (for companies and organizations) - http://association.pharo.org (for individuals) Our goal is to build a system so that we can make a living with our creativity and programming skills. You can find information about Pharo on http://www.pharo-project.org. In particular, you may be interested in: - Joining us and getting help http://www.pharo-project.org/community - Getting the Pharo By Example book (available as a free PDF): http://www.pharobyexample.org - Watching the screencasts http://www.pharocasts.com - Reporting problems http://www.pharo-project.org/community/issue-tracking - Reading the forth coming book http://rmod.lille.inria.fr/pbe2 - Reading the Pharo vision document http://bit.ly/HNkEru Thanks a lot for your participation, energy and fun. -- The Pharo Team Summarized issues for 2.0 ================== UI --- - Spec - Widget enhancements - Layout improvements/cleanups - Keybindings - New icons (famfam) - Growl style notifications - Revamp progress bar Developer tools --------------- - Nautilus browser - Critics browser - Improved version diff browsing - Spotlight - Revamp Code Completion and smart chars - Interactive navigation using ctrl/cmd+click over classes/methods - Shout themes - Andreas profiler Networking ----------- - Update Zinc - Zodiac (SSL) System ------- - System Announcer - RPackage replacing PackageInfo - Command line tools / Headless mode - Native boost - Update Ring metamodel - Fuel serializer - Freetype fonts Kernel ------ - DateAndTime refactoring - Updated FileSystem and replaced FileDirectory VM -- - Latests cog builds - SSLPlugin - FilePlugin enhancements - SocketPlugin fixes - Included libraries: freetype2, cairo Cleanups ------------- - FileDirectory removed (replaced by FileSystem) - SmartRefStream and ReferenceStream removed (replaced by Fuel) - PackageInfo deprecated (replaced by RPackage) Other ------- - Zeroconf scripts - Continuous Integration for every aspect of our release process. Not all the changes are reported here, but this is to give you an impression, you can find better explanation here: https://code.google.com/p/pharo/wiki/ActionsInPharo20

March 18, 2013

Re: [Pharo-project] moose job on jenkins

by Tudor Girba

Hi, You only should add the tag on the class side if you want to have a shortcut for the command. Indeed, I added these short names on the class side for our commands. Cheers, Doru On Mon, Mar 18, 2013 at 9:10 AM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > Doru in your blog you did not mention if you added the tag on the class > side of the handler. > I have the impression that you have to. > May be I could use your blog as an example for the zeroConfig chapter. > > > Stef > > On Mar 18, 2013, at 8:26 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > Hi Camillo, > > > > Something happened with the execution rights of the scripts because in > the meantime: > > wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh | > bash > > wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharoLatestVM.sh| bash > > > > do not have execution rights. > > > > Cheers, > > Doru > > > > > > On Mar 18, 2013, at 7:37 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > >> Hi Camillo, > >> > >> Thanks for the remarks. > >> > >> We (or at least I :)) want to use the latest of everything :). Moose > switched to developing on bleeding edge about 7 years ago, and the only > thing that still remained fixed was the VM. > >> > >> Now, we work with the latest VM and like that we can check integration > and give feedback. I guess this is particularly important now that you > chose Moose to be one of the benchmarks for the VM stability. > >> > >> If it will really not work, we will use the stable one, but at the > moment, it works :) > >> > >> Cheers, > >> Doru > >> > >> > >> On Mar 17, 2013, at 11:20 PM, Camillo Bruni <camillobruni(a)gmail.com> > wrote: > >> > >>> Nice! good to see ;) > >>> > >>> Some little remarks: > >>> > >>> - `wget --quiet -qO` can be simplified as `wget --quiet -O -` > >>> since -q is just the short form for --quiet ;) > >>> - I would not use the ciPharoVMLatest.sh but ciPharoVM.sh > >>> since Latest might break unexpectedly whereas ciPharoVM.sh points to > >>> latest stable release > >>> > >>> best cami > >>> > >>> On 2013-03-17, at 22:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >>>> Hi, > >>>> > >>>> I put together a little description of how we built the Moose job on > Jenkins using the CommandLine infrastructure. Perhaps it is useful for > other people as well: > >>>> http://www.tudorgirba.com/blog/moose-4-8-on-jenkins > >>>> > >>>> Cheers, > >>>> Doru > >>>> > >>>> -- > >>>> www.tudorgirba.com > >>>> > >>>> "Be rather willing to give than demanding to get." > >>>> > >>>> > >>>> > >>>> > >>> > >>> > >> > >> -- > >> www.tudorgirba.com > >> > >> "Reasonable is what we are accustomed with." > >> > > > > -- > > www.tudorgirba.com > > > > "In a world where everything is moving ever faster, > > one might have better chances to win by moving slower." > > > > > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

March 18, 2013

Re: [Pharo-project] Bug with drag and drop

by Benjamin

Unluckily, yesâ¦ We all have to... Ben On Mar 18, 2013, at 9:24 AM, jannik laval <jannik.laval(a)gmail.com> wrote: > Ok, > > Thanks for the answer. > So, I have just to wait and see :) > > Jannik > > 2013/3/18 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > Because we are fighting with the INRIA national it guys to have a server with ports 80 and 443 openâ¦ > > And of course, it took 4 days for a ticket to be addressed, plus it still doesn't work, plus do you expect them to work before 10 am or after 4pm ? > > > So the website is ready for deployment since 2 weeks, but we are waiting â¦ > (that why bugs.pharo.org is down, because already pointing to the new server â¦) > > Ben > > On Mar 18, 2013, at 9:09 AM, jannik laval <jannik.laval(a)gmail.com> wrote: > >> Ok, no problÃ¨me for me. >> >> But I do not understand why you are creating accounts manually ?! >> Is it a private betatest ? >> >> As soon as possible, the pharo website should be updated: this is the link to google tracker that is available. >> >> Jannik >> >> 2013/3/18 stephane ducasse <stephane.ducasse(a)free.fr> >> in the future we will have >> >> bugs.pharo.org >> >> Stef >> >> On Mar 17, 2013, at 9:11 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> >>> https://pharo.fogbugz.com >>> >>> And I am adding you right now (still waiting for Penelope) >>> >>> Ben >>> >>> On Mar 17, 2013, at 9:03 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: >>> >>>> ok, where is it ? >>>> >>>> Jannik >>>> >>>> On Mar 17, 2013, at 9:01 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>>> >>>>> fogz bugs :) >>>>> >>>>> On Mar 17, 2013, at 7:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>>> >>>>>> Hi all, >>>>>> >>>>>> I have a bug with drag and dropping windows inside Pharo. >>>>>> For example, take Nautilus and drag-drop the browser outside pharo. >>>>>> It should come back to its place, but there is a MessageNotUnderstood: SmallInteger>>extent: >>>>>> >>>>>> Another question: should I use GoogleCode issue tracking or fogbugs ? >>>>>> >>>>>> Cheers, >>>>>> Jannik >>>>> >>>>> >>>> >>>> >>> >> >> >> >> >> -- >> ~~Dr. Jannik Laval~~ >> Ãcole des Mines de Douai >> Enseignant-chercheur >> http://www.jannik-laval.eu >> > > > > > -- > ~~Dr. Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu >

March 18, 2013

Re: [Pharo-project] Bug with drag and drop

by jannik laval

Ok, Thanks for the answer. So, I have just to wait and see :) Jannik 2013/3/18 Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> > Because we are fighting with the INRIA national it guys to have a server > with ports 80 and 443 openâ¦ > > And of course, it took 4 days for a ticket to be addressed, plus it still > doesn't work, plus do you expect them to work before 10 am or after 4pm ? > > > So the website is ready for deployment since 2 weeks, but we are waiting â¦ > (that why bugs.pharo.org is down, because already pointing to the new > server â¦) > > Ben > > On Mar 18, 2013, at 9:09 AM, jannik laval <jannik.laval(a)gmail.com> wrote: > > Ok, no problÃ¨me for me. > > But I do not understand why you are creating accounts manually ?! > Is it a private betatest ? > > As soon as possible, the pharo website should be updated: this is the link > to google tracker that is available. > > Jannik > > 2013/3/18 stephane ducasse <stephane.ducasse(a)free.fr> > >> in the future we will have >> >> bugs.pharo.org >> >> Stef >> >> On Mar 17, 2013, at 9:11 PM, Benjamin < >> benjamin.vanryseghem.pharo(a)gmail.com> wrote: >> >> https://pharo.fogbugz.com >> >> And I am adding you right now (still waiting for Penelope) >> >> Ben >> >> On Mar 17, 2013, at 9:03 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: >> >> ok, where is it ? >> >> Jannik >> >> On Mar 17, 2013, at 9:01 PM, stephane ducasse <stephane.ducasse(a)free.fr> >> wrote: >> >> fogz bugs :) >> >> On Mar 17, 2013, at 7:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: >> >> Hi all, >> >> I have a bug with drag and dropping windows inside Pharo. >> For example, take Nautilus and drag-drop the browser outside pharo. >> It should come back to its place, but there is a MessageNotUnderstood: >> SmallInteger>>extent: >> >> Another question: should I use GoogleCode issue tracking or fogbugs ? >> >> Cheers, >> Jannik >> >> >> >> >> >> >> >> > > > -- > > ~~Dr. Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu > > > -- ~~Dr. Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu

March 18, 2013

Re: [Pharo-project] Bug with drag and drop

by Benjamin

Because we are fighting with the INRIA national it guys to have a server with ports 80 and 443 openâ¦ And of course, it took 4 days for a ticket to be addressed, plus it still doesn't work, plus do you expect them to work before 10 am or after 4pm ? So the website is ready for deployment since 2 weeks, but we are waiting â¦ (that why bugs.pharo.org is down, because already pointing to the new server â¦) Ben On Mar 18, 2013, at 9:09 AM, jannik laval <jannik.laval(a)gmail.com> wrote: > Ok, no problÃ¨me for me. > > But I do not understand why you are creating accounts manually ?! > Is it a private betatest ? > > As soon as possible, the pharo website should be updated: this is the link to google tracker that is available. > > Jannik > > 2013/3/18 stephane ducasse <stephane.ducasse(a)free.fr> > in the future we will have > > bugs.pharo.org > > Stef > > On Mar 17, 2013, at 9:11 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > >> https://pharo.fogbugz.com >> >> And I am adding you right now (still waiting for Penelope) >> >> Ben >> >> On Mar 17, 2013, at 9:03 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: >> >>> ok, where is it ? >>> >>> Jannik >>> >>> On Mar 17, 2013, at 9:01 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >>> >>>> fogz bugs :) >>>> >>>> On Mar 17, 2013, at 7:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: >>>> >>>>> Hi all, >>>>> >>>>> I have a bug with drag and dropping windows inside Pharo. >>>>> For example, take Nautilus and drag-drop the browser outside pharo. >>>>> It should come back to its place, but there is a MessageNotUnderstood: SmallInteger>>extent: >>>>> >>>>> Another question: should I use GoogleCode issue tracking or fogbugs ? >>>>> >>>>> Cheers, >>>>> Jannik >>>> >>>> >>> >>> >> > > > > > -- > ~~Dr. Jannik Laval~~ > Ãcole des Mines de Douai > Enseignant-chercheur > http://www.jannik-laval.eu >

March 18, 2013

Re: [Pharo-project] moose job on jenkins

by stephane ducasse

Doru in your blog you did not mention if you added the tag on the class side of the handler. I have the impression that you have to. May be I could use your blog as an example for the zeroConfig chapter. Stef On Mar 18, 2013, at 8:26 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Camillo, > > Something happened with the execution rights of the scripts because in the meantime: > wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh | bash > wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharoLatestVM.sh | bash > > do not have execution rights. > > Cheers, > Doru > > > On Mar 18, 2013, at 7:37 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi Camillo, >> >> Thanks for the remarks. >> >> We (or at least I :)) want to use the latest of everything :). Moose switched to developing on bleeding edge about 7 years ago, and the only thing that still remained fixed was the VM. >> >> Now, we work with the latest VM and like that we can check integration and give feedback. I guess this is particularly important now that you chose Moose to be one of the benchmarks for the VM stability. >> >> If it will really not work, we will use the stable one, but at the moment, it works :) >> >> Cheers, >> Doru >> >> >> On Mar 17, 2013, at 11:20 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> Nice! good to see ;) >>> >>> Some little remarks: >>> >>> - `wget --quiet -qO` can be simplified as `wget --quiet -O -` >>> since -q is just the short form for --quiet ;) >>> - I would not use the ciPharoVMLatest.sh but ciPharoVM.sh >>> since Latest might break unexpectedly whereas ciPharoVM.sh points to >>> latest stable release >>> >>> best cami >>> >>> On 2013-03-17, at 22:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> Hi, >>>> >>>> I put together a little description of how we built the Moose job on Jenkins using the CommandLine infrastructure. Perhaps it is useful for other people as well: >>>> http://www.tudorgirba.com/blog/moose-4-8-on-jenkins >>>> >>>> Cheers, >>>> Doru >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Be rather willing to give than demanding to get." >>>> >>>> >>>> >>>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Reasonable is what we are accustomed with." >> > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > >

March 18, 2013

Re: [Pharo-project] Bug with drag and drop

by jannik laval

Ok, no problÃ¨me for me. But I do not understand why you are creating accounts manually ?! Is it a private betatest ? As soon as possible, the pharo website should be updated: this is the link to google tracker that is available. Jannik 2013/3/18 stephane ducasse <stephane.ducasse(a)free.fr> > in the future we will have > > bugs.pharo.org > > Stef > > On Mar 17, 2013, at 9:11 PM, Benjamin < > benjamin.vanryseghem.pharo(a)gmail.com> wrote: > > https://pharo.fogbugz.com > > And I am adding you right now (still waiting for Penelope) > > Ben > > On Mar 17, 2013, at 9:03 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: > > ok, where is it ? > > Jannik > > On Mar 17, 2013, at 9:01 PM, stephane ducasse <stephane.ducasse(a)free.fr> > wrote: > > fogz bugs :) > > On Mar 17, 2013, at 7:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: > > Hi all, > > I have a bug with drag and dropping windows inside Pharo. > For example, take Nautilus and drag-drop the browser outside pharo. > It should come back to its place, but there is a MessageNotUnderstood: > SmallInteger>>extent: > > Another question: should I use GoogleCode issue tracking or fogbugs ? > > Cheers, > Jannik > > > > > > > > -- ~~Dr. Jannik Laval~~ Ãcole des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu

March 18, 2013

Re: [Pharo-project] Bug with drag and drop

by stephane ducasse

in the future we will have bugs.pharo.org Stef On Mar 17, 2013, at 9:11 PM, Benjamin <benjamin.vanryseghem.pharo(a)gmail.com> wrote: > https://pharo.fogbugz.com > > And I am adding you right now (still waiting for Penelope) > > Ben > > On Mar 17, 2013, at 9:03 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: > >> ok, where is it ? >> >> Jannik >> >> On Mar 17, 2013, at 9:01 PM, stephane ducasse <stephane.ducasse(a)free.fr> wrote: >> >>> fogz bugs :) >>> >>> On Mar 17, 2013, at 7:29 PM, jannik.laval <jannik.laval(a)gmail.com> wrote: >>> >>>> Hi all, >>>> >>>> I have a bug with drag and dropping windows inside Pharo. >>>> For example, take Nautilus and drag-drop the browser outside pharo. >>>> It should come back to its place, but there is a MessageNotUnderstood: SmallInteger>>extent: >>>> >>>> Another question: should I use GoogleCode issue tracking or fogbugs ? >>>> >>>> Cheers, >>>> Jannik >>> >>> >> >> >

March 18, 2013

Re: [Pharo-project] moose job on jenkins

by Tudor Girba

Never mind. My bad. Doru On Mar 18, 2013, at 8:26 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Camillo, > > Something happened with the execution rights of the scripts because in the meantime: > wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh | bash > wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharoLatestVM.sh | bash > > do not have execution rights. > > Cheers, > Doru > > > On Mar 18, 2013, at 7:37 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > >> Hi Camillo, >> >> Thanks for the remarks. >> >> We (or at least I :)) want to use the latest of everything :). Moose switched to developing on bleeding edge about 7 years ago, and the only thing that still remained fixed was the VM. >> >> Now, we work with the latest VM and like that we can check integration and give feedback. I guess this is particularly important now that you chose Moose to be one of the benchmarks for the VM stability. >> >> If it will really not work, we will use the stable one, but at the moment, it works :) >> >> Cheers, >> Doru >> >> >> On Mar 17, 2013, at 11:20 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: >> >>> Nice! good to see ;) >>> >>> Some little remarks: >>> >>> - `wget --quiet -qO` can be simplified as `wget --quiet -O -` >>> since -q is just the short form for --quiet ;) >>> - I would not use the ciPharoVMLatest.sh but ciPharoVM.sh >>> since Latest might break unexpectedly whereas ciPharoVM.sh points to >>> latest stable release >>> >>> best cami >>> >>> On 2013-03-17, at 22:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> Hi, >>>> >>>> I put together a little description of how we built the Moose job on Jenkins using the CommandLine infrastructure. Perhaps it is useful for other people as well: >>>> http://www.tudorgirba.com/blog/moose-4-8-on-jenkins >>>> >>>> Cheers, >>>> Doru >>>> >>>> -- >>>> www.tudorgirba.com >>>> >>>> "Be rather willing to give than demanding to get." >>>> >>>> >>>> >>>> >>> >>> >> >> -- >> www.tudorgirba.com >> >> "Reasonable is what we are accustomed with." >> > > -- > www.tudorgirba.com > > "In a world where everything is moving ever faster, > one might have better chances to win by moving slower." > > > -- www.tudorgirba.com "If you interrupt the barber while he is cutting your hair, you will end up with a messy haircut."

March 18, 2013

Re: [Pharo-project] moose job on jenkins

by Tudor Girba

Hi Camillo, Something happened with the execution rights of the scripts because in the meantime: wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharo20.sh | bash wget --quiet - http://pharo.gforge.inria.fr/ci/script/ciPharoLatestVM.sh | bash do not have execution rights. Cheers, Doru On Mar 18, 2013, at 7:37 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi Camillo, > > Thanks for the remarks. > > We (or at least I :)) want to use the latest of everything :). Moose switched to developing on bleeding edge about 7 years ago, and the only thing that still remained fixed was the VM. > > Now, we work with the latest VM and like that we can check integration and give feedback. I guess this is particularly important now that you chose Moose to be one of the benchmarks for the VM stability. > > If it will really not work, we will use the stable one, but at the moment, it works :) > > Cheers, > Doru > > > On Mar 17, 2013, at 11:20 PM, Camillo Bruni <camillobruni(a)gmail.com> wrote: > >> Nice! good to see ;) >> >> Some little remarks: >> >> - `wget --quiet -qO` can be simplified as `wget --quiet -O -` >> since -q is just the short form for --quiet ;) >> - I would not use the ciPharoVMLatest.sh but ciPharoVM.sh >> since Latest might break unexpectedly whereas ciPharoVM.sh points to >> latest stable release >> >> best cami >> >> On 2013-03-17, at 22:02, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> Hi, >>> >>> I put together a little description of how we built the Moose job on Jenkins using the CommandLine infrastructure. Perhaps it is useful for other people as well: >>> http://www.tudorgirba.com/blog/moose-4-8-on-jenkins >>> >>> Cheers, >>> Doru >>> >>> -- >>> www.tudorgirba.com >>> >>> "Be rather willing to give than demanding to get." >>> >>> >>> >>> >> >> > > -- > www.tudorgirba.com > > "Reasonable is what we are accustomed with." > -- www.tudorgirba.com "In a world where everything is moving ever faster, one might have better chances to win by moving slower."

March 18, 2013