Code Explorer/Parser

This is a two-fold extension of an existing IDE, based on the Innerfuse PascalScript scripting language. Obtain PascalScript at <[login to view URL]>, and you will see it is a full-fledged scripting language, and comes with an IDE example. Feel free to make seperate bids for each of the two extensions of the IDE. Note that I am not associated in any way with the parties described above, or in the deliverables section. See the deliverables section for details (not here because of insufficient space). ## Deliverables The first set of extensions I need can be described as making the IDE more professional and working with the code more visual: 1) Add a **Code Explorer**, just like in Delphi 2) Similar to the **Visual Studio** IDEs, add drop-down combo boxes that navigate to a particular function in the code, add new (pre-defined event) functions to the code. One combo box could be for functions and another for the sections in the code, such as globals, constants, etc. 3) A **programmatic way** to change the source code as follows: delete named functions, add a function body to specified location, add a function call to specified location (such as start/end of another functions body), etc. In general, whatever feature is available through the IDE should also be available in programmatically. The second set of extensions are more like representing the actual PascalScript code in a **poetic, semi-visual** way. For an example of what I mean by a poetic, semi-visual script, please try Wise Installation System Professional (get free eval from [login to view URL]). I will need the same look-and-feel for the IDE. In general: * an extended ListBox control to show the poetic script * ability to do copy/cut/paste on the poetic script (actions that also effect the actual script) * ability to double-click on the poetic script and raise the proper dialog to edit function parameters * ability to type in the ListBox to bring a list of supported functions (or add a remark, just like in Wise), or drag-drop a function name from a list to add it to the script (again, as in Wise) In particular: * Function names, parameters and their types used in the actual code must be obtainable programmatically. These parameters will be used in showing visual dialog boxes to edit functions. * Successive function blocks should be merged in the poetic script to reduce clutter and make the poetic script look "more poetic and easy to understand". For example, see how Wise merges statements that edit the registry - if you have two/three such lines, it says "Edit 3 Registry Items", instead of listing each edit operation one by one on a line by its own. * Conditionals, loops, try/excepts, and similar looping language constructs should be handled by the poetic script, with proper indentation. Again, see how Wise handles if/end. * The poetic script should properly recognize assignments and nested function calls within statements. * Line correspondence between the poetic and real script must be maintained. Both views should update one another automatically when switching from one to another. * Events in the ListBox component to indicate where the user is editing, which function/statement the user has chosen to edit visually, etc... 1) Complete and fully-functional working program(s) in executable form as well as complete source code of all work done. 2) Installation package that will install the software (in ready-to-run condition) on the platform(s) specified in this bid request. 3) Exclusive and complete copyrights to all work purchased. (No GPL, 3rd party components, etc. unless all copyright ramifications are explained AND AGREED TO by the buyer on the site). ## Platform All Win32 Platforms.