Re: [Pharo-project] MIT strikes back (was Re: [smalltalk-research] Re: [Esug-list] Google Summer Of Code 2010 news!!!)
Bryce Kampjes a écrit : On Thu, 2010-03-11 at 16:31 -0600, Chris Muller wrote: Well, I certainly care.. Stef wasn't remarking about license rights, he said didn't understand the smiley face. Frankly, I don't either. After years of teasing from Bryce and now this? What a crushing disappointment. I'm still here And still making progress though slowly. Can't you get support to progress more easily? Should not be difficult regarding the importance of your work? Hilaire ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] keyboard shortcut for 'save image'
Sergio there is a emacs guys in me too. This is why I would love that somebody - look at the key binding - look at the key binding implementation - look at the old package supporting per editor key binding and puths that to us Any taker? Stef On Mar 24, 2010, at 6:02 AM, sergio_101 wrote: wondering if there was a keyboard shortcut for 'save image' that i could just periodically hit while i am going.. maybe it's the emacs in me that makes me less mouse grabby.. thanks! -- peace, sergio photographer, journalist, visionary http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101 ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] [update 1.1] #11293 Polymorph Enhancements
11293 - Polymorph Enhancements - Further remembered keyboard focus fixes. PluggableButtonMorph refactorings. Added MultistateLabelMorph that can adapt to interaction sates from buttons. - Fixes for invalid (mis-spelled) sizing options (hResizing/vResizing). Layout tweaks for theme built widgets due to TableLayout fixes. Passivation ofactive window (topWIndow) upon click of World (c.f. remembered focus fixes). Added #backgroundImage:layout: to PasteUpMorph as convenience for setting scaleable background image. -Refactored automatic background image support in themes. Corner style of source view drop down in Browser matches theme button corner style. -Fixes for @- -Added SimpleHierarchicalListMorphgetListSelector. Thanks gary! ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements
Gary can you check because the button look ugly now inline: Screen shot 2010-03-24 at 12.24.55 PM.png Stef On Mar 24, 2010, at 12:20 PM, Stéphane Ducasse wrote: 11293 - Polymorph Enhancements - Further remembered keyboard focus fixes. PluggableButtonMorph refactorings. Added MultistateLabelMorph that can adapt to interaction sates from buttons. - Fixes for invalid (mis-spelled) sizing options (hResizing/vResizing). Layout tweaks for theme built widgets due to TableLayout fixes. Passivation ofactive window (topWIndow) upon click of World (c.f. remembered focus fixes). Added #backgroundImage:layout: to PasteUpMorph as convenience for setting scaleable background image. -Refactored automatic background image support in themes. Corner style of source view drop down in Browser matches theme button corner style. -Fixes for @- -Added SimpleHierarchicalListMorphgetListSelector. Thanks gary! ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements
argh I cannot use buttons anymore like pressing on open in MC. So I will rollback the changes! Houston we have a problem Stef On Mar 24, 2010, at 12:20 PM, Stéphane Ducasse wrote: 11293 - Polymorph Enhancements - Further remembered keyboard focus fixes. PluggableButtonMorph refactorings. Added MultistateLabelMorph that can adapt to interaction sates from buttons. - Fixes for invalid (mis-spelled) sizing options (hResizing/vResizing). Layout tweaks for theme built widgets due to TableLayout fixes. Passivation ofactive window (topWIndow) upon click of World (c.f. remembered focus fixes). Added #backgroundImage:layout: to PasteUpMorph as convenience for setting scaleable background image. -Refactored automatic background image support in themes. Corner style of source view drop down in Browser matches theme button corner style. -Fixes for @- -Added SimpleHierarchicalListMorphgetListSelector. Thanks gary! ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] soft squeak selection of non active window istoo pale
Seems that with Alain's refactoring the base window colours have been changed (Browser was lightGreen and is now paleGreen, for instance). See implementors of #patchworkUIThemeColor. So browsers are paler across the board. As for the menu selection colour, the attached should help (included the world resize change too since MC seems to be intent on not ever merging it...). You'll need to do: UIThemeWatery defaultSettings: nil. UIThemeWatery2 defaultSettings: nil; beCurrent To reset the persistent class defaults. Regards, Gary - Original Message - From: Lukas Renggli reng...@gmail.com To: Pharo-project@lists.gforge.inria.fr Sent: Tuesday, March 23, 2010 8:29 PM Subject: Re: [Pharo-project] soft squeak selection of non active window istoo pale Maybe in the same realm: The menu selection in Pharo 1.1 is not visible enough, the selection is a gray bar on gray background. I find the strong blue selection in Pharo 1.0 much easier to see.re Lukas On 23 March 2010 21:19, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi guys It would be great if one of you could fix that: the soft squeak selection color of non active window is too pale so we cannot see in another window which class is selected. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project MenuSelectionColor.1.cs Description: Binary data ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] soft squeak selection of non active window istoo pale
thanks gary. On Mar 24, 2010, at 12:30 PM, Gary Chambers wrote: Seems that with Alain's refactoring the base window colours have been changed (Browser was lightGreen and is now paleGreen, for instance). See implementors of #patchworkUIThemeColor. So browsers are paler across the board. As for the menu selection colour, the attached should help (included the world resize change too since MC seems to be intent on not ever merging it...). You'll need to do: UIThemeWatery defaultSettings: nil. UIThemeWatery2 defaultSettings: nil; beCurrent To reset the persistent class defaults. Regards, Gary - Original Message - From: Lukas Renggli reng...@gmail.com To: Pharo-project@lists.gforge.inria.fr Sent: Tuesday, March 23, 2010 8:29 PM Subject: Re: [Pharo-project] soft squeak selection of non active window istoo pale Maybe in the same realm: The menu selection in Pharo 1.1 is not visible enough, the selection is a gray bar on gray background. I find the strong blue selection in Pharo 1.0 much easier to see.re Lukas On 23 March 2010 21:19, Stéphane Ducasse stephane.duca...@inria.fr wrote: Hi guys It would be great if one of you could fix that: the soft squeak selection color of non active window is too pale so we cannot see in another window which class is selected. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project MenuSelectionColor.1.cs___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements
A slightly trickier merge this time... Best to keep current for the FuzzyLabelMorph change (somehow that has reverted) to fix the ugly buttons. And, perhaps, the trivial differences with respect to @- fixes. The rest should be ok. Merges alright here. Regards, Gary - Original Message - From: Stéphane Ducasse stephane.duca...@inria.fr To: Pharo-project@lists.gforge.inria.fr Sent: Wednesday, March 24, 2010 11:26 AM Subject: Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements argh I cannot use buttons anymore like pressing on open in MC. So I will rollback the changes! Houston we have a problem Stef On Mar 24, 2010, at 12:20 PM, Stéphane Ducasse wrote: 11293 - Polymorph Enhancements - Further remembered keyboard focus fixes. PluggableButtonMorph refactorings. Added MultistateLabelMorph that can adapt to interaction sates from buttons. - Fixes for invalid (mis-spelled) sizing options (hResizing/vResizing). Layout tweaks for theme built widgets due to TableLayout fixes. Passivation ofactive window (topWIndow) upon click of World (c.f. remembered focus fixes). Added #backgroundImage:layout: to PasteUpMorph as convenience for setting scaleable background image. -Refactored automatic background image support in themes. Corner style of source view drop down in Browser matches theme button corner style. -Fixes for @- -Added SimpleHierarchicalListMorphgetListSelector. Thanks gary! ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements
On Mar 24, 2010, at 12:54 14PM, Gary Chambers wrote: A slightly trickier merge this time... Best to keep current for the FuzzyLabelMorph change (somehow that has reverted) to fix the ugly buttons. Or if you liked it better, you can revert to the original version of FuzzyLabelMorphdrawOn:, and set fuzzColor to Color transparent alpha: 0.001 instead of Color transparent. There seems to be a bug in the primitive when alpha is exactly 0, which is what causes the weird look, but a color just a tiny fraction off, works. Cheers, Henry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements
Indeed, though the current Pharo version has a performance benefit for disabled buttons... Regards, Gary - Original Message - From: Henrik Johansen henrik.s.johan...@veloxit.no To: Pharo-project@lists.gforge.inria.fr Sent: Wednesday, March 24, 2010 12:07 PM Subject: Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements On Mar 24, 2010, at 12:54 14PM, Gary Chambers wrote: A slightly trickier merge this time... Best to keep current for the FuzzyLabelMorph change (somehow that has reverted) to fix the ugly buttons. Or if you liked it better, you can revert to the original version of FuzzyLabelMorphdrawOn:, and set fuzzColor to Color transparent alpha: 0.001 instead of Color transparent. There seems to be a bug in the primitive when alpha is exactly 0, which is what causes the weird look, but a color just a tiny fraction off, works. Cheers, Henry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements
Thanks guys I will give it a try now. \I'm sick so my brain works slowly On Mar 24, 2010, at 1:07 PM, Henrik Johansen wrote: On Mar 24, 2010, at 12:54 14PM, Gary Chambers wrote: A slightly trickier merge this time... Best to keep current for the FuzzyLabelMorph change (somehow that has reverted) to fix the ugly buttons. Or if you liked it better, you can revert to the original version of FuzzyLabelMorphdrawOn:, and set fuzzColor to Color transparent alpha: 0.001 instead of Color transparent. There seems to be a bug in the primitive when alpha is exactly 0, which is what causes the weird look, but a color just a tiny fraction off, works. Cheers, Henry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements
Join the club! Regards, Gary - Original Message - From: Stéphane Ducasse stephane.duca...@inria.fr To: Pharo-project@lists.gforge.inria.fr Sent: Wednesday, March 24, 2010 12:22 PM Subject: Re: [Pharo-project] [update 1.1] #11293 Polymorph Enhancements Thanks guys I will give it a try now. \I'm sick so my brain works slowly On Mar 24, 2010, at 1:07 PM, Henrik Johansen wrote: On Mar 24, 2010, at 12:54 14PM, Gary Chambers wrote: A slightly trickier merge this time... Best to keep current for the FuzzyLabelMorph change (somehow that has reverted) to fix the ugly buttons. Or if you liked it better, you can revert to the original version of FuzzyLabelMorphdrawOn:, and set fuzzColor to Color transparent alpha: 0.001 instead of Color transparent. There seems to be a bug in the primitive when alpha is exactly 0, which is what causes the weird look, but a color just a tiny fraction off, works. Cheers, Henry ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
On Sun, Mar 21, 2010 at 11:54 AM, Adrian Lienhard 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.1.zip Cheers Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
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 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.1.zip Cheers Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
On Wed, Mar 24, 2010 at 1:53 PM, Adrian Lienhard 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 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.1.zip Cheers Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
On Mar 24, 2010, at 13:56 , Mariano Martinez Peck wrote: On Wed, Mar 24, 2010 at 1:53 PM, Adrian Lienhard 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 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.1.zip Cheers Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
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 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.1.zip Cheers Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
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 alexan...@bergel.euwrote: 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 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.1.zip Cheers Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
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 alexan...@bergel.euwrote: 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 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.1.zip Cheers Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.0-10515-rc3dev10.03.1
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 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.1.zip Cheers Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Simon ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Montacello configuration writing
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 ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] ConfigurationOfDrGeo for Pharo
Hello, I have updated DrGeo to make it compliant to Pharo 1.0 (hello Laurent). I took the opportunity to write a ConfigurationOfDrGeo using Metacello package management facility. The Configuration is for now in the DrGeo repository: http://squeaksource.com/DrGeoII/ in case someone want to test it. Hilaire ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] ConfigurationOfDrGeo for Pharo
Hi Hilaire, I've downloaded DrGeo using this script (maybe you could advertise it the squeaksource page), Gofer new url: 'http://www.squeaksource.com/DrGeoII' ; package: 'ConfigurationOfDrGeo'; load. ((Smalltalk at: #ConfigurationOfDrGeo ) perform:#load. But how do i start the app? Thanks, Fernando On Mar 24, 2010, at 3:29 PM, Hilaire Fernandes wrote: Hello, I have updated DrGeo to make it compliant to Pharo 1.0 (hello Laurent). I took the opportunity to write a ConfigurationOfDrGeo using Metacello package management facility. The Configuration is for now in the DrGeo repository: http://squeaksource.com/DrGeoII/ in case someone want to test it. Hilaire ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] ConfigurationOfDrGeo for Pharo
I managed to open it, DrGeo new. but got a DNU. FlapTabshowFlap PasteUpMorphadapToWorld: EventHandler-does not understand #adaptToWorld On Mar 24, 2010, at 3:55 PM, Fernando olivero wrote: Hi Hilaire, I've downloaded DrGeo using this script (maybe you could advertise it the squeaksource page), Gofer new url: 'http://www.squeaksource.com/DrGeoII' ; package: 'ConfigurationOfDrGeo'; load. ((Smalltalk at: #ConfigurationOfDrGeo ) perform:#load. But how do i start the app? Thanks, Fernando On Mar 24, 2010, at 3:29 PM, Hilaire Fernandes wrote: Hello, I have updated DrGeo to make it compliant to Pharo 1.0 (hello Laurent). I took the opportunity to write a ConfigurationOfDrGeo using Metacello package management facility. The Configuration is for now in the DrGeo repository: http://squeaksource.com/DrGeoII/ in case someone want to test it. Hilaire ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ATT1..txt ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] ConfigurationOfDrGeo for Pharo
Right, I should document and fix that: DrGeo sample openInWorld Hilaire Fernando olivero a écrit : Hi Hilaire, I've downloaded DrGeo using this script (maybe you could advertise it the squeaksource page), Gofer new url: 'http://www.squeaksource.com/DrGeoII' ; package: 'ConfigurationOfDrGeo'; load. ((Smalltalk at: #*ConfigurationOfDrGeo* ) perform:#load. But how do i start the app? Thanks, Fernando On Mar 24, 2010, at 3:29 PM, Hilaire Fernandes wrote: Hello, I have updated DrGeo to make it compliant to Pharo 1.0 (hello Laurent). I took the opportunity to write a ConfigurationOfDrGeo using Metacello package management facility. The Configuration is for now in the DrGeo repository: http://squeaksource.com/DrGeoII/ in case someone want to test it. Hilaire ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] ConfigurationOfDrGeo for Pharo
Hello, Working great for me on rc3. On Wed, Mar 24, 2010 at 4:22 PM, Hilaire Fernandes hilaire.fernan...@gmail.com wrote: Right, I should document and fix that: DrGeo sample openInWorld Hilaire Fernando olivero a écrit : Hi Hilaire, I've downloaded DrGeo using this script (maybe you could advertise it the squeaksource page), Gofer new url: 'http://www.squeaksource.com/DrGeoII' ; package: 'ConfigurationOfDrGeo'; load. ((Smalltalk at: #*ConfigurationOfDrGeo* ) perform:#load. But how do i start the app? Thanks, Fernando On Mar 24, 2010, at 3:29 PM, Hilaire Fernandes wrote: Hello, I have updated DrGeo to make it compliant to Pharo 1.0 (hello Laurent). I took the opportunity to write a ConfigurationOfDrGeo using Metacello package management facility. The Configuration is for now in the DrGeo repository: http://squeaksource.com/DrGeoII/ in case someone want to test it. Hilaire ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Patrick Barroca ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Useless Netwoking classes?
Hi, I'm looking at the Network-Kernel category, and found two classes that seem unused: -ConnectionQueue -InternetConfiguration I checked in the latest PharoCore, and Pharo-Dev. Also, I checked in Pier 1.2. No reference/subclass. If you agree to remove them, how should I provide/package the following code snipet that does the change ? ConnectionQueue removeFromSystem. InternetConfiguration removeFromSystem. Noury http://car.ensm-douai.fr/noury/ -- -5th National Conference on Control Architecture of Robots (CAR). Douai, France, 18-19 may 2010 http://car.ensm-douai.fr/CAR2010/ -ESUG 18th International Smalltalk Conference. Barcelona, Spain, 11-17 september 2010 http://www.esug.org/Conferences/2010 ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Useless Netwoking classes?
Yes and open an bug entry. Stef On Mar 24, 2010, at 4:45 PM, Bouraqadi Noury wrote: Hi, I'm looking at the Network-Kernel category, and found two classes that seem unused: -ConnectionQueue -InternetConfiguration I checked in the latest PharoCore, and Pharo-Dev. Also, I checked in Pier 1.2. No reference/subclass. If you agree to remove them, how should I provide/package the following code snipet that does the change ? ConnectionQueue removeFromSystem. InternetConfiguration removeFromSystem. Noury http://car.ensm-douai.fr/noury/ -- -5th National Conference on Control Architecture of Robots (CAR). Douai, France, 18-19 may 2010 http://car.ensm-douai.fr/CAR2010/ -ESUG 18th International Smalltalk Conference. Barcelona, Spain, 11-17 september 2010 http://www.esug.org/Conferences/2010 ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] ConfigurationOfDrGeo for Pharo
this is cool hilaire! Stef On Mar 24, 2010, at 3:29 PM, Hilaire Fernandes wrote: Hello, I have updated DrGeo to make it compliant to Pharo 1.0 (hello Laurent). I took the opportunity to write a ConfigurationOfDrGeo using Metacello package management facility. The Configuration is for now in the DrGeo repository: http://squeaksource.com/DrGeoII/ in case someone want to test it. Hilaire ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Useless Netwoking classes?
On Mar 24, 2010, at 4:45 PM, Bouraqadi Noury wrote: InternetConfiguration this one is in the startup list, on Macos. The idea is that it sets to proxy automatically considering that this is needed as SCG, just imagine how much good this class did for Squeak and Smalltalk (and Research! Humanity!) over the last 4 years... When I added it, people mentioned that it's not perfect and thus it should not be added to 3.9, but, as one can imagine, nothing better has been ever proposed. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Useless Netwoking classes?
keep it :) On Mar 24, 2010, at 4:51 PM, Marcus Denker wrote: On Mar 24, 2010, at 4:45 PM, Bouraqadi Noury wrote: InternetConfiguration this one is in the startup list, on Macos. The idea is that it sets to proxy automatically considering that this is needed as SCG, just imagine how much good this class did for Squeak and Smalltalk (and Research! Humanity!) over the last 4 years... When I added it, people mentioned that it's not perfect and thus it should not be added to 3.9, but, as one can imagine, nothing better has been ever proposed. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] funny behavior with MC
this is strange before lunch I could select Polymorph-Widgets and merge at will and now I cannot anymore because I got a message could not find versions for example 107 Now this is really strange because this is the first version that was merged so normally it should be found. It is either in the UIEnhancements repository or the one of pharo. inline: Screen shot 2010-03-24 at 4.54.31 PM.png Does anybody encountered this behavior? Right now I'm blocked. MC looks so mysterious we will have to fix it in the future. Stef___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] [update 1.1] #11294
11294 - - Further remembered keyboard focus fixes. PluggableButtonMorph refactorings. Added MultistateLabelMorph that can adapt to interaction sates from buttons. - Fixes for invalid (mis-spelled) sizing options (hResizing/vResizing). Layout tweaks for theme built widgets due to TableLayout fixes. Passivation ofactive window (topWIndow) upon click of World (c.f. remembered focus fixes). Added #backgroundImage:layout: to PasteUpMorph as convenience for setting scaleable background image. -Refactored automatic background image support in themes. Corner style of source view drop down in Browser matches theme button corner style. -Fixes for @- -Added SimpleHierarchicalListMorphgetListSelector. - RevertedFuzzyLabelMorph drawOn: and added alpha:0.001 Thanks guys Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] ConfigurationOfDrGeo for Pharo
DrGeo is a really cool system. It is great to see it in action in Pharo. Are there any plan to integrate it into a window with menu and/or toolbar? First I had some troubles to find out how it works :-) Lukas On 24 March 2010 16:49, Stéphane Ducasse stephane.duca...@inria.fr wrote: this is cool hilaire! Stef On Mar 24, 2010, at 3:29 PM, Hilaire Fernandes wrote: Hello, I have updated DrGeo to make it compliant to Pharo 1.0 (hello Laurent). I took the opportunity to write a ConfigurationOfDrGeo using Metacello package management facility. The Configuration is for now in the DrGeo repository: http://squeaksource.com/DrGeoII/ in case someone want to test it. Hilaire ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] About MC
during the integration I was thinking that we kept the complete ancestry. I thought that since we merge all the times, the ancestry is kept. My idea is that after just taking Pharo would be enough to merge. Now this is not the case: if I look at Polymorph-Widgets for example I have holes and this is probably due to a load versus a merge. Lukas may be you know more than me on the topic. What do you think? Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
this is strange before lunch I could select Polymorph-Widgets and merge at will and now I cannot anymore because I got a message could not find versions for example 107 This problem is to be expected when you move or delete versions. You see this message when the closest ancestor of the version you have in your image and the one you merge cannot be found. It could help to add the TreatedInbox to the list of repositories. If you can't find the common ancestor you cannot automatically merge. Lukas -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] ConfigurationOfDrGeo for Pharo
Absolutely, if nothing else is in my path, it is the next thing I want to do: using polymorph to provide a feature complete UI for DrGeo, I have been waiting for that since a long time. Hilaire Lukas Renggli a écrit : DrGeo is a really cool system. It is great to see it in action in Pharo. Are there any plan to integrate it into a window with menu and/or toolbar? First I had some troubles to find out how it works :-) ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
what is strange is that when I merge the latest loaded version I got the normal no changes and I could merge without having to add a new repository. I think that in squeak they cut the problem (if you do not have the history what do you do). You should still be able to merge. Setf On Mar 24, 2010, at 6:02 PM, Lukas Renggli wrote: this is strange before lunch I could select Polymorph-Widgets and merge at will and now I cannot anymore because I got a message could not find versions for example 107 This problem is to be expected when you move or delete versions. You see this message when the closest ancestor of the version you have in your image and the one you merge cannot be found. It could help to add the TreatedInbox to the list of repositories. If you can't find the common ancestor you cannot automatically merge. Lukas -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
what is strange is that when I merge the latest loaded version I got the normal no changes and I could merge without having to add a new repository. Sure, because in this situation the common ancestor is the version you load (so it can always be found). And the delta between the working copy and the version you merge is empty, so you have no changes. I think that in squeak they cut the problem (if you do not have the history what do you do). You should still be able to merge. I don't think they do anything different? If the ancestor version is missing you simply cannot do a meaningful merge. It is as simple as that. Lukas -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] About MC
during the integration I was thinking that we kept the complete ancestry. I thought that since we merge all the times, the ancestry is kept. My idea is that after just taking Pharo would be enough to merge. Can you elaborate? I don't understand the last sentence. I was thinking that the Pharo repository alone would be enough to make sure that we can always merge. Now this is not the case: if I look at Polymorph-Widgets for example I have holes and this is probably due to a load versus a merge. There is not much of a difference between the two: - When loading the working copy has the loaded version as an single ancestor. - When merging the working copy has the previously loaded version and the merged version as an ancestor. In either case there is never a hole. Each version stores the complete ancestry tree it knows, that is the filename and uuid of each version. The problem you run into is that you delete and move version files. If Monticello cannot find the files that it refers to in its ancestry you cannot merge automatically. That's why repositories should strictly be read-only. I do not really understand how we ended up with holes then. Stef Lukas -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
On Mar 24, 2010, at 6:46 PM, Lukas Renggli wrote: what is strange is that when I merge the latest loaded version I got the normal no changes and I could merge without having to add a new repository. Sure, because in this situation the common ancestor is the version you load (so it can always be found). And the delta between the working copy and the version you merge is empty, so you have no changes. You did not get me right scenario 1: I click on the slice press merge get an error ancestor not found scenario 2: I click on the **latest working copy version* that led to the error of scenario and do merge I get no changes of course + scenario 1 and it merges without the error of scenario 1 (it means that he suddenly magically found the ancestry) for me there is a bug. Because between scenario 1 and 2 there is no difference since this is exactly the same version that I have as working copy. I think that in squeak they cut the problem (if you do not have the history what do you do). You should still be able to merge. I don't think they do anything different? If the ancestor version is missing you simply cannot do a meaningful merge. It is as simple as that. Yes i see what you mean. You cannot use the ancestry to do a clever merge. What I meant is that we should be able to see what changed based on the latest loaded version (no need to have the complete ancestor since it is broken). Because often using the latest working copy and having the diff is only what I need. Is whatI'm sayign make sense? ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] About MC
In either case there is never a hole. Each version stores the complete ancestry tree it knows, that is the filename and uuid of each version. The problem you run into is that you delete and move version files. If Monticello cannot find the files that it refers to in its ancestry you cannot merge automatically. That's why repositories should strictly be read-only. I do not really understand how we ended up with holes then. I guess I will have to explain it on a white-board, but here's another try: The problem is that Monticello cannot find the common ancestor because you deleted it from its repository. To fix the problem you have to find this version and tell Monticello where it can load it from by adding that repository. It is likely that you find the version somewhere on SqueakSource or in some package-cache on your machine. If you can't find the version you have to merge manually. This means you browse the other version or you calculate the changes between your version and the version you want to merge and apply the changes that you think should go in manually one-by-one. Then you 'adopt' that version to the ancestry. Lukas -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
what is strange is that when I merge the latest loaded version I got the normal no changes and I could merge without having to add a new repository. Sure, because in this situation the common ancestor is the version you load (so it can always be found). And the delta between the working copy and the version you merge is empty, so you have no changes. You did not get me right scenario 1: I click on the slice press merge get an error ancestor not found scenario 2: I click on the **latest working copy version* that led to the error of scenario and do merge I get no changes of course I do not understand. - What is the latest working copy version? The working copy is the code you currently have in your image. - What do slices have to do with this? They shouldn't, because in the end the dependent versions are merged individually. + scenario 1 and it merges without the error of scenario 1 (it means that he suddenly magically found the ancestry) The ancestry cannot be lost. The .mcz files are the one thing that can disappear. for me there is a bug. Because between scenario 1 and 2 there is no difference since this is exactly the same version that I have as working copy. The working copy is just one of the variable things in the merge. There is also the other version you load (and that might be different in your scenarios), and the common ancestor between the two (again that might be different in your scenarios). Yes i see what you mean. You cannot use the ancestry to do a clever merge. What I meant is that we should be able to see what changed based on the latest loaded version (no need to have the complete ancestor since it is broken). The ancestry is not broken! The problem is that you miss *ancestor versions*, because they were deleted or moved. Because often using the latest working copy and having the diff is only what I need. Is whatI'm sayign make sense? To get a diff between your working copy and a version you select this version and click on changes. That doesn't require any other version but the selected one. It doesn't even use the ancestry information. No, I can't make sense of it :-) Lukas -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
Stef and Lukas, The other situation that I have seen these types of errors is when the package that I am merging into(?) does not have the repository where the common ancestor mcz file is located. For example if I have Seaside.gemstone-dkh.500 with http://seaside.gemstone.com/ss/seaside in it's repository group. When I attempt to merge Seaside.lr.505 in http://www.squeaksource.com/seaside I get an error. If I add http://www.squeaksource.com/seaside to the repository group for Seaside.gemstone-dkh.500 and then try the merge, it works.. Does this help or have I missed something along the way:) Dale - Stéphane Ducasse stephane.duca...@inria.fr wrote: | On Mar 24, 2010, at 6:46 PM, Lukas Renggli wrote: | | what is strange is that when I merge the latest loaded version I | got the normal no changes | and I could merge without having to add a new repository. | | Sure, because in this situation the common ancestor is the version | you | load (so it can always be found). And the delta between the working | copy and the version you merge is empty, so you have no changes. | | You did not get me right | | scenario 1: I click on the slice press merge get an error ancestor | not found | scenario 2: I click on the **latest working copy version* that led to | the error of scenario and do merge I get no changes of course |+ scenario 1 and it merges without the error of scenario 1 (it means | that he suddenly magically found the ancestry) | | for me there is a bug. Because between scenario 1 and 2 there is no | difference since this is exactly the same version that I have | as working copy. | | | I think that in squeak they cut the problem (if you do not have the | history what do you do). | You should still be able to merge. | | I don't think they do anything different? If the ancestor version | is | missing you simply cannot do a meaningful merge. It is as simple as | that. | | Yes i see what you mean. You cannot use the ancestry to do a clever | merge. What I meant is that we should be able to see what changed | based on the latest loaded version (no need to have the complete | ancestor since it is broken). | | Because often using the latest working copy and having the diff is | only what I need. Is whatI'm sayign make sense? | | | ___ | Pharo-project mailing list | Pharo-project@lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] About MC
On Mar 24, 2010, at 7:11 PM, Lukas Renggli wrote: In either case there is never a hole. Each version stores the complete ancestry tree it knows, that is the filename and uuid of each version. The problem you run into is that you delete and move version files. If Monticello cannot find the files that it refers to in its ancestry you cannot merge automatically. That's why repositories should strictly be read-only. I do not really understand how we ended up with holes then. I guess I will have to explain it on a white-board, but here's another try: The problem is that Monticello cannot find the common ancestor because you deleted it from its repository. To fix the problem you have to find this version and tell Monticello where it can load it from by adding that repository. It is likely that you find the version somewhere on SqueakSource or in some package-cache on your machine. I know that ;) If you can't find the version you have to merge manually. This means you browse the other version or you calculate the changes between your version and the version you want to merge and apply the changes that you think should go in manually one-by-one. Then you 'adopt' that version to the ancestry. Yes this is for the me the minimum I would like to have instead of an error. Also during the manual merge we do not have to give up the fact that superclass, adding new method first... should be changed first and all the logic Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Montacello configuration writing
Hilaire, Thanks for the feedback. I've opened http://code.google.com/p/metacello/issues/detail?id=69 to track this issue. This might be a shortcut worth adding, since it _is_ used very frequently. You'd still need to revert to the #package:with: form if you wanted to set multiple attributes ... does that make sense? Dale - Hilaire Fernandes hilaire.fernan...@gmail.com wrote: | 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 | | | ___ | Pharo-project mailing list | Pharo-project@lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
The ancestry cannot be lost. The .mcz files are the one thing that can disappear. Yes I know but the result is the same. The working copy is just one of the variable things in the merge. There is also the other version you load (and that might be different in your scenarios), and the common ancestor between the two (again that might be different in your scenarios). I know. Yes i see what you mean. You cannot use the ancestry to do a clever merge. What I meant is that we should be able to see what changed based on the latest loaded version (no need to have the complete ancestor since it is broken). The ancestry is not broken! The problem is that you miss *ancestor versions*, because they were deleted or moved. I know now since we systematically merge during our process I wonder how we break it. May be this is when you publish the smalltalk rewrite. Could check if you have Polymorph-Widgets-lr.214 in your local cache? I know now let me repeat the bug I see scenario1 working copy polymorphWiget.7.mcz I click on polymorphWiget.24.mcz merge - I get an error ancestor cannot be found scenario1 working copy polymorphWiget.7.mcz I click on polymorphWiget.7.mcz merge - no changes (ok this is what I hope what arriving) Then I click on polymorphWiget.24.mcz merge - I get no error. So for me there is something strange. Stef ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
This is normal because ancestry cross over repository. I think that there is something really strange. EIther you get a truly distributed system or you get a local. With MC you get a distributed which can be brittle (even if I understand well the problem ancestry is solving). I think that a pessimistic merge (more than just going one by one on the changes would help). Stef On Mar 24, 2010, at 8:12 PM, Dale Henrichs wrote: Stef and Lukas, The other situation that I have seen these types of errors is when the package that I am merging into(?) does not have the repository where the common ancestor mcz file is located. For example if I have Seaside.gemstone-dkh.500 with http://seaside.gemstone.com/ss/seaside in it's repository group. When I attempt to merge Seaside.lr.505 in http://www.squeaksource.com/seaside I get an error. If I add http://www.squeaksource.com/seaside to the repository group for Seaside.gemstone-dkh.500 and then try the merge, it works.. Does this help or have I missed something along the way:) Dale - Stéphane Ducasse stephane.duca...@inria.fr wrote: | On Mar 24, 2010, at 6:46 PM, Lukas Renggli wrote: | | what is strange is that when I merge the latest loaded version I | got the normal no changes | and I could merge without having to add a new repository. | | Sure, because in this situation the common ancestor is the version | you | load (so it can always be found). And the delta between the working | copy and the version you merge is empty, so you have no changes. | | You did not get me right | | scenario 1: I click on the slice press merge get an error ancestor | not found | scenario 2: I click on the **latest working copy version* that led to | the error of scenario and do merge I get no changes of course | + scenario 1 and it merges without the error of scenario 1 (it means | that he suddenly magically found the ancestry) | | for me there is a bug. Because between scenario 1 and 2 there is no | difference since this is exactly the same version that I have | as working copy. | | | I think that in squeak they cut the problem (if you do not have the | history what do you do). | You should still be able to merge. | | I don't think they do anything different? If the ancestor version | is | missing you simply cannot do a meaningful merge. It is as simple as | that. | | Yes i see what you mean. You cannot use the ancestry to do a clever | merge. What I meant is that we should be able to see what changed | based on the latest loaded version (no need to have the complete | ancestor since it is broken). | | Because often using the latest working copy and having the diff is | only what I need. Is whatI'm sayign make sense? | | | ___ | Pharo-project mailing list | Pharo-project@lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] JPEGReadWriter and JPEGReadWriter2
Thanks! http://code.google.com/p/pharo/issues/detail?id=2206 Fixed. In Inbox Name: Graphics-MarianoMartinezPeck.225 Author: MarianoMartinezPeck Time: 24 March 2010, 9:16:53 pm UUID: f951fbb9-7db0-4b75-b383-ec616065476d Ancestors: Graphics-StephaneDucasse.224 Fix to issue http://code.google.com/p/pharo/issues/detail?id=2206 Rename JPEGReadWriter2 to PluginBasedJPEGReadWriter On Wed, Mar 17, 2010 at 4:24 PM, Stéphane Ducasse stephane.duca...@inria.fr wrote: PluginBasedJPEGReadWriter On Mar 17, 2010, at 2:11 PM, Mariano Martinez Peck wrote: I read class comments and seem to be different, but I don't like the name at all. We should rename (or remove?) JPEGReadWriter2 to something better. we should merge them ? I have no idea...I just send a warning to you. Cheers Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
The ancestry is not broken! The problem is that you miss *ancestor versions*, because they were deleted or moved. I know now since we systematically merge during our process I wonder how we break it. May be this is when you publish the smalltalk rewrite. Could check if you have Polymorph-Widgets-lr.214 in your local cache? Yes, and it is also in http://www.squeaksource.com/PharoTreatedInbox. So you need to add that repository to be able to merge. I know now let me repeat the bug I see This is not a bug of Monticello. This is because you move versions around and you don't tell Monticello where to find them. Lukas -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Issue 2205
http://code.google.com/p/pharo/issues/detail?id=2205 In PharoInbox: Morphic-LaurentLaffont.558 As all SimpleHierarchicalListMorph PluggableTreeMorph users put autoDeselect to false (or bug if not), it's now the default. Laurent Laffont ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] cannot update metacello in rc3
Hi, I took the RC3 dev image and I tried ConfigurationOfMetacello loadLatestVersion, but it fails. I did not have time to look into this, but this is problematic :). Cheers, Doru -- www.tudorgirba.com It's not how it is, it is how we see it. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] cannot update metacello in rc3
On Wed, Mar 24, 2010 at 9:28 PM, Tudor Girba tudor.gi...@gmail.com wrote: Hi, I took the RC3 dev image and I tried ConfigurationOfMetacello loadLatestVersion, but it fails. Hi Tudor. I have just tasted downloading ConfigurationOfMetacello-DaleHenrichs.266 and it worked ok for me, no problem. I did not have time to look into this, but this is problematic :). But Dale is not magician. You should at least said what was the problem or attach PharoDebug.log ;) Cheers Mariano Cheers, Doru -- www.tudorgirba.com It's not how it is, it is how we see it. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] cannot update metacello in rc3
Hi, Sorry, I am a bit sick and did not express myself correctly. I just wanted to point out the fact that loadLatestVersion crashes, which is a bit strange. And for that, I just described the simple scenario to reproduce it. I did not want to say that it is impossible to load the latest Metacello :) Cheers, Doru On 24 Mar 2010, at 21:32, Mariano Martinez Peck wrote: On Wed, Mar 24, 2010 at 9:28 PM, Tudor Girba tudor.gi...@gmail.com wrote: Hi, I took the RC3 dev image and I tried ConfigurationOfMetacello loadLatestVersion, but it fails. Hi Tudor. I have just tasted downloading ConfigurationOfMetacello- DaleHenrichs.266 and it worked ok for me, no problem. I did not have time to look into this, but this is problematic :). But Dale is not magician. You should at least said what was the problem or attach PharoDebug.log ;) Cheers Mariano Cheers, Doru -- www.tudorgirba.com It's not how it is, it is how we see it. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Don't give to get. Just give. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] cannot update metacello in rc3
On Wed, Mar 24, 2010 at 9:48 PM, Tudor Girba tudor.gi...@gmail.com wrote: Hi, Sorry, I am a bit sick and did not express myself correctly. I just wanted to point out the fact that loadLatestVersion crashes, which is a bit strange. And for that, I just described the simple scenario to reproduce it. Ufff sorry, now it was me that didn't express my self correctly (and I am not sick). I wanted to said that I downloaded ConfigurationOfMetacello- DaleHenrichs.266 and then I evaluated: ConfigurationOfMetacello loadLatestVersion and worked ok for me. Hope you get better. Mariano I did not want to say that it is impossible to load the latest Metacello :) Cheers, Doru On 24 Mar 2010, at 21:32, Mariano Martinez Peck wrote: On Wed, Mar 24, 2010 at 9:28 PM, Tudor Girba tudor.gi...@gmail.com wrote: Hi, I took the RC3 dev image and I tried ConfigurationOfMetacello loadLatestVersion, but it fails. Hi Tudor. I have just tasted downloading ConfigurationOfMetacello-DaleHenrichs.266 and it worked ok for me, no problem. I did not have time to look into this, but this is problematic :). But Dale is not magician. You should at least said what was the problem or attach PharoDebug.log ;) Cheers Mariano Cheers, Doru -- www.tudorgirba.com It's not how it is, it is how we see it. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com Don't give to get. Just give. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
I know now let me repeat the bug I see This is not a bug of Monticello. It is or may be of the network because tell me the difference between scenario 1 and scenario 2? I think that you do not read what I'm writing. There is no difference except that in the first scenario it barks and the second it works. And I just merge the latest working copy (which means that I did nothing) in between. scenario1 working copy polymorphWiget.7.mcz I click on polymorphWiget.24.mcz merge - I get an error ancestor cannot be found scenario1 working copy polymorphWiget.7.mcz I click on polymorphWiget.7.mcz merge - no changes (ok this is what I hope what arriving) Then I click on polymorphWiget.24.mcz merge - I get no error. AND I CAN MERGE None. So may be the network was flaky and when I merged the second time the package was loaded in my cache. I try to understand what is the problem. This is because you move versions around and you don't tell Monticello where to find them. But our process does not move them around since packages in the inbox are systematically merged and the merged versions are copied into pharo. Then the commited versions are moved to treated. So we have a merge barrier! to keep the ancestry. So by process we should not get that. This is strange that only this one is a problem (may be they are some others) but really few compared to the large number of package versions we have. So this is probably a glitch somewhere Lukas: I ***KNOW*** how MC branching/merging works. I KNOW IT. Now I'm trying to understand how the moved package could be moved in treated while it should have been to pharo. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Panic
Hi folks. OT In my university were I was graduated, used to teach with Dolphin few years ago, then squeak and this semester they will probably start to teach with Pharo. The good thing is that they have like 6 courses, with 50 students each courseso, it is good :) I hope several of them join the community. Carla, anything to say about PDP? ;) /OT I was talking with them, and they missed (me too) a little utility that was in Dolphin and that I remember in VAST: the panic button. In dolphin is panic, in VAST I don't remember exactly. But basically, what it does is to close ALL what it is open. All kind of windows, popups or anything. Right now, we have a Delete unchanged windows but: - it only takes into account windows. I want to close everything: transcripts, workspaces, popups, etc. Even more, OCompletion sometimes lets some popups alive and users (mostly beginners) don't know how to remove them. - I want to close ALL windows, I don't care if you were editing or not. - I dont like the name Delete unchanged Windows. Can we renamed to *Close * unchanged windows ? So...I can add it to the Windows - Panic I am not sure if Panic is the best name. Do you have better ideas? Basically, it does this: World submorphs reject: [:m | m == LogoImageMorph default ] thenDo: [:each | each delete] (remove all World submorphs but the Pharo logo) The first question is, do you like the idea? should I add it ? The second is, how can I delete a SystemWindows that has been being edited without saving ? because right now, the popup raises saying Changes has not been saved. I want to delete them without asking. I have no idea how to do this. Help ? maybe there is a preference or notifier that I can turn of before the execution and then put it back ? I searched in Morph to see if there is a deleteWithoutAsking or similar but I didn't find anything. Thanks Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] MIT strikes back (was Re: [smalltalk-research] Re: [Esug-list] Google Summer Of Code 2010 news!!!)
On Tue, 2010-03-23 at 19:30 +0100, Hilaire Fernandes wrote: Bryce Kampjes a écrit : On Thu, 2010-03-11 at 16:31 -0600, Chris Muller wrote: Well, I certainly care.. Stef wasn't remarking about license rights, he said didn't understand the smiley face. Frankly, I don't either. After years of teasing from Bryce and now this? What a crushing disappointment. I'm still here And still making progress though slowly. Can't you get support to progress more easily? Should not be difficult regarding the importance of your work? Help's always welcome but it's likely easier to help after Exupery supports closures. Bryce ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Searching for references
Hi folks. Today I were talking with Noury and from our point of view, there is a bug in the Class references. Forget about refactoring browser. Right now, if you look for the references of a class, it ONLY searches literal matches in the source code of methods. It doesn't take into account for example if you have subclasses. In the abstract speaking, if there are subclasses, isn't that considered a reference ? Even more, the tool would be much more useful if it can find such information. Several times, I look for references of a class I don't know and that I think it can be removed. I look references, zero. Excellent, I can removed. But thenI realized it has a subclass and that class is referenced in 20 places...fresh example: DummySuperclassOfColorPickerMorph. In summary, it would be great if subclasses can be tacking into account also. Or at least I don't know, create another menu entry for that... I am the only one who think that ? what is your opinion ? Cheers Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] funny behavior with MC
So this is probably a glitch somewhere I doubt so. Lukas: I ***KNOW*** how MC branching/merging works. I KNOW IT. Now I'm trying to understand how the moved package could be moved in treated while it should have been to pharo. I imagine that when you browsed the different repositories you touched the version and Monticello copied it to its cache. So it isn't enough to know how merging exactly works, but you need to know all the exact semantics of each mouse movement in the MC UI :-) Lukas -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Searching for references
Forget about refactoring browser. Right now, if you look for the references of a class, it ONLY searches literal matches in the source code of methods. It doesn't take into account for example if you have subclasses. In the abstract speaking, if there are subclasses, isn't that considered a reference ? If you use the refactoring browser to remove it will warn you about that situation. Maybe the normal remove should warn about subclasses too, like the rm in unix does. In summary, it would be great if subclasses can be tacking into account also. Or at least I don't know, create another menu entry for that... There is already a menu item, it is called 'show hierarchy'. I guess the tools don't display these kind of references because then you suddenly have two different kinds of objects as a result: methods and classes. Lukas -- Lukas Renggli http://www.lukas-renggli.ch ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] Panic
2010/3/24 Mariano Martinez Peck marianop...@gmail.com: Hi folks. OT In my university were I was graduated, used to teach with Dolphin few years ago, then squeak and this semester they will probably start to teach with Pharo. The good thing is that they have like 6 courses, with 50 students each courseso, it is good :) I hope several of them join the community. Carla, anything to say about PDP? ;) /OT I was talking with them, and they missed (me too) a little utility that was in Dolphin and that I remember in VAST: the panic button. In dolphin is panic, in VAST I don't remember exactly. But basically, what it does is to close ALL what it is open. All kind of windows, popups or anything. Right now, we have a Delete unchanged windows but: - it only takes into account windows. I want to close everything: transcripts, workspaces, popups, etc. Even more, OCompletion sometimes lets some popups alive and users (mostly beginners) don't know how to remove them. - I want to close ALL windows, I don't care if you were editing or not. - I dont like the name Delete unchanged Windows. Can we renamed to Close unchanged windows ? So...I can add it to the Windows - Panic I am not sure if Panic is the best name. Do you have better ideas? Basically, it does this: World submorphs reject: [:m | m == LogoImageMorph default ] thenDo: [:each | each delete] (remove all World submorphs but the Pharo logo) The first question is, do you like the idea? should I add it ? I thinking of even more radical process - replace the World instance alltogether, and then recreate all default things from scratch (logo, tabs etc). So, then old World instance and all its submorphs will be GCed.. and you don't have to delete anything. The panic, as i understand, is not where you interested whether you having something unsaved or not - it should reset UI unconditionally, and in this way, leaving minimal chances that you will still be plagued by some inconsistency after reset. The second is, how can I delete a SystemWindows that has been being edited without saving ? because right now, the popup raises saying Changes has not been saved. I want to delete them without asking. I have no idea how to do this. Help ? maybe there is a preference or notifier that I can turn of before the execution and then put it back ? I searched in Morph to see if there is a deleteWithoutAsking or similar but I didn't find anything. Thanks Mariano ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Best regards, Igor Stasenko AKA sig. ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Re: [Pharo-project] cannot update metacello in rc3
Doru, I was just a little bit worried when RC3 was shipped with a #development blessing for 1.0-beta.25, now I have a concrete reason to be worried. Since 1.0-beta.25 is in #development, the latestVersion of Metacello is 1.0-beta.24.1 and thats the version that gets loaded by #loadLatestVersion... With that said you _have_ exposed a bug in the #loadLatestVersion method: | project | project := self project. project updateProject. project latestversion load When self project is evaluated the latestVersion is 1.0-beta.24.1. After #updateProject is performed, the latestVersion in ConfigurationOfMetacello is 1.0-beta.25.1, but since we don't refresh the project, we load 1.0-beta.24.1. If you do ConfigurationOfMetacello loadLatestVersion, close the walkback(s) and try ConfigurationOfMetacello loadLatestVersion again, you'll be updated correctly. I've checked in a fix for #loadLatestVersion, so if you update the configuration first, then do #loadLatestVersion ... that will work also. Nice catch and I hope that you get better, Dale - Tudor Girba tudor.gi...@gmail.com wrote: | Hi, | | I took the RC3 dev image and I tried ConfigurationOfMetacello | loadLatestVersion, but it fails. | | I did not have time to look into this, but this is problematic :). | | Cheers, | Doru | | | -- | www.tudorgirba.com | | It's not how it is, it is how we see it. | | | ___ | Pharo-project mailing list | Pharo-project@lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Update cache?
Hi all Updating a Pharo image to the latest version doesn't use the downloaded update files as a cache for future updates. Is this done on purpose? Cheers, Hernán ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
[Pharo-project] Auto-rename image and changes file after updating
Hi, I've noticed every time I update a Pharo image I should rename manually the image and changes file names to match the new updated version number. I.e.: If you have PharoCore-1.1-11291-UNSTABLE.changes PharoCore-1.1-11291-UNSTABLE.image then update to #11295 and save and quit, you should modify the file names manually to PharoCore-1.1-11295-UNSTABLE.changes PharoCore-1.1-11295-UNSTABLE.image The attached files does the following: -After a Pharo software update, evaluate the FileOutNewNamesAfterUpdate.st script -Quit the image -For Win users: Run the batch updateFileNames.bat to rename the image and changes files to the latest version. (this is not the same as Save as...) Feel free to modify and use it as you want :) Cheers, Hernán FileOutNewNamesAfterUpdate.st Description: Binary data updateFileNames Description: Binary data ___ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
