home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 10 Tools
/
10-Tools.zip
/
owf.zip
/
wf.HLP
(
.txt
)
< prev
next >
Wrap
OS/2 Help File
|
1997-05-04
|
43KB
|
1,310 lines
ΓòÉΓòÉΓòÉ 1. About Object WorkFrame ΓòÉΓòÉΓòÉ
Object WorkFrame
Version 2.0
Object WorkFrame is a workframe for C++/Java-programmers, HTML-developers and
others who use projects based on files. It contains a MakeMake utility which
creates makefiles automaticaly and a class browser for C++ and Java code.
To get full access to the fuctionality of Object WorkFrame an editor is needed
which support DDE (like EPM 6.x or Mr. Ed 1.16 or higher).
You can customize Object WorkFrame in a simple way using a PM-utility. Error
messages from
EMX/GCC-compiler
VisualAge C++ / CSet ++ compiler ICC
Resource compiler (RC)
Compiler for online documents (IPFC)
VisualAge make utility (NMake)
other make utilities like DMake, GNU Make
Java compiler
are supported (see monitor-window).
Object WorkFrame is developed with the Open Object Library (OOL), a C++
class-library which makes PM-programming a little bit easier. Object WorkFrame
needs Warp 3 or higher.
Object WorkFrame is SHAREWARE until you have registered:
You are not allowed to sell or commercially distribute the Object
WorkFrame or any part of it. If you want to distribute the Object
WorkFrame commercialy you have to apply the authors permission.
You have a time-limit of one month to test/use Object WorkFrame. After
one month testing you are not allowed to use Object WorkFrame.
Additionaly the class browser is restricted, only 10 classes are parsed,
more than 10 classes are not displayed.
Only registered users of Object WorkFrame will receive help from the
author.
In some dialogs of Object WorkFrame a few windows are disabled. These windows
are only enabled in Object WorkFrame Pro which contains a REXX-interface for
programming Object WorkFrame.
Please send your bug-reports via EMail to: sbrauk@gwdg.de
(c)opyright Stefan von Brauk, 1996,1997
ΓòÉΓòÉΓòÉ 2. Register Object WorkFrame ΓòÉΓòÉΓòÉ
If you are a registered user of Object WorkFrame: THANK YOU!
If you are not and wanяt to become a registered user do the following:
1. Send 50 US$, 80 DM or 80 SFR to the author (check or money, money
prefered):
Stefan von Brauk
Lotzestr. 53
37083 Goettingen
Germany
2. or transfer 50 US$, 80 DM or 80 SFR to my acount at
Postbank Hannover (Germany)
BLZ 250 100 30
Konto 568515307
3. Additionaly you send your EMail-adress and you will get the next 2
updates of Object WorkFrame via EMail (SnailMail no Update).
ΓòÉΓòÉΓòÉ 3. Program setup ΓòÉΓòÉΓòÉ
If you start Object WorkFrame the first time, you have to:
Specify your text editor
Edit the menu entrys
Edit the list file
Configurate class browser files
Setup your compiler settings
Changing fonts
You cannot start Object WorkFrame directly (e.g. with a double-click on the
icon of the program). Object WorkFrame only starts with a double click on a
Object WorkFrame datafile created with the Object WorkFrame template!
ΓòÉΓòÉΓòÉ 3.1. Specify Editor Settings ΓòÉΓòÉΓòÉ
To change the settings for your editor you open the editor settings dialog
(menuentry Options\Editor Settings). In the dialog you have to:
Enter the name of your editors exe-file, you should enter the full
qualified path.
Enter the arguments your editor need. You can also enter the joker "%s"
so all files selected in the file window will be passed to the editor.
Check if your editor is EPM 6.x or Mr. Ed 1.16 or higher or an other
editor. If you use EPM Mr. Ed 1.16 you should check the related buttons
so Object WorkFrame can communicate with the editor (e.g. show
errormessages from the compiler).
Additionaly it is possible to enter special DDE-commands, the default values
should work with EPM/Mr.Ed
ΓòÉΓòÉΓòÉ <hidden> Menus ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 3.2. Setup menus ΓòÉΓòÉΓòÉ
You can customize the menus and the toolbar of the Object WorkFrame with a tool
you access under <Options\Menu Setup>. On default Object WorkFrame has only a
few menu entrys, all other menu entrys you see are inserted with MenuSetup.
This entrys are saved in a configuration file of Object WorkFrame.
If you see a lot of menu entrys (I hope you do so) an example configuration
file of Object WorkFrame is loaded which shows you how to involve tools,
applications and online-documentation in the Object WorkFrame. In this case the
tools and documentation involved by Object WorkFrame are from IBMs Visual Age
C++, so if you use a different development environment read the following
carefuly to invoke your development tools in a correct manner. Because the
sample configuration uses paths it is nessecary you modify the menu entrys to
make Object Workframe work with your development tools.
An example to invoke EMX/GCC into Object WorkFrame is also avaible. To use this
example instead the VisualAge C++ example you have to:
1. Close all instances of Object WorkFrame
2. Rename the file <WF.CFG> to <WF.SAV>
3. Rename the file <EMX.CFG> to <WF.CFG>
4. Start Oject WorkFrame
There is also a sample file how to use Java-tools (the JDK must be installed),
if you want to work with this configuration:
1. Close all instances of Object WorkFrame
2. Rename the file <WF.CFG> to <WF.SAV>
3. Rename the file <JAVA.CFG> to <WF.CFG>
4. Start Oject WorkFrame
It is possible to use multiple configurations. Usualy the configuration is
loaded from WF.CFG in the install-directory. You can specify a configuration
for a single project by
Edit the menu
Closing the menu-editor you will be asked to save your changes "global"
or for the project only. In the second case a configuration-file will be
created for your project.
Copy a configuration
You can also copy a configuration from another project. E.g. if you have
a project with "sample1.mak" as the makefile and want to copy the
configration to a project with "sample2.mak", copy the file "sample1.cfg"
to the directory of the second project and rename there "sample1.cfg" to
"sample2.cfg".
The following entrys describe how to
Modify an entry
Add an entry
Delete an entry
Save the menus
ΓòÉΓòÉΓòÉ 3.2.1. Modify an entry ΓòÉΓòÉΓòÉ
The first thing you might want to do is to change an entry, perhaps the make
utility. The menu entry which is created for this case in the configuration
file is <Action/Make>.
To change the entry, open MenuSetup. You see two trees (the main menu and the
context-menu). Three trees show all menu items in the hirarchy of the original
menus. Now expand the tree for the main menu until you see <Make>. Open the
entry with a double click (you can only edit menuentrys which are displayed
with a green key). Youяll get a dialog which shows the current settings of the
menu entry. In this example the menu title <Make> is displayed, the program
which is called is NMake. Now you can change the given options to values you
need.
For details of the options please reffer to the online help of the dialog.
ΓòÉΓòÉΓòÉ 3.2.2. Add an entry ΓòÉΓòÉΓòÉ
In the second step you may want to add a menu entry. You have three methods to
add one:
Separators
You can add a separator line to the menu. Select an entry, open the popup
menu and select <New/Separator>. A separator will be inserted behind the
selected entry.
Siblings
You can add a sibling separator. Select an entry an select <New/Sibling
entry> from the popup menu. The dialog for item settings appears and you
can enter the settings you need. For details of the settings please
reffer to the online help of the dialog. If the new entry should be a
submenu (means it will get child entrys), its only nessecary to enter the
title of the new entry.
Childs
You can add child entrys. Select an entry and select <New/Child entry>
from the popup menu and perform like above. The selected menu entry will
get an arrow, the new entry will be displayed in the submenu.
ΓòÉΓòÉΓòÉ 3.2.3. Delete an entry ΓòÉΓòÉΓòÉ
To delete a menu entry, select the entry and chose <Delete> from the popup
menu. You can only delete menu items which are displayed with a green key.
ΓòÉΓòÉΓòÉ 3.2.4. Save the menus ΓòÉΓòÉΓòÉ
if you have edited the menus you will be asked if you want to save your
changes. You have the choice to save the settings as:
Project configuration
Save the settings local. All settings are only in use for your opened
project. The settings are saved in a file named like your makefile with
the suffix "*.CFG" in your project directory. If you rename your makefile
you must rename the "*.CFG"-file too to access your menu setup. Otherwise
Object WorkFrame will start up with your global settings.
Global configuration
Save the settings global. All settings are avaible in every project which
does not have a local configuration file.
Changes to the toolbar will be visible when you restart Object WorkFrame.
ΓòÉΓòÉΓòÉ 3.3. Edit the Listfile ΓòÉΓòÉΓòÉ
You can edit the list-file (file WF.LST in the installation directory of Object
WorkFrame) to chose which filemask should be displayed in the combobox of the
toolbar. An entry in WF.LST has the following format:
name\mask1;mask2;...
where name is the title to display in the combobox, mask1;mask2;... are the
filemasks for files to display in the file-window, for example:
HTML\*.htm;*.html
shows an entry "HTML" in the combobox, if selected, all files of your
project-directory(s) matching *.htm and *.html are displayed.
If you have edited the list file you must restart Object WorkFrame.
ΓòÉΓòÉΓòÉ 3.4. Configurate class browser files ΓòÉΓòÉΓòÉ
C++ only: The class browser of Object WorkFrame uses a helping file which
contains filenames of standard header files not to scan like files of the
C-library (stdio.h etc) and the include files for PM-programming (os2.h...),
this is usefull to improve performance.
If you want to specify files which should not be scaned too to make the browser
faster (or you donяt need that information) you can add the filenames to the
file "neglist.lst" which you can find in the install-directory of Object
WorkFrame. Add the filename(s) using CAPITALS, each file on a separate line.
If you use one or more class-librarys on default they will be scaned and
displayed too. Because a class library contains lot of header files which must
be added to the "neglist.lst" to supress scanning, a litle tool called
"neglist.exe" is shiped with Object WorkFrame. On the commandline change to the
include-path of the library and call "neglist.exe" which one argument like
"*.h" or "*.h*". "neglist.exe" will produce a file called "neglist.tmp" which
contains all files found. Just add the content of the file with a text editor
to "neglist.lst" so the library will not be scanned any longer. If the browser
still shows the content of the library you should delete the class browser file
(the name of the makefile with suffix "*.cw") and rebuild your application.
Warning: Some librarys resolve name of header files with defines like
#define Application_i "app.h"
In this case there exists a file which contains these definitions. That file
shouldnяt be added to "neglist.lst", otherwise Object WorkFrame may throw some
errors when scanning files which use these defines.
ΓòÉΓòÉΓòÉ 3.5. Setup your compiler settings ΓòÉΓòÉΓòÉ
Object WorkFrame and MakeMake are working compiler independent. From this
reason the programs are using INI-files for the compiler/linker settings, you
can find them in the installation directory of Object WorkFrame and edit them
with a text-editor.
These INI-files give you the chance to
1. decide yourself (eg. to optimize) which compiler and/or linker switch is
enabled by MakeMake when an option in the compiler/linker settings
notebook of MakeMake is enabled
2. You can invoke a compiler of your choice: copy the IBM_CPP.INI file and
replace the settings made there with the settings needed for your
compiler
On default the settings follow this format:
VARNAME=CFLAGS(/option) LINK(/option)
where the options in the brakets are used for the compiler / linker. You can
enter both statements, one or none of them. If you donяt enter a statement you
cannot select this option in the notebook for compiler/linker settings. If you
want to select the option but nothing should be added to the compiler/linker
settings, enter the following line
VARNAME=EMPTY
There are some lines in the INI-file which are a little bit more complicated:
NAME='IBM ICC'
this is the name which is displayed in the compilers combobox
COMPILER=icc.exe
the 'true' name (the compilers exe-file)
LINKER='icc.exe /B"%options"'
the linker. In this case icc does the job to invoke the linker.
'%options' will be replaced with the linkers settings selected in the
notebook
DEFAULT_CFLAGS = /C
flags for the compiler which should always be used
LIB=LIB
the name of the environment variable of your config.sys which shows the
path for librarys to use
INCLUDE=INCLUDE
the name of the environment variable of your config.sys which shows the
path for header-files to use
ΓòÉΓòÉΓòÉ 3.6. Changing fonts ΓòÉΓòÉΓòÉ
You can change the used fonts of the file-, monitor- or classbrowser windows by
drag/drop a font on it, the settings will be stored.
ΓòÉΓòÉΓòÉ <hidden> Project ΓòÉΓòÉΓòÉ
ΓòÉΓòÉΓòÉ 4. Create a new project ΓòÉΓòÉΓòÉ
To create a new project drop the Object WorkFrame template on a place of your
workplace and open it with a double-click. A dialog for a new project will
apear where you can select:
The AppAssistant lets you select one new project from a list of
predefined projects
With Import it is possible to import a project or to create an empty
project
ΓòÉΓòÉΓòÉ 5. AppAssistant ΓòÉΓòÉΓòÉ
The AppAssistant shows a list of predefined applications (project templates)
which can be used for building a new application/project. The list of
predefined projects is currently a litle bit small (if you donяt use the Open
Objects Library) but you can create your own project templates.
AppAssistant lets you
1. select the type of application
2. select if menus and/or online-help is needed
3. set the name and required paths
For more information see the online-help of AppAssistant.
ΓòÉΓòÉΓòÉ 6. Create project templates ΓòÉΓòÉΓòÉ
Currently the Object WorkFrame brings only a few project templates. From this
reason you may want to create new project-templates, please read the folowing
carefully:
Each project template resides in a single directory, this directorys must
reside in the subdirectory <\template> which is created during the
installation of Object WorkFrame.
Each project has a <KEYWORD> which is defined by the name of the
directory the template resides in, e.g. the project templates delivered
with this packages have the <KEYWORDS> pm1, pm2 etc. If the user ceates a
new prroject with this project the content of the directory will be
copied to the new directory, the <KEYWORDS> will be replaced the name of
the new project!
The <KEYWORDS> are also used for filenames and in the files themselfs,
e.g. to identify a process or window. Example:
1. In the subdirectory pm1 you find pm1.cpp, pm1.h etc
2. If copied to a new directory the files are renamed with the new
title eg. MyApp so you have now MyApp.cpp, MyApp.h etc
3. Fiinished that the files are scaned for the keyword pm1, this text
will be replaced with MyApp. If there is eg. pm1Win it is now
MyAppWin, pm1File changes to MyAppFile etc.
There are also some information files in the directorys
<KEYWORD>.bmp is the bitmap shown in the listbox of AppAssistant
<KEYWORD>.dsc contains following information which is used by
AppAssistant:
1. In the first line are keywords which shows which options for the
project are supported, keywords are
a. HELP online help supported
b. MENU menus supported
2. The text of the second line is shown in the listbox of AppAssistant
3. The text of the third line following is shown if the user press the
button <Info> in the AppAssistant-dialog
Depending of the users selection some code-blocks are removed
1. If the user didnt select HELP from AppAssisstant, code-blocks
beginning with the keyword /HELP are removed until keyword HELP/, if
the user selected HELP theis keywords are removed from the source.
2. If the user didnt select MENU from AppAssisstant, code-blocks
beginning with the keyword /MENU are removed until keyword MENU/, if
the user selected MENU theis keywords are removed from the source.
ΓòÉΓòÉΓòÉ 7. Import an existing project ΓòÉΓòÉΓòÉ
To import a project drop the Object WorkFrame template on a place of your
workplace and open it with a double-click. A dialog for a new project will
apear, select <Import>. In the next dialog select <Browse> to open the
file-select dialog. Select the directory and the makefile of the project which
should be imported. The name of the makefile and the path will be shown int the
dialog. Now you have to
Enter the name of the compilers output-file (e.g sample1.exe, test.dll),
optional if you dont work with a makefile.
Enter the arguments to start the output-file with (optional).
Specify directorys to display additionaly (optional). See using multiple
directories for details
Close the dialog by pushing <OK>, Object WorkFrame will scan the directory for
files and show them in the file window. Now you should create a basic
makefile:
1. Select "Debug" in the second combobox of the toolbar
2. Call "MakeMake"
3. Select there your compiler, your make utility, the files to use in the
makefile, actions to perform etc.
4. Push <Settings> to select there the compiler/linker settings to use for
DEBUG mode
5. Select <Create> to build a new makefile and save it.
6. Close "MakeMake" and select "Release" in the second combobox of the
toolbar
7. Call "MakeMake" again, the actions and files you have selected will be
displayed
8. Push <Settings> to select there the compiler/linker settings to use for
RELEASE mode
9. Save the makefile and close "MakeMake"
Now you can switch between DEBUG, BETA and RELEASE before calling your make
utility, it will automaticaly use the correct compiler/linker settings (see
DEBUG/BETA/RELEASE for details).
ΓòÉΓòÉΓòÉ 8. Using multiple projects/directorys ΓòÉΓòÉΓòÉ
If you are creating more complex applications Object WorkFrame can support you
in two ways
1. Show multiple directorys
On default only the content of the main directory (the directory where
the makefile resides) is shown. To show the contents of more directorys
open the project settings where you can enter other directorys to display
additionaly (slows down performance of Object WorkFrame).
If you drop files ont the file-window the dropped files will always be
moved/copied to the main directory!
2. Using mulitple makefiles
MakeMake allows you to invoke other makefiles to the project makefile.
These makefiles are executed before any other action of the project
makefile is executed. So it is possible to create at first one or more
simple project, where each of it creates a single part of your target
application, eg. a library/DLL. Finaly you create the main project and
include the makefiles of the projects created before.
You can also create the main project first and then include/create new
makefiles for parts of your project without creating single project (see
help from MakeMake for details).
ΓòÉΓòÉΓòÉ 9. Window Functions ΓòÉΓòÉΓòÉ
The main window contains a main menu, a toolbar, and a client area. The client
area is split in a file window and a monitor window.
ΓòÉΓòÉΓòÉ 9.1. Main Menu ΓòÉΓòÉΓòÉ
On default the main menu contains only a few menu items
"Project Settings" shows the dialog for the project-setup
"MakeMake" is the utility shipped with Object WorkFrame to create
make-files
"Editor Settings" shows the dialog for the editor-setup
"Menu Setup" shows the dialog to edit the menus
Som help-entries
All other menu entys are created with MenuSetup, see there to create you own
menu entrys.
ΓòÉΓòÉΓòÉ 9.2. Toolbar ΓòÉΓòÉΓòÉ
The toolbar of Object WorkFrame contains on default this controls:
1. A combobox with different entrys for often used filetypes, every entry
hides one or more filemasks (e.g. Bitmap = *.bmp, CSource = *.c, *.cpp).
You can select one of these entrys and every file in your
project-directory which matchs the filemask will be shown in the
file-window.
You can also enter one or more filemasks in the combobox directly:
*.c
*.c;*.cpp;*.h;*.hpp
The default file-masks displayed in the combo-box are defined in WF.LST,
to customize Object WorkFrame you can edit the list-file.
2. The second combo box allows you to switch from debug-mode, beta-mode,
release-mode and back. To do so the MakeMake utility shiped with Object
WorkFrame defines a macro in the makefile, the make-utility is called
with a statement which shows the make-utility, if it should chose the
settings for debug-, beta- or release mode building your application. See
DEBUG/RELEASE/BETA for details.
3. The stop-button is used for programs started with Object Workframe
monitored. To stop the monitored program you just need to press the
stop-button and the monitored programm will be terminated.
All other toolbar buttons are created with MenuSetup, see there to create you
own toolbar buttons.
ΓòÉΓòÉΓòÉ 9.3. File Window ΓòÉΓòÉΓòÉ
The file window displays the files found with the filemask selected in the
combo-box. The window supports drag/drop, direct editing for filenames
(ALT+mousebutton 1) and offers a context menu. You can open displayed files
with following methods:
With a double-click on a file the editor is started to load the file
except exe-files which are executed directly.
Select Open\default from the context-menu of the file window will start
the file on the way your operating-system prefers (e.g. if you have
associated *.htm-files with the WebExplorer and select a *.htm file the
WebExplorer will start to show the file).
See using multiple directories for details if you have specified multiple
directories to display.
ΓòÉΓòÉΓòÉ 9.3.1. Context Menu ΓòÉΓòÉΓòÉ
You acccess the context-menu of the file-window on default with your right
mouse-button. The context-menu has following entrys:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéOpen Γöéopens a selected Γöé
Γöé Γöéfile with the editorΓöé
Γöé Γöé(default) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéOpen\Editor Γöéopens a selected Γöé
Γöé Γöéfile with the editorΓöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéOpen\default Γöéopens a selected Γöé
Γöé Γöéfile with the Γöé
Γöé Γöéassociated program Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSettings Γöéopens the Γöé
Γöé Γöésettings-notebook ofΓöé
Γöé Γöéthe selected file Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéRefresh Γöérescans the projet Γöé
Γöé Γöédirectory for files Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSelect\All Γöéall displayed files Γöé
Γöé Γöéare selected Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéSelect\None Γöéall displayed files Γöé
Γöé Γöéare de-selected Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéView\Icon Γöéfiles are displayed Γöé
Γöé Γöéin icon-view Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéView\Name Γöéfiles are displayed Γöé
Γöé Γöéin name-view Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéView\Text Γöéfiles are displayed Γöé
Γöé Γöéin text-view Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéView\Detail Γöéfiles are displayed Γöé
Γöé Γöéin detail-view Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéView\Toolbar Γöéshow/hide the Γöé
Γöé Γöétoolbar Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéFind... Γöéenables the Finder Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
You can add menu-entrys to the context-menu with MenuSetup
ΓòÉΓòÉΓòÉ 9.4. Monitor Window ΓòÉΓòÉΓòÉ
The monitor-window displays the output from programs which are started
monitored (e.g. compilers). The window contents will be erased every time you
start such a program.
Object WorkFrame supports error-messages if you use EPM 6.x or Mr.Ed 1.16 (or
higher) from:
ICC (IBMяs C/C++ compiler)
EMX/GCC (GNU C/C++ compiler-port from E. Mattes)
RC, the resource-compiler
IPFC, the IPF-compiler
NMake/GNU Make/DMake if the message contains a line number
Javac, the Java compiler
That means if you double-click on an error-message which contains a
line-number, Object WorkFrame tells the editor to show the file and the line
where the error occured, additionaly the editor shows the compilerяs
error-message in the status-line.
ΓòÉΓòÉΓòÉ 9.5. Class browser window ΓòÉΓòÉΓòÉ
The class browser shows the recognized classes and their member-functions. The
bitmaps shown in the window have the following meaning:
Class
Abstract class (Java)
Abstract member function (Java)
Public member function
Protected member function
Private member function
Static member function
Included project
With a double-click on a class the definition of the class will be loaded in
the editor, a double-click on a member function will load the implementation
code.
The class browser
cannot show local/global variables
cannot show non-member functions
cannot show local classes
has problems with the STL (Standard Template Library) and other intesive
usage of C++-templates
has problems with #defines, because it is no compiler it does not resolve
your defines, eg. if the following code is given:
#ifdef _BLA_BLA_
void myFunc( void * param1)
#else
void myFunc( )
#endif
you see both functions in the class brower.
For other actions you can access a local popup menu
To invoke the class browsers utilitys which generats the needed information
see creating class browser information. See also configurate class browser
files.
ΓòÉΓòÉΓòÉ 9.5.1. Context menu ΓòÉΓòÉΓòÉ
The class browser window has its own context menu, you access it with a click
with the right mouse-button on an item. The context menu has following
contents:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
ΓöéShow ΓöéShow the Γöé
Γöédefinition Γöéimplementation of a Γöé
Γöé Γöémember function Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéShow ΓöéShow the declarationΓöé
Γöédeclaration Γöéof the class/member Γöé
Γöé Γöéfunction (obsolete Γöé
Γöé Γöéfo Java) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéList ΓöéShow the list of allΓöé
Γöé Γöéscanned classes Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
ΓöéTree ΓöéShow the derivation Γöé
Γöé Γöéof all scanned filesΓöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ <hidden> using DEBUG/RELEASE/BETA ΓòÉΓòÉΓòÉ
The toolbar shows a combobox where you can select if you are working in debug-,
beta- or release-mode. This means that Object WorkFrame can start applications
like the compiler with options depending on your selection, e.g. if you have
selected DEBUG the compiler is started with the flags nessecary to debug your
application.
From this reason there must be three statements in the makefile with
compiler/linker flags, one for debug code, one for release mode and one for
beta-code. To create the needed statements it is recommended if you use the
MakeMake utility. In this utility you can select the compiler/linker flags for
debug- and release-mode seperatly. It is recomended if you work in this manner:
1. Create a project by droping the template on the workplace shell
2. Enter the project settings in the project dialog
3. Select DEBUG in the combobox
4. Start MakeMake, select your compiler and make-utility
5. Open the compiler settings and select the switches for DEBUG-code
6. Let Makemake create a makefile
7. Now select RELEASE in the combobox
8. Start MakeMake again
9. Open the compiler settings and select the switches for RELEASE-code
10. Let MakeMake overwrite the makefile
11. Select BETA and redo the actions from nr. 8
Now the makefile contains all needed statements for debug, beta and
release-code and you can select before starting the make-utility or the
comiler, if debug, beta or release-code should be created.
For BETA-code there is a special flag in the compilers INI-file (/DBETA). This
flag is passed to the compiler when BETA is selected and has the same function
like '#define BETA' in your sourcecode, so it is simple to write BETA-specific
code
#ifdef BETA
logFile.Write("some beta-information");
#endif
You donяt need to define BETA yourself, BETA is automaticaly defined if you
select BETA from the combobox.
The macros used are in the file <WF.DF>, you may edit them or implement new
macros in this file. Every macro must be on a single line, the line starts
with a name which is shown in the combobox, it is followed by a semicolon and
the macro(s) which are passed to the make-utility, e.g.
Debug;"debug=TRUE"
If you create new macros you need to modify your makefiles, beware of editing
the modified makefiles with MakeMake, your changes will be overridden in this
case.
ΓòÉΓòÉΓòÉ 10. The MakeMake Utility ΓòÉΓòÉΓòÉ
To develop programs you often need to use make-files. Writing makefiles is a
little bit boring so a utility should do it for you. To call the
MakeMake-utility open a project with Object WorkFrame and select
Project\MakeMake. Now select
the target make-utility (GNU Make and IBM NMake supported, most other
make utilitys should work like one of these)
the used compiler
settings for the compiler/linker
actions to control by the make-utility
additional librarys to use
additional projects/makfiles to include
(see online-help from MakeMake for details)
When youяve finished, MakeMake will create a makefile. Before you save the
makefile you can edit it directly.
Warning: MakeMake overwrites the makefile!
Because MakeMake works compiler independent it may be nessacary to edit/create
the INI-file for your compiler, see compiler settings for details.
MakeMake works dependent on your DEBUG/RELEASE/BETA-selection, refer to
DEBUG/RELEASE/BETA for details.
ΓòÉΓòÉΓòÉ 11. Class browser utilitys ΓòÉΓòÉΓòÉ
The class browser needs informations about the used classes, theirefore two
utilitys are needed. This utilities are invoked automaticaliy in your makefile
if you are using the MakeMake utility, just select "Create browser information"
from the actions window.
If you donяt use MakeMake you have to invoke the utilities yourself. The
creation of browser information is done in two steps. The first step is to add
all files which are compiled to a temporary file which is done by
"addfile.exe". The second step is to create the browser information
("browse.exe"), it uses the information of the temporary file. The filenames of
the browser information and the temporary file are identified by the name of
the makefile, eg. if your makefile is "make.mak", the temporary file is
"make.ctw", the browser information is in the file "make.cw".
To use the utilities in your makefile follow these steps:
1. Your makefile contains code which creates object-files from C++ files
like
".cpp.obj:
compiler.exe $(CFLAGS) %s"
Enter the following line after that statement:
"@<WorkFramePath>\addfile %s <MakeFile>"
where:
<WorkFramePath> is the full qualified path where you have installed
Object WorkFrame
<MakeFile> is the name of the current makefile
2. The second step is to invoke the browser when the application is created.
Your makefile contains code like:
"makemake.exe: $(OBJS)
ilink /Fe"app.exe" $(OBJS) $(LIBS)"
Add the following line:
"@<WorkFramePath>\browse.exe <MakeFile>"
where:
<WorkFramePath> is the full qualified path where you have installed
Object WorkFrame
<MakeFile> is the name of the current makefile
You can also create browser information for one or multiple source files.
Therfore call the browser utility with the name of the makefile and the files
to scan:
<WorkFramePath>\browse.exe <MakeFile> file1 file2 ...
where:
<WorkFramePath> is the full qualified path where you have installed
Object WorkFrame
<MakeFile> is the name of the current makefile
file1... are the files to scan (no jokers allowed)
"addfile.exe" suports one option:
-nologo donяt display the logo
Additonaly "browse.exe" supports following options:
-nologo donяt display the logo
-struct use structs and unions like classes (C++ only)
-java run in Java-mode
Eg. the invokation of "browse.exe" in your makfile looks like:
c:\wf\browse.exe MyMake.mak -nologo -struct
See also configurate class browser files.
ΓòÉΓòÉΓòÉ 12. History ΓòÉΓòÉΓòÉ
Version 2.0
WorkFrame
- New class browser
- New Finder utility
- The toolbar use smaller bitmaps
- File-handling uses now case-sensitive filenames
- Problems with different drives fixed
- The file window supports direct editing
- Bug fixed at minimizing the window
- Bugs fixed in drag/drop
- PM-tool to setup the menus
- Support for Debug/Release/Beta settings
- Changed to OOL Beta 1
MakeMake
- Notebook support for compiler/linker settings
- uses INI-files for comilers, compiler independent
- MakeMake reads the settings youяve made the last time and initialize
the windows with these settings
- scans resource files for dependencies (bitmaps, icons, dialog- and
include files)
- Bugs fixed in building the makefile
- Support for Debug/Release/Beta settings
- Changed to OOL Beta 1
ΓòÉΓòÉΓòÉ <hidden> Monitored Programms ΓòÉΓòÉΓòÉ
You can start programs from Object WorkFrame monitored which is useful for
command-line applications (e.g. compiler, linker...). The programs output is
shown in the monitor-window where you can inspect it.
In the case of the supported compiler (ICC, EMX/GCC, IPF, RC) you can switch
with a double-click on an error-message in the monitor window to the file and
line given there (if you use EPM or Mr. Ed 1.16 or higher).
ΓòÉΓòÉΓòÉ <hidden> Editor ΓòÉΓòÉΓòÉ
Insert here the name of your editors exe-file. You should enter the full
qualified path.
ΓòÉΓòÉΓòÉ <hidden> EPM ΓòÉΓòÉΓòÉ
Check if your editor is EPM or not. If you use EPM you should check this button
so Object WorkFrame can communicate with EPM (e.g. show errormessages from the
compiler).
ΓòÉΓòÉΓòÉ <hidden> Mr. Ed ΓòÉΓòÉΓòÉ
Check if your editor is Mr. Ed or not. If you use Mr. Ed you should check this
button so Object WorkFrame can communicate with Mr. Ed (e.g. show errormessages
from the compiler).
ΓòÉΓòÉΓòÉ <hidden> other ΓòÉΓòÉΓòÉ
Check this button if your editor is neither EPM nor Mr. Ed. DDE-communication
will be disabled.
ΓòÉΓòÉΓòÉ <hidden> Application name ΓòÉΓòÉΓòÉ
You can edit the DDE-application name which your comiler uses. The default
settings should work with EPM/Mr. Ed without any changes.
ΓòÉΓòÉΓòÉ <hidden> Topic name ΓòÉΓòÉΓòÉ
You can edit the DDE-topic name which your comiler uses. The default settings
should work with EPM/Mr. Ed without any changes.
ΓòÉΓòÉΓòÉ <hidden> Command ΓòÉΓòÉΓòÉ
You can edit the DDE-command which your comiler uses. The default settings
should work with EPM/Mr. Ed without any changes.
ΓòÉΓòÉΓòÉ <hidden> Editor arguments ΓòÉΓòÉΓòÉ
Enter here the arguments which should be passed to you editor. You can also use
the joker "%s". In this case the editor is started with all selected files from
the file window.
ΓòÉΓòÉΓòÉ <hidden> Editor Settings ΓòÉΓòÉΓòÉ
Specify here your text-editor. Make following entrys:
Editor
Editor arguments
EPM
Mr. Ed
other
Appname
Topic name
Command
ΓòÉΓòÉΓòÉ <hidden> Location ΓòÉΓòÉΓòÉ
Insert here the location of your project as a full qualified path.
ΓòÉΓòÉΓòÉ <hidden> Output File ΓòÉΓòÉΓòÉ
Enter the name of the compilers output-file (e.g sample1.exe, test.dll),
optional.
ΓòÉΓòÉΓòÉ <hidden> Run Options ΓòÉΓòÉΓòÉ
Enter the arguments to start the output-file with (optional).
ΓòÉΓòÉΓòÉ <hidden> Makefile ΓòÉΓòÉΓòÉ
Insert here the name of your makefile of this project if you use one
(optional). If you donяt use a makefile but want to use the class-browser you
must enter a "virtual" makefile-name like "dummy.mak". This file donяt need to
exist.
You can also press the browse-button to select a makefile from the file-dialog.
ΓòÉΓòÉΓòÉ <hidden> Multiple directorys ΓòÉΓòÉΓòÉ
On default the file window of Object WorkFrame shows only the files found in
the path you entered as the projects path in the projects-setting dialog. If
you build a more complex project it may be possible you want to invoke other
directories, eg. directories which contains source for DLLs. In this case you
can specify in the project-settings dialog one or more directories to display
additionaly in the file-window.
Therefore you open the project settings and enter the path(s) for the
directories in the multiline-control, each directory on a new line.
Warning: If you have specified drectories in the projects settings, drag/drop
actions will always be performed on the project directory, eg. if you drop a
file on the file window the file will be copied/moved to the project directory.
ΓòÉΓòÉΓòÉ <hidden> Dircetorys ΓòÉΓòÉΓòÉ
You can insert multiple directorys which contents are displayed in the
file-window. Every line of the mle can only contain one directory. See using
mulitple directorys for details.
ΓòÉΓòÉΓòÉ <hidden> Finder ΓòÉΓòÉΓòÉ
To find strings in one or more files do the following:
1. Enter a string which to find in the files
2. Select if the finder should search
a. in the directory
b. or in the selected files
c. or in files which have a file extension specified in the entry field
3. Select if the search should performed case-sensitive or not
The finder does not search in files with the following extension (even if you
have selected them):
*.BMP
*.CLASS
*.DLL
*.EXE
*.HLP
*.ICO
*.INF
*.LIB
*.RES
*.O
*.OBJ
*.TMP
ΓòÉΓòÉΓòÉ <hidden> Results of searching ΓòÉΓòÉΓòÉ
In this list you see the results of the search, on the left the filenames and
on the right the linennumber where the string was found. In the titlebar you
see the count of matches.
To view a found topic just double-click on the line which is of your interest
(EPM 6.x or Mr. Ed 1.16 or higher required).
ΓòÉΓòÉΓòÉ <hidden> Menu Setup ΓòÉΓòÉΓòÉ
You can customize Object WorkFrame by using this window. You can add
menu-entrys to the popup-menu and the main-menu of the frame window, associate
this menu-entrys with applications, set separators or delete menuentrys youяve
added.
The control shows the menu-entrys of the main- and popup-menu: red bitmaps show
you that the menu-entrys are program defined so you cannot edit or remove them.
Green bitmaps show that you can edit the entrys (with the right mouse button
you access the local popup-menu):
To edit an entry double-click on the entry of your interest or click for
the local popup-menu on that entry
To delete, add sibling or child-entrys or add separators click for the
local popup-menu on that entry
ΓòÉΓòÉΓòÉ <hidden> Joker ΓòÉΓòÉΓòÉ
Joker are signs which are filled by Object WorkFrame if they are used in the
menu settings. E.g. if you use the Joker %s in the arguments of a program,
Object WorkFrame replaces this joker with the filenames youяve selected in the
file-window.
ΓòÉΓòÉΓòÉ <hidden> Menu Title ΓòÉΓòÉΓòÉ
Enter at <Menu title> the title of the menu entry.
ΓòÉΓòÉΓòÉ <hidden> Program ΓòÉΓòÉΓòÉ
Enter at <Program> the application which should start when this menu entry is
selected. It can be nessacary to enter a full qualified path.
ΓòÉΓòÉΓòÉ <hidden> Arguments ΓòÉΓòÉΓòÉ
Enter the arguments which should be passed to the started application.
You can also enter Jokers. Valid jokers are:
ΓöîΓöÇΓöÇΓöÇΓöÇΓöÇΓö¼ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÉ
Γöé%c ΓöéThe compiler-settings (CFLAGS) from the makefile. The Γöé
Γöé Γöésettings are inserted depending of the debug/release Γöé
Γöé Γöéselection. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé%cc ΓöéThe compiler which is identified in your makefile by Γöé
Γöé Γöéthe macro CC= (e.g. CC=gcc.exe) Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé%d ΓöéIf you are in debug mode a macro ("debug=TRUE") is Γöé
Γöé Γöépassed to the program, in release mode nothing is Γöé
Γöé Γöépassed. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé%e ΓöéThe output-file you specified in the project-settings. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé%m ΓöéThe makefile you specified in the project-settings. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé%p ΓöéThe path of the project. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé%r ΓöéThe run-options you specified in the project-settings. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé%s ΓöéAll selected files from the file-window. If no file is Γöé
Γöé Γöéselected the program is not started. Γöé
Γö£ΓöÇΓöÇΓöÇΓöÇΓöÇΓö╝ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöñ
Γöé%S ΓöéAll selected files from the file-window. If no file is Γöé
Γöé Γöéselected the program is started anyway. Γöé
ΓööΓöÇΓöÇΓöÇΓöÇΓöÇΓö┤ΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÇΓöÿ
ΓòÉΓòÉΓòÉ <hidden> Hotkey ΓòÉΓòÉΓòÉ
Select a Hotkey for the menu entry. All hotkeys for user defines menu-entrys
must be used with <Ctrl+Shift+HOTKEY>
ΓòÉΓòÉΓòÉ <hidden> Toolbar Button ΓòÉΓòÉΓòÉ
You can select the button <Toolbar Button> to create a toolbar-button.
Changes to the toolbar will be visible if you restart Object WorkFrame.
ΓòÉΓòÉΓòÉ <hidden> Bitmap ΓòÉΓòÉΓòÉ
On default the toolbar button displays only text. You can enter at <Bitmap> a
full qualified path to a bitmap-file which should be displayed int the toolbar
button instaed of text.
Changes to the toolbar will be visible if you restart Object WorkFrame.
ΓòÉΓòÉΓòÉ <hidden> New Group ΓòÉΓòÉΓòÉ
Check the button <New Group> if the toolbar button should start a new group of
buttons.
Changes to the toolbar will be visible if you restart Object WorkFrame.
ΓòÉΓòÉΓòÉ <hidden> Change Path ΓòÉΓòÉΓòÉ
If the program need to be started from a special directory check the button
<Change Path> and enter the path in the field below.
ΓòÉΓòÉΓòÉ <hidden> Path ΓòÉΓòÉΓòÉ
Enter at <Path> the path Object WorkFrame should switch to before the
application is started.
ΓòÉΓòÉΓòÉ <hidden> Run monitored ΓòÉΓòÉΓòÉ
Check this button if the programs output should be displayed in the Object
WorkFrame monitor window. Very useful for all command-line applications.
ΓòÉΓòÉΓòÉ <hidden> Refresh File-window ΓòÉΓòÉΓòÉ
Check this button if the content of the project directory will changed by the
program which is started (e.g. compiler). In this case the file window from
Object WorkFrame will be updated if the started program has finished.
ΓòÉΓòÉΓòÉ <hidden> Remove .class-extension ΓòÉΓòÉΓòÉ
Some Java-utilities donяt like to work if an overgiven filename contains
".class". Check this button so the file-extension ".class" will not be
overgiven.
ΓòÉΓòÉΓòÉ <hidden> Remove .class-extension ΓòÉΓòÉΓòÉ
Some Java-utilities donяt like to work if an overgiven filename contains the
complete path. Check this button so the path will not be overgiven.
ΓòÉΓòÉΓòÉ <hidden> Item Settings ΓòÉΓòÉΓòÉ
Here you can associate your menu-entry to applications. Therefore you can:
Enter the title of the menu-item
Select a program to start
Enter arguments to pass to the program
Select a hotkey
Select if a toolbar button should be created
Enter a bitmap the toolbar button should display
Select if the toolbar-button should lead a new Group
Select if path must be set
Enter a path if it must be changed
Select if the program runs monitored
Select if window content must be refreshed
Select if file extensions must be removed
Select if paths must be removed
ΓòÉΓòÉΓòÉ <hidden> Save Menu Settings ΓòÉΓòÉΓòÉ
Select how to save the menu settings:
Project configuration
Save the settings local. All settings are only in use for your opened
project. The settings are saved in a file named like your makefile with
the suffix "*.CFG". If you rename your makefile you must rename the
"*.CFG"-file too.
Global configuration
Save the settings global. All settings are avaible in every project which
does not have a local settings-file.
Changes to the toolbar will be visible when you restart Object WorkFrame.
ΓòÉΓòÉΓòÉ <hidden> Project Settings ΓòÉΓòÉΓòÉ
Speciy here your project. Make the following entrys:
Project Location
Makefile
Output File
Run Options
Directorys
ΓòÉΓòÉΓòÉ <hidden> AppAssistant ΓòÉΓòÉΓòÉ
AppAssitant helps you to create a simple new application. Therfore it shows in
the list on the left side application-templates from which an application can
be created. With the button <Info> you access more information about every
application. if you have selected an application to create
1. Select it from the list
2. Enter the name of the new application
3. Enter the directory where it should be created or use the browse-button
4. If an application-template supports online-help and/or menus checkbuttons
for this support are enabled. Select that button if you want this
support.
When finished the application will be created and MakeMake starts where you
have select your compiler etc.
Currently only a few templates are delivered with Object WorkFrame, if you
donяt want to use this templates cancel the dialog and create a application on
the usual way.
You can also create your own templates.