Check-in [adee355c70]

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Updated help link to online help.
Timelines: family | ancestors | trunk
Files: files | file ages | folders
SHA1: adee355c708bef83622aad205b894a31dfd2f50d
User & Date: tinus 2016-11-30 21:01:24
Context
2016-11-30
21:01
Updated help link to online help. Leaf check-in: adee355c70 user: tinus tags: trunk
2016-01-11
16:48
Comments. check-in: e1d5f80a24 user: tinus tags: trunk
Changes

Changes to todo.md.

11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
  * set up a timer to check regularly
  * respond to events within the IDE itself when chances are that something's changed.
  * also, probably observe different timeouts for different things. Getting the remote status is
    (potentially) far more costly than the status of our local work directory.
  * Add a button to do a forced refresh. Use it to indicate automatic refreshing as well
    (`Down := True; try do stuff; finally Down := False`)
  * _It might be a good idea to start with a separate button that does something threaded, to make the setup more simple. One step at a time._
* Figure out how to respond to events ([XE7 help](ms-help://embarcadero.rs_xe7/rad/Notifying_a_Wizard_of_IDE_Events.html))
  - `IOTAEditorNotifier`: Modifying or saving a source file, or switching files
    in the editor
  - `IOTAModuleNotifier`: Changing, saving, or renaming a module
  - ⇒ whenever a file changes, check the file cache and then the repo cache,
    and if we've changed repo, we should switch our buttons' displayed info to
    the appropriate repo. If that repo's info is out of date, it should be
    refreshed first.







|







11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
  * set up a timer to check regularly
  * respond to events within the IDE itself when chances are that something's changed.
  * also, probably observe different timeouts for different things. Getting the remote status is
    (potentially) far more costly than the status of our local work directory.
  * Add a button to do a forced refresh. Use it to indicate automatic refreshing as well
    (`Down := True; try do stuff; finally Down := False`)
  * _It might be a good idea to start with a separate button that does something threaded, to make the setup more simple. One step at a time._
* Figure out how to respond to events ([10.1 Berlin help](http://docwiki.embarcadero.com/RADStudio/Berlin/en/Notifying_a_Wizard_of_IDE_Events))
  - `IOTAEditorNotifier`: Modifying or saving a source file, or switching files
    in the editor
  - `IOTAModuleNotifier`: Changing, saving, or renaming a module
  - ⇒ whenever a file changes, check the file cache and then the repo cache,
    and if we've changed repo, we should switch our buttons' displayed info to
    the appropriate repo. If that repo's info is out of date, it should be
    refreshed first.