Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Last revision Both sides next revision
clients:xwintox [2015/08/03 23:57]
sagem 		clients:xwintox [2015/08/31 04:02]
sagem update
Line 1: Line 1:
 ======XwinTox====== ======XwinTox======
  
-**XwinTox** is an experimental Tox client, developed by [[https://github.com/IRIXUser|IRIXuser]]+**XwinTox** is an experimental Tox client, developed by [[https://github.com/JX7P|Sagem]]
  
-| Repository: | https://github.com/IRIXUser/XwinTox |+| Repository: | https://github.com/JX7P/XwinTox |
 | Maintainers: | [[wiki:user:sagem]] | | Maintainers: | [[wiki:user:sagem]] |
 | Language: | C, C++, Forth | | Language: | C, C++, Forth |
Line 15: Line 15:
 Later, Tox developers began discussing the necessity of a 'synchronisation' model for maintaining (at a minimum) one's contact list across several installations of Tox. IRIXuser prepared a whitepaper detailing one possible solution: a server which would act as a proxy to Tox, so to speak, multiple clients accessing it at separate times or even in parallel while the server facilitated their sharing of a single contacts list and connection model.  Later, Tox developers began discussing the necessity of a 'synchronisation' model for maintaining (at a minimum) one's contact list across several installations of Tox. IRIXuser prepared a whitepaper detailing one possible solution: a server which would act as a proxy to Tox, so to speak, multiple clients accessing it at separate times or even in parallel while the server facilitated their sharing of a single contacts list and connection model. 
  
-A year later, in 2015, IRIXuser began work to realise the design which the whitepaper had put forward. Development began on the 9th of June with the laying of groundwork for the unique process mode, where libToxCore communicaton was in a process other than that which hosted the GUI, and where SunRPC served as the method of the intercommunication between the two processes. +A year later, in 2015, Sagem began work to realise the design which the whitepaper had put forward. Development began on the 9th of June with the laying of groundwork for the unique process mode, where libToxCore communicaton was in a process other than that which hosted the GUI, and where SunRPC served as the method of the intercommunication between the two processes. 
  
 Just one week on from the project's inception, it became possible to send and receive messages and to send friend requests. On the 20th of June, XwinTox DR1 was released; a day later, DR2 was released, which added groupchat support. Just one week on from the project's inception, it became possible to send and receive messages and to send friend requests. On the 20th of June, XwinTox DR1 was released; a day later, DR2 was released, which added groupchat support.
Line 34: Line 34:
   * POSIX platforms as first-class citizens, with support for other platforms on a best-effort basis.   * 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.   * Clean and usable GUI written with the lightweight FLTK toolkit.
 +
 +These unique features aside, it offers support for standard Tox operations - chat, file-transfer, avatars, group-chats, and so on.
  
 ===== Installation ===== ===== Installation =====

Trace:

Print/export