I do not see how discussing the fact that we could via a trick (I failed
to find it) navigate methods in the same name in other classes without
having to click on the class, catgeory and methods would have solve the
problem that I introduced a bug while trying to add this extra behavior?
Then you do not understand my point: I integrated the scroll fix from
jan because a change was breaking their flow.
And ??? How can I possibly know that it would break your fixes that
apparently broke their flow.
You see what I mean?
I could also simply ignore issue that I do not know or contributed too
but it would slow down the process, isn't?
Stef
stepharo wrote
Could you stop crying because this is a bit boring?
Could you address my policy suggestion instead of crying? ;) It would've
taken the same amount of time to answer my message productively instead of
lawyering it by pointing out the one example out of three that you could
turn back around on me and ignoring everything else.
stepharo wrote
So instead of crying help.
I've participated in fixing hundreds of issues, and that's just on the new
issue tracker. Is that a reasonable comment?
-----
Cheers,
Sean
--
View this message in context:
http://forum.world.st/UI-Workflows-Are-Like-Snowflakes-tp4814234p4814344.html
Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.
