Files
novelWriter/CHANGELOG.md
T
2019-05-25 20:41:05 +02:00

4.4 KiB

novelWriter ChangeLog

Version 0.1.4 [2019-05-25]

Bug Fixes

  • Fixed a bug where an item had to be selected in the tree view for a root item to be created. #16.

User Interface

  • The main area can now be split into two, with the document editor on the left and a document viewer on the right. PR #13.
  • The list of novel document status and plot element importance levels can now be edited through the Project Settings fialog. The values are per project, and saved in the main project XML file. PR #17.
  • Cleaned up opening and closing projects, as well as how new projects are created. A new project can also not be saved in a folder already containing a novelWriter project. That was previously possible. resulting in the old XML file being overwritten. PR #18.
  • Some minor GUI improvements were added, PR #19:
    • Pressing F2 also opens the edit item dialog, like Ctrl+E does.
    • When the document editor and viewer split slider is moved, the editor resizes properly.
    • The document viewer can be closed, expanding the editor to the full window size again.
    • A project can be closed with Ctrl+Shift+W, and the menu entry has an icon.
    • Exit button/menu now asks if you want to close.

Themes

  • The colours for syntax highlighting can now be edited in a config file in the themes folder. The main GUI css file also lives in the same folder. The default theme lives in the default subfolder, and more folders can be added. Switching themes involve changing the theme setting in the main config file to the name of the themes subfolder. PR #15.

Code Improvements

  • Loading the project with the items in the wrong order is possible. That is, the child item is stored before its parent. A saved file should not ever be like that, but an edited file might. Even if the file shouldn't be edited manually. PR #16.

Version 0.1.3 [2019-05-18]

User Interface

  • Cursor position is now saved when a document is saved, and restored when the document is opened. PR #12.

Test Suite

  • Major upgrades to the test suite, now also testing GUI elements. Coverage at 73%. PRs #9 and #11.

Version 0.1.2 [2019-05-12]

Bugfixes

  • Fixed a critical GUI bug when trying to create new folders and files in the tree.
  • Caught a bug when creating a new file, but novelWriter couldn't figure out what class the parent item had and returned a None. Could not recreate the bug, but added a check for it.

Code Improvements

  • Changed the way user alerts are generated, and added the alert levels to an enum class named nwAlert. Also added a new level named BUG.

Version 0.1.1 [2019-05-12]

User Interface

  • Rewritten the spell check context menu. The previous implementation was adapted from a Qt4 example, but could be improved a great deal. It now also doesn't have the default context menu, and allows for adding words to personal word list. Spell checking can also be enabled and disabled from the menu, and re-run on a the current document. PRs #1 and #3 (V.K. Berglyd Olsen)

Test Suite

  • Added a unit test framework based on pytest. This currently checks basic opening and saving of the main config file and the main project file. PR #2 (V.K. Berglyd Olsen)

Version 0.1 [2019-05-10]

This is the initial release of a working version of novelWriter, but with very limited capabilities. So far, the following has been implemented:

  • A document tree with a set of pre-defined root folders of a given sett of classes for different purposes for novel writing. That is, a root item for the novel itself, one for charcaters, plot elements, timeline, locations, objects, and a custom one.
  • A plain text editor with a simplified markdown format that allows for four levels of titles, and bold, italics and underline text.
    • In addition, the format supports comments with lines starting with a %.
    • It also allows for keyword/value sets staring with the character @. These will later be used to link documents together as tags point to other documents. For instance, a scene file can point the keyword @POV:name to a character file with the keyword @THIS:name.
  • The text editor has a set of autoreplace features:
    • Dashes are made by combining two or three hyphens.
    • Three dots are replaced with the ellipsis.
    • Straight quotes with your quote format of choice.
  • The text editor also allows for wrapping either selected text, or the word under the cursor, in:
    • Bold, italics, or underline tags.
    • Single, or double quotes.