samreid / piccolo2d

Automatically exported from code.google.com/p/piccolo2d
0 stars 0 forks source link

Piccolo doesn't seem to work with gcj java compiler #77

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start Eclipse, start a new project, copy/paste the hello world example
from the piccolo tutorial.
2. Go to project properties / Java build path / libraries.
3. You'll probably have JRE System Library [java-1...-sun...]
4. Click it and edit to change to the java-1...-gcj library (if it is
installed)
5. Run the application

What is the expected output? What do you see instead?

expected: Appearance of the window with text "hello world"
instead: Appearance of empty window. Error messages on console:

Exception during event dispatch:
java.lang.IllegalArgumentException: Start position must be < limit.
  at java.awt.font.TextMeasurer.getLayout(libgcj.so.81)
  at java.awt.font.LineBreakMeasurer.nextLayout(libgcj.so.81)
  at edu.umd.cs.piccolo.nodes.PText.computeNextLayout(Unknown Source)
  at edu.umd.cs.piccolo.nodes.PText.recomputeLayout(Unknown Source)
  at edu.umd.cs.piccolo.nodes.PText.setText(Unknown Source)
  at edu.umd.cs.piccolo.nodes.PText.<init>(Unknown Source)

What version of the product are you using? On what operating system?

piccolo 1.2.1, ubuntu 7.x

Please provide any additional information below.

not much else to say...

Original issue reported on code.google.com by Lko...@gmail.com on 28 Jan 2009 at 9:06

GoogleCodeExporter commented 9 years ago

Original comment by heue...@gmail.com on 16 Mar 2009 at 6:04

GoogleCodeExporter commented 9 years ago
Let me start by saying that I too think having Piccolo run on gcj would rock. I 
can't  wait for the day when Piccolo runs 
"out of box" on my Ubuntu system.

Unfortunately, after doing some research (see references below), the problem 
lies in gcj's current state. Only 93.12% of 
java.awt is implemented and java.awt.font is only at 90.45%.

If we were to write Piccolo to account for those deficiencies, we'd end up 
implementing a good portion of what a complete 
JDK already does.

So, unfortunately, we can't deal with this problem since it is outside the 
scope of this project.

Allain

http://gcc.gnu.org/java/status.html
    re. awt: "A lot of code exists, but not enough
    for use in real applications."

http://www.kaffe.org/~stuart/japi/htmlout/h-jdk14-classpath
    Claims that java.awt is 93.12% implemented and 
    java.awt.font is only 90.45% implemented.

Original comment by allain.lalonde on 21 Jul 2009 at 6:45

GoogleCodeExporter commented 9 years ago
Verifying Wont Fixes. Reasons are sound by my mind.

Original comment by allain.lalonde on 5 Nov 2009 at 3:15