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

Re: [Pharo-project] How do you extract a superclass if you can't select multiple classes?

by Tim Mackinnon

Hi Lukas - sorry to keep this thread going, but I don't quite understand what you mean? Partly I think the issue is that over the years I've become very familiar with the Eclipse/IntelliJ refactorings (and how they approach things) and I've slowly forgotten how they work in smalltalk (although - in Dolphin they seem to more closely match Eclipse/IntelliJ - adding to my confusion in Pharo). To give some context, I had a class X, then I copied it to create class Y - made some changes and got something useful working. However X and Y are mostly the same - so deserve a superclass. This sounds to me like standard Refactor Class | Create Superclass refactoring (available in the context menu). Is this what you are referring to? (And this is a seaside30.rc image). Is this the create class refactoring you are referring to? It doesn't sound like it? The one I am referring to just asks me for a name of a superclass and shows me the method changes it will make (and I can remove those which I don't deem common) - but they only apply to the single class I ran the refactoring for - say X. This then leaves me with Y which still needs work. I was expecting somewhere where it would ask me if there are any other classes to consider for the refactoring (or better still - let me multi-select several classes before I do the "create superclass" in the first place - which apparently is very hard in Pharo for some reason?). So is there some other browser, or menu option that I am missing? Tim On 6 Aug 2010, at 00:31, Lukas Renggli wrote: >>> Good point. I've been struggling with multiple selection too e.g. >>> when >>> setting the refactoring scope. There's an entry called >>> "selection..." but >>> since I've never been able to select more than one item from a list, >>> selecting "selection..." has the same effect as âcategory" (when >>> in a >>> category list of course). >> >> So is there some way of applying a refactoring to more than one >> class? What >> is that refactoring scope menu item - is there some way to specify >> 2 or more >> classes in there? Why is this so hard? > > The refactoring scope is something completely different. It selects > the part of the system that is considered by a refactoring. > > Did you ever try to go through the whole create-class refactoring? I > get a dialog that offers me to select multiple classes. > > Lukas > > -- > Lukas Renggli > 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

Aug. 6, 2010

Re: [Pharo-project] [Sugar-devel] [ANN] DrGeo 10.08

by Bert Freudenberg

On 06.08.2010, at 08:54, Hilaire Fernandes wrote: > Dear all, > > I am please to announce the release 10.08 of the DrGeo activity. > > http://blog.ofset.org/hilaire/index.php?post/drgeo-xo-10.08-release Congratulations! For people unfamiliar with Squeak, you might want to add a note about how to quit (e.g., not to save when asked). Also, I had to manually install the bundle. After downloading, Sugar did not recognize it as an activity. I guess your wiki does not serve the right mime type. Uploading to aslo might be better (although it would be nice if Sugar was a little more forgiving). This is on the OLPC 260py build (Sugar 0.88.1). - Bert -

Aug. 6, 2010

Re: [Pharo-project] Are the bytecodes correct?

by Marcus Denker

On Aug 6, 2010, at 5:55 AM, James Ladd wrote: > Hi All, > > I asked about primitives earlier and found out that there are quite a few new primitives > than those listed in the blue book. Very useful. > See Re: [Pharo-project] Additional Primitives? > > This leads me to ask, are all the bytecodes as listed in the blue book or are there > differences I should know about ? > The best is to just check the VM sourcecode. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Aug. 6, 2010

Re: [Pharo-project] Autotest, proof-of-concept [was: About TDD and Pharo]

by laurent laffont

Hi Alex, Now that I've managed to use Pharo at work (youhou !!) I'm in a case where I have very long tests (selenium acceptance tests) *and* I want them to run. Ideally I also want to queue and schedule them (if a test is saved twice in a queue, run only once and put it in higher position on the queue). Solutions: - have to running modes for Autotest (normal and batch) - tagging - ? Laurent On Mon, Jul 26, 2010 at 8:01 AM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Ideally, we should not tag long tests. The system should be smart enough to > characterize a test as long. If it takes more than 200ms, then it is long. > Autotest should then offer me to include long test or not in the automatic > test execution. > > Using tags means that I have to go over each method test and tag them. This > is a costly effort that is likely to not work in practice. > > We have > -=-=-=-=-=-=-=-=-=-=-=-= > TestCase class>>newTestDictionary > ^ Dictionary new at: #timeStamp put: TimeStamp now; > at: #passed put: Set new; > at: #failures put: Set new; > at: #errors put: Set new; > yourself > -=-=-=-=-=-=-=-=-=-=-=-= > > Maybe it should be extended with > -=-=-=-=-=-=-=-=-=-=-=-= > at: #long put: Set new > -=-=-=-=-=-=-=-=-=-=-=-= > > I guess the tweak in SUnit to identify long tests should not be that hard > to implement. > > Cheers, > Alexandre > > > On 26 Jul 2010, at 07:44, laurent laffont wrote: > > > > > On Sat, Jul 24, 2010 at 10:16 AM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > I have been using Autotest for a while already. I greatly reduce the > window switching. This is cool. > > However, I have to disable Autotest when the tests take time to execute. > > > > > > An idea is to be able to tag tests with pragmas to put them in > categories. So we can have a LongRunning category which is not run by > default. Like NUnit (http://www.nunit.org/index.php?p=category&r=2.2) > > > > Then SUnit could be enhanced to show these categories. Useful to quickly > select all tests related to a project for example; or run only performance > tests. > > > > > > How would you name the tag ? Where the implementation should go ? > (TestCase ?) > > > > > > Laurent. > > > > > > Alexandre > > > > > > On 15 Jun 2010, at 21:41, laurent laffont wrote: > > > > > Hi Alexandre, > > > > > > I've reorganized Autotest to write tests. The tests now run in a thread > with lower priority. Thanks for feedback. > > > > > > Cheers, > > > > > > Laurent Laffont > > > > > > http://pharocasts.blogspot.com/ > > > http://magaloma.blogspot.com/ > > > > > > > > > On Mon, Jun 14, 2010 at 4:52 PM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > > Hi Laurent, > > > > > > I tried to program while having AutoTest running. > > > More importantly than the interface, I experienced some problem with > long executing tests. Basically, these tests should not be executed while I > am programming. Or at least in a thread of a lesser priority. Am I the only > one to experience this? > > > > > > Cheers, > > > Alexandre > > > > > > > > > On 11 Jun 2010, at 09:02, laurent laffont wrote: > > > > > > > On Fri, Jun 11, 2010 at 2:29 PM, Alexandre Bergel < > alexandre(a)bergel.eu> wrote: > > > > Hi Laurent, > > > > > > > > I like Autotest. It is true that I always execute the test after > modifying it. > > > > There are three horizontal panes. Why so? Is it just to open a > debugger when necessary? > > > > > > > > I want to be able to open a debugger from autotest. I agree the GUI > is crap now. > > > > > > > > > > > > We could imagine one standalone button instead with a green color to > say the test I just edited is green, and yellow or red when it fails. In > that case, clicking on the button open a debugger. > > > > > > > > I just feel the window of autotest takes a lot of space in the > screen, without having a real benefit. > > > > > > > > Yes it's true. I'm still thinking on a good GUI. But I'm learning how > to make GUI now :) > > > > > > > > If you look at Autotest package, AutotestView is just the GUI, so we > can implement several GUI and see the best solution. I need to take the time > to do it, repository is read / write so feel free to commit :) > > > > > > > > What I want to have is a dashboard docked on one side of the screen > which acts like you're driving a car. It's always visible, you have to be > able to look quickly at it as when you check the speed of your car, adjust > your drive, .... > > > > > > > > Also another problem with the current version if that if a test > fails, change it and fails again, you don't see it has run (nothing moves in > the GUI). > > > > > > > > Finally, another problem is that you see that a test has failed, but > you don't know why (SUnit TestRunner has the same problem). I want to > display the exception message too. > > > > > > > > Thanks a lot for feedback. > > > > > > > > Laurent Laffont > > > > > > > > http://pharocasts.blogspot.com/ > > > > http://magaloma.blogspot.com/ > > > > > > > > > > > > > > > > Cheers, > > > > Alexandre > > > > > > > > > > > > On 3 Jun 2010, at 17:11, laurent laffont wrote: > > > > > > > > > Hi, > > > > > > > > > > I've written a proof-of-concept for Autotest. Draft/crappy code and > no tests (exploration mode :) but it loads on PharoCore-1.1-11383-beta > image. > > > > > > > > > > Load it: > > > > > Gofer new > > > > > squeaksource: 'Autotest'; > > > > > package: 'Autotest'; > > > > > load > > > > > > > > > > Open it: > > > > > AutotestView open > > > > > (there's en entry in WorldMenu > Tools) > > > > > > > > > > And change a tested method to see the results. > > > > > > > > > > There's a bug I need to find, maybe someone knows: > > > > > - Change Bag>>occurrencesOf: > > > > > - Autotest gives: > > > > > > > > > > 284 run, 281 passes, 0 expected failures, 1 failures, 2 errors, 0 > unexpected passes > > > > > Failures: > > > > > CollectionRootTest>>#test0FixtureIterateTest > > > > > > > > > > Errors: > > > > > CollectionRootTest>>#testBasicCollect > > > > > CollectionRootTest>>#testDoWithout > > > > > > > > > > but in SUnit CollectionRootTest gives > > > > > 0 run, 0 passes, 0 expected failures, 0 failures, 0 errors, 0 > unexpected passes ?? > > > > > > > > > > > > > > > Cheers, > > > > > > > > > > Laurent Laffont > > > > > > > > > > http://pharocasts.blogspot.com/ > > > > > http://magaloma.blogspot.com/ > > > > > > > > > > > > > > > On Thu, Jun 3, 2010 at 6:09 PM, Alexandre Bergel < > alexandre(a)bergel.eu> wrote: > > > > > The idea is excellent. > > > > > > > > > > Cheers, > > > > > Alexandre > > > > > > > > > > > > > > > On 3 Jun 2010, at 10:22, laurent laffont wrote: > > > > > > > > > > > > > > > > > > > > > > > On Thu, Jun 3, 2010 at 3:42 PM, Alexandre Bergel < > alexandre(a)bergel.eu> wrote: > > > > > > > You may have a lot of noise. > > > > > > > > > > > > > > I guess that Ruby uses files as a unit of > development/deployment. The closest Smalltalk/Pharo has is the class and the > package. > > > > > > > > > > > > > > I would suggest that TestCase which would use this feature use > some pragma/method to identify/declare which classes/packages this test > depends upon. Then the "autotest" framework would register such tests and > listen for changes in the given classes/packages, launching required tests > whenever a change happen. > > > > > > > > > > > > > > Additionally, one could declare such a pragma on a single test > method, when this test should be run for a specific class. > > > > > > > > > > > > > > Of course, you also to take care of long running tests, which > you probably want to exclude from auto-testing. > > > > > > > > > > > > I see autotest in Pharo in a slighly different way: When I press > save in the Monticello browser, I have a popup menu which asks me whether > (i) I want to run all the tests or (ii) only the tests that cover that I > changed from the last version. > > > > > > > > > > > > Does this make sense? > > > > > > > > > > > > Please no popup :) What I like in ruby autotest is that I can > quickly look at test results if I want (or not) without stop writing. Often > you want to see your tests failing, as you type / save code. I don't have to > stop writing, click a button, wait test results, go again.... testing is > done in background and I just see notifications whether it's OK or not. > > > > > > > > > > > > So test log in a Transcript is OK for me. > > > > > > > > > > > > > > > > > > For autotest unit of work is file: it runs the test file which > has the same name as the code file, but you can customize this behavior. For > autotest-rails: > > > > > > "A simplified version of Autotest heuristics in this mode would > be: > > > > > > When changing a test file, only this file is run (e.g. > test/unit/foo_test.rb âtest/unit/foo_test.rb). > > > > > > When changing a model file, only associated unit test file is run > (e.g.app/models/foo.rb â test/unit/foo_test.rb). > > > > > > When changing a controller file, associated functional test file > is run (e.g.app/controllers/foo_controller.rb > âtest/functional/foo_controller_test.rb). > > > > > > When changing a fixture file, associated unit test and functional > test are run (e.g.app/fixtures/foos.yml â test/unit/foo_test.rb > +test/functional/foo_controller_test.rb). > > > > > > When changing a helper file, associated functional test file is > run (e.g.app/helpers/foo_helper.rb âtest/functional/foo_controller_test.rb). > > > > > > When changing application_helper.rb file all functional test > files are run (e.g.application_helper.rb â test/functional/*_test.rb). > > > > > > When changing a file under the config directory, all tests are > run." > > > > > > > > > > > > Laurent > > > > > > > > > > > > > > > > > > > > > > > > Cheers, > > > > > > Alexandre > > > > > > -- > > > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > > > Alexandre Bergel http://www.bergel.eu > > > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > > 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 > > > > > > > > > > -- > > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > > Alexandre Bergel http://www.bergel.eu > > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > > 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 > > > > > > > > -- > > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > > Alexandre Bergel http://www.bergel.eu > > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > 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 > > > > > > -- > > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > > Alexandre Bergel http://www.bergel.eu > > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > 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 > > > > > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > 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 > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Aug. 6, 2010

Re: [Pharo-project] Poll: missing libraries to support busines

by Stephan Eggermont

I would like to have native, or at least better, libraries for manipulating PDFs and office files. Stephan

Aug. 6, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Pharo 1.0, Pharo 1.1 and Pharo 1.2

by Miguel Enrique CobÃ¡ MartÃnez

El jue, 05-08-2010 a las 20:57 -0500, Chris Muller escribiÃ³: > Thanks Miguel, you have definitely done better than I ever did at > making a clear, coherent, clean installation. Your solution to the > FlapTab warning is creative, although I'm curious whether it was > possible to simply handle the warning in the load-script and resume > it? Ah, one bad aspect of simply handling / resuming Warning is that > it would tend to hide any future warnings about other classes (which > might be important).. Yes it occurred to me too to use something like that but as I didn't know how to do it I prefered to create an empty class and then delete it. > > Also, I'm curious about why it was necessary to capture and restore > the underscore-assignment setting for 1.1r2. Did I miss some > underscores or is that only to support loading older Magma versions in > 1.1? No, it was because versions previous to 1.1r2 had underscores and to load them I wanted to restore the user preference after installing Magma. In 1.1r2 it isn't really needed, it was too late at night :) I will remove it soon. Cheers -- Miguel CobÃ¡ http://miguel.leugim.com.mx

Aug. 6, 2010

Re: [Pharo-project] Analog to Dolphin's CompositePresenter

by Schwab,Wilhelm K

Gary, I more or less have ComposableMorph doing what I want, but the the insertion of an additional morph (the composite) is restricting the visible area of the morphs it contains. The solution is Dolphin is generally to ensure that any such views have a layout manager that properly positions the children. It would be really nice to make something similar happen here, because it means a lot to reuse. For example, my current goal is to make something that has an image[*] and a few buttons beneath it. That structure would repeat in two tabs or perhaps just side-by-side (the images come in pairs), and that gets repeated many times, probably based on selection in a list to the left of all of this. It seems there should be an obvious way to create something tha is not a full system window, so it can be embedded in other things BUT, it should wrap itself in a system (standard) window on queue, such as #show or somehing. Does this make sense? Am I missing an easy way to do it in Pharo? Bill [*] they are infrared images for added nerdly pleasure :) -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K Sent: Thursday, August 05, 2010 9:41 AM To: Pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] Analog to Dolphin's CompositePresenter Gary, all, I am far from comfortable with Polymorph design and programming, but I have managed stick some controls on standard windows. Now I need to do something that would benefit from composition of an image and a selection mask into something that allows the mask to be edited while "scrubbing" over the image. Then those get paired, and then the pairs go into sequences. The pairing can be done with tabs, and maybe a "copy from peer" button. I think I can manage that. My question is on how to make what in Dolphin is called a CompositePresenter, which are useful critters. They are not directly tied to a top-level shell, but sending #show to them will create just that, mostly for testing purposes. Is there already something like this in Polymorph? ComposableMorph might be a place to start?? Is there a better way? Bill _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 6, 2010

[Pharo-project] Are the bytecodes correct?

by James Ladd

Hi All, I asked about primitives earlier and found out that there are quite a few new primitives than those listed in the blue book. Very useful. See Re: [Pharo-project] Additional Primitives? This leads me to ask, are all the bytecodes as listed in the blue book or are there differences I should know about ? Rgs, James.

Aug. 6, 2010

[Pharo-project] Issue 2756: Morphic Cleansing - Remove use of findA:

by Guillermo Polito

Hi, removing some findA: message sendings i've found: MenuMorph>>doButtonAction "Do the receiver's inherent button action. Makes sense for the kind of MenuMorph that is a wrapper for a single menu-item -- pass it on the the item" (self findA: MenuItemMorph) ifNotNil: [:aMenuItem | aMenuItem doButtonAction] And for me it doesn't make sense :). Even the comment doesn't make sense, because it isn't considering the case where a MenuMorph has multiple MenuItemMorph s. What should be done in cases like that? If it's my code, i should be tempted to delete it or maybe to deprecate it. And I'm really upset because it is a very difficult thing to verify not to break too much other things. So, what is the "official policy" about this cases? :P I don't like to leave it as it is... Cheers, Guille

Aug. 6, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Pharo 1.0, Pharo 1.1 and Pharo 1.2

by Chris Muller

Thanks Miguel, you have definitely done better than I ever did at making a clear, coherent, clean installation. Your solution to the FlapTab warning is creative, although I'm curious whether it was possible to simply handle the warning in the load-script and resume it? Ah, one bad aspect of simply handling / resuming Warning is that it would tend to hide any future warnings about other classes (which might be important).. Also, I'm curious about why it was necessary to capture and restore the underscore-assignment setting for 1.1r2. Did I miss some underscores or is that only to support loading older Magma versions in 1.1? - Chris > Pharo 1.0 > ---------------------- > > - 1.1r1 is the last versions that works in Pharo 1.0. This is because > upstream Magma code depends on code that only exists on Pharo 1.1 and > superior. > > - Pharo 1.0 uses Preferences to enable/disable the underscore as > assigment in code. This release captures current value of this > preference. Enables it for loading Magma and restores it to the original > value after installing Magma. > > Pharo 1.1, Pharo 1.2 > ---------------------- > - The configuration for these Pharo releases is based on the one from > Pharo 1.0. > - 1.1r2 uses a new baseline because Magma has a new package dependency > (Ma files additions). > - Pharo 1.1 and superior uses Scanner allowUnderscoreAsAssignment > instead of Preferences. The current value is captured and restored after > installation of Magma. > - Pharo 1.1 and superior doesn't include FlapTab class anymore. Magma > adds some methods to it so the Configuration adds an empty class named > FlapTab before installing and removes from the system after installing. > This avoid a warning prompt when installing Magma. > - This Configuration includes support for installing Magma releases > previous to 1.1r2. Those versions should install correctly on Pharo 1.1 > and greater but if a lot of problems are detected, the support for those > old versions will be removed, and only 1.1r2 and newer versions will be > supported. > > Now that Pharo has Universes, Magma has different ConfigurationOfMagma > in each universe for Pharo. Each of those Configuration install the > appropriate packages in Pharo. > > Installing Magma > > Pharo 1.0 > --------------- > Evaluate: > > Gofer new > Â Â Â Â squeaksource: 'UniverseForPharo10'; > Â Â Â Â package: 'ConfigurationOfMagma'; > Â Â Â Â load. > > And then, one of: > > ConfigurationOfMagma project latestVersion load: 'Client'. > ConfigurationOfMagma project latestVersion load: 'Server'. > ConfigurationOfMagma project latestVersion load: 'Tester'. > > latestVersion is 1.1r1 > > Pharo 1.1 > --------------- > Evaluate: > > Gofer new > Â Â Â Â squeaksource: 'UniverseForPharo11'; > Â Â Â Â package: 'ConfigurationOfMagma'; > Â Â Â Â load. > > And then, one of: > > ConfigurationOfMagma project latestVersion load: 'Client'. > ConfigurationOfMagma project latestVersion load: 'Server'. > ConfigurationOfMagma project latestVersion load: 'Tester'. > > latestVersion is 1.1r2 > > Pharo 1.2 > --------------- > Evaluate: > > Gofer new > Â Â Â Â squeaksource: 'UniverseForPharo12'; > Â Â Â Â package: 'ConfigurationOfMagma'; > Â Â Â Â load. > > And then, one of: > > ConfigurationOfMagma project latestVersion load: 'Client'. > ConfigurationOfMagma project latestVersion load: 'Server'. > ConfigurationOfMagma project latestVersion load: 'Tester'. > > latestVersion is 1.1r2 > > Comments and bugs accepted. > > Enjoy. > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma >

Aug. 6, 2010