March 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Alexandre Bergel

I do not have a definite answer. I personally prefer O2 instead of OB. OB is more stable though, which is a big advantage. Maybe a pool will help the community to say its word on it? Whether it wants to see O2 included or not in Pharo 1.0. Like this, you will not have to make an arbitrary decision. just an idea. Cheers, Alexandre On 24 Mar 2010, at 08:49, Mariano Martinez Peck wrote: > > > On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > Hi Mariano, > > I wonder why you mentioned O2 issues below because O2 is not in > Pharo anymore, isn't it? > > > Sorry Adrian. I forgot about this email. I answer to the mail as it > has an excellent question and my bad :) > > I put the O2 issues because: > > - I think it is a "official package that works on Pharo" even if we > don't know what a official package is. > - I have to create a version of the metacello configuration for O2 > and I wanted to put the issues in the "description" of the release > - The O2 issues were submitted in Pharo issue tracking, thus, I > wanted to put them as closed and put "integrated in PharoXXX" > - I changed the welcome workspace to load this new version of O2 > > However, it doesn't mean that O2 is now included in Dev images. Now > you made me realize that this can be confusing. So, what should I > do ? I am all ears :) > > > Cheers, > Adrian > > On Mar 20, 2010, at 20:40 , Mariano Martinez Peck wrote: > > > Hi folks. We are proud to announce the (hopefully) last RC3 for > Pharo 1.0. > > > > This image is based in PharoCore-1.0-10515rc3. The image also > contain lot of > > fixes and improvements of external packages: > > > > These, are the fixed issues of the external tools: > > > > OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 > > > > O2: issues 1887, 1312, 1429, 1886, 2073 > > > > New Inspector: issues 1783, 1499 > > > > Refactoring Browser: issue 2108 > > > > The link is: > > https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… > > > > Cheers > > > > Mariano > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

March 24, 2010

[Pharo-project] Montacello configuration writing

by Hilaire Fernandes

Learning Montacello configuration. Instead of writing a package dependency as spec package: 'CoolToolSet--Core' with: [spec requires: 'CoolBrowser ALL'] Can't we write more clearly as; spec package: 'CoolToolSet--Core' requires: 'CoolBrowser ALL' I find the first one far too cryptic. Hilaire

March 24, 2010

[Pharo-project] [GSoC] Call for students

by Mariano Martinez Peck

Dear Students, Now it is your turn! You will have to register in our website, put there some information, show interest for the projects and contact the project mentors. After the registration step you will get all the mentors information in order to contact them. By pressing the button on the project, you will show your interest. This is not something formal yet. Our mentors will vote for the most interesting projects and in the middle of the voting Google will tell us, how many projects will actually be funded. Voting will happen in April, with final results expected at the end of April. At that time you will finally know if you are accepted or not. Of course, there can be many students interested per project. This means that interest for this project is high, but on the other side a chance that you will be chosen is lower. It is up to you to convince a mentor that you are the best! Note also that the Ideas page is deprecated. On ideas page just the project ideas were collected. Now, we are preparing the real projects. So, please from now on always refer to this link for the projects: http://gsoc2010.esug.org/projects So, the initial steps are: 1. Register on our special Smalltalk GSoC website: http://gsoc2010.esug.org/registration 2. Edit your profile to get some more contact information for mentors to let you know, 3. Fulfill your brief Biography page (see Biography tab on profile), 4. Go to Projects page, choose up to three projects and click there I'm interested button, 5. Contact and discuss with project mentors about your interest. You will be also subscribed to a special mailing list [1] where we will help you with further steps. Deadline: as soon as possible, because the deadline to register on official GSoC website [2] is 9.April, which is, well, soon! But about that later... Finally, we will really appreciate if you can help us to distribute this call for students. One of our goals is to increase the Smalltalk community. Those who have access to universities can distribute this among the students. GSoC Admin Team esug.gsoc.adm2010(a)gmail.com http://gsoc2010.esug.org [1] Students mailing list: http://groups.google.com/group/smalltalk-gsoc-students mailto:smalltalk-gsoc-students@googlegroups.com [2] Official GSoC website http://socghop.appspot.com/

March 24, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Simon Denier

On 24 mars 2010, at 15:03, Alexandre Bergel wrote: > I do not have a definite answer. I personally prefer O2 instead of OB. OB is more stable though, which is a big advantage. > Maybe a pool will help the community to say its word on it? Whether it wants to see O2 included or not in Pharo 1.0. Like this, you will not have to make an arbitrary decision. just an idea. I recently came back to O2 and it's a huge relief in usability. However as Alex puts it, OB is more stable (for example in O2, I just noticed that I dont have anymore the completion in the mercury bar). In favor of pushing 1.0 release, I am for keeping OB because it is stable. However, I remember that it also impacts the book pharo by example, which has to use only one browser. > > Cheers, > Alexandre > > > On 24 Mar 2010, at 08:49, Mariano Martinez Peck wrote: > >> >> >> On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: >> Hi Mariano, >> >> I wonder why you mentioned O2 issues below because O2 is not in Pharo anymore, isn't it? >> >> >> Sorry Adrian. I forgot about this email. I answer to the mail as it has an excellent question and my bad :) >> >> I put the O2 issues because: >> >> - I think it is a "official package that works on Pharo" even if we don't know what a official package is. >> - I have to create a version of the metacello configuration for O2 and I wanted to put the issues in the "description" of the release >> - The O2 issues were submitted in Pharo issue tracking, thus, I wanted to put them as closed and put "integrated in PharoXXX" >> - I changed the welcome workspace to load this new version of O2 >> >> However, it doesn't mean that O2 is now included in Dev images. Now you made me realize that this can be confusing. So, what should I do ? I am all ears :) >> >> >> Cheers, >> Adrian >> >> On Mar 20, 2010, at 20:40 , Mariano Martinez Peck wrote: >> >> > Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo 1.0. >> > >> > This image is based in PharoCore-1.0-10515rc3. The image also contain lot of >> > fixes and improvements of external packages: >> > >> > These, are the fixed issues of the external tools: >> > >> > OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 >> > >> > O2: issues 1887, 1312, 1429, 1886, 2073 >> > >> > New Inspector: issues 1783, 1499 >> > >> > Refactoring Browser: issue 2108 >> > >> > The link is: >> > https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… >> > >> > Cheers >> > >> > Mariano >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Simon

March 24, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Adrian Lienhard

For Pharo 1.0 it is clear that it does not include O2. For Pharo 1.1 we can consider adding it again if it is stable and people express their interest in it. So, Mariano, until we add O2 back into the main release, you don't need to mention it anymore as part of the release log. Of course, if there are new versions and fixes please mention them in a separate thread as it is good to communicate any progress of internal and external packages. Cheers, Adrian On Mar 24, 2010, at 14:15 , Mariano Martinez Peck wrote: > Sorry. Want I wanted to ask is...for next Pharo releases, I do the same but > making clear O2 is not by default ? or I just don't say anything about O2 > in the release ? > > On Wed, Mar 24, 2010 at 3:03 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > >> I do not have a definite answer. I personally prefer O2 instead of OB. OB >> is more stable though, which is a big advantage. >> Maybe a pool will help the community to say its word on it? Whether it >> wants to see O2 included or not in Pharo 1.0. Like this, you will not have >> to make an arbitrary decision. just an idea. >> >> Cheers, >> Alexandre >> >> >> >> On 24 Mar 2010, at 08:49, Mariano Martinez Peck wrote: >> >> >>> >>> On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard <adi(a)netstyle.ch> >>> wrote: >>> Hi Mariano, >>> >>> I wonder why you mentioned O2 issues below because O2 is not in Pharo >>> anymore, isn't it? >>> >>> >>> Sorry Adrian. I forgot about this email. I answer to the mail as it has an >>> excellent question and my bad :) >>> >>> I put the O2 issues because: >>> >>> - I think it is a "official package that works on Pharo" even if we don't >>> know what a official package is. >>> - I have to create a version of the metacello configuration for O2 and I >>> wanted to put the issues in the "description" of the release >>> - The O2 issues were submitted in Pharo issue tracking, thus, I wanted to >>> put them as closed and put "integrated in PharoXXX" >>> - I changed the welcome workspace to load this new version of O2 >>> >>> However, it doesn't mean that O2 is now included in Dev images. Now you >>> made me realize that this can be confusing. So, what should I do ? I am all >>> ears :) >>> >>> >>> Cheers, >>> Adrian >>> >>> On Mar 20, 2010, at 20:40 , Mariano Martinez Peck wrote: >>> >>>> Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo >>> 1.0. >>>> >>>> This image is based in PharoCore-1.0-10515rc3. The image also contain >>> lot of >>>> fixes and improvements of external packages: >>>> >>>> These, are the fixed issues of the external tools: >>>> >>>> OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 >>>> >>>> O2: issues 1887, 1312, 1429, 1886, 2073 >>>> >>>> New Inspector: issues 1783, 1499 >>>> >>>> Refactoring Browser: issue 2108 >>>> >>>> The link is: >>>> >>> https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… >>>> >>>> Cheers >>>> >>>> Mariano >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 24, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Mariano Martinez Peck

Sorry. Want I wanted to ask is...for next Pharo releases, I do the same but making clear O2 is not by default ? or I just don't say anything about O2 in the release ? On Wed, Mar 24, 2010 at 3:03 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > I do not have a definite answer. I personally prefer O2 instead of OB. OB > is more stable though, which is a big advantage. > Maybe a pool will help the community to say its word on it? Whether it > wants to see O2 included or not in Pharo 1.0. Like this, you will not have > to make an arbitrary decision. just an idea. > > Cheers, > Alexandre > > > > On 24 Mar 2010, at 08:49, Mariano Martinez Peck wrote: > > >> >> On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >> Hi Mariano, >> >> I wonder why you mentioned O2 issues below because O2 is not in Pharo >> anymore, isn't it? >> >> >> Sorry Adrian. I forgot about this email. I answer to the mail as it has an >> excellent question and my bad :) >> >> I put the O2 issues because: >> >> - I think it is a "official package that works on Pharo" even if we don't >> know what a official package is. >> - I have to create a version of the metacello configuration for O2 and I >> wanted to put the issues in the "description" of the release >> - The O2 issues were submitted in Pharo issue tracking, thus, I wanted to >> put them as closed and put "integrated in PharoXXX" >> - I changed the welcome workspace to load this new version of O2 >> >> However, it doesn't mean that O2 is now included in Dev images. Now you >> made me realize that this can be confusing. So, what should I do ? I am all >> ears :) >> >> >> Cheers, >> Adrian >> >> On Mar 20, 2010, at 20:40 , Mariano Martinez Peck wrote: >> >> > Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo >> 1.0. >> > >> > This image is based in PharoCore-1.0-10515rc3. The image also contain >> lot of >> > fixes and improvements of external packages: >> > >> > These, are the fixed issues of the external tools: >> > >> > OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 >> > >> > O2: issues 1887, 1312, 1429, 1886, 2073 >> > >> > New Inspector: issues 1783, 1499 >> > >> > Refactoring Browser: issue 2108 >> > >> > The link is: >> > >> https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… >> > >> > Cheers >> > >> > Mariano >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 24, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Adrian Lienhard

On Mar 24, 2010, at 13:56 , Mariano Martinez Peck wrote: > On Wed, Mar 24, 2010 at 1:53 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > >> Hi Mariano, >> >> No problem. I was just a bit confused because I was not sure whether you >> intended to add O2 back into Pharo 1.0 ;) >> > > > Yes, I know. But I asked what do you think because I don't want to get more > users confused ahahhaha Sorry, I don't understand what you mean. Think about what? Adrian > > > >> >> Cheers, >> Adrian >> >> On Mar 24, 2010, at 13:49 , Mariano Martinez Peck wrote: >> >>> On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >>> >>>> Hi Mariano, >>>> >>>> I wonder why you mentioned O2 issues below because O2 is not in Pharo >>>> anymore, isn't it? >>>> >>>> >>> Sorry Adrian. I forgot about this email. I answer to the mail as it has >> an >>> excellent question and my bad :) >>> >>> I put the O2 issues because: >>> >>> - I think it is a "official package that works on Pharo" even if we don't >>> know what a official package is. >>> - I have to create a version of the metacello configuration for O2 and I >>> wanted to put the issues in the "description" of the release >>> - The O2 issues were submitted in Pharo issue tracking, thus, I wanted to >>> put them as closed and put "integrated in PharoXXX" >>> - I changed the welcome workspace to load this new version of O2 >>> >>> However, it doesn't mean that O2 is now included in Dev images. Now you >> made >>> me realize that this can be confusing. So, what should I do ? I am all >> ears >>> :) >>> >>> >>> >>>> Cheers, >>>> Adrian >>>> >>>> On Mar 20, 2010, at 20:40 , Mariano Martinez Peck wrote: >>>> >>>>> Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo >>>> 1.0. >>>>> >>>>> This image is based in PharoCore-1.0-10515rc3. The image also contain >> lot >>>> of >>>>> fixes and improvements of external packages: >>>>> >>>>> These, are the fixed issues of the external tools: >>>>> >>>>> OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 >>>>> >>>>> O2: issues 1887, 1312, 1429, 1886, 2073 >>>>> >>>>> New Inspector: issues 1783, 1499 >>>>> >>>>> Refactoring Browser: issue 2108 >>>>> >>>>> The link is: >>>>> >>>> >> https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… >>>>> >>>>> Cheers >>>>> >>>>> Mariano >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 24, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Mariano Martinez Peck

On Wed, Mar 24, 2010 at 1:53 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi Mariano, > > No problem. I was just a bit confused because I was not sure whether you > intended to add O2 back into Pharo 1.0 ;) > Yes, I know. But I asked what do you think because I don't want to get more users confused ahahhaha > > Cheers, > Adrian > > On Mar 24, 2010, at 13:49 , Mariano Martinez Peck wrote: > > > On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > > > >> Hi Mariano, > >> > >> I wonder why you mentioned O2 issues below because O2 is not in Pharo > >> anymore, isn't it? > >> > >> > > Sorry Adrian. I forgot about this email. I answer to the mail as it has > an > > excellent question and my bad :) > > > > I put the O2 issues because: > > > > - I think it is a "official package that works on Pharo" even if we don't > > know what a official package is. > > - I have to create a version of the metacello configuration for O2 and I > > wanted to put the issues in the "description" of the release > > - The O2 issues were submitted in Pharo issue tracking, thus, I wanted to > > put them as closed and put "integrated in PharoXXX" > > - I changed the welcome workspace to load this new version of O2 > > > > However, it doesn't mean that O2 is now included in Dev images. Now you > made > > me realize that this can be confusing. So, what should I do ? I am all > ears > > :) > > > > > > > >> Cheers, > >> Adrian > >> > >> On Mar 20, 2010, at 20:40 , Mariano Martinez Peck wrote: > >> > >>> Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo > >> 1.0. > >>> > >>> This image is based in PharoCore-1.0-10515rc3. The image also contain > lot > >> of > >>> fixes and improvements of external packages: > >>> > >>> These, are the fixed issues of the external tools: > >>> > >>> OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 > >>> > >>> O2: issues 1887, 1312, 1429, 1886, 2073 > >>> > >>> New Inspector: issues 1783, 1499 > >>> > >>> Refactoring Browser: issue 2108 > >>> > >>> The link is: > >>> > >> > https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… > >>> > >>> Cheers > >>> > >>> Mariano > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 24, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Adrian Lienhard

Hi Mariano, No problem. I was just a bit confused because I was not sure whether you intended to add O2 back into Pharo 1.0 ;) Cheers, Adrian On Mar 24, 2010, at 13:49 , Mariano Martinez Peck wrote: > On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > >> Hi Mariano, >> >> I wonder why you mentioned O2 issues below because O2 is not in Pharo >> anymore, isn't it? >> >> > Sorry Adrian. I forgot about this email. I answer to the mail as it has an > excellent question and my bad :) > > I put the O2 issues because: > > - I think it is a "official package that works on Pharo" even if we don't > know what a official package is. > - I have to create a version of the metacello configuration for O2 and I > wanted to put the issues in the "description" of the release > - The O2 issues were submitted in Pharo issue tracking, thus, I wanted to > put them as closed and put "integrated in PharoXXX" > - I changed the welcome workspace to load this new version of O2 > > However, it doesn't mean that O2 is now included in Dev images. Now you made > me realize that this can be confusing. So, what should I do ? I am all ears > :) > > > >> Cheers, >> Adrian >> >> On Mar 20, 2010, at 20:40 , Mariano Martinez Peck wrote: >> >>> Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo >> 1.0. >>> >>> This image is based in PharoCore-1.0-10515rc3. The image also contain lot >> of >>> fixes and improvements of external packages: >>> >>> These, are the fixed issues of the external tools: >>> >>> OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 >>> >>> O2: issues 1887, 1312, 1429, 1886, 2073 >>> >>> New Inspector: issues 1783, 1499 >>> >>> Refactoring Browser: issue 2108 >>> >>> The link is: >>> >> https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… >>> >>> Cheers >>> >>> Mariano >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 24, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1

by Mariano Martinez Peck

On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi Mariano, > > I wonder why you mentioned O2 issues below because O2 is not in Pharo > anymore, isn't it? > > Sorry Adrian. I forgot about this email. I answer to the mail as it has an excellent question and my bad :) I put the O2 issues because: - I think it is a "official package that works on Pharo" even if we don't know what a official package is. - I have to create a version of the metacello configuration for O2 and I wanted to put the issues in the "description" of the release - The O2 issues were submitted in Pharo issue tracking, thus, I wanted to put them as closed and put "integrated in PharoXXX" - I changed the welcome workspace to load this new version of O2 However, it doesn't mean that O2 is now included in Dev images. Now you made me realize that this can be confusing. So, what should I do ? I am all ears :) > Cheers, > Adrian > > On Mar 20, 2010, at 20:40 , Mariano Martinez Peck wrote: > > > Hi folks. We are proud to announce the (hopefully) last RC3 for Pharo > 1.0. > > > > This image is based in PharoCore-1.0-10515rc3. The image also contain lot > of > > fixes and improvements of external packages: > > > > These, are the fixed issues of the external tools: > > > > OB: Issues 1891, 1748, 1670, 1667, 1705, 1667 > > > > O2: issues 1887, 1312, 1429, 1886, 2073 > > > > New Inspector: issues 1783, 1499 > > > > Refactoring Browser: issue 2108 > > > > The link is: > > > https://gforge.inria.fr/frs/download.php/26680/Pharo-1.0-10515-rc3dev10.03.… > > > > Cheers > > > > Mariano > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

March 24, 2010