Tour through T-IDE V2.0
T-IDE V2.0 is brand-new, includes
themes for better look-and-feel on every platform (incl. WIN-XX). It
includes several enhancements and speedups. After you have used it for
a project you will know about the benefits you get through T-IDE and
you will never use anything else (and it is not limited to Tcl only!).
After the "welcome-picture" has disappeared the T-IDE-starter pops up.
This is the place where you can create new projects, open existing ones (the last 10 can be easily accessed via the History-menu), close open ones, rename and delete projects. In the Tool-menu you will find an entry called "Workspaces". If you are programming in a team, this is the place where you define your workspaces (every programmer gets his own private workspace to work in and put then the result into the shared workspace to make it accessible to all others). But in our tour we will omit this step.
First we have to create a project
By pressing the "New Project"-Button we get now a window called "New Project" to set all necessary values.
We will use a path with already existing files with the shown settings:
Lets press "Create".
The parser parses through all source-files and stores the result in a database.
Then the Project-editor pops up.
Here showing some different styles:
In case CVS is your Revision Control System the Project-Editor would look like this (with additional buttons to control CVS):
<>The Project-editor lets you modify the structure of the
can not only add or remove files to every project, you can also add or
remove subprojects (or complete trees), where the physical location of
the single project is unimportant.
You can view the files of a specific project by clicking on the appropriate folder. The folder-icon itself is replaced by a sheet-icon. Files in bold are readable and writeable; files in normal script are read-only; this in italic are symbolic links. Symbolic links are used if the current project is opened in a private workspace (team-developement). Enabling the switch "Lockers" shows the locker and the locked revision. Enabling the switch "History" shows the revision-tree for the selected file (only if a revision-tool has been specified).
Now we want to edit a file. A doubleclick on a source-file opens the editor :
On the right hand side of the editor you see a list of all procs defined in this file. Clicking on it relocates the editor to the location of the proc. Proc-names can be shown in colorized in a different font, comments also (can be modified in the Preferences).
The editor offers you all possibilities of navigation :
From the editor you can debug your current file (if its a part of an other one you can specify it). TUBA has been integrated as standard-debugger (thanks to John Stump). You can easily jump between editing and debugging (only for Tcl8.0.x!).
To test your application you have just to press the "RUN"-button....
If your application has been tested well you can compile it to byte-code by selecting "Make - make target".
Other features of the editor : easy access to a VCS-tool (currently RCS and CVS, other will follow soon), to a GUI-builder, a user-menu to add own tools, mostly used commands as keyboard-shortcuts, use more than one editor at a time.
Lets continue with the Diff/Merge-tool ....
The Diff/Merge-tool is available as 2- and 3-way diff (e.g. to merge 2 branches into the main-branch).
The Retriever :
A double-click on a listed item opens the source-code-editor just at the position of the retrieved item.
The Symbol-Browser :
Shows procs, variables and globals used in the selected projects. The contents of the list may be filtered. This is a good way to find double-use of a symbol. Like above in the Retriever the location of the selected symbol can be edited by double-clicking on the symbol.
The Referencer :
The above screenshot shows a nested "ref-to" tree. To limit the displayed information Tcl/Tk-commands and globals/variables can be switched off.
You cannot only view the proc call-tree, but also find the procedures where global variables are referenced for write or read-access.
e.g. "global TREE referred by" gives you all procs reading or writing the global. Or : "proc Tree:build referred by" gives you all procs calling Tree:build.
By double-clicking on a node the source-code-editor opens at the position where the symbol is used. This is a very convenient way to understand the process-flow of an application.
Even this view can be limited by selecting or deselecting projects.
The Hierarchy-Browser :
Shows the used widgets depending on the selected projects. Will be available with our GUI-Builder.
The Configuration-Manager :
Helps to manage configurations within your preferred VCS-Tool.
Note: this tool is not available in TIDE light!
The Documentation-Editor :
Produces HTML-documents of your source-files. The documentation can be done for the whole project or file-by-file. Colors indicate the documentation-state of the Project/File (red = not documented, yellow = partially and green = fully documented). A master-index can be generated by request. Each generated .html-file can be modified by the T-IDE HTML-editor.
This tool is available in the full version of T-IDE.
The Shell :
The purpose of this tool is to catch the results of a lint- or compiler-run. By selecting an error-message you can directly navigate back to the source-code-location to fix the problem.
Supported platforms (T-IDE 2.0) : Linux, Solaris, WIN-XX.
Other platforms will be available on request.
Note: This is just a
preview to the new release, its not available yet!
NOTE: to bring this
great tool to market, I am either looking for an investor, who helps
doing the final things or an interested company willing to purchase the
source (including me).