Comment #7 on issue 99 by [email protected]: PNode.toString refactoring http://code.google.com/p/piccolo2d/issues/detail?id=99
Hi Michael, if we want to keep the dubugging output of toString, I'd second Allain in adding a new class to the core. Expanding the interface gives me quite a headache, but for the sake of DRY-ness of the toStrings, I follow Allains argument. An external dependency is a no-go. Maybe a reflected toString is an option? What's your concerns about adding the class (which could be deprecated from the beginning)? P.S.: Ceterum censeo toString esse delendam - see comment 5 #c5. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en -~----------~----~----~----~------~----~------~--~---
