Opinions Please

Hi there,

I have an application that, among other things, allows for image sharing between clients on a virtual whiteboard. I have added functionality that allows the user to transfer a screenshot of their desktop to other clients. The main problem is that the board that displays the images isn't big enough to show the whole image by default, and scrolling to see an image is something that I would like to avoid as much as possible.

I am therefore introducing a more fullscreen mode that the user can choose to switch to and from. In this fullscreen mode most of the GUI components will be taken off the screen, only the most vital will be displayed at a tiny bar along the bottom; the rest of the users screen, 90% of it, will be comprised of the board to view the large screenshots. A client, by pressing a button, can switch to a mode optimized mode for viewing larger images (like screenshots). They can then switch back to normal screen mode, where they can perform more features, when they are done.

Im trying to think of the best way to do this; right now I am using a horribly inefficient method of always creating a second JFrame with many duplicate components of the main JFrame and just leaving it invisible until they switch to fullscreen mode. Ideally I would like to have a way to tell all of the components on the screen to grow/hide/move when the user switches modes in order to avoid having all of these duplicate components on a seperate JFrame, eating up additional memory. But I am using a GUI builder that uses a complicated layout and it just wouldn't be practical to rearrange all of the components on the fly given the number of components I have on the screen and their relationship with one another.

I hope that the problem that I am describing makes sense. Does anyone have any ideas? I appreciate any suggestions, thanks for your time.

[1902 byte] By [Malcolm_Fa] at [2007-10-3 4:53:19]
# 1
Just an idea: If you can group - on the screen - the components that "come and go", then you might be able to position them in an individual panel, and make that alternatively visible and invisible. That would eliminate doing a whole lot of monkeying with component locations at runtime.
bschauwejavaa at 2007-7-14 22:58:10 > top of Java-index,Java Essentials,Java Programming...
# 2
GUI builders are a tool of the devil.
-Kayaman-a at 2007-7-14 22:58:10 > top of Java-index,Java Essentials,Java Programming...