OSX progress.... Follow
First of all, thanks for prividing an OSX bundle for build 689! Secondly...it doesn't work ;)
The reason is that from DP8 onwards, apps have to explicitly specify that they require 1.4.1. This is done by specifying a JVMVersion key in the Info.plist file. Attached is my own Info.plist which does work.
Also, choosing options -> file templates throws up an internal error (i'll file an SCR shortly). But it's getting there!
Also, is there any chance of you providing a 128x128 version of the IDEA icon? Would be nice to create a really good looking .icns OSX icon for it ;)
Please sign in to leave a comment.
On the plus side:
Heavy Menus work
Meta Keys work
Aliasing is cleaner
Unless it's a problem with the Monaco font in particular, the source code coloring is screwed up. Scrolling the editor window re-colors (seemingly) random lines with (seemingly) random colors.
Also, the Info.plist file that was installed using the 689 installer isn't even close to correct. It appears to be the Info.plist from the installer application that got put in $IDEA_HOME/bin/idea.app/ Really strange.
Here is a info.plist with Heavy menus AND without hani's .cvspass directory file ;)
oops here's the file, and just increased the memory usage too, runs better
Where is it?
Thanks, but it doesn't work. After copying the file into $IDEA_HOME/bin/idea.app/ OSX doesn't recognize idea.app as an application.
It doesn't appear that I should need to hand-edit Info.plist for my installation.
Attached is the Info.plist file that the 689.sit Installer puts int $IDEA_HOME/bin/idea.app/
Ok i must be missing something. I am pretty new to Mac but old to unix. None of these plist files work for me. I overwrote the old Info.plist and I get an unexpected error 1000 when launching. Can anyone give some pretty good instructions on how to get this to work
Ok, attached is the Info.plist I use. BEFORE YOU USE IT, you'll need to do an "ln -s IntelliJ-IDEA-3.0.1 idea" from your /Applications dir. THis will create the soflink necessary for the attached plist to work. I like links :)
This works for me and should work for others, too.
it works thanks
It seems that you made a mistake in your Info.plist. Instead of idea.popup.weight, you defined a key idea.poup.weight.
Anyway, it's great to see workarounds for this. I am new to Java development on OS X and when I tried to add only the JVMVersion key to IDEA's Info.plist, it didn't work.
Also, I filed a bug for this before looking at the forum.
Yep, you are correct. Thanks for catching that.
BTW, idea being Aqua-ified looks great!
Your attachment did not come through on the newsgroup. Could you mail
it to me directly?
Brian Calhoun wrote:
Would someone please explain what's up with the error 1000 stuff? I tried to modify Robert's Info.plist to fit my setup (by removing the $JAVAROOT reference) but to no avail. I tried first to create a IDEA_HOME environment variable (just because I preferred IDEA_HOME than JAVAROOT _) but it doesn't seem that idea.app cares about it. I then tried to replace all the JAVAROOT/IDEA_HOME references by the path where IDEA is installed but it didn't work either. Could someone point me to the appropriate documentation on how to deal with that or explain why what I did doesn't work?
OK, I think I found why it didn't work (since I managed to get it to work). Apparently, the value for CFBundleExecutable was not correct for some reason. I reverted it to "idea" (the name of the idea.app bundle) and it worked! :)
Well, I managed to get idea.app to work but IDEA is still unusable. I mean, it launches OK but if I try to do anything with it (like trying to write some code), it stops responding (beach ball). What is weird, is that looking at what's hogging the CPU, I found that both idea and loginwindow share half of the CPU! And it seems that loginwindow starts acting crazy at the same time as IDEA stops responding!
Has anyone else experienced the same thing?
... and loginwindow stops hogging the CPU as soon as I force quit IDEA!
... went back to 688, which started to get irresponsive as well. This time, no problem with loginwindow going crazy but it seems that there is an infinite loop in Apple's JVM since the Terminal process in which I launched IDEA started to hog the CPU and continuously output the following:
FocusManager nextResponder called
until I forced quit IDEA.
Looks like heavy menus aren't quite there yet. Check out this funny looking popup with the normal popup there, and an upside down ghost of the edit menu. If filed this with apple as bug 3133488.
Nice, it seems that the contextual menus behave correctly now too. So if the menu is going to hit the dock, it displays the other way. Works really nicely.
The readme file from 1.4.1dp8 talks about the possibility of windows drawing upside down. Not that it helps, but this could possibly be related.
Same thing here. IDEA (the JVM?) deadlocks if you look at it the wrong way. sigh
What ever you do, don't go to full screen mode with JDK 1.4.1 DP8!
In general, just don't use idea with dp8. It's not ready for prime time. I'm sticking with my crashing and deadlocking version of build 628 for now.
Seems that the deadlock happens when I use the arrow keys... I filed a bug on IDEA's tracker... I am considering filing one with Apple as well.
BTW, I tried with both medium and heavy popups to see if it made a difference but no luck there... I reverted to 2.6 for now since I really need to have something working correctly.
Eric, I'm not entirely sure why you say that. I've been in IDEA with DP8 for the past 4 hours, and except for this massive ugliness of full screen, I have no problems.
Rules are simple:
1- Use medium menus
2- Don't use full screen.
3- If you're going to turn on aliasing, use Courier for the font.
If you have locking issues, try switching to the Metal laf. Might be a problem with the Aqua laf.
So do you actually succeed in using IDEA 689? Have you tried writing some code (or using the arrow keys in an editor window which creates the problem for me)?
I am curious to know if it is my setup that's messed up or if it's DP8...
Absolutely! I've been writing code. Works fine. JUST tried the arrow keys and they respond real nicely, so does the mouse wheel and everything else I use. it works just fine for me. I actually like it better in the Aqua laf too, although some of the highlight stuff is a bit funky with that.
Maybe I should mention that I AM using OS 10.2.3 6G30. Maybe some things are fixed in there which help???
I just tried to switch back to default LAF and my problem is gone. I mean, console.app is complaining about lots of things but no deadlocks when I use the arrow keys.
This is weird though that Aqua LAF is working for you without problem and not for some of us... :(