polsys / ref Goto Github PK

Add UI Automation properties to all UI elements so that the UI is programmatically readable. This makes life easier for screen readers and other uses.

(I've had to programmatically control a program with no accessibility features whatsoever. It was horrible. I doubt the authors ever thought somebody would do so, and it really was a huge hack.)

Allow launching the application with a file name parameter so that the file is opened. This is a prerequisite for a file extension association.

As mentioned in #27, BibLaTeX does things very differently regarding electronic sources. The current implementation targets BibTeX. It could be useful to have a separate BibLaTeX exporter with these slight differences.

BibTeX will get annoyed by stray \ { } %, etc. in the file. A decision is needed between

• abstracting away the platform (escape the special characters), and
• giving the user more power (don't do anything).

I assume most BibTeX users fall into the latter category, but I'm still holding out the decision.

Matching the BibTeX inbook type, for parts of a book. The fields are mostly same as in books, but with page/chapter information.

Show a warning if there are missing or duplicate keys, or things that will blow up later (eg. missing title or author with BibTeX).

Copying and pasting entries within and between projects. How to handle merges? Need multiple select?

This needs some working out, because references are typically to single web pages. However it would be nice to group the site as one. The pages should therefore have a key in addition to the URL, and be exported along with some data from the site entry. I'm not sure how the current Page infrastructure will handle that.

The common shortcuts for the main toolbar, Edit/Cancel/Apply, Add Page, Add Entry. Also need to make sure the whole interface is usable with just a keyboard (tab order mostly).

Steps to reproduce:

1. Create a new thesis.
2. Commit the changes.
3. Click the Thesis kind combo box and select another option.

Expected:

• You can't open the combo box when not in edit mode.

Actual:

• You can open the combo box. The changes are not reflected in the view model, though.

Searching all fields and notes. Would probably be just a filter on the entry list.

(Sounds so simple...)

At the moment, all the strings are hard-coded. This issue has multiple parts:

• Moving the strings to resources.
• Ensuring that hyphenation etc. are localized.
• Figuring out how to localize things like exporter names without layering spaghetti.
• Making keyboard shortcuts localizable. (Linked to #11)
• Adding and maintaining at least one localized version (Finnish as my native language).

Things that should be done, but not now:

• Supporting RTL layouts.
• Supporting local variants of the fields.

Currently the Word exporter would mangle the organizational author name, and the BibTeX exporter would probably have trouble with casing. Make it possible to indicate that the author is an organization, possibly also allowing BibTeX author/shortauthor fields.

(Marking this as a feature since it requires a model change, which will affect the file format.)

This is a data binding issue - the Title property change (or Volume for that matter) is not processed because the title is bound to the entry itself through EntryTitleConverter.

Filing the issue here so that I still remember it after merging #27 - the change would conflict.

It could be useful to export as plaintext references, either the whole catalogue or single entries (maybe with a copyable popup instead of a file). It should support all the common styles.

Instead of writing notes on pages, I'd like to attach pictures. For an article it wouldn't be completely unreasonable to attach the PDF file.

The files could be stored in a subdirectory next to the project file. Of course, then there needs to be handling for broken links, existing directories, renaming and all the other fun. Sharing the project would be more complicated.

Another option would be using an archive format like ZIP for the project. This would have the advantage of compressing the textual content.

The property grid is implemented in a very manual way, and that is starting to create some pain. Investigate a better solution.

This is quite straightforward, since there are only a few applicable BibTeX fields. There should be a distinction between Master's and PhD theses, honored in the export process.

• There is some unnecessary repetition in some tests, e.g. Create[Article/Book/Thesis]_AsksIfEditing. Refactor out the common parts.
• Add a 0.1.0 test file and check that it is correctly loaded. Do the same for 0.2.0 when the feature work is completed.
• Commit an up-to-date test file for manual testing / demoing and write a checklist for manual tests.

#16 implements #5, but with several features missing.

• Implement more citation styles.
• Add some missing fields: edition, volume, translator.
• As part of the UI improvement, make sure that the dialog actually scales with font sizes. I've a hunch it only works on 100% fonts.

Investigate how Word imports references and write an exporter.

(Sounds way simpler than it probably is 😄)

Many e-libraries and journals allow exporting bibliographical data in EndNote/etc. format. It would be useful to be able to import that data directly into Ref.

Add icons to the catalogue list, so that it's easy to distinguish between entry types. Currently the only way is looking at the available properties.