Package organization: from structural to ...

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Package organization: from structural to ...

Stéphane Ducasse
Hi guys

I'm starting to work on http://code.google.com/p/pharo/issues/detail?id=2635
        which I split into
                http://code.google.com/p/pharo/issues/detail?id=2875

Now after I will apply Seaside decomposition to have Test "in their package"

Tests-ToolBuilder
        -> ToolBuilder-Test

Now in addition I would like to have

Kernel
        the right stuff there

Collection-Kernel
        Containing what is needed for the core
        I prefer that to Kernel-Collection
        since people that want to look at collection will fin it grouped in Collection
        but the kernel means that we know that they will be for the kernel
        Now for Array we will have

                Array will be in
                Collection-Kernel
                Collection-Kernel-Test

Stef
_______________________________________________
Pharo-users mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
Reply | Threaded
Open this post in threaded view
|

Re: Package organization: from structural to ...

Igor Stasenko
Maybe
Collections-Kernel
i.e. not Collection, but Collections
?

On 27 August 2010 16:37, Stéphane Ducasse <[hidden email]> wrote:

> Hi guys
>
> I'm starting to work on http://code.google.com/p/pharo/issues/detail?id=2635
>        which I split into
>                http://code.google.com/p/pharo/issues/detail?id=2875
>
> Now after I will apply Seaside decomposition to have Test "in their package"
>
> Tests-ToolBuilder
>        -> ToolBuilder-Test
>
> Now in addition I would like to have
>
> Kernel
>        the right stuff there
>
> Collection-Kernel
>        Containing what is needed for the core
>        I prefer that to Kernel-Collection
>        since people that want to look at collection will fin it grouped in Collection
>        but the kernel means that we know that they will be for the kernel
>        Now for Array we will have
>
>                Array will be in
>                Collection-Kernel
>                Collection-Kernel-Test
>
> Stef
> _______________________________________________
> Pharo-users mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>



--
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-users mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
Reply | Threaded
Open this post in threaded view
|

Re: Package organization: from structural to ...

Stéphane Ducasse
yes!
Now I would love to have time doing something instead of talking (nothing against you - now I can print here ----)

Stef

On Aug 30, 2010, at 4:22 PM, Igor Stasenko wrote:

> Maybe
> Collections-Kernel
> i.e. not Collection, but Collections
> ?
>
> On 27 August 2010 16:37, Stéphane Ducasse <[hidden email]> wrote:
>> Hi guys
>>
>> I'm starting to work on http://code.google.com/p/pharo/issues/detail?id=2635
>>        which I split into
>>                http://code.google.com/p/pharo/issues/detail?id=2875
>>
>> Now after I will apply Seaside decomposition to have Test "in their package"
>>
>> Tests-ToolBuilder
>>        -> ToolBuilder-Test
>>
>> Now in addition I would like to have
>>
>> Kernel
>>        the right stuff there
>>
>> Collection-Kernel
>>        Containing what is needed for the core
>>        I prefer that to Kernel-Collection
>>        since people that want to look at collection will fin it grouped in Collection
>>        but the kernel means that we know that they will be for the kernel
>>        Now for Array we will have
>>
>>                Array will be in
>>                Collection-Kernel
>>                Collection-Kernel-Test
>>
>> Stef
>> _______________________________________________
>> Pharo-users mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>>
>
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
> _______________________________________________
> Pharo-users mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users


_______________________________________________
Pharo-users mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
Reply | Threaded
Open this post in threaded view
|

Re: Package organization: from structural to ...

Igor Stasenko
On 30 August 2010 17:53, Stéphane Ducasse <[hidden email]> wrote:
> yes!
> Now I would love to have time doing something instead of talking (nothing against you - now I can print here ----)
>

Rule of thumb: Measure 7 times, before cutting.

But yes, i am more talking than doing in recent months. Accumulating
energy for next crazy coding sesison :)

> Stef
>
> On Aug 30, 2010, at 4:22 PM, Igor Stasenko wrote:
>
>> Maybe
>> Collections-Kernel
>> i.e. not Collection, but Collections
>> ?
>>
>> On 27 August 2010 16:37, Stéphane Ducasse <[hidden email]> wrote:
>>> Hi guys
>>>
>>> I'm starting to work on http://code.google.com/p/pharo/issues/detail?id=2635
>>>        which I split into
>>>                http://code.google.com/p/pharo/issues/detail?id=2875
>>>
>>> Now after I will apply Seaside decomposition to have Test "in their package"
>>>
>>> Tests-ToolBuilder
>>>        -> ToolBuilder-Test
>>>
>>> Now in addition I would like to have
>>>
>>> Kernel
>>>        the right stuff there
>>>
>>> Collection-Kernel
>>>        Containing what is needed for the core
>>>        I prefer that to Kernel-Collection
>>>        since people that want to look at collection will fin it grouped in Collection
>>>        but the kernel means that we know that they will be for the kernel
>>>        Now for Array we will have
>>>
>>>                Array will be in
>>>                Collection-Kernel
>>>                Collection-Kernel-Test
>>>
>>> Stef
>>> _______________________________________________
>>> Pharo-users mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>>>
>>
>>
>>
>> --
>> Best regards,
>> Igor Stasenko AKA sig.
>>
>> _______________________________________________
>> Pharo-users mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>
>
> _______________________________________________
> Pharo-users mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>



--
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-users mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
Reply | Threaded
Open this post in threaded view
|

Re: Package organization: from structural to ...

Stéphane Ducasse

On Aug 30, 2010, at 6:43 PM, Igor Stasenko wrote:

> On 30 August 2010 17:53, Stéphane Ducasse <[hidden email]> wrote:
>> yes!
>> Now I would love to have time doing something instead of talking (nothing against you - now I can print here ----)
>>
>
> Rule of thumb: Measure 7 times, before cutting.
>
> But yes, i am more talking than doing in recent months. Accumulating
> energy for next crazy coding sesison :)
lol

I was more talking for me. I have a lot of things to do that I should get more focused :)

Stef


>
>> Stef
>>
>> On Aug 30, 2010, at 4:22 PM, Igor Stasenko wrote:
>>
>>> Maybe
>>> Collections-Kernel
>>> i.e. not Collection, but Collections
>>> ?
>>>
>>> On 27 August 2010 16:37, Stéphane Ducasse <[hidden email]> wrote:
>>>> Hi guys
>>>>
>>>> I'm starting to work on http://code.google.com/p/pharo/issues/detail?id=2635
>>>>        which I split into
>>>>                http://code.google.com/p/pharo/issues/detail?id=2875
>>>>
>>>> Now after I will apply Seaside decomposition to have Test "in their package"
>>>>
>>>> Tests-ToolBuilder
>>>>        -> ToolBuilder-Test
>>>>
>>>> Now in addition I would like to have
>>>>
>>>> Kernel
>>>>        the right stuff there
>>>>
>>>> Collection-Kernel
>>>>        Containing what is needed for the core
>>>>        I prefer that to Kernel-Collection
>>>>        since people that want to look at collection will fin it grouped in Collection
>>>>        but the kernel means that we know that they will be for the kernel
>>>>        Now for Array we will have
>>>>
>>>>                Array will be in
>>>>                Collection-Kernel
>>>>                Collection-Kernel-Test
>>>>
>>>> Stef
>>>> _______________________________________________
>>>> Pharo-users mailing list
>>>> [hidden email]
>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>>>>
>>>
>>>
>>>
>>> --
>>> Best regards,
>>> Igor Stasenko AKA sig.
>>>
>>> _______________________________________________
>>> Pharo-users mailing list
>>> [hidden email]
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>>
>>
>> _______________________________________________
>> Pharo-users mailing list
>> [hidden email]
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users
>>
>
>
>
> --
> Best regards,
> Igor Stasenko AKA sig.
>
> _______________________________________________
> Pharo-users mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users


_______________________________________________
Pharo-users mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users