-TODO for Irssi SILC Client 1.0
-==============================
+TODO for 1.1
+============
- o Signed message payload handling on UI
+NOTE: Any item that doesn't have (***DONE) in it, isn't done yet. The
+(***TESTING NEEDED) means that the item has been done but not yet properly
+tested.
- 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
-
-
-TODO for SILC Server 1.0
-========================
-
- o 1.2 backup router support
-
- o Testing
-
-
-TODO/bugs In SILC Libraries
+apps/silcd, The SILC Server ****PARTLY DONE****
===========================
- 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).
-
-
-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 Rewrite rehash, HUP.
- 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.
+SILC Client
+===========
- 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
- nice).
+lib/silcclient, The Client Library
+==================================