While doing this I realized some new listener and other code needs to
be added in the other clases as well.
The listener classes to be added are not in spellcheck package but to
the "net.java.sip.communicator.service.gui.event" example
"NewChatListener" and some to Core GUI classes need to be changed to
This seems to be a good working approach but then I finally I stumbled
on the class "net.java.sip.communicator.impl.gui.main.chat.ChatWindowManager".
The design of this class is different in the trunk branch.
The constructor is default which in the spellcheck version took a
"net.java.sip.communicator.impl.gui.main.MainFrame" as an argument.
Now there is a default constrcutor.
Actually what bothers me is the design of the Application, which might
have changed. The way it renders its core GUI frame. And that got me
thinking about the approach.
Just making a constructor for
taking a MainFrame and get it to successfully compile wont solve the
Some other changes are there in the class. The spellchecker verison
contains a "Hashtable <Object, ChatPanel> chats" declaration and some
"get" method code which needs to be there for the other class
depending on it to compile.
Thats what I think. Maybe I need to understand what and why the
changes have achieved. I was wondering about the correctness of
I am working to understand how SIP core GUI implementation classes
work. I think it will be really important job to do to work further
Thanks to Yana for answering my doubts. Cheers!!