Reminds me of a dream: combining the code editor + the debugger + data dictionary + source code repository + a very large display screen format into a single integrated developer interface.
1. make it possible to record (or associate for later integration) our typing (speaking) during interactive sessions with the code. Today we use separate and isolated sessions to interact with these sub-systems to our detriment because precious information obtained during debugging is too hard to integrate back into source code. This process should instead be smooth and transparent. 2. display the code being run on a very large screen in flowchart format using icons to represent objects in play. Show the logic flow through the system from entry point through the life of the execution thread, leaving a (light green) trail of the logic flow as code progresses from box to box. In high level view, flow would be between object icons, but with a drill-down capability to the instruction level. Would need a throttle that goes from stepping through individual instructions to incrementally running faster until full speed. Open databases, prgs, objects, etc. would appear as high-level icons on the screen, but clicking on an object expands the object to reveal it's PEMs, especially useful as instruction execution proceeds through the object. Leave a green-colored trial as logic progresses through the objects of the system. At startup, show icons for each component as they become active. Make it possible to view (at whatever speed, from single step to full speed) the (green) trial of logic as it goes between objects, at the object/box level -> detail instruction level. Very large screens aren't available (inexpensively) today, but this stuff can all be done with scaleable math that would allow for very large as well as presently available display sizes (including multiple monitor systems). No reason not to expect the underlying technologies to continue behaving according to Moore's law, so we should be seeing very large displays before too much longer. 3. Allow for changing names (permanently, of anything - but no mistakes!) during this combined editor/debugging process. This involves the data dictionary, which should be dynamic, not static, when development is active (and with locking for shared dev systems) 4. Continuous backups, which it manages, are mirrored in at least 2 places, and support step by step and date/time "undo" processes. When a build is run, all contributing source code for the numbered version number should be stamped and saved. Bill _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
