text2d package updated

Qudus · July 19, 2006, 2:52am

Because of bugs and inconsistencies I decided to update the text2d package. It now has a bit nicer fonts, but I still need to play around with the stretch factor. And you can now use different font sizes. And the code has become much cleaner. Of course I sticked to the coding style found there

Please tell me if it breaks anything by accident.

Marvin

EDIT: Ah, before I forget: It is now able to display letters of different widths correctly, which also results in nicer texts, because an “i” doesn’t always necessarily need as much place as an “X” as it was before.

Goliat · July 19, 2006, 9:56am

i can’t say i’m happy with you changing stuff all over the cvs tree … but i guess in this case it was for good … my stuff is very unorganized

Qudus · July 19, 2006, 10:10am

Ah, You’re Florian Hofmann. Grmpf, I could have known that. Sorry, if I knew it, I would certainly have asked before I made this change. Since most original authors are gone and have never been seen anymore and have left some bugs, the project in dead in some parts. I try to revive these parts.

Are there any lines that annoy you?

Marvin

Qudus · July 19, 2006, 6:12pm

Changing the code in some belongs is necessary because we don’t have a committee like e.g. sun has, that discusses for a long time to result in a stable and elaborative API just to be implemented. Some authors code something and after a time they’re not actively developing anymore. If there are bugs in the coding they wrote, someone has to fix it. Since the original author has gone someone else has to take the code and fix it. Well in your case it was a misunderstanding by myself
From time to time (or constantly) an API has to be updated (e.g. for Java 1.5 compliance) which results in a more or less slightly changing API. But I think it’s just normal.

If really many people have developed on a project over the time that haven’t taken part in a committee, one has to clean up the project, when it has become too untidy. This untidyness shell not offend anyone, it’s just normal.

Well, that’s what I want to do.

Marvin

bahuman · July 20, 2006, 8:56am

Hello Marvin,
First off, I want to say that I don’t use Xith, so I have no idea of the impact of your changes. Reading the forums, I gather you’re changing quite a bit.

Of course, the effort is very laudable, but I think you underestimate the impact of changing the API like you do. It stops developers from upgrading to the newer version with confidence, and it will eventually discourage them from using the Xith library at all. Once a library has reached a certain maturity, some ugly parts will just have to be left in, if only to remain backwards compatible.

If you look at the example you yourself gave (the Java API as specified by Sun), you’ll notice that very few of the legacy methods and classes actually completely disappear. Sun will mark them “deprecated” and discourage their use, but they are still there! Some methods have been deprecated since Java 1.0, and yet Sun does not remove them. This must mean Sun appreciates the importance of backward compatibility, doesn’t it ?

Qudus · July 20, 2006, 10:00am

the API changes are quite small, but the code changes are bigger.

bahuman:

Of course, the effort is very laudable, but I think you underestimate the impact of changing the API like you do. It stops developers from upgrading to the newer version with confidence, and it will eventually discourage them from using the Xith library at all. Once a library has reached a certain maturity, some ugly parts will just have to be left in, if only to remain backwards compatible.

If you look at the example you yourself gave (the Java API as specified by Sun), you’ll notice that very few of the legacy methods and classes actually completely disappear. Sun will mark them “deprecated” and discourage their use, but they are still there! Some methods have been deprecated since Java 1.0, and yet Sun does not remove them. This must mean Sun appreciates the importance of backward compatibility, doesn’t it ?

You’re absolutely right, but I guess you got me a bit wrong. I wrote “please tell me, if it brakes something for you”, because I thought, not so many people actually use the text2d library at the moment or they don’t use it very extensively, such that these changes don’t matter at all. But if they do, I will add the changed methods as deprecated. I think this should be ok.

eMKa · July 21, 2006, 7:08pm

@Qudus : “break”, not “brake”
And good work… But, heh I get a NullPointerException, see the stack trace :


java.lang.NullPointerException
	at org.xith3d.ui.hud.HUD.resize(HUD.java:181)
	at org.xith3d.ui.hud.HUD.<init>(HUD.java:594)
	at org.xith3d.ui.hud.HUD.createAndInitialize(HUD.java:813)
	at org.xith3d.ui.hud.HUD.createAndInitialize(HUD.java:844)
	at org.xith3d.ui.hud.QuickHUD.<init>(QuickHUD.java:21)
	at org.stratagem.AnimatedModelViewer.initHUD(AnimatedModelViewer.java:332)
	at org.stratagem.AnimatedModelViewer.<init>(AnimatedModelViewer.java:295)
	at org.stratagem.AnimatedModelViewer.main(AnimatedModelViewer.java:269)

What’s happening, huh ?

Qudus · July 21, 2006, 7:17pm

[quote="<MagicSpark.org [ BlueSky ]>,post:7,topic:27947"]
@Qudus : “break”, not “brake”
[/quote]
I’ll have to remember, finally

[quote="<MagicSpark.org [ BlueSky ]>,post:7,topic:27947"]
And good work… But, heh I get a NullPointerException, see the stack trace :


java.lang.NullPointerException
	at org.xith3d.ui.hud.HUD.resize(HUD.java:181)
	at org.xith3d.ui.hud.HUD.<init>(HUD.java:594)
	at org.xith3d.ui.hud.HUD.createAndInitialize(HUD.java:813)
	at org.xith3d.ui.hud.HUD.createAndInitialize(HUD.java:844)
	at org.xith3d.ui.hud.QuickHUD.<init>(QuickHUD.java:21)
	at org.stratagem.AnimatedModelViewer.initHUD(AnimatedModelViewer.java:332)
	at org.stratagem.AnimatedModelViewer.<init>(AnimatedModelViewer.java:295)
	at org.stratagem.AnimatedModelViewer.main(AnimatedModelViewer.java:269)

What’s happening, huh ?
[/quote]
Can you paste your code? I’m not getting this error.

eMKa · July 21, 2006, 7:37pm


QuickHUD hud = new QuickHUD();

Heheh ;D

Qudus · July 21, 2006, 8:04pm

[quote="<MagicSpark.org [ BlueSky ]>,post:9,topic:27947"]


QuickHUD hud = new QuickHUD();

Heheh ;D
[/quote]
Ok, I’ll check it.

Qudus · July 21, 2006, 8:50pm

Strange. I’m still not getting this error. Please try to find you, which part of your code produces this error.

Are you using Canvas3DWrapper?

eMKa · July 21, 2006, 9:15pm

Yes :


env.addCanvas(new Canvas3DWrapper(Resolution.RES_800X600,
				ColorDepth.B24, DisplayMode.FULLSCREEN, frame));

But I don’t use createStandalone() cause it doesn’t permit me to specify the owner of the canvas.

Qudus · July 21, 2006, 9:22pm

[quote="<MagicSpark.org [ BlueSky ]>,post:12,topic:27947"]
But I don’t use createStandalone() cause it doesn’t permit me to specify the owner of the canvas.
[/quote]
That’s not necessary, because there is Canvas3DPanel, which is much easier to use in this case. But using the contructor this way should be fine, too.

eMKa · July 21, 2006, 9:29pm

Please Qudus, re-add the constants for text alignment in the Text2D class and mark them as deprecated.

That’s a good exercise for you to keep backward compatibility.

Qudus · July 21, 2006, 9:38pm

[quote="<MagicSpark.org [ BlueSky ]>,post:14,topic:27947"]
Please Qudus, re-add the constants for text alignment in the Text2D class and mark them as deprecated.

That’s a good exercise for you to keep backward compatibility.
[/quote]
ok

Qudus · July 21, 2006, 10:17pm

[quote="<MagicSpark.org [ BlueSky ]>,post:14,topic:27947"]
Please Qudus, re-add the constants for text alignment in the Text2D class and mark them as deprecated.

That’s a good exercise for you to keep backward compatibility.
[/quote]
Done. Should be absolutely backwards compatible now.

eMKa · July 21, 2006, 10:22pm

Done. Should be absolutely backwards compatible now.
[/quote]
Good.