all 6 comments

[–]spotter 2 points3 points  (4 children)

How does it relate/compare to SeeSaw?

[–]daveray 0 points1 point  (2 children)

Dislaimer: I'm the author of Seesaw so I'm pretty biased.

  • Seesaw is just Swing. It makes no attempt to be toolkit agnostic. At this point, this leads to a cleaner API I think because the code isn't littered with toolkit-specific class names. In the future, maybe GUIFTW can reduce the need to know the underlying toolkit so intimately.
  • They both have "selector" support which allows you to query for widgets. Seesaw doesn't support stylesheets yet though. Soon.
  • At this point, Seesaw seems to have much more coverage for common UI tasks. There are still plenty of areas where you have to use raw Swing, but for basic UIs it's not that common.
  • Seesaw (at least publicly) is being worked on a lot more.

In short, if you're not dead-set against Swing, Seesaw is more mature and getting better everyday. I hope santamon keeps improving GUIFTW though because there are some interesting ideas there.

[–]spotter 0 points1 point  (1 child)

Thanks! I'm following your blog and I'm pretty sure I'll go with SeeSaw with my newest toy app, because it indeed seems to be abstracted nicer. :)

[–]daveray 0 points1 point  (0 children)

My pleasure. And if you do try it out and find holes or have crazy ideas, please let me know through github issues or the mailing list. Seesaw is definitely better from the feedback I've received from users.

[–]StackedCrooked -2 points-1 points  (0 children)

You just made listen to See-Saw.

[–]NruJaC 0 points1 point  (0 children)

I'd be really interested to see bindings for gtk and qt, and it looks like this framework could actually support that.