Chronicle Plugin Release Notes

Changes in this release...
- Fixed a major bug related to how Chronicle handles multiple open text documents. Xcode's array of current text documents offers no mechanism for referencing the "frontmost" text document. Previous versions of Chronicle mistakenly use 'text document 1' to refer to the active text document. Because Xcode uses a static, linear array of text documents that does not reflect the front-to-back order of documents, but rather lists documents in order of when they were viewed, 'text document 1' always refers to the first document opened in the project work session, not the file currently being edited. As you can imagine (or may have experienced) this could lead to some unusual behavior and potentially cause some undesirable effects. If you experience Chronicle inserting text into the wrong location or file, PLEASE report it to the author as soon as possible.

- Toolbar 'Send' and 'Capture' buttons are now clickable buttons, as well as click-hold or control-click contextual menu's. Clicking the 'Send' button now performs a send operation to the frontmost Xcode text document's insertion point (equivalent to selecting "Insertion Point" from the Send menu). Clicking the 'Capture' button now immediately captures the current Xcode text selection into Chronicle (equivalent to selecting "Selection" from the Capture menu). For more Send and Capture options, you can pop up the contextual menu for either by control-clicking, right-clicking (with two-button mouse), or by clicking and holding the mouse button down for 1 second.

- Chronicle windows now use the standard window appearance rather than utility window appearance.

- The Actions menu is now also available as a contextual menu for the Files list. Simply control-/right-click on the FIles list to pop up the Actions menu.

- Newly-created items are now properly highlighted in the Files List if your preferences are not set to open the object automatically in the appropriate editor.

- You can now create a new file or folder while using either the File Editor or the Folder Editor. Previously, you had to return to the files list to create new files and folders.

- Pressing the "Delete" key while in the FIles List will now move the selected item to the Trash.

- Cleaned up much of the redundancy and development comments in the application code.

This version was an intermediate development release, and was not publicly available.

Changes in this release...
- Fixed the "Can't set «Class imaA» of "" to «Class imaA» id 2." error encounterd at startup by some users.

The second public beta release. This update fixes a few development oversights and some aesthetic issues. It also adds a couple new features.

Changes in this release...
- Default User Data folder path was hard-coded for development purposes, but is now assigned dynamically to a custom folder in the current user's application support path.

- Chronicle Installer now confirms that Xcode is not running while installing the plugin. Previously, the Installer failed to check if Xcode was active, producing an error when uninstalling or overwriting previous installations of the plugin.

- When capturing text from Xcode into a new Chronicle file, or a Chronicle file that still only contains the default placeholder content, the captured text over-writes the default content rather than being appended to it.

- A new preference has been added, which allows you to determine whether Chronicle should alert you before exiting an editor or closing the window while there are unsaved changes to the item being edited. User can now choose to save changes, discard changes, or cancel the action.

- Fixed a minor bug where the "Save" button remained disabled after capturing text from Xcode. User had to manually make additional changes to the file contents to enable the save button.

- Added a new preference that allows the user to choose a Creator code to assign to new Chronicle files. By default, the creator type is set to "????", but the user can now elect to provide any 4-digit creator code. This enables Chronicle files to be opened automatically by another editor when opened via the Finder.

- Fixed a minor aesthetic bug where the windows were allowed to be moved beneath the main menu bar.

- The help content now opens in the "Help Viewer" application, rather than the user's default application for html documents. This created a problem for people who's default html application was an editor rather than a browser. Unfortunately, plugins (bundles) do not seem to use the standard methods of registering and displaying help content in the Help system, so I have been reduced to requesting that Help Viewer handle the help files like a browser. Although this seems to work under most circumstances, a dialog will alert users if an error displaying the help content occurred, and will offer the option to attempt to load it in the default html application or copy the url to the clipboard.

This is the first public beta release of the new format. This version is a pre-release of what will become version 1.0 of the Chronicle Plugin. It has a new user interface, and new supporting features such as the help files and preferences interface.

This was the original beta version, released (in haste) in early 2005 to a select group of beta testers as version 1.0. This is no longer a public version, and is not supported. This version had most of the features found in the current version, but had a different user interface.