January 2012 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Speeding up Finder string search

by Stefan Marr

Hi: On 17 Jan 2012, at 09:47, Mariano Martinez Peck wrote: > Stefan, another approach would be to store the source code in the compiled method trailer. Looks like everything is there already, but it does not seem to work stable enough. With the code below, this should work: (do not apply the change to getSourceFromFile!!) ------------- |trailer source m | m := (Gofer>>#load). trailer := m trailer. source := m getSource. trailer sourceCode: source. m recompileWithTrailer: trailer. ------------- Here the code: ------------- !Behavior methodsFor: 'compiling' stamp: 'StefanMarr 1/17/2012 15:14' prior: 82391250! recompile: selector from: oldClass withNewTrailer: trailer "Compile the method associated with selector in the receiver's method dictionary." "ar 7/10/1999: Use oldClass compiledMethodAt: not self compiledMethodAt:" | method methodNode | method := oldClass compiledMethodAt: selector. methodNode := self compilerClass new compile: (oldClass sourceCodeAt: selector) in: self notifying: nil ifFail: [^ self]. "Assume OK after proceed from SyntaxError" selector == methodNode selector ifFalse: [self error: 'selector changed!!']. self basicAddSelector: selector withMethod: (methodNode generate: trailer). ! ! !Behavior methodsFor: 'compiling' stamp: 'StefanMarr 1/17/2012 15:15' prior: 82391969! recompile: selector from: oldClass | method | method := oldClass compiledMethodAt: selector. self recompile: selector from: oldClass withNewTrailer: method trailer. ! ! !CompiledMethod methodsFor: 'as yet unclassified' stamp: 'StefanMarr 1/17/2012 15:16' prior: 82392229! recompileWithTrailer: trailer self methodClass recompile: self selector from: self methodClass withNewTrailer: trailer.! ! !CompiledMethod methodsFor: 'source code management' stamp: 'StefanMarr 1/17/2012 15:23' prior: 68352220! getSourceFromFile "Read the source code from file, determining source file index and file position from the last 3 bytes of this method." | position source trailer | trailer := self trailer. source := trailer sourceCode. source ifNotNil: [ ^ source ]. (position := self filePosition) = 0 ifTrue: [^ nil]. source := (RemoteString newFileNumber: self fileIndex position: position) string. trailer sourceCode: source. self recompileWithTrailer: trailer. ^ source.! ! ------------- This is unfortunately undebuggable. At least I do not get a debugger (which seems logical if there is something going wrong and recurses in getSource...) Good that we have a stratified system. Best regards Stefan > > PS: I will interested if you do it :) In return, I would really appreciate if you could learn a bit about etiquette and quoting http://www.gweep.ca/~edmonds/usenet/ml-etiquette.html#SECTION00090000000000… And I am apparently not the only one who would like that. See the recent reference to http://emailcharter.org/ -- Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525

Jan. 17, 2012

Re: [Pharo-project] Scat - Public Release and announcement

by Bernat Romagosa

Hi Ralph, I'm sorry I took so long to answer, we've been quite busy here... If you decide to work on top of what's already been ported, you can rely on us for any questions you may have, no worries. If you go for the original Scratch code, I guess we could also help you on portability and architecture-related questions. We know the name is a bit unfortunate... it was chosen after scat singing<http://en.wikipedia.org/wiki/Scat_singing> without being aware the word had other not-so-educational meanings. Anyway, any trouble you may have understanding the code, you can use our mailing list at scat-project(a)googlegroups.com to communicate with us and we'll gladly try to help you, although I have to admit there are parts of the code that we don't even begin to understand and probably not even their author does anymore... Good luck! Bernat. 2011/12/22 Ralph Boland <rpboland(a)gmail.com> > Bernat Romagosa <tibabenfortlapalanca@...> writes: > > > > > > > Hi list, > > > > Joan GÃ¼ell and I have been working on Scat -the Scratch port to > Pharo- quite a > lot recently. We wanted to push it to a point where we could release the > first > reasonably working version, which we've just managed today. > > > > > > Please take a look at the release announcement (which should be read in > a bit > of a humorous tone), in which we explain what's up with the project and > what > future is left for it. > > > > > > > > For the tl;dr version, please read: > > > > > > Many things are working, many aren't, but the state of the project > allows us > to move into more interesting stuff based on the graphic programming > metaphor. > > > > Scat is a time-consuming, brain-smashing, life sucking-project. > > We no longer will be maintaining this massive unmaintainable code. > > Suddenly: free time for other projects! > > > > > > Cheers everyone! > > > > -- Bernat Romagosa. > > > > > > I do not wish to take over the Scat project but I am interested in helping > bringing it forward. My interest is in only a portion of Scat. As an > example > of what I want to do consider the "Enchanting" project that uses Scratch to > program the Legos Mindstorms toy robot. Enchanting uses a major portion of > Scratch but some of the interface is replaced by the interface needed by > Enchanting. I am interested in refactoring Scratch (now Scat) so that > projects > such as Enchanting can use the lower level stuff it needs but add its own > stuff, > particularly the GUI part. > This is what I will need to do for the projects, not add things on top of > Scratch (Scat) but on top of (say) 80% of Scat. I have my own projects > that I > want to do someday that would similarly be built on top of a portion of > Scat. > > Ideally I would like someone or some group to take over Scat who could > oversee > work that we could agree that I can do and ideally that work would relate > to the > part of Scat I am interested in. > > So can you place my name as a contact person by anyone taking over Scat. > > Lastly I encourage changing the name of Scat. > > Sincerely, > > Ralph Boland > > > -- Bernat Romagosa.

Jan. 17, 2012

Re: [Pharo-project] Styling in Inspector

by Guillermo Polito

Hmm, true :) :P. shoutAboutToStyle: aPluggableShoutMorphOrView aPluggableShoutMorphOrView getText = self contents ifTrue: [ ^false ]. aPluggableShoutMorphOrView classOrMetaClass: self object class. ^ true shoutAboutToStyle: aPluggableShoutMorphOrView aPluggableShoutMorphOrView getTextSelector == #trash ifFalse: [ ^false ]. aPluggableShoutMorphOrView classOrMetaClass: self object class. ^ true Here I've two solutions but no one pleases me... Maybe shoutAboutToStyle: aPluggableShoutMorphOrView aPluggableShoutMorphOrView getTextSelector == *self trashSelector*ifFalse: [ ^false ]. aPluggableShoutMorphOrView classOrMetaClass: self object class. ^ true And then use #trashSelector on UIManager? On Fri, Jan 13, 2012 at 7:01 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > > I added the following method to inspector and styling turned on: > > > > shoutAboutToStyle: aPluggableShoutMorphOrView > > ^ true > > > > Should we add it? > > Maybe you also want to set the class context so that it doesn't > highlight variable references as errors? > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > >

Jan. 17, 2012

Re: [Pharo-project] First steps making OB work in 1.4

by Esteban Lorenzano

great guille! El 17/01/2012, a las 1:19p.m., Guillermo Polito escribiÃ³: > Hi! > > I've been working the last days in making OB work in pharo 1.4. I updated several deprecations like method reference and stuff and discovered some bugs that I've already published in: > > http://code.google.com/p/pharo/issues/detail?id=5189&q=milestone%3D1.4&cols… > http://code.google.com/p/pharo/issues/detail?id=5183&q=milestone%3D1.4&cols… > > I've already proposed some fixes for them, but if anyone can have a look too I'll feel better :). > Those fixes are needed in order to load OB. Meanwhile, you can also have some patches from the cs and fileout I attach. > > What's working now? OB + OCompletion + Shout + Sunit integration. > > So, It's everything but Refactoring browser, which is a little more difficult since there is another RB version loaded in the image :P. > > To load it (after integrating the patches): > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfOmniBrowser'; > load. > > (ConfigurationOfOmniBrowser project version: #stable) load: #( 'Core Tests' 'OCompletion Tests' ) , #( 'Core' 'OB-SUnitIntegration' 'OB-Shout' 'OCForOB'). > > Cheers, > Guille > <pluggable list morph fix.1.cs><Slider-setValue.st>

Jan. 17, 2012

[Pharo-project] First steps making OB work in 1.4

by Guillermo Polito

Hi! I've been working the last days in making OB work in pharo 1.4. I updated several deprecations like method reference and stuff and discovered some bugs that I've already published in: http://code.google.com/p/pharo/issues/detail?id=5189&q=milestone%3D1.4&cols… http://code.google.com/p/pharo/issues/detail?id=5183&q=milestone%3D1.4&cols… I've already proposed some fixes for them, but if anyone can have a look too I'll feel better :). Those fixes are needed in order to load OB. Meanwhile, you can also have some patches from the cs and fileout I attach. What's working now? OB + OCompletion + Shout + Sunit integration. So, It's everything but Refactoring browser, which is a little more difficult since there is another RB version loaded in the image :P. To load it (after integrating the patches): Gofer it squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfOmniBrowser'; load. (ConfigurationOfOmniBrowser project version: #stable) load: #( 'Core Tests' 'OCompletion Tests' ) , #( 'Core' 'OB-SUnitIntegration' 'OB-Shout' 'OCForOB'). Cheers, Guille

Jan. 17, 2012

Re: [Pharo-project] Squeaksource Mirror Q&A

by Alexandre Bergel

> Friendler configuration / user interface / having it in the core image / ...: I am all for it, but I cannot dedicate the time to this right now. All help is welcome and highly appreciated. I guess that some of you must be much more knowledgeable at preferences settings/user interfaces et al. so what would take you 10 minutes would take me a day ... We will announce very soon Versionner, a GUI to manage software versions, based on Metacello. Having a support for the mirror is definitely something valuable we will look into Alexandre

Jan. 17, 2012

Re: [Pharo-project] New IDE alternative (was Misc. newbie questions)

by StÃ©phane Ducasse

> image, more like construct a tent and tear it down. (It makes me angry > that I can sometimes feel more productive writing Ruby in Emacs than > in Squeak/Pharo! Why can I not have BOTH a world-class text editor AND > live in an image (when I choose to)?)) This is why I want Coral. Stef

Jan. 17, 2012

[Pharo-project] Squeaksource Mirror Q&A

by Johan Fabry

Hi All, Alex notified me that there were some mails flying around here about the squeaksource mirror. I'm usually not on this mailing list because of its high volume. I'd like to gather some questions that have been raised in the last few days (thanks Nabble!) and give answers / share my thoughts. I'll try to keep it brief. - How to use the mirror. If you don't know or tend to forget, just point a web browser at http://dsal.cl/squeaksource Everything is explained there. Write the URL on a post-it, add it to your browers favorites or whatever ;-) Just remember http://dsal.cl/squeaksource - Mirror not complete: It is supposed to be a full mirror of the public packages on Squeaksource. We are using wget to copy everything over. If you know of a project that misses packages, please send me a mail (personally, not to the list is best I guess) and we will try to debug the issue. - Pharo 1.4 / ObjectAsMethodWrapper issues: The redirect package was written for 1.3, it uses ObjectAsMethodWrapper (i.e. method wrappers). I don't know why ObjectAsMethodWrapper (apparently) is no longer in 1.4 but I would highly recommend including it as it is a very useful package. I thought even the profiler used it. In any case, I welcome any contributions on how to make it work for 1.4 - Friendler configuration / user interface / having it in the core image / ...: I am all for it, but I cannot dedicate the time to this right now. All help is welcome and highly appreciated. I guess that some of you must be much more knowledgeable at preferences settings/user interfaces et al. so what would take you 10 minutes would take me a day ... I subscribed to the list now BTW so any comments/questions simply hit reply :-) ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Jan. 17, 2012

Re: [Pharo-project] New IDE alternative (was Misc. newbie questions)

by Frank Shearar

On 17 January 2012 03:20, blake <dsblakewatson(a)gmail.com> wrote: > On Mon, Jan 16, 2012 at 2:43 PM, Frank Shearar <frank.shearar(a)gmail.com> > wrote: > > > Frank, > > I agree with what you said EXCEPT that I don't see the NIH mentality in > Smalltalk. What I do see, and have seen a lot of over the years, is people > coming in and banging on Smalltalk's differences without taking the time to > learn the whys and wherefores. I don't think it's knee-jerk defense so much > as a creeping sense that the person complaining maybe isn't in the best > position to do so. (And I say this as someone who's been on several sides of > the argument.) I'm aware of the reasons why the NIH arises, and I'm sure that's part of why the reaction arises in many other communities. I reserve the right to say "ahem, take the time to actually read what the person's asking for, because they might actually have good ideas". And, in particular, Gerry raises concerns _this very list_ has raised. Living permanently in the image is _bad_, which is why we're moving to Metacello for everything so we can _construct_ an image. Look at Coral, and how they're building a REPL. Look at Laurent Laffont's work on TWM so we can move away from the ridiculous human-as-window manager. That someone comes and says "hey, I score you 90% of my wonderfulometer" is no reason to drive that person away with "go away newbie until you indoctrinate yourself in our ways". (I'm using hyperbole in that last sentence. Please don't understand me as suggesting that we're in a flame war.) Anyway, I have real Smalltalking work to do, to try realise some of the things I need from Smalltalk. Maybe we should all go do that instead of bickering. frank

Jan. 17, 2012

Re: [Pharo-project] Exception logging

by StÃ©phane Ducasse

Thanks guys now what is really strange to me is that whe the code does not contain error to make it compile I have to wrap it with on:do: Any idea? > and if I wrap the execution with a on: error do: > I get > Start33 in the file > > > |file| > [ file := StandardFileStream fileNamed: 'loglog.txt'. > file nextPutAll: 'Start'. > [ file nextPutAll: ((OCClosureCompiler new > compile: 'foo ^ 33.' in: Object classified: nil notifying: nil ifFail: []) > generate valueWithReceiver: Object new arguments: #()) asString] on: Error do: [:ex | ex outer errorReportOn: file]. > ] > ensure: [file close]. > [true] whileTrue: [Beeper primitiveBeep. > ]] newProcess > > > if I remove the on:do: > I do not get anything no beep.

Jan. 17, 2012