- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Log for June and July

by StÃ©phane Ducasse

Hi guys of course it was dry because we run to go to have lunch. But in a nutshell it was our monthly update and evaluation for the next period. I particularly like the last item :) Stef > Planned Tasks for June > ----------------------- > > - ClassBuilder > should be integrated beginning of July > > - Class Organizer > is integrated > > - new inspector > integrated > but > problems with focus > returning the window > > - Opal integration > - stabilization > - methods withoutsource > - > Athens > integrated > submorph problems > Configurations are missing > Issue > > TxModel > Not ready > > Metacello 2 > not integrated > integrated as soon as a BuilderCI is working > Still issues in 30. > should be Integrated in this release > > VM acceptance tests > - > > NewList Widget migration > - stress tests needed > - integrated but little glitches > > NewSpec interpreter > - two of works > - should be integrated in this iteration > > Tabs > - integrated > > Kill Package Info > - Rpackage iteration under way > - > > TreeModel should use the new enhance the new TreeMorph > - for this integration > > > Planned Tasks For JULY > ---------------------- > > - ClassBuilder > > - New inspector glitches > > - Enable new debugger > > - Opal integration > - stabilization > - methods withoutsource > > - Athens > submorph problems > Configurations are missing > > - TxModel > Not ready > > - Diff to the mailing-list > > - Metacello 2 > > - VM acceptance tests > - > - NewList Widget migration > - stress tests needed > - integrated but little glitches > > - NewSpec interpreter > > - Kill Package Info > - Rpackage iteration under way > > - TreeModel should use the new enhance the new TreeMorph > > - Reflectivity > > - Monkey > > - Class and traits > > - Monticello and traits > > - VM > - stackVM slowdow > - 64 bits -> bad on linux > - crashes > - small integer > - iOS > - VM > > > Planned in August/September > ------------------ > - Morph rewrite > > - Athens use > > - remove old organizer > > - remove Package Info > > - StringHolder hierarchy > > - remove URL > > - reevaluate color editing based on AST > > - make the Old compiler unloadable > > - new user experience > > Summer Release > -------------- > - Metacello 2 (if easy) > - Delay back port > - interrupt fixes > - ProfStef (plus extension saying that stef is cool) >

July 3, 2013

Re: [Pharo-dev] Text Encoding questions

by StÃ©phane Ducasse

On Jul 3, 2013, at 10:10 AM, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: > > > Le 03/07/2013 09:55, Camillo Bruni a Ã©crit : >> AFAIK that might depend on the font ;). > > Oh, that sounds about right. > >> Do you have the same font for everything? > > In the settings, yes. Oh, finally, no. The Bitmap DejaVu Sans used by default was the culprit, the rest of the fonts were set automagically to DejaVu Sans (without the Bitmap). > > It went correct with selecting DejaVu Sans Regular 9 for the Default font (instead of Bitmap DejaVu Sans Regular 9). I got some funny behavior when I enable FreeType in my startup preferences. The sad thing is that it was the same configuration as the one of camillo. So I was puzzled. Stef > >> I remember having problems displaying some strange characters in methods, whereas they would show up fine in the inspectors. > >> If you have a reproducible use case can you open a bug report with a nice description? > > As you can see, not really the case for a bug report :) > > Thanks Camillo. I can also confirm that FileReference get utf8 file names and path correctly :) > > Thierry > >> On 2013-07-03, at 09:55, Goubier Thierry <thierry.goubier(a)cea.fr> wrote: >>> Hi All, >>> >>> anybody able to explain why in some cases I get a correct display of non-latin1 characters and in others not ? Like in the joined inspector. >>> >>> Note that I'm displaying more or less the same WideString (where the Ï letter appears as ? or as Ï). >>> >>> Thanks, >>> >>> Thierry >>> -- >>> Thierry Goubier >>> CEA list >>> Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s >>> 91191 Gif sur Yvette Cedex >>> France >>> Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >>> >> >> >> >> > > -- > Thierry Goubier > CEA list > Laboratoire des Fondations des SystÃ¨mes Temps RÃ©el EmbarquÃ©s > 91191 Gif sur Yvette Cedex > France > Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95 >

July 3, 2013

Re: [Pharo-dev] Monticello Migration Script

by StÃ©phane Ducasse

On Jul 3, 2013, at 9:01 PM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Today I (finally) duplicated most of my public repositories into StHub (Zinc, Zodiac, STON, Neo). Once again I was amazed by StHub's general speed. > > It was also the first time I used the Monticello Migration Script as published on the SqS home page. I really like that script: it is beautiful and embodies a lot of what I like about Pharo, scripting elegantly using some powerful helper objects. > > I edited it a little bit though (using #select:thenDo: and some longer temporary names): > > http://ws.stfx.eu/AACQP1RUZ818 > > I do wonder however why in the first part #allResolved is used, instead of using #allVersionNames directly like in the rest of the script. I do not know :) It works so I used it :) I will push your version in the gofer chapter :) > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

July 3, 2013

Re: [Pharo-dev] NativeBoost with no access to sources

by StÃ©phane Ducasse

>> > I don't know.. look: > > realloc: flags mem: lpMem size: dwBytes > > <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode> > > > ^ self nbCall: > #( LPVOID HeapReAlloc (self, DWORD flags, LPVOID lpMem, SIZE_T dwBytes) ) > > here, see: flags, lpMem, dwBytes names is in function signature same > as in your method. > That's how NB knows which argument from method corresponds to argument > passed to function. > > now if you don't use argument names , how the above should look like? > > realloc: flags mem: lpMem size: dwBytes > > <primitive: #primitiveNativeCall module: #NativeBoostPlugin error: errorCode> > > ^ self nbCall: > #( LPVOID HeapReAlloc (self, DWORD @1, LPVOID @2, SIZE_T @3) ) > ? Igor I understand your concerns but also the problem thierry is facing and it looks to me like a valid scenario. Stef

July 3, 2013

Re: [Pharo-dev] We did it! SlotClassBuilder is active

by StÃ©phane Ducasse

I'm impressed and pleased! Thanks Camillo and Martin for your attitude. Really. It opens a new range of possibilities with first class instance variables. Now with Opal + slots we will be able to implement cool features. Stef > Hi, > > Today we turned on the SlotClassBuilderâ¦ this means actually quite a huge change, as it puts into place > lots of things that we can build on later. > > What it means for now > > -> A new, much easier to understand ClassBuilder > -> meta Objects. Layouts + Slots > > For example, there is now for every instance variable a meta object that describes it > It will be very interesting to see what we can do with that! > > Thanks to Toon + Camillo for the original implementation, and Martin Dias with Camillo > for the work to get in really into 3.0. > > Marcus

July 3, 2013

Re: [Pharo-dev] Monticello Migration Script

by Camillo Bruni

On 2013-07-03, at 21:01, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Today I (finally) duplicated most of my public repositories into StHub (Zinc, Zodiac, STON, Neo). Once again I was amazed by StHub's general speed. nice :) > It was also the first time I used the Monticello Migration Script as published on the SqS home page. I really like that script: it is beautiful and embodies a lot of what I like about Pharo, scripting elegantly using some powerful helper objects. > > I edited it a little bit though (using #select:thenDo: and some longer temporary names): > > http://ws.stfx.eu/AACQP1RUZ818 > > I do wonder however why in the first part #allResolved is used, instead of using #allVersionNames directly like in the rest of the script. > > Sven > > -- > Sven Van Caekenberghe > Proudly supporting Pharo > http://pharo.org > http://association.pharo.org > http://consortium.pharo.org > > > > >

July 3, 2013

Monticello Migration Script

by Sven Van Caekenberghe

Today I (finally) duplicated most of my public repositories into StHub (Zinc, Zodiac, STON, Neo). Once again I was amazed by StHub's general speed. It was also the first time I used the Monticello Migration Script as published on the SqS home page. I really like that script: it is beautiful and embodies a lot of what I like about Pharo, scripting elegantly using some powerful helper objects. I edited it a little bit though (using #select:thenDo: and some longer temporary names): http://ws.stfx.eu/AACQP1RUZ818 I do wonder however why in the first part #allResolved is used, instead of using #allVersionNames directly like in the rest of the script. Sven -- Sven Van Caekenberghe Proudly supporting Pharo http://pharo.org http://association.pharo.org http://consortium.pharo.org

July 3, 2013

Re: [Pharo-dev] We did it! SlotClassBuilder is active

by camille teruel

Yeeessss!!!!! 2013/7/3 Luc Fabresse <luc.fabresse(a)gmail.com> > > Yes thanks to all to keep pushing this kind of really cool new features! > > Luc > > > 2013/7/3 Sven Van Caekenberghe <sven(a)stfx.eu> > >> >> On 03 Jul 2013, at 17:00, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> > Hi, >> > >> > Today we turned on the SlotClassBuilderâ¦ this means actually quite a >> huge change, as it puts into place >> > lots of things that we can build on later. >> > >> > What it means for now >> > >> > -> A new, much easier to understand ClassBuilder >> > -> meta Objects. Layouts + Slots >> > >> > For example, there is now for every instance variable a meta object >> that describes it >> > It will be very interesting to see what we can do with that! >> > >> > Thanks to Toon + Camillo for the original implementation, and Martin >> Dias with Camillo >> > for the work to get in really into 3.0. >> > >> > Marcus >> >> Progress, progress ! >> >> Now we need some nice blog posts explaining all this to mere mortals, >> like me. >> >> Sven >> >> >> >

July 3, 2013

Re: [Pharo-dev] question about UI

by Pablo R. Digonzelli

Thanks ! Ing. Pablo Digonzelli Sofware Solutions IP Soluciones SRL 25 de Mayo 521. Entrepiso A email: pdigonzelli(a)softsargentina.com email: pdigonzelli(a)gmail.com twitter: @pdigonzelli Tel: 0381 4227378 Cel: 0381 155982714 ----- Mensaje original ----- De: "Gisela Decuzzi" <giseladecuzzi(a)gmail.com> Para: "Pharo Development List" <pharo-dev(a)lists.pharo.org> Enviados: MiÃ©rcoles, 3 de Julio 2013 3:54:47 Asunto: Re: [Pharo-dev] question about UI Hi Pablo, a few days ago I wrote about implementing a simple window with spec here: http://pharorwrules.wordpress.com/2013/06/26/a-look-into-spec/ 2013/7/3 Pablo R. Digonzelli < pdigonzelli(a)softsargentina.com > Thanks to all! I starting learn spec Ing. Pablo Digonzelli Sofware Solutions IP Soluciones SRL 25 de Mayo 521. Entrepiso A email: pdigonzelli(a)softsargentina.com email: pdigonzelli(a)gmail.com twitter: @pdigonzelli Tel: 0381 4227378 Cel: 0381 155982714 De: "Esteban Lorenzano" < estebanlm(a)gmail.com > Para: "Pharo Development List" < pharo-dev(a)lists.pharo.org > Enviados: Martes, 2 de Julio 2013 18:37:57 Asunto: Re: [Pharo-dev] question about UI On Jul 2, 2013, at 10:25 PM, StÃ©phane Ducasse < stephane.ducasse(a)inria.fr > wrote: <blockquote> <blockquote> hello list. I am thinking develop a business application in pharo. Excellent! <blockquote> I need information about tools for UI for business applications. for example dolphin has MVP framework for desktop. </blockquote> Yes and its MVP framework is cool. <blockquote> I prefer browser/desktop enable UI framework. Which are the tools you can recommend? </blockquote> You should have a look at Spec - ben I do not remember where is the tutorial. Benjamin started to rewrite widgets like list. <blockquote> Perhaps someone has experience with businnes app. </blockquote> Esteban, benjamin. What I suggest is to really ask for feedback in the mailing-list and to be prepared to help also because we are changing the widgets and the tools (and the underlying layers but our time is short). </blockquote> I made a commercial desktop application using glamour+magritte+home made stuff nowadays, you could do more or less the same using spec/glamour+magritte3+keychain... it requires some work (mostly on learning any of them), but is perfectly doable :) Esteban <blockquote> <blockquote> TIA PD: Sorry for my english </blockquote> :) Frankly this is not important. <blockquote> Ing. Pablo Digonzelli Sofware Solutions IP Soluciones SRL 25 de Mayo 521. Entrepiso A email: pdigonzelli(a)softsargentina.com email: pdigonzelli(a)gmail.com twitter: @pdigonzelli Tel: 0381 4227378 Cel: 0381 155982714 </blockquote> </blockquote> </blockquote>

July 3, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/./label=wi… 1 regressions found. Tests.CodeImport.ChunkImportTestCase.testImportAClassCategory

July 3, 2013