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

Re: [Pharo-dev] Smalltalkhub ci image

by Yuriy Tymchuk

I was using a latest stable build and it works ok. Uko On 03 Dec 2013, at 15:58, Stephan Eggermont <stephan(a)stack.nl> wrote: > The smalltalkhub build has been red for quite some time now. If I want to run a hub, > should I take the latest build? > > Stephan

Dec. 3, 2013

Re: [Pharo-dev] Roassal Bug related to Athens?

by kilon alios

you dont have to wait for my example as i said checkSession is already the example checkSession session == Smalltalk session ifFalse: [ "just reset the surface" surface := nil. session := Smalltalk session. ] as you can see here essentially we compare session if they differ then we know we need to reinitialize all our external resources in this example surface . Not that it assigns surfaces as nil but you will need to fully reinitialize the surface cause otherwise you will have a non existent surface still. In this class a nill surface is reinitialized by another method. Also I like to note here that Roassal Easel appear also not to check sessions and exhibits the known problem if image is stored with Easel open. Its something Roassal people would need to look at. On Tue, Dec 3, 2013 at 4:51 PM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: > > > > On Tue, Dec 3, 2013 at 3:46 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > >> You are correct but so is Igor. Managing external resources has to do >> with VM and Nativeboost itself and not with Athens. This could happen with >> any other library. >> >> Session aware code is actually very easy to do and its explained >> Athens-Tutorial package in AthensViewMorph>>checkSession . Its just 2 lines >> of code. >> >> In step2 method there is a relevant comment >> >> "IMPORTANT NOTE: >> the surface which we will create at this step will be used in later steps. >> This means that if you resize the window (changing the view size), you >> may need to recreate surface. >> Also, since surface uses external resources, quitting an image and >> restarting it, will also require to >> create a new surface, because the one from previous session will be no >> longer accessible. >> " >> > > Ok. Tx. That's very useful info. I'll have a look. > > >> >> but there is no mention to check the checkSession method for an example >> how sessions can be handled. I think this deserves a separate step by >> itself with a nice example. Igor you want me to give me commit rights to >> Athens repo to add that myself ? >> > > And if you add the example to Athens, please let me know. > > >> >> >> On Tue, Dec 3, 2013 at 4:21 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: >> >>> >>> On Tue, Dec 3, 2013 at 2:29 PM, Igor Stasenko <siguctua(a)gmail.com>wrote: >>> >>>> >>>> >>>> >>>> On 3 December 2013 14:18, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: >>>> >>>>> Igor, >>>>> >>>>> I had a look at Athens demo to understand how to manage sessions and >>>>> surfaces because Roassal uses AthensSurface and there is a defensive >>>>> mechanism in place in Roassal to initialize the surface in case it is not >>>>> done. In the meantime, I have discovered that the red rectangle bug is >>>>> present in Athens demos as well. >>>>> >>>>> So, to reproduce. >>>>> AthensFlakeDemo new openInWorld >>>>> save image >>>>> open image >>>>> >>>> >>>>> I tested in Moose 5.0. >>>>> >>>>> 1. Should I open a bug entry in Pharo? >>>>> >>>>> only if you intend to fix it. because this demo was not intended to be >>>> 'fully featured, end-user compatible >>>> and fool-proof demo'. it just a demo to show animation and discard it, >>>> but if you insist this is a bug, >>>> feel free to fix it. >>>> >>> >>> Unfortunately, I wont have time for this. For me it would have been >>> good, had Athens provided an example of session management as a good client >>> so that example-oriented people like me could understand easily. Because, >>> otherwise, I'll have to look at the code of NativeBoost and that adds to >>> the level of complexity because I would do things with trial and error. >>> >>> >>>> >>>> >>>>> 2. With my superficial knowledge of Athens, my guess is that the >>>>> session management can be done in Athens so that Roassal (and other tools >>>>> built on top of Athens) do not need to do it. May be it is the case already >>>>> but the demos are not using it then. >>>>> >>>>> I disagree. >>>> >>> Because then, files can also open/close and delete themselves >>>> automatically, so you will be left only to do reading and writing... >>>> Resource management is an application-level responsibility, not >>>> framework level. >>>> I cannot predict in Athens, how often one wants to create/destroy or >>>> (re)use surfaces, and therefore i cannot >>>> create and dispose them when i see fit within framework. >>>> Correct me if i wrong. >>>> >>> >>> I think this doesn't compare to file handling because there are many >>> types of operations possible on files and that are application-specific. >>> Here resource management is actually exception-handling: I should not give >>> to my client a surface that does not exist any more. Now, of course, if >>> there is some application-level intelligence is involved, we cannot put >>> that in the framework. >>> >>> But I would understand the absence of such a mechanism in the framework >>> but then a tutorial should explain to novices/first-timers how to do it. >>> >>> Usman >>> >>> >>> >>> >>>> >>>> >>>>> Usman >>>>> >>>>> >>>>> >>>>> On Mon, Dec 2, 2013 at 5:14 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: >>>>> >>>>>> Hello Igor, >>>>>> >>>>>> Moose 5.0 is using Athens as default canvas for Roassal and we have >>>>>> bug with Roassal that seems to be related to Athens. >>>>>> http://code.google.com/p/moose-technology/issues/detail?id=1019 >>>>>> >>>>>> I think it is related to the fact that we create a surface in the OS >>>>>> with Athens and once we quit the image, the surface is destroyed as well. >>>>>> So, when image is restarted with the visualization trying to use the >>>>>> surface, we get the error. >>>>>> >>>>>> Could you point to what possibly can be done to avoid this error? >>>>>> Merely checking the existence of an appropriate drawing surface in Athens >>>>>> every time visualization is drawn, would it suffice? >>>>>> >>>>>> regards, >>>>>> >>>>>> Usman >>>>>> >>>>> >>>>> >>>> >>>> >>>> -- >>>> Best regards, >>>> Igor Stasenko. >>>> >>> >>> >> >

Dec. 3, 2013

Re: [Pharo-dev] Roassal Bug related to Athens?

by Usman Bhatti

On Tue, Dec 3, 2013 at 3:46 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > You are correct but so is Igor. Managing external resources has to do with > VM and Nativeboost itself and not with Athens. This could happen with any > other library. > > Session aware code is actually very easy to do and its explained > Athens-Tutorial package in AthensViewMorph>>checkSession . Its just 2 lines > of code. > > In step2 method there is a relevant comment > > "IMPORTANT NOTE: > the surface which we will create at this step will be used in later steps. > This means that if you resize the window (changing the view size), you > may need to recreate surface. > Also, since surface uses external resources, quitting an image and > restarting it, will also require to > create a new surface, because the one from previous session will be no > longer accessible. > " > Ok. Tx. That's very useful info. I'll have a look. > > but there is no mention to check the checkSession method for an example > how sessions can be handled. I think this deserves a separate step by > itself with a nice example. Igor you want me to give me commit rights to > Athens repo to add that myself ? > And if you add the example to Athens, please let me know. > > > On Tue, Dec 3, 2013 at 4:21 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: > >> >> On Tue, Dec 3, 2013 at 2:29 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> >>> >>> >>> >>> On 3 December 2013 14:18, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: >>> >>>> Igor, >>>> >>>> I had a look at Athens demo to understand how to manage sessions and >>>> surfaces because Roassal uses AthensSurface and there is a defensive >>>> mechanism in place in Roassal to initialize the surface in case it is not >>>> done. In the meantime, I have discovered that the red rectangle bug is >>>> present in Athens demos as well. >>>> >>>> So, to reproduce. >>>> AthensFlakeDemo new openInWorld >>>> save image >>>> open image >>>> >>> >>>> I tested in Moose 5.0. >>>> >>>> 1. Should I open a bug entry in Pharo? >>>> >>>> only if you intend to fix it. because this demo was not intended to be >>> 'fully featured, end-user compatible >>> and fool-proof demo'. it just a demo to show animation and discard it, >>> but if you insist this is a bug, >>> feel free to fix it. >>> >> >> Unfortunately, I wont have time for this. For me it would have been good, >> had Athens provided an example of session management as a good client so >> that example-oriented people like me could understand easily. Because, >> otherwise, I'll have to look at the code of NativeBoost and that adds to >> the level of complexity because I would do things with trial and error. >> >> >>> >>> >>>> 2. With my superficial knowledge of Athens, my guess is that the >>>> session management can be done in Athens so that Roassal (and other tools >>>> built on top of Athens) do not need to do it. May be it is the case already >>>> but the demos are not using it then. >>>> >>>> I disagree. >>> >> Because then, files can also open/close and delete themselves >>> automatically, so you will be left only to do reading and writing... >>> Resource management is an application-level responsibility, not >>> framework level. >>> I cannot predict in Athens, how often one wants to create/destroy or >>> (re)use surfaces, and therefore i cannot >>> create and dispose them when i see fit within framework. >>> Correct me if i wrong. >>> >> >> I think this doesn't compare to file handling because there are many >> types of operations possible on files and that are application-specific. >> Here resource management is actually exception-handling: I should not give >> to my client a surface that does not exist any more. Now, of course, if >> there is some application-level intelligence is involved, we cannot put >> that in the framework. >> >> But I would understand the absence of such a mechanism in the framework >> but then a tutorial should explain to novices/first-timers how to do it. >> >> Usman >> >> >> >> >>> >>> >>>> Usman >>>> >>>> >>>> >>>> On Mon, Dec 2, 2013 at 5:14 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: >>>> >>>>> Hello Igor, >>>>> >>>>> Moose 5.0 is using Athens as default canvas for Roassal and we have >>>>> bug with Roassal that seems to be related to Athens. >>>>> http://code.google.com/p/moose-technology/issues/detail?id=1019 >>>>> >>>>> I think it is related to the fact that we create a surface in the OS >>>>> with Athens and once we quit the image, the surface is destroyed as well. >>>>> So, when image is restarted with the visualization trying to use the >>>>> surface, we get the error. >>>>> >>>>> Could you point to what possibly can be done to avoid this error? >>>>> Merely checking the existence of an appropriate drawing surface in Athens >>>>> every time visualization is drawn, would it suffice? >>>>> >>>>> regards, >>>>> >>>>> Usman >>>>> >>>> >>>> >>> >>> >>> -- >>> Best regards, >>> Igor Stasenko. >>> >> >> >

Dec. 3, 2013

Re: [Pharo-dev] Roassal Bug related to Athens?

by kilon alios

You are correct but so is Igor. Managing external resources has to do with VM and Nativeboost itself and not with Athens. This could happen with any other library. Session aware code is actually very easy to do and its explained Athens-Tutorial package in AthensViewMorph>>checkSession . Its just 2 lines of code. In step2 method there is a relevant comment "IMPORTANT NOTE: the surface which we will create at this step will be used in later steps. This means that if you resize the window (changing the view size), you may need to recreate surface. Also, since surface uses external resources, quitting an image and restarting it, will also require to create a new surface, because the one from previous session will be no longer accessible. " but there is no mention to check the checkSession method for an example how sessions can be handled. I think this deserves a separate step by itself with a nice example. Igor you want me to give me commit rights to Athens repo to add that myself ? On Tue, Dec 3, 2013 at 4:21 PM, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: > > On Tue, Dec 3, 2013 at 2:29 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> >> >> >> On 3 December 2013 14:18, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: >> >>> Igor, >>> >>> I had a look at Athens demo to understand how to manage sessions and >>> surfaces because Roassal uses AthensSurface and there is a defensive >>> mechanism in place in Roassal to initialize the surface in case it is not >>> done. In the meantime, I have discovered that the red rectangle bug is >>> present in Athens demos as well. >>> >>> So, to reproduce. >>> AthensFlakeDemo new openInWorld >>> save image >>> open image >>> >> >>> I tested in Moose 5.0. >>> >>> 1. Should I open a bug entry in Pharo? >>> >>> only if you intend to fix it. because this demo was not intended to be >> 'fully featured, end-user compatible >> and fool-proof demo'. it just a demo to show animation and discard it, >> but if you insist this is a bug, >> feel free to fix it. >> > > Unfortunately, I wont have time for this. For me it would have been good, > had Athens provided an example of session management as a good client so > that example-oriented people like me could understand easily. Because, > otherwise, I'll have to look at the code of NativeBoost and that adds to > the level of complexity because I would do things with trial and error. > > >> >> >>> 2. With my superficial knowledge of Athens, my guess is that the session >>> management can be done in Athens so that Roassal (and other tools built on >>> top of Athens) do not need to do it. May be it is the case already but the >>> demos are not using it then. >>> >>> I disagree. >> > Because then, files can also open/close and delete themselves >> automatically, so you will be left only to do reading and writing... >> Resource management is an application-level responsibility, not framework >> level. >> I cannot predict in Athens, how often one wants to create/destroy or >> (re)use surfaces, and therefore i cannot >> create and dispose them when i see fit within framework. >> Correct me if i wrong. >> > > I think this doesn't compare to file handling because there are many types > of operations possible on files and that are application-specific. Here > resource management is actually exception-handling: I should not give to my > client a surface that does not exist any more. Now, of course, if there is > some application-level intelligence is involved, we cannot put that in the > framework. > > But I would understand the absence of such a mechanism in the framework > but then a tutorial should explain to novices/first-timers how to do it. > > Usman > > > > >> >> >>> Usman >>> >>> >>> >>> On Mon, Dec 2, 2013 at 5:14 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: >>> >>>> Hello Igor, >>>> >>>> Moose 5.0 is using Athens as default canvas for Roassal and we have bug >>>> with Roassal that seems to be related to Athens. >>>> http://code.google.com/p/moose-technology/issues/detail?id=1019 >>>> >>>> I think it is related to the fact that we create a surface in the OS >>>> with Athens and once we quit the image, the surface is destroyed as well. >>>> So, when image is restarted with the visualization trying to use the >>>> surface, we get the error. >>>> >>>> Could you point to what possibly can be done to avoid this error? >>>> Merely checking the existence of an appropriate drawing surface in Athens >>>> every time visualization is drawn, would it suffice? >>>> >>>> regards, >>>> >>>> Usman >>>> >>> >>> >> >> >> -- >> Best regards, >> Igor Stasenko. >> > >

Dec. 3, 2013

Re: [Pharo-dev] Versionner Impressions

by Stephan Eggermont

Hi Sean, Didi you compare it to Metaceller in Moose? Stephan

Dec. 3, 2013

Re: [Pharo-dev] Grease conflicts #packages with RPackage

by Stephan Eggermont

I could copy the separate packages, but not the slice. Please note that the added test is expected to fail on all builds containing Grease-Core. Stephan

Dec. 3, 2013

Re: [Pharo-dev] Roassal Bug related to Athens?

by Usman Bhatti

On Tue, Dec 3, 2013 at 2:29 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > > > > On 3 December 2013 14:18, Usman Bhatti <usman.bhatti(a)gmail.com> wrote: > >> Igor, >> >> I had a look at Athens demo to understand how to manage sessions and >> surfaces because Roassal uses AthensSurface and there is a defensive >> mechanism in place in Roassal to initialize the surface in case it is not >> done. In the meantime, I have discovered that the red rectangle bug is >> present in Athens demos as well. >> >> So, to reproduce. >> AthensFlakeDemo new openInWorld >> save image >> open image >> > >> I tested in Moose 5.0. >> >> 1. Should I open a bug entry in Pharo? >> >> only if you intend to fix it. because this demo was not intended to be > 'fully featured, end-user compatible > and fool-proof demo'. it just a demo to show animation and discard it, but > if you insist this is a bug, > feel free to fix it. > Unfortunately, I wont have time for this. For me it would have been good, had Athens provided an example of session management as a good client so that example-oriented people like me could understand easily. Because, otherwise, I'll have to look at the code of NativeBoost and that adds to the level of complexity because I would do things with trial and error. > > >> 2. With my superficial knowledge of Athens, my guess is that the session >> management can be done in Athens so that Roassal (and other tools built on >> top of Athens) do not need to do it. May be it is the case already but the >> demos are not using it then. >> >> I disagree. > Because then, files can also open/close and delete themselves > automatically, so you will be left only to do reading and writing... > Resource management is an application-level responsibility, not framework > level. > I cannot predict in Athens, how often one wants to create/destroy or > (re)use surfaces, and therefore i cannot > create and dispose them when i see fit within framework. > Correct me if i wrong. > I think this doesn't compare to file handling because there are many types of operations possible on files and that are application-specific. Here resource management is actually exception-handling: I should not give to my client a surface that does not exist any more. Now, of course, if there is some application-level intelligence is involved, we cannot put that in the framework. But I would understand the absence of such a mechanism in the framework but then a tutorial should explain to novices/first-timers how to do it. Usman > > >> Usman >> >> >> >> On Mon, Dec 2, 2013 at 5:14 PM, Usman Bhatti <usman.bhatti(a)gmail.com>wrote: >> >>> Hello Igor, >>> >>> Moose 5.0 is using Athens as default canvas for Roassal and we have bug >>> with Roassal that seems to be related to Athens. >>> http://code.google.com/p/moose-technology/issues/detail?id=1019 >>> >>> I think it is related to the fact that we create a surface in the OS >>> with Athens and once we quit the image, the surface is destroyed as well. >>> So, when image is restarted with the visualization trying to use the >>> surface, we get the error. >>> >>> Could you point to what possibly can be done to avoid this error? Merely >>> checking the existence of an appropriate drawing surface in Athens every >>> time visualization is drawn, would it suffice? >>> >>> regards, >>> >>> Usman >>> >> >> > > > -- > Best regards, > Igor Stasenko. >

Dec. 3, 2013

Re: [Pharo-dev] Opal hook?

by ClÃ©ment Bera

*do you know if the OCUndeclaredVariable is raised for unknown superclass?* this code: AnUnknownClass subclass: #Adaptor1Example instanceVariableNames: 'customers accountID address name phoneNumber' classVariableNames: '' poolDictionaries: '' category: 'Examples-Cookbook' is run as a Do It. In Do It, unknown variables (as here AnUnknownClass) raise an OCUndeclaredVariableWarning. For example, running: AnUnknownClass subclass: #Adaptor1Example instanceVariableNames: 'customers accountID address name phoneNumber' classVariableNames: '' poolDictionaries: '' category: 'Examples-Cookbook' executes the default action for OCUndeclaredVariableWarning, which is opening a pop-up titled: "Unknown variable ...". Here the error is raised at *compilation time, *therefore it would have* no effect to wrap this with a #on:do: * [ AnUnknownClass subclass: #Adaptor1Example instanceVariableNames: 'customers accountID address name phoneNumber' classVariableNames: '' poolDictionaries: '' category: 'Examples-Cookbook' ] on: OCSemanticWarning do: [ ] ==> same problem. Now if you do: [ OpalCompiler new evaluate: 'AnUnknownClass subclass: #Adaptor1Example instanceVariableNames: ''customers accountID address name phoneNumber'' classVariableNames: '''' poolDictionaries: '''' category: ''Examples-Cookbook''' ] on: OCSemanticWarning do: [ :e | e halt ] Here we catch the error, and you can handle it. Now it is not easily possible to resume the error, because you want a global instead and Opal expects a temp (there are way to resume but with very deep stack manipulation that I do not want to show to young pharoers present on this mailing list). So the best is to retry it. One solution is therefore: [ OpalCompiler new evaluate: 'AnUnknownClass subclass: #Adaptor1Example instanceVariableNames: ''customers accountID address phoneNumber'' classVariableNames: '''' poolDictionaries: '''' category: ''Examples-Cookbook''' ] on: OCSemanticWarning do: [ :e | Smalltalk at: e node name put: StubRootClass. e retry ] with e node name answering #AnUnknownClass here. Now you need to make sure that the exception block is executed for the case of a missing superclass and not something else or you will end up creating loads of globals. The exception block should be something similar to: [ :e | e node name first isUppercase and: [ "some condition" ] ifTrue: [ Smalltalk at: e node name put: StubRootClass. ^ e retry ]. e pass ] *How to undefined and OCUndeclaredVariableWarning relate?* In your case, while loading from Monticello the code is compiled and evaluated in non interactive mode. Therefore it cannot trigger the default action of OCUndeclaredVariableWarning which is a UI event. So it sets by default the unknown global to: Undeclared at: varName asSymbol put: nil. OCUndeclaredVariable new name: varName asSymbol in: OCUndeclaredVariableWarning >>defaultAction which then later triggers the code in UndefinedObject. 2013/12/3 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Dec 3, 2013, at 11:20 AM, ClÃ©ment Bera <bera.clement(a)gmail.com> wrote: > > Then for your project replace ProtoObject by StubRootClass in > UndefinedObject>>subclass:instanceVariableNames:classVariableNames: > poolDictionaries:category: it will work. > > > yes but this is ugly because I do not want override. > So I will introduce an exception so that we can do that in a clean way. > > > An alternative is to catch OCSemanticWarning or its subclass > OCUndeclaredVariableWarning while loading the new classes and execute > another code instead of the default action in the exception handling block > > > > do you know if the OCUndeclaredVariable is raised for unknown superclass? > How to undefined and OCUndeclaredVariableWarning relate? > > Stef > > > > 2013/12/3 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > >> > Well if the class does not exists it calls the method on >> UndefinedObject (UndeclaredBinding). And you have: >> >> I will check and see if I can set up a hook because having classes >> subclasses of protoobject is not a good idea >> when loading broken code. >> >> > UndefinedObject>>subclass: nameOfClass >> > instanceVariableNames: instVarNames >> > classVariableNames: classVarNames >> > poolDictionaries: poolDictnames >> > category: category >> > "Calling this method is now considered an accident. If you >> really want to create a class with a nil superclass, then create the class >> and then set the superclass using #superclass:" >> > self traceCr: ('Attempt to create ', nameOfClass, ' as a subclass >> of nil. Possibly a class is being loaded before its superclass.'). >> > ^ProtoObject >> > subclass: nameOfClass >> > instanceVariableNames: instVarNames >> > classVariableNames: classVarNames >> > poolDictionaries: poolDictnames >> > category: category >> > >> > The best is to set manually the superclass after with #superclass: >> >> No because I have no idea what are the classes whose superclasses are not >> in the image. >> With a proper hook I could just say >> if the superclass is unknow please use the "StubRootClass" of my >> framework. >> else let the system handles it. >> >> Stef >> > > >

Dec. 3, 2013

Re: [Pharo-dev] Unifying Testing Ideas

by Dennis Schetinin

Sure, there are objects: it's Smalltalk, methods are obects too :) That's really correct: SUnit is the simplest thing that (still) works. But is it still enough? Isn't it a time to make more steps and improve? I just mean it would be great to have test as distinct object that I can explore, add certain behavior and properties to, relate to other objects in system (other tests, test suites, groups and more), open in specific tools (to be yet created), log all runs and resultsâ¦ and associate with frameworks that it should be run withinâ¦ In general, to create a full-fledged and easy-to-use environment for TDD and controlling all the development steps with tests, use them as documentation, etc. etc. etc. -- Best regards, Dennis Schetinin 2013/12/3 Esteban A. Maringolo <emaringolo(a)gmail.com> > 2013/12/3 Dennis Schetinin <chaetal(a)gmail.com> > > > > I see the only correct way to build a good testing environment: tests > should be basically objects, not methods. > > They are objects. Instances of TestCase. > > But for simplicity they're implemented in a single "factory" class, > the TestCase subclass... > > > > Esteban A. Maringolo > >

Dec. 3, 2013

Re: [Pharo-dev] Versionner Impressions

by Christophe Demarey

Hi Sean, Le 3 dÃ©c. 2013 Ã 06:43, Sean P. DeNigris a Ã©crit : > Wow, it's light years ahead of where I last saw it! It is already much better > than writing configs by hand. I was able to do about 75% via the UI to go > from nothing, to an initial commit with a baseline including dependent > projects and my packages. > > A few notes. It would be nice to be able... > â¢ to specify other repos for dependent project Can you explain me your use case? > â¢ to select the project's repo from a list if it's already known by the > system instead of having to type Do you mean for a new project? Yes, maybe the developer has already done some commits. I will add that. > Bugs: > â¢ I added BabyMock as a dependent project, Versionner showed "(stable)" in > the UI, but when it added it to the baseline, it was loading bleeding edge Indeed. Looks like a bug. > â¢ Added packages were a mixture of strings and symbols i.e. 'FMOD', > #FMODSpecification, 'BabyMock-Core' should be easy to fix > â¢ I added a main repository to Versionner, but it didn't appear in baseline > when clicked "update dev" I also noticed that. It is a bug in MetacelloToolBox. I need to catch it. > â¢ If you accidentally navigate away from the version you're viewing, e.g. > by clicking on another version, all changes are lost without warning It is the first item on my list because you can loose your time here. I will add a warning. > Keep up the great work. This is a very important tool! By the way, Versionner will be part of Pharo 3.0 image in a few days. Thanks for your kind feedbacks. Christophe.

Dec. 3, 2013