-
Notifications
You must be signed in to change notification settings - Fork 0
/
todo.txt
77 lines (66 loc) · 4.42 KB
/
todo.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
# Todo list for NVDA Addon Team #
in the following:
bitNVDA=http://bitbucket.org/nvdaaddonteam
# outstanding #
* Major overhaul of mrconfig needed due to changes to Bitbucket Cloud that prevents new repos from being created unless a project name is given, use of GitHub and among other reasons.
* If possible, switch from Bitbucket to GitHub, with authors encouraged to maintain their own add-ons.
@Alberto: add a guide for your batch files in allrepos.txt
* Blacklisted add-ons: File Reader, causing NVDA to not exit.
* Resolve differences between add-on guidelines and review process document.
* Refactor how SCons script generates add-on documentation based on recent comments in NVDA core ticket 2694.
Pending review/action:
* StationPlaylist: Merge new messages and readme from translators.
* Goldwave: Further testing with GoldWave 6 needed.
* windows7Magnifier, config validation routine rewrite requested (NvDA core #3632).
* dropbox, checking with author for outstanding changes, otherwise ready for stable release.
* controlUsageAssistant, ?
* VirtualRevision, fix newline problem, make available for translators.
* Instant translate, Needs english language changes, make available for translators.
* systraylist, Rui fixed a bug, what was it/needs documenting?
* Tree View Navigation (for users) vs TreeSpy /(for developers)
https://ABuffEr@bitbucket.org/ABuffEr/treeviewnavigation.git
https://github.com/cromarty/nvda-treespy.git
* audibledownloadmanager, ?
https://bitbucket.org/dave090679/audibledownloadmanager
* realtek hd audio manager, ?
https://bitbucket.org/dave090679/realtek_hd_audio_manager
* trackbar_routing, ?
https://bitbucket.org/dave090679/trackbar_routing
* Balloon history, ?
http://web.radiolavila.es/download/file/fid/38
* Web Hotspots, how is this different from placeMarkers?
http://web.radiolavila.es/download/file/fid/39
* Speech mode beeps omiter, same functionality as NoBeepsSpeechMode
http://web.radiolavila.es/download/file/fid/42
* FileReader, play audio and read files without a window on a screen (blacklisted due to causing problems with NVDA core).
http://web.radiolavila.es/download/file/fid/44
* Document percentage, maybe merge with Jump to line and WordCount?
http://web.radiolavila.es/download/file/fid/45
http://web.radiolavila.es/download/file/fid/46
http://web.radiolavila.es/download/file/fid/41
* NVSettings, what are the advantages of this over the new nvda profiles? May need more code documentation, coding style updates, update to latest template, translator comments needed.
http://web.radiolavila.es/download/file/fid/51
* teamtalk, ?
* ventrilo, ?
* apolo2, ?
# To Discuss #
# Historical/notes #
* T2694: remove documentation generation routine from SCons once NVDA 2014.3 is released.
* Create an add-on development guide, which will serve as an extension of NvDA core Development Guide but designed for writing add-ons.
* Script category: use NVDA core categories if an add-on enhances the functionality of NVDA such as adding shortcuts to preferences dialogs; use add-on name if the add-on adds misc features such as system information.
* document where the prefered path of addon config files should be saved in guidelines document.
The new path allows for addons to be used while running temp copy of nvda or something like that.
* Let commit emails go to a commit list, rather than to the nvda-addons discussion mailing list.
* Idealy documentation should only be written once, and accessed both
from the web and from nvda itself.
Done thanks to addon template.
* Noelia, see Jamies last comment on #2694.
* Derek, review translatable strings for place markers.
* The add-ons mailing list has been created, and the list has been widely publisized.
* When we know the system works well for one or two addons, we should write an announcement/invitation for people to submit addons.
* Mesar, write scripts to integrate with translator workflow and the community addon website.
** When an addon is added to bitNVDA/addon-files it will automatically be available for download.
** Addon pot files are merged into po files every mon/thu, just like main nvda.po.
** po files from translators are merged back into addons at the middle and end of each month, like what we do with nvda.
** We need to check nvda/srt/website/addon/addon.mdwn and nvda/addons/{addonName}/readme.mdwn are the same by hand, potentially list new languages that have been added.
* beqa, mesar, review resource monitor and unicode-braille-input addons.