Bruce Dodson wrote:
There is some name confusion though. SciTE is a sample application, not a
library. With that in mind, would it be okay to reconcile some of these
names? Right now we have AddCommand, AddJob, and Execute (plus whatever we
call the worker method that gets invoked from both ToolsMenu and AddJob).
It gets difficult to keep track.
Since we use the word Tool for the menu title and the settings,. how about:
AddTool() to replace AddCommand()
DecodeToolMode() to replace DecodeCommandMode()
AddToolEx() to replace AddJob()
and LuaExtension could stick with scite.Execute() or could adopt
scite.AddTool()
I do not know anything about Director so I cannot say whether the
DecodeCommandMode() method would ever be required. If not, then many of
Bruce's suggestions could be implemented with no loss of functionality.
I know that I would never use scite.Execute() with the numeric
indicators for the subsystem and flags, so removing that feature would
not harm me. And since it is a new development, there would be no
breaking of existing code, but there could be a negative impact on the
users who prefer to set up the tools using the flags...
Okay, I just shot my own argument down. Users may not use the tool mode
string, but that is only replaced by several equivalent tool properties,
so instead of having the scite.Execute() method look like the internal
AddCommand() method, use what is easier!
damn, I've got some developing to do :-)
April
--
I am one with my duality.
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
