| Content of these pages are owned and copyrighted by the poster. | |
| Hosted by: |
|
I Configure
A Allow for jar plug-ins (infobus?)
1 Editors
2 Viewers
3 Debuger
B Project Configurations
1 Compile Options
* JVM, System Classes, Platform Target
2 Runtime Options
* JVM, System Classes, Platform Target
3 Versioning
II Editor
A Editor interface
III Debuger
A Allow programs to be run from FB
B Create debuger
IV Project Management
A Tasklist
B Task owner
C Task timeline
D Sub task
E Auto progrss tracking
V Source Management
A Auto Doc
B Source Control, Integrate JCVS
C JAR Builder
D Decompiler
E Patching
F Verson Control
VI Documentation
allow a plugable syntax beans that use java mime type labeling. beans should able to recognise text syntax and parse the data to return the color type.
java syntax coloring bean should color all primitive types differntly. Color String Constants using corresponding mime type syntax bean User customizeable syntax coloring database
java syntax completion beans should autotype user object names methods veriables user customizeable text databases
Possibility to configure keystroke-combinations for different actions (eg show the code for the class under the cursor.)
Ability to use editor of choice instead of the one delivered with FreeBuilder (eg vi, emacs, UltraEdit.)
LinusGLarsson: f96-lla@nada.kth.se
Here are some things which are good to be known. FB have 3 kind of configurations. When you start FreeBuilder for the first time, FB use its build in options. From this moment you can change them like you want. These new options become your default configuration options. They are saved in JFBuilder.cfg (have to check) When I say options, this concern almost everything, even beans palette and FB position and size. This comes from FreeBuilder, not from Swing. When you create a new project, you configure your project options. First project options are your default options. So for every project you can have even own beans palette. Suppose some projects use more beans than others. The names for all your recently opened projects and files are also saved. So you can quickly reopen them. (File | Reopen)
FB can compile, make javadoc .html file, or put some file in a archive. Depending on what kind is the file, we can do some of this actions with it.
In project manager you can add : 1. Files. IF this is a java file or .pizza file, you can compile it, or make javadoc's html file. Otherwise, you can only put this file in archive and use it like a resource. For example .gif files. 2. Package. We will use all the .java or .pizza files in this directory 3. Root Package. If you do not like the name, we can change it. This means that we will use all the .java or pizza file in this directory & its sub directories.
For example, when I compile FB from FB, FreeBuilder project is made by one Root Package : "fb". For example in JBuilder I have to add all the packages in project manager. In Symantec Cafe all the files in the project. They are about 15X. 4. Directory. All the files in it can be included in .jar file. 5. Root Directory. Like Directory, but with all its sub directories.
I read that JBuilder ver 2.0 can add directories too. Because ver 1.0 can not. May be they have looked at the FreeBuilder :-)) In Project | Properties | Project Options there are several paths to directories.
JavaDoc output Path. This is the directory where javadoc will generate project's .html files.
Class Output Path. In this directory compiler will write your project's .class files.
Pizza Output Source Path. Pizza compiler can produce .java files from .pizza files. So this is the directory where these files will be written.
Doc Path. This is the directories, (including .zip or jar files) where FB will look for your .html documentation files and Show it.
Hey, we have to put a .html viewer in FreeBuilder.
Source Path. The places where your source files are.
FB make l list of all the not unique root paths from : Project path, Source path, Class Path & Class Output path. When you say New Package, or New Root Package, you see a tree with all the packages in these directories.
In this way, you can not add a package which is not in your paths. This makes you to create your directory structure, add path(s) to your project configuration, and then add a packages, files, directories and so on.
You or who wants can continue ...........
George Petkov
| Content of these pages are owned and copyrighted by the poster. | |
| Hosted by: |
|