Firebreath how to know if my method is called without debugging

I am using Objective-C++ in my firebreath project. The problem is that I am using Xcode 4 and I can not find the way to debug my project. So I have thought about if my method is been called from the web page. Here is my source code: In my OpenOnDesktopPluginAPI.h class:

class OpenOnDesktopPluginAPI : public FB::JSAPIAuto
{
    public:
    OpenOnDesktopPluginAPI(const OpenOnDesktopPluginPtr& plugin, const FB::BrowserHostPtr& host);
    virtual ~OpenOnDesktopPluginAPI();
    OpenOnDesktopPluginPtr getPlugin();
  开发者_运维技巧 ...
   //This is my method 
   void runNotification();
   ...
};

In my OpenOnDesktopPluginAPI.mm class:

OpenOnDesktopPluginAPI::OpenOnDesktopPluginAPI(const OpenOnDesktopPluginPtr& plugin,     const FB::BrowserHostPtr& host) : m_plugin(plugin), m_host(host)
{
    ...
    //Register my method
    registerMethod("runNotification",  make_method(this, &OpenOnDesktopPluginAPI::runNotification));
    ...
}

//DistributedNotification class is my objective-c class with the implementation for post a distributed notification.

void OpenOnDesktopPluginAPI::runNotification()
{
     DistributedNotification * notificationClass = [[DistributedNotification alloc] init]; 
    [notificationClass postNotification];
    [notificationClass release];
}

In my FBControl.html: ... function myFunction() { plugin().runNotification(); } ... My new method

...

I put my DistributedNotification.mm class in the

 Build Phases -> "Compile Sources"

for my plugin target. But I don´t know if my runNotification method is called, because when (In my web page) I click on My new method link, nothing happens.

---

I'll repeat what I said on the forum when you ask; perhaps you haven't seen that answer yet:

First of all, you can debug with Xcode4, at least on some browsers; the trick is figuring out which process to connect to.

Secondly, you can always use NSLog to log things to the console. Thirdly, you could use log4cplus (see http://www.firebreath.org/display/documentation/Logging).

Finally, you haven't specified what browser you're testing on, nor have you indicated what happens. It looks reasonable, but aparently doesn't work? What doesn't work? What does it do?

It's nearly impossible to give you any useful advice without detailed information about what you are encountering.