- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Really Important message (tm)

by StÃ©phane Ducasse

kiss to Florencia :) On Apr 16, 2010, at 10:37 PM, Mariano Martinez Peck wrote: > Be aware (Carla) you don't need to be a letter...it can be the letter signed, scanned and sent by email. For those who live far away from France it is easier and cheaper ;) > > Mariano > > ps: don't tell my wife I am here hahahah > > On Fri, Apr 16, 2010 at 10:08 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Apr 16, 2010, at 12:02 AM, GermÃ¡n Arduino wrote: > > > The letter is on the way. > > > > A first question, to help with unstable I should use it as it comes > > (with no added packages) or I can install somethings to make the > > environment more comfortable (as shout for example) ? > > the way you want but if you load packages you should pay attention that you changes do not impact them by accident. > Ideally we would like to have metacello to manage core and the process would be > > - take latest core > - update > -> get Pharo with maintained Pharo package: sound > ------------------------------------------------------- this phase should be done for us on a server with a hudson cron like job > > - you change > - you publish changes > -------------------------------------------------------- > we take the current unstable core + packages > - integrate your changes > -> produce new version of packages + new metacello configuration > > Now since loading code is too slow we have to pay attention and avoid to frantically remove packages from the image > because they can desync too easily when we do system wide changes. > > So for simple things just take the latest unstable and publish changes > > > > > > GermÃ¡n. > > > > 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> Thanks! > >> As I said, 30 min are enough > >> Stef > >> > >> On Apr 15, 2010, at 9:25 PM, GermÃ¡n Arduino wrote: > >> > >>> ok, my signed agreement is leaving today for France. > >>> > >>> I will try to start understanding how is the contribution process in > >>> Pharo and playing a bit with unstable. > >>> > >>> Unfortunately I've very little free time, but still, will try to help. > >>> > >>> Cheers. > >>> > >>> > >>> 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >>>> Hi guys > >>>> > >>>> Let me reiterate it: > >>>> > >>>> - We need you! > >>>> - 75 % of the issues on the bug tracker are simple. > >>>> - BTW how did we learn stuff, by reading code and learning. I'm not smart I'm just a tedious learner > >>>> I can any opportunity to learn something new. > >>>> - if you spend 30 min a week, YOU CAN get an IMPACT! > >>>> - if pharo is important for you then 30 min in a good investment > >>>> - every single LITTLE bugs fixed and improvement is IMPORTANT > >>>> - we do not want the final latest coolest superhyper cool and hyper clever fixes! > >>>> - we accept little improvement > >>>> - in UNSTABLE we have the right to push not 100% finish code > >>>> > >>>> Now think what YOU can do for pharo. Because Yes YOU can > >>>> - screencast > >>>> - checking tests (yesterday I moved CompiledMethodAsStringTest>>testPrint to CompiledMethodTest>>testPrint) Yeah hyper difficult > >>>> - Class comments: look at the URI class comment > >>>> - blogging > >>>> - tweeting > >>>> > >>>> > >>>> We should slowly change our process so that Pharo continue to evolve even if we disappear on the moon. > >>>> > >>>> Now I asked marcus to focus on the newcompiler and stop fixing little bugs because we want to make progress on other fronts. > >>>> > >>>> We want newcompiler - we want the newcompiler - we want the newcompiler and fixing it and fixing its interface. > >>>> We want Helvetia hooks -We want Helvetia hooks. > >>>> We want a new package object (but I do not find time to code argh). > >>>> > >>>> Stef > >>>> > >>>> > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>> > >>> > >>> > >>> > >>> -- > >>> ================================================= > >>> GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino > >>> Arduino Software & Web Hosting http://www.arduinosoftware.com > >>> PasswordsPro http://www.passwordspro.com > >>> ================================================= > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 17, 2010

Re: [Pharo-project] we need help for rome

by StÃ©phane Ducasse

Thanks john oops I learned something. Now the problem is that I did not touch them. I just loaded code. So I wonder where they got lost or changed. Alain do you have the same in your image? Stef On Apr 17, 2010, at 4:09 AM, John M McIntosh wrote: > (a) In Sophie > RomeCanvas subclass: #RomePluginCanvas > instanceVariableNames: 'handle target flags strokeColor stack font fontSize fontMatrix currentFillColor currentBackColor glyphAccuracy cachedGlyphBlt cachedClearBlt drawRunPositions drawRunGlyph drawRunPointY' > classVariableNames: 'CachedTarget FlagFill FlagStro > > (b) In Pharo > > RomeCanvas subclass: #RomePluginCanvas > instanceVariableNames: 'handle target flags strokeColor stack font fontSize fontMatrix' > classVariableNames: 'FlagFill FlagStroke Registry' > poolDictionaries: '' > category: 'Rome-PluginCanvas' > > Comment warning: > > INST VAR ORDER IS KNOWN TO PLUGIN! DO NOT REARRANGE! > > > So in the plugin we have... > > if (interpreterProxy->slotSizeOf(canvasOop)) < CanvasInstSize) > fail(). > > > where CanvasInstSize is 13 > > but as you see in (b) the number of instance slots for the canvas Oops is 8. > > 8 < 13, oops you fail. > > So where did the instance vars currentFillColor currentBackColor glyphAccuracy cachedGlyphBlt cachedClearBlt > go? On purpose gone, refactored, old code. etc.... > > > On 2010-04-16, at 1:37 PM, StÃ©phane Ducasse wrote: > >> >> On Apr 16, 2010, at 10:30 PM, John McIntosh wrote: >> >>> Well I'm just as puzzled as you since the primitive gets executed and you are using the same binary that was shipped with Sophie years back. >> >> I like to hear that because I feel less idiot. :) >> >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > =========================================================================== > John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 > Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com > =========================================================================== > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

April 17, 2010

[Pharo-project] MongoDB and Pharo

by Laszlo Zsolt Kiss

Hello! Anybody use this http://www.squeaksource.com/MongoTalk/ with Pharo? Can i will be use this stuff in the production environment? Thx.

April 17, 2010

Re: [Pharo-project] Really Important message (tm)

by Miguel Enrique CobÃ¡ Martinez

El vie, 16-04-2010 a las 22:37 +0200, Mariano Martinez Peck escribiÃ³: > Be aware (Carla) you don't need to be a letter...it can be the letter > signed, scanned and sent by email. For those who live far away from > France it is easier and cheaper ;) > > Mariano > > ps: don't tell my wife I am here hahahah so you are now a married man, congratulations Mariano. Cheers > > On Fri, Apr 16, 2010 at 10:08 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > On Apr 16, 2010, at 12:02 AM, GermÃ¡n Arduino wrote: > > > The letter is on the way. > > > > A first question, to help with unstable I should use it as > it comes > > (with no added packages) or I can install somethings to make > the > > environment more comfortable (as shout for example) ? > > > the way you want but if you load packages you should pay > attention that you changes do not impact them by accident. > Ideally we would like to have metacello to manage core and the > process would be > > - take latest core > - update > -> get Pharo with maintained Pharo package: > sound > ------------------------------------------------------- > this phase should be done for us on a server with a hudson > cron like job > > - you change > - you publish changes > > -------------------------------------------------------- > we take the current unstable core + packages > - integrate your changes > -> produce new version of packages + new metacello > configuration > > Now since loading code is too slow we have to pay attention > and avoid to frantically remove packages from the image > because they can desync too easily when we do system wide > changes. > > So for simple things just take the latest unstable and publish > changes > > > > > > > GermÃ¡n. > > > > 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> Thanks! > >> As I said, 30 min are enough > >> Stef > >> > >> On Apr 15, 2010, at 9:25 PM, GermÃ¡n Arduino wrote: > >> > >>> ok, my signed agreement is leaving today for France. > >>> > >>> I will try to start understanding how is the contribution > process in > >>> Pharo and playing a bit with unstable. > >>> > >>> Unfortunately I've very little free time, but still, will > try to help. > >>> > >>> Cheers. > >>> > >>> > >>> 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >>>> Hi guys > >>>> > >>>> Let me reiterate it: > >>>> > >>>> - We need you! > >>>> - 75 % of the issues on the bug tracker are > simple. > >>>> - BTW how did we learn stuff, by reading code and > learning. I'm not smart I'm just a tedious learner > >>>> I can any opportunity to learn something new. > >>>> - if you spend 30 min a week, YOU CAN get an > IMPACT! > >>>> - if pharo is important for you then 30 min in a > good investment > >>>> - every single LITTLE bugs fixed and improvement > is IMPORTANT > >>>> - we do not want the final latest coolest > superhyper cool and hyper clever fixes! > >>>> - we accept little improvement > >>>> - in UNSTABLE we have the right to push not 100% > finish code > >>>> > >>>> Now think what YOU can do for pharo. Because Yes YOU can > >>>> - screencast > >>>> - checking tests (yesterday I moved > CompiledMethodAsStringTest>>testPrint to > CompiledMethodTest>>testPrint) Yeah hyper difficult > >>>> - Class comments: look at the URI class comment > >>>> - blogging > >>>> - tweeting > >>>> > >>>> > >>>> We should slowly change our process so that Pharo > continue to evolve even if we disappear on the moon. > >>>> > >>>> Now I asked marcus to focus on the newcompiler and stop > fixing little bugs because we want to make progress on other > fronts. > >>>> > >>>> We want newcompiler - we want the newcompiler - we want > the newcompiler and fixing it and fixing its interface. > >>>> We want Helvetia hooks -We want Helvetia hooks. > >>>> We want a new package object (but I do not find time to > code argh). > >>>> > >>>> Stef > >>>> > >>>> > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>> > >>> > >>> > >>> > >>> -- > >>> ================================================= > >>> GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino > >>> Arduino Software & Web Hosting > http://www.arduinosoftware.com > >>> PasswordsPro http://www.passwordspro.com > >>> ================================================= > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

April 17, 2010

Re: [Pharo-project] we need help for rome

by John M McIntosh

(a) In Sophie RomeCanvas subclass: #RomePluginCanvas instanceVariableNames: 'handle target flags strokeColor stack font fontSize fontMatrix currentFillColor currentBackColor glyphAccuracy cachedGlyphBlt cachedClearBlt drawRunPositions drawRunGlyph drawRunPointY' classVariableNames: 'CachedTarget FlagFill FlagStro (b) In Pharo RomeCanvas subclass: #RomePluginCanvas instanceVariableNames: 'handle target flags strokeColor stack font fontSize fontMatrix' classVariableNames: 'FlagFill FlagStroke Registry' poolDictionaries: '' category: 'Rome-PluginCanvas' Comment warning: INST VAR ORDER IS KNOWN TO PLUGIN! DO NOT REARRANGE! So in the plugin we have... if (interpreterProxy->slotSizeOf(canvasOop)) < CanvasInstSize) fail(). where CanvasInstSize is 13 but as you see in (b) the number of instance slots for the canvas Oops is 8. 8 < 13, oops you fail. So where did the instance vars currentFillColor currentBackColor glyphAccuracy cachedGlyphBlt cachedClearBlt go? On purpose gone, refactored, old code. etc.... On 2010-04-16, at 1:37 PM, StÃ©phane Ducasse wrote: > > On Apr 16, 2010, at 10:30 PM, John McIntosh wrote: > >> Well I'm just as puzzled as you since the primitive gets executed and you are using the same binary that was shipped with Sophie years back. > > I like to hear that because I feel less idiot. :) > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

April 17, 2010

Re: [Pharo-project] Really Important message (tm)

by GermÃ¡n Arduino

Thanks by the explanations. I'm already checking the issues and the 1.1 version. Will be back with more questions, be sure! 2010/4/16 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > On Apr 16, 2010, at 12:02 AM, GermÃ¡n Arduino wrote: > >> The letter is on the way. >> >> A first question, to help with unstable I should use it as it comes >> (with no added packages) or I can install somethings to make the >> environment more comfortable (as shout for example) ? > > the way you want but if you load packages you should pay attention that you changes do not impact them by accident. > Ideally we would like to have metacello to manage core and the process would be > > Â Â Â Â - take latest core > Â Â Â Â - update > Â Â Â Â Â Â Â Â -> get Pharo with maintained Pharo package: sound > Â Â Â Â ------------------------------------------------------- this phase should be done for us on a server with a hudson cron like job > > Â Â Â Â - you change > Â Â Â Â - you publish changes > Â Â Â Â -------------------------------------------------------- > Â Â Â Â we take the current unstable core + packages > Â Â Â Â - integrate your changes > Â Â Â Â -> produce new version of packages + new metacello configuration > > Now since loading code is too slow we have to pay attention and avoid to frantically remove packages from the image > because they can desync too easily when we do system wide changes. > > So for simple things just take the latest unstable and publish changes > > > > >> GermÃ¡n. >> >> 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> Thanks! >>> As I said, 30 min are enough >>> Stef >>> >>> On Apr 15, 2010, at 9:25 PM, GermÃ¡n Arduino wrote: >>> >>>> ok, my signed agreement is leaving today for France. >>>> >>>> I will try to start understanding how is the contribution process in >>>> Pharo and playing a bit with unstable. >>>> >>>> Unfortunately I've very little free time, but still, will try to help. >>>> >>>> Cheers. >>>> >>>> >>>> 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>>>> Hi guys >>>>> >>>>> Let me reiterate it: >>>>> >>>>> Â Â Â Â - We need you! >>>>> Â Â Â Â - 75 % of the issues on the bug tracker are simple. >>>>> Â Â Â Â - BTW how did we learn stuff, by reading code and learning. I'm not smart I'm just a tedious learner >>>>> Â Â Â Â I can any opportunity to learn something new. >>>>> Â Â Â Â - if you spend 30 min a week, YOU CAN get an IMPACT! >>>>> Â Â Â Â - if pharo is important for you then 30 min in a good investment >>>>> Â Â Â Â - every single LITTLE bugs fixed and improvement is IMPORTANT >>>>> Â Â Â Â - we do not want the final latest coolest superhyper cool and hyper clever fixes! >>>>> Â Â Â Â - we accept little improvement >>>>> Â Â Â Â - in UNSTABLE we have the right to push not 100% finish code >>>>> >>>>> Now think what YOU can do for pharo. Because Yes YOU can >>>>> Â Â Â Â - screencast >>>>> Â Â Â Â - checking tests (yesterday I moved CompiledMethodAsStringTest>>testPrint to CompiledMethodTest>>testPrint) Yeah hyper difficult >>>>> Â Â Â Â - Class comments: look at the URI class comment >>>>> Â Â Â Â - blogging >>>>> Â Â Â Â - tweeting >>>>> >>>>> >>>>> We should slowly change our process so that Pharo continue to evolve even if we disappear on the moon. >>>>> >>>>> Now I asked marcus to focus on the newcompiler and stop fixing little bugs because we want to make progress on other fronts. >>>>> >>>>> We want newcompiler - Â we want the newcompiler - Â we want the newcompiler and fixing it and fixing its interface. >>>>> We want Helvetia hooks -We want Helvetia hooks. >>>>> We want a new package object (but I do not find time to code argh). >>>>> >>>>> Stef >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> >>>> >>>> -- >>>> ================================================= >>>> GermÃ¡n S. Arduino Â <gsa @ arsol.net> Â Twitter: garduino >>>> Arduino Software & Web Hosting Â http://www.arduinosoftware.com >>>> PasswordsPro Â http://www.passwordspro.com >>>> ================================================= >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2010

Re: [Pharo-project] Really Important message (tm)

by GermÃ¡n Arduino

hehe, I understood that a real letter is needed, and sent it yesterday :) 2010/4/16 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Be aware (Carla) you don't need to be a letter...it can be the letter > signed, scanned and sent by email. For those who live far away from France > it is easier and cheaper ;) > > Mariano > > ps: don't tell my wife I am here hahahah > > On Fri, Apr 16, 2010 at 10:08 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> >> On Apr 16, 2010, at 12:02 AM, GermÃ¡n Arduino wrote: >> >> > The letter is on the way. >> > >> > A first question, to help with unstable I should use it as it comes >> > (with no added packages) or I can install somethings to make the >> > environment more comfortable (as shout for example) ? >> >> the way you want but if you load packages you should pay attention that >> you changes do not impact them by accident. >> Ideally we would like to have metacello to manage core and the process >> would be >> >> Â Â Â Â - take latest core >> Â Â Â Â - update >> Â Â Â Â Â Â Â Â -> get Pharo with maintained Pharo package: sound >> Â Â Â Â ------------------------------------------------------- this phase >> should be done for us on a server with a hudson cron like job >> >> Â Â Â Â - you change >> Â Â Â Â - you publish changes >> Â Â Â Â -------------------------------------------------------- >> Â Â Â Â we take the current unstable core + packages >> Â Â Â Â - integrate your changes >> Â Â Â Â -> produce new version of packages + new metacello configuration >> >> Now since loading code is too slow we have to pay attention and avoid to >> frantically remove packages from the image >> because they can desync too easily when we do system wide changes. >> >> So for simple things just take the latest unstable and publish changes >> >> >> >> >> > GermÃ¡n. >> > >> > 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >> Thanks! >> >> As I said, 30 min are enough >> >> Stef >> >> >> >> On Apr 15, 2010, at 9:25 PM, GermÃ¡n Arduino wrote: >> >> >> >>> ok, my signed agreement is leaving today for France. >> >>> >> >>> I will try to start understanding how is the contribution process in >> >>> Pharo and playing a bit with unstable. >> >>> >> >>> Unfortunately I've very little free time, but still, will try to help. >> >>> >> >>> Cheers. >> >>> >> >>> >> >>> 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> >>>> Hi guys >> >>>> >> >>>> Let me reiterate it: >> >>>> >> >>>> Â Â Â Â - We need you! >> >>>> Â Â Â Â - 75 % of the issues on the bug tracker are simple. >> >>>> Â Â Â Â - BTW how did we learn stuff, by reading code and learning. >> >>>> I'm not smart I'm just a tedious learner >> >>>> Â Â Â Â I can any opportunity to learn something new. >> >>>> Â Â Â Â - if you spend 30 min a week, YOU CAN get an IMPACT! >> >>>> Â Â Â Â - if pharo is important for you then 30 min in a good >> >>>> investment >> >>>> Â Â Â Â - every single LITTLE bugs fixed and improvement is IMPORTANT >> >>>> Â Â Â Â - we do not want the final latest coolest superhyper cool and >> >>>> hyper clever fixes! >> >>>> Â Â Â Â - we accept little improvement >> >>>> Â Â Â Â - in UNSTABLE we have the right to push not 100% finish code >> >>>> >> >>>> Now think what YOU can do for pharo. Because Yes YOU can >> >>>> Â Â Â Â - screencast >> >>>> Â Â Â Â - checking tests (yesterday I moved >> >>>> CompiledMethodAsStringTest>>testPrint to CompiledMethodTest>>testPrint) Yeah >> >>>> hyper difficult >> >>>> Â Â Â Â - Class comments: look at the URI class comment >> >>>> Â Â Â Â - blogging >> >>>> Â Â Â Â - tweeting >> >>>> >> >>>> >> >>>> We should slowly change our process so that Pharo continue to evolve >> >>>> even if we disappear on the moon. >> >>>> >> >>>> Now I asked marcus to focus on the newcompiler and stop fixing little >> >>>> bugs because we want to make progress on other fronts. >> >>>> >> >>>> We want newcompiler - Â we want the newcompiler - Â we want the >> >>>> newcompiler and fixing it and fixing its interface. >> >>>> We want Helvetia hooks -We want Helvetia hooks. >> >>>> We want a new package object (but I do not find time to code argh). >> >>>> >> >>>> Stef >> >>>> >> >>>> >> >>>> _______________________________________________ >> >>>> Pharo-project mailing list >> >>>> Pharo-project(a)lists.gforge.inria.fr >> >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >>>> >> >>> >> >>> >> >>> >> >>> -- >> >>> ================================================= >> >>> GermÃ¡n S. Arduino Â <gsa @ arsol.net> Â Twitter: garduino >> >>> Arduino Software & Web Hosting Â http://www.arduinosoftware.com >> >>> PasswordsPro Â http://www.passwordspro.com >> >>> ================================================= >> >>> >> >>> _______________________________________________ >> >>> Pharo-project mailing list >> >>> Pharo-project(a)lists.gforge.inria.fr >> >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> >> >> >> _______________________________________________ >> >> Pharo-project mailing list >> >> Pharo-project(a)lists.gforge.inria.fr >> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> > >> > _______________________________________________ >> > Pharo-project mailing list >> > Pharo-project(a)lists.gforge.inria.fr >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- ================================================= GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino Arduino Software & Web Hosting http://www.arduinosoftware.com PasswordsPro http://www.passwordspro.com =================================================

April 16, 2010

Re: [Pharo-project] we need help for rome

by laurent laffont

On Linux, Squeak-4.0.3.2202 binaries from squeak vm, Pharo 1.0 image, it works. With PharoCore 1.1-11312 too. Smalltalk listLoadedModules #('SurfacePlugin Apr 13 2010 (i)' 'RomePlugin pango_yo.38 10 April 2010 (e)' 'ZipPlugin 10 April 2010 (i)' 'SocketPlugin 10 April 2010 (i)' 'LargeIntegers v1.5 10 April 2010 (i)' 'LocalePlugin 10 April 2010 (i)' 'B2DPlugin 10 April 2010 (i)' 'BitBltPlugin 10 April 2010 (i)' 'SecurityPlugin 10 April 2010 (i)' 'FilePlugin 10 April 2010 (i)' 'MiscPrimitivePlugin 10 April 2010 (i)') Laurent Laffont On Fri, Apr 16, 2010 at 12:39 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > Hi > > We need help. > Can you execute > > Gofer new > squeaksource: 'PharoTaskForces'; > version: 'Rome-StephaneDucasse.4'; > load > > RomeDemo demoMovingCar > > And let me know if you get an error? > > Then can you let us know what is the value of Smalltalk listLoadedModules > > I do not understand why the prim failed even if the plugin is loaded. > Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2010

Re: [Pharo-project] we need help for rome

by StÃ©phane Ducasse

On Apr 16, 2010, at 10:30 PM, John McIntosh wrote: > Well I'm just as puzzled as you since the primitive gets executed and you are using the same binary that was shipped with Sophie years back. I like to hear that because I feel less idiot. :)

April 16, 2010

Re: [Pharo-project] Really Important message (tm)

by Mariano Martinez Peck

Be aware (Carla) you don't need to be a letter...it can be the letter signed, scanned and sent by email. For those who live far away from France it is easier and cheaper ;) Mariano ps: don't tell my wife I am here hahahah On Fri, Apr 16, 2010 at 10:08 AM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr> wrote: > > On Apr 16, 2010, at 12:02 AM, GermÃ¡n Arduino wrote: > > > The letter is on the way. > > > > A first question, to help with unstable I should use it as it comes > > (with no added packages) or I can install somethings to make the > > environment more comfortable (as shout for example) ? > > the way you want but if you load packages you should pay attention that you > changes do not impact them by accident. > Ideally we would like to have metacello to manage core and the process > would be > > - take latest core > - update > -> get Pharo with maintained Pharo package: sound > ------------------------------------------------------- this phase > should be done for us on a server with a hudson cron like job > > - you change > - you publish changes > -------------------------------------------------------- > we take the current unstable core + packages > - integrate your changes > -> produce new version of packages + new metacello configuration > > Now since loading code is too slow we have to pay attention and avoid to > frantically remove packages from the image > because they can desync too easily when we do system wide changes. > > So for simple things just take the latest unstable and publish changes > > > > > > GermÃ¡n. > > > > 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >> Thanks! > >> As I said, 30 min are enough > >> Stef > >> > >> On Apr 15, 2010, at 9:25 PM, GermÃ¡n Arduino wrote: > >> > >>> ok, my signed agreement is leaving today for France. > >>> > >>> I will try to start understanding how is the contribution process in > >>> Pharo and playing a bit with unstable. > >>> > >>> Unfortunately I've very little free time, but still, will try to help. > >>> > >>> Cheers. > >>> > >>> > >>> 2010/4/15 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > >>>> Hi guys > >>>> > >>>> Let me reiterate it: > >>>> > >>>> - We need you! > >>>> - 75 % of the issues on the bug tracker are simple. > >>>> - BTW how did we learn stuff, by reading code and learning. I'm > not smart I'm just a tedious learner > >>>> I can any opportunity to learn something new. > >>>> - if you spend 30 min a week, YOU CAN get an IMPACT! > >>>> - if pharo is important for you then 30 min in a good > investment > >>>> - every single LITTLE bugs fixed and improvement is IMPORTANT > >>>> - we do not want the final latest coolest superhyper cool and > hyper clever fixes! > >>>> - we accept little improvement > >>>> - in UNSTABLE we have the right to push not 100% finish code > >>>> > >>>> Now think what YOU can do for pharo. Because Yes YOU can > >>>> - screencast > >>>> - checking tests (yesterday I moved > CompiledMethodAsStringTest>>testPrint to CompiledMethodTest>>testPrint) Yeah > hyper difficult > >>>> - Class comments: look at the URI class comment > >>>> - blogging > >>>> - tweeting > >>>> > >>>> > >>>> We should slowly change our process so that Pharo continue to evolve > even if we disappear on the moon. > >>>> > >>>> Now I asked marcus to focus on the newcompiler and stop fixing little > bugs because we want to make progress on other fronts. > >>>> > >>>> We want newcompiler - we want the newcompiler - we want the > newcompiler and fixing it and fixing its interface. > >>>> We want Helvetia hooks -We want Helvetia hooks. > >>>> We want a new package object (but I do not find time to code argh). > >>>> > >>>> Stef > >>>> > >>>> > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>>> > >>> > >>> > >>> > >>> -- > >>> ================================================= > >>> GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino > >>> Arduino Software & Web Hosting http://www.arduinosoftware.com > >>> PasswordsPro http://www.passwordspro.com > >>> ================================================= > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

April 16, 2010