[sip-comm-dev] Extending Sip-Communicator for a personal project


#1

Hi,

I am a new user and I initially need to change the GUI and add code to access a db and send some XML code to peers on a network. I am an observer and don't plan to work on the core code.

I have the code already worked out but don't yet understand what the proper Sip-Communicator coding approach is. For instance, I assumed that I would create additional SIP message handlers to handle my XML messages.

If I was modifying the impl code I would find where the message handlers are loaded and add my new ones. But I don't believe this is the correct approach.

Do I need to work in bundles? Use Sip-Communicator as a bunch of jar files? Create a branch?

For the GUI, I found the menu button example, but I would like to build the GUI from the JFrame myself only including core components.

thanks, Kim

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hey Kim,

Basically it all depends on what it is that you need exactly. Plugins
would be fine if your part of the UI would be implemented in separate
frames and dialogs and you only need to add access buttons/menus in the
existing interface.

Plugins can also handle incoming messages and send outgoing without
having to modify existing code.

If you absolutely need to modify existing UI then you'd probably have to
change code in impl which is far less convenient because modified code
would very easily go out of sync with the mainstream sip communicator.

Cheers
Emil

Kim Michael Fairchild написа:

···

Hi,

I am a new user and I initially need to change the GUI and add code to
access a db and send some XML code to peers on a network. I am an
observer and don't plan to work on the core code.

I have the code already worked out but don't yet understand what the
proper Sip-Communicator coding approach is. For instance, I assumed that
I would create additional SIP message handlers to handle my XML messages.

If I was modifying the impl code I would find where the message handlers
are loaded and add my new ones. But I don't believe this is the correct
approach.

Do I need to work in bundles? Use Sip-Communicator as a bunch of jar
files? Create a branch?

For the GUI, I found the menu button example, but I would like to build
the GUI from the JFrame myself only including core components.

thanks, Kim

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Emil Ivov wrote:

Thank you for answering a newbie question. I figured this out myself now and am using a plug-in that adds a tab to the existing GUI. Adapting my code to your structure was a good experience and I think it has made my code much more stable in the process.

I did have an odd problem that I couldn't figure out. I wanted to return a JPanel from a bundle to the GUI plugin and just couldn't get it to work. Moving the same code to the plug-in worked. I have it in the plug-in now but am still curious why that won't work.

Speaking as a new user, I found the tutorial to be excellent. It shows the basic steps needed to integrate with SC. What seems to be lacking is any code samples for doing anything with the protocols. Certainly all the code is there to search but even for very experienced programmers the learning curve is really steep. It seems it would be nice to collect some samples that do things like "make a call", "modify the protocols used", "record calls", etc. Is there any other place besides here, the code, the tutorials, and the IRC where I can find such additional documents?

BTW, please email me if you get the debugger running again in Netbeans, a really useful feature (I am debugging in emacs again!).

thanks, Kim

···

Hey Kim,

Basically it all depends on what it is that you need exactly. Plugins
would be fine if your part of the UI would be implemented in separate
frames and dialogs and you only need to add access buttons/menus in the
existing interface.

Plugins can also handle incoming messages and send outgoing without
having to modify existing code.

If you absolutely need to modify existing UI then you'd probably have to
change code in impl which is far less convenient because modified code
would very easily go out of sync with the mainstream sip communicator.

Cheers
Emil

Kim Michael Fairchild написа:
  

Hi,

I am a new user and I initially need to change the GUI and add code to access a db and send some XML code to peers on a network. I am an observer and don't plan to work on the core code.

I have the code already worked out but don't yet understand what the proper Sip-Communicator coding approach is. For instance, I assumed that I would create additional SIP message handlers to handle my XML messages.

If I was modifying the impl code I would find where the message handlers are loaded and add my new ones. But I don't believe this is the correct approach.

Do I need to work in bundles? Use Sip-Communicator as a bunch of jar files? Create a branch?

For the GUI, I found the menu button example, but I would like to build the GUI from the JFrame myself only including core components.

thanks, Kim

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: users-help@sip-communicator.dev.java.net