> For the complete documentation index, see [llms.txt](https://digitalgarden.batamladen.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digitalgarden.batamladen.com/notes/programming/java/gui.md).

# GUI

A Java GUI (Graphical User Interface) is a visual interface that allows users to interact with a Java program. It includes graphical components such as buttons, text fields, labels, and more, which users can interact with using a mouse, keyboard, or touch screen.

In Java, GUIs are typically created using the Swing or JavaFX libraries. These libraries provide classes and methods to create windows, dialogs, and various types of components, as well as manage events such as button clicks or mouse movements. GUI programming in Java involves creating these components, arranging them on a screen, and adding functionality to them using event handling.

The GUI is made in a separate class file in Java, but would be nice if it is in the same package at the class/es that you want to interact with.

Below is a explanation on using the set of Switch classes and components from the javax.switch package.

{% content-ref url="/pages/pXX60k6ojEO2hRumcBSF" %}
[SWING](/notes/programming/java/gui/swing.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://digitalgarden.batamladen.com/notes/programming/java/gui.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.