Skip to main content

0.62 development branch open

39 replies [Last post]
paulby
Offline
Joined: 2003-06-13
Points: 0

The dev-0-6-2 branch is now open (and dev-0-6-1-1 and dev-0-6-1-1-apiupdate are closed).

Use 'cvs co -r dev-0-6-2 lg3d-core lg3d-demo-apps lg3d-incubator' to get all the new code.

dev-0-6-2 contains all the api changes that we've been working on over the past weeks. Some internal work is still required but the API should be stable and the system is ready for porting of the incubator projects etc.

Please note that lg3d-incubator projects don't compile at the moment as they need porting to the new api.

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
hideya
Offline
Joined: 2003-07-22
Points: 0

Hi Juan,

I tried the new version on 0.62. Looks great, always.

One thing I noticed is that the use of "setVisible()".
If you use "changeVisible()" instead, the Clock app will perform the visibility change animation automatically (this animation is implemented by the scenemanager). Please consider to make the change.

As for the issue you reported:

> The problem comes when I pass the mouse over the Frame3D, and
> the scenemanager "requestHighlight" for it. When it(the Frame3D) gets/drops
> the higllight, the CPU shoots up for a while (100% ~ 3secs), and after that
> period comes down again (if you don't get the mouse in/out the application).

I could reproduce this. Weird thing is that CDViewer and Help don't show this behavior. Maybe your code is hitting something in the transparency manager that might have not been tested fully. It would be great if you could file an issue against it.

Thanks,
hideya

hideya

hideya
Offline
Joined: 2003-07-22
Points: 0

Hi Juan,

> I've just commited the adapted code for the 3Dclock in the dev-0-6-2 branch
> of lg3d-incubator,

I have a suggestion about the 3D clock app.
In the current implementation, there are invocations like setRotationAxis() against the Frame3D object.

However, Frame3D's transform/rotation/scale are something that the scenemanager will operate on directly when arranging the apps in the 3-D space. So, in order to avoid conflicts with what scenemanager does and what your app is trying to do, it is a good idea to introduce an additional container between Frame3D and other components (like clocks, outBox, etc), and perform animation against it (I guess I should add this info to some document).

Currently, there is no big conflict, except that the Clock starts swaying a bit differently when dragged after changing the clock's face. But it can become more tricky when more sophisticated scenemanager appears...

Hope this helps,
hideya

hideya
Offline
Joined: 2003-07-22
Points: 0

Hi Juan,

> > I've just commited the adapted code for the 3Dclock in the dev-0-6-2 branch
> > of lg3d-incubator,

I have one more suggestion. The 3D clock seems to instanciate many java.util.Timer objects. One instanciation creates one thread, so it is resulting in creating many threads. I'd suggest to share one timer object across the entire application., if possible. Would you take a look into it?

hideya

Juan González

Thanks hideya for taking a look at this (it's nice that somebody smarter than
the university teachers looks your code ;). I'm looking to clean that
problems, and i'll post any update here.

Thanks again

--
opsi
--
Indifference will be the downfall of mankind, but who cares?

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
For additional commands, e-mail: interest-help@lg3d.dev.java.net

Anonymous

> Just curious -- what kind of machine you use for
> running LG3D? CPU, Memory, Graphics card and Linux
> distro?
> (please write back to me after your illness goes
> away)

P4 2400 mhz, ram 512 mb, Geforce 4 mx 440 64 mb, Gentoo Linux

(Today I'm feeling better)

> Please don't hesitate to file issues using the
> following page (after you get better):
>
> https://lg3d-core.dev.java.net/issues/reports.cgi

I don't know how to do it, I've never done a report...

Amir Bukhari

here is one exception which occure always in lgserver.log when an X11
application opened:

Mar 20, 2005 10:32:54 AM org.jdesktop.lg3d.wg.TransparencyManager
addGraph
SEVERE: Problems setting up TransparencyManager
java.lang.ClassCastException:
org.jdesktop.lg3d.displayserver.nativewindow.NativeWindowObject$Gr
Cell
at org.jdesktop.lg3d.sg.Group.getAllChildren(Group.java:162)
at
org.jdesktop.lg3d.sg.utils.traverser.TreeScan.actualFindNode(TreeScan.java:146)
at
org.jdesktop.lg3d.sg.utils.traverser.TreeScan.actualFindNode(TreeScan.java:148)
at
org.jdesktop.lg3d.sg.utils.traverser.TreeScan.actualFindNode(TreeScan.java:148)
at
org.jdesktop.lg3d.sg.utils.traverser.TreeScan.findNode(TreeScan.java:81)
at
org.jdesktop.lg3d.wg.TransparencyManager.addGraph(TransparencyManager.java:144)
at
org.jdesktop.lg3d.wg.Component3D.addChild(Component3D.java:397)
at
org.jdesktop.lg3d.scenemanager.utils.decoration.GlassyNativeWindowLookAndFeel.setupCo
onents(GlassyNativeWindowLookAndFeel.java:160)
at
org.jdesktop.lg3d.scenemanager.utils.decoration.GlassyNativeWindowLookAndFeel.initial
e(GlassyNativeWindowLookAndFeel.java:143)
at
org.jdesktop.lg3d.displayserver.nativewindow.NativeWindow3D.createLookAndFeel(NativeW
dow3D.java:143)
at
org.jdesktop.lg3d.displayserver.nativewindow.NativeWindow3D.nativeSizeChanged(NativeW
indow3D.java:198)
at
org.jdesktop.lg3d.displayserver.nativewindow.NativeWindow3D.visibilityChanged(NativeW
indow3D.java:328)
at
org.jdesktop.lg3d.displayserver.nativewindow.x11.X11Client.mapNotify(X11Client.java:2
40)
at
org.jdesktop.lg3d.displayserver.nativewindow.x11.X11WindowManager.mapNotify(X11Window
Manager.java:595)
at
org.jdesktop.lg3d.displayserver.nativewindow.x11.X11WindowManager.dispatch(X11WindowM
anager.java:250)
at
org.jdesktop.lg3d.displayserver.nativewindow.x11.X11WindowManager.readAndDispatchEven
t(X11WindowManager.java:217)
at
org.jdesktop.lg3d.displayserver.nativewindow.x11.X11WindowManager.run(X11WindowManage
r.java:200)
at java.lang.Thread.run(Thread.java:595)

On Sat, 2005-03-19 at 21:32 -0500, lg3d-interest@javadesktop.org wrote:
> > this answer quickly: reasonable... yes, i can say that i could use lg3d without singular problem, a little slow but the 345M video card is not a great support to expand lot of performance...
>
> Great. I'm glad to know that. Once a texture manipulation issue gets fixed in Java 3D, it could be better. Thanks for the reply, Florian!
>
> hideya
> ---
> [Message sent by forum member 'hideya' (hideya kawahara)]
>
> http://www.javadesktop.org/forums/thread.jspa?messageID=65654𐁶
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
> For additional commands, e-mail: interest-help@lg3d.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
For additional commands, e-mail: interest-help@lg3d.dev.java.net

Anonymous

I updated lg3d dev-0.6.2 and I'm actually running it. It is faster than the 0.6.1. So very faster (but still not fast). There are also lots of problems with the windows.
Just a little example:
I started an xterm by clicking on the icon on the taskbar. I iconified it, then i clicked on the icon on the bar. The xterm raised wasn't usable, and cannot be iconified again. I had to close it.

p.s. sorry for my english, I have the flu and I cannot write well even in my own language in this condition

hideya
Offline
Joined: 2003-07-22
Points: 0

Hi Raffo,

Thanks for testing the new build, even though you have a flu! I appreciate it a lot.

> I updated lg3d dev-0.6.2 and I'm actually running it. It is faster than the 0.6.1. So very faster

I'm very happy to be informed about that!
Just curious -- what kind of machine you use for running LG3D? CPU, Memory, Graphics card and Linux distro?
(please write back to me after your illness goes away)

> (but still not fast).

Yeah, there are (at least) two issues we know -- some inefficiency in a specific texture manipulation by Java 3D and lots of temporary object creation in the picking code in Java 3D. Paulby is looking into these, and knows more details about the cause and schedule for fixing them. I thought that he is trying to fix them in Java 3D 1.4 (thus LG3D 0.7).

> I started an xterm by clicking on the icon on the taskbar. I iconified it, then i clicked on the icon on the bar. The xterm raised wasn't usable, and cannot be iconified again. I had to close it.

Please don't hesitate to file issues using the following page (after you get better):

https://lg3d-core.dev.java.net/issues/reports.cgi

Thanks, and take care...

hideya

P.S.
> p.s. sorry for my english, I have the flu and I cannot write well even in my own language in this condition

Actually, I couldn't tell anything wrong in your writing ;-)

fl0rian
Offline
Joined: 2004-12-05
Points: 0

Hi,
the earth icon doesn't work.
Sorry to write only that.

Florian.

Yuichi SAKURABA

Hi,

On Sat, 19 Mar 2005 01:21:20 EST
lg3d-interest@javadesktop.org wrote:
> Hopefully incubator project owners will port their apps to the 0.62 API shortly...
>
> "Porting to 0.62" Wiki is at:
> http://wiki.java.net/bin/view/Javadesktop/PortingTo062

I've ported the Zoetrope to 0.62 and committed.

When i ported it, I have a question about Component3D#setSizeHint/getSizeHint.
I'm happy that event model changes to AWT/Swing style in dev-0-6-2.
It's easy for us to make a program.

If LG3D goes forward to AWT/SWING progrming style, I think PreferredSize
is better than SizeHint. I think the meaning of PreferredSize is similar
to one of SizeHint. Moreover, PreferredSize is familiar word to AWT/Swing
programmers.

How do you seem?

Regards,
Yuichi.

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
For additional commands, e-mail: interest-help@lg3d.dev.java.net

hideya
Offline
Joined: 2003-07-22
Points: 0

So far, we got the following feedback from Yuichi:

> If LG3D goes forward to AWT/SWING progrming style, I think PreferredSize
> is better than SizeHint. I think the meaning of PreferredSize is similar
> to one of SizeHint. Moreover, PreferredSize is familiar word to AWT/Swing
> programmers.

If we don't hear any objection from the community, Paul and I are thinking to take this suggestion into the 0.62 API, since it does make sense. Would it be fine with you folks?

Also, if you have any other suggestions, please let us know by the end of this week (the sooner, the better).

Thanks,
hideya

hideya
Offline
Joined: 2003-07-22
Points: 0

> here's 100 errors with incubator apps, without lg3d-incubator, ant works fine.

I've ported the Ping Pong demo, and excluded other apps that have not been ported to 0.62 from the javac compilation files in the dev-0-6-2 version of incubator's build.xml.

You should be able to check out the incubator's dev-0-6-2 branch and try the Clock and the Ping Pong apps.
NOTE: please realize the issue about the Clock app Juan reported in this thread.

hideya

fl0rian
Offline
Joined: 2004-12-05
Points: 0

>I'm happy to know that you are testing LG3D on a IGP, 345M. I also hope it's not the cause of the issue, but we haven't had good experience with ATI's... Did 0.61 LG3D run on the chip reasonably?

this answer quickly: reasonable... yes, i can say that i could use lg3d without singular problem, a little slow but the 345M video card is not a great support to expand lot of performance...

Florian

hideya
Offline
Joined: 2003-07-22
Points: 0

> this answer quickly: reasonable... yes, i can say that i could use lg3d without singular problem, a little slow but the 345M video card is not a great support to expand lot of performance...

Great. I'm glad to know that. Once a texture manipulation issue gets fixed in Java 3D, it could be better. Thanks for the reply, Florian!

hideya

fl0rian
Offline
Joined: 2004-12-05
Points: 0

>Please file an issue against it at the following page and add the log to the issue

I did it.

I've compile lg3d with incubator: no problem this time.
On the taskbar no icons (ping-pong and clock) and two computeur-icon wich launch extern.
Try few secondes and the system freeze.

Florian.

hideya
Offline
Joined: 2003-07-22
Points: 0

> >Please file an issue against it at the following page and add the log to the issue
>
> I did it.

Thanks, Florian!

> I've compile lg3d with incubator: no problem this time.

Glad to hear that :-)

> On the taskbar no icons (ping-pong and clock) and two computeur-icon wich launch extern.

Yeah, I notice this too. I'll check with Paul any intention about it.

> Try few secondes and the system freeze.

Too bad. Let's see if it is related to the new transparency management and we can fix it in 0.62...

hideya

fumi
Offline
Joined: 2004-05-04
Points: 0

Hello,

We are using the branch 0.62. But we have a problem
of "Component3D#setTransparencey(float val)" as following...

import org.jdesktop.lg3d.utils.shape.*;
import org.jdesktop.lg3d.wg.*;

public class Test {
public Test() {
Frame3D frame = new Frame3D();

Box box = new Box(0.03f, 0.03f, 0.03f,
new SimpleAppearance(1.0f, 1.0f, 1.0f, 0.5f));
Component3D comp = new Component3D();
comp.addChild(box);
comp.setTransparency(1.0f);

frame.addChild(comp);
frame.changeEnabled(true);
frame.changeVisible(true);
}

public static void main(String[] args) {
new Test();
}
}

The SimpleAppearance alpha argumenet is set to 0.5f.
Transparency Value in Component3D is set to 1.0f.
When we execute this program, a box which has the transparency value
0.5f is diplayed.
The transparency value which is set in set in Component3D is ignored.

This problem occurs in Linux, but does not occur in Windows XP.
Our test Enviroments are ...
-Vine Linux3.0, 2.4.26, GeForce,
JDK1.5.0_02, JAI 1.1.2_01, JAVA3D 1.3.2
-FedoraCore3 2.6.10, GeForce6600, DispDriver v1.0-7167
JDK1.5.0_02, JAI 1.1.2_01, JAVA3D 1.3.2

-> this problem occurs

-WindowsXP SP2 DispDriver v65,
JDK1.5.0_02, JAI 1.1.2_01, JAVA3D 1.3.2

-> no problems

Please tell us about this Problem in your enviroments.

thanks

fumi

paulby
Offline
Joined: 2003-06-13
Points: 0

Thanks for raising this issue. I think this is probably a timing/threading issue. I'll try and reproduce it tomorrow when I get in the office. In the meantime can you please file a bug on the issue so we can track it.

Thanks

Paul

Message was edited by: paulby

paulby
Offline
Joined: 2003-06-13
Points: 0

Actually I was wrong, the system is behaving exactly as it should, let me explain and then we can discuss how to document it so other people don't fall into the same trap.

The actual base transparency of an object is specified by that objects appearance TransparencyAttribute. The setTransparency and changeTransparency methods then allow the user to apply an animated modification to the base transparency.

When you call setTransparency(1) the system does indeed modify the transparency to 1, however once you make the Frame3D live via setEnabled() the GlassySceneManager applies it's transparency animation which results in a transparency level of 0.25. This is how GlassSceneManager shows the window does not have focus.

The calls to set/changeTransparency modify the underlying transparency specified in the objects appearance. So in your case with the appearance transparency set to 0.5 a call to setTransparency(0) will result in a transparency of 0.5 while setTransparency(1) will result in a transparency on 1.

Another way to think about this is that the appearance specifies the maximum opaqueness of an object and the Comonent3D set/changeTransparency methods will animation from this maximum opaqueness to fully transparent as specified.

Anonymous

while using it a completely white zone appeared on the screen..
here you can see what I'm talking about..

http://img137.exs.cx/my.php?loc=img137&image=lg54zq.png

fl0rian
Offline
Joined: 2004-12-05
Points: 0

yes i've seen something like that on my desktop.

Florian

paulby
Offline
Joined: 2003-06-13
Points: 0

Please file a bug with as much info as possible about what you were doing when the white area appeared.

fl0rian
Offline
Joined: 2004-12-05
Points: 0

well, the thing appears to me one time in the first time of current branch and nothing after that...
If the white form does another apparition, i file an issue.

Florianairolf

dai
Offline
Joined: 2004-11-03
Points: 0

Hi, all.

Belatedly, at last, I've checked out 0.6.2.
At the first setout, I DO want to say, it runs quite faster that that of the old one!! Phew, really cool & usefull!! ;)

When it comes to errors, 4 errors appear.(Actually 1 error)

Main.java [org.jdesktop.lg3d.displayserver].
Error messages are same, "Can not resolve LgBuildInfo".

/******
logger.info("Version : "+LgBuildInfo.getVersion());
logger.info("Built : "+LgBuildInfo.getBuildDate());
logger.info("Build Type : "+LgBuildInfo.getBuildType());

logger.info("LG Build Time : " + LgBuildInfo.getBuildTimeStamp());
********/

Does anyone have these errors??

paulby
Offline
Joined: 2003-06-13
Points: 0

LgBuildInfo is created dynamically by the ant script at compile time. Try running ant clean and then ant again and look for ant problems in the early stages.

yasuyuki@javaopen.org

hi.

> Use 'cvs co -r dev-0-6-2 lg3d-core lg3d-demo-apps lg3d-incubator' to get all the new code.

My Eclipse 3.1 reports these 'operand type missmatch' errors.

org.jdesktop.lg3d.utils.layoutmanager.BookshelfLayout (line 128)
org.jdesktop.lg3d.utils.layoutmanager.HallwayLayout (line 162)
org.jdesktop.lg3d.utils.layoutmanager.HorizontalLayout (line 172)

if (compList.indexOf(comp) == constraints) {

I re-write it like this:

if (compList.get(compList.indexOf(comp)).equals(constraints)) {

Is this correct?

--
ENDO Yasuyuki
http://www.javaopen.org/~yasuyuki/
http://www.javaopen.org/jfriends/

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
For additional commands, e-mail: interest-help@lg3d.dev.java.net

hideya
Offline
Joined: 2003-07-22
Points: 0

Hi Yasuyuki,

> My Eclipse 3.1 reports these 'operand type missmatch' errors.
>
> org.jdesktop.lg3d.utils.layoutmanager.BookshelfLayout (line 128)
> org.jdesktop.lg3d.utils.layoutmanager.HallwayLayout (line 162)
> org.jdesktop.lg3d.utils.layoutmanager.HorizontalLayout (line 172)
>
> if (compList.indexOf(comp) == constraints) {

Eclipse seems to perform tighter parameter checking.
I expected that the compiler performs auto-unboxing against 'constraints' because the type of the left argument of the "==" operator is 'int'. But in order to do so, I should have clearly said that:
[code]
if (compList.indexOf(comp) == (Integer)constraints) {
[/code]
I've fixed the issue and will putback the changes together with other fix shortly.

Thanks for reporting the issue!

hideya

paulby
Offline
Joined: 2003-06-13
Points: 0

The 1.5 compiler does do autoboxing for this, the original code was correct. You should file a bug on Eclipse.

hideya
Offline
Joined: 2003-07-22
Points: 0

> The 1.5 compiler does do autoboxing for this, the original code was correct. You should file a bug on Eclipse.

Yeah, but in this case,

> if (compList.indexOf(comp) == constraints) {

the type of 'constraints' is 'Object' (not 'Integer').
I checked JLS ver 3 (that includes changes for JSR 201) but it basically says an Integer object can be unboxed to an 'int' value. I couldn't find a behavioral definition in the case the type was 'Object'...

hideya

fl0rian
Offline
Joined: 2004-12-05
Points: 0

Here, live on looking glass, my system doesn't crash, the translucidity it's good, many thanks to you.
And thanks to the japanese's devellopers about ls3d, very nice and zoetroppe, the image viewer, wonderfull.

Have a nice day.

Florian.

Juan González

Hi all,
I've just commited the adapted code for the 3Dclock in the dev-0-6-2 branch
of lg3d-incubator, but i've noticed an issue that i'm not sure where is
coming from. The problem comes when I pass the mouse over the Frame3D, and
the scenemanager "requestHighlight" for it. When it(the Frame3D) gets/drops
the higllight, the CPU shoots up for a while (100% ~ 3secs), and after that
period comes down again (if you don't get the mouse in/out the application).
Anyway, it may be problem with my (poor) code ;)

Does it make any sense to fill an issue for that, or it's a known problem?
--
opsi
--
Indifference will be the downfall of mankind, but who cares?

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
For additional commands, e-mail: interest-help@lg3d.dev.java.net

hideya
Offline
Joined: 2003-07-22
Points: 0

Hi Juan,

Great! Thanks for your quick action to port to 0.62!
I'm very happy to see that you've done it so quickly.
Did it go all right? What kind of additional info to the Porting 0.62 Wiki would help? (or, was it helpful???)

> Anyway, it may be problem with my (poor) code ;-)
> Does it make any sense to fill an issue for that, or it's a known problem?

Please file an issue against it. I guess it is an issue related to newly introduced transparency manager. It is great since it tries to change translucency of an entire application (if you know Java 3D well, you'd understand how difficult it is. I'm glad that Paul implemented it), but it does some very complicated work. The code if fresh, so could be an issue there.

Also, if you find anything unhappy about the new API (except the porting work itself), please let us know.

Thanks,
hideya

hideya
Offline
Joined: 2003-07-22
Points: 0

> Please file an issue against it. I guess it is an issue related to newly introduced transparency manager.

I skipped one explanation -- the updated scenemanager changes app's translucency automatically when you move mouse over it. The transparency manager does all the messy work to realize the effect.

hideya

fl0rian
Offline
Joined: 2004-12-05
Points: 0

Hi,

I've testing this new dev branch and after a first reboot, i can saw the rapidity and agility of the mouse (great), i opened the web browser... translucide all the time and the system freeze... well i reboot ant test it with dev-mode and after few secondes it freezes too.
Just for you to know (if you didn't remember), i've a radeon 345M igp in my notebook and there's now a problem with [b]drm[/b] whereas with last branch there wasn't.
i'll post my logs later if you think it's not my video card the cause of problem (i've pray not)

Florian

hideya
Offline
Joined: 2003-07-22
Points: 0

Hi Florian,

Thanks for reporting the issue.

> i opened the web browser... translucide all the time and the system freeze...

Please file an issue against it at the following page and add the log to the issue:

https://lg3d-core.dev.java.net/servlets/ProjectIssues

> i've a radeon 345M igp in my notebook and there's now a problem with drm whereas with last branch there wasn't.

I'm happy to know that you are testing LG3D on a IGP, 345M. I also hope it's not the cause of the issue, but we haven't had good experience with ATI's... Did 0.61 LG3D run on the chip reasonably?

hideya

fl0rian
Offline
Joined: 2004-12-05
Points: 0

hi,
there's 100 errors with incubator apps, without lg3d-incubator, ant works fine.

Florian

hideya
Offline
Joined: 2003-07-22
Points: 0

Thanks for trying it out, Florian!

> there's 100 errors with incubator apps, without lg3d-incubator, ant works fine.

Hopefully incubator project owners will port their apps to the 0.62 API shortly...

"Porting to 0.62" Wiki is at:
http://wiki.java.net/bin/view/Javadesktop/PortingTo062

hideya

Juan González

Hi all,
i've almost ported the clock to 0.62, but i've a question: Do I put it in the
dev-0-6-2 branch directly?

Regards

On Saturday 19 March 2005 06:21, lg3d-interest@javadesktop.org wrote:
> Thanks for trying it out, Florian!
>
> > there's 100 errors with incubator apps, without lg3d-incubator, ant works
> > fine.
>
> Hopefully incubator project owners will port their apps to the 0.62 API
> shortly...
>
> "Porting to 0.62" Wiki is at:
> http://wiki.java.net/bin/view/Javadesktop/PortingTo062
>
> hideya
> ---
> [Message sent by forum member 'hideya' (hideya kawahara)]
>
> http://www.javadesktop.org/forums/thread.jspa?messageID=65493&#65493
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
> For additional commands, e-mail: interest-help@lg3d.dev.java.net

--
opsi
--
Indifference will be the downfall of mankind, but who cares?

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
For additional commands, e-mail: interest-help@lg3d.dev.java.net

Amir Bukhari

On Sat, 2005-03-19 at 14:58 +0000, Juan González wrote:
> Hi all,
> i've almost ported the clock to 0.62, but i've a question: Do I put it in the
> dev-0-6-2 branch directly?
>

I don't think there is a problem, as soon as you only put your change
into incubator subproject only!

-Amir

> Regards
>
> On Saturday 19 March 2005 06:21, lg3d-interest@javadesktop.org wrote:
> > Thanks for trying it out, Florian!
> >
> > > there's 100 errors with incubator apps, without lg3d-incubator, ant works
> > > fine.
> >
> > Hopefully incubator project owners will port their apps to the 0.62 API
> > shortly...
> >
> > "Porting to 0.62" Wiki is at:
> > http://wiki.java.net/bin/view/Javadesktop/PortingTo062
> >
> > hideya
> > ---
> > [Message sent by forum member 'hideya' (hideya kawahara)]
> >
> > http://www.javadesktop.org/forums/thread.jspa?messageID=65493ï¿•
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
> > For additional commands, e-mail: interest-help@lg3d.dev.java.net
>

---------------------------------------------------------------------
To unsubscribe, e-mail: interest-unsubscribe@lg3d.dev.java.net
For additional commands, e-mail: interest-help@lg3d.dev.java.net