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

Re: [Pharo-project] Getting the website ready for 1.0

by Adrian Lienhard

On Mar 21, 2010, at 17:51 , Miguel Enrique CobÃ¡ Martinez wrote: > El dom, 21-03-2010 a las 12:48 +0100, Adrian Lienhard escribiÃ³: >> Hi all, >> >> I've updated the website content, in particular the following pages, which are linked from the welcome workspace: >> >> http://www.pharo-project.org/documentation/getting-started >> http://www.pharo-project.org/documentation/tutorials-books >> >> If you have any suggestions to improve the website (e.g., for the FAQ), please let me know! >> >> Cheers, >> Adrian >> >> BTW, I also updated the download links to the new Pharo RC3 image > > Shouldn't the RC process said that no download links should be updated > until the beta testers give the blessing that no new problems are found > in a new released RC? Or it was already announced the wide availability > of RC3 (not that it has any big problem so far, as I try it) Yes, you are right. I forgot that. Since there are no large changes and all seems to work fine, it should be ok this time. Adrian > > Cheers >> >> ___________________ >> http://www.adrian-lienhard.ch/ >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 21, 2010

Re: [Pharo-project] Getting the website ready for 1.0

by Adrian Lienhard

Mariano, I would wait with the workspace changes a bit and then we produce RC4 that should be identical to the final version. We also need to find a solution for the changes log. Cheers, Adrian On Mar 21, 2010, at 17:55 , Miguel Enrique CobÃ¡ Martinez wrote: > El dom, 21-03-2010 a las 17:17 +0100, Mariano Martinez Peck escribiÃ³: >> >> On Sun, Mar 21, 2010 at 5:01 PM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >> Thanks for the suggestions. I deleted the /getting-started >> page and added the content in the side column of the home >> page. I added direct links to the book and the screencast. >> >> Mariano, this means we need to update the links in the >> workspace. Please also remove the sentence "We really need >> your help to fix all these issues and to get all tests green!" >> because this is the case now :) >> >> >> So...what I do ? I take the same image, uncompress it, change >> workspace, compress, upload it again ? >> >> Regarding the links, the only thing I have to do is to remove "Getting >> started" ? or add something else ? >> > > I think that you take all those improvements and generate a last RC4 zip > and that will be the last version. That was the point of the RC, to > polish the final release. > > BTW, the changelog.txt says in the first line: > > Here is a list of packages included in this PharoCore1.0rc2 (#1 => Here > is a list of packages included in this PharoCore1.0rc3 (#1 > > the first rc2 should be rc3. > > Cheers >> Cheers, >> Adrian >> >> >> On Mar 21, 2010, at 14:01 , laurent laffont wrote: >> >>> Hi, >>> >>> "Get the Pharo By Example book" : on this page there's a lot >> more than Pharo >>> By Example. >>> >>> "Watch the Pharo Screencasts" points to >>> http://www.pharo-project.org/documentation/tutorials-books >>> >>> I think I'd rather delete the Getting Started page and put >> its content at >>> the top of the homepage, above Mission section. >>> >>> Cheers, >>> >>> Laurent Laffont >>> >>> >>> On Sun, Mar 21, 2010 at 12:48 PM, Adrian Lienhard >> <adi(a)netstyle.ch> wrote: >>> >>>> Hi all, >>>> >>>> I've updated the website content, in particular the >> following pages, which >>>> are linked from the welcome workspace: >>>> >>>> http://www.pharo-project.org/documentation/getting-started >>>> http://www.pharo-project.org/documentation/tutorials-books >>>> >>>> If you have any suggestions to improve the website (e.g., >> for the FAQ), >>>> please let me know! >>>> >>>> Cheers, >>>> Adrian >>>> >>>> BTW, I also updated the download links to the new Pharo RC3 >> image >>>> >>>> ___________________ >>>> http://www.adrian-lienhard.ch/ >>>> >>>> >>>> _______________________________________________ >>>> 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 > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 21, 2010

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

by Dale Henrichs

Yep, A metacello 1.0-beta.25 bug ... I'll fix it right now (or after breakfast:). Dale ----- "Dale Henrichs" <dale.henrichs(a)gemstone.com> wrote: | If that's the build process you use, I'm not sure why the repsitory | isn't mapped correctly ... maybe it's a metacello bug then...I will do | a build and see what I can find out... | | Dale | ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | | | On Sun, Mar 21, 2010 at 6:36 PM, Dale Henrichs | | <dale.henrichs(a)gemstone.com>wrote: | | | | > Mariano, | | > | | > I am seriously considering releasing 1.0-beta.25 today ... I have | | smacked | | > the heck out Metacello over the last three days without issues so | | I'm | | > thinking I can let this puppy out the door:)...Especially if it | will | | clean | | > up the release process... | | > | | > One other point I have noticed is that the following | configurations | | aren't | | > pointing to the correct repository: | | > | | > ConfigurationOfOmniBrowser | | > ConfigurationOfRefactoringBrowser | | > ConfigurationOfOCompletion | | > ConfigurationOfShout | | > ConfigurationOfProfStef | | > | | > They all reference the package-cache instead of SqueakSource | | > MetacelloRepository. | | > | | | | | | Thanks Dale. I didn't realise about that. | | | | | | > | | > I'm assuming this is because they were in your package-cache when | | you did | | > the build. | | > | | > | | No. I take a PharoCore image which is zip, without even the | | package-cache | | folder and then I evaluate what you can see in installScript, which | is | | : | | | | Gofer new | | gemsource: 'metacello'; | | package: 'ConfigurationOfMetacello'; | | load. | | | | | | ((Smalltalk at: #ConfigurationOfMetacello) project version: | | '1.0-beta.25') | | perform: #load. | | | | Gofer new | | squeaksource: 'MetacelloRepository'; | | package: 'ConfigurationOfPharo'; | | load. | | | | ((Smalltalk at: #ConfigurationOfPharo) project version: | | '1.0-rc3.10515') | | perform: #silently: with: true; perform: #load. | | | | | | > I think this is happening because of a recent change in the | sorting | | order | | > for Gofer ... | | > | | > | | I have no idea. | | | | | | > For the build process you may want to either make sure your | | package-cache | | > is empty | | | | | | | | My package-cache was empty. I even didn't have that folder- | | | | | | > or use disablePackageCache in the places where you explicitly load | | a | | > Configuration or perhaps something else? | | > | | > | | How can I do that ? where should I put disablePackageCache ? do you | | have a | | example? | | | | Thanks! | | | | Mariano | | | | | | | | > Dale | | > | | | | | | > ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | | > | | > | > | | > | > I see that the installScript uses ConfigurationOfMetacello | from | | > | > gemsource metacello repository instead of Metacello | repository. | | > | Given | | > | > that this will be the final release of 1.0, shouldn't we copy | | > | > ConfigurationOfMetacello to squeaksource/MetacelloRepository | so | | that | | > | the | | > | > package registered in monticello is this instead of the | | gemstone | | > | one. | | > | > This repo for ConfigurationOfMetacello overrides the one of | | > | PharoCore | | > | > that points to squeaksource. | | > | > | | > | > Dale, can you put this version in squeaksource. The release is | | very | | > | > close and anyway it will be shipped in Pharo dev 1.0, so will | | reach | | > | a | | > | > lot of people, even if not on squeaksource | | > | > | | > | > | | > | Yes. This is because I added the ImageForDevelopers in the | group. | | With | | > | that, | | > | when running headless I have the problem with the progress Bar. | | > | Then, i needed to use the silntly method, which is in Metacello | | > | beta.25 | | > | which is not released yet. That's why I have to put the other | | one. | | > | | | > | Don't worry that beta.25 will be then correctly uploaded and | | released. | | > | After | | > | that, the installScript will be even simpler as I won't need to | | > | install | | > | Metacello manually, but with the ensureMetacello ;) | | > | | | > | Cheers | | > | | | > | Mariano | | > | | | > | | | > | | | > | > Cheers | | > | > > | | > | > > Mariano | | > | > > | | > | > > _______________________________________________ | | > | > > Pharo-users mailing list | | > | > > Pharo-users(a)lists.gforge.inria.fr | | > | > > | | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users | | > | > | | > | > -- | | > | > Miguel CobÃ¡ | | > | > http://miguel.leugim.com.mx | | > | > | | > | > | | > | | | > | _______________________________________________ | | > | 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 21, 2010

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

by Mariano Martinez Peck

Miguel. Good idea. I have just commited the following in http://www.squeaksource.com/ImageForDevelopers Can you please check and change/commit as necessary ? Name: ImageForDevelopers-pharo-MarianoMartinezPeck.221 Author: MarianoMartinezPeck Time: 21 March 2010, 7:55:04 pm UUID: d30a8535-7609-4bf6-b078-546fd0ea0c1b Ancestors: ImageForDevelopers-pharo-MarianoMartinezPeck.220 - Changed size of workspaces to fix better in 800*600 - Update Magma documentation Cheers Mariano 2010/3/21 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El dom, 21-03-2010 a las 18:26 +0100, Mariano Martinez Peck escribiÃ³: > > > > > > Mee too. The image windows open in like 800x600 and the > > workspace is > > partially off-screen. > > > > > > If you see in the definition of the workspace, there are the sized. > > Can you give me a size that correctly match your needs? > > For the size the image opens in my machine, this values let see the > Pharo logo and the workspace image is fully enclosed in the image > windows border. > > position: 50@90; > extent: 800 @ 500; > > Can this be used for every workspace (or maybe a little offset for each > different one position: 50@90, position: 60@90, position: 70@90; and so > on) > > Cheers > > > > Thanks > > > > Mariano > > > > cheers > > > > > > > Dale > > > ----- "Miguel Enrique CobÃ¡ Martinez" <miguel.coba(a)gmail.com> > > wrote: > > > > > > | El sÃ¡b, 20-03-2010 a las 20:40 +0100, Mariano Martinez > > Peck escribiÃ³: > > > | > 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 > > > | > > > | I see that the installScript uses ConfigurationOfMetacello > > from > > > | gemsource metacello repository instead of Metacello > > repository. Given > > > | that this will be the final release of 1.0, shouldn't we > > copy > > > | ConfigurationOfMetacello to > > squeaksource/MetacelloRepository so that > > > | the > > > | package registered in monticello is this instead of the > > gemstone one. > > > | This repo for ConfigurationOfMetacello overrides the one > > of PharoCore > > > | that points to squeaksource. > > > | > > > | Dale, can you put this version in squeaksource. The > > release is very > > > | close and anyway it will be shipped in Pharo dev 1.0, so > > will reach a > > > | lot of people, even if not on squeaksource > > > | > > > | Cheers > > > | > > > > | > Mariano > > > | > > > > | > _______________________________________________ > > > | > Pharo-users mailing list > > > | > Pharo-users(a)lists.gforge.inria.fr > > > | > > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > > | > > > | -- > > > | Miguel CobÃ¡ > > > | http://miguel.leugim.com.mx > > > | > > > | > > > | _______________________________________________ > > > | 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 > > > > > > -- > > > > Miguel CobÃ¡ > > http://miguel.leugim.com.mx > > > > > > _______________________________________________ > > 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 > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

March 21, 2010

Re: [Pharo-project] isInMemory :)

by Marcus Denker

On Mar 20, 2010, at 3:46 PM, stephane ducasse wrote: > Mariano > > I was wondering (since we already removed a lot of the behavior related to inMemory) if we could not remove is in > > traitNames > "Answer a SortedCollection of all traits (not including class-traits) names." > | names | > names := OrderedCollection new. > self do: > [:cl | (cl isInMemory > and: [(cl isKindOf: Trait) > and: [(cl name beginsWith: 'AnObsolete') not]]) > ifTrue: [names add: cl name]]. > ^ names > > and friend > Yes... #isInMemory is clearly not needed anymore. I have a changeset that I will upload to the bug tracker. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

March 21, 2010

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

by Dale Henrichs

If that's the build process you use, I'm not sure why the repsitory isn't mapped correctly ... maybe it's a metacello bug then...I will do a build and see what I can find out... Dale ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | On Sun, Mar 21, 2010 at 6:36 PM, Dale Henrichs | <dale.henrichs(a)gemstone.com>wrote: | | > Mariano, | > | > I am seriously considering releasing 1.0-beta.25 today ... I have | smacked | > the heck out Metacello over the last three days without issues so | I'm | > thinking I can let this puppy out the door:)...Especially if it will | clean | > up the release process... | > | > One other point I have noticed is that the following configurations | aren't | > pointing to the correct repository: | > | > ConfigurationOfOmniBrowser | > ConfigurationOfRefactoringBrowser | > ConfigurationOfOCompletion | > ConfigurationOfShout | > ConfigurationOfProfStef | > | > They all reference the package-cache instead of SqueakSource | > MetacelloRepository. | > | | | Thanks Dale. I didn't realise about that. | | | > | > I'm assuming this is because they were in your package-cache when | you did | > the build. | > | > | No. I take a PharoCore image which is zip, without even the | package-cache | folder and then I evaluate what you can see in installScript, which is | : | | Gofer new | gemsource: 'metacello'; | package: 'ConfigurationOfMetacello'; | load. | | | ((Smalltalk at: #ConfigurationOfMetacello) project version: | '1.0-beta.25') | perform: #load. | | Gofer new | squeaksource: 'MetacelloRepository'; | package: 'ConfigurationOfPharo'; | load. | | ((Smalltalk at: #ConfigurationOfPharo) project version: | '1.0-rc3.10515') | perform: #silently: with: true; perform: #load. | | | > I think this is happening because of a recent change in the sorting | order | > for Gofer ... | > | > | I have no idea. | | | > For the build process you may want to either make sure your | package-cache | > is empty | | | | My package-cache was empty. I even didn't have that folder- | | | > or use disablePackageCache in the places where you explicitly load | a | > Configuration or perhaps something else? | > | > | How can I do that ? where should I put disablePackageCache ? do you | have a | example? | | Thanks! | | Mariano | | | | > Dale | > | | | > ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | > | > | > | > | > I see that the installScript uses ConfigurationOfMetacello from | > | > gemsource metacello repository instead of Metacello repository. | > | Given | > | > that this will be the final release of 1.0, shouldn't we copy | > | > ConfigurationOfMetacello to squeaksource/MetacelloRepository so | that | > | the | > | > package registered in monticello is this instead of the | gemstone | > | one. | > | > This repo for ConfigurationOfMetacello overrides the one of | > | PharoCore | > | > that points to squeaksource. | > | > | > | > Dale, can you put this version in squeaksource. The release is | very | > | > close and anyway it will be shipped in Pharo dev 1.0, so will | reach | > | a | > | > lot of people, even if not on squeaksource | > | > | > | > | > | Yes. This is because I added the ImageForDevelopers in the group. | With | > | that, | > | when running headless I have the problem with the progress Bar. | > | Then, i needed to use the silntly method, which is in Metacello | > | beta.25 | > | which is not released yet. That's why I have to put the other | one. | > | | > | Don't worry that beta.25 will be then correctly uploaded and | released. | > | After | > | that, the installScript will be even simpler as I won't need to | > | install | > | Metacello manually, but with the ensureMetacello ;) | > | | > | Cheers | > | | > | Mariano | > | | > | | > | | > | > Cheers | > | > > | > | > > Mariano | > | > > | > | > > _______________________________________________ | > | > > Pharo-users mailing list | > | > > Pharo-users(a)lists.gforge.inria.fr | > | > > | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users | > | > | > | > -- | > | > Miguel CobÃ¡ | > | > http://miguel.leugim.com.mx | > | > | > | > | > | | > | _______________________________________________ | > | 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 21, 2010

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

by Mariano Martinez Peck

On Sun, Mar 21, 2010 at 6:36 PM, Dale Henrichs <dale.henrichs(a)gemstone.com>wrote: > Mariano, > > I am seriously considering releasing 1.0-beta.25 today ... I have smacked > the heck out Metacello over the last three days without issues so I'm > thinking I can let this puppy out the door:)...Especially if it will clean > up the release process... > > One other point I have noticed is that the following configurations aren't > pointing to the correct repository: > > ConfigurationOfOmniBrowser > ConfigurationOfRefactoringBrowser > ConfigurationOfOCompletion > ConfigurationOfShout > ConfigurationOfProfStef > > They all reference the package-cache instead of SqueakSource > MetacelloRepository. > Thanks Dale. I didn't realise about that. > > I'm assuming this is because they were in your package-cache when you did > the build. > > No. I take a PharoCore image which is zip, without even the package-cache folder and then I evaluate what you can see in installScript, which is : Gofer new gemsource: 'metacello'; package: 'ConfigurationOfMetacello'; load. ((Smalltalk at: #ConfigurationOfMetacello) project version: '1.0-beta.25') perform: #load. Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project version: '1.0-rc3.10515') perform: #silently: with: true; perform: #load. > I think this is happening because of a recent change in the sorting order > for Gofer ... > > I have no idea. > For the build process you may want to either make sure your package-cache > is empty My package-cache was empty. I even didn't have that folder- > or use disablePackageCache in the places where you explicitly load a > Configuration or perhaps something else? > > How can I do that ? where should I put disablePackageCache ? do you have a example? Thanks! Mariano > Dale > > ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: > > | > > | > I see that the installScript uses ConfigurationOfMetacello from > | > gemsource metacello repository instead of Metacello repository. > | Given > | > that this will be the final release of 1.0, shouldn't we copy > | > ConfigurationOfMetacello to squeaksource/MetacelloRepository so that > | the > | > package registered in monticello is this instead of the gemstone > | one. > | > This repo for ConfigurationOfMetacello overrides the one of > | PharoCore > | > that points to squeaksource. > | > > | > Dale, can you put this version in squeaksource. The release is very > | > close and anyway it will be shipped in Pharo dev 1.0, so will reach > | a > | > lot of people, even if not on squeaksource > | > > | > > | Yes. This is because I added the ImageForDevelopers in the group. With > | that, > | when running headless I have the problem with the progress Bar. > | Then, i needed to use the silntly method, which is in Metacello > | beta.25 > | which is not released yet. That's why I have to put the other one. > | > | Don't worry that beta.25 will be then correctly uploaded and released. > | After > | that, the installScript will be even simpler as I won't need to > | install > | Metacello manually, but with the ensureMetacello ;) > | > | Cheers > | > | Mariano > | > | > | > | > Cheers > | > > > | > > Mariano > | > > > | > > _______________________________________________ > | > > Pharo-users mailing list > | > > Pharo-users(a)lists.gforge.inria.fr > | > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > | > > | > -- > | > Miguel CobÃ¡ > | > http://miguel.leugim.com.mx > | > > | > > | > | _______________________________________________ > | 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 21, 2010

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

by Miguel Enrique CobÃ¡ Martinez

El dom, 21-03-2010 a las 18:26 +0100, Mariano Martinez Peck escribiÃ³: > > > Mee too. The image windows open in like 800x600 and the > workspace is > partially off-screen. > > > If you see in the definition of the workspace, there are the sized. > Can you give me a size that correctly match your needs? For the size the image opens in my machine, this values let see the Pharo logo and the workspace image is fully enclosed in the image windows border. position: 50@90; extent: 800 @ 500; Can this be used for every workspace (or maybe a little offset for each different one position: 50@90, position: 60@90, position: 70@90; and so on) Cheers > > Thanks > > Mariano > > cheers > > > > Dale > > ----- "Miguel Enrique CobÃ¡ Martinez" <miguel.coba(a)gmail.com> > wrote: > > > > | El sÃ¡b, 20-03-2010 a las 20:40 +0100, Mariano Martinez > Peck escribiÃ³: > > | > 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 > > | > > | I see that the installScript uses ConfigurationOfMetacello > from > > | gemsource metacello repository instead of Metacello > repository. Given > > | that this will be the final release of 1.0, shouldn't we > copy > > | ConfigurationOfMetacello to > squeaksource/MetacelloRepository so that > > | the > > | package registered in monticello is this instead of the > gemstone one. > > | This repo for ConfigurationOfMetacello overrides the one > of PharoCore > > | that points to squeaksource. > > | > > | Dale, can you put this version in squeaksource. The > release is very > > | close and anyway it will be shipped in Pharo dev 1.0, so > will reach a > > | lot of people, even if not on squeaksource > > | > > | Cheers > > | > > > | > Mariano > > | > > > | > _______________________________________________ > > | > Pharo-users mailing list > > | > Pharo-users(a)lists.gforge.inria.fr > > | > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > | > > | -- > > | Miguel CobÃ¡ > > | http://miguel.leugim.com.mx > > | > > | > > | _______________________________________________ > > | 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 > > > -- > > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > 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 -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 21, 2010

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

by Miguel Enrique CobÃ¡ Martinez

El dom, 21-03-2010 a las 18:34 +0100, Mariano Martinez Peck escribiÃ³: > > > 2010/3/21 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com> > El sÃ¡b, 20-03-2010 a las 20:40 +0100, Mariano Martinez Peck > escribiÃ³: > > > Hi folks. We are proud to announce the (hopefully) last RC3 > for Pharo > > 1.0. > > > - What happened to the background image? > > > I said several times I don't have a screen to test. And I ask several > times for help. I won't do everything. I don't know how to do it > neither how to test it. > So, or someone do it and test it, or it won't be again. > > I only remember this link, but there were more opportunities: > > http://n4.nabble.com/Latest-Polymorph-td1468728.html#a1468728 Well, then for 1.1. No problem then. > > > - The text on: DEVImageWorkspaces openExternalProjectWorkspace > at the > end says: > > "If you want an object database, you can install Magma > (http://wiki.squeak.org/squeak/2665) > For the installation instuctions check the method: > ConfigurationOfMagma > >> workspace " > > Can we change this to: > > "Magma is an object oriented database for Smalltalk. It > supports > replication, high-availability fault-tolerance and multiuser > capabilities (http://wiki.squeak.org/squeak/2665) You can > install it > with: > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfMagma'; > load. > > ((Smalltalk at: #ConfigurationOfMagma) project latestVersion) > load > > "You can also review the method > ConfigurationOfMagma>>workspace for > alternative installation methods for Magma. > > Sure, no problem. I will do. > > > > - Also, in the same workspace: > Gofer new > squeaksource: 'Moose'; > package: 'ConfigurationOfMoose'; > load. > > (Smalltalk at: #ConfigurationOfMoose) perform: > #loadDefault. > > Should be: > Gofer new > squeaksource: 'Moose'; > package: 'ConfigurationOfMoose'; > load. > > (Smalltalk at: #ConfigurationOfMoose) loadDefault > > As the other examples use the methods directly and not the > perform > indirection. > > > Yes, true. But the problem is that as loadDefualt doesn't exist in the > image, with the Shout Workpsace you see that word in red...is not > nice. > > What do you think ? ah, ok, no problem then :) > > Thanks for the feedback. > > Mariano > > > Cheers > > > > > > > _______________________________________________ > > Pharo-users mailing list > > Pharo-users(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > -- Miguel CobÃ¡ http://miguel.leugim.com.mx

March 21, 2010

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

by Dale Henrichs

Mariano, I am seriously considering releasing 1.0-beta.25 today ... I have smacked the heck out Metacello over the last three days without issues so I'm thinking I can let this puppy out the door:)...Especially if it will clean up the release process... One other point I have noticed is that the following configurations aren't pointing to the correct repository: ConfigurationOfOmniBrowser ConfigurationOfRefactoringBrowser ConfigurationOfOCompletion ConfigurationOfShout ConfigurationOfProfStef They all reference the package-cache instead of SqueakSource MetacelloRepository. I'm assuming this is because they were in your package-cache when you did the build. I think this is happening because of a recent change in the sorting order for Gofer ... For the build process you may want to either make sure your package-cache is empty or use disablePackageCache in the places where you explicitly load a Configuration or perhaps something else? Dale ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | > | > I see that the installScript uses ConfigurationOfMetacello from | > gemsource metacello repository instead of Metacello repository. | Given | > that this will be the final release of 1.0, shouldn't we copy | > ConfigurationOfMetacello to squeaksource/MetacelloRepository so that | the | > package registered in monticello is this instead of the gemstone | one. | > This repo for ConfigurationOfMetacello overrides the one of | PharoCore | > that points to squeaksource. | > | > Dale, can you put this version in squeaksource. The release is very | > close and anyway it will be shipped in Pharo dev 1.0, so will reach | a | > lot of people, even if not on squeaksource | > | > | Yes. This is because I added the ImageForDevelopers in the group. With | that, | when running headless I have the problem with the progress Bar. | Then, i needed to use the silntly method, which is in Metacello | beta.25 | which is not released yet. That's why I have to put the other one. | | Don't worry that beta.25 will be then correctly uploaded and released. | After | that, the installScript will be even simpler as I won't need to | install | Metacello manually, but with the ensureMetacello ;) | | Cheers | | Mariano | | | | > Cheers | > > | > > Mariano | > > | > > _______________________________________________ | > > Pharo-users mailing list | > > Pharo-users(a)lists.gforge.inria.fr | > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users | > | > -- | > Miguel CobÃ¡ | > http://miguel.leugim.com.mx | > | > | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

March 21, 2010