Status: Accepted Owner: allain.lalonde Labels: Type-Enhancement Priority-Medium Effort-Medium OpSys-All Toolkit-Piccolo2D.Java Component-Core Milestone-2.0 Usability
New issue 121 by allain.lalonde: Refactor PNode to break out some responsibilities. http://code.google.com/p/piccolo2d/issues/detail?id=121 Piccolo2D's Monolithic design is great but when it comes to aspects of PNode's implementation that don't relate to the scene, it seems like they could be broken out in some way without complicating things too greatly. One example is PNode's print method. It doesn't specifically relate to rendering the scene and it strikes me as something that could broken out into another class (maybe PNodePrinter). Another example is toImage, it has so many overloads that it's becoming ridiculous. Considering that rendering a Node is something that's already handled by PCamera. I can't help but think that this logic is something that should be handled outside of PNode. I'm not suggesting any particular fix, just mentioning something that should be discussed when we get started on v2.0. -- 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 -~----------~----~----~----~------~----~------~--~---
