> about a weeks worth of work to finish up the changes, before I can =
> to test it. It looks like I'll have to rework a lot of the code to get =
> the right framework. I am taking steps to be able to reuse as much of =
> existing code as I can, but changing from a C to C++ framework is =
> time. So far I have a handle on where stuff needs to go and the plugin =
> little that I have done) is compiling and does register with mozilla =
> does see the methods, although nothing is working yet.=20
some code gets called. From that one it's simple to get everything =
> The code is being really moved around and reorganized to make this =
work. So it=20
> is going to be slower than I hoped, but it will get done. Mainly =
> want to see this work.
This is important on some sites. I know many radio sites where =
without any kind of control.
> The code that I thought would work didn't and so I dug into the =
> SDK and mozilla tree and kinda figured it out. The good thing so far =
> you won't have to have the mozilla tree to compile this code. You'll =
> need the mozilla-devel package installed. I am taking all the steps =
> can to make sure that this code will compile with just the =
> package installed and no other SDK's or source tree's will be =
Can you compile and sucessfully run any of the samples? I coulndn't. =
That one you told me did not work. I don't know if I linked it right. If =
you have any simple scriptable plugin working, can you send me?
I have done some typecasts corrections on support.c and on other sources =
to make it compile against g++-3.2. If you want I can send you a patch =
that compiles against g++-3.2 or g++-2.95.
If you want any help on this just let me know.=20