jogamp › general

NEWT / Windowing Toolkits?

Classic

List

Threaded

4 messages Options

JStoecker

NEWT / Windowing Toolkits?

Hi,

I was wondering if anyone could point me in a direction for learning more information about the basics of windowing toolkits and how they function. I've been writing JOGL programs for a while by adding a GLCanvas to a Java AWT Frame or Swing JFrame, but I've read there are performance issues with this?

I would like to learn how NEWT plays a role in all of this, but I feel I need a better grasp of the underlying mechanics first. This is especially true since there is no (to my knowledge) documentation for NEWT.

Thanks

Demoscene Passivist

Re: NEWT / Windowing Toolkits?

Administrator

For a basic overview of modern GUI architectures u could take a look here: http://java.sun.com/products/jfc/tsc/articles/architecture/

In the end most modern GUI system use some or all of these base concepts. Other than that threading in general is a major problem in all GUI architectures. This gives u a hint about the whole mess: http://weblogs.java.net/blog/kgh/archive/2004/10/multithreaded_t.html

Regarding NEWT I'm not aware of any complete documentation, but the API is quite similar to AWT so more or less "self-explanatory". If u are specifically looking for the performance issues with AWT and why NEWT solves this issue u should take a look here: http://jogamp.org/wiki/index.php/Jogl_FAQ#What_is_Newt.27s_Threading_Model_for_native_window_events_.3F

As far as I'm informed one of the motivations for creating a new window toolkit for JOGL was the fact that AWT is no longer developed by Sun. It's in maintenance mode since many years. Another motivation was the above mentioned locking issue wich is quite bad for performance in some environments.

Hope these infos help a little bit ...

JStoecker

Re: NEWT / Windowing Toolkits?

Thanks a lot! I will take a look at this.

Sven Gothel

Re: NEWT / Windowing Toolkits?

Administrator

In reply to this post by Demoscene Passivist

On Thursday, July 22, 2010 03:39:30 am Demoscene Passivist [via jogamp] wrote:

>
> For a basic overview of modern GUI architectures u could take a look here:
> http://java.sun.com/products/jfc/tsc/articles/architecture/
>
> In the end most modern GUI system use some or all of these base concepts.
> Other than that threading in general is a major problem in all GUI
> architectures. This gives u a hint about the whole mess:
> http://weblogs.java.net/blog/kgh/archive/2004/10/multithreaded_t.html
>
> Regarding NEWT I'm not aware of any complete documentation, but the API is
> quite similar to AWT so more or less "self-explanatory". If u are
> specifically looking for the performance issues with AWT and why NEWT solves
> this issue u should take a look here:
> http://jogamp.org/wiki/index.php/Jogl_FAQ#What_is_Newt.27s_Threading_Model_for_native_window_events_.3F
>
> As far as I'm informed one of the motivations for creating a new window
> toolkit for JOGL was the fact that AWT is no longer developed by Sun. It's
> in maintenance mode since many years. Another motivation was the above
> mentioned locking issue wich is quite bad for performance in some
> environments.

Plus we wanted to have a very simple windowing toolkit only API
which can be implemented on mobile/embedded platforms as well,
without the need of 2D graphics - which is provided by OpenGL/JOGL for example.

>
> Hope these infos help a little bit ...
>
> ______________________________________
> View message @ http://jogamp.762907.n3.nabble.com/NEWT-Windowing-Toolkits-tp985201p986673.html
> To start a new topic under jogamp, email [hidden email]
> To unsubscribe from jogamp, click http://jogamp.762907.n3.nabble.com/subscriptions/Unsubscribe.jtp?code=c2dvdGhlbEBqYXVzb2Z0LmNvbXw3NjI5MDd8MzkxNDI4MzU5
>

--
health & wealth
mailto:[hidden email] ; http://jausoft.com
land : +49 (471) 4707742 ; cell: +49 (151) 28145941
Timezone CET: PST+9, EST+6, UTC+1