Skip to content
This repository

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

OneTeam XMPP multi-platform client. This is a Mozilla / XUL based platform, developed mostly in Javascript and C++ XPCOM.

branch: master
chrome Fix strict warnings
components Add support for detecting screen locking event in windows
defaults Use icon roster by default
docs List of url parameters.
extension Add .gitignore files.
extensions Updated the default theme's name creator.
installer MPL license text for windows installer
platform Add support for detecting screen locking event in windows
po Revert "Merge branch 'master' of git+ssh://gitorious.process-one.net/…
src Add support for detecting screen locking event in windows
tools Fix xulapp generation broken by changes required by wxi
.gitignore Merge branch 'master' of git+ssh://gitorious.process-one.net/oneteam/…
COPYING Listed libraries and artwork
GPLv2 License
Info.plist Set CFBundleIdentifier in Info.plist
LICENSE Listed libraries and artwork
MPL1.1 License
Makefile Remove all code used by web* targets
README.txt Update README.txt file
application.ini Bump max supported firefox/xulrunner versions
build.pl WXI generator
chrome.manifest Don't show load errors when trying to load platform specific rules on…
icon.png Added the icon for xpi.
icon64.png Add 64x64 icon to extension package top dir
install.rdf Set correct version of supported ff version
oneteam.icns Make sure that windows in xulapp have icon
oneteam.ico Make sure that windows in xulapp have icon
README.txt
OneTeam
-------

OneTeam is XMPP/Jabber client useable as Firefox extension, or
standalone Xulrunner application.

Developing
----------

Source directory has structure which allows it to be used directly as
Firefox extension (by putting file named oneteam@oneteam.im containing
path to source), or with small change (uncommenting line with
toolkit.defaultChromeURI in defaults/preferences/non-build.js) as
xulrunner application.

Building packages
-----------------

Building infrastructure is writen in Perl, and requires one non-standard
module - Sub::Name.

It can be called directly by executing "perl build.pl <FLAGS>" or using
targets defined in Makefile.

Build script recognizes those flags:
  XULAPP <any value>         - use this to generate xulrunner application
  XPI <any value>            - generate firefox extension XPI package
  DMG <any value>            - generate MacOS DMG archive
  XULLRUNNER <path>          - path to xulrunner application, right now used 
                               only by DMG target
  DEBUG <any value>          - enable some additional debug infrastructure
  NOJAR <any value>          - prevent from storing files in jar archive
  UPDATE_URL <url>           - location used by firefox to looking for
                               updates to extension
  XPI_URL <url>              - location of .xpi file used in creation of
                               update.rdf file
  MAR_BASE_URL <url>         - location where .mar (xulapp update) files
                               are accessible
  MAR_UPDATE_URL <url>       - location of service handling update requests
                               for xulrunner apps
  MAR_UPDATE_CHANNEL <name>  - name of channel used in update process
  MAR_FILE <filename>        - file name pattern used for naming generated
                               .mar files

Makefile has few targets which may be used as shortcuts for calling build.pl
manually. Most usefull are 'xpi', 'xpidbg', 'xulapp' and 'xulappdbg'

Compiling C code
----------------

To do that you will need tools listed for your platfrom from
https://developer.mozilla.org/En/Developer_Guide/Build_Instructions
under 'Build Prerequisites'. Additionally you will need to have
cmake available in your system, and copy of xulrunner-sdk for your platform.

Code for compilation lives in src/components, first step you should do is
create directory somewhere which will hold build files. After that you should
call 'cmake -D XPCOM_GECKO_SDK=<path to xulrunner sdk> <path to src/components>'
and 'make' (or 'nmake' in case of windows). After successfull build calling
'make install' or 'make install/strip' will copy newly compiled libraries
into platform/ in OneTeam directory.

Something went wrong with that request. Please try again.