####################################################################
## BlueJ properties default values
#####################################################################
##
## All settings in this file may be changed to configure BlueJ.
## Settings in this file are system wide and apply to all users.
##
## BlueJ property settings may also be specified on a per-user basis
## in the user property file. The user property file is in
##
## <USER_HOME>/.bluej/bluej.properties (Unix)
## C:\Users\<USER_NAME>\bluej\bluej.properties (Windows)
##
## (The location of the properties file is the same as the location
## of the debug log file, and this location is displayed in the
## "About BlueJ" dialog).
##
## Each of the properties in this file may be copied to the user
## properties file. Settings in the user file override the system
## wide settings here.
##
#####################################################################
#####################################################################
## The interface language. A directory must exist for the language in
## <BLUEJ_HOME>/lib. Language directories can be created by copying
## an existing language directory and translating the contents of the
## text files in that directory. If you make a language version for
## a new language, please send it to bluej@bluej.org
#####################################################################
bluej.language=english
# A list of available languages, in the form:
# internal-name:human-readable-name
# The internal-name controls the name of the directory that BlueJ
# will look for translations in.
bluej.language1=english:English
bluej.language2=afrikaans:Afrikaans
bluej.language3=catalan:Catalan
bluej.language4=chinese:Chinese
bluej.language5=czech:Czech
bluej.language6=danish:Danish
bluej.language7=dutch:Dutch
bluej.language8=french:French
bluej.language9=german:German
bluej.language10=greek:Greek
bluej.language11=italian:Italian
bluej.language12=japanese:Japanese
bluej.language13=korean:Korean
bluej.language14=portuguese:Portuguese
bluej.language15=russian:Russian
bluej.language16=slovak:Slovak
bluej.language17=spanish:Spanish
bluej.language18=swedish:Swedish
#####################################################################
## The JVM language and region.
## This is different to the value above which sets the language for
## BlueJ's labels.
## In most cases the values below can be left commented out.
## Its intended usage is for the scenario where you want the Java VM that
## BlueJ runs on to use a different language than its default Locale.
## For instance, you are using a machine that has its region set to
## China and you want to run BlueJ in English. Default UI elements
## in Java such as File Choosers and dialogs
## will show the local language for the Region as set in the OS. This
## allows you to override that value. To get the desired language of
## interface for your OS's Regional Settings it may be necessary to
## set both vm.language and vm.region. These map to Java's environment
## variables user.language and user.country.
##
## The two letter language code that is required is the ISO-639 code, see:
## http://www.unicode.org/unicode/onlinedat/languages.html
## The two letter country code that is required is the ISO-3166 code, see:
## http://www.unicode.org/unicode/onlinedat/countries.html
##
## By default these are commented out, you can specify either or both
## to get the desired combination for your system.
## Note: these settings are used for the VM that runs BlueJ and also
## for the Debug VM that is used to run code, create objects etc.
#####################################################################
#vm.language=en
#vm.language=zh
#vm.language=fr
#vm.language=cz
#vm.language=dk
#vm.country=US
#vm.country=CN
#vm.country=FR
#vm.country=CZ
#vm.country=DK
#####################################################################
## URLs for the BlueJ manuals and documentation. If you have the
## documents installed locally and want to use your local version,
## edit these URLs.
#####################################################################
bluej.url.bluej=http://www.bluej.org
bluej.url.tutorial=http://www.bluej.org/doc/documentation.html
bluej.url.reference=http://www.bluej.org/reference/manual.pdf
# The URL for the Java API documentation can be specified here, however
# this will only apply the first time you use BlueJ. After that, the
# setting is saved in the user preferences file (and the setting here
# is ignored). You can adjust the user preferences via the preferences
# dialog (found under the "tools" menu) in BlueJ.
bluej.url.javaStdLib=http://download.oracle.com/javase/6/docs/api/
# Location of the Java standard library sources. This does not need to
# be specified if the "src.jar" file is in the standard location (in
# the Java home directory) - only when it is elsewhere. This is used
# to show comments for standard methods in code completion.
#bluej.jdk.source=/System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home/src.jar
# do not change the following:
bluej.url.versionCheck=http://www.bluej.org/version.info
#####################################################################
## Additional help menu items. Users can add their own menu items to
## the help menu here. Each menu item, when selected, will open a URL
## in a web browser. The items are listed in the help.menu.items
## property in the form
## bluej.help.items=<tag1> <tag2> ...
## Tags can be any identifier. For every tag, there should be two
## additional properties:
## bluej.help.<tag>.label=<menu label>
## bluej.help.<tag>.url=<URL to open>
## The label will appear in the menu, the URL will be opened in the
## browser. See (commented out) example below.
#####################################################################
#bluej.help.items=myCustomLib courseInfo
#bluej.help.myCustomLib.label=My CS1 libraries
#bluej.help.myCustomLib.url=http://www.google.com/
#bluej.help.courseInfo.label=CS1 course info
#bluej.help.courseInfo.url=http://www.bluej.org/help/archive.html
#####################################################################
## The number of past projects that will be shown on the
## File/Open Recent... menu.
#####################################################################
bluej.numberOfRecentProjects=12
#####################################################################
## User's home directory. This is also defined by Java, and if that's
## fine for you, don't specify this property. This property, if
## specified, will override Java's user.home property.
##
## You can specify multiple values by appending consecutive numbers
## (starting at 2) to the property name, eg:
##
## bluej.userHome=/home/mik/tmp
## bluej.userHome2=/some/other/directory
## bluej.userHome3=/yet/another/directory
##
## In this case the first location that is writable will be selected.
#####################################################################
#bluej.userHome=/home/mik/tmp
#####################################################################
## Where the "userlib" directory is. This directory contains java
## libraries, in the form of jar and zip files, which will be
## available to all projects opened in BlueJ.
##
## If you leave this commented out the userlib directory is:
## <BLUEJ_HOME>/lib/userlib
##
## Generally this can be left alone, though it may be useful in a
## lab environment to move userlib to a location the instructor has
## write permissions for.
##
## Note: As with all entries in this file, backslashes in the path
## should be doubled, and colons should also be preceded by a single
## backslash, as in the example setting.
#####################################################################
#bluej.userlibLocation=C\:\\some\\directory\\somewhere
#####################################################################
## Where the extensions folder is. This is the folder which is
## searched for extensions (in jar files) when BlueJ starts.
##
## The default is:
## <BLUEJ_HOME>/lib/extensions
#####################################################################
#bluej.extensions.systempath=C\:\\some\\other\\directory
#####################################################################
## Allow BlueJ to automatically open any projects that were open when
## it was last closed down.
#####################################################################
bluej.autoOpenLastProject=true
#####################################################################
## Web browser. The following are the commands used for opening a
## web browser. (Only relevant for systems other than Windows and
## MacOS. On Win and MacOS, the mechanism is built-in.)
##
## When running on Java 6, BlueJ will first attempt to use Java 6's
## desktop integration features to launch the browser. The commands
## specified here will only be used if that fails.
#####################################################################
# First, try to open the URL in a running firefox process. If that
# fails, start firefox. The first dollar sign ($) will be
# replaced by the URL to be opened.
browserCmd1=firefox -remote openURL($)
browserCmd2=firefox $
#######################################################################
## Documentation generation. This specifies the command used for
## generating documentation and the directory name within the project
## directory where the documentation is stored.
## Most of the options are sensible as they are.
##
## If the doctool.command line is commented out (default), the javadoc
## command is located in the JDK directory that was used to launch BlueJ
##
## If you want private methods included in the documentation,
## change "-package" in the options to "-private".
## If "linkToStandardLib" is true, we will try to use the URL specified
## above as "bluej.url.javaStdLib" to create links. If that URL is
## not accessible, documentation generation will fail. Therefore, if
## you want to work offline, set "linkToStandardLib" to false (you
## can also do that from within BlueJ in the Preferences dialog).
#######################################################################
#doctool.command=javadoc
doctool.options=-author -version -nodeprecated -package
doctool.outputdir=doc
doctool.linkToStandardLib=true
#######################################################################
## Applets. Preferences for how applets are generated and executed.
##
## If the appletViewer.command line is commented out (default), the viewer
## command is located in the JDK directory that was used to launch BlueJ
#######################################################################
#appletViewer.command=appletviewer
#######################################################################
## For Mac OS only: indicate whether to place the menu bar at top of
## screen (screenmenubar=true), or top of each window
## (screenmenubar=false).
#######################################################################
bluej.macos.screenmenubar=true
#####################################################################
## The VM that the windows client should use
##
## This setting can be used in lab environment where there is a
## shared instance of BlueJ on a network drive, along with
## a shared instance of a JDK somewhere.
##
## This setting should not be uncommented except in that situation.
##
## NOTE: this setting is _only_ used under windows, and only when
## BlueJ is launched with the standard windows launcher (not if
## launched using a windows batch file)
##
## The commented out examples below are just to show the
## syntax used
#####################################################################
#bluej.windows.vm=X\:\\Programming Apps\\J2SDK_1.4.1_02
#######################################################################
## Class templates for new class generation. When creating a new class
## a list of templates is presented to choose from. This property
## defines this list. To add additional templates, you should
## - choose a name <template-name> for the template
## - create a file named <template-name>.tmpl in
## <bluej>/lib/<language>/templates/newclass/ that contains the text
## - add <template-name> to the classTemplates list below (optional)
## - add a property named "pkgmgr.newClass.<template-name>" in the
## language label files for all languages you intend to use
## (<bluej>/lib/<language>/labels), defining the label to appear in
## the dialogue. (optional)
## If the template is for an applet, interface or abstract class, the
## name you choose should start with "applet", "interface" or
## "abstract", respectively. Everything else will be treated as a
## standard class.
## More information is in
## <bluej-home>/lib/<language>/templates/newclass/README
## The bluej.templatePath property can be used to choose a different
## directory to store the templates (the default is
## <bluej_home>/lib/<language>/templates/newclass).
## Note: if the path contains backslashes, they must be written as
## double-backslashes (see example).
#######################################################################
bluej.classTemplates = midlet stdclass abstract interface appletj unittest enum
#bluej.templatePath = /home/mik/bluej/lib/english/templates/newclass
#bluej.templatePath = F:\\shared\\bluej\\templates
#######################################################################
## BlueJ Look and Feel.
## By default no option is specified, this means that BlueJ decides.
## At present this means:
## Windows: System look and feel
## Linux: CrossPlatform look and feel (Metal)
## Solaris: CrossPlatform look and feel (Metal)
## Where a crossplatform look and feel has been specified, font
## customisation can be done through the use of the BlueJ theme option
#######################################################################
#bluej.lookAndFeel=system
#bluej.lookAndFeel=crossplatform
#######################################################################
## Fonts. You can choose a font size for most of the interface
## components, and a font face and size for the editor. The editor font
## size can be redefined by a user in their preference dialogue.
#######################################################################
#######################################################################
# Theme fonts for User Interface components
# These specify font and font sizes for most of the interface components
# if using a crossplatform setting for bluej.lookandfeel. When using a
# system look-and-feel, UI fonts are derived from the OS settings.
#
# The font setting is specified as the name of a font face with an optional
# "-bold" at the end.
#
# The theme fonts are only used if bluej.useTheme flag is true and the
# bluej.lookandfeel property has been uncommented and set to crossplatform.
# Use theme, which means interface and menu fonts can be specified.
bluej.useTheme=false
bluej.fontsize=12
bluej.font=SansSerif
#bluej.font=Monospaced
#bluej.font=SIMSUN
# fonts for menus
bluej.menu.font=SansSerif-bold
bluej.menu.fontsize=12
# END OF THEME FONTS
#######################################################################
# fonts for Targets (classes in display)
bluej.target.font=SansSerif-bold
bluej.target.fontsize=12
# default fontsize for the editor (can be changed in Preferences dialog)
bluej.editor.fontsize=12
# font and fontsize for the terminal (the size defaults to the editor font size
# if not specified here)
bluej.terminal.font=Monospaced
#bluej.terminal.font=Monospaced-bold
#bluej.terminal.fontsize=12
# fontsize for the codepad (defaults to editor font size if not specified here)
#bluej.codepad.fontsize=12
# The editor font. This is the name of a font face with an optional
# "-bold" at the end. Most used are monospaced fonts, such as Courier.
# Good large fonts for screen projections are SansSerif-bold, 14pt, or
# Courier-bold, 18pt. Only the font face is specified here, the font
# size is specified in the BlueJ preference dialogue. Some examples:
bluej.editor.font=Monospaced
bluej.editor.MacOS.font=Monaco
# bluej.editor.font=Monospaced-bold
# bluej.editor.font=SansSerif
# bluej.editor.font=SansSerif-bold
# bluej.editor.font=Arial-bold
# The font used in the code completion display (method list)
bluej.codecompletion.font=Courier
#######################################################################
## Printing settings.
#######################################################################
# fonts for printing source text
bluej.fontsize.printText=10
bluej.fontsize.printTitle=14
# scale factor for printing the class diagram. The value is in percent.
# (a value of 100 will print at approx same size as the diagram on
# screen, a value of 50 will reduce the printed version to 50%, etc.)
bluej.print.scale=60
#######################################################################
## Terminal settings. Height and width are in number of characters.
#######################################################################
bluej.terminal.height=22
bluej.terminal.width=80
bluej.terminal.clearscreen=false
bluej.terminal.recordcalls=false
bluej.terminal.buffering=false
# If not specified, the VM default encoding will be used.
bluej.terminal.encoding=UTF-8
#######################################################################
## Some settings for editor preferences.
## These are the initial defaults - the settings can be changed by
## users in their preferences dialogue. (values: true / false)
#######################################################################
bluej.editor.autoIndent=true
bluej.editor.syntaxHilighting=true
bluej.editor.displayLineNumbers=false
bluej.editor.makeBackup=false
bluej.editor.matchBrackets=true
bluej.editor.tabsize=4
## Code Completion. When true it is enabled; when false it is disabled
## There is no option to change this from the preferences dialogue
bluej.editor.codecompletion=true
#######################################################################
## Settings for test, teamwork, and Java ME tools preferences.
## These are the initial defaults - the settings can be changed by
## users in their preferences dialogue. (values: true / false)
#######################################################################
bluej.testing.showtools=false
bluej.teamwork.showtools=false
bluej.javame.showtools=false
#######################################################################
### Colours. All are specified as RGB values.
#######################################################################
#colour for selections (in text and otherwise)
colour.selection=233,225,0
colour.selection2=255,250,0
#colour for highlights (in text editor)
colour.highlight=180,220,255
colour.highlight2=110,190,255
#####################################################################
## Compiler options.
##
## Here, you can add compile options for the Java compiler.
## If this attribute is not specified, the compiler is run with
## default options.
##
## The following options will ALWAYS be added internally in BlueJ. If
## you change these, funny things might happen (such as BlueJ not
## working at all!):
##
## -deprecation (Show description of each use of a deprecated method)
## -g (Generate all debugging information)
## -d (set the output directory)
##
## The following is also added internally, but is safe to change:
## -source (set by BlueJ to the version of the JDK)
##
#####################################################################
#bluej.compiler.options=-source 1.4 -target 1.4
# Whether to show the "unchecked" warnings generated when using generic
# classes in a non-typesafe manner (java 1.5+ only)
bluej.compiler.unchecked=true
#####################################################################
## Compiler options to compile classes in Java ME projects.
##
## Here you can add compile options for the Java compiler (by
## default javac; see bluej.compiler setting above) to compile
## classes in Java Micro Edition projects.
##
## Do not change the options below, -target and -source, unless you
## really know what you are doing. You can add options by attaching
## them to the end of the string below. For example, to add the
## -verbose option, change the string to be:
## bluej.javame.compiler.options=-source 1.4 -target 1.4 -verbose
##
## The -bootclasspath option will ALWAYS be added internally in BlueJ
## when compiling Java ME projects. This option specifies the
## MIDP and CLDC jar files needed to compile Java ME projects.
##
#####################################################################
bluej.javame.compiler.options=-source 1.4 -target 1.4
#####################################################################
## The Wireless Toolkit directory.
#####################################################################
bluej.javame.toolkit.dir=C:\\WTK2.5.1
#####################################################################
## Java Micro Edition libraries, core and optional, in
## blank-separated lists. For example:
## bluej.javame.optlibraries=jsr238.jar jsr239.jar mmapi.jar
#####################################################################
bluej.javame.corelibraries=midpapi20.jar cldcapi11.jar
#bluej.javame.optlibraries=
#####################################################################
## Options for the preverify command used in the deployment of MIDlets,
## as well as for the command that launches the emulator.
#####################################################################
#bluej.javame.preverify.options=-verbose
#bluej.javame.emulator.options=-Xverbose:all
#####################################################################
## Options for starting the internal virtual machine.
## bluej.vm.args provides arguments to the debug VM that
## is launched to run Java code, the code pad and the object bench.
## This setting is likely to not be needed in most instances.
## It is provided for situations where bluej and/or Java defaults
## need to be modified.
##
## Settings here have the ability to stop BlueJ running correctly
## if not configured properly.
##
## Each separate argument should be separated by white space.
## Double-quotes (") can surround text which not should be split
## into separate arguments. The backslash (\) always escapes the
## next character (however: backslashes are also escaped according
## to Java's property file handling).
##
## Examples: one two three => 3 arguments: 'one', 'two', 'three'
## one "two three" => 2 arguments: 'one', 'two three'
## abcde\\\\fg => 1 argument: 'abcde\fg'
#####################################################################
bluej.vm.args=-ea -Djavafx.macosx.embedded=true
# -ea : enable assertions
#####################################################################
## bluej.windows.vm.args provides arguments to the Java VM that
## launches the bluej GUI on Windows only. These arguments do not apply to
## the debug VM that is launched to run Java code, the code pad and
## the object bench. At present there is no equivalent for Linux,
## Unix or Mac. On Unix & Linux the launch script can be edited
## manually to add these arguments, on Mac they can be added by
## editing the Info.plist file found inside the BlueJ.app package
## contents. This setting is likely to not be needed in most
## instances. It is provided for situations where bluej and/or
## Java defaults need to be modified.
#####################################################################
#bluej.windows.vm.args=
#####################################################################
## Transport used to communicate with the debug VM. Available
## transports are "dt_socket" (TCP/IP transport) and "dt_shmem"
## (shared memory transport, which is available on Windows only).
##
## Normally, this setting should be left alone.
##
## The default is to try shared memory first, if it is available,
## and then to fall back to TCP/IP. TCP/IP may not work if an overly
## restrictive firewall is installed. The transport actually used
## will be noted in the debuglog file.
#####################################################################
bluej.vm.transport=dt_shmem
#######################################################################
## Debugging. When true, debug output goes to console; when false, it
## is written to a log file in the user's bluej settings directory.
#######################################################################
bluej.debug=false
#######################################################################
## Images.
#######################################################################
# README in main frame:
image.readme=readme.png
image.readme-selected=readme-selected.png
# arrow buttons
image.build.depends=arrow_black_uml.gif
image.build.extends=darrow_black_uml.gif
# editor breakpoint and step mark
image.editor.breakmark=break.gif
image.editor.stepmark=stepmark.gif
image.editor.breakstepmark=stepbreak.gif
# object bench
image.bench.object=object.png
image.bench.object-selected=object-selected.png
#text eval area
image.eval.prompt=prompt.gif
image.eval.continue=prompt-continue.gif
image.eval.object=small-object.gif
image.eval.dragobject-plus=drag-object-plus.gif
image.eval.dragobject-noplus=drag-object-noplus.gif
#editor-divider panel
image.editordivider.open=bluej_arrow_naviview_open.gif
image.editordivider.close=bluej_arrow_naviview_close.gif
# extensions manager help page
image.extmgr.info=extmgr-info.gif
#inspector object reference arrow
image.inspector.objectref=objectref.gif
#######################################################################
## Blackbox
#######################################################################
blackbox.uuid=optout
