|
Introduction
|
|
| Facilitating
the array of common development tasks, Visual Xbase++ 2.0 introduces
a new template mechanism. It further supports plug-in helper applications
typically called wizards, that can guide you through specific development
tasks. A "New Item" dialog can be opened up, simply by selecting
a menu item. This allows you to select the template you want to use
for your new VX Project very easily. |
|
| |
|
|
|
| |
|
|
Support of Win32 Applications, Web Applications and Packages
|
|
|
Through this template
mechanism, VX can automatically insert into your project code sections
and/or create new files, depending upon application framework selected.
For WAA applications,
for example, VX can automatically insert FORM() functions, saving
a lot of time generally spent coding the framework instead of the
logic of your application.
|
|
| |
|
|
Multiple application types (Console, Hybrid, GUI)
|
|
|
With Xbase++ various
changes of a certain type need to be implemented and/or changed.
Many Xbase++ developers have the tendency to overload the standard
AppSys() procedure as to prevent the creation of the default XbpCrt
window. This is especially true for the implementation of fulll-blown
GUI applications.
With VX, all of
these changes and modifications are performed automatically! This
functionality is going to be extended up to the point where you
can request extended application types to be created, such as Explorer-style,
MDI or Workspace applications.
|
|
| |
|
|
Plug in your own Wizard using Xbase++
|
|
|
The template and
wizard system is specified to be extensible via a plug-in mechanism.
Depending on your
requirements, you can provide a wizard and/or template suitable
for seemless integration your package(s) into the environment.
All Wizards shipped
with VX are written in Xbase++ and their source code is going to
be included as part of the standard installation. This allows you
to customize existing behaviour according to your needs and/or to
write your own Wizards, using existing ones as a guideline.
|
|
| |
|
|
Project Navigation
|
|
The
project manager integrated into Visual Xbase++ features several views
for browsing project-related information. Check out some of the samples
below. On the right hand-side you can observe the File View. It lists
the files belonging to your project grouped by targets (EXE or DLL).
On the left hand-side, the Entity View is shown. It desplays a project
by classes and their respective attributes, such as instance variables
or methods. Different icons are used to visualize these attributes,
providing vital information at a glance.
|
|
| |
|
|
|
| |
|
|
Multiple targets per project
|
|
| With
VX, there are no limits or restrictions when it comes to the types
and/or the number of targets that are to be a part of a project. Thus,
large projects, which are kept within a single project file, can be
maintained (of course, including their assorted service and utility
DLLs, if desired or need be). |
|
| |
|
|
Full backward compatibility with PBUILD and XPJ
|
|
|
VX builds on Alaska
Software's project builder (PBUILD) which is already used with current
Xbase++ revisions. Therefore, full compatibility with existing projects
is guaranteed. Furthermore, full command-line support for the build
tools is provided, allowing you to do batch-compiles or integrate
an Xbase++ project into another project that is built using a MAKE-like
build utility.
|
|
