December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] SUnit

by Lukas Renggli

> BTW I do not know what is the status of the recent SUnit changes made by Nial > I know that at ESUG they published a squeak version so it would be good to start there. I tries to merge that code, but more than half of the code-base is a conflict. The SUnit framework in Squeak/Pharo has seen an uncountable number of tiny changes that prevents a strait forward merge with the official framework. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 21, 2009

Re: [Pharo-project] can we include this in NewInspector ?? (WAS) Fwd: [ANN] MagmaBrowser

by Henrik Sperre Johansen

On 21.12.2009 20:09, Frederic Pluquet wrote: > Cool :) > > It is added in the last version. Thank you for your participation at > NewInspector ! > > I think the best way to preview a form is to show it in the right side > of the NewInspector in place of the description panel, but it is a > really big challenge: NewInspector is unaware about the composants of > the frame (everything is done by model). I must found a way to achieve > this :) > > FrÃ©d > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet Yes, that was my first thought too, as I told Mariano in a private mail. Sadly, setting the description to be a Form didn't work as well as I had hoped ... So this was the result of the "what can I come up with in 20 mins?" approach :) Probably should be written with a PluggableImageSpec/Morph (which don't exist yet) either way if you're using ToolBuilder for the cross-ui implementation potential. Cheers, Henry

Dec. 21, 2009

Re: [Pharo-project] did you check in 1.1 how the old browser now support the creation of new method cat

by Stan Shepherd

Mariano Martinez Peck wrote: > > As already said several times. For me, we have to: > > 1) Put ALL our effort and or priority to release the 1.0 stable. This > means, > try to fix the 1.0 opened fixes. > > What is the suggested workflow for those of us who want to work off the stable version, and feedback where we find outstanding issues? I would expect to try out the offending code in a 'patched up to date' version of 1.0, to see if it is reproducable there, in which case a search of open bug reports, and possibly a new bug report, would be in order. Is there an easy way to maintain such an up to date version 1.0, with harvested bug fixes? ...Stan -- View this message in context: http://n2.nabble.com/Re-did-you-check-in-1-1-how-the-old-browser-now-suppor… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 21, 2009

Re: [Pharo-project] SUnit

by Julian Fitzell

On Mon, Dec 21, 2009 at 9:36 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks julian. I think that this is nice way to look at it. > > Defining another one would be good - the only important point is that we could load it and > it can transparently replace SUnit. Yes, it would be nice if it still supported the same basic protocol (#assert:, #deny:, etc) so you could simply change the superclass of your test cases and things would (at least more or less) work. Julian

Dec. 21, 2009

Re: [Pharo-project] 1.1unstable Gofer gofer update -> break

by Lukas Renggli

> is your update doing a load or a merge because I wonder if we have changes in pharo Update does a load. Merge does a merge. http://www.lukas-renggli.ch/blog/gofer Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 21, 2009

Re: [Pharo-project] 1.1unstable Gofer gofer update -> break

by Lukas Renggli

> I wanted to load the latest version of Gofer (with Fetch :)) in pharo > so I did Gofer gofer update and I got a GoferReference with a name = nil -> breaks Use this script to update: [ Gofer gofer load ] on: Error do: [ :err | err retry ]. Gofer gofer recompile. The problem is that Gofer changed quite heavily and thus fails in this case because it replaces itself completely. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 21, 2009

Re: [Pharo-project] Update to current in one go?

by Stan Shepherd

StÃ©phane Ducasse wrote: > > what do you mean? > Stef > > Sorry, didn't mean to hit send -- View this message in context: http://n2.nabble.com/Update-to-current-in-one-go-tp4199611p4200284.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 21, 2009

Re: [Pharo-project] did you check in 1.1 how the old browser now support the creation of new method cat

by Adrian Lienhard

Yes, it seems renaming would already help a lot. I think it is ok to have the links to 1.1 dev images on the web page but it should be made clear what these images are supposed to serve for. Adrian On Dec 21, 2009, at 20:07 , StÃ©phane Ducasse wrote: > But having a dev image with unstable is nice because like that we > can test it too :) > I think that 1.1 should be renamed unstable and everything is solved. > I misunderstood what lukas wanted to tell me: in essence the problem > was not really the tools > but the fact that maintaining two versions was too much. > > Stef > >> As already said several times. For me, we have to: >> >> 1) Put ALL our effort and or priority to release the 1.0 stable. >> This means, try to fix the 1.0 opened fixes. >> >> 2) Tag the 1.1 as UNSTABLE. >> >> 3) Remove 1.1 dev link from website and even do not create dev >> images using 1.1 for the moment. Peope should use 1.0 for their >> development. (this was not my idea, adrian i think). >> >> Cheers, >> >> Mariano >> >> On Mon, Dec 21, 2009 at 5:48 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr >> > wrote: >> sure no problem. Lukas. >> I sent the mail because this is an important point. >> I think that we should also understand what is a good amount of >> time between two releases. >> >> On Dec 21, 2009, at 12:20 PM, Lukas Renggli wrote: >> >>>> Lukas, is there a particular reason why you want/need your stuff to >>>> work also with 1.1? >>> >>> The initial trigger for this discussion was Stef asking me to use >>> #chooseOrRequestFrom: for creating protocols in OB. This method >>> was a >>> recently added to morphic in Pharo 1.1 and is used in the old ST-80 >>> browser to create new method protocols with one click. I would >>> love to >>> add it to OB, but since this requires Pharo 1.1 I cannot. >>> >>>> I don't think it makes sense to adapt and fix the external packages >>>> that are in Pharo (of which you maintain a few) as long as >>>> PharoCore >>>> is in alpha state. >>> >>> I do not complain, I completely agree with the Pharo development >>> process. It is great what you are doing. >>> >>> I was telling Stef that I cannot take advantage of the cool new >>> dialogs right now, but only when there is a release candidate for >>> Pharo 1.1. Also I was hoping that I could use Helvetia directly in >>> Pharo 1.1, maybe together with a proposal for making the compiler >>> tool-chain easier to plug-in. However since Helvetia depends on RB >>> and >>> OB that would mean that I had to fork these two projects. >>> Something I >>> cannot do right now. >>> >>> Lukas >>> >>> -- >>> Lukas Renggli >>> http://www.lukas-renggli.ch >>> >>> _______________________________________________ >>> 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

Dec. 21, 2009

Re: [Pharo-project] SUnit

by laurent laffont

Hi, Isn't it similar to Thoughbot shoulda's nested contexts ? http://github.com/thoughtbot/shoulda Laurent On Mon, Dec 21, 2009 at 5:06 PM, Adrian Kuhn <akuhn(a)iam.unibe.ch> wrote: > Niko and me are thinking about doing some work on SUnit. > > Background is that we are working on Phexample, which extends SUnit with > test > that expand on one another [1]. We got test dependencies working with the > current SUnit, but had to do some quick ugly hacks. So we thought about > cleaning the internals SUnit up, and then include test dependencies in the > core. > > Things we would possible change (we will certainly identify more as we > clean > up SUnit...) > > - store test resources in a dynamic variable rather than a static one > - refactor the assert: protocol to a trait, such that they can be used in > setup and teardown of test resources as well (actually I already did that, > you can find a version on my squeaksource account) > - apply the fixes to test resources in Niall's slide deck that Lukas showed > us > - add expectations matchers as used in behavior-driven testing > - break testcase into two classes, and to run the test and one to store the > result (no more #cleanUpInstanceVariables hack to avoid memory leaks) > - add test dependencies to test results, such that one test can extend on > the > return value of another test > - fix expected failures such that they are a first-class result (no more > #shouldPass with O(n^2) or worse behavior) > > So you see, the idea is twofold: first to clean up what is there, and > second > to add test dependencies as a new feature. For those that dont know test > dependencies. They had first been proposed by Markus GÃ¤lli based on an > analysis of all Squeak tests years ago. He found that most tests cover a > superset of another test's coverage set. A prototype in Java as been > implemented later by Lea HÃ¤nsenberger and me. We published a case study at > XP 2008, which lead to PHP folks to include test dependencies in the > latest > PHPUnit. The idea of explicit test dependencies is to shift the burden of > isolating test cases from the developers to the framework. You avoid > duplicate test code and you get less red test cases per failure. Please > refer to Niko's blog post for more details [2]. > > We got some more ideas (such as API baseline testing, search in test > results, > etc...) but they will not likely make it into a first clean up. > > One thing we do not know is how many folks are out there that depend on > internal representation of SUnit. I talked to some folks and identified > two > requirements, first that legacy tests should keep running and second that > contributions to other sunit forks should keep being mergeable. The first > seems feasible, the second sounds like it boils down to not cleaning > anything :) > > What do you think? > > cheers, > AA > > [1]: http://www.squeaksource.com/phexample.html > [2]: > http://smalltalkthoughts.blogspot.com/2009/11/phexample-because-examples-ex… > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 21, 2009

Re: [Pharo-project] can we include this in NewInspector ?? (WAS) Fwd: [ANN] MagmaBrowser

by Mariano Martinez Peck

On Mon, Dec 21, 2009 at 8:09 PM, Frederic Pluquet <fpluquet(a)ulb.ac.be>wrote: > Cool :) > > It is added in the last version. Thank you for your participation at > NewInspector ! > you are welcome, it was all thanks to henrik. > > I think the best way to preview a form is to show it in the right side of > the NewInspector in place of the description panel, but it is a really big > challenge: NewInspector is unaware about the composants of the frame > (everything is done by model). I must found a way to achieve this :) > > yes, that would be REALLYYYYYYYYY cool! but REALLY COOL. hahahah. I don't know to much, but maybe you can ask in the mailing list and someone has an idea :) > FrÃ©d > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet > > > > On Mon, Dec 21, 2009 at 4:57 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Hi Frederic. Henrik Sperre Johansen created this method: >> >> Form >> asNINode >> ^ (super asNINode) >> addAction: >> (NIAction labeled: 'Preview' >> shortcut: $p >> target: >> [ :aForm | >> | anOffset aFrame | >> anOffset := aForm width @ aForm height / -2. >> aFrame := LayoutFrame fractions: (0.5 @ 0.5 >> corner: 0.5 @ 0.5) offsets: (anOffset corner: anOffset). >> (SystemWindow labelled: 'Form preview') >> addMorph: (ImageMorph new image: aForm) >> fullFrame: aFrame; >> openInWorldExtent: (aForm extent max: 267 @ >> 0) ] >> actionSelector: #value: >> withArgs: {self} >> category: 'Preview'); >> yourself >> >> >> >> It let you see the image of something. Example, inspect a form ( >> ThemeIcons infoIcon ), right-click the Form >> node, and select preview. >> >> In addition, he told me this: >> >> "For inclusion in the NewInspector package on SqueakSource, I would at >> least change the magic number 267 first, to one computed based on the width >> of the Window label, 267 is merely what is needed to display it fully with >> the standard window font in PharoDev :) >> Feel free to do so, and ask Frederique Pluquet to to include it there." >> >> So....can you take care of this and include it ? would be very useful!!! >> >> Thank you very much. >> >> Mariano >> >> >> ---------- Forwarded message ---------- >> From: Henrik Sperre Johansen <henrik.s.johansen(a)veloxit.no> >> Date: Thu, Dec 17, 2009 at 10:12 PM >> Subject: Re: [Pharo-project] [ANN] MagmaBrowser >> To: pharo-project(a)lists.gforge.inria.fr >> >> >> On 16.12.2009 11:29, Mariano Martinez Peck wrote: >> > This is an excellent job. Congratulations HernÃ¡n. >> > >> > I have a question....how could you draw the photo instead of the array >> > of bytes on the browser? I really hate when developing with seaside >> > and I have some pictures in my filelibrary class and when I browse >> > them I see the array of bits...but I want to see the picture!!! >> > >> > Thanks >> > >> > Mariano >> For a proof of concept of what is possible using the NewInspector, >> install this method: >> Form>>asNINode >> ^ (super asNINode) >> addAction: >> (NIAction labeled: 'Preview' >> shortcut: $p >> target: >> [ :aForm | >> aForm depth < 32 ifTrue: [ Display >> getCanvas image: aForm at: 10 @ 10 ] >> ifFalse: [ Display getCanvas >> translucentImage: aForm at: 10 @ 10 ] ] >> actionSelector: #value: >> withArgs: {self} >> category: 'Preview'); >> yourself >> >> then inspect a form (Say, ThemeIcons infoIcons ), right-click the Form >> node, and select preview. >> >> Ideally it'd be nice to add an extra "Preview" item to the subnodes of >> Forms in the NI, which when clicked would show the form on the right >> side, but I don't (easily) see how you can temporarily replace the >> TextMorph on the right side with something capable of displaying Forms >> >> With some more work on the closure it should be possible to open the >> preview in a separate window though :) >> >> Cheers, >> Henry >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >

Dec. 21, 2009