1.i hope that the ui doesn't occupy more memory and more file size.
2.the ui will be easy to extend
3.the ui is Pluggable, like to apple apps store,google apps store etc.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The three most important constraints that we had to keep in mind when designing Jitsi (at the time called SIP Communicator) were multi-protocol support, cross-platform operation, and developer-friendliness. http://www.aosabook.org/en/jitsi.html
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1.In order to add a bundle to the Jitsi build process, you need to edit the build.xml file in the root directory of the project
2.Now the only thing that we need to do is to make Felix load it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
1.i hope that the ui doesn't occupy more memory and more file size.
2.the ui will be easy to extend
3.the ui is Pluggable, like to apple apps store,google apps store etc.
The three most important constraints that we had to keep in mind when designing Jitsi (at the time called SIP Communicator) were multi-protocol support, cross-platform operation, and developer-friendliness.
http://www.aosabook.org/en/jitsi.html
An OSGi bundle is little more than a regular JAR file like the ones used to distribute Java libraries and applications.
All services and implementations in Jitsi are separated under these two packages
The BundleContext gives bundles a way to connect to the OSGi environment
1.In order to add a bundle to the Jitsi build process, you need to edit the build.xml file in the root directory of the project
2.Now the only thing that we need to do is to make Felix load it.
Plugins in Jitsi often need to be able to interact with the user.
This means they have to open, close, move or add components to existing windows and panels in the user interface
Last edit: x x x 2012-06-20