Rev 444 | Rev 447 | Go to most recent revision | Show entire file | Regard whitespace | Details | Blame | Last modification | View Log | RSS feed
| Rev 444 | Rev 445 | ||
|---|---|---|---|
| Line 133... | Line 133... | ||
| 133 | 133 | ||
| 134 | 134 | ||
| 135 | Regarding Macintosh |
135 | Regarding Macintosh |
| 136 | ------------------- |
136 | ------------------- |
| 137 | 137 | ||
| - | 138 | * Please make a port to the latest Apple versions (and possible builds for older MacOS versions, too?) |
|
| - | 139 | ||
| 138 | * Unsure regarding AppleScript ! |
140 | * Unsure regarding AppleScript ! |
| 139 | https://developer.apple.com/library/archive/documentation/mac/pdf/Interapplication_Communication/AE_Term_Resources.pdf |
141 | https://developer.apple.com/library/archive/documentation/mac/pdf/Interapplication_Communication/AE_Term_Resources.pdf |
| 140 | 1. Do we need an 'auet' resource? |
142 | 1. Do we need an 'auet' resource? |
| 141 | 2. Does our implementation work with AppleScript? |
143 | 2. Does our implementation work with AppleScript? |
| 142 | 3. Must the human-language term REALLY be unique?! So only one plugin on the whole system may use the word "ctl(0)" or "red" or "size"??? Why do we have unique keys if the human language needs to be unique too?! (see "Important" section at page 8-14) |
144 | 3. Must the human-language term REALLY be unique?! So only one plugin on the whole system may use the word "ctl(0)" or "red" or "size"??? Why do we have unique keys if the human language needs to be unique too?! (see "Important" section at page 8-14) |