IBM VisualAge C++ 3.0 Workframe: Difference between revisions
No edit summary |
m Ak120 moved page IBM VAC 3.0 Workframe to IBM VisualAge C++ 3.0 Workframe |
||
| (6 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
A WPS integrated developer's workframe. The "projects" are generated from templates and represent some kind of extended folders. The folders contain all the source and target files belonging to your project. Define all necessary tools and their settings directly from the same workframe window, and also all actions can be started from there. As a part of [[VisualAge C++ 3.0]] the workframe is preconfigured to contain the tools from that package, but it's possible to add whatever other tools you would like (although this process is not very obvious at first sight). The workframe is "object oriented" in the sense that you can derive new projects from existing ones, so the new projects inherit the features of the old project and you can add new ones or change features selectively. | |||
==Links== | |||
* [[VisualAge C++ 3.0]] | |||
[[Category:Integrated Development Environment]] | |||
Latest revision as of 20:27, 2 December 2019
A WPS integrated developer's workframe. The "projects" are generated from templates and represent some kind of extended folders. The folders contain all the source and target files belonging to your project. Define all necessary tools and their settings directly from the same workframe window, and also all actions can be started from there. As a part of VisualAge C++ 3.0 the workframe is preconfigured to contain the tools from that package, but it's possible to add whatever other tools you would like (although this process is not very obvious at first sight). The workframe is "object oriented" in the sense that you can derive new projects from existing ones, so the new projects inherit the features of the old project and you can add new ones or change features selectively.