Frequently Asked Questions

The idea of a “project” in jIDEE is a directory that holds all the code, images, and any other bits needed to build a program. In other words, a project should ideally contain only one program. Therefore, it makes no sense to use the system root or your user root as a “project directory.”

In addition, parsing the contents of the system root or your account root normally takes an inconveniently long time. Given this and the fact that it makes no logical sense to let either of these locations be “project folders,” jIDEE doesn't let you.

jIDEE has been tested using only Oracle's “official” JRE. However, jIDEE will use whatever the default JRE is on your system. So, if on your system the java command invokes a JRE other than Oracle's, and if that JRE is fully compliant, then it should work. If the java command invokes a non-compliant JRE, then you can expect problems.

jIDEE has been tested using only Oracle's “official” JDK. So, in theory, under Windows if you point jIDEE at a JDK other than Oracle's, and if that JDK is fully compliant, then it should work. Otherwise you can expect problems.

In the Linux version, jIDEE will use whatever the default JDK is on your system. So, if on your system the javac command invokes a JDK other than Oracle's, and if that JDK is fully compliant, then it should work.

OS X essentially gives you no choice in the JDK and JRE.

It depends on whether you are running the Windows, Linux or OS X version.

Versions of jIDEE from version 2.0.0 onwards are not tested or supported on Windows XP. However, testing suggests that it works just fine. In any case, use at your own risk. Alternately, you can use on older version of jIDEE.

When you start jIDEE for the first time, if it cannot find one of the default programmer's editors (Notepad++ or Programmer's Notepad), it will fall back to using Notepad. If you install one of these editors after you start jIDEE or if you want to change the editor that jIDEE uses (including editors other than Notepad++ or Programmer's Notepad), you can set the desired editor in jIDEE's Preferences dialog.

Probably. The only requirement is that {your favorite text editor} be able to open a file from the command line with the syntax:

{path-to-your-editor}\{your-editor.exe} {filename}

for example,

C:\Program Files\My Favorite Editor\great_edit.exe MyJavaClass.java

Set the editor you want to use in the Preferences dialog.

A standard JDK installation on Windows does not place the JDK on the PATH—in other words, the javac (Java compile) command cannot be invoked as a one-term command; it must be invoked as something like C:\Program Files\Java\jdk1.6.0_21\bin\javac.exe. From jIDEE's point of view there are three choices:

  1. Force the user to put the JDK on the PATH.
    This is significantly more complicated than telling jIDEE where the JDK is—and if done incorrectly can hose your system.
  2. Let jIDEE try to figure out where the JDK is.
    This might work until it stops working.
  3. Let the user tell jIDEE where the JDK is.
    This seems to be the least evil option.

Yes. Open jIDEE's Preferences dialog and point the JDK to the new version.

When jIDEE starts up the first time, it will use whatever text editor it can find as the default text editor. If you don't like what it picked, first install the editor you want to use, then specify the command to open the editor in jIDEE's Preferences dialog. The text editor you use must be able to open files with the syntax

{editor-command} {filename}

Sort of. The code has a lot of the stubs and whatnot needed to make the OS X port go. It's just a matter of making it happen. Do you want to help?

When jIDEE starts up the first time, it will use whatever text editor it can find as the default text editor. If you don't like what it picked, first install the editor you want to use, then specify the command to open the editor in jIDEE's Preferences dialog. The text editor you use must be able to open files with the syntax

{editor-command} {filename}

Apple doesn't (conveniently, anyway) let users use a JRE or JDK other than the ones they themselves provide. In the past, Apple has been a bit slow in releasing up-to-date versions of the JRE and JDK. If you are having problems:

  1. Make sure you have updated to the latest Apple release of Java software.
  2. If you still have issues, complain to Apple.
 
faq/start.txt · Last modified: 2010/09/17 12:41 by mithat
 
Except where otherwise noted, content on this wiki is licensed under the following license:GNU Free Documentation License 1.2
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki