| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
- further minor improvements
- make usage of more constants
|
|
|
|
| |
able to make usage of constants in categorial addition files
|
|
|
|
|
|
| |
- further simplifications and centralizations
- runBashCommandWithEnvironment: now it can execute each script command whose first line begins with #!/... natively
- added some more shell variables
|
|
|
|
|
| |
- fixed appending of the entire sqlText after parsing
- removed replacing of / for better wrapping since it'll break the syntax highlighting
|
|
|
|
|
|
|
| |
causing crashes on certain files (lines 420,422)
- Improve SQL wrapping
|
|
|
|
|
| |
- added skeleton for scope datatable support
- removed unnecessary code
|
|
|
|
|
|
| |
- started to populate the main menu item Bundles [still hidden]
- enabled key equivalents for NSTextViews
- distinguishes between Query Editor scope and text input scope via menu item validation inside main menu Bundles
|
|
|
|
|
|
|
| |
- outsourced code to SPAppController to centralise Bundle support and make it available for different scopes (query editor, input text fields, data tables etc.)
- store bundle info scope-based
- added input text field support
- made usage of constants
|
|
|
|
| |
- note : still some sql files can be opened only sometimes - reason can't pin down so far
|
|
|
|
|
|
|
|
|
| |
- used embedded icon image via cid and mime type image/tiff
- sql view now wraps long lines
- improved general stability
- QL now runs on main thread
note: there're still some issues for which QL crashed mostly due NSAutoReleasePool releases - more investigations are needed; most of this issues are releted to long lines, icon caching, releasing ...
|
|
|
|
| |
Custom Query view. This addresses Issue #897
|
|
|
|
|
|
|
| |
when viewing SQL files - this fixes certain crashers, addressing Issue 896.
- Tweak a misspelling in the templates
|
| |
|
|
|
|
| |
- addresses issue 896
|
|
|
|
| |
• added URL scheme constants
|
|
|
|
| |
- not yet visible
|
| |
|
|
|
|
| |
unnecessarily. This improves speed slightly by reducing interface interaction, and preserves state better during actions, fixing bugs like Issue #574.
|
|
|
|
| |
issues when reconnecting after a network loss causing a drop in connection and proxy at the same time.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
last used favorite.
|
| |
|
| |
|
|
|
|
| |
well as the method to migrate existing favorites data. Currently not yet active.
|
|
|
|
|
|
|
|
|
|
| |
SP_ALL_DATABASES, SP_ALL_TABLES, SP_ALL_VIEWS, SP_ALL_FUNCTIONS, SP_ALL_PROCEDURES, SP_RDBMS_VERSION, SP_RDBMS_TYPE [hard-coded yet ;)]
• some minor improvements to editor Bundle support
• fixed issue while running a bash command that the SP GUI doesn't block
• added first sequelpro url scheme functionality
- sequelpro://$SP_PROCESS_ID/passToDoc/SelectTable/a_name
- sequelpro://$SP_PROCESS_ID/passToDoc/SelectDatabase/a_db_name
- sequelpro://$SP_PROCESS_ID/passToDoc/SelectDatabase/a_db_name/a_table_name
|
|
|
|
|
|
| |
scheme support
- introduced an unique process ID for each called bash command which will be set for the current SPDatabaseDocument and passed as environment shell variable SP_PROCESS_ID to ensure that such a scheme command will be executed by the correct SPDatabaseDocument, to avoid security issues ie one can authenticate such a sheme command, to enable url scheme process communication based on file shake-hands etc.
|
|
|
|
| |
doesn't start editing the selected favorite. This will also allow behaviour to be further customised. Fixes issue #892.
|
| |
|
|
|
|
|
|
|
| |
temp file SP_BUNDLE_INPUT_FILE since stdin and shell vars are difficult to handle for a large amount of data
• fixed AppleScript class definition since it was renamed
• added support for the URL scheme 'sequel' to allow to interact with Sequel Pro eg via bash: open 'sequelpro://executequery=select%205' [not yet implemented ;)]
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
improves handling of special characters in passwords, improving Issue #890
- Improve code in (the unused) [MCPConnection connectWithLogin:password:host:socket:] to match latest updates in the rest of the framework
- Fix creation of new users
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
list to an outline view in order to support grouping favorites. Future changes include creating a favorites data controller, including migrating favorites storage to their own plist in the app support directory as well as support for grouping favorites.
|
| |
|
|
|
|
|
|
|
| |
runBashCommandWithEnvironment:atCurrentDirectoryPath:error which will run self as bash command and will return its result
- if an error occurred it will return a NSError if desired
- added the chance to pass shell environment variables and start directory for future usage in user-definable plugins written as scripts
|
|
|
|
| |
filtered table content
|
|
|
|
| |
the opening resultset tag that produced the result.
|
|
|
|
|
|
| |
- Show the text cursor at the location future input will be inserted for clarity
- Show autocompleted text faded to indicate it's temporary and may be replaced by other keypresses
|
|
|
|
| |
exporting. Also, restore our old format and give the user the choice during export (defaults to MySQL schema). Completes the implementation of issue #840.
|
|
|
|
| |
- fixes issue 886
|
|
|
|
| |
10.5.8, addressing Issue #884.
|