December 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Moose-dev] Woden-GT integration

by Ronie Salgado

And I have to fix a bug that chrashes it. (opening a view twice) 2014-12-01 11:35 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > If I remember correctly, Doru told me he worked on it > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > On Dec 1, 2014, at 5:31 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi everyone, > > I think that during ESUG Woden was integrated into Toolkit in a way, what > you can see a 3D visualization as one of the representations of the view. > Is there any additional package that provides this functionality? > > Uko > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > >

Dec. 1, 2014

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by Markus Fritsche

On 2014-12-01 07:00, seaside(a)rmod.lille.inria.fr wrote: > Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to > coordinate efforts. Just answer informally, and feel free to spawn > discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > - Created a Ubuntu 14.04 32 Bit virtual machine to take over the ubuntu ppa updating from Damien Cassou > > ### What's next, until 2014-12-14 (*): > - Switching my scripts back to the pharo-ppa once my packages turn out to be useable - Make myself familiar with the pharo vm generation process - see if there are more pharo vm flavours that could be offered in the ppa

Dec. 1, 2014

Re: [Pharo-dev] [Moose-dev] Woden-GT integration

by Alexandre Bergel

If I remember correctly, Doru told me he worked on it Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Dec 1, 2014, at 5:31 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi everyone, > > I think that during ESUG Woden was integrated into Toolkit in a way, what you can see a 3D visualization as one of the representations of the view. Is there any additional package that provides this functionality? > > Uko > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Dec. 1, 2014

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by Esteban A. Maringolo

El Mon Dec 01 2014 at 3:00:29 AM, <seaside(a)rmod.lille.inria.fr> escribiÃ³: > ### Here's what I've been up to since the last WhatsUp: > > - $HEROIC_ACHIEVEMENTS_OR_DISMAL_FAILURES_OR_SIMPLE_BORING_NECESSARY_TASKS > > ### What's next, until 2014-12-14 (*): > - I Attended to a regional BarCamp to talked about OOP, Smalltalk and Pharo. Got very good reception and feedback. One of the attendants even tried Pharo some time ago. The critics were same as usual. > - $NEXT_STEPS_TOWARDS_WORLD_DOMINATION > > Continue to improve our Pharo based applications. Refactoring all the way down.

Dec. 1, 2014

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by Tudor Girba

On Mon, Dec 1, 2014 at 7:00 AM, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to coordinate > efforts. Just answer informally, and feel free to spawn discussions > thereafter! > > ### Here's what I've been up to since the last WhatsUp: Fixed remaining Moose 5.0 issues. Worked on a project I cannot wait to announce :) ### What's next, until 2014-12-14 (*): > Find a way to reliably release Moose. Announce the unannounced project :) Doru -- www.tudorgirba.com "Every thing has its own flow"

Dec. 1, 2014

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by Sven Van Caekenberghe

Nice ! > On 01 Dec 2014, at 15:01, phil(a)highoctane.be wrote: > > On Mon, Dec 1, 2014 at 7:00 AM, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the community an opportunity to easily know what's happening and to coordinate efforts. Just answer informally, and feel free to spawn discussions thereafter! > > ### Here's what I've been up to since the last WhatsUp: > > Two commercial installs of a Pharo/Seaside based solution. > Some tweets with the #pharo tag. > > > > ### What's next, until 2014-12-14 (*): > > More installs. More deals. > Using Mongodb more extensively for one application. > Start of a new application module on business dashboarding. > Documentation of our system writing using Pillar. > CommandLineHandler based tool for console based administration of the system. > > > > (*) we'll be expecting results by then ;) > >

Dec. 1, 2014

Re: [Pharo-dev] WhatsUp from: 2014-12-01 until: 2014-12-14

by phil＠highoctane.be

On Mon, Dec 1, 2014 at 7:00 AM, <seaside(a)rmod.lille.inria.fr> wrote: > Hi! We're sending this automatic email twice a month, to give the > community an opportunity to easily know what's happening and to coordinate > efforts. Just answer informally, and feel free to spawn discussions > thereafter! > > ### Here's what I've been up to since the last WhatsUp: > Two commercial installs of a Pharo/Seaside based solution. Some tweets with the #pharo tag. > > ### What's next, until 2014-12-14 (*): > More installs. More deals. Using Mongodb more extensively for one application. Start of a new application module on business dashboarding. Documentation of our system writing using Pillar. CommandLineHandler based tool for console based administration of the system. > > (*) we'll be expecting results by then ;) > >

Dec. 1, 2014

Re: [Pharo-dev] tests coverage of minimal Pharo

by Pavel Krivanek

Right. Some tests ended with out-of-memory errors or vm crash. One problem was in a trait so I had to put all users of it on the blacklist. Cheers, -- Pavel 2014-12-01 14:21 GMT+01:00 Alejandro Infante <alejandroinfante91(a)gmail.com>: > Hapao works using method wrappers, and do some stuff for every method > execution. If Hapao use something you are instrumenting, you are start > looping endlessly. So blacklisted classes are classes you are not going to > instrument. > > But, I was trying to understand all the classes you blacklisted, and I donât > understand why you have some tests blacklisted, any reason for them? > > Cheers, > Alejandro > > On Dec 1, 2014, at 7:57 AM, Guillermo Polito <guillermopolito(a)gmail.com> > wrote: > > ignorant question: What is a black listed class? :) > > On Sun, Nov 30, 2014 at 7:21 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> > wrote: >> >> Hi, >> >> I set the job for tests coverage testing of the mimimal Pharo using Hapao: >> >> >> https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-2… >> >> To load results you should load ConfigurationOfSUnit and >> ConfigurationOfKernelTests from Pharo/SystemConfigurations repository >> into an image with Hapao. Then inspect: >> >> FLMaterializer materializeFromFileNamed: 'hapao.fuel'. >> >> Do not try to visualise it ;-) >> >> Currently blacklisted classes are: >> >> Array Association ArrayedCollection Behavior BlockClosure ByteSymbol >> ByteString ClassDescription CompiledMethod Class Dictionary >> Hapao2Package HashedCollection IdentityDictionary Integer LookupKey >> FileStream Magnitude Object ProtoObject Process ProcessLocalVariable >> ProcessorScheduler ProcessSpecificVariable RPackageOrganizer RPackage >> SmalltalkImage SequenceableCollection Set Semaphore SmallInteger >> Symbol String SourceFileArray VirtualMachine OCCompilerTest >> SortedCollectionTest DictionaryTest SetTest ArrayTest SymbolTest >> BagTest StringTest HeapTest FloatArrayTest OrderedCollectionTest >> LinkedListTest S2BasicNewStub S2BasicNewStubClass S2BasicNewStubMethod >> S2BasicNewStubPackage S2BasicNewTest S2C S2CClass S2CMethod S2CPackage >> S2Class S2ClassPlugin S2Context S2InsertBehaviorPlugin S2Lock S2Method >> S2MethodPlugin S2Package S2Plugin S2PluginTest S2PointNewPlugin >> S2Profiler S2ProfilerPlugin S2ProfilerTest S2SenderTest S2SpyStack >> S2StringNewPlugin S2TestException S2Tester S2TesterClass >> S2TesterMethod S2TesterPackage S2TesterSpy S2py S2pyA S2pyB >> S2pyDummyTest S2pySenderStub S2pySenderStubClass S2pySenderStubMethod >> S2pySenderStubPackage >> >> Cheers, >> -- Pavel >> > >

Dec. 1, 2014

Re: [Pharo-dev] merge conflict (issue validator)

by Nicolai Hess

2014-12-01 13:39 GMT+01:00 Marcus Denker <marcus.denker(a)inria.fr>: > > On 01 Dec 2014, at 11:40, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > On 29 Nov 2014, at 23:04, Nicolai Hess <nicolaihess(a)web.de> wrote: > > I don't understand this merge conflict in hte issue validation for case > 14288 <https://pharo.fogbugz.com/default.asp?14288> > I can manually load the slice and it does not show any conflicts. > > > I actually looked at it when the same time it failed with the monkye, and > I got the > same conflicts. > > I think this is a bug that might be related to MC not getting the right > file to diff sometimes > from SmalltalkHub. > > I have put it back to review needed to see if it works now. > > > This time it worked fine, I will integrate it now. > > Marcus > > Thank you.

Dec. 1, 2014

Re: [Pharo-dev] tests coverage of minimal Pharo

by Alejandro Infante

Hapao works using method wrappers, and do some stuff for every method execution. If Hapao use something you are instrumenting, you are start looping endlessly. So blacklisted classes are classes you are not going to instrument. But, I was trying to understand all the classes you blacklisted, and I donât understand why you have some tests blacklisted, any reason for them? Cheers, Alejandro > On Dec 1, 2014, at 7:57 AM, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > ignorant question: What is a black listed class? :) > > On Sun, Nov 30, 2014 at 7:21 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: > Hi, > > I set the job for tests coverage testing of the mimimal Pharo using Hapao: > > https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-2… <https://ci.inria.fr/pharo/view/4.0-Bootstrap/job/Pharo-4.0-Bootstrap-Step-2…> > > To load results you should load ConfigurationOfSUnit and > ConfigurationOfKernelTests from Pharo/SystemConfigurations repository > into an image with Hapao. Then inspect: > > FLMaterializer materializeFromFileNamed: 'hapao.fuel'. > > Do not try to visualise it ;-) > > Currently blacklisted classes are: > > Array Association ArrayedCollection Behavior BlockClosure ByteSymbol > ByteString ClassDescription CompiledMethod Class Dictionary > Hapao2Package HashedCollection IdentityDictionary Integer LookupKey > FileStream Magnitude Object ProtoObject Process ProcessLocalVariable > ProcessorScheduler ProcessSpecificVariable RPackageOrganizer RPackage > SmalltalkImage SequenceableCollection Set Semaphore SmallInteger > Symbol String SourceFileArray VirtualMachine OCCompilerTest > SortedCollectionTest DictionaryTest SetTest ArrayTest SymbolTest > BagTest StringTest HeapTest FloatArrayTest OrderedCollectionTest > LinkedListTest S2BasicNewStub S2BasicNewStubClass S2BasicNewStubMethod > S2BasicNewStubPackage S2BasicNewTest S2C S2CClass S2CMethod S2CPackage > S2Class S2ClassPlugin S2Context S2InsertBehaviorPlugin S2Lock S2Method > S2MethodPlugin S2Package S2Plugin S2PluginTest S2PointNewPlugin > S2Profiler S2ProfilerPlugin S2ProfilerTest S2SenderTest S2SpyStack > S2StringNewPlugin S2TestException S2Tester S2TesterClass > S2TesterMethod S2TesterPackage S2TesterSpy S2py S2pyA S2pyB > S2pyDummyTest S2pySenderStub S2pySenderStubClass S2pySenderStubMethod > S2pySenderStubPackage > > Cheers, > -- Pavel > >

Dec. 1, 2014