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(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
_______________________________________________
Moose-dev mailing list
Moose-dev(a)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(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev