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

Re: [Pharo-dev] [pharo-project/pharo-core] 8be654: 40392

by Ben Coman

> > Log Message: > ----------- > 40392 > > 14546 Failed inherited tests should show home class (in TestRunner, like the debugger) > https://pharo.fogbugz.com/f/cases/14546 > Thanks for this Nicolai. I only logged the idea yesterday, and here it is integrated overnight before I get home from work to review it. The yellow highlight in the attached picture shows the new feature. cheers -ben

Dec. 1, 2014

Re: [Pharo-dev] SmalltalkHub bugs & hangs :-(

by Andreas Wacknitz

Am 01.12.14 12:34, schrieb kilon alios: > No of course not. That would have been a deal braker. > > Personally I prefer using Sourcetree to browser history of commits > than using the pharo on board tools. Pharo is good on that respect, > but sourcetree is better Alas Sourcetree is only available for Windows and Mac OSX. Non-portable programs die with their system. Closed source programs die with their company. That's one of the reasons I like Pharo: it's open source and I was able to port the VM to my prefered OS (Ok, NativeBoost is still missing (not working) but the rest is doing fine). Furthermore I really enjoy Squeak's and Pharo ecosystem. The more tools and frameworks are inside the less they depend on the underlying OS. Andreas > and smartgit I have used in the past. It also has nice visualisation > for branches , merges etc. I have not shown these features in my video > tutorial as I was planning to show them to a separate tutorial. I > would not mind bypassing monticello completely since its usage is > unnecessary at least to me with all these git tools that one can > download and use for free. The same is true for other IDEs out there , > generally people prefer using dedicate tools. > > Usually dedicate tools are hard to beat this is why I believe > modularising Pharo is extremely important as will make integrating > external tools way easier. > > I think however that Roassal can be used to visualise in similar way > the history as Sourcetree does. So pharo is not far from it but as > always its a matter of someone doing the hard work. > > On Mon, Dec 1, 2014 at 12:21 PM, Hilaire <hilaire(a)drgeo.eu > <mailto:hilaire@drgeo.eu>> wrote: > > Le 27/11/2014 11:29, kilon alios a Ã©crit : > > My personal opinion on Github and Pharo is that it already works great > > with Pharo. The workflow with filetree is exactly the same as other > > languages that gives the added advantage that you can use all the > > powerful tools you use with other languages for commiting to git and > > github. I have not experienced any kind of issue of problem > using github > > with Pharo nor my experience has been any worse than other > languages. > > > > With git, don't you lost the capability to browse the history of > changes > in your code? > > Hilaire > > > -- > Dr. Geo - http://drgeo.eu > iStoa - http://istoa.drgeo.eu > > >

Dec. 1, 2014

Re: [Pharo-dev] [Moose-dev] Woden processor occupation and text highlight

by Yuriy Tymchuk

> On 01 Dec 2014, at 16:14, Ronie Salgado <roniesalg(a)gmail.com> wrote: > > It was the case in Roassal2 yes. This happens when the the window was constantly refreshing, > That is not a problem of Woden. It has to be constantly refreshing. > > But it is a problem for Woden-Roassal... > > I guess, that the problem could be worse if I enabled vsync in the SDL2 backend (it blocks). Ok, but can we make this work better? :) > > > 2014-12-01 12:09 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>>: > > Woden and Roassal3D have a problem that when the 3D window is shown, text highlighting is not working. Usually itâs not a big deal, but Rubric writes white text on white background :). I think a problem like that was already in Roassal2 and maybe someone remembers how to solve that? > > It was the case in Roassal2 yes. This happens when the the window was constantly refreshing, thus no time left for the process behind the text hilighting. Maybe there is the same problem. You can have a look at the TRMorph class. > > Cheers, > Alexandre >

Dec. 1, 2014

Re: [Pharo-dev] [Moose-dev] Woden processor occupation and text highlight

by Ronie Salgado

> > It was the case in Roassal2 yes. This happens when the the window was > constantly refreshing, That is not a problem of Woden. It has to be constantly refreshing. But it is a problem for Woden-Roassal... I guess, that the problem could be worse if I enabled vsync in the SDL2 backend (it blocks). 2014-12-01 12:09 GMT-03:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > > Woden and Roassal3D have a problem that when the 3D window is shown, > text highlighting is not working. Usually itâs not a big deal, but Rubric > writes white text on white background :). I think a problem like that was > already in Roassal2 and maybe someone remembers how to solve that? > > It was the case in Roassal2 yes. This happens when the the window was > constantly refreshing, thus no time left for the process behind the text > hilighting. Maybe there is the same problem. You can have a look at the > TRMorph class. > > Cheers, > Alexandre >

Dec. 1, 2014

Re: [Pharo-dev] [Moose-dev] Woden processor occupation and text highlight

by Alexandre Bergel

> Woden and Roassal3D have a problem that when the 3D window is shown, text highlighting is not working. Usually itâs not a big deal, but Rubric writes white text on white background :). I think a problem like that was already in Roassal2 and maybe someone remembers how to solve that? It was the case in Roassal2 yes. This happens when the the window was constantly refreshing, thus no time left for the process behind the text hilighting. Maybe there is the same problem. You can have a look at the TRMorph class. Cheers, Alexandre

Dec. 1, 2014

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

by Alexandre Bergel

> Would Hapao benefit from using reflectivity as it's intercession framework instead of using method wrappers? Maybe in such a way it can also instrument classes such as Array, Objectâ¦ May be. But I am wondering whether it will really solve the problem. I guess reflectivity is using the same kind of transformation as we do. In Java, the JVM provides an interface, to which you can connect a debugger. With such interface, you can literally profile anything. Alexandre > > On Mon, Dec 1, 2014 at 2:34 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com <mailto:pavel.krivanek@gmail.com>> wrote: > 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 <mailto:alejandroinfante91@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 <mailto:guillermopolito@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

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

by Guillermo Polito

Would Hapao benefit from using reflectivity as it's intercession framework instead of using method wrappers? Maybe in such a way it can also instrument classes such as Array, Object... On Mon, Dec 1, 2014 at 2:34 PM, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > 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] Woden processor occupation and text highlight

by Tudor Girba

I think it is fine to keep the discussions either on the Pharo or on the Moose mailing list :). Doru On Mon, Dec 1, 2014 at 3:39 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi, > > first of all let me know where I can write questions about Woden (because > I have not seen a lot of activity around it in any chat). > > Woden and Roassal3D have a problem that when the 3D window is shown, text > highlighting is not working. Usually itâs not a big deal, but Rubric writes > white text on white background :). I think a problem like that was already > in Roassal2 and maybe someone remembers how to solve that? > > Uko > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 1, 2014

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

by Tudor Girba

There is a GT-InspectorExtensions-Woden package in the GT repository. Doru On Mon, Dec 1, 2014 at 3:39 PM, Ronie Salgado <roniesalg(a)gmail.com> wrote: > 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 >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 1, 2014

Woden processor occupation and text highlight

by Yuriy Tymchuk

Hi, first of all let me know where I can write questions about Woden (because I have not seen a lot of activity around it in any chat). Woden and Roassal3D have a problem that when the 3D window is shown, text highlighting is not working. Usually itâs not a big deal, but Rubric writes white text on white background :). I think a problem like that was already in Roassal2 and maybe someone remembers how to solve that? Uko

Dec. 1, 2014