simon can you open bug entry for pharo?
Stef
>> Hi,
>>
>> I just tried creating a new image, but there is a problem with traits definition:
>> http://hudson.moosetechnology.org/job/moose-latest-dev/370/console
>>
>> Could you take a look?
>
>
> Re-argh, same problem, renaming a trait does not make a package dirty by default, and I didn't check for external users of traits (now I know how to do that :()
> Fixed in Famix-Extensions and DSM.
>
> Can you try again?
>
>
>>
>> Cheers,
>> Doru
>>
>>
>> On 28 Sep 2010, at 17:20, Simon Denier wrote:
>>
>>>
>>>
>>> It's done. Squeaksource was down a bit this afternoon, and Lukas's server seems down since this morning, so I can't test a load default now, but hopefully everything is alright now. We will see tomorrow.
>>>
>>>
>>>
>>> On 28 sept. 2010, at 13:01, Simon Denier wrote:
>>>
>>>>
>>>> On 28 sept. 2010, at 09:11, Tudor Girba wrote:
>>>>
>>>>> Hi Simon,
>>>>>
>>>>> It looks like while renaming you missed to publish some packages: MOTarjanNodeDSM still seems to inherit from the old MOTarjanNode, and because of that the build breaks :).
>>>>
>>>>
>>>> Argh, never thought I could still be bitten by the non-dirty package bug in MC :(
>>>>
>>>> So changing a superclass does not make a package dirty mmm... I guess I will to check with Package Blueprints what's the impact of renaming classes.
>>>>
>>>>
>>>> As for the prefix, I will take Mal, just because fireflies do not bite (...)
>>>>
>>>>
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> On 27 Sep 2010, at 22:00, Tudor Girba wrote:
>>>>>
>>>>>> Hi Simon,
>>>>>>
>>>>>> These classes should be called MAlgo (or MAL ?). I started to do that a while ago, but apparently I forgot to commit this change.
>>>>>>
>>>>>> Cheers,
>>>>>> Doru
>>>>>>
>>>>>>
>>>>>> On 27 Sep 2010, at 19:42, Simon Denier wrote:
>>>>>>
>>>>>>>
>>>>>>> On 27 sept. 2010, at 18:17, Lukas Renggli wrote:
>>>>>>>
>>>>>>>> Please note that the MA* (with an uppercase $A) prefix is already
>>>>>>>> taken by Magritte. Ma* (with a lowercase $a) is taken by Magma, if I
>>>>>>>> remember correctly they renamed their classes at some point a long
>>>>>>>> time ago to avoid the conflict with Magritte.
>>>>>>>
>>>>>>>
>>>>>>> ok, one issue is that all classes in Moose-Algos (not only Moose-Algos-Graph) are prefixed with MA so we will need to change that...
>>>>>>>
>>>>>>> but at least now there is some consistency in class names.
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Lukas
>>>>>>>>
>>>>>>>> On 27 September 2010 17:51, Simon Denier <Simon.Denier(a)inria.fr> wrote:
>>>>>>>>> I just performed a mass class renaming in Moose Algos Graph. Some classes still had the old prefix MO*, they now all have a MA* prefix. Class references in default Moose have been updated too (this includes DSM...)
>>>>>>>>>
>>>>>>>>> So, if you use Moose-Algos-Graph and your package is not part of Moose default, you might to take a look and see if you need to update some references.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Also, the API of MAGraphAlgorithm has been extracted into trait MATGraphBuilder if someone wants to reuse it in a different setting (as requested). I don't support nested graph for now though, as it is not clear for me the best way to build them.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Simon
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Moose-dev mailing list
>>>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Lukas Renggli
>>>>>>>> www.lukas-renggli.ch
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Moose-dev mailing list
>>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>>
>>>>>>> --
>>>>>>> Simon
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Moose-dev mailing list
>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>
>>>>>> --
>>>>>> www.tudorgirba.com
>>>>>>
>>>>>> "Not knowing how to do something is not an argument for how it cannot be done."
>>>>>>
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "Be rather willing to give than demanding to get."
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> Moose-dev(a)iam.unibe.ch
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>> --
>>>> Simon
>>>>
>>>>
>>>>
>>>
>>> --
>>> Simon
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "We cannot reach the flow of things unless we let go."
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> Simon
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 23 sept. 2010, at 10:30, Mariano Martinez Peck wrote:
> Hi Folks...Sorry for the "urgen" but I got an idea for my paper with deadline tomorro hahahahah
>
> I was using DistributionMaps where the containers were packages for example, elements classes, and properties the amount of instances. For example, see the attached screenshot.
>
> Now....it is difficult to find the classes with most instances since I need to search for an specific color.
I am not sure I understand what it is difficult:
- because the mapping color <-> range does not match your expectations (like red would be highest, blue would be lowest)
- or because you are looking for one class with the most instances
- or because you want to compare the real values, not ranges.
>
> I thoguht that having someting like CodeCity can be interesting. I would like:
>
> - EAch building (square) is a container -> package
> - Each little squeare (that has heigh) is a element -> class
> - The heigh is a property, in this case, the amount of instances for example.
>
> Then I can easily see packages/classes with several intances easily (the highest ones).
>
> So...is that possible? how easier? :)
>
> Right now I was doing my DM something like this:
>
> I checked for *City* class in Moose 4.1 but I didn't find anything :(
>
> The only thing I found was this link: http://www.moosetechnology.org/tools/vw/codecity
>
> Thanks for any help
>
> Mariano
> <amuntUsedInstances.png>_______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
On 28 sept. 2010, at 22:51, Tudor Girba wrote:
> Great, now it's all fine:
> http://hudson.moosetechnology.org/job/moose-latest-dev/
>
> I just had to fix a missing refactoring in Famix-Extensions.
Good, apparently I was a bit careless with the refactoring in Ma Graph (well the image hung up, I had to restart and probably forgot to commit)
>
> Cheers,
> Doru
>
>
> On 28 Sep 2010, at 21:46, Simon Denier wrote:
>
>>
>> On 28 sept. 2010, at 20:57, Tudor Girba wrote:
>>
>>> Hi,
>>>
>>> I just tried creating a new image, but there is a problem with traits definition:
>>> http://hudson.moosetechnology.org/job/moose-latest-dev/370/console
>>>
>>> Could you take a look?
>>
>>
>> Re-argh, same problem, renaming a trait does not make a package dirty by default, and I didn't check for external users of traits (now I know how to do that :()
>> Fixed in Famix-Extensions and DSM.
>>
>> Can you try again?
>>
>>
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> On 28 Sep 2010, at 17:20, Simon Denier wrote:
>>>
>>>>
>>>>
>>>> It's done. Squeaksource was down a bit this afternoon, and Lukas's server seems down since this morning, so I can't test a load default now, but hopefully everything is alright now. We will see tomorrow.
>>>>
>>>>
>>>>
>>>> On 28 sept. 2010, at 13:01, Simon Denier wrote:
>>>>
>>>>>
>>>>> On 28 sept. 2010, at 09:11, Tudor Girba wrote:
>>>>>
>>>>>> Hi Simon,
>>>>>>
>>>>>> It looks like while renaming you missed to publish some packages: MOTarjanNodeDSM still seems to inherit from the old MOTarjanNode, and because of that the build breaks :).
>>>>>
>>>>>
>>>>> Argh, never thought I could still be bitten by the non-dirty package bug in MC :(
>>>>>
>>>>> So changing a superclass does not make a package dirty mmm... I guess I will to check with Package Blueprints what's the impact of renaming classes.
>>>>>
>>>>>
>>>>> As for the prefix, I will take Mal, just because fireflies do not bite (...)
>>>>>
>>>>>
>>>>>>
>>>>>> Cheers,
>>>>>> Doru
>>>>>>
>>>>>>
>>>>>> On 27 Sep 2010, at 22:00, Tudor Girba wrote:
>>>>>>
>>>>>>> Hi Simon,
>>>>>>>
>>>>>>> These classes should be called MAlgo (or MAL ?). I started to do that a while ago, but apparently I forgot to commit this change.
>>>>>>>
>>>>>>> Cheers,
>>>>>>> Doru
>>>>>>>
>>>>>>>
>>>>>>> On 27 Sep 2010, at 19:42, Simon Denier wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> On 27 sept. 2010, at 18:17, Lukas Renggli wrote:
>>>>>>>>
>>>>>>>>> Please note that the MA* (with an uppercase $A) prefix is already
>>>>>>>>> taken by Magritte. Ma* (with a lowercase $a) is taken by Magma, if I
>>>>>>>>> remember correctly they renamed their classes at some point a long
>>>>>>>>> time ago to avoid the conflict with Magritte.
>>>>>>>>
>>>>>>>>
>>>>>>>> ok, one issue is that all classes in Moose-Algos (not only Moose-Algos-Graph) are prefixed with MA so we will need to change that...
>>>>>>>>
>>>>>>>> but at least now there is some consistency in class names.
>>>>>>>>
>>>>>>>>
>>>>>>>>>
>>>>>>>>> Lukas
>>>>>>>>>
>>>>>>>>> On 27 September 2010 17:51, Simon Denier <Simon.Denier(a)inria.fr> wrote:
>>>>>>>>>> I just performed a mass class renaming in Moose Algos Graph. Some classes still had the old prefix MO*, they now all have a MA* prefix. Class references in default Moose have been updated too (this includes DSM...)
>>>>>>>>>>
>>>>>>>>>> So, if you use Moose-Algos-Graph and your package is not part of Moose default, you might to take a look and see if you need to update some references.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Also, the API of MAGraphAlgorithm has been extracted into trait MATGraphBuilder if someone wants to reuse it in a different setting (as requested). I don't support nested graph for now though, as it is not clear for me the best way to build them.
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Simon
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> _______________________________________________
>>>>>>>>>> Moose-dev mailing list
>>>>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Lukas Renggli
>>>>>>>>> www.lukas-renggli.ch
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Moose-dev mailing list
>>>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>>>
>>>>>>>> --
>>>>>>>> Simon
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Moose-dev mailing list
>>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>>
>>>>>>> --
>>>>>>> www.tudorgirba.com
>>>>>>>
>>>>>>> "Not knowing how to do something is not an argument for how it cannot be done."
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> www.tudorgirba.com
>>>>>>
>>>>>> "Be rather willing to give than demanding to get."
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moose-dev mailing list
>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>
>>>>> --
>>>>> Simon
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> Simon
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> Moose-dev(a)iam.unibe.ch
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "We cannot reach the flow of things unless we let go."
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> Simon
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "Problem solving efficiency grows with the abstractness level of problem understanding."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
On 28 sept. 2010, at 20:57, Tudor Girba wrote:
> Hi,
>
> I just tried creating a new image, but there is a problem with traits definition:
> http://hudson.moosetechnology.org/job/moose-latest-dev/370/console
>
> Could you take a look?
Re-argh, same problem, renaming a trait does not make a package dirty by default, and I didn't check for external users of traits (now I know how to do that :()
Fixed in Famix-Extensions and DSM.
Can you try again?
>
> Cheers,
> Doru
>
>
> On 28 Sep 2010, at 17:20, Simon Denier wrote:
>
>>
>>
>> It's done. Squeaksource was down a bit this afternoon, and Lukas's server seems down since this morning, so I can't test a load default now, but hopefully everything is alright now. We will see tomorrow.
>>
>>
>>
>> On 28 sept. 2010, at 13:01, Simon Denier wrote:
>>
>>>
>>> On 28 sept. 2010, at 09:11, Tudor Girba wrote:
>>>
>>>> Hi Simon,
>>>>
>>>> It looks like while renaming you missed to publish some packages: MOTarjanNodeDSM still seems to inherit from the old MOTarjanNode, and because of that the build breaks :).
>>>
>>>
>>> Argh, never thought I could still be bitten by the non-dirty package bug in MC :(
>>>
>>> So changing a superclass does not make a package dirty mmm... I guess I will to check with Package Blueprints what's the impact of renaming classes.
>>>
>>>
>>> As for the prefix, I will take Mal, just because fireflies do not bite (...)
>>>
>>>
>>>>
>>>> Cheers,
>>>> Doru
>>>>
>>>>
>>>> On 27 Sep 2010, at 22:00, Tudor Girba wrote:
>>>>
>>>>> Hi Simon,
>>>>>
>>>>> These classes should be called MAlgo (or MAL ?). I started to do that a while ago, but apparently I forgot to commit this change.
>>>>>
>>>>> Cheers,
>>>>> Doru
>>>>>
>>>>>
>>>>> On 27 Sep 2010, at 19:42, Simon Denier wrote:
>>>>>
>>>>>>
>>>>>> On 27 sept. 2010, at 18:17, Lukas Renggli wrote:
>>>>>>
>>>>>>> Please note that the MA* (with an uppercase $A) prefix is already
>>>>>>> taken by Magritte. Ma* (with a lowercase $a) is taken by Magma, if I
>>>>>>> remember correctly they renamed their classes at some point a long
>>>>>>> time ago to avoid the conflict with Magritte.
>>>>>>
>>>>>>
>>>>>> ok, one issue is that all classes in Moose-Algos (not only Moose-Algos-Graph) are prefixed with MA so we will need to change that...
>>>>>>
>>>>>> but at least now there is some consistency in class names.
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Lukas
>>>>>>>
>>>>>>> On 27 September 2010 17:51, Simon Denier <Simon.Denier(a)inria.fr> wrote:
>>>>>>>> I just performed a mass class renaming in Moose Algos Graph. Some classes still had the old prefix MO*, they now all have a MA* prefix. Class references in default Moose have been updated too (this includes DSM...)
>>>>>>>>
>>>>>>>> So, if you use Moose-Algos-Graph and your package is not part of Moose default, you might to take a look and see if you need to update some references.
>>>>>>>>
>>>>>>>>
>>>>>>>> Also, the API of MAGraphAlgorithm has been extracted into trait MATGraphBuilder if someone wants to reuse it in a different setting (as requested). I don't support nested graph for now though, as it is not clear for me the best way to build them.
>>>>>>>>
>>>>>>>> --
>>>>>>>> Simon
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Moose-dev mailing list
>>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Lukas Renggli
>>>>>>> www.lukas-renggli.ch
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Moose-dev mailing list
>>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>
>>>>>> --
>>>>>> Simon
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moose-dev mailing list
>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>
>>>>> --
>>>>> www.tudorgirba.com
>>>>>
>>>>> "Not knowing how to do something is not an argument for how it cannot be done."
>>>>>
>>>>
>>>> --
>>>> www.tudorgirba.com
>>>>
>>>> "Be rather willing to give than demanding to get."
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> Moose-dev(a)iam.unibe.ch
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> Simon
>>>
>>>
>>>
>>
>> --
>> Simon
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> www.tudorgirba.com
>
> "We cannot reach the flow of things unless we let go."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
It's done. Squeaksource was down a bit this afternoon, and Lukas's server seems down since this morning, so I can't test a load default now, but hopefully everything is alright now. We will see tomorrow.
On 28 sept. 2010, at 13:01, Simon Denier wrote:
>
> On 28 sept. 2010, at 09:11, Tudor Girba wrote:
>
>> Hi Simon,
>>
>> It looks like while renaming you missed to publish some packages: MOTarjanNodeDSM still seems to inherit from the old MOTarjanNode, and because of that the build breaks :).
>
>
> Argh, never thought I could still be bitten by the non-dirty package bug in MC :(
>
> So changing a superclass does not make a package dirty mmm... I guess I will to check with Package Blueprints what's the impact of renaming classes.
>
>
> As for the prefix, I will take Mal, just because fireflies do not bite (...)
>
>
>>
>> Cheers,
>> Doru
>>
>>
>> On 27 Sep 2010, at 22:00, Tudor Girba wrote:
>>
>>> Hi Simon,
>>>
>>> These classes should be called MAlgo (or MAL ?). I started to do that a while ago, but apparently I forgot to commit this change.
>>>
>>> Cheers,
>>> Doru
>>>
>>>
>>> On 27 Sep 2010, at 19:42, Simon Denier wrote:
>>>
>>>>
>>>> On 27 sept. 2010, at 18:17, Lukas Renggli wrote:
>>>>
>>>>> Please note that the MA* (with an uppercase $A) prefix is already
>>>>> taken by Magritte. Ma* (with a lowercase $a) is taken by Magma, if I
>>>>> remember correctly they renamed their classes at some point a long
>>>>> time ago to avoid the conflict with Magritte.
>>>>
>>>>
>>>> ok, one issue is that all classes in Moose-Algos (not only Moose-Algos-Graph) are prefixed with MA so we will need to change that...
>>>>
>>>> but at least now there is some consistency in class names.
>>>>
>>>>
>>>>>
>>>>> Lukas
>>>>>
>>>>> On 27 September 2010 17:51, Simon Denier <Simon.Denier(a)inria.fr> wrote:
>>>>>> I just performed a mass class renaming in Moose Algos Graph. Some classes still had the old prefix MO*, they now all have a MA* prefix. Class references in default Moose have been updated too (this includes DSM...)
>>>>>>
>>>>>> So, if you use Moose-Algos-Graph and your package is not part of Moose default, you might to take a look and see if you need to update some references.
>>>>>>
>>>>>>
>>>>>> Also, the API of MAGraphAlgorithm has been extracted into trait MATGraphBuilder if someone wants to reuse it in a different setting (as requested). I don't support nested graph for now though, as it is not clear for me the best way to build them.
>>>>>>
>>>>>> --
>>>>>> Simon
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Moose-dev mailing list
>>>>>> Moose-dev(a)iam.unibe.ch
>>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Lukas Renggli
>>>>> www.lukas-renggli.ch
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> Moose-dev(a)iam.unibe.ch
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>
>>>> --
>>>> Simon
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> Moose-dev(a)iam.unibe.ch
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> www.tudorgirba.com
>>>
>>> "Not knowing how to do something is not an argument for how it cannot be done."
>>>
>>
>> --
>> www.tudorgirba.com
>>
>> "Be rather willing to give than demanding to get."
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>
> --
> Simon
>
>
>
--
Simon
On 28 sept. 2010, at 15:16, Guillermo Schwarz wrote:
> Hi Guys,
>
> Why don't you do something more focused on the long term and don't you change the Smalltalk compiler with namespaces?
As you said, it's something for long-term....
Meanwhile, I'm just putting some pressure on our daily tools (Moose + OR) and it's also good :)
>
> I don't think it should be that hard since each class already belongs to a category. Each category could instead be a dictionary from where the compiler could find classes that are mentioned in the class source.
>
> This has worked wonders in Java (classes inside packages). This way classes' names can be repeated ad eternum without generating collisions or otherwise polluting excessively the name space.
>
> So for example:
>
> FAMIXAssociation subclass: #FAMIXInvocation
> instanceVariableNames: 'sender receiver receiverSourceCode signature candidates'
> classVariableNames: ''
> poolDictionaries: ''
> category: 'Famix-Core'
>
> Would be instead:
>
> Association subclass: #Invocation
> instanceVariableNames: 'sender receiver receiverSourceCode signature candidates'
> classVariableNames: ''
> poolDictionaries: ''
> category: #FamixCore
>
> Then the category would be an index in the SystemDictionary:
>
> SystemDictionary at: #FamixCore put: Category new.
>
> (SystemDictionary at: #FamixCore) belongingClassList add: #Invocation "this should be done automatically by the subclass: method above"
>
> (SystemDictionary at: #FamixCore) referencedClassList add: ... "classes that are referenced by classes belonging to category #FamixCore"
>
> What do you think?
>
> Cheers,
> Guillermo.
>
> Message: 1
> Date: Mon, 27 Sep 2010 22:00:33 +0200
> From: Tudor Girba <tudor.girba(a)gmail.com>
> Subject: [Moose-dev] Re: Class renaming in Moose Algos Graph
> To: Moose-related development <moose-dev(a)iam.unibe.ch>
> Message-ID: <C912A83B-6BDC-4775-AC26-CE2DBC5540AE(a)gmail.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hi Simon,
>
> These classes should be called MAlgo (or MAL ?). I started to do that a while ago, but apparently I forgot to commit this change.
>
> Cheers,
> Doru
>
>
> On 27 Sep 2010, at 19:42, Simon Denier wrote:
>
> >
> > On 27 sept. 2010, at 18:17, Lukas Renggli wrote:
> >
> >> Please note that the MA* (with an uppercase $A) prefix is already
> >> taken by Magritte. Ma* (with a lowercase $a) is taken by Magma, if I
> >> remember correctly they renamed their classes at some point a long
> >> time ago to avoid the conflict with Magritte.
> >
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
Hi,
I moved all code from Moose-MondrianScripts to Moose-
MondrianPaintings, and I removed the Moose-MondrianScripts from the
configuration.
I would like to work slowly on package restructuring. In the
following, I would like to rename the test packages:
Moose-LAN -> Moose-TestResources-LAN
Famix-LANTests -> Moose-Tests-SmalltalkImporter-LAN
MooseKGB-TestFamix3 -> Moose-Tests-KGB
Moose-KGB-* -> Moose-TestResources-KGB-*
Moose-SmalltalkImporterTests -> Moose-Tests-SmalltalkImporter
Moose-Test-PackageOne -> Moose-TestResources-Reference-PackageOne
Moose-Test-PackageTwo -> Moose-TestResources-Reference-PackageTwo
Cheers,
Doru
--
www.tudorgirba.com
"There are no old things, there are only old ways of looking at them."
On 28 sept. 2010, at 13:05, Tudor Girba wrote:
>
>> As for the prefix, I will take Mal, just because fireflies do not bite (...)
>
> Great, although I am not sure I understand the word play :)
http://en.wikipedia.org/wiki/Malcolm_Reynolds
Hehe, I hope some people in the wave got it pretty easily :D
--
Simon
On 28 sept. 2010, at 09:11, Tudor Girba wrote:
> Hi Simon,
>
> It looks like while renaming you missed to publish some packages: MOTarjanNodeDSM still seems to inherit from the old MOTarjanNode, and because of that the build breaks :).
Argh, never thought I could still be bitten by the non-dirty package bug in MC :(
So changing a superclass does not make a package dirty mmm... I guess I will to check with Package Blueprints what's the impact of renaming classes.
As for the prefix, I will take Mal, just because fireflies do not bite (...)
>
> Cheers,
> Doru
>
>
> On 27 Sep 2010, at 22:00, Tudor Girba wrote:
>
>> Hi Simon,
>>
>> These classes should be called MAlgo (or MAL ?). I started to do that a while ago, but apparently I forgot to commit this change.
>>
>> Cheers,
>> Doru
>>
>>
>> On 27 Sep 2010, at 19:42, Simon Denier wrote:
>>
>>>
>>> On 27 sept. 2010, at 18:17, Lukas Renggli wrote:
>>>
>>>> Please note that the MA* (with an uppercase $A) prefix is already
>>>> taken by Magritte. Ma* (with a lowercase $a) is taken by Magma, if I
>>>> remember correctly they renamed their classes at some point a long
>>>> time ago to avoid the conflict with Magritte.
>>>
>>>
>>> ok, one issue is that all classes in Moose-Algos (not only Moose-Algos-Graph) are prefixed with MA so we will need to change that...
>>>
>>> but at least now there is some consistency in class names.
>>>
>>>
>>>>
>>>> Lukas
>>>>
>>>> On 27 September 2010 17:51, Simon Denier <Simon.Denier(a)inria.fr> wrote:
>>>>> I just performed a mass class renaming in Moose Algos Graph. Some classes still had the old prefix MO*, they now all have a MA* prefix. Class references in default Moose have been updated too (this includes DSM...)
>>>>>
>>>>> So, if you use Moose-Algos-Graph and your package is not part of Moose default, you might to take a look and see if you need to update some references.
>>>>>
>>>>>
>>>>> Also, the API of MAGraphAlgorithm has been extracted into trait MATGraphBuilder if someone wants to reuse it in a different setting (as requested). I don't support nested graph for now though, as it is not clear for me the best way to build them.
>>>>>
>>>>> --
>>>>> Simon
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Moose-dev mailing list
>>>>> Moose-dev(a)iam.unibe.ch
>>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Lukas Renggli
>>>> www.lukas-renggli.ch
>>>>
>>>> _______________________________________________
>>>> Moose-dev mailing list
>>>> Moose-dev(a)iam.unibe.ch
>>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>>
>>> --
>>> Simon
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Moose-dev mailing list
>>> Moose-dev(a)iam.unibe.ch
>>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>> --
>> www.tudorgirba.com
>>
>> "Not knowing how to do something is not an argument for how it cannot be done."
>>
>
> --
> www.tudorgirba.com
>
> "Be rather willing to give than demanding to get."
>
>
>
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
On 27 sept. 2010, at 18:17, Lukas Renggli wrote:
> Please note that the MA* (with an uppercase $A) prefix is already
> taken by Magritte. Ma* (with a lowercase $a) is taken by Magma, if I
> remember correctly they renamed their classes at some point a long
> time ago to avoid the conflict with Magritte.
ok, one issue is that all classes in Moose-Algos (not only Moose-Algos-Graph) are prefixed with MA so we will need to change that...
but at least now there is some consistency in class names.
>
> Lukas
>
> On 27 September 2010 17:51, Simon Denier <Simon.Denier(a)inria.fr> wrote:
>> I just performed a mass class renaming in Moose Algos Graph. Some classes still had the old prefix MO*, they now all have a MA* prefix. Class references in default Moose have been updated too (this includes DSM...)
>>
>> So, if you use Moose-Algos-Graph and your package is not part of Moose default, you might to take a look and see if you need to update some references.
>>
>>
>> Also, the API of MAGraphAlgorithm has been extracted into trait MATGraphBuilder if someone wants to reuse it in a different setting (as requested). I don't support nested graph for now though, as it is not clear for me the best way to build them.
>>
>> --
>> Simon
>>
>>
>>
>>
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
>>
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>
> _______________________________________________
> Moose-dev mailing list
> Moose-dev(a)iam.unibe.ch
> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Simon
