June 2012 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Nautilus subclassing

by StÃ©phane Ducasse

Thanks dan! Stef > > I added a new comment to Issue 5954 regarding Nautilus and groups. I'm having an issue adding any package containing class side extension methods to a group. If this should be a separate issue please let me know and I will open one. I think it's similar enough to clump together with the original problem. > > Dan Uber > > On 05/22/2012 10:10 AM, Benjamin wrote: >> Basically, I think this is a mistake I made :) >> >> It should always use the nonMetaClass side of the current selectedClass :) >> >> >> Thank you for feedback :) >> Could you simply open a bug entry, to be sure I do not forget about it ? :) >> >> Thanks in advance, >> >> Ben >> >> On May 22, 2012, at 4:40 PM, djuber wrote: >> >>> my apologies, this should have had its own thread. >>> >>> Dan Uber >>> >>> -- >>> View this message in context: http://forum.world.st/auto-format-methods-tp4630741p4631398.html >>> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >>> >> > >

June 6, 2012

Re: [Pharo-users] Something does not work with issue tracker status

by Sean P. DeNigris

Mariano Martinez Peck wrote > > We really need people helping review changes... So, please, help us review > issues. Is the only way > to improve. > +1. I will try a few... Sean -- View this message in context: http://forum.world.st/Something-does-not-work-with-issue-tracker-status-tp4… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 6, 2012

Re: [Pharo-users] Nautilus subclassing

by Daniel Uber

I added a new comment to Issue 5954 regarding Nautilus and groups. I'm having an issue adding any package containing class side extension methods to a group. If this should be a separate issue please let me know and I will open one. I think it's similar enough to clump together with the original problem. Dan Uber On 05/22/2012 10:10 AM, Benjamin wrote: > Basically, I think this is a mistake I made :) > > It should always use the nonMetaClass side of the current selectedClass :) > > > Thank you for feedback :) > Could you simply open a bug entry, to be sure I do not forget about it ? :) > > Thanks in advance, > > Ben > > On May 22, 2012, at 4:40 PM, djuber wrote: > >> my apologies, this should have had its own thread. >> >> Dan Uber >> >> -- >> View this message in context: http://forum.world.st/auto-format-methods-tp4630741p4631398.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >

June 6, 2012

Re: [Pharo-users] Something does not work with issue tracker status

by Benjamin

On Jun 6, 2012, at 1:47 PM, Mariano Martinez Peck wrote: > Hi guys. Previously, we use to mark issues as "Fixed" once someone proposed a solution. Now we have to first put it as ""FixReviewNeeded" and then when someone else takes the time to review it put it as "FixToInclude". Now...the problem is that nobody reviews and issues get outdated. And then, when trying to load the slice or .cs it does not work anyomre, or it is outdated, or whatever. Meaning that it has to be regenerated and we spend the double of time. So, what can we do to improve this???? ideas: > > 1) We should be more confident ourselves. Imagine we have proposed something and it is as "FixReviewNeeded". If we have run the tests, and we didn't break anything, and the problem is really fixed, and the topic is not something REALLY critical, and no one has reviewed your issue, why not to putting it as "FixToInclude" ? The problem here is the objectivity, or the lack of knowledge :) Usually when I post a fix, I have tried it, it works in my image etc. But it happened that it breaks something hidden somewhere because of a side effect I wasn't aware of :) > 2) We really need people helping review changes. There are only a few guys that do this. You DON'T need to be an expert. "FixReviewNeeded" does not mean "HasToBeReviewedByAGuruExperiencedHacker". It just means "it just requires another eyes". So, please, help us review issues. Is the only way to improve. But I totally agree with this :) Reviewing fix can be really easy and fast :) Maybe we should also use more often the flag "Easy" or "Difficult". I admit doing that form time to time, just take the "Easy" ones and review them :) But in general, I think that more people should review :) And when a fix break something, nobody checks who was the poster or who was the reviewer :) My 2cts, Ben > so, what do you think? > > > -- > Mariano > http://marianopeck.wordpress.com >

June 6, 2012

Something does not work with issue tracker status

by Mariano Martinez Peck

Hi guys. Previously, we use to mark issues as "Fixed" once someone proposed a solution. Now we have to first put it as ""FixReviewNeeded" and then when someone else takes the time to review it put it as "FixToInclude". Now...the problem is that nobody reviews and issues get outdated. And then, when trying to load the slice or .cs it does not work anyomre, or it is outdated, or whatever. Meaning that it has to be regenerated and we spend the double of time. So, what can we do to improve this???? ideas: 1) We should be more confident ourselves. Imagine we have proposed something and it is as "FixReviewNeeded". If we have run the tests, and we didn't break anything, and the problem is really fixed, and the topic is not something REALLY critical, and no one has reviewed your issue, why not to putting it as "FixToInclude" ? 2) We really need people helping review changes. There are only a few guys that do this. You DON'T need to be an expert. "FixReviewNeeded" does not mean "HasToBeReviewedByAGuruExperiencedHacker". It just means "it just requires another eyes". So, please, help us review issues. Is the only way to improve. so, what do you think? -- Mariano http://marianopeck.wordpress.com

June 6, 2012

Re: [Pharo-users] foreign function call

by Esteban Lorenzano

Hi, In essence, is the same. To have all complete version running (in 1.4), you should execute: Gofer it squeaksource:'Alien' ; package: 'ConfigurationOfOldAlien'; load. ((Smalltalk globals classNamed: 'ConfigurationOfOldAlien') project version: #stable) load. This will load FFI and Alien (who allows the callback stuff). Then you can look for the examples. (yes... this is an ugly and low-documented issue... we should improve in that area this year) Esteban On Jun 6, 2012, at 11:02 AM, Raffaello Giulietti wrote: > Hello, > > is there documentation and/or examples about Pharo's Foreign Function > Interface? Is FFI inherited from Squeak's > (http://wiki.squeak.org/squeak/1414)? > > Thanks > Raffaello Giulietti >

June 6, 2012

foreign function call

by Raffaello Giulietti

Hello, is there documentation and/or examples about Pharo's Foreign Function Interface? Is FFI inherited from Squeak's (http://wiki.squeak.org/squeak/1414)? Thanks Raffaello Giulietti

June 6, 2012

GemSource, seaside.gemstone.com, SS3 MAINTENANCE Saturday June 9 from 10am-2pm PDT

by Dale Henrichs

Maintenance is scheduled for this Saturday and according to the internal announcement no downtime is anticipated: The work is considered low risk and no downtime is anticipated, this is being sent out as a courtesy. If you experience problems on Saturday, don't hesitate to send email. Dale

June 5, 2012

IWST'12 Call for papers

by Alain Plantec

Dear Smalltalkers, We apologize for multiple reception of this announcement. The International Workshop on Smalltalk Technologies, is a European Smalltalk User Group (ESUG) Conference joint event, that focuses on research activities - namely academic creative work undertaken on smalltalk use, and more generally on object technologies. IWST was launched in 2009, in Brest, during the 17th ESUG Conference. The second edition took place in Barcelona, and the third edition was held in 2011 at the heart of historic Edinburgh. Next edition will be in Gent, Begium this summer (28th of august). ESUG gathers groups of professionals and hobbyists who share an interest in the Smalltalk programming languages and related technologies. The goal of the workshop is to create a forum around advances or experience in Smalltalk. IWST contributes to triggering discussions and exchanges of ideas. As always, we make a point to have a very constructive paper review process that aims to provide in-depth comments and suggestions to all of them (no one-liners!) This makes it ideal to disseminate new research directions, and is a good venue for early stage PhD students to receive feedback on their work. In addition, we intent to invite best papers to a journal special issue as we did last year. Looking forward to your submissions, and to meeting you in Gent! Best regards, LoÃ¯c Lagadec& Alain Plantec Co-chairs of IWST International Workshop on Smalltalk Technologies 2012 August 28th, 2012 Gent, Belgium. ESUG 2012 Smalltalk joint event Important dates Submission deadline: June 15, 2012 Notification deadline: July 15, 2012 All accepted papers will be published in ACM DL, and the authors of the best papers will be invited to submit an extended version to a journal special issue (To Be Confirmed). Goals and scopes The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. Participants are invited to submit research articles. We will not enforce any length restriction. However we expect papers of two kinds: Short position papers describing emerging ideas. Long research papers with deeper description of experiments and of research results. Topics We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: Aspect-oriented programming, Design patterns, Experience reports, Frameworks, Implementation, new dialects or languages implemented in Smalltalk, Interaction with other languages, Meta-programming and Meta-modeling, Tools Links home page:http://www.esug.org/wiki/pier/Conferences/2012/International-Workshop-… submission:http://www.easychair.org/conferences/?conf=iwst2012 Publication Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm. This site also contains links to useful informations on how to write effective submissions. Program chairs LoÃ¯c Lagadec and Alain Plantec (LabSticc CACS/CNRS, University of Brest, France) Program committee Gabriela Arevalo Universidad Nacional de Quilmes, Argentina Alexandre Bergel University of Chile Andrew P. Black Portland State University, US Marcus Denker Rmod, INRIA Lille - Nord Europe, France Luc Fabresse Ecole des Mines de Douai, France, Tudor Girba CompuGroup Medical Schweiz, Switzerland Andy Kellens Software Languages Lab, Vrije Universiteit Brussel, Belgium MickaÃ«l Kerboeuf LabSticc, University of Brest, France Jannik Laval LaBRI, University of Bordeaux, France Mariano Martinez Peck Ecole des Mines de Douai, France, Lukas Renggli Google, Switzerland Jorge Ressia Software Composition Group, University of Bern, Switzerland Bastian Steinert HPI, Software Architecture Group, Germany Hernan Wilkinson 10Pines, IT consultancy, Buenos Aires, Argentina Roel Wuyts IMEC Leuven, Belgium

June 5, 2012

Re: [Pharo-users] Another new Blog

by Sven Van Caekenberghe

Very nice and informative: I read it all. Thank you ! Sven On 03 Jun 2012, at 06:38, Guillermo Polito wrote: > Hi all! > > Probably some of you already saw my tweets about it: http://playingwithobjects.wordpress.com/. I'll be writing there stuff, whatever I want to write :). Probably in this first few weeks, documentation about the Pharo bootstrap project. > > I didn't make it public before because I wanted to see if I had time and will to write. And it seems I have both :). > > So far, three posts: > - how the objects are formatted in memory for the VM > - image based vs non image based environments > - bootstrap introduction > > Please, do not hesitate to leave me your comments. I'm very far from being a gurÃº on any of the things I write, so do not expect that. Even better: expect me to make mistakes and write wrong things, and please correct me :). > > Saludos, > Guille

June 5, 2012