view src/protocols/jabber/README.libxode @ 4359:5fb47ec9bfe4

[gaim-migrate @ 4625] Wow, okay, where to begin with this one ;) I rewrote the whole conversation backend. It is now core/UI split. Here's how it works.. Every conversation is represented by a gaim_conversation structure. This branches out into gaim_im and gaim_chat structures. Every conversation lives in (well, normally, but it doesn't have to) a gaim_window structure. This is a _CORE_ representation of a window. There can be multiple gaim_window structures around. The gaim_window and gaim_conversation structures have UI-specific operation structures associated with them. At the moment, the only UI is GTK+, and this will be for some time. Don't start thinking you can write a QT UI now. It's just not going to happen. Everything that is done on a conversation is done through the core API. This API does core processing and then calls the UI operations for the rendering and anything else. Now, what does this give the user? - Multiple windows. - Multiple tabs per window. - Draggable tabs. - Send As menu is moved to the menubar. - Menubar for chats. - Some very cool stuff in the future, like replacing, say, IRC chat windows with an X-Chat interface, or whatever. - Later on, customizable window/conversation positioning. For developers: - Fully documented API - Core/UI split - Variable checking and mostly sane handling of incorrect variables. - Logical structure to conversations, both core and UI. - Some very cool stuff in the future, like replacing, say, IRC chat windows with an X-Chat interface, or whatever. - Later on, customizable window/conversation positioning. - Oh yeah, and the beginning of a stock icon system. Now, there are things that aren't there yet. You will see tabs even if you have them turned off. This will be fixed in time. Also, the preferences will change to work with the new structure. I'm starting school in 2 days, so it may not be done immediately, but hopefully in the next week. Enjoy! committer: Tailor Script <[e-mail]>

  libxode README
  Jabber Documentation Team
  March 27, 2000
  ____________________________________________________________

  Table of Contents


  1. Introduction

     1.1 General
     1.2 What This Package Is

  2. Getting Things Installed

     2.1 Dependencies
     2.2 Compilation and Installation
     2.3 Problems/Bugs

  3. Jabber Information

     3.1 General Information
     3.2 Developer Information
  ______________________________________________________________________

  1.  Introduction

  1.1.  General

  This document gives pointers for information on this package as well
  as links to learn more about the Jabber project and about
  participating in the project.

  Copyright information can be found in each package directory in the
  files "COPYRIGHT" and "COPYING."

  1.2.  What libxode is

  libxode provides a library of XML, memory, and string helper functions.

  Jabber server software uses libxode extensively.


  2.  Getting it Installed

  2.1.  Dependencies

  Apart from the standard UNIX fare, this package isn't dependent on
  anything.

  2.2.  Compilation and Installation

  To install as super user do the following in the libxode root directory:

  ______________________________________________________________________
  ./configure
  make
  (become root)
  make install
  ldconfig
  ______________________________________________________________________

  2.3.  Problems/Bugs
 
  Submit bug reports at http://bugs.jabber.org.
 
  For additional real-time support, many members of the development team
  frequent jabber groupchat in [e-mail] and irc at
  irc.openprojects.net in #jabber.
 

  3.  Jabber Information

  3.1.  General Information

  For general information about Jabber, including a quick introduction
  to Jabber concepts, see the FAQ at http://docs.jabber.org/.

  3.2.  Developer Information

  There are many areas of Jabber that developers can contribute to.
  Jabber encompasses many fields of expertise and anyone that is willing
  to help can contribute.

  You may want to delve into the internals of the Jabber project at
  http://docs.jabber.org/ and http://protocol.jabber.org/.

  Or maybe you would like to go ahead become a developer on the project.
  Just go on over to http://jabber.org/ and register.  You may also
  sign up for the main Jabber mailing list (JDEV).