A GUI editor for Java that can manipulate objects on RUNTIME [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.

---

We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.

Closed 2 years ago.

Improve this question

I am looking for a Java GUI editor or library with the following exotic property: the GUI can be manipulated开发者_高级运维 on runtime. That is, a running frame can include special controls, e.g., right-click, that enable users to add buttons and other widgets to it.

Alternatively, I can use a GUI editor that can interact with a running Java program. The program says "please add a button" and the editor shows the user a palette with buttons. The user adds a button and presses it, and the program receives an event "button pressed".

It there such a thing that can be used off-the-shelf, without writing it from scratch?

---

Any compliant JavaBean library would support Design Time semantics. In a nutshell, a bean (component) is understood to run in a container. In design time, that container is the editor 'canvas' and in runtime, the root of of (gui) container hierarchy. The author of the bean is expected to query this state flag and act appropriately e.g. change borders in designtime to include 'handles' to drag for resize, etc. And, naturally, the parent component (which is assumed to be a design canvas of sorts) is also expected to respect design changes e.g. modify the layout to handle the resized component.

That said, I don't believe any of the current offerings allow you to simply switch between designtime and runtime at whim in your app.

Effectively, you'll need to (a) pick a library and (b) bundle the necessary machinery to support designtime with your running app, and (c) in effect masquerade a design surface (canvas) as your runtime gui. Of course you will only need to support the design ops you are interested in, but bottom line, you are writing a GUI editor.

What's the benefit of this approach? Well, you are reusing "components" and mostly need to hack the container.

If I had to do something like this, I would seriously look at netbeans, keep this STO question in mind, and take it from there.