I don't have any time by now, but It would be better to have only one log tool, maybe with extensions.� Not 3 different ones.� There should be a way to have an integrated version that more or less suits the most people.

Maybe the most simple solution is a set of adapters to make the three tools polymorphic, and a metacello conf to load them.

On Fri, Jul 16, 2010 at 9:36 AM, Germ�n Arduino <garduino@gmail.com> wrote:
hehe, I'm not against Metacello, but will not write a conf to this tiny project.

Not by now :)

2010/7/16 Mariano Martinez Peck <marianopeck@gmail.com>:
> Another advantage of using Metacello is that even if you don't have
> dependencies, it helps you to release and define stable versions. How do you
> know which mcz should I use ? which one is the stable ?
>
> If in 3 months I download it again (the latest) in the same Pharo image,
> will it work?� You cannot know it.
>
> 2010/7/16 laurent laffont <laurent.laffont@gmail.com>
>>
>> On Fri, Jul 16, 2010 at 1:12 PM, Germ�n Arduino <garduino@gmail.com>
>> wrote:
>>>
>>> Hi Alex:
>>>
>>> Yes I know how to write a configuration (I did one for Iliad) but to
>>> this case in particular I think have not sense. My logger is only one
>>> class with a few methods.....Easily you can include the class on your
>>> own project.
>>
>> Having a configuration for all tools means there's one way to load every
>> package. That means we can automate with the Hudson server and check that
>> every package can load on Pharo. It's also easier for newbies, they can
>> start by learning only one (documented) way to load a tool.
>> That's a great strength in Ruby world, there's a gem for every lib.
>> Anyway, I can do it as it's an opportunity to record a screencast for
>> Pharocasts to show how to write a ConfigurationOfXXX and put it on
>> MetacelloRepository. (if anybody else want to do it I can help)
>> Cheers,
>> Laurent
>>
>>
>>
>>>
>>> Cheers.
>>> Germ�n.
>>>
>>>
>>>
>>> 2010/7/15 Alexandre Bergel <alexandre@bergel.eu>:
>>> > Hi Germ�n,
>>> >
>>> > Configuration may be a bit tricky to write time to time. However, they
>>> > are indispensable to manage dependencies.
>>> > Suppose I want to use your logger in one of my software. The dependency
>>> > I will introduce is easier if you have a configuration.
>>> >
>>> > It takes 4,5 minutes to write one with the tutorial:
>>> > ConfigurationOfMetacello project latestVersion load: #('Tutorial').
>>> > ProfStef goOn: MetacelloCreateConfigurationTutorial.
>>> >
>>> >
>>> > Cheers,
>>> > Alexandre
>>> >
>>> >
>>> > On 15 Jul 2010, at 13:45, Germ�n Arduino wrote:
>>> >
>>> >> Hi Alex:
>>> >>
>>> >> I have not a configuration for this package, I think is not necessary,
>>> >> being that is really very simple.
>>> >>
>>> >> On squeak-dev the people is talking about these topics, on the thread
>>> >> "About Configurations".
>>> >>
>>> >> Cheers.
>>> >> Germ�n.
>>> >>
>>> >>
>>> >>
>>> >> 2010/7/15 Alexandre Bergel <alexandre@bergel.eu>:
>>> >>>> ok, I added the documentation of my own package......Took me 15' :)
>>> >>>
>>> >>> Hi Germ�n,
>>> >>>
>>> >>> Do you have a configuration for this?
>>> >>> Thanks for the documentation
>>> >>>
>>> >>> Cheers,
>>> >>> Alexandre
>>> >>>
>>> >>>>
>>>
>>> _______________________________________________
>>> Pharo-project mailing list
>>> Pharo-project@lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>
>>
>> _______________________________________________
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>
> _______________________________________________
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

_______________________________________________
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project