[piccolo2d-dev] Issue 121 in piccolo2d: Refactor PNode to break out some responsibilities.
Comment #1 on issue 121 by heuermh: Refactor PNode to break out some responsibilities. http://code.google.com/p/piccolo2d/issues/detail?id=121 I agree, toImage and print functionality seem like good candidates for extracting out into instances of the Strategy pattern. -- 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 -~--~~~~--~~--~--~---
[piccolo2d-dev] Issue 121 in piccolo2d: Refactor PNode to break out some responsibilities.
Comment #2 on issue 121 by mr0...@mro.name: Refactor PNode to break out some responsibilities. http://code.google.com/p/piccolo2d/issues/detail?id=121 Couldn't they even be completely removed from PNode and rather be decorators to PNode leveraging POffscreenCanvas? -- 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 -~--~~~~--~~--~--~---
