Re: [Metacello] Metacello ESUG 2010 topics for discussion/decision

> + 1
> If someone could look at simpleLog (because we ned to change this situation)
>
> On Sep 8, 2010, at 10:09 AM, Simon Denier wrote:
>
>> I have no idea whether this issue has been discussed before, and perhaps even solved, but is there an easy way to configure Metacello logging? Right now in Pharo, it goes into the Transcript, and consequently mixes with Compiler warning and other stuff. When we load ConfigurationOfMoose, there are so many items in the Transcript that we lost the first ones. We have to hack the Transcript to dump the interesting info into a file.
>>
>>
>> On 7 sept. 2010, at 21:00, Dale Henrichs wrote:
>>
>>> I've done a search through the Pharo and Metacello mailing lists (and my memory ... but only a little of that:) for open issues on Metacello and I've put together the following list:
>>>
>>> - #pharo1.0, #pharo1.1, #pharo1.2 attributes
>>> - Pharo1.0/Pharo1.1/Pharo1.2 version management
>>> - Metacello for updating pharo core configuration
>>> - ConfigurationOfOmniBrowser differences across versions
>>>
>>> - Pharo Metacello Universes
>>> (http://forum.world.st/ANN-Pharo-Metacello-Universes-td2313088.html#a2313088)
>>> (http://forum.world.st/ANN-Pharo-Metacello-Universes-td2313088i20.html#a2327571)
>>> (http://forum.world.st/Managing-Pharo-external-packages-with-Metacello-please-read-td2218629.html#a2218985)
>>> - AbstractMetacelloConfiguration
>>> (http://forum.world.st/How-can-I-load-metacello-without-OB-td2332353.html#a2335615)
>>>
>>> - default convention
>>> (http://forum.world.st/default-convention-td2316783.html#a2316783)
>>> - programmatic spec creation
>>> (http://forum.world.st/OO-Specs-td2328587.html#a2328587)
>>> - OS dependency
>>> (http://forum.world.st/Loading-platform-specific-code-td2318610.html#a2335791)
>>> - Gofer Project Loader
>>> (http://forum.world.st/ANN-Gofer-Project-Loader-1-0-BETA-td1596389i20.html#a2062909)
>>>
>>> These issues stand out for me, since I need some whiteboard time to wrap my brain around the requirements and then discuss potential solutions.
>>>
>>> I would hope that we can find time at ESUG for discussing these issues and making decisions on as many of the issues as possible (or at least plans of action)...
>>>
>>> If anyone else has issues that they think haven't been adequately covered, now would be a good time to bring up the issue (again) for discussion at ESUG ... if you aren't attending ESUG, refreshing the issue for consideration by those who are present is still a good idea.
>>>
>>> Dale
>> --
>> Simon
>>
>>
>>
>