• first implementation to allow the user to write and use self-definable functions inside the Custom Query Editor

- such commands will be stored as foo.spBundle in SP's Application Folder/Bundles
- up to now they will be displayed inside the context menu as submenu Bundles which can be by itself contain further submenus specified via 'category' key
- to each command the user can assign a tooltip and a keyboard short-cut; if user chose a standard SP short-cut it will be ignored
- commands will be executed as bash commands ie it can also be written in any script language
- the bash process inherits several environment variables like SP_BUNDLE_PATH, SP_SELECTED_TEXT, SP_SELECTED_DATABASE, SP_SELECTED_TABLE, SP_CURRENT_QUERY, SP_CURRENT_LINE, SP_CURRENT_WORD
- the bash command's result can be processed as follows: insertAsText, insertAsSnippet, replaceContent, replaceSeletion (with fallbacks to word, line, query, entire content), showAsTextTooltip, showAsHTMLTooltip
- up to now all installed bundles are reload for each menuForEvent: [this is tendative!]
- each spBundle command has a scope to allow to the user to specify for which SP element a command can be useful; up to now only the scope 'editor' is supported; further scopes could be 'data table' for context menus of mysql table data (Content or Custom Query - including info of selected lines, table data in different formats, etc.)

- foo.spBundle files can be installed simply by double-clicking at it (remember up to now Bundles will be reloaded while opening the editor's context menu!)

two tiny examples for testing: http://wwwstaff.eva.mpg.de/~bibiko/dt/temp/spBundleExamples.zip

0 files changed, 0 insertions, 0 deletions