- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Transcript needs your love

by Igor Stasenko

Speaking about penetrating multiple layers.. Lemme tell you the story: One day, a brave hero (let's call him Stef :) ) decided to save the world... err improve Transcript and make it thread-safe. And everything vent well until he stumbled upon #endEntry logic, because he was unable to figure out how it is handled and where it is handled.. He asked me for help and we sat together and looked for what can be done.. After many months and fierce battles (longer that any developer would except), we finally discovered that #endEntry logic is handled .. (drumroll...) in TextMorph, as a separate case in case-statement in its #changed: method. Sure it was a long ago, and my memory could fail me, i might be completely wrong on some details, and maybe instead we were drinking ale with fairies in the pub, and there was no any fights. But that's what is fairy tale for :) -- Best regards, Igor Stasenko.

May 11, 2015

Re: [Pharo-dev] Lighthouse example throw segfault

by Alejandro Infante

> On May 11, 2015, at 4:43 PM, stepharo <stepharo(a)free.fr> wrote: > > Hi alejandro > > which image? â For the already built image, I used the version of May 9th (Build #467) and is based on Pharo 3 â For the one that I loaded the stable code using the last ConfigurationOf (commit number 13) on a Pharo4.0 image (#40611) > which version? Guess this is answered up there. > which latest vm? Iâm not sure how to get this, sending --version or --help do not work. Even though, comparing the creation date of the file of the VM, I guess that is PharoVM 421.zip from the fileserver. > > do you see a pattern :) 5 minutes ago I tried to using a different vm. Using the PharoS VM (206.zip from the pharo fileserver) I wasnât able to reproduce the error. > > Stef > > Le 11/5/15 20:37, Alejandro Infante a Ã©crit : >> Hello, >> >> When I try to open the image from Jenkins the screen goes black for 5 seconds and then it throws a segmentation fault in my Mac. I use a Macbook air with the latest stable Pharo VM. >> >> Using the ConfigurationOf I have found that Lighthouse by default set the display to work in fullscreen, and is perfectly usable, but when saving the image it is impossible to open it again (segfault). I attached the crash.dmp. >> >> If I try to disable the fullscreen before saving it, the error does not appear again. >> >> Iâm the only one capable to reproduce this? >> >> Cheers, >> Alejandro >> > > Cheers, Alejandro

May 11, 2015

Re: [Pharo-dev] Transcript needs your love

by Igor Stasenko

On 10 May 2015 at 10:23, stepharo <stepharo(a)free.fr> wrote: > > i think there is a fundamental difference between 'stream' and 'update on >>> the screen' . Choose one and stick to it. >>> We shall separate such responsibilities and NEVER ever merge them again , >>> even if it was cool, nice, soft and puffy in the past. >>> Yes, sure, we can then build the facade on top of that providing similar >>> behavior of what was in the past.. >>> >>> But if not, then it will always be something that will forever be causing >>> problem, since it is conceptually wrong and looks like attempt to cross >>> breed two different species. >>> >> <OT> >> I have no particular opinions about Transcsript, but I would like to say >> that I am very happy to have Igor back in the Squeak/Pharo/Cuis/Smalltalk >> discussions. I may not agree with everything, but I really appreciate his >> thoughtful perspective. There are a few people whose posts I will always >> read, and Igor is one of them. >> </OT> >> > Thanks Dave. I share the same feelings. > >> Dave >> >> > Guys, that was completely unnecessary. :) My problem with transcript was always a multiple layers penetration to get things done. And Cuis version is good demonstration to that (sorry, Juan): - who the heck needs APIs, protocols and overall design rules, if we can just cut through things to get to the functionality we need and put things one the screen right away without dabbling with Morphic/whatever? Because why not? Half of Squeak (and subsequently, Pharo) code is written that way anyways.. Following such development style, then i should rewrite everything in assembler, make it work blazingly fast, and who are you to criticize thing that works well and outperforms everything that ever written before? Right? What is broken, needs to be fixed. Who opposed that? I just have different than Eliot view on what is broken and consequently, what is needed to fix it. Note, that i *want* the very same behavior at the end. I want transcript that can handle immediate updates on the screen. But i want it to be async, and do not impact the performance of the system, because it is awful, when console output takes 99% of your computation resources. Sure, it may be cool for VM devs, but have you thought about rest of use cases? Because there's plenty of them, and not all of them require immediate feedback on the screen. My 'doctrine' is to have a versatile tool that suits well for many use cases, not just one. P.S. Please note, i said nothing new about Transcript that i wasn't saying couple years ago to Stef and to other people i was communicating with.. Yeah time runs fast, and not everything you want can be done, but it doesn't means that i changed my mind. I wonder, how other people feel, when they stating obvious (to their thinking), and others look at them as a doctrinal dumbass. That's how i feel. :) -- Best regards, Igor Stasenko.

May 11, 2015

Re: [Pharo-dev] On Missing Class: Why not describe error?

by Sean P. DeNigris

Sean P. DeNigris wrote > Any reason not to make it... Issue 15524: CodeImport: Better info on non-existent behavior https://pharo.fogbugz.com/default.asp?15524 Fix in inbox: SLICE-Issue-15524-CodeImport-Better-info-on-non-existent-behavior-SeanDeNigris.1 - Put which class and which label in the error message ----- Cheers, Sean -- View this message in context: http://forum.world.st/On-Missing-Class-Why-not-describe-error-tp4825681p482… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 11, 2015

Issue 15523: Code Cruft Rule Only Matches One-Liners

by Sean P. DeNigris

https://pharo.fogbugz.com/default.asp?15523 Ouch, burned by "you must match at the level of the parse tree you are altering" again... It is ridiculously easy to fall into the following trap - when rewriting, you must match at the same level that you alter the parse tree. Thus, if your rule has one statement, like "`@object setHaltOnce", you can just focus on it... Unless you want to remove it completely! Then, you are altering the parse tree one level up, so you can't just write the above... Unless you're working on a one-line method, in which case you are at the top level and can do what you want! Woah! WTH!! Because of this common pitfall, RBCodeCruftLeftInMethodsRule was only matching one-line methods (which are the only ones we test of course). I rewrote it and added some tests. Fix in inbox: SLICE-Issue-15523-Code-Cruft-Rule-Only-Matches-One-Liners-SeanDeNigris.1 - Fix and clean RBCodeCruftLeftInMethodsRule to work on methods with multiple lines - Add tests for above - Move Object halting methods into 'halting' protocol. I had originally put them in an extension protocol, but Halt is in the same package, so that doesn't make much sense! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Issue-15523-Code-Cruft-Rule-Only-Matches-One-Liners-t… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

May 11, 2015

Re: [Pharo-dev] Package comments

by stepharo

Le 11/5/15 20:10, Kasper Osterbye a Ã©crit : > Sergio Fedi and I are now working on this. > > As part of the work, we need a "default package comment", akin the the > default class comment. The class comment is inspired by CRC idea. > Translating CRC to a PRC, we suggest the following, and ask for comments > from the community. As I believe we will by the end of the year have a > inworld pillar renderer which is fairly stable, the default PRC template > could be: Coooooool :) > 'Please comment me using the following ""template"", ''inspired'' by Class > Responsibility Collaborator (CRC) design: > > !Package XXX, part of (reference to main package if one exist) I did not get " (reference to main package if one exist) " > one line description: For example, I'm xxx package, containing the hierarchy > of visitor objects. What are the public main classes? > > ;Responsibiliies > :Three sentences about my main responsibility, what I'm doing, what classes > do I offer. > ;Collaborators > :State my related packages, and which classes are the ones used from the > outside of the package. > > !!Public API > > - message one in class one > - message two in class two > - what is the way to use this package. > > One simple example is simply gorgeous. Or refer to which package is the > main package if there are several packages in play > > !!Internal Representation and Key Implementation Points. > > -Implementation Points, in particular references to classes with good class > comments.' > > Will this work? > > Best, Sergio & Kasper > > > > -- > View this message in context: http://forum.world.st/Package-comments-tp4824353p4825838.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > > >

May 11, 2015

Re: [Pharo-dev] Lighthouse example throw segfault

by stepharo

Hi alejandro which image? which version? which latest vm? do you see a pattern :) Stef Le 11/5/15 20:37, Alejandro Infante a Ã©crit : > Hello, > > When I try to open the image from Jenkins the screen goes black for 5 seconds and then it throws a segmentation fault in my Mac. I use a Macbook air with the latest stable Pharo VM. > > Using the ConfigurationOf I have found that Lighthouse by default set the display to work in fullscreen, and is perfectly usable, but when saving the image it is impossible to open it again (segfault). I attached the crash.dmp. > > If I try to disable the fullscreen before saving it, the error does not appear again. > > Iâm the only one capable to reproduce this? > > Cheers, > Alejandro >

May 11, 2015

Re: [Pharo-dev] On Missing Class: Why not describe error?

by stepharo

Yes It was on my to do to create a little addd-ons that create stupid stub classes. so that I can load broken code and do not care. Le 11/5/15 14:40, Sean P. DeNigris a Ã©crit : > Current implementation: > MethodDeclaration>>#handleMissingBehavior > "self error: ('Cannot install method in unexistent behavior {1}' format: > {(behaviorName asString)})" > > (MissingClassError > className: behaviorName asString) > signal > > Any reason not to make it: > MethodDeclaration>>#handleMissingBehavior > > (MissingClassError > className: behaviorName asString) > signal: 'Cannot install method in unexistent behavior', behaviorName > asString > ? > > It seems so obvious that I'm sure I must be missing something important! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/On-Missing-Class-Why-not-describe-error-tp4825681.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. > >

May 11, 2015

Re: [Pharo-dev] Transcript needs your love

by Alain Rastoul

Le 10/05/2015 13:15, Esteban Lorenzano a Ã©crit : > >> On 10 May 2015, at 13:10, stepharo <stepharo(a)free.fr> wrote: >> >> Why we cannot use the of Juan? >> >> > > you can type in it, make do it, etc. (just like now) > >> Hi Esteban, did you try it in pharo ? It took me some time to read this whole thread yesterday evening back from WE, wow ... lot of posts... and make a test today. (thanks to Clement explanations, the issue is more clear now. Indeed it's a pity that vm development cannot be done in pharo too, sometimes I really would like to have a look at it when I have questions on internals). I tried to import Juan's source from the fogbugz post in pharo, renaming Tranncript to CuisTranscript, TranscriptMorph to CuisTranscriptMorph etc. finally after some big red-death morph, and now a weird non-correctly refreshing transcript I wonder how good this solution fit in pharo morphic world ? It is somewhat hooked to morphic at low level and I had to import some old deprecated methods from squeak - since cuis doesn't start on my pc, I took them from squeak but may be this is not good. Also it will not solve the Elliot's editable and styling requirement. (Editable should be possible, but styling...? no clue) -- Regards, Alain

May 11, 2015

Lighthouse example throw segfault

by Alejandro Infante

Hello, When I try to open the image from Jenkins the screen goes black for 5 seconds and then it throws a segmentation fault in my Mac. I use a Macbook air with the latest stable Pharo VM. Using the ConfigurationOf I have found that Lighthouse by default set the display to work in fullscreen, and is perfectly usable, but when saving the image it is impossible to open it again (segfault). I attached the crash.dmp. If I try to disable the fullscreen before saving it, the error does not appear again. Iâm the only one capable to reproduce this? Cheers, Alejandro

May 11, 2015