[Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0. * Issues fixed*: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862. *Big changes*: - Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800. *Smaller changes: * - Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly. The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2.... Cheers Mariano
- Background with Pharo picture. This was a joke. It looked nice :)Â Â Â I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white.
I was shocked when I read this, but actually it looks pretty cool. The only problem is that my screen is too large. Could a single instance be aligned in the top middle of the screen? I like the image. I just loaded some of the extra packages and that works really great. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
On Fri, Jan 22, 2010 at 3:56 PM, Lukas Renggli <renggli@gmail.com> wrote:
- Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white.
I was shocked when I read this, but actually it looks pretty cool.
hahahahah thanks :) Actually, I did it for my own image, but then I like it and wanted to show you :)
The only problem is that my screen is too large.
That cannot be a problem ;)
Could a single instance be aligned in the top middle of the screen?
Lukas, I really don't understand the problem when you have a bigger screen. Is the picture cut ? do you have an screenshot ?
I like the image. I just loaded some of the extra packages and that works really great.
Cool! Thanks. Mariano 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
Could a single instance be aligned in the top middle of the screen?
Lukas, I really don't understand the problem when you have a bigger screen. Is the picture cut ? do you have an screenshot ?
It is a minor problem, but I couldn't find another one (hahahahhaha) The image just repeats in a not so nice way. I think it would look better if the rest of the screen was white. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
2010/1/22 Lukas Renggli <renggli@gmail.com>
Could a single instance be aligned in the top middle of the screen?
Lukas, I really don't understand the problem when you have a bigger screen. Is the picture cut ? do you have an screenshot ?
It is a minor problem, but I couldn't find another one (hahahahhaha)
This is a good news then :) Hope everyone has this kind of problems hahaha
The image just repeats in a not so nice way. I think it would look better if the rest of the screen was white.
ok...now I understand....that's because I don't have a screen! hahaha I have no idea how we can solve this :( Maybe some Morphic guru can help us.
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
El vie, 22-01-2010 a las 16:10 +0100, Mariano Martinez Peck escribió:
Hey Mariano, good work. the 1.0 release is almost here. I like the image, but as the others say centered and in a white background or a blue like the one of the image. Cheers -- Miguel Cobá http://miguel.leugim.com.mx
2010/1/22 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
El vie, 22-01-2010 a las 16:10 +0100, Mariano Martinez Peck escribió:
Hey Mariano, good work. the 1.0 release is almost here.
I like the image, but as the others say centered and in a white background or a blue like the one of the image.
If you really like the idea of having a nice background like this, we will someone can take care about it. I know nothing. Just did a Proof of concept :) Does someone want to take care of this please?
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi Mariano, Nice work. Moose loads and works as expected. I also loaded O2 without problems. Cheers, Doru On 22 Jan 2010, at 15:32, Mariano Martinez Peck wrote:
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0.
Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
Big changes:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
Smaller changes:
- Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- www.tudorgirba.com "We cannot reach the flow of things unless we let go."
On 22 janv. 2010, at 16:33, Tudor Girba wrote:
Hi Mariano,
Nice work.
Moose loads and works as expected. I also loaded O2 without problems.
And the Moose tests run fine on a linux server.
Cheers, Doru
On 22 Jan 2010, at 15:32, Mariano Martinez Peck wrote:
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0.
Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
Big changes:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
Smaller changes:
- Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- www.tudorgirba.com
"We cannot reach the flow of things unless we let go."
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Simon
Hi Mariano: looks great, but the background picture should be fixed ;) (no repetition and centered please). First thing I noticed, is that the behavior of the code editor changed. I am using O2 incase that matters. Looks like the type assistance is disabled? Examples are opening parentheses, which are not auto-completed with the closing parentheses. But also selecting text and typing ( or " does not lead to the old behavior where the selection was surrounded accordingly, but now it is just simply replaced. How do I get back the old/smarter behavior? Thanks Stefan On 22 Jan 2010, at 15:32, Mariano Martinez Peck wrote:
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0.
Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
Big changes:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
Smaller changes:
- Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525
Well, and in the whole system, there is no code completion at all. Neither in the code editor, nor in the search bar... Very nasty... Best Stefan On 22 Jan 2010, at 16:42, Stefan Marr wrote:
Hi Mariano:
looks great, but the background picture should be fixed ;) (no repetition and centered please).
First thing I noticed, is that the behavior of the code editor changed. I am using O2 incase that matters.
Looks like the type assistance is disabled? Examples are opening parentheses, which are not auto-completed with the closing parentheses. But also selecting text and typing ( or " does not lead to the old behavior where the selection was surrounded accordingly, but now it is just simply replaced.
How do I get back the old/smarter behavior?
Thanks Stefan
On 22 Jan 2010, at 15:32, Mariano Martinez Peck wrote:
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0.
Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
Big changes:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
Smaller changes:
- Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525
On Fri, Jan 22, 2010 at 4:55 PM, George Herolyants < george.herolyants@gmail.com> wrote:
2010/1/22 Stefan Marr <pharo@stefan-marr.de>:
Well, and in the whole system, there is no code completion at all.
Neither in the code editor, nor in the search bar...
Very nasty...
Very strange... I've just checked. Code completion works just fine in this RC.
But you are using OB, aren't you ?
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On Fri, Jan 22, 2010 at 4:55 PM, George Herolyants < george.herolyants@gmail.com> wrote:
2010/1/22 Stefan Marr <pharo@stefan-marr.de>:
Well, and in the whole system, there is no code completion at all.
Neither in the code editor, nor in the search bar...
Very nasty...
Very strange... I've just checked. Code completion works just fine in this RC.
Works here too... (exupery vm, Linux). Laurent
On Fri, Jan 22, 2010 at 4:42 PM, Stefan Marr <pharo@stefan-marr.de> wrote:
Hi Mariano:
looks great, but the background picture should be fixed ;) (no repetition and centered please).
It was just for fun. As this image is for beta-testers, I could give my self this luxury ahahah. But yes, we need someone that help us with this if we want to keep it.
First thing I noticed, is that the behavior of the code editor changed. I am using O2 incase that matters.
Yes, I think it matters O2, because in the default dev, everything works. I tried installing O2, and I noticed the same behavior as you.
Looks like the type assistance is disabled?
OCompletion, yes.
Examples are opening parentheses, which are not auto-completed with the closing parentheses.
I think this is Shout, but yes, I noticed too.
But also selecting text and typing ( or " does not lead to the old behavior where the selection was surrounded accordingly, but now it is just simply replaced.
How do I get back the old/smarter behavior?
I copied the code that O2 maintainers give us in their ANN email. But, I looked and I think the problem is that they are installing the core of O2 as default. But you may want to load a Dev version. To do that, can you try installing O2 in this way and let us know: Gofer new squeaksource: 'MetacelloRepository'; package:'ConfigurationOfO2'; load. ((Smalltalk at: #ConfigurationOfO2) project version: '1.0') load: 'Dev'
Thanks Stefan
On 22 Jan 2010, at 15:32, Mariano Martinez Peck wrote:
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0.
Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
Big changes:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
Smaller changes:
- Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr <http://soft.vub.ac.be/%7Esmarr> Phone: +32 2 629 3956 Fax: +32 2 629 3525
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
On 22 Jan 2010, at 16:54, Mariano Martinez Peck wrote:
Gofer new squeaksource: 'MetacelloRepository'; package:'ConfigurationOfO2'; load.
((Smalltalk at: #ConfigurationOfO2) project version: '1.0') load: 'Dev'
That gives me an error: -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525
Ok...there seems to be a problem in the configuration then... 2010/1/22 Stefan Marr <pharo@stefan-marr.de>
On 22 Jan 2010, at 16:54, Mariano Martinez Peck wrote:
Gofer new squeaksource: 'MetacelloRepository'; package:'ConfigurationOfO2'; load.
((Smalltalk at: #ConfigurationOfO2) project version: '1.0') load:
'Dev'
That gives me an error:
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr <http://soft.vub.ac.be/%7Esmarr> Phone: +32 2 629 3956 Fax: +32 2 629 3525
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Just tried a fresh image, there you get the same error: Could not load: OCForO2 On 22 Jan 2010, at 17:01, Stefan Marr wrote:
On 22 Jan 2010, at 16:54, Mariano Martinez Peck wrote:
Gofer new squeaksource: 'MetacelloRepository'; package:'ConfigurationOfO2'; load.
((Smalltalk at: #ConfigurationOfO2) project version: '1.0') load: 'Dev'
That gives me an error: <PastedGraphic-1.tiff>
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 3956 Fax: +32 2 629 3525
Gofer new squeaksource: 'MetacelloRepository'; package:'ConfigurationOfO2'; load.
((Smalltalk at: #ConfigurationOfO2) project version: '1.0') load: 'Dev'
That gives me an error:
ah, there was an error in the dev spec group, I fixed this. Mariano, probably it's best when you copy the loading statement above in the workspace, so that in the dev image, people get syntax highlighting and completion when loading O2. David
On Fri, Jan 22, 2010 at 5:52 PM, David Röthlisberger <squeak@webcitas.ch>wrote:
Gofer new squeaksource: 'MetacelloRepository'; package:'ConfigurationOfO2'; load.
((Smalltalk at: #ConfigurationOfO2) project version: '1.0') load:
'Dev'
That gives me an error:
ah, there was an error in the dev spec group, I fixed this.
Mariano, probably it's best when you copy the loading statement above in the workspace, so that in the dev image, people get syntax highlighting and completion when loading O2.
Yes, I can perfectly do it. I just didn't realize it :( The other possiblily is you put Dev as defult..maybe this make sense? What do you think? For me it is the same... Cheers Mariano
David
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/1/22 Mariano Martinez Peck <marianopeck@gmail.com>
On Fri, Jan 22, 2010 at 4:42 PM, Stefan Marr <pharo@stefan-marr.de> wrote:
Hi Mariano:
looks great, but the background picture should be fixed ;) (no repetition and centered please).
It was just for fun. As this image is for beta-testers, I could give my self this luxury ahahah. But yes, we need someone that help us with this if we want to keep it.
I like it ! Laurent
I'm very pressed for time right now, but I like the external projects workspace. I still think that there is way too much code, as all of the work can be done by one method that forms the name of the configuation class and takes (at most) a version string. The phrase "syntactic sugar" comes to mind - not quite the same thing, essentially so for our purposes. One question: why do we "need" to release 1.0? It would be nice, if we are ready, but I would not want to see a sense of urgency replace good judgement - just asking the question. Bill ________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Friday, January 22, 2010 9:32 AM To: Pharo Development Subject: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2 Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0. Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862. Big changes: - Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800. Smaller changes: - Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly. The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2.... Cheers Mariano
2010/1/22 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
I'm very pressed for time right now, but I like the external projects workspace. I still think that there is way too much code, as all of the work can be done by one method that forms the name of the configuation class and takes (at most) a version string. The phrase "syntactic sugar" comes to mind - not quite the same thing, essentially so for our purposes.
Why we don't use Loader ? Still in alpha state ? I like it and it's simple to use. Laurent
2010/1/22 laurent laffont <laurent.laffont@gmail.com>
2010/1/22 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
I'm very pressed for time right now, but I like the external projects workspace. I still think that there is way too much code, as all of the work can be done by one method that forms the name of the configuation class and takes (at most) a version string. The phrase "syntactic sugar" comes to mind - not quite the same thing, essentially so for our purposes.
Why we don't use Loader ? Still in alpha state ? I like it and it's simple to use.
Because we are not even stable with the current tools. We cannot do all toghether. Please guys, we need to go step by step. Loader is still in development.
Laurent
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
We do not need new tools to take several lines and lots of irrelevant/redundant sugar down to one line with two relevant items. Please consider adding something like the attached to *anything* that is in the image; then load scripts will be far simpler than we are encouraging at present. Bill ________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Friday, January 22, 2010 11:15 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2 2010/1/22 laurent laffont <laurent.laffont@gmail.com<mailto:laurent.laffont@gmail.com>> 2010/1/22 Schwab,Wilhelm K <bschwab@anest.ufl.edu<mailto:bschwab@anest.ufl.edu>> I'm very pressed for time right now, but I like the external projects workspace. I still think that there is way too much code, as all of the work can be done by one method that forms the name of the configuation class and takes (at most) a version string. The phrase "syntactic sugar" comes to mind - not quite the same thing, essentially so for our purposes. Why we don't use Loader ? Still in alpha state ? I like it and it's simple to use. Because we are not even stable with the current tools. We cannot do all toghether. Please guys, we need to go step by step. Loader is still in development. Laurent _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr<mailto:Pharo-project@lists.gforge.inria.fr> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/1/22 Schwab,Wilhelm K <bschwab@anest.ufl.edu>
I'm very pressed for time right now, but I like the external projects workspace. I still think that there is way too much code, as all of the work can be done by one method that forms the name of the configuation class and takes (at most) a version string. The phrase "syntactic sugar" comes to mind - not quite the same thing, essentially so for our purposes.
One question: why do we "need" to release 1.0? It would be nice, if we are ready, but I would not want to see a sense of urgency replace good judgement - just asking the question.
There are SEVERAL reasons, but I don't have time to answer correctly. I will let the board to answer, but I will to a summary: - Because of marketing - Because to give visibility to outside - People that are waiting to build stuff because they won't do it until have a "stable release" - Companies may not move on a propject that doesn't have yet a stable release - Having two branches requieres time and effort - We need to progress in 1.1 - Because people won't believe in us anymore. We said that the 1.0 release was going to be one year ago. If you want to continue this discussion, please open another thread. Cheers Mariano
Bill
------------------------------ *From:* pharo-project-bounces@lists.gforge.inria.fr [mailto: pharo-project-bounces@lists.gforge.inria.fr] *On Behalf Of *Mariano Martinez Peck *Sent:* Friday, January 22, 2010 9:32 AM *To:* Pharo Development *Subject:* [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0. * Issues fixed*: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
*Big changes*:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
*Smaller changes: * - Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
There are SEVERAL reasons, but I don't have time to answer correctly. I will let the board to answer, but I will to a summary:
- Because of marketing - Because to give visibility to outside - People that are waiting to build stuff because they won't do it until have a "stable release" - Companies may not move on a propject that doesn't have yet a stable release
- Having two branches requieres time and effort Am I understanding this correctly? Am I to believe that Pharo doesn't have both a development and production branch, or have I misunderstood?
- We need to progress in 1.1 - Because people won't believe in us anymore. We said that the 1.0 release was going to be one year ago.
If you want to continue this discussion, please open another thread.
Cheers
Mariano
Bill
________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck Sent: Friday, January 22, 2010 9:32 AM To: Pharo Development Subject: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0.
Issues fixed:Â In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
Big changes:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!!   Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
Smaller changes:
- Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again.  Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :)   I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
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
- Having two branches requieres time and effort Am I understanding this correctly? Am I to believe that Pharo doesn't have both a development and production branch, or have I misunderstood?
Maybe I don't understand you :) The thing is that there are two "System Update" or Update Stream: One for 1.0 and one for 1.1. So...integrating fixes in both, takes and requires time. And time that we can use is somthing better. And not only that, we you are going to report a bug, submit an issue, etc...you spent time checking if it works on both..etc
Bill
________________________________ From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of
Mariano
Martinez Peck Sent: Friday, January 22, 2010 9:32 AM To: Pharo Development Subject: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0.
Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
Big changes:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
Smaller changes:
- Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
The link is:
https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
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
Michael We have 1.0 (on final release cycle) and 1.1-unstable and for both we have core and dev images. 1.0 is on release period for too long now mainly because of a vicious bug due to mac menu that duplicated events. Now we will release 1.0 because as mariano explained we should move on. His arguments are quite clear to me and the board agrees with him. Then 1.1 already improves so much compared to 1.0 that we will probably a much shorter iteration. Because else people will report bugs on 1.0 that do not make sense in 1.1 and we will try to avoid the "already fixed in 1.1 syndrome" This is why 1.0 should get out! and we celebrate it and go fast improving 1.1. I want a 1.1 version for May/June. Stef
Ok, I had spend a couple of hours with Michael Rueger on the mac menu bug. But I'm not sure if he got around to sending out any changes before he took some time off. If someone can test this I can offer up some change sets for review. I've never been able to recreate this here so someone else has to try. On 2010-01-24, at 12:05 PM, Stéphane Ducasse wrote:
Michael
We have 1.0 (on final release cycle) and 1.1-unstable and for both we have core and dev images.
1.0 is on release period for too long now mainly because of a vicious bug due to mac menu that duplicated events.
-- =========================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
On Mon, Jan 25, 2010 at 2:38 AM, John M McIntosh < johnmci@smalltalkconsulting.com> wrote:
Ok, I had spend a couple of hours with Michael Rueger on the mac menu bug. But I'm not sure if he got around to sending out any changes before he took some time off.
If someone can test this I can offer up some change sets for review. I've never been able to recreate this here so someone else has to try.
Cool. If you send me changesets I can test it.
On 2010-01-24, at 12:05 PM, Stéphane Ducasse wrote:
Michael
We have 1.0 (on final release cycle) and 1.1-unstable and for both we have core and dev images.
1.0 is on release period for too long now mainly because of a vicious bug due to mac menu that duplicated events.
-- =========================================================================== John M. McIntosh <johnmci@smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Ok, I had spend a couple of hours with Michael Rueger on the mac menu bug. But I'm not sure if he got around to sending out any changes before he took some time off.
If someone can test this I can offer up some change sets for review. I've never been able to recreate this here so someone else has to try.
please send. We removed the mac menu for 1.0 but we would like to have it in 1.1 Stef
- Having two branches requieres time and effort Am I understanding this correctly? Am I to believe that Pharo doesn't have both a development and production branch, or have I misunderstood?
Pharo has both a development and production branch. The release 1.0 is going to be the maintained production branch and it will get maintenance releases (1.0.x) if important fixes need to be added. At the same time we are working on the 1.1 development branch, which currently is in unstable alpha stage. Cheers, Adrian
On Jan 24, 2010, at 8:48 PM, Michael Litchard wrote:
There are SEVERAL reasons, but I don't have time to answer correctly. I will let the board to answer, but I will to a summary:
- Because of marketing - Because to give visibility to outside - People that are waiting to build stuff because they won't do it until have a "stable release" - Companies may not move on a propject that doesn't have yet a stable release
- Having two branches requieres time and effort Am I understanding this correctly? Am I to believe that Pharo doesn't have both a development and production branch, or have I misunderstood?
It has... in 1.0, only bugfixes are integrated. There is a 1.1 (already 180 updates) where all the other stuff is done. You can download the last pre-built core image of 1.1 here: http://gforge.inria.fr/frs/download.php/25338/PharoCore-1.1-11177-UNSTABLE.z... The idea is to release 1.0 officially as soon as possible... Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.
El vie, 22-01-2010 a las 15:32 +0100, Mariano Martinez Peck escribió:
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0.
Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
Big changes:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
Smaller changes:
- Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :)
Don't forget Magma. There is a ConfigurationOfMagma already in MetacelloRepository.
Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it.
+1 I generally use: Preferences enable: #fastDragWindowForMorphic. Preferences disable: #windowAnimation. Preferences enable: #updateSavesFile. Preferences disable: #windowAnimation.
- When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
Isn't working? In the image from your link, the preference is working correctly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Miguel Cobá http://miguel.leugim.com.mx
Don't forget Magma. There is a ConfigurationOfMagma already in
MetacelloRepository.
Yes...there are a lot of projects..I even didn't put SqueakDBX/GlorpDBX. I guess that in a future we will have Loader to do this... I don't know. Do you think we should also include Magma? I put the projects I though were most used.
Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it.
+1
I generally use: Preferences enable: #fastDragWindowForMorphic. Preferences disable: #windowAnimation. Preferences enable: #updateSavesFile. Preferences disable: #windowAnimation.
Well....that's why they are called Preferences :) I will check them and see if they make sense. Thanks!!
- When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
Isn't working? In the image from your link, the preference is working correctly.
The link is:
https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
don't put magma there was a list of tools that we wanted in the dev image. The dev image should be convenient for coding after people should load what they want. On Jan 22, 2010, at 5:58 PM, Mariano Martinez Peck wrote:
Don't forget Magma. There is a ConfigurationOfMagma already in MetacelloRepository.
Yes...there are a lot of projects..I even didn't put SqueakDBX/GlorpDBX. I guess that in a future we will have Loader to do this...
I don't know. Do you think we should also include Magma? I put the projects I though were most used.
Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it.
+1
I generally use: Preferences enable: #fastDragWindowForMorphic. Preferences disable: #windowAnimation. Preferences enable: #updateSavesFile. Preferences disable: #windowAnimation.
Well....that's why they are called Preferences :) I will check them and see if they make sense. Thanks!!
- When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
Isn't working? In the image from your link, the preference is working correctly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@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@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
El vie, 22-01-2010 a las 22:14 +0100, Stéphane Ducasse escribió:
don't put magma there was a list of tools that we wanted in the dev image.
Not loaded in the image, but only the snippet to load it in the welcome workspace. As an example of the packages available to load. :) Cheers
The dev image should be convenient for coding after people should load what they want.
On Jan 22, 2010, at 5:58 PM, Mariano Martinez Peck wrote:
Don't forget Magma. There is a ConfigurationOfMagma already in MetacelloRepository.
Yes...there are a lot of projects..I even didn't put SqueakDBX/GlorpDBX. I guess that in a future we will have Loader to do this...
I don't know. Do you think we should also include Magma? I put the projects I though were most used.
Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it.
+1
I generally use: Preferences enable: #fastDragWindowForMorphic. Preferences disable: #windowAnimation. Preferences enable: #updateSavesFile. Preferences disable: #windowAnimation.
Well....that's why they are called Preferences :) I will check them and see if they make sense. Thanks!!
- When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
Isn't working? In the image from your link, the preference is working correctly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@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@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
-- Miguel Cobá http://miguel.leugim.com.mx
What about the NetNameResolver issues ? 1852<http://code.google.com/p/pharo/issues/detail?id=1852&sort=-id&colspec=ID%20T...> 1853<http://code.google.com/p/pharo/issues/detail?id=1853&sort=-id&colspec=ID%20T...>
hi ramiro this is not that we do not want to fix them :) First we wan to finish/release 1.0 then after we need help for all kinds of things so that we can make time on the difficult ones. Stef On Jan 23, 2010, at 1:45 AM, Ramiro Diaz Trepat wrote:
What about the NetNameResolver issues ?
1852 1853
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
2010/1/23 Ramiro Diaz Trepat <ramiro@diaztrepat.name>
What about the NetNameResolver issues ?
1852<http://code.google.com/p/pharo/issues/detail?id=1852&sort=-id&colspec=ID%20T...> 1853<http://code.google.com/p/pharo/issues/detail?id=1853&sort=-id&colspec=ID%20T...>
I don't know, but are you aware of these: http://code.google.com/p/pharo/issues/detail?id=961 http://code.google.com/p/pharo/issues/detail?id=1031 http://code.google.com/p/pharo/issues/detail?id=794 Can you check if it is the same problem and update the issues as required ? Cheers Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Maybe it would be better to add these definitions to a wiki page or to the website. Like this we can add new ones and update existing ones independent of releases. In the welcome workspace you could then just point to the URL that contains the current list. There is already a related wiki page: http://code.google.com/p/pharo/wiki/PackagesTestedInPharo Cheers, Adrian On Jan 22, 2010, at 17:58 , Mariano Martinez Peck wrote:
Don't forget Magma. There is a ConfigurationOfMagma already in
MetacelloRepository.
Yes...there are a lot of projects..I even didn't put SqueakDBX/GlorpDBX. I guess that in a future we will have Loader to do this...
I don't know. Do you think we should also include Magma? I put the projects I though were most used.
Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it.
+1
I generally use: Preferences enable: #fastDragWindowForMorphic. Preferences disable: #windowAnimation. Preferences enable: #updateSavesFile. Preferences disable: #windowAnimation.
Well....that's why they are called Preferences :) I will check them and see if they make sense. Thanks!!
- When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
Isn't working? In the image from your link, the preference is working correctly.
The link is:
https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@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@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
I generally use: Preferences enable: #fastDragWindowForMorphic. Preferences disable: #windowAnimation.
ok...this two are ok in the dev image. Aren't they ?
Preferences enable: #updateSavesFile.
I am not sure what it does. But anyway, we remove the update from the dev image...so, this still make sense? What does it saves ? which kind of file is it ? a mcz ?
Preferences disable: #windowAnimation.
- When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
Isn't working? In the image from your link, the preference is working correctly.
The link is:
https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ Pharo-project mailing list Pharo-project@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@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
El vie, 22-01-2010 a las 18:13 +0100, Mariano Martinez Peck escribió:
I generally use: Preferences enable: #fastDragWindowForMorphic. Preferences disable: #windowAnimation.
ok...this two are ok in the dev image. Aren't they ?
Preferences enable: #updateSavesFile.
I am not sure what it does. But anyway, we remove the update from the dev image...so, this still make sense?
What does it saves ? which kind of file is it ? a mcz ?
Yes it saves the files of the update stream and as you correctly state, it is not needed because the updat eoption is disable. :)
Preferences disable: #windowAnimation.
> - When installing Seaside now doesn't ask for user and password > ( admin/seaside ). In addition, the Seaside Control Panel is only > isntalled if OB is installed. This means that yu can install it in > core or dev. Thanks Dale! > - Disable of System Update for Dev images as it is not working > properly.
Isn't working? In the image from your link, the preference is working correctly.
> > > The link is: > https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2.... > > Cheers > > Mariano > >
> _______________________________________________ > Pharo-project mailing list > Pharo-project@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@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
-- Miguel Cobá http://miguel.leugim.com.mx
2010/1/22 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
El vie, 22-01-2010 a las 18:13 +0100, Mariano Martinez Peck escribió:
I generally use: Preferences enable: #fastDragWindowForMorphic. Preferences disable: #windowAnimation.
ok...this two are ok in the dev image. Aren't they ?
Preferences enable: #updateSavesFile.
I am not sure what it does. But anyway, we remove the update from the dev image...so, this still make sense?
What does it saves ? which kind of file is it ? a mcz ?
Yes it saves the files of the update stream and as you correctly state, it is not needed because the updat eoption is disable. :)
:) Sol...in summary, you agree with the default preferences!
Preferences disable: #windowAnimation.
> - When installing Seaside now doesn't ask for user and password > ( admin/seaside ). In addition, the Seaside Control Panel is only > isntalled if OB is installed. This means that yu can install it in > core or dev. Thanks Dale! > - Disable of System Update for Dev images as it is not working > properly.
Isn't working? In the image from your link, the preference is working correctly.
> > > The link is: >
https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
> > Cheers > > Mariano > >
> _______________________________________________ > Pharo-project mailing list > Pharo-project@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@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
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Thanks Mariano for this image. I like the background. Am I the only one to prefer rounded windows instead of straight corners? Cheers, Alexandre On 22 Jan 2010, at 11:32, Mariano Martinez Peck wrote:
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0.
Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
Big changes:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
Smaller changes:
- Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
On Jan 23, 2010, at 3:36 AM, Alexandre Bergel wrote:
Thanks Mariano for this image. I like the background.
Am I the only one to prefer rounded windows instead of straight corners?
= slower
Cheers, Alexandre
On 22 Jan 2010, at 11:32, Mariano Martinez Peck wrote:
Hi folks. This is 1.0 RC2. Please, look at this image in a nice way because it is very likely that if there is no big issue, it will be 1.0 official. We need to release 1.0.
Issues fixed: In addition to the fixes from the PharoCore, we have: 1033, 1182, 1826, 1862.
Big changes:
- Now we use OB from Lukas Renggli repository and we have ALL TESTS GREEN!!! Thanks Lukas! - O2 loads again in the image without breaking OB. Read the workspace to see how to install it. Thanks David and Alexandre! - We have almost (only one failing here) ALL TESTS of the PharoDev image in green. They are more than 8800.
Smaller changes:
- Fixed the problem with Metacello and OCompletion. No more overrides. - System -> About now shows the real Pharo name, not the core. I am also being "compatible" with the new SystemVersion that we have in 1.1 :) Thanks Michael and Miguel! - I didn't left again my proxy settings. I fixed this in my build scripts. It should be clean :) - Mercury bar is back again. If you want to disable: Preferences disable: #mercuryPanel. - Added a lot of cleanups after creating the image, including condensing .changes - Added Refactoring-Spelling again. Thanks Stan! - I wrote a ConfigurationOfNile instead of Nile-All and depends on Monticello dependencies. - New welcome workspaces. Also getting started workspace and another workspace explaining how to load external packages like Seaside (2.8 and 3), Magritte, Pier, Moose, GetTools, O2, etc. Finally it is also added a link to the new ProfStef :) Do you think that with this we are able to close issue1479 ? - Background with Pharo picture. This was a joke. It looked nice :) I promise I don't put it again if you don't like. To remove it evaluate: World color: Color white. - Enable the preference fastDragWindowForMorphic. Sorry, but it most computers this works REALLY slow. If you want them back, just disable it. - When installing Seaside now doesn't ask for user and password ( admin/seaside ). In addition, the Seaside Control Panel is only isntalled if OB is installed. This means that yu can install it in core or dev. Thanks Dale! - Disable of System Update for Dev images as it is not working properly.
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Cheers
Mariano
_______________________________________________ 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
The link is: https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Just a minor thing. Shouldn't the name be: Pharo-1.0-10508-rc2dev10.01.2.zip in order to match the PharoCore name format: PharoCore-1.0-10508-rc2.zip Format: (Pharo|PharoCore)-version-update-tag Cheers -- Miguel Cobá http://miguel.leugim.com.mx
Thanks. I will take care next time. 2010/1/23 Miguel Enrique Cobá Martinez <miguel.coba@gmail.com>
The link is:
https://gforge.inria.fr/frs/download.php/25397/Pharo1.0-10508-rc2dev10.01.2....
Just a minor thing. Shouldn't the name be:
Pharo-1.0-10508-rc2dev10.01.2.zip
in order to match the PharoCore name format:
PharoCore-1.0-10508-rc2.zip
Format:
(Pharo|PharoCore)-version-update-tag
Cheers
-- Miguel Cobá http://miguel.leugim.com.mx
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Hi Mariano, great job of the release. I've hit this one bug- pool dictionary spelling is checking a collection where it expects a string. Here's an alternative. RBPoolDictionaryNamesSpellingRule>>checkClass: aContext (aContext selectedClass isTrait or: [ aContext selectedClass isMeta ]) ifTrue: [ ^ self ]. aContext selectedClass poolDictionaryNames do: [:poolName | (self check: poolName) do: [ :each | result addSearchString: each; addClass: aContext selectedClass ]] Otherwise refactoring etc all seem good. I get the same test results as other Linux testers. ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10507-rc2dev10-01-2-tp4440307p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
On Sat, Jan 23, 2010 at 4:47 PM, Stan Shepherd <stan.shepherd414@gmail.com>wrote:
Hi Mariano, great job of the release.
Thanks!
I've hit this one bug- pool dictionary spelling is checking a collection where it expects a string.
Here's an alternative.
RBPoolDictionaryNamesSpellingRule>>checkClass: aContext (aContext selectedClass isTrait or: [ aContext selectedClass isMeta ]) ifTrue: [ ^ self ]. aContext selectedClass poolDictionaryNames do: [:poolName |
(self check: poolName) do: [ :each | result addSearchString: each; addClass: aContext selectedClass ]]
Otherwise refactoring etc all seem good. I get the same test results as other Linux testers.
Lukas, do you know if this a bug ?
...Stan
-- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10507-rc2dev10-01-2-tp4440307p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Otherwise refactoring etc all seem good. I get the same test results as other Linux testers.
Lukas, do you know if this a bug ?
I removed the rule for the pool imports a while ago, they are already checked more appropriately at the place they are defined. Btw, I integrated the tests of Stan into the package: Refactoring-Tests-Spelling. Also I had to rename the tests packages of the rest of the refactoring browser to avoid conflicts. The packages are now called: AST-Tests-Core and Refactoring-Tests-Core. Can you update the Metacello definitions? Lukas -- Lukas Renggli http://www.lukas-renggli.ch
On Sun, Jan 24, 2010 at 3:25 PM, Lukas Renggli <renggli@gmail.com> wrote:
Otherwise refactoring etc all seem good. I get the same test results as other Linux testers.
Lukas, do you know if this a bug ?
I removed the rule for the pool imports a while ago, they are already checked more appropriately at the place they are defined.
Btw, I integrated the tests of Stan into the package: Refactoring-Tests-Spelling.
Also I had to rename the tests packages of the rest of the refactoring browser to avoid conflicts. The packages are now called: AST-Tests-Core and Refactoring-Tests-Core.
Can you update the Metacello definitions?
Thanks Lukas. I have just updated the configuration. I got 11 failures. Is this correct ? Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfRefactoringBrowser'; load. ((Smalltalk at: #ConfigurationOfRefactoringBrowser) project version: '1.2') load: 'Core Tests'
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
Thanks Lukas. I have just updated the configuration. I got 11 failures. Is this correct ?
Gofer new    squeaksource: 'MetacelloRepository';    package: 'ConfigurationOfRefactoringBrowser';    load.
((Smalltalk at: #ConfigurationOfRefactoringBrowser) project version: '1.2') load: 'Core Tests'
No, that's not correct. Hahahahahahahahahhahahahahhahaahhahahahaa. They all pass on my machine. What is the problem? Lukas
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
-- Lukas Renggli http://www.lukas-renggli.ch
On Sun, Jan 24, 2010 at 4:41 PM, Lukas Renggli <renggli@gmail.com> wrote:
Thanks Lukas. I have just updated the configuration. I got 11 failures. Is this correct ?
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfRefactoringBrowser'; load.
((Smalltalk at: #ConfigurationOfRefactoringBrowser) project version: '1.2') load: 'Core Tests'
No, that's not correct. Hahahahahahahahahhahahahahhahaahhahahahaa.
They all pass on my machine. What is the problem?
For correct I meant "expected". Can you try to reproduce them with with https://gforge.inria.fr/frs/download.php/25366/PharoCore-1.0-10508rc2.zip ? Some examples: testTemporaryVariableNames fails in runRule: aClass expect: aCollection because when it does: self assert: (rule = each or: [ each result isEmpty ]) description: rule name , ' should not report errors' ]. each is RBClassCategoriesSpellingRule and rule is RBTemporaryVariableNamesSpellingRule and each result isEmpty gives false testClassCategories failes in runRule: aClass expect: aCollection because when it does self assert: (aCollection includes: each) description: each printString , ' should not be reported' ]. aCollection is #('Wrng') and each is 'Refactoring' I attach screenshot. Cheers Mariano
Lukas
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
-- 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
I attach screenshot.
Delete the file rb-spelling.dat next to your image, that should fix the problem. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
On Sun, Jan 24, 2010 at 5:08 PM, Lukas Renggli <renggli@gmail.com> wrote:
I attach screenshot.
Delete the file rb-spelling.dat next to your image, that should fix the problem.
I haven't such file :(
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
I haven't such file :(
True, you are on a mac too :-) Go to "Apple Mail" and type the word "Refactoring". It should be highlighted with the spell-checker. Click on "Add to Dictionary". Then the tests should pass. No, sorry. I have to fix the tests. Wait. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
On Sun, Jan 24, 2010 at 5:25 PM, Lukas Renggli <renggli@gmail.com> wrote:
I haven't such file :(
True, you are on a mac too :-)
Since two months, yes :)
Go to "Apple Mail" and type the word "Refactoring". It should be highlighted with the spell-checker. Click on "Add to Dictionary". Then the tests should pass.
No, sorry. I have to fix the tests. Wait.
hahahahha no problem. I am not hurry at all :)
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
Go to "Apple Mail" and type the word "Refactoring". It should be highlighted with the spell-checker. Click on "Add to Dictionary". Then the tests should pass.
No, sorry. I have to fix the tests. Wait.
hahahahha no problem. I am not hurry at all :)
I think I fixed it. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
On Sun, Jan 24, 2010 at 10:24 PM, Lukas Renggli <renggli@gmail.com> wrote:
Go to "Apple Mail" and type the word "Refactoring". It should be highlighted with the spell-checker. Click on "Add to Dictionary". Then the tests should pass.
No, sorry. I have to fix the tests. Wait.
hahahahha no problem. I am not hurry at all :)
I think I fixed it.
Wiiiii :) Only one expected failire! 351 run, 350 green :) Thanks Lukas!! Next Pharo image will use RB 1.2. Cheers Mariano
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
Wiiiii :)Â Â Â Only one expected failire!
Yeah, I don't know how to fix that one. And it probably won't be in the near future. Maybe at some point somebody understands why it is broken.
Thanks Lukas!! Next Pharo image will use RB 1.2.
RB 1.2 ? Lukas -- Lukas Renggli http://www.lukas-renggli.ch
On Sun, Jan 24, 2010 at 11:43 PM, Lukas Renggli <renggli@gmail.com> wrote:
Wiiiii :) Only one expected failire!
Yeah, I don't know how to fix that one. And it probably won't be in the near future. Maybe at some point somebody understands why it is broken.
Thanks Lukas!! Next Pharo image will use RB 1.2.
RB 1.2 ?
hahahahha sorry. I meant the 1.2 version of the ConfigurationOfRefactoringBrowser :)
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
Lukas, I get three fails of your 'meta' tests: #testIdentifier - 'Got ''$a'', but expected ''a''' #testCamelCase - '#normalizeCamelCase: is not idempotent' (puts in an extra space) 'Camel Case' vs 'Camel Case' #testSelector - '#normalizeSelector: is not idempotent' also in the original tests on real classes RBArgumentVariableNamesSpellingClass>>argumentVariableNamesSpelling: rong <- not flagged ^self RBTemporaryVariableNamesSpellingClassSideClass>>temporaryVariableNamesSpellingClassSide | rongTemporary | <- not flagged ^self RBCorrectSpellingClass 'IT' 'OK and 'don't' are all flagged - don't is not flagged. Is this your preferred behaviour? What do you think about including the 'real' tests as well as the meta tests? Real tests also have the benefit of serving as examples to people who are trying to use tests to understand the system. And there might be a risk that a meta test passes without testing the real live situation. ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10507-rc2dev10-01-2-tp4440307p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
I get three fails of your 'meta' tests:
#testIdentifier - 'Got ''$a'', but expected ''a''' #testCamelCase - '#normalizeCamelCase: is not idempotent'  (puts in an extra space) 'Camel  Case' vs 'Camel Case' #testSelector - '#normalizeSelector: is not idempotent'
Are you sure you have the latest code loaded (Refactoring-Spelling-lr.19)? Because I fixed those bugs.
also in the original tests on real classes
RBArgumentVariableNamesSpellingClass>>argumentVariableNamesSpelling: rong <- not flagged     ^self
'rong' is in the dictionary as a correct word thus it is correct. The tests that work on code should only test the extraction of text from code, not other things like the spell checker itself. That's why I moved such tests to a separate class (RBSpellCheckerTest). Of course you can argue that it is a bug to have 'rong' in the dictionary. Could be that this was part of some slang or abbreviations dictionary I've included. I bet nobody wants to go through this list of almost a million words and check them all?
'IT' 'OK and 'don't' are all flagged - don't is not flagged. Is this your preferred behaviour?
They are all not flagged on my machine. Neither with the internal nor with the mac spelling.
What do you think about including the 'real' tests as well as the meta tests?
I don't like it at all. I hate the situation we currently have with Slime. We will have to fix that. People run the rules on the complete image and then they suddenly have dozens of errors that do not matter.
Real tests also have the benefit of serving as examples to people who are trying to use tests to understand the system. And there might be a risk that a meta test passes without testing the real live situation.
These are negative examples. You don't want to show a newbie negative examples. It is also dangerous in books to show examples of how not to do it. People don't always understand/read everything and just copy and past whatever they see. After all these are not meta-examples, these are just like the real examples. Except that the code is only present in the image while the tests run. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
'IT' 'OK and 'don't' are all flagged - don't is not flagged. Is this your preferred behaviour?
They are all not flagged on my machine. Neither with the internal nor with the mac spelling.
Maybe you need to delete the cached dictionary rb-spelling.dat? I had to create a new one to include all the short forms "don't", "won't", ... Lukas -- Lukas Renggli http://www.lukas-renggli.ch
Lukas Renggli wrote:
'rong' is in the dictionary as a correct word thus it is correct. ...
OK, when I use a different misspelling those tests pass.
'IT' 'OK and 'don't' are all flagged - don't is not flagged. Is this your preferred behaviour?
They are all not flagged on my machine. Neither with the internal nor with the mac spelling.
Still flagged here. Seem to be extra ' characters in the check strings. See http://www.flickr.com/photos/8185994@N03/4303501422/sizes/o/ search strings screen print on Flickr ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10507-rc2dev10-01-2-tp4440307p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
They are all not flagged on my machine. Neither with the internal nor with the mac spelling.
Still flagged here. Seem to be extra ' characters in the check strings. See  http://www.flickr.com/photos/8185994@N03/4303501422/sizes/o/ search strings screen print on Flickr
The words you show are simply not in the dictionary: - These words I don't know, but I am not a native speaker: ftmch drepehs - The implementation excepts to have natural language in comments, not code. Thus this is not split: goodVariable - I don't know about apostrophes at the end of the word. Should they be removed? methods'' don't' RB' IT' OK' Lukas -- Lukas Renggli http://www.lukas-renggli.ch
Lukas Renggli wrote:
The words you show are simply not in the dictionary:
- These words I don't know, but I am not a native speaker:
ftmch drepehs
Intentional misspellings, which are correctly flagged (first was a character on the BBC show 'The Young Ones, second is my surname backwards :) ) Lukas Renggli wrote:
- The implementation excepts to have natural language in comments, not code. Thus this is not split:
goodVariable
OK. I put those in the class comments because the browser creates the comment for you by default, like: A RBLiteralValuesSpellingRule is xxxxxxxxx. Instance Variables matcher: matcher - xxxxx So it is your call whether you want class comments to be able to have the variable names in.
- I don't know about apostrophes at the end of the word. Should they be removed?
methods'' don't' RB' IT' OK'
Again, your call as to whether you want people to be able to use in class comments something like: To test, enter into a workspace: 'This is what you need to type' or, The valid entries are: 'yes', 'no','maybe' There is the edge case of possessive plural apostrophes like: The methods' categories which is grammatically correct but most people can probably live without. Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10507-rc2dev10-01-2-tp4440307p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
OK. I put those in the class comments because the browser creates the comment for you by default, like: A RBLiteralValuesSpellingRule is xxxxxxxxx.
Instance Variables     matcher:
matcher     - xxxxx So it is your call whether you want class comments to be able to have the variable names in.
Ahh true, I just never used that kind of class comment. But in this case we should probably do a camel case normalization for the class comment too. Thanks for pointing out.
- I don't know about apostrophes at the end of the word. Should they be removed?
  methods''   don't'   RB'   IT'   OK'
Again, your call as to whether you want people to be able to use in class comments something like:
To test, enter into a workspace: 'This is what you need to type'
or,
The valid entries are: 'yes', 'no','maybe'
There is the edge case of possessive plural apostrophes like:
The methods' categories
which is grammatically correct but most people can probably live without.
Ok, thanks for the clarification. I am convinced that they need to be trimmed. Lukas -- Lukas Renggli http://www.lukas-renggli.ch
Sorry, forget this. Lukas has dropped the pool dictionary test. ...Stan -- View this message in context: http://n2.nabble.com/BetaTesting-ANN-Pharo1-0-10507-rc2dev10-01-2-tp4440307p... Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
participants (19)
-
Adrian Lienhard -
Alexandre Bergel -
David Röthlisberger -
George Herolyants -
John M McIntosh -
laurent laffont -
Lukas Renggli -
Marcus Denker -
Mariano Martinez Peck -
Michael Litchard -
Miguel Enrique Cobá Martinez -
Ramiro Diaz Trepat -
Schwab,Wilhelm K -
Schwab,Wilhelm K
-
Simon Denier -
Stan Shepherd -
Stefan Marr -
Stéphane Ducasse -
Tudor Girba