Skip to main content

SwingLabs-Demos: which LAF to default to?

11 replies [Last post]
kleopatra
Offline
Joined: 2003-06-11

Right it defaults to system which isn't the most pretty but all others I can think of are even worse

- Metal (aka: basic) is the only one completely supported by all SwingX but looks ... ehem ...
- Nimbus is the core-default-to-be but - besides not completely supported by SwingX - so ill-behaved (the child who never cleans up behind itself ;-) that it is not usable in a demo where switching between lafs is part of the demo
- Substance looks cool, but doesn't support SwingX fully plus is incompatible with some SwingX goodies
- JGoodies looks is completely SwingX unaware, and no effort from any side to change that - so the overall look isn't pleasant (btw, should we remove it from the options?)

Opinions, please?

Thanks
Jeanette

Reply viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
kschaefe
Offline
Joined: 2006-06-08

Jeanette,

We should default to system.

Karl

kleopatra
Offline
Joined: 2003-06-11

> We should default to system.

seems to be a unanimous preference :-)

So be it, thanks everybody
Jeanette

kirillcool
Offline
Joined: 2004-11-17

> - Substance looks cool, but doesn't support SwingX
> fully plus is incompatible with some SwingX goodies

There are two issues that i am aware of as far as Substance support is concerned:

1. Issue 601 on SwingX [1] that prevents Substance from installing custom renderers on trees and tree tables.
2. No custom UI delegate for JXList.

The first issue has been known to SwingX team for more than two years. The second issue has come to my attention in the last couple of months, and is pending while the work on 6.0dev core is done.

If there are any other functional / visual issues or enhancements, let me know. Oh, and don't forget about Synthetica.

Thanks
Kirill

[1] https://swingx.dev.java.net/issues/show_bug.cgi?id=601

kleopatra
Offline
Joined: 2003-06-11

> 1. Issue 601 on SwingX [1] that prevents Substance
> from installing custom renderers on trees and tree
> tables.

sure, but besides that's not even consistently supported in core (we talked about it) that's a no-nothing-easy to do in SwingX - clashing culture. It got worse with current Substance buries its niceties so deep inside the ui and forces clients to pull in substance api ;-)

> The first issue has been known to SwingX team for
> more than two years.

true - we agreed on waiting for Substance community (or you ) to come up with a reasonable suggestion for a solution.

Thanks
Jeanette

kirillcool
Offline
Joined: 2004-11-17

> true - we agreed on waiting for Substance community
> (or you ) to come up with a reasonable suggestion
> for a solution.

I guess we had different impressions from our exchange. As i have stated a number of times, i doesn't really matter to me what type of API is provided by SwingX, as long as it allows third-party look-and-feels such as Substance to plug in their own animation / highlight visuals. Looking for such a solution is unfortunately beyond what i can devote to supporting the SwingX project.

Thanks
Kirill

kleopatra
Offline
Joined: 2003-06-11

split-off a dedicated thread for the rendering stuff

http://forums.java.net/jive/thread.jspa?threadID=69868

Eager for feedback!
Jeanette

luciobiondi
Offline
Joined: 2006-12-21

Jeanette,

At least on Linux, in my opinion, you should go with GTK. I'm using it right now with SwingX in a demo I'm working on and It seems quite good, even without special customizations. Among other things you would not even need to add additional jars.

Furthermore, the JXTaskPane, which is the driving element in your demo, looks pretty cool.

Just my 2c, of course. :-)

Lucio

kleopatra
Offline
Joined: 2003-06-11

Lucio,

> At least on Linux, in my opinion, you should go with
> GTK.

not familiar with Linux, so a maybe a question with an obvious answer: is that what systemLAF would come up with?

> I'm using it right now with SwingX in a demo I'm
> working on and It seems quite good, even without
> special customizations. Among other things you would
> not even need to add additional jars.
>

just to clarify: I'm talking about the SwingLabs-Demos, not SwingX, so additional jars or not is not a big deal IMO.

> Furthermore, the JXTaskPane, which is the driving
> element in your demo, looks pretty cool.
>

glad it does :-)

> Just my 2c, of course. :-)

always welcome!

Jeanette

luciobiondi
Offline
Joined: 2006-12-21

> not familiar with Linux, so a maybe a question with an obvious answer: is that what systemLAF would come up with?

You got it, Metal.... really, really ugly :-(

> just to clarify: I'm talking about the SwingLabs-Demos, not SwingX, so additional jars or not is not a big deal

Yes, provided that the demo is running on your Desktop and not coming along the wire as an applet ;-)
However you're right, not a big deal, indeed.

Lucio

noelopan
Offline
Joined: 2008-07-01

Stick to system I would think. But you're right, we need Kirill on the Sun LAF team :)

Is Substance support incomplete even with the swingx plugin?

kleopatra
Offline
Joined: 2003-06-11

> Stick to system I would think.

current state - not overly happy with it, but maybe really the best we can do right now

> But you're right, we
> need Kirill on the Sun LAF team :)
>

better not - he probably would be slaved into FX

> Is Substance support incomplete even with the swingx
> plugin?

yeah, doesn't support JXList and restricted the ui-provided effects (which always clashed with SwingX renderer/highlighter anyway) to subclasses of substance api in the 6dev version.

Thanks
Jeanette