Updates:
Owner: mr0...@mro.name
Comment #10 on issue 99 by mr0...@mro.name: PNode.toString refactoring
http://code.google.com/p/piccolo2d/issues/detail?id=99
I'll do the job on Saturday, expect some commit activity between
12:00-14:00 UTC.
--
You received this message because you are
Comment #6 on issue 99 by allain.lalonde: PNode.toString refactoring
http://code.google.com/p/piccolo2d/issues/detail?id=99
Very strange, majority rules I guess. PParamStringBuilder is basically the
same thing
as the ToStringBuilder class, and the change is binary compatible to the
current
Comment #8 on issue 99 by heuermh: PNode.toString refactoring
http://code.google.com/p/piccolo2d/issues/detail?id=99
I agree with Allain in that paramString methods smell bad. I also see them
of
little-to-no utility. If someone wants to debug, use a debugger. My full
suggestion
is to
1.
Comment #2 on issue 99 by heuermh: PNode.toString refactoring
http://code.google.com/p/piccolo2d/issues/detail?id=99
My opinion would be to @deprecate all the paramString methods and remove
them in the
next released version.
I would rather not add the new class PParamStringBuilder to core.
Comment #3 on issue 99 by allain.lalonde: PNode.toString refactoring
http://code.google.com/p/piccolo2d/issues/detail?id=99
Sure. Of course we'd be adding an external dependency for something rather
trivial.
--
You received this message because you are listed in the owner
or CC fields of
Status: Started
Owner: allain.lalonde
Labels: Type-Enhancement Priority-Medium Effort-Low Toolkit-Piccolo2D.Java
Component-Core Milestone-1.3 Maintainability
New issue 99 by allain.lalonde: PNode.toString refactoring
http://code.google.com/p/piccolo2d/issues/detail?id=99
With all of its
