Skip to main content

DJ Native Swing 0.9.6 released

6 replies [Last post]
chrriis
Offline
Joined: 2003-11-17
Points: 0

DJ Native Swing allows to easily integrate some native components into Swing applications, and provides some native utilities to enhance Swing's APIs.

The main focus is the integration of a native Web Browser and Flash Player using a Swing-like API. Nevertheless, it also offers other useful components like a multimedia player (based on VLC) and an HTML editor (using FCKeditor).
All the threading issues and general integration headaches are handled automatically. It also allows to mix lightweight and heavyweight components without major visual problems.

Native Swing: http://djproject.sourceforge.net/ns
Screenshots: http://djproject.sourceforge.net/ns/screenshots
Webstart Demo: http://djproject.sourceforge.net/ns/DJNativeSwing-SWTDemo.jnlp

The Webstart demo is configured to work on Windows. It also works on Linux (GTK, x86/i386) where XULRunner is installed. Note that this demo is part of the release distribution.

It uses SWT under the hood, and thus should work everywhere SWT allows to be placed inside a Swing component. To get the web browser to work on Linux, follow the FAQ on SWT's website (XULRunner may be required).
DJ Native Swing is licensed under LGPL and requires Java 5 or later.

Note that it is a sub-project of the DJ Project ( http://djproject.sourceforge.net ), which is a set of tools and libraries to enhance the user experience of Java on the Desktop.

In this release, the library is now split into a framework library and its SWT-based implementation. This allows to re-use the Native Swing integration framework for other types of native components.

-Christopher

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
andypeters
Offline
Joined: 2008-08-30
Points: 0

> In this release, the library is now split into a
> framework library and its SWT-based implementation.
> This allows to re-use the Native Swing integration
> framework for other types of native components.

Hi Christopher,
Is it mean that I can use jcoolbar in swing without using swingwt?
Can you give a demo for this new function?

Kind Regards

Andy

chrriis
Offline
Joined: 2003-11-17
Points: 0

> Is it mean that I can use jcoolbar in swing without
> using swingwt?

The framework part allows to better integrate native components that are using an AWT component (Canvas).

The SWT-based implementation uses the Native Swing framework to offer a web browser and various components with a Swing-like API. The fact that it uses SWT is an implementation detail.
It is possible to extend the SWT-based code to have the CoolBar, but I am not sure this is desirable. Indeed, I consider native integration as a last resort, when you want a web browser or a media player for example. If something can be coded in Swing instead, I would rather do that because native integration hads some constraints.

A Swing coolbar would be a nice addition to projects like SwingX in fact.

Cheers,
-Christopher

andypeters
Offline
Joined: 2008-08-30
Points: 0

> A Swing coolbar would be a nice addition to projects
> like SwingX in fact.

I agree.I will try to code this CoolBar with pure swing.In fact there is a commercial
product named ESP Toolbar 1.5.7 .You can try it at
http://www.magi-au.com/download/index.html#esptoolbar

Of course,Netbeans ToolBar has the similar feature.
Thanks for your reply!

Best Regards

Message was edited by: andypeters

maxz1
Offline
Joined: 2006-01-10
Points: 0

Chris,

Cool API, cool DEMO! Congrats!
When are you going to have 1.x version?

-Maxim

chrriis
Offline
Joined: 2003-11-17
Points: 0

Maxim,

> Cool API, cool DEMO! Congrats!

Thanks!

> When are you going to have 1.x version?

Isn't it the trend to stay in beta forever? ;)

As long as I make some releases that still affect the API, then I prefer to stay in 0.9.x. If after several months I have no changes affecting the API, then I would consider a 1.0 version.

I think I am getting closer to a stable API though, now that the framework is separated from its SWT-based implementation.

-Christopher

maxz1
Offline
Joined: 2006-01-10
Points: 0

>Isn't it the trend to stay in beta forever? ;)
Yee, it is quite common trend indeed :)
Try to be a pioneer, make at least 1.0.1 and many
people will start to use your cool stuff. May be at least
a subset of the API... Swing community needs more
support, specially now.