home *** CD-ROM | disk | FTP | other *** search
- ####################################################################
- ## 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:\Winnt\profiles\<USER_NAME>\bluej\bluej.properties (WinNT)
- ## C:\<JDK_HOME>\bluej\bluej.properties (Win9x)
- ##
- ## 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
- #bluej.language=afrikaans
- #bluej.language=chinese
- #bluej.language=czech
- #bluej.language=french
- #bluej.language=german
- #bluej.language=italian
- #bluej.language=japanese
- #bluej.language=korean
- #bluej.language=portuguese
- #bluej.language=spanish
- #bluej.language=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/tutorial/tutorial.pdf
- bluej.url.reference=http://www.bluej.org/reference/manual.pdf
- bluej.url.javaStdLib=http://java.sun.com/j2se/1.5/docs/api/index.html
-
- # 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.
- #####################################################################
-
- #bluej.userHome=/home/mik/tmp
-
- #####################################################################
- ## 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.)
- #####################################################################
-
- # First, try to open the URL in a running netscape process. If that
- # fails, start netscape. The first dollar sign ($) will be
- # replaced by the URL to be opened.
- browserCmd1=netscape -remote openURL($)
- browserCmd2=netscape $
-
- #######################################################################
- ## 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
-
-
- #####################################################################
- ## System libraries which are added to BlueJ's class path
- ##
- ## The commented out examples below are just to show the
- ## syntax used
- #####################################################################
-
- #bluej.systemlibrary1.description=A Sample Library for Windows
- #bluej.systemlibrary1.location=S\:\\Programming\\Java\\lib\\sample.jar
-
- #bluej.systemlibrary2.description=A Sample Library for UNIX
- #bluej.systemlibrary2.location=/usr/local/java/lib/sample.jar
-
-
- #####################################################################
- ## 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 = 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 lookandfeel UI fonts are derived from the OS settings.
- # This is 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.
- # Note: the use of theme flag and specification and non-standard fonts
- # may affect bluej startup time (not confirmed for all systems)
-
- # 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
-
- # fontsize for the editor
- bluej.editor.fontsize=12
-
- # fontsize for the terminal
- bluej.terminal.font=monospaced
- #bluej.terminal.font=monospaced-bold
- bluej.terminal.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
-
-
- #######################################################################
- ## Printing settings.
- #######################################################################
-
- # fonts for printing source text
- bluej.fontsize.printText=10
- bluej.fontsize.printTitle=14
- bluej.fontsize.printInfo=9
-
- # 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
-
-
- #######################################################################
- ## 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
-
-
- #######################################################################
- ## Settings for test 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
-
-
- #######################################################################
- ### Colours. All are specified as RGB values.
- #######################################################################
-
- colour.background=208,212,208
- colour.graph.background=255,255,255
- colour.text.bg=255,255,255
- colour.text.fg=0,0,0
-
- colour.arrow.uses=0,0,0
- colour.arrow.implements=0,0,0
- colour.arrow.extends=0,0,0
-
- colour.target.border=0,0,0
- colour.target.bg.compiling=200,150,100
- colour.target.stripes=152,152,152
-
- # colours for different types of classes (by default we make most
- # of them the same - except for unit tests).
- colour.class.bg.default=245,204,155
- colour.class.bg.abstract=245,204,155
- colour.class.bg.interface=245,204,155
- colour.class.bg.applet=245,204,155
- colour.class.bg.unittest=197,211,165
- colour.class.bg.enum=245,204,155
-
- colour.package.bg.default=180,130,44
-
-
- # object bench
- colour.objectbench.background=250,250,250
- colour.wrapper.bg=205,38,38
- colour.wrapper.shadow=152,152,152
-
- #text colour for environment specific commands in popup menus
- colour.menu.environOp=152,32,32
-
- #colour for selections (in text and otherwise)
- colour.selection=249,225,87
-
- #####################################################################
- ## Compiling. Commands used to execute a compiler. The first property
- ## sets the type of the compiler. Currently it can be one of
- ## internal, javac or jikes. The second property if it exists,
- ## specifies the name of the executable to run as the compiler. This
- ## can be a fully qualified path or the name of an executable in the
- ## path. If it is not specified then BlueJ defaults to the standard
- ## name of the specified compiler type (ie javac for type javac and
- ## jikes for type jikes).
- #####################################################################
-
- bluej.compiler.type=internal
-
- #bluej.compiler.type=jikes
- #bluej.compiler.executable=jikes
-
- #bluej.compiler.type=javac
- #bluej.compiler.executable=javac
-
- #####################################################################
- ## Compiler options.
- ##
- ## Here, you can add compile options for the Java compiler (by
- ## default javac; see bluej.compiler setting above). If this attribue
- ## 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)
- ## -source (set to the version of the running JDK (1.4 or 1.5))
- ## -d (set the output directory)
- ##
- #####################################################################
-
- #bluej.compiler.options=-source 1.4
-
- #####################################################################
- ## Options for starting the internal virtual machine.
- ## By default, we switch Hotspot optimisation off. There are some
- ## bugs in Hotspot that cause debugging errors when optimising.
- ## If you really want, you can switch it on here - this will make
- ## your programs run faster, but cause bugs in BlueJ's debugger!!
- ## This can also be switched in the preferences dialog.
- #####################################################################
-
- bluej.vm.optimize=true
-
-
- #######################################################################
- ## 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.
- #######################################################################
-
- image.icon=bluej-icon.gif
- image.icon.terminal=bluej-icon-terminal.gif
- image.icon.editor=bluej-icon-edit.gif
- image.logo=bluej-logo.gif
- image.empty=empty.gif
-
- # arrow buttons
- image.build.depends=arrow_black_uml.gif
- image.build.extends=darrow_black_uml.gif
-
- # the machine indicator
- image.working=working.gif
- image.working.idle=working-idle.gif
- image.working.disab=working-disab.gif
- image.working.stopped=working-stopped.gif
-
- # editor breakpoint and step mark
- image.editor.breakmark=break.gif
- image.editor.stepmark=stepmark.gif
- image.editor.breakstepmark=stepbreak.gif
-
- # file chooser
- image.filechooser.packageIcon=packageIcon.gif
- image.filechooser.classIcon=classIcon.gif
-
- # class
- image.class.broken=broken-arrow.gif
-
- # editor help icon
- image.editor.help=help.gif
-
- # debugger
- image.debug.continue=continue.gif
- image.debug.step=step.gif
- image.debug.step_into=step_into.gif
- image.debug.stop=stop.gif
- image.debug.terminate=terminate.gif
-
- #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
-
- # unit testing
- image.test.recording=record.gif
-
- # test manager
- image.testmgr.ok=ok.gif
- image.testmgr.error=error.gif
- image.testmgr.failure=failure.gif
-
- # extensions manager help page
- image.extmgr.info=extmgr-info.gif
-
- #inspector object reference arrow
- image.inspector.objectref=objectref.gif
-
- # borders
- image.border.topleft=corner_top_left.gif
- image.border.topright=corner_top_right.gif
- image.border.bottomleft=corner_bottom_left.gif
- image.border.bottomright=corner_bottom_right.gif