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

Re: [Pharo-dev] Grease conflicts #packages with RPackage

by Stephan Eggermont

Stef wrote: >The real problem is that a CLASS now responds to the packages message. SUnitAPIDocumentation also implements packages class-side. If I try to add a instance side method #bla I get a debugger (but the method is added). Searching for implementors then also returns a debugger. I assume this problem wasnât seen as the classes implementing packages class-side donât have instance side behavior. The classes implementing packages class-side are SUnitAPIDocumentation AnnouncementsAPIDocumentation HelpAPIDocumentation ProfStefAPIHelp They all return an array of package name strings Stephan

Dec. 3, 2013

Re: [Pharo-dev] NativeBoost String Handling Bug?

by Benjamin

I testify, there are 2 conflicts Ben On 03 Dec 2013, at 12:44, Igor Stasenko <siguctua(a)gmail.com> wrote: > apparently i was looking at wrong place, and according to report there's merge conflict. > why? because i merged everything before commit. > > > > On 3 December 2013 12:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Igor > > where do you get this information? > Because I see > https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/3549//artifact/vali… > and it is different. > > stef > > On Dec 3, 2013, at 11:59 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> i have no idea, but following is not related to what changes i did: >> >> ./pharo Pharo.image update --from-file=updates30.staged >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> VersionnerProjectToolBar>>update (MBUpdateDevCommand is Undeclared) >> >> VersionnerProjectToolBar>>update (update is Undeclared) >> >> MBAddDescriptionCommandTest>>testExecute (MBAddDescriptionCommand is Undeclared) >> >> MBConfigurationInfoTest>>testInitialization (ConfigurationOfVersionner is Undeclared) >> >> MBAbstractVersionInfo>>cmdSetCurrentVersion (MBSetCurrentVersionCommand is Undeclared) >> >> MTProject>>addDependentProject:from:withVersion:loads:(repository is shadowed) >> >> >> >> On 3 December 2013 10:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> You know what? >> It will not be integrated because apparently the monkey tagged it as invalid. >> >> I have no idea why. I hate this automatic down grading. May be we should have a different tags to make the difference >> between >> >> work needed = nothing was done or something but it was never in the state where we could think it should be integrated >> was integration ready = it was ready but something happen >> >> Stef >> >> >> >> > Igor Stasenko wrote >> >> if yes then i think we can finally close the bug entry). >> > >> > I updated the issue and made your packages into a slice: >> > https://pharo.fogbugz.com/default.asp?7542 >> > SLICE-Issue-7542-NB-system-example-SeanDeNigris.1 >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: http://forum.world.st/NativeBoost-String-Handling-Bug-tp4726860p4726895.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >> >> >> >> >> >> -- >> Best regards, >> Igor Stasenko. > > > > > -- > Best regards, > Igor Stasenko.

Dec. 3, 2013

Re: [Pharo-dev] Roassal 3d now support textures

by StÃ©phane Ducasse

did you move some functionality (to the place they belong) to NBOpenGL? Because this should be done and JB has already spent time on that. Stef > hi! > > Just to keep you up to date with the Roassal 3d effort. > https://www.facebook.com/photo.php?fbid=547995685287033&set=a.5299979037534… > > Cheers, > Alexandre > > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > >

Dec. 3, 2013

Re: [Pharo-dev] NativeBoost String Handling Bug?

by Igor Stasenko

apparently i was looking at wrong place, and according to report there's merge conflict. why? because i merged everything before commit. On 3 December 2013 12:09, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > Igor > > where do you get this information? > Because I see > > https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/3549//artifact/vali… > and it is different. > > stef > > On Dec 3, 2013, at 11:59 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > i have no idea, but following is not related to what changes i did: > > ./pharo Pharo.image update --from-file=updates30.staged > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (MBUpdateDevCommand is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > MBAddDescriptionCommandTest>>testExecute (MBAddDescriptionCommand is Undeclared) > > MBConfigurationInfoTest>>testInitialization (ConfigurationOfVersionner is Undeclared) > > MBAbstractVersionInfo>>cmdSetCurrentVersion (MBSetCurrentVersionCommand is Undeclared) > > MTProject>>addDependentProject:from:withVersion:loads:(repository is shadowed) > > > > > On 3 December 2013 10:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > >> You know what? >> It will not be integrated because apparently the monkey tagged it as >> invalid. >> >> I have no idea why. I hate this automatic down grading. May be we should >> have a different tags to make the difference >> between >> >> work needed = nothing was done or something but it was never in >> the state where we could think it should be integrated >> was integration ready = it was ready but something happen >> >> Stef >> >> >> >> > Igor Stasenko wrote >> >> if yes then i think we can finally close the bug entry). >> > >> > I updated the issue and made your packages into a slice: >> > https://pharo.fogbugz.com/default.asp?7542 >> > SLICE-Issue-7542-NB-system-example-SeanDeNigris.1 >> > >> > >> > >> > ----- >> > Cheers, >> > Sean >> > -- >> > View this message in context: >> http://forum.world.st/NativeBoost-String-Handling-Bug-tp4726860p4726895.html >> > Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> > >> >> >> > > > -- > Best regards, > Igor Stasenko. > > > -- Best regards, Igor Stasenko.

Dec. 3, 2013

Re: [Pharo-dev] Versionner Impressions

by Sean P. DeNigris

Yea, in 3.0 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Versionner-Impressions-tp4726902p4726960.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 3, 2013

Re: [Pharo-dev] NativeBoost String Handling Bug?

by StÃ©phane Ducasse

Igor where do you get this information? Because I see https://ci.inria.fr/pharo/job/Pharo-3.0-Issue-Validator/3549//artifact/vali… and it is different. stef On Dec 3, 2013, at 11:59 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > i have no idea, but following is not related to what changes i did: > > ./pharo Pharo.image update --from-file=updates30.staged > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > VersionnerProjectToolBar>>update (MBUpdateDevCommand is Undeclared) > > VersionnerProjectToolBar>>update (update is Undeclared) > > MBAddDescriptionCommandTest>>testExecute (MBAddDescriptionCommand is Undeclared) > > MBConfigurationInfoTest>>testInitialization (ConfigurationOfVersionner is Undeclared) > > MBAbstractVersionInfo>>cmdSetCurrentVersion (MBSetCurrentVersionCommand is Undeclared) > > MTProject>>addDependentProject:from:withVersion:loads:(repository is shadowed) > > > > On 3 December 2013 10:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > You know what? > It will not be integrated because apparently the monkey tagged it as invalid. > > I have no idea why. I hate this automatic down grading. May be we should have a different tags to make the difference > between > > work needed = nothing was done or something but it was never in the state where we could think it should be integrated > was integration ready = it was ready but something happen > > Stef > > > > > Igor Stasenko wrote > >> if yes then i think we can finally close the bug entry). > > > > I updated the issue and made your packages into a slice: > > https://pharo.fogbugz.com/default.asp?7542 > > SLICE-Issue-7542-NB-system-example-SeanDeNigris.1 > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: http://forum.world.st/NativeBoost-String-Handling-Bug-tp4726860p4726895.html > > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > > > > > > > -- > Best regards, > Igor Stasenko.

Dec. 3, 2013

Re: [Pharo-dev] transcript is plain bad

by StÃ©phane Ducasse

Sure have a look at SystemLogger http://smalltalkhub.com/#!/~StephaneDucasse/SystemLogger I did not check the changes made by norbert. I will work on it during xmas. Stef On Dec 3, 2013, at 11:47 AM, "phil(a)highoctane.be" <phil(a)highoctane.be> wrote: > What's wrong with Strings anyway? But yeah, I understand your point. > > What I have done for my own stuff is to have a TLog aspect with info, debug, error, warn and, well, Strings. But double dispatch could take care of that, like printOn:, storeOn: etc. > > Do you have some code that I can look at? > > TLog>>info: anObject > > anObject logOn: Logger default info. > > > Phil > > > > On Tue, Dec 3, 2013 at 11:27 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Dec 3, 2013, at 10:34 AM, phil(a)highoctane.be wrote: > >> I am working on this one. >> >> Don't kill the transcript, it is useful when working without a console. > > I will not kill it but it will just be dull outputer for my logger. In fact I'm missing a user interface (the idea was to build it with fernando) and right now > the transcript just displays the printstring of my log objects. So I can even control what I want to output. > more important I can filter the log ojbjects. For example I need to know when my framework finish to deal with a class and now this is mix with the compiler > logherea > >> Now, adding the features you mention is not hard. And the top right triangle menu of Transcript could get a clue from the Workspace one with a Save As entry. > > No i just DO NOT WANT STRINGS!!!! > >> I once had an issue with things like (out of the top of my head) FileStream stdout nextPutAll: 'hello'; cr; flush. when I went headless. The image worked at one point and the froze/locked. Until this is sorted out in full, keep a transcript handy. >> >> I gave the image to Guille who sent me back a version "unlocked" with Oz, but it still dies on Windows for example. Weird. >> >> Phil >> >> >> >> --- >> Philippe Back >> Dramatic Performance Improvements >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 >> Mail:phil@highoctane.be | Web: http://philippeback.eu >> Blog: http://philippeback.be | Twitter: @philippeback >> Youtube: http://www.youtube.com/user/philippeback/videos >> >> High Octane SPRL >> rue cour Boisacq 101 | 1301 Bierges | Belgium >> >> Pharo Consortium Member - http://consortium.pharo.org/ >> Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com >> Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller >> >> >> >> >> On Tue, Dec 3, 2013 at 10:10 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> On Dec 2, 2013, at 8:46 PM, phil(a)highoctane.be wrote: >> >>> And missing a ton of methods. >>> >>> Teh StackInterpreterSimulator is agreeing with this statement. >> >> send us the ones that are missing. >> >> Please note that we should kill the transcript in the future because this is a ^%$&*((^%$* outdated way to manage >> feedback: plain string, close the window data is lost, limited in length, no filteringâ¦.. >> bad bad bad does not scale horrible and so frustrating. I will not send you the current transcript I have because I deal with private code >> but this does not work. >> >> Stef >>> >>> >>> >>> >>> >>> On Mon, Dec 2, 2013 at 8:05 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> yes, the transcript is ThreadSafeTranscript >>> >>> >>> On Mon, Dec 2, 2013 at 8:00 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> Buy the way, is absence of Transcript class - ok? >>> >>> I know how it all works now, but is it ok? :) >>> >>> uko >>> >>> >>> On 02 Dec 2013, at 19:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> yes, please :) >>>> >>>> >>>> On Mon, Dec 2, 2013 at 7:56 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> > The return of the toothpick is near. o/ >>>> >>>> No I will finish my logger :) >>>> >>>> Stef >>>> >>>> >>> >>> >>> >> >> > >

Dec. 3, 2013

Re: [Pharo-dev] Responsible development

by StÃ©phane Ducasse

>> fork neither. > > It should not freeze your image anymore, only its own thread I'm not convinced. Because if you get a thread per nautilus to me it just introduces potentially more problems. Just forking a process in general does not solve problem. Also debugging can be harder when you have different threads executing the same code. Not freezing is just that you do not damage the main ui thread. > > Ben > >> >>> (why cache by the way ?) >> >> I thought the discussion was about speeding up nautilus when performing start up actions. >>> >>> Ben >>> >>>> >>>> Stef >

Dec. 3, 2013

Re: [Pharo-dev] transcript is plain bad

by Norbert Hartl

Am 03.12.2013 um 11:47 schrieb phil(a)highoctane.be: > What's wrong with Strings anyway? But yeah, I understand your point. > Strings are fine when you donât need specific behavior oder structure of your log messages anymore. A conversion to string should in most cases happen as late as possible. A log entry can still serve other purposes than represent an custom formatted string thing. Think about making all the exception handling in away that it can only signal strings. The same you feel now you would lose here is similar to the gain youâll get making log messages objects ;) It is just that you are used to objects when it comes to exceptions and you are used to strings when comes to log messages. The former being a good idea the latter not. > What I have done for my own stuff is to have a TLog aspect with info, debug, error, warn and, well, Strings. But double dispatch could take care of that, like printOn:, storeOn: etc. > > Do you have some code that I can look at? > http://smalltalkhub.com/#!/~StephaneDucasse/SystemLogger Norbert > TLog>>info: anObject > > anObject logOn: Logger default info. > > > Phil > > > > On Tue, Dec 3, 2013 at 11:27 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > On Dec 3, 2013, at 10:34 AM, phil(a)highoctane.be wrote: > >> I am working on this one. >> >> Don't kill the transcript, it is useful when working without a console. > > I will not kill it but it will just be dull outputer for my logger. In fact I'm missing a user interface (the idea was to build it with fernando) and right now > the transcript just displays the printstring of my log objects. So I can even control what I want to output. > more important I can filter the log ojbjects. For example I need to know when my framework finish to deal with a class and now this is mix with the compiler > logherea > >> Now, adding the features you mention is not hard. And the top right triangle menu of Transcript could get a clue from the Workspace one with a Save As entry. > > No i just DO NOT WANT STRINGS!!!! > >> I once had an issue with things like (out of the top of my head) FileStream stdout nextPutAll: 'hello'; cr; flush. when I went headless. The image worked at one point and the froze/locked. Until this is sorted out in full, keep a transcript handy. >> >> I gave the image to Guille who sent me back a version "unlocked" with Oz, but it still dies on Windows for example. Weird. >> >> Phil >> >> >> >> --- >> Philippe Back >> Dramatic Performance Improvements >> Mob: +32(0) 478 650 140 | Fax: +32 (0) 70 408 027 >> Mail:phil@highoctane.be | Web: http://philippeback.eu >> Blog: http://philippeback.be | Twitter: @philippeback >> Youtube: http://www.youtube.com/user/philippeback/videos >> >> High Octane SPRL >> rue cour Boisacq 101 | 1301 Bierges | Belgium >> >> Pharo Consortium Member - http://consortium.pharo.org/ >> Featured on the Software Process and Measurement Cast - http://spamcast.libsyn.com >> Sparx Systems Enterprise Architect and Ability Engineering EADocX Value Added Reseller >> >> >> >> >> On Tue, Dec 3, 2013 at 10:10 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> On Dec 2, 2013, at 8:46 PM, phil(a)highoctane.be wrote: >> >>> And missing a ton of methods. >>> >>> Teh StackInterpreterSimulator is agreeing with this statement. >> >> send us the ones that are missing. >> >> Please note that we should kill the transcript in the future because this is a ^%$&*((^%$* outdated way to manage >> feedback: plain string, close the window data is lost, limited in length, no filteringâ¦.. >> bad bad bad does not scale horrible and so frustrating. I will not send you the current transcript I have because I deal with private code >> but this does not work. >> >> Stef >>> >>> >>> >>> >>> >>> On Mon, Dec 2, 2013 at 8:05 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> yes, the transcript is ThreadSafeTranscript >>> >>> >>> On Mon, Dec 2, 2013 at 8:00 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >>> Buy the way, is absence of Transcript class - ok? >>> >>> I know how it all works now, but is it ok? :) >>> >>> uko >>> >>> >>> On 02 Dec 2013, at 19:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> yes, please :) >>>> >>>> >>>> On Mon, Dec 2, 2013 at 7:56 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>>> >>>> > The return of the toothpick is near. o/ >>>> >>>> No I will finish my logger :) >>>> >>>> Stef >>>> >>>> >>> >>> >>> >> >> > >

Dec. 3, 2013

Re: [Pharo-dev] NativeBoost String Handling Bug?

by Igor Stasenko

i have no idea, but following is not related to what changes i did: ./pharo Pharo.image update --from-file=updates30.staged VersionnerProjectToolBar>>update (update is Undeclared) VersionnerProjectToolBar>>update (update is Undeclared) VersionnerProjectToolBar>>update (update is Undeclared) VersionnerProjectToolBar>>update (update is Undeclared) VersionnerProjectToolBar>>update (MBUpdateDevCommand is Undeclared) VersionnerProjectToolBar>>update (update is Undeclared) MBAddDescriptionCommandTest>>testExecute (MBAddDescriptionCommand is Undeclared) MBConfigurationInfoTest>>testInitialization (ConfigurationOfVersionner is Undeclared) MBAbstractVersionInfo>>cmdSetCurrentVersion (MBSetCurrentVersionCommand is Undeclared) MTProject>>addDependentProject:from:withVersion:loads:(repository is shadowed) On 3 December 2013 10:17, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > You know what? > It will not be integrated because apparently the monkey tagged it as > invalid. > > I have no idea why. I hate this automatic down grading. May be we should > have a different tags to make the difference > between > > work needed = nothing was done or something but it was never in > the state where we could think it should be integrated > was integration ready = it was ready but something happen > > Stef > > > > > Igor Stasenko wrote > >> if yes then i think we can finally close the bug entry). > > > > I updated the issue and made your packages into a slice: > > https://pharo.fogbugz.com/default.asp?7542 > > SLICE-Issue-7542-NB-system-example-SeanDeNigris.1 > > > > > > > > ----- > > Cheers, > > Sean > > -- > > View this message in context: > http://forum.world.st/NativeBoost-String-Handling-Bug-tp4726860p4726895.html > > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > > > > > -- Best regards, Igor Stasenko.

Dec. 3, 2013