Support for SWT TrayItem

[raphael]

Just wondering if you will be adding support for the new SWT TrayItem that allows you to place icons in the system tray. It is not hard to program it by hand, but it would be easier to do it graphically. A code snippet on using the system tray with a popup menu can be found at:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-swt-home/snippits/snippet143.html

[Eric Clayberg]

Just wondering if you will be adding support for the new SWT TrayItem that allows you to place icons in the system tray. It is not hard to program it by hand, but it would be easier to do it graphically. A code snippet on using the system tray with a popup menu can be found at:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-swt-home/snippits/snippet143.html

I took a look at that snippet. It looks interesting, but I'm not sure how to handle it from Designer's point of view. It seems like a self-contained entity that does not fit into an existing window layout.

[raphael]

Yeah, I see what you mean. It is not a big deal. There are probably more important features to implement anyways. I just came across it and found it interesting.

[Hansz]

Just as a suggestion/observation ...

Coming from a Borland (Delphi) background, this is not an unfamiliar concept. In the Borland products they have what is called a 'DataModule'. A 'visual' container that works much in the same way as a normal 'window/view' editor.

It allows for dropping the so-called 'non-visual' components on. Now, at first, this doesn't seem to provide much of an advantage as many of those 'non-visual' components seem to be trivial, and could easily be coded (or stored) just as code-snippets like the one above, and just added to any piece of software by copy-paste. However... having them available as 'components', just like the visual widgets etc has 1 big advantage ... They become accessible thru the property editor, which gives it a nice touch, and makes the use of them a 'piece of cake' ... It lowers the threshold for people and also the chance of making mistakes in the process of copying them into your software, because of the drag-n-drop nature of widgets/components.

just my 2 cnts.[/img]