Did you receive this? I got an error message from the mailing list.
yes you should use @lists...
Lukas you should have a look no super read different super black simple super green
I do not understand, so I am reading <http://smallwiki.unibe.ch/hermion/icons/
:
- What means "super method does not exit" ? Do you mean "exists"?
I mean super zork and zork does not exit
- What has priority if there are multiple super sends in one method?
- What is shown when you have a sub-implementation and do a super call to a non existing method?
triangle up and down + red foot
Again there is an inconsistent mix of icons and meanings, for example:
- The case "super send, but super method does not exists." has a big yellow up arrow. The big yellow arrow on its own means "overrides super class methods", however this method does not exist in the given example.
Indeed but like that we are consistent
now I was thinking that it would be great to have an icon for a class using traits and a traits used so that we could navigate the same as for the methods because clicking on the icon is cool
For the test icons:
- The icons for "more red tests than green", "equal number of green and red tests" and "more green tests than red" are cute, but absolutely useless because inconsistant. "red", "yellow", "green" and "black" is the only information that is valuable. Or do you plan to add icons for all combinations like "some red tests, a few yellow and green and most of them are not run yet"?
Lukas it would be good that you do not have total statement. We already use the class icons and this is cool to see if all your tests are green or if some of them fail/error/ At this level this is not important to be really precise.
- Abstract test cases always remain in the state of not being run. Maybe it is better not to show the test icon at all in that case, or fetch the result from all the concrete subclasses (that would go nicely with the semantics of SUnit).
Yeap. One remark is that this is not absolute :) Stef