Issue 62: Publish release 1.2.1 to a public maven repo
http://code.google.com/p/piccolo2d/issues/detail?id=62
Comment #7 by [EMAIL PROTECTED]:
Oops, completely forgot about this one. I start right now.
--
You received this message because you are listed in the owner
or CC fields of this issue
Issue 62: Publish release 1.2.1 to a public maven repo
http://code.google.com/p/piccolo2d/issues/detail?id=62
Comment #8 by [EMAIL PROTECTED]:
Ok, I just created a new mvn release bundle (see the attached jar) by
running the
attached shell script.
Please have a look into it and tell me, if you
Issue 62: Publish release 1.2.1 to a public maven repo
http://code.google.com/p/piccolo2d/issues/detail?id=62
Comment #9 by [EMAIL PROTECTED]:
Ok, I just created a new mvn release bundle (see the attached jar) by
running the
attached shell script.
Please have a look into it and tell me, if you
Hi folks,
before christmas, I'd like to get 1.3 (java) out of the door.
There's some issues to deal with until that,
http://code.google.com/p/piccolo2d/issues/list?can=1&q=label%3AMilestone-1.3&colspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Component+Summary&x=type&y=status&mode=grid&ce
Sorry I have been a bit distant... I let work overtake my life for a
few months. :-(
I should have some time to work on this during the week. Besides
integrating those changes, some other things I would like to do are:
* Port over my Piccolo-UI testing framework (it is based on FEST-Swi
M. Rohrmoser wrote:
> Hi folks,
>
> before christmas, I'd like to get 1.3 (java) out of the door.
I agree.
> There's some issues to deal with until that,
> http://code.google.com/p/piccolo2d/issues/list?can=1&q=label%3AMilestone-1.3&colspec=ID+Type+Status+Priority+Milestone+Owner+Toolkit+Compon
Stephen Chin schrieb:
> I should have some time to work on this during the week. Besides
> integrating those changes, some other things I would like to do are:
>
> * Port over my Piccolo-UI testing framework (it is based on FEST-Swing)
> * Create a JavaFX language binding for Piccolo (f
Issue 58: Create a Piccolo2D application archetype
http://code.google.com/p/piccolo2d/issues/detail?id=58
Comment #1 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Milestone-1.3 Milestone-2.0
--
You received this message because you a
Michael Heuer schrieb:
> M. Rohrmoser wrote:
>
>> Hi folks,
>>
>> before christmas, I'd like to get 1.3 (java) out of the door.
>
> I agree.
>
>> There's some issues to deal with until that,
>> http://code.google.com/p/piccolo2d/issues/list?can=1&q=label%3AMilestone-1.3&colspec=ID+Type+Status+P
Issue 68: move SWT dependant classes to a new subproject (piccolo2d-swt)
http://code.google.com/p/piccolo2d/issues/detail?id=68
New issue report by [EMAIL PROTECTED]:
namely the classes in edu.umd.cs.piccolox.swt to a new artifact.
Issue attributes:
Status: New
Owner: [EMAIL PRO
Issue 68: move SWT dependant classes to a new subproject (piccolo2d-swt)
http://code.google.com/p/piccolo2d/issues/detail?id=68
Comment #2 by [EMAIL PROTECTED]:
P.S.: I use git as a proxy for svn - therefore I hesitate a bit to
svn-branch.
http://www.jcurl.org/wiki/GitSvn#Change_svn_backend_url
Issue 68: move SWT dependant classes to a new subproject (piccolo2d-swt)
http://code.google.com/p/piccolo2d/issues/detail?id=68
Comment #1 by [EMAIL PROTECTED]:
I have a patch at hand here in my wc. It's pretty straightforward - shall I
commit it
to the trunk or is it necessary to create a bran
Issue 68: move SWT dependant classes to a new subproject (piccolo2d-swt)
http://code.google.com/p/piccolo2d/issues/detail?id=68
Comment #3 by heuermh:
trunk is ok with me
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this i
Issue 68: move SWT dependant classes to a new subproject (piccolo2d-swt)
http://code.google.com/p/piccolo2d/issues/detail?id=68
Comment #4 by [EMAIL PROTECTED]:
I vote to put this change in trunk as well.
--
You received this message because you are listed in the owner
or CC fields of this is
Issue 49: PFixedWidthStrokes are not fixed width on Mac OSX
http://code.google.com/p/piccolo2d/issues/detail?id=49
Comment #3 by [EMAIL PROTECTED]:
Hi Michael,
I just tried a naive shot a this - can you have a look? Does that solve our
Problem?
Attachments:
PFixedWidthStrokeMRO.java 7
Issue 48: Eliminate dependency on sun.* classes in PFixedWidthStroke
http://code.google.com/p/piccolo2d/issues/detail?id=48
Comment #4 by [EMAIL PROTECTED]:
Hi boys,
I just attached a possible solution to issue#49 - could you have a look and
try it
out? I'm not sure about the required use-cases
Issue 68: move SWT dependant classes to a new subproject (piccolo2d-swt)
http://code.google.com/p/piccolo2d/issues/detail?id=68
Comment #5 by [EMAIL PROTECTED]:
ok, I'll commit that to the trunk as soon as your president-elect tells
us "yes, we
can!".
Issue attribute updates:
Status:
Issue 48: Eliminate dependency on sun.* classes in PFixedWidthStroke
http://code.google.com/p/piccolo2d/issues/detail?id=48
Comment #5 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Status: Started
--
You received this message because you are
Issue 49: PFixedWidthStrokes are not fixed width on Mac OSX
http://code.google.com/p/piccolo2d/issues/detail?id=49
Comment #4 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Status: Started
Labels: -Milestone-2.0 Milestone-1.3
--
You re
Issue 49: PFixedWidthStrokes are not fixed width on Mac OSX
http://code.google.com/p/piccolo2d/issues/detail?id=49
Comment #5 by [EMAIL PROTECTED]:
P.S.: I'd prefer not to implement Stroke and Serializable but rather just
extend
BasicStroke - but as that violates the compatibility rules, I didn
Issue 64: Add shadow nodes to extras
http://code.google.com/p/piccolo2d/issues/detail?id=64
Comment #1 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Status: Started
--
You received this message because you are listed in the owner
or CC fields
Issue 49: PFixedWidthStrokes are not fixed width on Mac OSX
http://code.google.com/p/piccolo2d/issues/detail?id=49
Comment #6 by [EMAIL PROTECTED]:
Sorry, extending BasicStroke is nonsense as it's guts aren't visible. But
getting rid
of Serializable would be fine, wouldn't it?
--
You receiv
Issue 49: PFixedWidthStrokes are not fixed width on Mac OSX
http://code.google.com/p/piccolo2d/issues/detail?id=49
Comment #7 by heuermh:
This looks reasonable at first glance. I will have to try it out on Mac
OSX this
evening.
--
You received this message because you are listed in the own
Issue 22: Name property for PNodes
http://code.google.com/p/piccolo2d/issues/detail?id=22
Comment #5 by [EMAIL PROTECTED]:
Sounds like https://appframework.dev.java.net/intro/index.html
and
http://java.sun.com/j2se/1.5.0/docs/api/java/awt/Component.html#setName(java.lang.String)
+1 from my side.
Author: [EMAIL PROTECTED]
Date: Tue Nov 4 14:31:32 2008
New Revision: 401
Added:
piccolo2d.java/trunk/extras/src/test/java/edu/umd/cs/piccolox/util/PFixedWidthStrokeMRO.java
(contents, props changed)
Log:
issue#49 issue#48 - possible solution.
Added:
piccolo2d.java/trunk/extras/sr
Author: [EMAIL PROTECTED]
Date: Tue Nov 4 14:36:15 2008
New Revision: 402
Modified:
piccolo2d.java/trunk/extras/src/test/java/edu/umd/cs/piccolox/util/PFixedWidthStrokeMRO.java
Log:
issue#49 issue#48 - pull out an extension point.
Modified:
piccolo2d.java/trunk/extras/src/test/java/edu
Issue 49: PFixedWidthStrokes are not fixed width on Mac OSX
http://code.google.com/p/piccolo2d/issues/detail?id=49
Comment #8 by [EMAIL PROTECTED]:
I had a NPE in there and improved it a bit.
See r402 (and r401) for the current version - forget about the attachment
above.
--
You received t
Author: [EMAIL PROTECTED]
Date: Tue Nov 4 15:22:03 2008
New Revision: 403
Modified:
piccolo2d.java/trunk/extras/src/test/java/edu/umd/cs/piccolox/util/PFixedWidthStrokeMRO.java
Log:
issue#49 issue#48 - comments and minor improvements.
Modified:
piccolo2d.java/trunk/extras/src/test/java
Author: [EMAIL PROTECTED]
Date: Tue Nov 4 16:09:55 2008
New Revision: 404
Modified:
piccolo2d.java/trunk/extras/src/test/java/edu/umd/cs/piccolox/util/PFixedWidthStrokeMRO.java
Log:
issue#49 issue#48 - much more elegant plus delegates but also less robust
(sic\!). Maybe we'll keep the p
Author: [EMAIL PROTECTED]
Date: Tue Nov 4 16:53:44 2008
New Revision: 405
Added:
piccolo2d.java/trunk/extras/src/main/java/edu/umd/cs/piccolox/util/PSemanticStroke.java
(contents, props changed)
Removed:
piccolo2d.java/trunk/extras/src/test/java/edu/umd/cs/piccolox/util/PFixedWi
Issue 49: PFixedWidthStrokes are not fixed width on Mac OSX
http://code.google.com/p/piccolo2d/issues/detail?id=49
Comment #9 by [EMAIL PROTECTED]:
I pushed it even further (and maybe too far?) with the last commit r405 -
but I think
the class looks now almost as it should.
PFixedWidthStroke n
Issue 48: Eliminate dependency on sun.* classes in PFixedWidthStroke
http://code.google.com/p/piccolo2d/issues/detail?id=48
Comment #6 by [EMAIL PROTECTED]:
see issue#49
Issue attribute updates:
Status: Duplicate
--
You received this message because you are listed in the owner
or CC f
Issue 22: Name property for PNodes
http://code.google.com/p/piccolo2d/issues/detail?id=22
Comment #6 by [EMAIL PROTECTED]:
and let's not mix "+" and "append" string concatenation.
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starr
Author: heuermh
Date: Tue Nov 4 22:44:31 2008
New Revision: 406
Added:
piccolo2d.java/trunk/examples/src/main/java/edu/umd/cs/piccolo/examples/StrokeExample.java
Modified:
piccolo2d.java/trunk/examples/src/main/java/edu/umd/cs/piccolo/examples/ExampleRunner.java
Log:
Issue 49 ; addi
Issue 49: PFixedWidthStrokes are not fixed width on Mac OSX
http://code.google.com/p/piccolo2d/issues/detail?id=49
Comment #10 by heuermh:
Committing an example. Works ok on Mac OSX with some visual flicker. I
would still
like some time to profile this and compare to workaround I mentioned ab
35 matches
Mail list logo