Hi, > Ah, so a wtk.Window "runs inside" a wtk.Display, which represents an > awt.Frame or awt.Dialog (in the desktop case).... I see. > > I've read the links you provided. I personally think that > DesktopApplicationContext.createDisplay() is slightly inconvenient because: > 1) It's based on a DesktopApplicationContext.HostDialog, which extends > awt.Dialog, which, as somebody else already mentioned in 2010 does not have > minimize/maximize buttons etc. Instead there should be a version that is > based on an awt.Frame. > 2) You still need to manually create an awt.Frame/Dialog first to have > createDisplay() create, on top of that, another awt.Dialog... > ok, but has been developed in this way since the beginning (by Greg), and at that time probably it was more targeted on Applets and on a Swing-like mode than what is required today.
> There's also some considerations about splash screens and fullscreen mode > that I haven't looked at yet. we have both splash screen and full-screen mode, and both works good, but I agree that could be more complex than required ... > Yeah, I had a look at that. Seems a little bit of a kludge to me to be > honest. If I understand the proposed feature correctly, this is really about > being able to present a dialog to the user which can be placed outside of > the wtk.Display. But from the screenshot it still looks like the full > rendering of the decorations is done by Pivot, which makes sense in a > Browser Context, but not so much in a Desktop context. > ok, if you have some proposal, we could try to improve and integrate it, I'm not against ... but of course we have to keep the same functionality for Applets and Desktop applications, which is not-so-trivial. > Oh, I wasn't expecting groovy-specific suggestions :) I'm mainly looking for > suggestions on: > (1) how to avoid any calls to Class.forName() anywhere we have an existing jira issue to simplify/improve it for our next major release (2.1) ... and not that this will be major in the sense that some (but not-so-much) features could be a little not-so-compatible, or better, it there is something in our API to change for mid-term, we can do it, but NOT before (or NOT in the 2.0.x timeframe). If I remember well, should be possible to pass a Classloader to our classes, useful in some situations ... > (2) how to create top-level windows/dialogs/alerts/etc that have a behavior > that is familiar to desktop GUI programmers, eg more in the line of how > awt.Frame/Dialog behave. ok, suggestions (and prototype code) are welcome :-) ... > I suspect that (1) would require extensions to the DesktopApplicationContext > class. For (2), that would basically mean that whenever a wtk.Dialog/Window > is opened, a n native awt.Dialog/Frame is created which is then used as the > Display for the wtk.Display/Window. All controlled by some configuration > option of course so as not to break backwards compatibility. this wouls be great. If you want, add some things in one (or more) jira issue, so we can track all them for 2.1. > Oh, that's really not necessary at this point :) ok, it's up to you, is/when you want tell me, don't worry. Anyway, if you need some info tell to us ... I hope you can continue to develop using Pivot. Bye, Sandro
