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

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

2010/1/22 Schwab,Wilhelm K <bschwab(a)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(a)lists.gforge.inria.fr [mailto: > pharo-project-bounces(a)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(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

2010/1/22 laurent laffont <laurent.laffont(a)gmail.com> > > 2010/1/22 Schwab,Wilhelm K <bschwab(a)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(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Stefan Marr

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(a)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

Jan. 22, 2010

[Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Torsten Bergmann

Things I've noticed: - Code completion is working for me - the intro workspace window should be smaller - the intro workspace window should provide colors as the other two workspaces (maybe we can group them in a window with tree like help system) - maybe the background should be stretched according to window size (Gary?) - the class categories in the browser are not ordered alphabetic - I hate the old style Squeak cursor and would rather see different cursors (see ConfigurationOfVistaCursors for an example) - anything looks professional - except the old squeak icons, any designer around - I was not able to compile Java and C# code with it ;) Have fun T. -- Haiti-Nothilfe! Helfen Sie per SMS: Sende UIHAITI an die Nummer 81190. Von 5 Euro je SMS (zzgl. SMS-GebÃ¼hr) gehen 4,83 Euro an UNICEF.

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by laurent laffont

2010/1/22 Schwab,Wilhelm K <bschwab(a)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

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Mariano Martinez Peck

Ok...there seems to be a problem in the configuration then... 2010/1/22 Stefan Marr <pharo(a)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(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Schwab,Wilhelm K

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(a)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

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by laurent laffont

2010/1/22 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > On Fri, Jan 22, 2010 at 4:42 PM, Stefan Marr <pharo(a)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

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by laurent laffont

On Fri, Jan 22, 2010 at 4:55 PM, George Herolyants < george.herolyants(a)gmail.com> wrote: > 2010/1/22 Stefan Marr <pharo(a)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

Jan. 22, 2010

Re: [Pharo-project] [BetaTesting] [ANN] Pharo1.0-10507-rc2dev10.01.2

by Stefan Marr

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

Jan. 22, 2010