Comment #8 on issue 150 by heue...@gmail.com: Prepare SwingLayoutNode for
distribution
http://code.google.com/p/piccolo2d/issues/detail?id=150
I would vote to leave as-is for now. Would you want to mark this one as
Fixed, Allain?
--
You received this message because you are listed in the
Comment #7 on issue 150 by allain.lalonde: Prepare SwingLayoutNode for
distribution
http://code.google.com/p/piccolo2d/issues/detail?id=150
I'm looking at the Anchor approach and am wondering if it's too restrictive.
It's basically a fill strategy for whatever bounds the LayoutManager
Comment #1 on issue 150 by samrreid: Prepare SwingLayoutNode for
distribution
http://code.google.com/p/piccolo2d/issues/detail?id=150
On Dec 1, Michael Heuer wrote:
I think this is cool, and a good fit for piccolox.swing in extras.
Could you create an issue for this? With the proper license
Comment #2 on issue 150 by samrreid: Prepare SwingLayoutNode for
distribution
http://code.google.com/p/piccolo2d/issues/detail?id=150
See this thread for context:
http://groups.google.com/group/piccolo2d-users/browse_thread/thread/741bca3c0aa2d96e?pli=1
--
You received this message because
Comment #3 on issue 150 by samrreid: Prepare SwingLayoutNode for
distribution
http://code.google.com/p/piccolo2d/issues/detail?id=150
Chris suggested that we also spend some additional time to verify that (1)
we're not
exposing anything that we'll regret later, and (2) method names are
Comment #4 on issue 150 by samrreid: Prepare SwingLayoutNode for
distribution
http://code.google.com/p/piccolo2d/issues/detail?id=150
I don't have plans for working on this in the near future, if someone wants
to work
on it. Here's a quick itemized summary of proposed work:
1. Add to SVN
Comment #6 on issue 150 by allain.lalonde: Prepare SwingLayoutNode for
distribution
http://code.google.com/p/piccolo2d/issues/detail?id=150
I'd tried something like this in the past and failed, so I'm very much
liking this code.
--
You received this message because you are listed in the