So what would be a good solution?On Dec 7, 2013, at 9:47 PM, Tudor Girba <tudor@tudorgirba.com> wrote:Hi Syeg :),printOn: is not at all ideal, but nobody did anything so it remained like that. Any improvement is more than welcome.I sa that there ismooseNameOn: and printOn:The mooseNameOn: looks better (more compact to me).Now do we want to have a little object shared by model that specify the printing of the entities?StefDoru_______________________________________________On Sat, Dec 7, 2013 at 8:32 PM, Stéphane Ducasse <stephane.ducasse@inria.fr> wrote:Hi
This is several times that I ask and I got no reaction but the printOn: of FAMIX entities is a problem.
I do not think that it makes sense to have ClassName in namespace (namespace) :: namespace (namespace) (class)
So how do we address it?
- I would introduce either a strategy to control what is displayed
- I would make the dinstction between full name and name.
Of course I can hack it and have my own implementation because it really get on my nerves that I cannot
even see the name of a class in a set in the inspector.
Syeg
_______________________________________________
Moose-dev mailing list
Moose-dev@iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--"Every thing has its own flow"
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