MetacelloBrowser ....

In an earlier email I mentioned that there are update issues that need
to be resolved ...

before tackling the update issues, the update logic should be moved into
ConfigurationRoot ... the update logic is currently duplicated for OB
and Morphic ... then the configurationRoto can generate it's own
announcements about structural changes ...

in parallel, I think that improvements can be made to the way that a new
configuration is specified. Right now there is a series of simple dialog
boxes prompting for strings and such when a wizard-style window would be
better with input fields for each of the inputs...this wizard should
also support identifying dependencies between packages and should then
evolve to a tool that can be used for adding packages/projects and
modifying dependencies ... Ideally the wizard would have a Morphic and
OB skin ...

Dale

Yes, Merlin would help to do the wizard.
However, I experienced a number of important issues with the browser. I just tried with a student to create a configuration, but it ended with some complains that no stable version was defined after I added the dependent packages, and some critical issues (package versions were missing in the version).

I will create a test repository on SqueakSource.

Alexandre


On 9 Mar 2011, at 15:07, Dale Henrichs wrote:

> In an earlier email I mentioned that there are update issues that need to be resolved ...
>
> before tackling the update issues, the update logic should be moved into ConfigurationRoot ... the update logic is currently duplicated for OB and Morphic ... then the configurationRoto can generate it's own announcements about structural changes ...
>
> in parallel, I think that improvements can be made to the way that a new configuration is specified. Right now there is a series of simple dialog boxes prompting for strings and such when a wizard-style window would be better with input fields for each of the inputs...this wizard should also support identifying dependencies between packages and should then evolve to a tool that can be used for adding packages/projects and modifying dependencies ... Ideally the wizard would have a Morphic and OB skin ...
>
> Dale

--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On 03/09/2011 11:40 AM, Alexandre Bergel wrote:
> Yes, Merlin would help to do the wizard.
> However, I experienced a number of important issues with the browser. I just tried with a student to create a configuration, but it ended with some complains that no stable version was defined after I added the dependent packages, and some critical issues (package versions were missing in the version).
>
> I will create a test repository on SqueakSource.
>
> Alexandre
>

Alexandre,

Please don't make the tests dependent upon SqueakSource this is the
wrong direction to go for a number of different reasons (if that is what
you are doing) ... Please look at the way that Gofer and Metacello
manages the directory-based resources --- this is much better than
trying to do things with live http repositories ...

Dale

> Please don't make the tests dependent upon SqueakSource this is the wrong direction to go for a number of different reasons (if that is what you are doing) ... Please look at the way that Gofer and Metacello manages the directory-based resources --- this is much better than trying to do things with live http repositories ...


ah ah! I did not mean to write some unit tests based on squeaksource. I was instead thinking about an acceptance tests instead.

Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

On 03/09/2011 02:07 PM, Alexandre Bergel wrote:
>> Please don't make the tests dependent upon SqueakSource this is the wrong direction to go for a number of different reasons (if that is what you are doing) ... Please look at the way that Gofer and Metacello manages the directory-based resources --- this is much better than trying to do things with live http repositories ...
>
>
> ah ah! I did not mean to write some unit tests based on squeaksource. I was instead thinking about an acceptance tests instead.
>
> Alexandre

Ah good ... I plan to (eventually) write tests using the directory-based
repository test resources, just haven't gotten there yet:)

Dale