| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
attempt to further address http://spbug.com/l/13
- Update localisable strings
|
|
|
|
|
|
|
|
|
|
|
| |
with extended characters in MySQL identifiers (names of dbs/tables/cols):
- Move encoding queries and control into MCPKit, with newly cleaned-up methods, and switch a number of locations to using the new code.
- Use UTF8 connections for many identifier-based queries (selecting and listing databases, tables, stored procs, table information). This fixes selection and creation of table and database names containing extended characters, also fixing exceptions and errors.
- Improve UTF8 over Latin1 to correctly set the client character set encoding as well, fixing custom queries and edits; remove custom code in SPTableContent achieving the same thing in a single location.
- Fix database encoding detection routines
- Update localisable strings
|
|
|
|
| |
indexes view labels
|
| |
|
|
|
|
| |
item localisable
|
|
|
|
|
|
|
| |
code; this addresses hangs (see Issue #6677) and also prevents triggering the discrete graphics chip on newer MacBook Pros.
- Update localisable strings
|
|
|
|
|
|
|
|
|
| |
methods
- Improve error handling when the connecting dies during import (previous the sheet would stay open)
- Fix localised strings for error messages (label and text the wrong way round)
- Improve comments
|
|
|
|
|
|
|
|
| |
strings
- Tweak MySQL help search to include a localisable language code for results in requested languages
This addresses Issue #743
|
|
|
|
|
|
|
|
| |
- Add custom Safari-style tab close buttons
- Tweak margins, especially on the right when a progress indicator is active to avoid doubled margins
- Fix tab bar rendering when using font/help etc windows
Also update the .strings files to match latest changes
|
|
|
|
| |
progress indicator to indicate that it's connecting in the event that the user switches to a different tab. Also preserve the tab's label as 'Connecting...' when switching tabs.
|
|
|
|
| |
update strings files.
|
|
|
|
| |
as how they are updated with respect to the selected export type.
|
| |
|
| |
|
|
|
|
|
| |
- Only applies when one tab is present.
- Saves last used state to preferences.
|
| |
|
| |
|
| |
|
|
|
|
| |
controller and XIB in preparation for the UI redesign.
|
|
|
|
|
|
|
|
| |
.xibs; add a build stage to Release/Dist builds which generates .strings files for each nib, and swizzle nib loading to automatically translate strings based on any localised .strings files
- Fix the genstring stage of the build script and move it to Release/Dist builds only
- Update Localizable.strings to match latest code
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Includes a completely redesign approach to all export data types based on the use of NSOperation subclasses. CSV, SQL, XML and dot export types are currently functional, while the source files for PDF and HTML export types exist they are to be implemented, but are currently hidden from the interface.
Also includes the following:
- Completely redesigned export interface.
- The ability to customize CSV NULL values.
- The ability to specify whether the UTF-8 BOM should be used in SQL dumps.
- The ability to specify whether BLOB fields are output as hex or plain text during SQL dumps. Defaults to hex.
- Exporting currently selected tables via the tables list context menu.
Outstanding issues:
- Not all progress indicators for all export types are functional (or functioning correctly).
- A few issues related to the introduction of only exporting the content and create and drop syntax of specific tables during SQL dumps.
Needs some serious testing and benchmarking to ensure it replicates the current export functionality.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
be NULL as nullable fields are not supported. Fixes issue #614. Although resolved, this will ultimately be fixed in a better approach upon the implementation of issue #297 that should allow the user to customize many of the properties of the initial field of a new table.
|
| |
|
| |
|
|
Interfaces/ for XIBs. This addresses the first point on issue #593.
|