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

SmalltalkHub password lost

by Dennis Schetinin

Hello all, who should I contact to restore/reset my password at SmalltalkHub? -- Best regards, Dennis Schetinin

Jan. 30, 2014

Re: [Pharo-dev] Please keep your cool new stuff for Pharo 4

by Pharo4Stef

Thanks Gemini Criquet :) You are right On 30 Jan 2014, at 17:11, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Soâ¦ instead following my advice, you people continue submitting and asking for integration things that are API changes. > As a result, instead gaining stability we are loosing itâ¦ > > can you guys please be so kind and stop doing what you shouldnât? > > I will ask it again: *now* we need to bugfix the upcoming release. > Cleanups, enhancements, small additions *are not* bugfixing. And even if you are sure that it is not breaking anything, it most probably will do (for more details, take as an example the mail I will send in 5 min). > > I know we all want a better Pharo. But at this moment the way to achieve it is to collaborate in testing, reporting and fixing the current version. > > Thanks, > Esteban

Jan. 30, 2014

Re: [Pharo-dev] [Review]: Case 12737 Morph sends mouseUp twice to handlers

by Pharo4Stef

thanks this is indeed nice to be able to spot the one we viewed too. On 30 Jan 2014, at 13:25, btc(a)openinworld.com wrote: > Stef, A little different than you asked for, but I find the following combination useful when I'm trying to find a case that I recently viewed that was opened by someone else: > * Viewed by me - Show only cases I have viewed before > * Sort By - Last viewed by me (Reverse) > > cheers -ben > > Benjamin wrote:

Jan. 30, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Esteban Lorenzano

and is even worst: classes from system that uses pools do not show them. take a look at AJx86Assembler it should be like that: AJAssembler subclass: #AJx86Assembler instanceVariableNames: 'instructions last labels stackManager level is64' classVariableNames: '' poolDictionaries: 'AJConstants AJx86Registers' category: 'AsmJit-x86â and now you cannot see it (pools are there, the problem of not being there is with injected classes). And EVEN WORST: I cannot re-add my pools. It just does not works. please, fix it. AND GUYS STOP CHANGING THE API IN A FROZEN VERSION!!!!!! thanks, Esteban On 30 Jan 2014, at 18:14, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Soâ¦ that. > > Is super cool to remove poolDictionaries from the default class template. > What is not cool *at all* is the fact that now my low level projects, who uses them intensively, does not work anymore. > The reason? the classes are created without poolDictionaries. > > So, pleaseâ¦ whoever pushed this change. Please fix it. > > thanks, > Esteban

Jan. 30, 2014

Re: [Pharo-dev] poolDictionaries removal breaks my projects

by Sebastian Sastre

Woha that sounds kind of wild Easy on radical changes guys, change have costs On Jan 30, 2014, at 3:14 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Soâ¦ that. > > Is super cool to remove poolDictionaries from the default class template. > What is not cool *at all* is the fact that now my low level projects, who uses them intensively, does not work anymore. > The reason? the classes are created without poolDictionaries. > > So, pleaseâ¦ whoever pushed this change. Please fix it. > > thanks, > Esteban

Jan. 30, 2014

poolDictionaries removal breaks my projects

by Esteban Lorenzano

Soâ¦ that. Is super cool to remove poolDictionaries from the default class template. What is not cool *at all* is the fact that now my low level projects, who uses them intensively, does not work anymore. The reason? the classes are created without poolDictionaries. So, pleaseâ¦ whoever pushed this change. Please fix it. thanks, Esteban

Jan. 30, 2014

Please keep your cool new stuff for Pharo 4

by Esteban Lorenzano

Soâ¦ instead following my advice, you people continue submitting and asking for integration things that are API changes. As a result, instead gaining stability we are loosing itâ¦ can you guys please be so kind and stop doing what you shouldnât? I will ask it again: *now* we need to bugfix the upcoming release. Cleanups, enhancements, small additions *are not* bugfixing. And even if you are sure that it is not breaking anything, it most probably will do (for more details, take as an example the mail I will send in 5 min). I know we all want a better Pharo. But at this moment the way to achieve it is to collaborate in testing, reporting and fixing the current version. Thanks, Esteban

Jan. 30, 2014

[ANN] CJSolver

by Luc Fabresse

Hi all, As a teacher, I always try to find new programming exercices for students. I discovered the CodeJam coding contest that provides problems and their data sets. We can also upload a solution on the website and it tells us if it is right or wrong. Example of problem: http://code.google.com/codejam/contest/dashboard?c=351101#s=p2 So, I did a little framework (CJSolver) to make it easier to read data sets and write result files. More info here: http://car.mines-douai.fr/2014/01/cjsolver-a-framework-to-solve-problems-of… The code is on Smalltalkhub but since I also wanted to commit data set files and correct results, I also have a github repo here: https://github.com/LucFabresse/CJSolver You can checkout the code, test it, implement solution to other problems or *optimize* already implemented solutions (I did the simplest version ;-)) and sometimes it is slow on big data sets. have fun, #Luc

Jan. 30, 2014

Re: [Pharo-dev] process to collaborate on cleaning morphic

by Sean P. DeNigris

Pharo4Stef wrote > Because we should really learn about morph internals. Yes, it's more than cleaning. There has been so much stuff tacked on to the basic beautiful idea of Morphic that it's hard to tell what it currently does and what it needs to do. That's why as a first step, I'm learning several Morphic implementations - Lively Kernel, Cuis, Self - as well as the new VPRI work, to understand what the core is and what the options are. I'm not against cleaning, but I believe it will take work from both sides - cleaning what we have, and building/reorganizing the core ideas. ----- Cheers, Sean -- View this message in context: http://forum.world.st/process-to-collaborate-on-cleaning-morphic-tp4739325p… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 30, 2014

Better #cleanUpForProduction

by Marcus Denker

Hi, I did a small pass over #cleanUpForProduction -> do not delete Classes (package should not get dirty) -> do not use SUnitUnloader, as people want SUnit in the deployed system -> unload all *Tests and *-Help TODO -> some test packages are missed because they are not XXTest -> Maybe we should not unload Deprecated30 (this would avoid some dirty packages) -> There might be other things to unload (e.g. ProfStef) But all in all it is already quite nice. It shrinks the current image to 17.5MB Marcus

Jan. 30, 2014