To view parent comment, click here.
To read all comments associated with this story, please click here.
The only reason you are losing is because you have proven you don't know what you are talking about.
It's called development libraries and APIs that people can pick up and use today - not sometime in the next few days, weeks or years, or if I write my own plugin to create my own projects. If you don't understand that then you fail miserably as a developer.
The parent was a naive and daft comment I have encountered many times that has no bearing on the real world at all:
Basically yes, because system tray does not have applets, but rather embeds windows created by another application using Xembed.....Thus a "system tray applet" is any application which has a system tray window component and Java can do those.
Errr, no self-respecting developer is going to do that when they have better ways of doing this, and better platforms to do it on. C'est la vie.
Care to explain why clarifying that system tray embedding is just a matter of using the respective system tray object is either naive or daft?
Better ways of doing it than using a standard API?
In case of Java java.awt.SystemTray, in case of Qt QSystemTrayIcon?






Member since:
2007-10-29
> Sigh..... I'm on to a losing battle trying to
> explain this one.
The only reason you are losing is because you have proven you don't know what you are talking about. I can't really say that any other way. But you'd rather just keep trying to dig yourself a deeper hole, and resort to off the cuff statements about things you know nothing about, then just admit you don't know what you are talking about.