|
|
|
|
|
| Project Manager |
|
This is where you manage all current
projects. The project manager can open a "Workspace" which can
consist of an unlimited number of "Projects". This is where you
will navigate the files of your project on a graphical "Tree -
View". Files within a project can be separated into
"Folders" to ease conceptual separation of files and
browsing/selecting the files. This will also be the primary point of
project configuration including, but not limited to, compiler/build tool
options.
|
|
Plug - in Editor Components |
|
All editors are being implemented as plug-in
modules. This will allow for easy addition of new editors such as icon
editors, dialog editors, etc. Default editors can be assigned to each file
type, and these choices can be overridden to use any installed editor with
any file. This will also allow different types of editors to be created
for different programming styles.
|
| Editor Plug-ins currently
under development include |
|
Aleksandras Gluchovas' Language Sensitive
Editor - Syntax highlighting for C/C++ and Java, Auto-indenting,
multi-level undo, more
Generic Text editor - simple text editor
based on the wxWindows text control - also contributed by Aleksandras |
| Plug in file manipulators |
|
File browsers, class browsers,
autocompletion tools - these are all being developed with a plug-in
interface to allow easy addition, removal, or changing of these
components.
|
| Online Help
(contributed by
Vaclav Slavik) |
|
wxStudio has an integrated Hypertext Help
system based on wxHTML which will allow context sensitive help as well as
help browsing by "book" or subject. New help "books"
can be added at any time by the user to allow adding help for a specific
tool or library.
|
| Application Framework
Generator (App Wizzard) |
|
Automatic generation of projects and base
template files for several types of wxWindows and non wxWindows
applications. Custom application generators will be possible.
|
| Compiler/build tool
Integration |
|
Automatic generation of projects and base
template files for several types of wxWindows and non wxWindows
applications. Custom application generators will be possible. The ability
to build programs directly from the IDE with various compilers/build
tools. This will most likely be in the form of tool-specific plug-ins.
|
| Debugger Integration |
|
Automatic generation of projects and base
template files for several types of wxWindows and non wxWindows
applications. Custom application generators will be possible. The ability
to debug programs from within the IDE and navigate debug errors in editor
windows.
|
| CVS/Source Code Tool
Integration |
|
Project management and source code
maintenance from within the IDE.. able to check - out/commit files
"on the fly" as needed without leaving the programming
environment. Online diffs against cvs sources.
|
| Dialog Editor |
|
This will now need to be implemented as an
editor plug-in -- perhaps more than one will be available with different
features. There may also be a "form editor" to allow designing
VisualBasic(tm) style form based applications.
|
|
|
|
|
|
|
SUGGESTIONS
FOR FEATURES - NOT YET ADOPTED |
|
|
| Component gallery (suggested
by Julian Smart) |
|
One frustrating thing when starting a new
programming project is having to set all the include and library variables
to link in external libraries. We could instead have a gallery of
libraries and their locations, so we only have to select which libraries
we wish to include, and the relevant makefile components will be
generated. It could also match the settings of the library to the settings
of the application, which means keeping tabs on several configurations per
library and app.This implies that the user should be able to set up a
number of different, custom, configurations, and compile them
simultaneously. The basic setup would be debug and release, but there
could be others. MS DevStudio allows custom configurations, which is a
very useful facility which would otherwise mean that a separate project
file is needed per configuration.
|
| Documentation tool (suggested
by Julian Smart) |
|
How about a documentation-generation
facility, or at least something that cross-references files, classes,
variables etc. It would be nice to be able to edit class library
documentation independently of the headers, but be told where there are
inconsistencies between the documentation and the classes. The headers
could be used to generate a series of forms for filling in the
documentation. Or, we could have a hybrid approach combining the use of
specially-marked comments, plus more in-depth and flexible documentation
in a seperate database that's merged in to the final document.
|
| Folding in editor (suggested
by Vaclav Slavik) |
|
- ed. note: with new plug-in editor organization, this
would be a nice alternative editor! |
| Automatic saving of changes
(suggested by Vaclav Slavik) |
|
local CVS repository used as backup tool
(and thus you can trace changes w/o access to internet CVS repository --
you could have 2 CVSs for one project - local backup and global one)
|
|
|
|
|
|
