updates.

diff --git a/CHANGES b/CHANGES
index 268d704714a207bdbe38749cff03a76939c211c4..2ab7eafa0ba654c1ab4afc171c1da10ef81cea04 100644 (file)
--- a/CHANGES
+++ b/CHANGES
@@ -1,3 +1,15 @@
+Fri May 18 18:10:36 EEST 2007  Pekka Riikonen <priikone@silcnet.org>
+
+       * Fixed nickname formatting to handle already formatted nicknames
+         better.  Affected file is lib/silccilent/client_entry.c.
+
+       * Added "foo#2 appears as foo" support to SILC Client when user
+         leaves or quits and one formatted nickname remain.  Affected file 
+         is apps/irssi/src/silc/core/client_ops.c.
+
+       * Send SilcChannelEntry to application in SILC_NOTIFY_TYPE_SIGNOFF.
+         Affected file is lib/silcclient/client_notify.c.
+
 Thu May 17 18:05:10 EEST 2007  Pekka Riikonen <priikone@silcnet.org>
 
        * Fixed silc_show_public_key to not free public key in case of

diff --git a/lib/doc/notifyargs.html b/lib/doc/notifyargs.html
index 1844ceb8d5bd7b4e9f0dee53976477a4c56c9cca..d7e8209435f269df6e95035f207174a7024aef9c 100644 (file)
--- a/lib/doc/notifyargs.html
+++ b/lib/doc/notifyargs.html
@@ -113,11 +113,11 @@ Sent when someone leaves (parts) the channel.
 <td><small>SILC_NOTIFY_TYPE_SIGNOFF</td>
 <td><small>
 Sent when someone signoff the SILC network.  The 'signoff_message' may be
-NULL.  The 'leaving_client' SilcClientEntry may be incomplete and contain
-NULL pointers, application must check it's pointers before attempting to
-display for example nickname information.
+NULL.  The `signoff_client' is the client signing off.  The `channel' is
+the channel where the client was joined.  The `channel' may be NULL.
 </td>
-<td width="50%"><small>SilcClientEntry signoff_client, char *signoff_message
+<td width="50%"><small>SilcClientEntry signoff_client, char 
+*signoff_message, SilcChannelEntry channel
 </td>
 </tr>
 

diff --git a/lib/doc/platforms.html b/lib/doc/platforms.html
index e2c0341978ed87766301672ce274928003081f19..c34c500d0ecc6ceb2a42421b3afce0659c5daafe 100644 (file)
--- a/lib/doc/platforms.html
+++ b/lib/doc/platforms.html
@@ -4,22 +4,20 @@
 This document describes the implementation issues with different platforms
 that the SILC Toolkit support.  Some of the supported platforms does not
 support all the features delivered with the Toolkit or they may behave
-differently from other platforms.  This document descibres these
-differences between platforms.
+differently from other platforms.
 
 <br />&nbsp;<br />
 <li><a href="#unix">Unix & Linux Implementation</a><br />
 <li><a href="#windows">Windows Implementation</a><br />
 <li><a href="#macosx">Mac OS X Implementation</a>
-<li><a href="#symbian">Symbian Implementation</a>
+<li><a href="#symbian">Symbian OS Implementation</a>
 
 <br />&nbsp;<br />&nbsp;<br />
 <b>Supported Platforms</b>
 
 <br />&nbsp;<br />
 SILC Toolkit supports by default all Unix and Linux platforms, Windows
-platforms from Windows 98 and newer, and Mac OS X.  In the future there is
-also plans to add support for other platforms such as Symbian OS (EPOC).
+platforms from Windows 2000 and newer, Mac OS X and Symbian OS.
 
 <br />&nbsp;<br />&nbsp;<br />
 <b><a name="unix"></a>Unix Implementation</b>
@@ -34,15 +32,12 @@ implementation issues with current version of SILC Toolkit.
 <b><a name="windows"></a>Windows Implementation</b>
 
 <br />&nbsp;<br />
-By default all features and components delivered with SILC Toolkit are
-supported on Windows.  However, there are some certain issues with the
+By default all features and components delivered with SILC Toolkit are 
+supported on Windows.  However, there are some certain issues with the 
 Windows version of the SILC Toolkit.
 
 <br />&nbsp;<br />
-<li>Toolkit users should not use <tt>silc_client_run</tt> function to
-execute the Client Library.  Instead the <tt>silc_client_run_one</tt> should
-be used, for example as an timer task and the Windows application's own
-message loop should be used as the main message loop.
+<li>Some of the network routines do not support IPv6.
 
 
 <br />&nbsp;<br />&nbsp;<br />
@@ -55,19 +50,30 @@ implementation issues with current version of SILC Toolkit.
 
 
 <br />&nbsp;<br />&nbsp;<br />
-<b><a name="symbian"></a>Symbian Implementation</b>
+<b><a name="symbian"></a>Symbian OS Implementation</b>
 
 <br />&nbsp;<br />
-Symbian support in SILC Toolkit is still experimental.  By default all
-feature and components delivered with SILC Toolkit are supported on
-Symbian.  However, there are some certain issues with the Symbian version
-of the SILC Toolkit
+Symbian OS support in SILC Toolkit is still experimental.  By default all 
+features and components delivered with SILC Toolkit are supported and 
+should work on Symbian.  However, there are some issues with the Symbian 
+version of the SILC Toolkit of what Symbian developers need to be aware.
 
 <br />&nbsp;<br />
-<li>The function <tt>silc_schedule</tt> on Symbian will return immediately,
-instead of blocking the calling thread/process as on other platforms.  On
-symbian the function is equivalent to <tt>silc_schedule_one</tt>, and that
-function should be used instead.  The design of SilcSchedule on Symbian
-enables efficient data I/O even when <tt>silc_schedule_one</tt> is called
-from a timer task.  The data I/O is scheduled separately by the Symbian
-Active Scheduler and the SilcSchedule will merely schedule timeouts.
+<li>The function <tt>silc_schedule</tt> on Symbian will allocate new Active 
+Scheduler Waiter and will block the calling thread.  The caller should 
+allocate Active Scheduler before calling <tt>silc_schedule</tt>.
+
+<li>When adding timeout tasks to SILC Scheduler the SILC Scheduler is woken 
+up after the timeout task has been added.  This allows adding of the 
+timeout tasks from Symbian active objects outside the SILC Scheduler loop.  
+On other platforms this wakeup operation is not performed.
+
+<li>Adding fd task to SILC Scheduler will not schedule the fd for any 
+operation.  Instead, programmer should use SILC Socket Stream API and SILC 
+Fd Stream API on Symbian when dealing with file descriptors and sockets.  
+These APIs provide asynchronous notification when data is available and can 
+be written.
+
+<li>The function <tt>silc_thread_create</tt> on Symbian will install Active 
+Scheduler and allocate Cleanup Stack for the new thread.  The created 
+thread always shares heap with the parent thread.

diff --git a/lib/doc/porting.html b/lib/doc/porting.html
index 665357f7c73fbbca68a4c86a0aa7c3c24a7c1951..6621298a97218b160ed42009767fab230122cc8f 100644 (file)
--- a/lib/doc/porting.html
+++ b/lib/doc/porting.html
@@ -351,6 +351,7 @@ messages for Toolkit 1.1.
 <br />&nbsp;<br />
 SILC_NOTIFY_TYPE_NICK_CHANGE<br />
 SILC_NOTIFY_TYPE_CMODE_CHANGE<br />
+SILC_NOTIFY_TYPE_SIGNOFF<br />
 SILC_NOTIFY_TYPE_SERVER_SIGNOFF<br />
 
 <br />&nbsp;<br />