Re: [piccolo2d-dev] Re: add Aaron Dixon as committer

2010-10-18 Thread Samuel Robert Reid

 Sounds good to me,

Sam Reid

On 10/18/2010 3:33 PM, cmal...@pixelzoom.com wrote:

+1

On Oct 17, 8:56 pm, Michael Heuerheue...@gmail.com  wrote:

I would like to invite Aaron Dixon to join the Piccolo2D project as a
committer.  He is already listed in the parent/pom.xml as a
contributor.

He has been active on the piccolo2d-user mailing list and has written
some nice examples in his github repository at

http://github.com/atdixon/piccolo2d-examples

Though I'm not sure a formal vote is neccessary, here is my +1.

michael


--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en


Re: [piccolo2d-dev] Re: Issue 166 in piccolo2d: Refactor PNode.moveToBack() and related

2010-02-27 Thread Samuel Robert Reid

 raise and lower relative to what?

This is regarding the z-ordering of child nodes within a parent node.

Sam Reid

--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en


Re: [piccolo2d-dev] Re: Release Piccolo2D.Java 1.3

2010-01-26 Thread Samuel Robert Reid
So far, I have tested 3 of my Piccolo applications, and found only 1 
problem in one of the 3 applications.  My problem is exhibited with the 
release candidate 1.3 rc1, but not with our previously used snapshot 
r390 (circa 9/9/2008), and it also appears to be related to PSwing; a 
panel with 2 radio buttons is shown in the scene graph, but is 
noninteractive.  This problem by itself wouldn't suggest to me just 
cause for opposing rc1, unless there is no application-side fix (rather 
than piccolo or pswing fix) that can resolve or workaround the problem 
(I don't yet know whether there is an application-side fix).  However, 
based on cmalley's remarks below, I don't think this version should be 
promoted to a release, and perhaps we'll be able to isolate and resolve 
my issue as we are working on the related pswing issues.


Sam Reid

On 1/26/2010 2:35 PM, cmal...@pixelzoom.com wrote:

---
  [ ] +1  I support this release
  [ ] +0
  [ ] -0
[X] -1  I oppose this release because...

 

PSwing appears to have some new problems, and PhET (my client) relies
heavily on PSwing.  Specifically:

(1) Visibility issues; there are nodes that should be visible and are
not, and vice-versa.
(2) Bounds issues; computing PSwing offsets for the purposes of layout
is resulting in additional whitespace.

I've observed problem (1) in 3 applications, problem (2) in 1
application, on both Windows and Mac platforms.  I've been trying to
isolate the problems in small test applications, but have been
unsuccessful so far.   I'm going to continue with that effort a little
longer, then have a look at PSwing changes.

   


--
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en


[piccolo2d-dev] Default fonts for PText and PHTMLView

2009-11-30 Thread Samuel Robert Reid
Piccolo Team,

My team and I write piccolo applications that need to support many 
languages, and the default fonts specified in PText and PHTMLView often 
need to be replaced (or glyphs can appear as empty boxes). We are 
currently overriding these fonts on a case-by-case basis, but I wanted 
to discuss the possibility of being able to specify these globally, such 
as Swing does in UIManager.

Please let me know what you think,
Sam Reid

-- 
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en


[piccolo2d-dev] New team member introduction

2009-10-30 Thread Samuel Robert Reid

I'd like to introduce our newest team member, Chris Malley.  I've been 
working with him for over 5 years now on piccolo-based science eduction 
projects at http://phet.colorado.edu/, and he's provided several key bug 
reports and patches for Piccolo.  He also has an excellent sense of user 
interface design, and a great understanding of Piccolo's API and 
implementation.  So welcome aboard, Chris!

Sam Reid

--~--~-~--~~~---~--~~
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
-~--~~~~--~~--~--~---



[piccolo2d-dev] Re: Any objections to me adding Cobertura coverage report to the Maven Build?

2009-07-15 Thread Samuel Robert Reid





GPL itself says output from a GPL program is not covered:
http://www.gnu.org/licenses/gpl-faq.html#GPLOutput

Sam Reid

Michael Heuer wrote:

  allain wrote:

  
  
My reasons for wanting to do this are:
- Obviously Code Coverage Metrics are good but this one is IDE
agnostic.
- It has a Hudson plugin that can be installed allowing us to diagram
the (hopefully) increasing progression of code coverage over time in a
nice convenient graph.

http://wiki.hudson-ci.org//display/HUDSON/Cobertura+Plugin

  
  
The _javascript_ code used in the Cobertura reports themselves are
licensed under the GPL, and there was concern in e.g. the Apache
Commons community that distributing those reports violates the terms
of the license.  You may find some discussion threads in archives of
the commons-dev mailing list.  I can't recall what the resolution of
the issue was though.

   michael


  


--~--~-~--~~~---~--~~
Piccolo2D Developers Group: http://groups.google.com/group/piccolo2d-dev?hl=en
-~--~~~~--~~--~--~---





[piccolo2d-dev] Re: Issue 12 in piccolo2d: Generics Support

2009-07-10 Thread Samuel Robert Reid





One effective way to obtain a vote would be to: 
1. branch now (leaving generics in HEAD and 1.4 as an old branch)
2. publish a new version of piccolo with generics and 1.5 dependencies
3. see how many people complain

If there is an overwhelming response that we need to keep up
significant support for 1.4, we can always focus our efforts on the
branch, or just revert HEAD to the 1.4 branch.

Sam Reid

allain wrote:

  If this is the direction the project wants to go in, I'd more than
gladly make the changes to the rest of the code base. Just want to
know that it won't be wasted effort.

When will we have a result for this "vote"?

On Jul 8, 4:04pm, codesite-nore...@google.com wrote:
  
  
Comment #11 on issue 12 by willismorse: Generics Supporthttp://code.google.com/p/piccolo2d/issues/detail?id=12

I vote for adding generics. We're almost ready to drop support for 1.5 in 
our products; 1.4 has been off our
radar for a couple years now.

--
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
-~--~~~~--~~--~--~---