July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Pharo-users] Recent Messages Browser

by StÃ©phane Ducasse

On Jul 30, 2010, at 10:47 AM, Mariano Martinez Peck wrote: > > > On Fri, Jul 30, 2010 at 2:47 AM, Benjamin Van Ryseghem <benjamin.vanryseghem(a)gmail.com> wrote: > Hi everybody, > > > > I've rewrited a recent messages browser based on MorphTreeMorph. > > > Hi, this is very good idea! > > > If you can test it and tell me what's do you think about, it will be cool (I'm a new Smalltalker ^^) > > > welcome! > > > You can download code here : > > Gofer new > squeaksource: 'PharoTaskForces'; > package: 'RecentSubmissions'; > load. > > > To launch it, just click on the World >> Tools >> Recent Messages. > > You can set it up in the Setting Menu >> Code browsing >> Recent Message. > > > > Ok...I did it. A few remarks: > > 1) RecentMessageList >> initialize > > you do > > SmalltalkImage current addToStartUpList: self class. > > but should be SmalltalkImage addToStartUpList: self class. just Smalltalk addToStartUpList: self class. > > > (at least in Pharo 1.1) > > 2) What is the idea of the Recent Messages? To see the recent MODIFIED methods ? isn't it? If true, maybe would be good to > 2.1) directly show the diff with the previous version > 2.2) Have a button to see the versions of that method > > 3) Once you press any button, like collapse all or similar, they become blue and neve grey again > > 4) When is the list of recen messages clean ? how do you know the recen messages? you store that information somewhere? when is that cleaned? > > > Thank you very much and continue with the good work! Maybe once we can include it by defult in Pharo. yes this is the point. >

July 31, 2010

Re: [Pharo-project] PharoCore 1.1 comments

by StÃ©phane Ducasse

> Other than that, the new image is *very* fast! We did a lot of cleans. Now it should be clear that we benefitted from the work done in Squeak by levente, nicolas and a couple of others. Now this is not easy to follow what exactly can benefit to pharo and they were supportive. Now people can help at this level, comparing behavior, methods.... Finally we do not want to give the impression that we are stealing from Squeak - I think that Squeak can also learn from Pharo. Our goal is to make a really cool Smalltalk system. There are still a lot of work to be done. Stef

July 31, 2010

Re: [Pharo-project] there are still references to PluggableButtonMorphPlus

by StÃ©phane Ducasse

marcus can you update http://code.google.com/p/pharo/issues/detail?id=2732 Stef On Jul 29, 2010, at 8:56 PM, Marcus Denker wrote: > > On Jul 29, 2010, at 7:35 PM, Mariano Martinez Peck wrote: > >> I am in PharoCore 12066 and there are still references to PluggableButtonMorphPlus, which doesn't exist anymore: >> >> > > As much as I understand what Stef did with Gary is to start to merge all those many many button classes into one. > They removed all the *Plus ones, for example. The standard Pluggable one can now do what the Plus did. > >> 1) MorphicToolBuilder >> buttonClass >> ^ PluggableButtonMorphPlus >> >> is it ok to change it to >> >> buttonClass >> ^ PluggableButtonMorph >> >> ? >> > yes, did that. > >> 2) UITheme >> newButtonIn: aThemedMorph for: aModel getState: stateSel action: actionSel arguments: args getEnabled: enabledSel getLabel: labelSel help: helpText >> >> >> |b| >> b := PluggableButtonMorphPlus >> on: aModel >> getState: stateSel >> action: actionSel >> label: labelSel. >> >> .... >> >> is it ok to change it to >> >> |b| >> b := PluggableButtonMorph >> on: aModel >> getState: stateSel >> action: actionSel >> label: labelSel. >> >> ? >> > > I did that. >> >> 3) MorphicToolBuilderTests >> expectedFailures >> "Polymorph override of PluggableButtonMorphPlus>>update: makes color not being updated anymore in respond to sending #changed:. Was this an intentional change and this test is obsolete?" >> ^ #(testGetButtonColor) >> >> >> I don't know how this one should be. But it should be updated, at least the class name. >> > > Yes, the classname should be fixed. > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 31, 2010

Re: [Pharo-project] PluggableThemedOverflowPanelMorph(Object)>>doesNotUnderstand: #statusColor

by StÃ©phane Ducasse

Thanks gary mentions that to me but I was off. http://code.google.com/p/pharo/issues/detail?id=2732 On Jul 29, 2010, at 8:54 PM, Marcus Denker wrote: > > On Jul 29, 2010, at 7:38 PM, Mariano Martinez Peck wrote: > >> ok...as martin said, recompiling (change and save) PluggableButtonMorph>>#update: >> did the trick...weird. Now we need to include this fix ASAP in the stream.. >> > I did: > > -> fix all refrences to PluggableButtonPlus (and all other Undeclared) > -> recompile the image. > > Works. > > >> cheers >> >> mariano >> >> On Thu, Jul 29, 2010 at 7:23 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> We need help to solve this problem....I cannot do anything as I need the TestRunner. >> >> WE have http://code.google.com/p/pharo/issues/detail?id=2717 >> >> and http://code.google.com/p/pharo/issues/detail?id=2700 >> >> I tried a Compiler recompileAll but still have the same problem. >> >> Cheers >> >> Mariano >> >> >> On Mon, Jul 26, 2010 at 11:02 PM, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> Just try open a TestRunner. You will get a DNU and that won't let you even debug the error. >> >> Pharo core version: PharoCore-1.2-12061 >> >> I attach PharoDebug.log >> PluggableThemedOverflowPanelMorph(Object)>>doesNotUnderstand: #statusColor >> >> Issue: http://code.google.com/p/pharo/issues/detail?id=2717 >> >> Cheers >> >> Mariano >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 31, 2010

Re: [Pharo-project] Conflic between Shout and PluggableTextMorph in Pharo 1.2

by StÃ©phane Ducasse

open a ticket :) Stef On Jul 29, 2010, at 8:49 PM, Mariano Martinez Peck wrote: > Hi. If you try to load Shout, you will have the error: 'styler is already defined in PluggableTextMorph' > > The problem is that the Shut class PluggableShoutMorph subclass PluggableTextMorph. > PluggableShoutMorph has its own instVar 'styler' which PluggableTextMorph doesn't have in Pharo 1.1 > > But in Pharo 1.2 (I don't know why) PluggableTextMorph has its own instVar 'styler'....thus, the problem. > > Of course, if I remove the instVar 'styler' from PluggableShoutMorph it shoud load...but I am not sure if this is the correct action. > > Thanks for the help in advance > > Mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 31, 2010

Re: [Pharo-project] what about deprecating deprecated: ?

by StÃ©phane Ducasse

Good idea. Now what I want and we will do it with veronica :) is to have *****ALL***** the squeak/pharo code in a Gemstone db so that we can browse the complete history. Stef On Jul 29, 2010, at 8:24 PM, Mariano Martinez Peck wrote: > Hi folks. Yes, I know it sounds weird...but just read > > We said (don't remember when) that when we deprecate a method, we give a whole release time so that eternal packages can fix they senders. And then in the next release we remove it. > > For example, in Pharo 1.1 we deprecate the methodX. Then, in Pharo 1.2, we should remove it, together with the rest of methods depreacted in Pharo 1.1. > > How to detect the methods deprecated in Pharo 1.1? You need to take a 1.1 image and look there. > > But to solve this, and other problems, we have not only deprecate: but also deprecated: anExplanationString on: date in: version > This is muuuch better and we can even then automate code so that it automatically removes the deprecation of a previous image. You can browse and see where each method was deprecated. > > It would be cool if everybody uses that method instead of deprecated. And thus, it would be cool to deprecate deprecated: hahahahaha > > what do you think? > > cheers > > mariano > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 31, 2010

Re: [Pharo-project] Books for summer (was: Time Machine)

by StÃ©phane Ducasse

C 90 ansi. Socket chapters for the next books Gentle introduction to semaphores (reread in fact). Not sure that this is inspiring... On Jul 26, 2010, at 7:39 AM, laurent laffont wrote: > > > On Sat, Jul 24, 2010 at 10:59 AM, Patrick Barroca <patrick.barroca(a)gmail.com> wrote: > I've ordered "Why programs fail" by Andreas Zeller. > It will be my summer holidays book ;) > > So I'll borrow it once read :) > > I've ordered > "Your Brain at Work: Strategies for Overcoming Distraction, Regaining Focus, and Working Smarter All Day Long" - David Rock > > "The 10-day MBA: A Step-by-Step Guide to Mastering the Skills Taught in Top Business Schools" - Steven Silbiger (recommended in "Passionate Programmer" by Chad Fowler). > > And you dear Pharoers, what will you read this summer regarding your computing/business activity ? > > > Laurent > > > > On Thu, Jul 22, 2010 at 11:52 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: > > http://www.st.cs.uni-saarland.de/dd/ > > you can get some papers but also the slides that go with the book > > Stef > > > > On Jul 22, 2010, at 11:36 PM, laurent laffont wrote: > > > >> > >> On Thu, Jul 22, 2010 at 11:34 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >> did you read delta debugging from andreas Zeller? > >> > >> No. Where ? > >> > >> Laurent > >> > >> > >> > >> Stef > >> > >> On Jul 22, 2010, at 11:11 PM, laurent laffont wrote: > >> > >> > Hi, > >> > > >> > From a discussion I had with Kent Beck about Continuous Testing / Autotest (see http://pharocasts.blogspot.com/2010/07/live-testing-with-autotest.html ), I would like to add a kind of Time Machine for Smalltalk code in Autotest. > >> > > >> > When a test fails, what I really want to know is why. Sometimes a test fails and I don't know why. So I have to go through a debugging session which distracts me from what I've been coding. > >> > > >> > So an idea is to diff backtrace before and after the test fails: > >> > - revert to last green > >> > - replay the test and save the trace > >> > - forward to current test and run (test fails) > >> > - compare execution paths in order to see the consequence of last change > >> > > >> > How would you do this ? Where should I look for materials which can help me coding this ? > >> > > >> > Cheers, > >> > > >> > Laurent Laffont > >> > > >> > http://pharocasts.blogspot.com/ > >> > http://magaloma.blogspot.com/ > >> > _______________________________________________ > >> > Pharo-project mailing list > >> > Pharo-project(a)lists.gforge.inria.fr > >> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Patrick Barroca > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 31, 2010

Re: [Pharo-project] HTTP client library in Pharo?

by StÃ©phane Ducasse

> Welcome to the wonderful world of squeak: > > (Robin Williams genii voice on) > > Vast, Cosmic Programming Powers!!!! > > poorlymaintainedlibraries Even if you are right, nothing prevents people to - load - fix - enh libraries We are working on books, chapters, ... and any help is welcomed. People often mentions that Python has good documentations, but documentations/tests.... do not get written magically. People do write them. We will make sure with Metacello that libraries gets archived and loadable since metacello will help us to build distributions. Kent Beck told me recently that we often forget that everything done (even simple) is not to be done anymore and that each time you do something you progress. This is an important vision behind pharo. Do something small and do it a lot. Everybody can do something small. Stef

July 31, 2010

Re: [Pharo-project] Aida/Web now loads and runs well on Pharo 1.1

by StÃ©phane Ducasse

janko excellent news. Did you create and publish configurationOfSwazoo.... Aida? Because this is the way to go :) Stef On Jul 28, 2010, at 11:15 PM, Janko MivÅ¡ek wrote: > Hi guys, > > I just made Aida ready on new and wonderfull Pharo 1.1. and now Aida > installs and run nicelly and even side by side with Seaside. You can > even run both on the same Swazoo web server, which is also included. > > Just evulate DEVImageWorkspaces openExternalProjectWorkspace then > evaluate loads of both Seaside and Aida, then start both, for Aida evaluate: > > SwazooAida demoStart > "open http://localhost:8888 in your web browser" > > Best regards > Janko > > > -- > Janko MivÅ¡ek > AIDA/Web > Smalltalk Web Application Server > http://www.aidaweb.si > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 31, 2010

Re: [Pharo-project] About overlapping packages :(

by StÃ©phane Ducasse

> sounds tricky. at the very least add a checker to a menu somewhere so > we can start to use it. I will do that. > You wouldn't need to that deeply integrate it > in the first instance... > > do you need to match the existing semantics exactly? I don't think > it's good that we can get into these situations. Perhaps we should > prevent them being able to be created in the first place, rather than > deal with them once they overlap. It will change the flow: we will not be able to create a new subpackage Foo-Core (if Foo is already created) , but will have to start delete the top package. Stef

July 31, 2010