Hello John, On Saturday 14 July 2007 08:31, John Drescher wrote: > Kern, > Here is an update. I am just about to have a bacula-tray-monitor.exe > app that compiles. The time consuming part so far has been finding the > common parts of the gtk tray-monitor code to use with the new win32 > code in the same way as the win32 filed, stored and dird share code > with the unix code for these daemons. > > Also, I have attached a patch that will remove the tray from the win32 > filed when run as a service. If the user runs it the tray remains.
Thanks for the patch and for the update. Since it would be a bit unkind to the user to remove the tray-monitor before we have a stand-alone replacement, I think the best thing to do with your patch is to apply it, but to put it on an #ifdef, and for the moment make it function as it does now. For the rest -- getting a stand-alone tray monitor working, yes, I can understand the problem. To simplify it a bit, I would recommend the following strategy: - You implement a stand-alone program that calls the existing tray monitor code. - Turn off the call to get the status text and the daemon status. This means that you can implement everything including putting the correct icon up (you can just use the normal icon) and putting the actual text in the window. However, the icon and window will show, which is a big step forward, in the sense that you will have a nice "skeleton" of what we need. - Once you get close to that point, let me know, and I will help you write the comm routine (actually, I am working on one for bat that can probably be used), since this should help speed up your work. - Once the program is communicating with the FD, we can think about adding a "conf" file and making it communicate with multiple daemons much like the Unix tray monitor. Anyway, that is what I would recommend, since it is a step-wise implementation, which is my preferred way of working. If you are someone who likes to design all the details top down, then you will undoubtedly want to do it somewhat differently. Thanks for your work :-) Best regards, Kern PS: After the release of 2.2.0, I will be making some substantial changes to the winservice.cpp and wintray.cpp routines. In fact, I will be rewriting the original code (I'll keep my additions) so as to eliminate the 3rd party copyright, which is causing Bacula some hassles with several big distros (Debian and Fedora). ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
