Problem in Structure of Libjingle...

[GoogleCodeExporter]

Hi!

I'd like to ask one problem on structure of libjingle.

To be frank, It's a lot more difficult to use libjingle.

I will take an example of MUC chatting.
A part of implementation for MUC chatting is involved in "call" project but I 
am wondering why those like logging in, joining and sending message are in 
"call project".
At least those must be in libjingle.lib.

Because, when i use libjingle.lib, i shouldn't recognize complicated structure 
of call project and libjingle's structure should be as following.

for example
- login : chatmanager->login(username, pwd, onStatus);
- join  : chatmanager->getAccount()->join(room);
- send  : chatmanager->getAccount()->muc->send(addr, msg);
          chatmanager->getAccount()->send(addr, msg);
And the declaration of those above should be in libjingle.lib not in "call 
project".

What I mean is, Libjingle must be easiest lib to use which has simple interface 
so that everyone could use it simply not like "call project" (callclient.cc, 
friendinvitesendtask.cc, voicemailjidrequester.cc....)

Do i think wrong?
I really hope this project will be developed wonderful("Simple is the best 
^-^").
Thank you. 

Original issue reported on code.google.com by adam1988...@gmail.com on 12 Jan 2012 at 4:44

[GoogleCodeExporter]

It sounds like what you are saying is that we don't have a simple MUC text chat 
example, and only a audio/video call example that has a little bit of MUC chat 
in it.

That's true.  "call" is a poor example of how to do MUC chat, if that's all you 
want to do.   It would be nice to have a good example, perhaps called 
"examples/chat", that only does text chat, and does MUC chat text well.  We 
don't have any plans to make such an example app, but this is an open source 
project, so if you'd like to make such an example, please share it with us.

It also sounds like you are saying is that there is some functionality in 
examples/call which belongs in library, not in call.

That is true as well.  Almost everything you need for text chat is in xmpp/, 
which is a separate library.
But a few things in examples/login and examples/call which rightly belong in 
xmpp/.   We're slowly trying to clean things like this up.

Thanks for you interest in libjingle.  Patches are welcome :).

Original comment by pthatc...@google.com on 12 Jan 2012 at 5:53

[GoogleCodeExporter]

Original comment by pthatc...@google.com on 12 Jan 2012 at 5:55

• Changed state: WontFix