 |
JDIC Features in Mustang
Posted by georgez on April 24, 2005 at 09:58 PM | Comments (10)
JDIC (JDesktop Integration Components) project incubates many useful desktop features. In the recent months, we have been working closely with the J2SE team to incorporate some of the exciting features from JDIC into the next J2SE
release (J2SE 6.0, code named Mustang). Check out
the JDIC Inclusion Into J2SE section of my blog Where's JDIC Going?
for a briefing of JDIC's feature inclusion into J2SE.
Both the Tray Icon API (org.jdesktop.jdic.tray.*) and Desktop
component
(org.jdesktop.jdic.desktop.*) will be included in
Mustang. These two sets of APIs will be added under the java.awt package. Here are more details:
- Feature: API to add a Java application to a system's app-launching
panel/toolbar
Bug ID: 4310333.
This feature started as the JDIC Tray Icon
API.
The main functionality of these features in J2SE will be similar to the one in JDIC, although the APIs in these features will be reviewed and revised to ensure they fit nicely with the rest of the J2SE APIs.
The feature inclusion shows the potential reward in contributing to the JDIC project: if you work on a useful desktop feature within JDIC, one day it may be included in every copy of J2SE!
Questions & Answers
Q: Will you remove those packages from JDIC after the inclusion in
Mustang?
A: We won't do that in the near future. Since there will still be a lot of people using
J2SE 1.4 or 1.5, we'll keep them within JDIC, but mention their availability in
Mustang and suggest a migration.
Q: If you keep them in JDIC, how will you maintain the code?
A: Afterwards, these features in JDIC will be in maintenance mode.
Q: Where should I report bugs after the Mustang inclusion, J2SE or
JDIC?
A: It depends on where you find the bug. Raise it to J2SE through the
"normal" bug database if it happens to J2SE, and to JDIC if you are
using JDIC releases. If a bug reported to JDIC also happens to J2SE, we'll
report it to J2SE as well.
Q: What other JDIC components will be included in later J2SE releases after Mustang?
A: As the next step, we are working closely with the J2SE team to incorporate
the JDIC
Browser component (package org.jdesktop.jdic.browser) into a future release of J2SE after Mustang.
Bookmark blog post:  del.icio.us  Digg  DZone  Furl  Reddit
Comments
Comments are listed in date ascending order (oldest first) | Post Comment
-
nice job.
just a few quick ones:
In MS Windows, the behaviour when clicking on a tray icon seems to differ a bit with various programs: a single right mousebutton-click usually opens the popupmenu. a single left mousebutton-click can open a different popupmenu (like the "Safely Remove Hardware" icon in Windows XP), or show the main program frame. A double click usually shows the main frame.
A common scenario is that a frame can be minimized to the tray (adding the trayicon to the systemtray). A double click on the trayicon shows the frame again, and usually removes the tray icon.
In other words: all this could be supported by TrayIcon by allowing to add a MouseListener to it. The programmer can then decide what the various mouse events will do.
Just throwing in some ideas here so the TrayIcon api will have maximum flexibility :)
Thomas
Posted by: tlund_ on April 25, 2005 at 07:18 AM
-
And will these methods from (https://jdic.dev.java.net/issues/show_bug.cgi?id=188) be added to the rewritten API?
java.lang.String getCaption();
javax.swing.Icon getIcon();
boolean isIconAutoSize();
javax.swing.JPopupMenu getPopupMenu();
java.lang.String getToolTipText();
Posted by: tlund_ on April 25, 2005 at 07:28 AM
-
Can we alter the java/javaw default process priority yet?
http://www.javadesktop.org/forums/thread.jspa?threadID=11113&tstart=0
100% cpu usage is another pattern I see all too often from Java applications, and its seemly difficult to control this important integration aspect by code alone.
Posted by: osbald on April 25, 2005 at 07:40 AM
-
With respect to the JDIC browser component, I remember reading something about Mustang improving the mixture of lightweight and heavyweight components. Could you elaborate on that in another post, please? I wrote a netbeans tutorial (http://www.netbeans.org/kb/articles/feedreader-tutorial.html) that uses the JDIC browser component, and was forced to open the browser in a separate frame (and I tried all kinds of hacks to make it work as a TopComponent within netbeans).
Posted by: richunger on April 25, 2005 at 10:43 AM
-
Hi, tlund: The tray icon feature spec was finalized by the J2SE team, which is tracked by this bug:
http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4310333
I think the API and code in JDIC will be in maintainance mode, so we won't do that for now. I'd suggest you add those requests to the above bug. This feature was actually proposed and finalized by some J2SE members.
Posted by: georgez on April 25, 2005 at 08:24 PM
-
Hi osbald: I gave my comments and would like to continue the discussion in JDIC forum.
Posted by: georgez on April 25, 2005 at 08:25 PM
-
Hi richunger: I'm talking with the J2SE team for more information on the improving of the mixture of lightweight and heavyweight components, will give you update.
Posted by: georgez on April 25, 2005 at 08:26 PM
-
I found this feature:
"Feature: Allow mixing of heavy and lightweight components"
in below article:
http://java.sun.com/developer/technicalArticles/J2SE/Desktop/mustang/index.html
address the mixture of lightweight and heavyweight components.
Posted by: georgez on May 18, 2005 at 07:49 PM
-
Seems a year has passed by and was wondering what the status is on integration of JDIC into Mustang. Specifically the WebBrowser functionality.
Thanks,
-Tony
Posted by: tdanecito on May 02, 2006 at 10:33 PM
|
java.net RSS Feeds
