send "mouseUp" to button "xyzzy" of stack "someIDEstack"
dispatch "aSystemEvent" to stack "someIDEstack"
-- in ideDispatcher:
-- look up which components are interested in the "aSystemEvent" message
-- dispatch the message to those components and let them handle it
mwieder wrote:As a high-level overview, one of the problems with the current design of the IDE is that there are way too many dependencies among the various stacks.
What I'd like to see is a well-thought-out API that defines the contract for stack interaction, and the IDE components made as autonomous as possible.
malte wrote:In the meantime would it be a good idea to list pet peeves with the current IDE in seperate threads?
So in terms of community, it may be helpful to set up two teams: one team coordinating the new architecture, and the other doing the less glamorous work of taking care of issues in the current IDE until the new one is available.
phaworth wrote:FourthWorld wrote:Is it really the case that "we" would get into writing a completely new IDE? That's a huge task that I would have thought RunRev should be managing.
-- necessary because control-key sequences trigger a mouseDown event
-- in menuBars (bugs 9850, 9851).
if the mouse is not down then
if 99 is in the keysDown then -- control-C
else if 120 is in the keysDown then -- control-X
-- do stuff to support undo here
else if 118 is in the keysDown then -- control-V
exit to top -- resolves tmControl conflict
Users browsing this forum: No registered users and 3 guests