Hi,
The implementation of the Moose Finder from the Object>>inMoose started to be way too large to, so I moved it into an own class MooseFinder.
Cheers, Doru
-- www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
I wasn't aware of this method. If I execute "10 inMoose", then I have a DNU: SmallInteger does not understand #description. Maybe you can provide a default Object>>description method?
Cheers, Alexandre
On 15 Jan 2010, at 22:07, Tudor Girba wrote:
Hi,
The implementation of the Moose Finder from the Object>>inMoose started to be way too large to, so I moved it into an own class MooseFinder.
Cheers, Doru
-- www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
But may be it makes no sense to do that
may be inMoose only works on MooseAbtsractENtity and as such should not be in Object.
Stef
On Jan 16, 2010, at 2:14 AM, Alexandre Bergel wrote:
I wasn't aware of this method. If I execute "10 inMoose", then I have a DNU: SmallInteger does not understand #description. Maybe you can provide a default Object>>description method?
Cheers, Alexandre
On 15 Jan 2010, at 22:07, Tudor Girba wrote:
Hi,
The implementation of the Moose Finder from the Object>>inMoose started to be way too large to, so I moved it into an own class MooseFinder.
Cheers, Doru
-- www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
openInMoose should work on Object, it's just that indeed the MooseFinder has a couple of messages that are specific to MooseEntity. We should refactor that, but description will surely not get in Object :). The other two messages are: - complexPropertySelectors - this should be in the MetaDescription - propertiesToDisplay: which then depends on "asMooseFinderItemNamed: aString in: aMooseEntity"
Cheers, Doru
On 16 Jan 2010, at 12:47, Stéphane Ducasse wrote:
But may be it makes no sense to do that
may be inMoose only works on MooseAbtsractENtity and as such should not be in Object.
Stef
On Jan 16, 2010, at 2:14 AM, Alexandre Bergel wrote:
I wasn't aware of this method. If I execute "10 inMoose", then I have a DNU: SmallInteger does not understand #description. Maybe you can provide a default Object>>description method?
Cheers, Alexandre
On 15 Jan 2010, at 22:07, Tudor Girba wrote:
Hi,
The implementation of the Moose Finder from the Object>>inMoose started to be way too large to, so I moved it into an own class MooseFinder.
Cheers, Doru
-- www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Relationships are of two kinds: those we choose and those that happen. They both matter."
a question what kind of object do you expect to be displayed in Moose via openInMoose? Because your answer confused me.
Stef On Jan 16, 2010, at 12:52 PM, Tudor Girba wrote:
Hi,
openInMoose should work on Object, it's just that indeed the MooseFinder has a couple of messages that are specific to MooseEntity. We should refactor that, but description will surely not get in Object :). The other two messages are:
- complexPropertySelectors - this should be in the MetaDescription
- propertiesToDisplay: which then depends on "asMooseFinderItemNamed: aString in: aMooseEntity"
Cheers, Doru
On 16 Jan 2010, at 12:47, Stéphane Ducasse wrote:
But may be it makes no sense to do that
may be inMoose only works on MooseAbtsractENtity and as such should not be in Object.
Stef
On Jan 16, 2010, at 2:14 AM, Alexandre Bergel wrote:
I wasn't aware of this method. If I execute "10 inMoose", then I have a DNU: SmallInteger does not understand #description. Maybe you can provide a default Object>>description method?
Cheers, Alexandre
On 15 Jan 2010, at 22:07, Tudor Girba wrote:
Hi,
The implementation of the Moose Finder from the Object>>inMoose started to be way too large to, so I moved it into an own class MooseFinder.
Cheers, Doru
-- www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Relationships are of two kinds: those we choose and those that happen. They both matter."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
At this moment you can just say "someentity openInMoose" and this will spawn a MooseFinder with that entity as an input. It's like saying inspect only with information that depend on mooseDescription.
Given that any Object understands mooseDescription, we should be able to browse meta-described objects that are not necessarily subclasses of MooseEntity.
Is this better as an explanation?
Doru
On 16 Jan 2010, at 12:58, Stéphane Ducasse wrote:
a question what kind of object do you expect to be displayed in Moose via openInMoose? Because your answer confused me.
Stef On Jan 16, 2010, at 12:52 PM, Tudor Girba wrote:
Hi,
openInMoose should work on Object, it's just that indeed the MooseFinder has a couple of messages that are specific to MooseEntity. We should refactor that, but description will surely not get in Object :). The other two messages are:
- complexPropertySelectors - this should be in the MetaDescription
- propertiesToDisplay: which then depends on
"asMooseFinderItemNamed: aString in: aMooseEntity"
Cheers, Doru
On 16 Jan 2010, at 12:47, Stéphane Ducasse wrote:
But may be it makes no sense to do that
may be inMoose only works on MooseAbtsractENtity and as such should not be in Object.
Stef
On Jan 16, 2010, at 2:14 AM, Alexandre Bergel wrote:
I wasn't aware of this method. If I execute "10 inMoose", then I have a DNU: SmallInteger does not understand #description. Maybe you can provide a default Object>>description method?
Cheers, Alexandre
On 15 Jan 2010, at 22:07, Tudor Girba wrote:
Hi,
The implementation of the Moose Finder from the Object>>inMoose started to be way too large to, so I moved it into an own class MooseFinder.
Cheers, Doru
-- www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Relationships are of two kinds: those we choose and those that happen. They both matter."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Reasonable is what we are accustomed with."
yes
On Jan 16, 2010, at 1:04 PM, Tudor Girba wrote:
Hi,
At this moment you can just say "someentity openInMoose" and this will spawn a MooseFinder with that entity as an input. It's like saying inspect only with information that depend on mooseDescription.
Given that any Object understands mooseDescription, we should be able to browse meta-described objects that are not necessarily subclasses of MooseEntity.
Is this better as an explanation?
Doru
On 16 Jan 2010, at 12:58, Stéphane Ducasse wrote:
a question what kind of object do you expect to be displayed in Moose via openInMoose? Because your answer confused me.
Stef On Jan 16, 2010, at 12:52 PM, Tudor Girba wrote:
Hi,
openInMoose should work on Object, it's just that indeed the MooseFinder has a couple of messages that are specific to MooseEntity. We should refactor that, but description will surely not get in Object :). The other two messages are:
- complexPropertySelectors - this should be in the MetaDescription
- propertiesToDisplay: which then depends on "asMooseFinderItemNamed: aString in: aMooseEntity"
Cheers, Doru
On 16 Jan 2010, at 12:47, Stéphane Ducasse wrote:
But may be it makes no sense to do that
may be inMoose only works on MooseAbtsractENtity and as such should not be in Object.
Stef
On Jan 16, 2010, at 2:14 AM, Alexandre Bergel wrote:
I wasn't aware of this method. If I execute "10 inMoose", then I have a DNU: SmallInteger does not understand #description. Maybe you can provide a default Object>>description method?
Cheers, Alexandre
On 15 Jan 2010, at 22:07, Tudor Girba wrote:
Hi,
The implementation of the Moose Finder from the Object>>inMoose started to be way too large to, so I moved it into an own class MooseFinder.
Cheers, Doru
-- www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Relationships are of two kinds: those we choose and those that happen. They both matter."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Reasonable is what we are accustomed with."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
openInMoose should work on Object, it's just that indeed the MooseFinder has a couple of messages that are specific to MooseEntity. We should refactor that, but description will surely not get in Object :). The other two messages are:
- complexPropertySelectors - this should be in the MetaDescription
- propertiesToDisplay: which then depends on
"asMooseFinderItemNamed: aString in: aMooseEntity"
I think that #inMoose should not raise a "random" error.
Cheers, Alexandre
Cheers, Doru
On 16 Jan 2010, at 12:47, Stéphane Ducasse wrote:
But may be it makes no sense to do that
may be inMoose only works on MooseAbtsractENtity and as such should not be in Object.
Stef
On Jan 16, 2010, at 2:14 AM, Alexandre Bergel wrote:
I wasn't aware of this method. If I execute "10 inMoose", then I have a DNU: SmallInteger does not understand #description. Maybe you can provide a default Object>>description method?
Cheers, Alexandre
On 15 Jan 2010, at 22:07, Tudor Girba wrote:
Hi,
The implementation of the Moose Finder from the Object>>inMoose started to be way too large to, so I moved it into an own class MooseFinder.
Cheers, Doru
-- www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Relationships are of two kinds: those we choose and those that happen. They both matter."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Alexandre Bergel -
Stéphane Ducasse -
Tudor Girba