Merged silc_1_0_branch to trunk.

[silc.git] / TODO

diff --git a/TODO b/TODO
index e597065a0c864ce460d4f0cd8221dd4addf81bf9..416a3cf15cc1344ccdf0f98fcf948d344ea144b8 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,15 +1,6 @@
 TODO for Irssi SILC Client 1.0
 ==============================
 
- o Signed message payload handling on UI
-
- o Support to set arbitrary pulic key in CMODE
-
- o INVITE/BAN by public key file and Client ID, new INVITE/BAN list handling
-   in command reply.
-
- o bugs parsing nicknames with @ in NICK_CHANGE
-
  o Testing - See test plan:
      http://silcnet.org/docs/silc-client-1.0-test.pdf
      http://silcnet.org/docs/silc-client-1.0-test.ps
@@ -18,19 +9,17 @@ TODO for Irssi SILC Client 1.0
 TODO for SILC Server 1.0
 ========================
 
- o Remove client from invite lists in KICKED and KILLED.
-
- o 1.2 backup router support
-
  o Testing
 
 
 TODO/bugs In SILC Libraries
 ===========================
 
- o WIN32 silc_net_create_connection_async does not work the same way
-   than on Unix.  Do it with threads on WIN32.  The function works but
-   is not actually async currently (Fix this to 0.9.x).
+ o Test cases for all cryptographic primitive in lib/silccrypt/
+
+ o Test cases for all payload encoding and decoding routins in lib/silccore/
+
+ o Test cases for math library routines in lib/silcmath/
 
 
 TODO in Toolkit Documentation
@@ -39,18 +28,11 @@ TODO in Toolkit Documentation
 Stuff that needs to be done in order to complete the Tooolkit Reference
 Manual (Do these to 0.9.x).
 
- o Document the "notify" and "command_reply" client operations variable 
-   argument lists for all possible notify types and command replys.
-
  o Write "Programming with Toolkit" document, describing how to build
    Toolkit, how the build system works, where is everything, how
    new (external) projects can be glued into Toolkit (use irssi as an
    example), and how external projects can use Toolkit without gluing into
    it (how to link etc), debugging, architecture, types, etc.
 
- o Write "Platform Implementations" document to describe what platforms
-   Toolkit support, what has been implemented, what has not been, what
-   works differently etc.
-
- o Searching of predefined keywords, exact and partial matches (would be 
+ o Searching of predefined keywords, exact and partial matches (would be
    nice).