Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
clients:xwintox [2015/07/31 18:56]
sagem add history 		clients:xwintox [2015/08/03 23:57]
sagem
Line 25: Line 25:
 ===== Features ===== ===== Features =====
  
-Features that are unique to your client, or make your client stand out, should go here+XwinTox primarily differentiates itself from other clients through these features: 
 +  * Modular design, seperating the Module Manager, libToxCore communication, and GUI. 
 +  * Extensive plugin interface, allowing any level of flexibility desired, with the ability to trade this for security. 
 +  * First-class library for developing XwinTox features safely in Forth. 
 +  * Clean C++ interface for C++ plugin development, as well as for export to languages which can bind against it, like Lua. 
 +  * Simple C API for exporting the XwinTox plugin interface to other languages. 
 +  * Generic, minimal, yet comprehensive design, with an emphasis on correctness, security, and idiomatic behaviour. 
 +  * POSIX platforms as first-class citizens, with support for other platforms on a best-effort basis. 
 +  * Clean and usable GUI written with the lightweight FLTK toolkit.
  
 ===== Installation ===== ===== Installation =====
  
-Installation instructions go here+XwinTox stable builds are published on its [[https://github.com/IRIXUser/XwinTox/releases|its releases page]].
  
 ===== Usage ===== ===== Usage =====
  
-Any usage information goes here+Stable builds include a script titled `run.sh` for running XwinTox. 
 + 
 +Unstable builds, available on Jenkins, are run with ../cmrun.sh from within the `bld` folder.
  
 ===== Other clients ===== ===== Other clients =====
  
 {{page>include:clients_others}} {{page>include:clients_others}}

Trace:

Print/export