Jump to: navigation, search

Difference between revisions of "Talk:Platform UI Command Design"

(org.eclipse.ui.commands?)
Line 6: Line 6:
  
 
Shouldn't the commands extension point be in org.eclipse.core? It should be possible to drive behavior in a headless application - there would just be no menus or icons or key bindings.
 
Shouldn't the commands extension point be in org.eclipse.core? It should be possible to drive behavior in a headless application - there would just be no menus or icons or key bindings.
 +
--[[User:Ed.burnette.sas.com|Ed.burnette.sas.com]] 11:33, 13 September 2006 (EDT)
 +
 +
== Macros, scripting, etc. ==
 +
 +
There should be more info here about how this helps macros (scripting).
 +
--[[User:Ed.burnette.sas.com|Ed.burnette.sas.com]] 11:33, 13 September 2006 (EDT)
 +
 +
== Undo ==
 +
 +
Special thought should be given to how this fits in with "undo" functionality. It seems the simplest thing would be to require each command to not only specify a class to "do" something, but also to "undo" it. I know there's a whole undo framework and IUndoableOperation, etc., but it all seems like overkill to me for such basic functionality.
 +
--[[User:Ed.burnette.sas.com|Ed.burnette.sas.com]] 11:33, 13 September 2006 (EDT)

Revision as of 11:33, 13 September 2006

Commands, Handlers, and KeyBindings are mostly done. Now we need support to place command items in menus and toolbars.

--Pwebster.ca.ibm.com 08:35, 17 August 2006 (EDT)

org.eclipse.ui.commands?

Shouldn't the commands extension point be in org.eclipse.core? It should be possible to drive behavior in a headless application - there would just be no menus or icons or key bindings. --Ed.burnette.sas.com 11:33, 13 September 2006 (EDT)

Macros, scripting, etc.

There should be more info here about how this helps macros (scripting). --Ed.burnette.sas.com 11:33, 13 September 2006 (EDT)

Undo

Special thought should be given to how this fits in with "undo" functionality. It seems the simplest thing would be to require each command to not only specify a class to "do" something, but also to "undo" it. I know there's a whole undo framework and IUndoableOperation, etc., but it all seems like overkill to me for such basic functionality. --Ed.burnette.sas.com 11:33, 13 September 2006 (EDT)