Okay, in that case it would be a common method that is called by both AddJob and ToolsMenu, rather than having ToolsMenu call AddJob directly. (Mainly for the sake of clenliness.)
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. Regards, Bruce * I like the idea of loadable extensions. If nobody else is working on that right now, I may look into that personally. (I assume this won't be stepping on April's toes, since it is not really tied to the Job system. Correct me if I'm wrong!) "Neil Hodgson" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > April White: > >> Neil did not want an extension to interface to a SciTE method such as >> AddCommand(); AddJob() only has simple C parameter types > > One of the plans was to allow the extension interfaces to be used > from other languages or compilers through loading a DLL. > > Neil _______________________________________________ Scite-interest mailing list [email protected] http://mailman.lyra.org/mailman/listinfo/scite-interest
