Hi,
> FYI, the build containing Jim's changes for
>the puggable rasterizer is finally out (see attached
>email).
Yeah cool. I've already checked it out.
I'll try to address Jim's 'complaints' as soon as possible.
Unfortunately, the legal side of the story doesn't seem to pan out as
easi
FYI, the build containing Jim's changes for
the puggable rasterizer is finally out (see attached
email).
List of changes:
http://download.java.net/jdk7/changes/jdk7-b14.html
Relevant bug id:
6566807: Need pluggable interface to facilitate OpenJDK replacement of
encumbered Duc
How's the read-only HG and/or SVN workspace for Java2D going?
I'm not working on that - I'll ping the people involved...
I'm told we're still working on it. Our team workspace suffering
corruption yesterday didn't help (already restored).
Thanks for the patience.
Thanks,
Dmitri
True. However, the clipping can simply be ignored or ripped out of you
don't need this. Should make the code simpler and faster.
It won't be needed to satisfy the needs of the RenderingEngine plugin
API that I sent out a few days ago. Longer term we may want to stick
with Region clipping as w
On Tue, 2007-06-12 at 21:26 +0200, Roman Kennke wrote:
> Hi Mark,
>
> > >I don't think it's Sun only policy, pretty much any company has it.
> > >It is easy to become tainted by looking at other's people code.
> > >The fact that the code is open-source doesn't matter, since
> > >it
Hi Jim,
> - It's also very basic in its mathematical techniques, though. The math
> to trace the slope of a line is inefficient and inaccurate and it
> flattens everything before tracing. There is a lot of room for
> improvement here.
Indeed, that's true.
> - It uses a push technology - yo
Some preliminary thoughts in looking over the ScanlineConverter...
- It does quite a lot for such a small piece of code - very cool.
- It's also very basic in its mathematical techniques, though. The math
to trace the slope of a line is inefficient and inaccurate and it
flattens everything be
I'm starting to look at this now, but first I wanted to give some
feedback on the technical notes below:
Roman Kennke wrote:
I finished up what I wanted to add to my rasterizer and want to make it
available to anybody who would like to review it or play with it. You
can download the code here:
Dmitri Trembovetski wrote:
I have to ask my boss(es). I believe that I am the copyright holder of
that code because I didn't write it in my work time, and not for the
purpuse of using it in the JamaicaVM, and I submitted this particular
piece of code under my personal FSF copyright assignment. Bu
Hello Mark,
> >>> I think it would make sense to at least provide read access to the real
> >>> group workspace (if you're paranoid then maybe only to group members,
> >>> but then comes the question, how can anybody become a group member?).
> >>
> >>I'll see if we could arrange that. I belie
> From: [EMAIL PROTECTED]
> Date: Tue, 12 Jun 2007 19:32:51 +0200
> ...
>>> I think it would make sense to at least provide read access to the real
>>> group workspace (if you're paranoid then maybe only to group members,
>>> but then comes the question, how can anybody become a group member?).
>>
Hi Mark,
> >I don't think it's Sun only policy, pretty much any company has it.
> >It is easy to become tainted by looking at other's people code.
> >The fact that the code is open-source doesn't matter, since
> >it's a question of copyright.
>
> Note that the copyright isn't in q
Dmitri Trembovetski <[EMAIL PROTECTED]> writes:
> Roman Kennke wrote:
>However, in this case it will be useful for everybody
>else to understand the restrictions under which we currently
>operate.
Thanks, that is useful.
>I don't think it's Sun only policy, pretty much any company
Roman Kennke <[EMAIL PROTECTED]> writes:
> > > The remaining issue is
> > > that the copyright is assigned to the FSF. I have hoped that you would
> > > review my code before I start the copyright grantback dance for that
> > > code. I am currently discussing this issue with Tom Marble and Mark
> >
Hi Phil,
> > When I wrote this code for GNU Classpath, I assigned copyright to the
> > FSF, just like OpenJDK contributions are copyright-assigned to Sun. With
> > the difference that the SCA is automatically granting the contributor
> > all rights to the code, while with the FSF CA I need to go t
Roman Kennke wrote:
When I wrote this code for GNU Classpath, I assigned copyright to the
FSF, just like OpenJDK contributions are copyright-assigned to Sun. With
the difference that the SCA is automatically granting the contributor
all rights to the code, while with the FSF CA I need to go thr
Hi,
> > I will send in my signed SCA the next couple of days, and at the same
> > time find out who is the actual copyright owner (me, or aicas - my
> > employer -, aicas already signed the SCA even). The remaining issue is
> > that the copyright is assigned to the FSF. I have hoped that you would
Hi,
>getting back on the list.
Good!
> >>I think there are still legal issues preventing
> >>us looking at this code =(
> >
> > Unbelievable. But oh well... Why exactly can't you *look* at the code.
> > Because it's not submitted via the SCA? I mean, it's free, open source
> > softw
Roman Kennke wrote:
Hi,
I will send in my signed SCA the next couple of days, and at the same
time find out who is the actual copyright owner (me, or aicas - my
employer -, aicas already signed the SCA even). The remaining issue is
that the copyright is assigned to the FSF. I have hoped that y
Hi Jim,
> The status on the pluggability API is that it is now completed and in
> our 2D integration workspaces waiting to go through the testing and
> promotion queues. The best current estimate as to when all of that
> process will be done is that it will probably appear on the OpenJDK
> pr
Note that the webrev includes some of the closed sources too :
Javadocs Cdiffs Sdiffs Old New
src/closed/share/classes/sun/dc/pr/PathStroker.java
Javadocs Cdiffs Sdiffs Old New src/closed/share/native/sun/dc/pr/PathStroker.c
I am quite sure they would need to be [manually] elided.
-phil.
Tom
Dmitri Trembovetski wrote:
> It is also unfortunate that you do not have access to our
> code review system - although this is relatively easy
> to fix - we can include you as a reviewer in relevant
> code changes (the system is email and web-based).
>
> We'll have to send you the actual
Hi Roman,
getting back on the list.
Roman Kennke wrote:
Hi Dmitri,
first of all, you should continue discussion on the mailing list IMO. It
doesn't leave a good impression against 'the community' when half of the
discussions are held privately. I won't CC the list now though, because
you
Hi there,
> Thanks for this. Jim Graham is the best person to comment
> on this but he's on vacation until next week some time.
I'm also back from my honeymoon vacation now. Has anybody had the time
to review my rasterizer yet?
/Roman
--
Dipl.-Inf. Roman Kennke, Software Engineer, http://kenn
Roman,
Thanks for this. Jim Graham is the best person to comment
on this but he's on vacation until next week some time.
And congrats on getting married.
-phil.
Roman Kennke wrote:
Hello,
I finished up what I wanted to add to my rasterizer and want to make it
available to anybody who would l
Hello,
I finished up what I wanted to add to my rasterizer and want to make it
available to anybody who would like to review it or play with it. You
can download the code here:
http://kennke.org/~roman/rasterizer-rkennke-2007-05-24.zip
Legal note: Right now this is ripped straight out of GNU Cla
26 matches
Mail list logo
