GpgFrontend/gpgme
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update some entries.

Browse Source
This commit is contained in:
Marcus Brinkmann 2004-09-28 23:25:35 +00:00
parent cc769c66ed
commit b6852571b3
1 changed files with 1 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
TODO
View File

@ -8,10 +8,7 @@ Hey Emacs, this is -*- outline -*- mode!
* ABI's to break:
** I/O and User Data could be made extensible. But this can be done
without breaking the ABI hopefully.
** gpgme_keylist_mode_t should not be an enum. Maybe some other values
should also not be an enum. All enums that should be enums need to
have a maximum value to ensure a certain minimum width for
extensibility.
* All enums that should be enums need to have a maximum value to ensure a certain minimum width for extensibility.
** Compatibility interfaces that can be removed in future versions:
*** ath compatibility modules.
*** gpgme_data_new_from_filepart
@ -46,13 +43,6 @@ Hey Emacs, this is -*- outline -*- mode!
** --learn-code support
This might be integrated with import. we still need to work out how
to learn a card when gpg and gpgsm have support for smartcards.
** How to terminate a pending operation? Something like gpgme_op_reset,
but where are you allowed to call it (think callback handlers).
Then gpgme_op_*list_end can go. Update: The only place where this
can go is returning errors from callback handlers, and a function
to be called for example from the user event loop code. The user
must observe the threading rules! A blocking thread can not be
cancelled.
** Might need a stat() for data objects and use it for length param to gpg.
** Allow to export secret keys.
** Implement support for photo ids.