Comment #24 on issue 43 by mr0...@mro.name: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
Releasenote issue list:
For
http://code.google.com/p/piccolo2d/wiki/TodosRelease1_3#For_the_Release_Notes
I'd even just go with copying
Comment #25 on issue 43 by mr0...@mro.name: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
(mind the CSV link bottom right on the issues listing at
http://code.google.com/p/piccolo2d/wiki/TodosRelease1_3#For_the_Release_Notes)
--
You received this message
Comment #22 on issue 43 by mr0...@mro.name: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
@Sam:
Please file new issues rather than adding them to this one. If the problems
from #19 persist, can you open issues
for them, please.
--
You received this message
Comment #20 on issue 43 by allain.lalonde: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
Thank you very much for responding!
I hope that we can work together to resolve your problems. To shed some
light on the
changes that were made.
#1 and #2 stem from the
Comment #18 on issue 43 by heuermh: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
I added an Issues section to
http://code.google.com/p/piccolo2d/wiki/TodosRelease1_3.
There are a few issues left to triage, a few new issues left to review,
and a ton of
Comment #14 on issue 43 by re...@colorado.edu: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
I created issue #137 to track one of the new rendering problems:
http://code.google.com/p/piccolo2d/issues/detail?id=137
--
You received this message because you are
Comment #16 on issue 43 by allain.lalonde: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
I thought I hadn't changed the strategy, but of course I might be wrong.
Can you
confirm that it wasn't just the big in Issue 137 causing it to misbehave?
Thank you.
--
Comment #10 on issue 43 by re...@colorado.edu: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
My team and I had been using a copy of piccolo's r390 and when I tried
upgrading to
r689 I noticed a few rendering problems; some nodes don't appear, some are
the
Comment #11 on issue 43 by allain.lalonde: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
Piccolo is undergoing a cleanup, and in the process, it's quite possible
thatsome
things have broken (probably by my hand). I'd tried to push the code
coverage up
before
Comment #12 on issue 43 by heuermh: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
Yes, by all means, if you find difference in behavior between 1.2.1 and svn
trunk,
please submit issues against Milestone 1.3. All the refactoring and
cleanup going on
lately
Comment #7 on issue 43 by samrreid: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
Since the 1.3 timeframe is looking like it might be a long ways off, I'm
wondering
how stable the svn trunk is, or about the possibility of making a 1.2.2
release
candidate
Comment #2 on issue 43 by akurtakov: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
Also can you consider adding the code used in pydev?
It was sent to piccolo list long ago.
See https://mailman.cs.umd.edu/pipermail/piccolo-chat/2006/003452.html
--
You received
Comment #3 on issue 43 by heuermh: Prepare the 1.3 release
http://code.google.com/p/piccolo2d/issues/detail?id=43
Eliminate dependency on sun.* classes in PFixedWidthStroke is Issue 48.
Added the post to piccolo-dev as Issue 124.
Could you create a new issue for depends on swt 2.*? I'm not a
13 matches
Mail list logo
