Visualage for Java Skills
Yang Xugang
IBM's Visualage for Java is a powerful, Spiritual Java programming environment. This article introduces several techniques and secrets that are related to this tool.
Remove code from the warehouse
VisuaLage stores all Java source code, class files, visual design information, and item premium first selection settings in a database. This data library is also called a warehouse. Visualage's most clear mobilized leak is that the user cannot directly delete the code from the warehouse. The only path of the clearance of the warehouse is to export the east west to keep it, and the output documents are used as a warehouse. In the next process, the smart user can reduce the capacity of the warehouse from 36MB to 18MB, significantly improve the system.
Is there anything in the warehouse? The warehouse contains Java source code, class files, and visual designers, with items (PROJECT) groups, the package in Visualage for Java is a package defined by Java language. The project is a concept of Visualage for Java. This concept is to group the code as a group. Visualage for Java's warehouse contains the following items: Two versions of the Java class library: one is the Presentation Manager (OS / 2) version, the other is Win32 (Windows95 / NT) version; about 4MB paradigm (included in the Enterprise Edition) Many examples); IBM UVM class libraries, mainly as a proprietary editor in the Visual Composition editor; any item that any user has added.
In order to develop applications and Java Applets with Visualage for Java, the warehouse (Repository) and Workspace must include the following items: the Java class library version used in the platform; "Sun Class Libraries Win32" for Windows 95 / NT; IBM UVM class library; EAB project (only Visualage for Java Enterprise); any user planned or modified code when using Visualage for Java.
The process of clearing the warehouse is as follows (Note: Before executing the process, you must first prepare the warehouse and work in space, to prevent the recovery of the present time):
1. Requakers on the warehouse and work. If you have installed VisualAge for Java to C: / IBMVJAVA /, these files are located in C: / IBMVJAVA / IDE / Repository / Ivj.dat and C: / IBmvjava / IDE / Program / IDE.ICX. 2. Convert the present version in the front workshop to select "Version" from the pop-up menu in an item in the work space.
3. Ensure that only the items you want to keep in the work space, delete anything else needed. If you run Visualage for Java on Windows, don't include the Presentation Manager Java class library; if you run on OS / 2, don't include Win32 Java class libraries; if you need, you can add it from the warehouse.
4. Use the interchange format to output the JDK, BDK, and IBM modes to a Samples.dat document in an interchange format, in order to use it. For this output, you need to select these items in the work space, then select "Export" from the file menu. When you are output, you must select "Interchange Format". It is proposed to save these files in the C: / IBMVJAVA / IDE / Repository sub-direct record in the document named Samples.dat. Note that the output will only keep the latest version of the resulting code, and the new warehouse will not contain an earlier version. If you want to make the old warehouse as the old version of the archive file, you can enter from the archive document, just like it is intended to exchange the document.
5. Remove JDK, BDK, and IBM model items from work space.
6. Export all the items left to another to another exchange document, which is recommended to use the Core.DAT name in the same warehouse. ---- 7. Make sure the project in the workspace is an item output to Core.Dat, which does not to edit any files in the workspace before the clerution process, otherwise, warehouses and workspaces may have consistency problems. .
8. Reverse Visualage for Java.
9. Enter the C: / IBMVJAVA / IDE / Repository Directory (or the corresponding installation).
10. More Ivj.dat is more than Ivj.OLD, save this document until it is determined to make a success.
11. More named Cat is more imported. ---- Now, we have clearly removed unwanted items from the Visualage for Java warehouse. When you enter Visual As Java, we will only see items in Core.Dat!
After you get a clean warehouse and work space, we have a copy of them,:
1. Copy C: / IBMVJAVA / IDE / Repository / Ivj.dat to base.dat. 2. Copy C: / IBMVJAVA / IDE / Program / IDE.ICX to Base.icx.
Inferring step, you can follow the simple step of following the surface:
1. More than the warehouse file (C: / IBMVJAVA / IDE / Repository / Ivj.dat) is all the all.dat.
2. Copy the saved base.dat file to c: / ibmvjava / IDE / repository / ivj.dat.
3. Copy the saved base.ICX file to C: / IBMVJAVA / IDE / Program / IDE.ICX. This move will use the pre-contained work space (the working space and the storage warehouse) to replace the existing work space.
4. Launch Visualage for Java.
5. Enter the code you want to keep from all.bat documents. Note the warehouse file is the exchange of documents, which can be completed with the choice "Interchange Format" as an input format, which can choose any of the items and bags that want to keep the items and bags to keep the project and package from all.bat documents.
6. Adding items and packets from the warehouse to work space.
With this process, we can easily save multiple code editions in the warehouse, and clear the version that does not want to keep it. Improve the development of environmental energy
Visualage for Java is a development environment that requires a large amount of resources, executing multiple tasks, such as adding editing and from attribute confidence. In order to make this process less consume some time, we can use the following skills.
1. Select the appropriate driver and remove the fragmented
The hard drive drive often has a lot of impact. When installing Visualage for Java, please follow the following box: SCSI drive's access rate is often fast than the IDE driver, if possible, should be installed on the SCSI drive. If there are multiple physical drive (not multiple partitions on a physical drive), do not put VisuaLage for Java on a hard disk containing virtual memory. If there is an air-zone of about 200MB, it is installed in this zone and does not install any other east west in the partition, which will reduce the warehouse fragment.
The Visualage for Java warehouse is large (Tong often exceeds 20m), and will have a lot of fragments. Dragmatic slices (more than, for example, every day) are often accessed, and the speed can be significantly added.
2. Optimized window exchange file
If you run Visualage for Java on Windows 95 and NT, virtual memory settings will greatly effectively. If there is no number of internal memory spaces, when using VisualAge for Java and other tools in the system, there is a memory that can be exchanged with magnetic disks. This is a spin of several optimization systems: use a system monitoring tool to find the size of the exchange document, which will help accurately determine how much exchange space is required. Set the minimum exchange document size. According to the system, set the minimum exchange file size to the size observed by the previous step, and Windows will distribute this size of the hard disk space to the exchange document. In the case, when the file size is default, Windows will be converted to the document size. Set the maximum exchange file size to the maximum available magnetic disk space, which will help to avoid overflow errors, Windows will not adjust the file size, divide more spaces. 3. Remove the code from the warehouse and work space
As mentioned earlier, the Visualage for Java warehouse is a database, which contains all source code versions and class libraries, as well as visual design information and project preferred information, smaller warehouses mean good data when actually use. interview time. The work space is a window that enters the warehouse. This window allows you to visit a set of identified items and packages, which only contain one code version.
When the user performs a editing operation, Visualage for Java will check from the property in the work space, and re-edit anything needs to be re-edited. Larger work space intensifies more from property inspection, results, and performance is reduced. If there is a code in the work space, please follow the steps below:
(1). The code version that is no longer used. Select this code (or yourself) in the work space, and select "Version" from the pop-up menu. Passing the code of the code in the warehouse in the warehouse, when the code is required, it can be retrieved from the warehouse when this code is required.
(2). Remove the code from the work space. After the conversion code is removed, it can be removed from the work space, and it is still in the warehouse. Now, any editor of the work in the work space will not check this code.
The sustainable "small warehouse" "small warehouse" is a method between two deletion of the proceedings. If you have some code, you use (for example, a Java model), the useer can lead the skills deleted from the warehouse in the article, but it is necessary to use a separate exchange document to save the code. For example, the use of the school is issuing a practical solution, he can make a lot of work for this, then write it on the CD or on the web network, and there is a time period no need to use it. When this code is not used frequently, he can output it into an exchange document, then remove it from the warehouse. The lower surface is a specific method: the package or item that will be stored will be stored. Out of it in a single-alone exchange document, give it a meaningful name, which can be easily recalling which document is. Remove the code from the warehouse in the warehouse. When this code is required again, enter the exchange document, then add this item to the work space. 4. Get more memory
The best, the most suitable method of obtaining Visualage For Java is to increase more memory. As the computer has become faster, the number of file I / O speeds is more and more, and it is a bottle of neck factor. If there is no sufficient memory to run the program, the data must be exchanged with the hard disk, compared to his operations on the operator, this exchange will be non-slow. Adding more memory can be raised to at least 64MB, which can be changed, which can be significantly changed.
For VisuaLage, 64MB memory has been enough, but there is no more, especially if you run Visualage for Java, browser, mail program, drawing program, word processing software, and text editing. By below, the memory is very suitable, and the efficiency of work efficiency can be retrieved.
