Hrmph, spoke too soon. It doesn't work well at all (menubars flash on and off too briefly to click on anything, comboboxes don't drop down). Guess that backport to 1.3.1 will be needed after alll...sigh
Ditto on all this. Tried it with Jaguar 10.2.2 build 6F15 and still the same as Hani. Funny thing is that I can't even find how to turn off HWAccell in 1.4.1... doesn't look like it's possible.
FYI It is actually possible to get it working rather well! Change IDEA_POPUP_WEIGHT in idea.sh to medium, and things will work surprisingly well. I was able to create a project and navigate around it somewhat. Although ctrl-n doesn't seem to work, and there is some slight font clipping (but nothing too drastic).
Seems the issue is here: NOT IMPLEMENTED FOR CLASS: class sun.awt.font.NativeFontWrapper - usePlatformFontMetrics we do not need to implement - returning null)
Not sure who's saying we do not need to implement returning null... but that bites :)
Hum no mac look and feel, but the funny thing is that when a window wants to first redraw half the mac look and feel shows up, and then it's over drawn by their interface.
Seems slow to come up with some windows at first, but then picks up speed once it configures the window the first time. Not sure if they're caching it or something.
I can't seem to submit key commands to anything. Copy paste stuff like that just throws errors. I guess I'm gonna have to start filing bugs and see what comes out of their tests.
I was just told that the Apple dev group is using IDEA for testing and they're aware of a lot of the issues, so I'm not sure who to throw this at.
It's pretty severe focus issues which I suspect IntelliJ can't do much about. Looks like editor body panel never actually gets focus. If you scroll around you'll notice that the scrollbar gets the actual events and scrolls down the editor, but the cursor itself doesn't move. It would explain the key commands not working too I think.
Yeah, I'm also noticing that nothing about this build supports anything JDK 1.4.1 on the mac, which is no surprise.
Also it seems that IntelliJ is using their own redraw mechanisms for SWING, which is going to make it very difficult for them to properly support 1.4.1 on OS X. I'm hoping that once they get their hands on the 1.4.1 JDK they can write some code to hand the draws to the JDK and not do it on their own, otherwise everything apple went through to improve the JDK and support tight integration with the OS was a complete waste of space and time.
After quitting the app now I'm getting this nice stack every time I restart and I can't start the app up at all now:
NOT IMPLEMENTED FOR CLASS: class sun.awt.font.NativeFontWrapper - usePlatformFontMetrics WARNING: handleEvent is using old paintArea.paint(fTarget, true)!!! apple.awt.EventQueueExceptionHandler Caught Throwable : java.lang.ClassCastException at apple.awt.CEventQueue.push(CEventQueue.java:190) at com.intellij.ide.p.initComponent(p.java:104) at com.intellij.openapi.components.a.a.a(a.java:88) at com.intellij.openapi.components.a.a.getComponent(a.java:10) at com.intellij.openapi.components.a.a.j(a.java:102) at com.intellij.openapi.components.a.a.f(a.java:23) at com.intellij.openapi.application.a.e.g(e.java:248) at com.intellij.idea.r.g(r.java:17) at com.intellij.idea.r.a(r.java:13) at com.intellij.idea.l.run(l.java:2) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178) at java.awt.EventQueue.dispatchEvent(EventQueue.java:448) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136) at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)
Why even try to get IDEA to work with DP2? It's a half-formed thing with warnings plastered all over it. Even aside from the partially implemented Cocoa GUI wrappers, it's bloated with debugging statements. It's slower than 1.3.1 with benchmarks like scimark2.
Not that I don't think it's worth keeping an eye on what Apple and Sun are doing to make sure the eventual shipping version works perfectly with IDEA. I just don't want attention deflected from the backport... I've been waiting for a long time to get a post-629 build, and I don't fancy waiting until a beta version of 1.4.1 ships in 1Q2003 to get it.
yup. I just smoked the mac version and started to setup my linux box over again. IDEA 3 has a lot of things I need and I can't wait for JDK 1.4.1 for the mac anymore. I'm not even sure that the back port will be as good as the 1.4.1 version... we'll see. In the mean time I'm going to keep testing the mac JDK and submitting all the bugs I can, but I need to develop (with pleasure of course) and RedHat lets me do this.
No joy, looks like the class name for the OSX Aqua LAF has now changed to apple.laf.AquaLookAndFeel, however, specifying this in config/options/other.xml results in an error:
com.intellij.openapi.components.a.c: com.intellij.openapi.util.InvalidDataException: unknown LookAndFeel : apple.laf.AquaLookAndFeel at com.intellij.openapi.components.a.a.a(a.java:64) at com.intellij.openapi.components.a.a.a(a.java:16) at com.intellij.openapi.components.a.a.getComponent(a.java:168) at com.intellij.openapi.components.a.a.j(a.java:105) at com.intellij.openapi.components.a.a.f(a.java:101) at com.intellij.openapi.application.b.e.g(e.java:231) at com.intellij.idea.r.g(r.java:81) at com.intellij.idea.r.a(r.java:75) at com.intellij.idea.l.run(l.java:2) at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178) at java.awt.EventQueue.dispatchEvent(EventQueue.java:448) at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136) at java.awt.EventDispatchThread.run(EventDispatchThread.java:99) Caused by: com.intellij.openapi.util.InvalidDataException: unknown LookAndFeel : apple.laf.AquaLookAndFeel at com.intellij.ide.k.c.readExternal(c.java:122) at com.intellij.openapi.components.a.a.a(a.java:25) ... 15 more
After some digging around, I found the source of the problem. The Apple 1.4.1 JDK does not return the Aqua LAF in UIManager.getInstalledLookAndFeels(), which is what IDEA relies on to determine what is available and whether a specified LAF exists (pretty reasonably). If you're truly desperate to get Aqua LAF (yes, it's possible!) then the following little app will help. Just add it to your classpath and switch the MAIN_CLASS_NAME var in idea.sh to use Launcher instead, and you'll be able to select the Aqua look. Admittedly, this is a fairly pointless exercise, so only try this if you're very bored and really have nothing better to do
public class Launcher { public static void main(String[] args) { javax.swing.UIManager.installLookAndFeel("MacOS Adaptive", javax.swing.UIManager.getS ystemLookAndFeelClassName()); com.intellij.idea.Main.main(args); } }
Cool. Sounds like IDEA can in fact make some quick changes and get this running. From the various errors and changes we've reported, there is no reason why IDEA shouldn't work, with a little 'bug fixing' on IDEA's end, and get the IDE to launch and work properly.
Well, IDEA works fine on Linux and Windows. I'm guessing it's Apple's problem... They'd better get it together, else I have to move to linux to keep up with the rest of the world.
Well, to an extent. The current JVM for OSX clearly has many issues that have nothing to do with IDEA. So for those, we would look to Apple to have them addressed. However, IDEA didn't used to run so well on linux, or on OSX for quite a while pre build-629. It was through reporting issues and having the intellij guys 'massage' IDEA to behave better under different OS's. I'm sure they're the best judges of what belongs firmly in the realm of the OS/environment, and what IDEA can do to behave better under said environment.
Us reporting issues with the current OSX jdk might be premature, however, for every 9 issues we report that are Apple's fault, there will be 1 issue that can be addressed by IDEA, which makes it worth reporting. Besides, we're all java developers here, so should be able to at least make an educated guess as to whether a bug is a JVM issue or an app issue.
Incidentally, this ClassCastException is the culprit for all the odd focus issues. IDEA tries to registers its own EventQueue (which is perfectly legal), but DP2 currently only allows apple.awt.CEventQueue queues to be registered...hence the CCE. The solution (for the adventurous and knowledgable...I won't reveal how since it probably invalidates any number of licenses) is to make IDEA's EventQueue impl extend Apple's, then it will get registered without any problems and suddenly a lot of things will start working (for one thing, you'll be able to actually code in the editor)
Marvellous! :-D
Does it mean we may use IDEA 3 build 665? I think not. Hope great JetBrain people can support MacOS X as soon as possible!!!
Hrmph, spoke too soon. It doesn't work well at all (menubars flash on and off too briefly to click on anything, comboboxes don't drop down). Guess that backport to 1.3.1 will be needed after alll...sigh
We can't call these IJ issues, but we can hope that if they are not significant to find and resovle, maybe they can do it.
Let's hope :)
Thanks,
John
Ditto on all this. Tried it with Jaguar 10.2.2 build 6F15 and still the same as Hani. Funny thing is that I can't even find how to turn off HWAccell in 1.4.1... doesn't look like it's possible.
FYI It is actually possible to get it working rather well! Change IDEA_POPUP_WEIGHT in idea.sh to medium, and things will work surprisingly well. I was able to create a project and navigate around it somewhat. Although ctrl-n doesn't seem to work, and there is some slight font clipping (but nothing too drastic).
Yup. Pretty cool.
Seems the issue is here:
NOT IMPLEMENTED FOR CLASS: class sun.awt.font.NativeFontWrapper - usePlatformFontMetrics we do not need to implement - returning null)
Not sure who's saying we do not need to implement returning null... but that bites :)
R
Hum no mac look and feel, but the funny thing is that when a window wants to first redraw half the mac look and feel shows up, and then it's over drawn by their interface.
Seems slow to come up with some windows at first, but then picks up speed once it configures the window the first time. Not sure if they're caching it or something.
I can't seem to submit key commands to anything. Copy paste stuff like that just throws errors. I guess I'm gonna have to start filing bugs and see what comes out of their tests.
I was just told that the Apple dev group is using IDEA for testing and they're aware of a lot of the issues, so I'm not sure who to throw this at.
ideas? (haha)
It's pretty severe focus issues which I suspect IntelliJ can't do much about. Looks like editor body panel never actually gets focus. If you scroll around you'll notice that the scrollbar gets the actual events and scrolls down the editor, but the cursor itself doesn't move. It would explain the key commands not working too I think.
Yeah, I'm also noticing that nothing about this build supports anything JDK 1.4.1 on the mac, which is no surprise.
Also it seems that IntelliJ is using their own redraw mechanisms for SWING, which is going to make it very difficult for them to properly support 1.4.1 on OS X. I'm hoping that once they get their hands on the 1.4.1 JDK they can write some code to hand the draws to the JDK and not do it on their own, otherwise everything apple went through to improve the JDK and support tight integration with the OS was a complete waste of space and time.
After quitting the app now I'm getting this nice stack every time I restart and I can't start the app up at all now:
NOT IMPLEMENTED FOR CLASS: class sun.awt.font.NativeFontWrapper - usePlatformFontMetrics
WARNING: handleEvent is using old paintArea.paint(fTarget, true)!!!
apple.awt.EventQueueExceptionHandler Caught Throwable :
java.lang.ClassCastException
at apple.awt.CEventQueue.push(CEventQueue.java:190)
at com.intellij.ide.p.initComponent(p.java:104)
at com.intellij.openapi.components.a.a.a(a.java:88)
at com.intellij.openapi.components.a.a.getComponent(a.java:10)
at com.intellij.openapi.components.a.a.j(a.java:102)
at com.intellij.openapi.components.a.a.f(a.java:23)
at com.intellij.openapi.application.a.e.g(e.java:248)
at com.intellij.idea.r.g(r.java:17)
at com.intellij.idea.r.a(r.java:13)
at com.intellij.idea.l.run(l.java:2)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:448)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)
Why even try to get IDEA to work with DP2? It's a half-formed thing with warnings plastered all over it. Even aside from the partially implemented Cocoa GUI wrappers, it's bloated with debugging statements. It's slower than 1.3.1 with benchmarks like scimark2.
Not that I don't think it's worth keeping an eye on what Apple and Sun are doing to make sure the eventual shipping version works perfectly with IDEA. I just don't want attention deflected from the backport... I've been waiting for a long time to get a post-629 build, and I don't fancy waiting until a beta version of 1.4.1 ships in 1Q2003 to get it.
yup. I just smoked the mac version and started to setup my linux box over again. IDEA 3 has a lot of things I need and I can't wait for JDK 1.4.1 for the mac anymore. I'm not even sure that the back port will be as good as the 1.4.1 version... we'll see. In the mean time I'm going to keep testing the mac JDK and submitting all the bugs I can, but I need to develop (with pleasure of course) and RedHat lets me do this.
R
I think it's too early to tell if the issue are apples vm or idea....
Has anyone figured out how to get idea to use the native look and feel, such as it does in build 629?
In build 629 it was called something like "adaptive" and works quite well.
I assume that one would just need to modify the swing.properties in the {jdk-home}/jre/lib dir for jdk1.4.1, but to what values?
BTW Idea (on windows) works great with alternative look and feels - my personal favoriate is Alloy.
.peter
No joy, looks like the class name for the OSX Aqua LAF has now changed to apple.laf.AquaLookAndFeel, however, specifying this in config/options/other.xml results in an error:
com.intellij.openapi.components.a.c: com.intellij.openapi.util.InvalidDataException: unknown LookAndFeel : apple.laf.AquaLookAndFeel
at com.intellij.openapi.components.a.a.a(a.java:64)
at com.intellij.openapi.components.a.a.a(a.java:16)
at com.intellij.openapi.components.a.a.getComponent(a.java:168)
at com.intellij.openapi.components.a.a.j(a.java:105)
at com.intellij.openapi.components.a.a.f(a.java:101)
at com.intellij.openapi.application.b.e.g(e.java:231)
at com.intellij.idea.r.g(r.java:81)
at com.intellij.idea.r.a(r.java:75)
at com.intellij.idea.l.run(l.java:2)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:178)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:448)
at java.awt.EventDispatchThread.pumpOneEventForHierarchy(EventDispatchThread.java:197)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:150)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:144)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:136)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:99)
Caused by: com.intellij.openapi.util.InvalidDataException: unknown LookAndFeel : apple.laf.AquaLookAndFeel
at com.intellij.ide.k.c.readExternal(c.java:122)
at com.intellij.openapi.components.a.a.a(a.java:25)
... 15 more
After some digging around, I found the source of the problem. The Apple 1.4.1 JDK does not return the Aqua LAF in UIManager.getInstalledLookAndFeels(), which is what IDEA relies on to determine what is available and whether a specified LAF exists (pretty reasonably). If you're truly desperate to get Aqua LAF (yes, it's possible!) then the following little app will help. Just add it to your classpath and switch the MAIN_CLASS_NAME var in idea.sh to use Launcher instead, and you'll be able to select the Aqua look. Admittedly, this is a fairly pointless exercise, so only try this if you're very bored and really have nothing better to do
public class Launcher
{
public static void main(String[] args)
{
javax.swing.UIManager.installLookAndFeel("MacOS Adaptive", javax.swing.UIManager.getS
ystemLookAndFeelClassName());
com.intellij.idea.Main.main(args);
}
}
Cool. Sounds like IDEA can in fact make some quick changes and get this running. From the various errors and changes we've reported, there is no reason why IDEA shouldn't work, with a little 'bug fixing' on IDEA's end, and get the IDE to launch and work properly.
Well, IDEA works fine on Linux and Windows. I'm guessing it's Apple's problem... They'd better get it together, else I have to move to linux to keep up with the rest of the world.
Well, to an extent. The current JVM for OSX clearly has many issues that have nothing to do with IDEA. So for those, we would look to Apple to have them addressed. However, IDEA didn't used to run so well on linux, or on OSX for quite a while pre build-629. It was through reporting issues and having the intellij guys 'massage' IDEA to behave better under different OS's. I'm sure they're the best judges of what belongs firmly in the realm of the OS/environment, and what IDEA can do to behave better under said environment.
Us reporting issues with the current OSX jdk might be premature, however, for every 9 issues we report that are Apple's fault, there will be 1 issue that can be addressed by IDEA, which makes it worth reporting. Besides, we're all java developers here, so should be able to at least make an educated guess as to whether a bug is a JVM issue or an app issue.
Incidentally, this ClassCastException is the culprit for all the odd focus issues. IDEA tries to registers its own EventQueue (which is perfectly legal), but DP2 currently only allows apple.awt.CEventQueue queues to be registered...hence the CCE. The solution (for the adventurous and knowledgable...I won't reveal how since it probably invalidates any number of licenses) is to make IDEA's EventQueue impl extend Apple's, then it will get registered without any problems and suddenly a lot of things will start working (for one thing, you'll be able to actually code in the editor)
Build666, with default IDEA_POPUP_WEIGHT, non of the dropdowns, drop down.
However if you set IDEA_POPUP_WEIGHT to medium, they do. Why is that?