A native launcher would in theory make it possible to open a .java file in an existing instance of IDEA rather than starting a new one. For a java-only (non-native) way of doing this, see the Jext editor. They use a socket for interprocess communication.
Michael Damberger wrote: >>For a start, IDEA can follow jBuilder approach. >> >>That is, open the file with default project settings that >>not that useful but allow you to view the file using the Java specific >>features of IDEA (e.g. class structure). >> > > I agree, and I would also find it very useful, if IDEA just would > "add the file temporarily" to the current project if IDEA is already > open when you doubleclick some .java file on windows explorer. > > I vote for the native launcher - there's code for it at the > eclipse project, for example. > I think having a batch file and console window looks very > unprofessional. (although the console is useful for seeing > stack traces - but this is only for evaluating EAP builds) > > > best regards, > Michael Damberger > ________________________________________________________________ > Keine verlorenen Lotto-Quittungen, keine vergessenen Gewinne mehr! > Beim WEB.DE Lottoservice: http://tippen2.web.de/?x=13 > > > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features > > -- Erb ============================================================== "The only time I like in the morning is afternoon." - Russell D. Cooper "If you do everything, then you're all done." - Melissa F. Cooper "Most of you are familiar with the virtues of a programmer. There are three, of course: laziness, impatience, and hubris." - Larry Wall ============================================================== _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
