Metacello browser idea...

> IN the shower this morning I was thinking that it would be nice to be able to a senders/implementers from within OmniBrowser based on a Metacello configuration ... one thing lead to another ... so here's the scenario:
>
> Start with a fresh Pharo core, open the MetacelloBrowser (ConfigurationBrowser ... ProjectBrowser...?) and select the create new project menu item, supply a name and an initial version number (development blessing by default)...import configuration/versions into your project as your starting point ... load the imported configurations ... create packages that are automatically added to your configuration and start doing development ...
>
> alternatively you can start with an existing configuration, load, open a version for development and get busy ...
>
> The basic idea is that the management of the project artifacts is done "behind the scenes" and the info is stored in a Metacello version spec ... saving a package version automatically updates the associated configuration ...
>
> Presumably the tools could recognize that you have modified a package that does not have a version open for development and automatically opens a new development version for you ...
>
> I would think that this browser could be built upon the PackageBrowser with additional operations in support of managing configurations ....
>
>
> I know that in the past I have thought of the MetacelloBrowser along the lines of the MonticelloBrowser where you do your work along side the normal development process...and the MetacelloBrowser just supports the work of maintaining the configurataions ....
>
> It seems that integrating the maintenance of the configuration into the development tools themselves makes a lot of sense ...
>
> It is just an idea that came to me in the shower, so that's about it ... I'm swamped with work at the moment, but perhaps someone else will find inspiration...
>
> Dale