The Cache page of the Productivity! Project Properties pages provides the following options:
See also: Productivity! Options Property Page, Productivity! JavaDoc Property Page, Productivity! Code Style Property Page, Productivity! Options
To set these options for all the new projects, select Project|Default from the Project Properties.
The main goal of Productivity! is to increase the developers’ productivity to its maximum. Since, presumably the application will be frequently used, it should work as quickly as possible. The project may contain several thousands of classes (including the classes directly included into the project, JDKs and required libraries classes) and constant search through them would be highly inconvenient. Thus, Productivity! builds classes cache right after the first invocation and then stores it to hard drive providing for future re-use. After cache build or load, Productivity! uses it for quick access to the classes according to the specified criteria.
Options grouped on this page allow you to control the process of class cache building and refreshing.
This option allows you to specify whether cache will be refreshed automatically.
The most frequently changed classes from all the classes used by the project are those included into the project itself, in other words, the classes developed by you within a project. Whereas changing JDK and adding or removing libraries are very rare operations, new classes within a project appear, change their location or become renamed every day.
The Autorefresh options are designed to make the cache content as up-to-date as possible, offering convenient usage of such Productivity! tools as Class.Insight and Browse.Insight with your classes, and also to reduce the necessity of manual refresh of Productivity! classes cache.
This option enables your class cache to be refreshed after every successful project build or make. Refresh of classes included in the project is normally a short operation that requires much less time compared to project build, so we recommend that these options be always enabled.
Please note that the class cache refresh will be performed only under the condition that the whole project build or make is successfully completed (not just some of its files), and that there were no compiler errors during the build process.
You may tune the cache refresh process by using the refresh groups. Refresh group is a set of packages that may be refreshed independently. Thus you may specify a set of refresh groups that would include the most frequently changing classes, and refresh their cache individually.
You may specify your refresh groups using the table shown above. Use the Add new button to create a new group, the Edit button to edit the existing group, and the Remove button to delete a group.
The Refresh button allows you to refresh the selected group.
Please note that double-clicking a group row brings you up to group editing (similar to pressing the Edit button).
Creating new groups as well as editing the existing ones
is performed via the New/Edit Refresh Group dialog.
Please use the Group Name field to specify the name of the group to be refreshed, and the Packages to refresh field to specify the packages to be included into the group. You may specify the packages for inclusion by either manual typing (only valid Java symbols are allowed, separator for packages is ;), or by adding them via the Select Package dialog, invoked by the Add button. The order of specified packages is not essential.
These options enable immediate start of the refresh operation for the Productivity! class cache.
You may choose from the following refresh types: of the classes included into the project only; of the project libraries (which is crucial to do after adding or removing libraries); or of the whole cache (including the classes from JDK).
See also: Productivity! Options Property Page, Productivity! JavaDoc Property Page, Productivity! Code Style Property Page, Productivity! Options