How to Build a Self‑Control IntelliJ Plugin to Stop Coding Fatigue
This article explains why the author created the StopCoding IntelliJ plugin, provides step‑by‑step installation and usage instructions, and walks through the Java Swing and Timer‑based implementation details, enabling developers to prevent prolonged sitting and improve productivity.
01 Preface
When I was young, I chose a computer science major because my parents heard it was a good choice. Over the years I have spent countless hours in dorms, labs, and libraries writing C, C++, Java, and other code. After entering the workforce as a developer, long periods of sitting and continuous coding caused back and leg discomfort, prompting me to create a tool to enforce regular breaks.
02 Installation Guide
Install
Search for "StopCoding" in the IntelliJ Marketplace and install the officially approved plugin.
For internal network users, download the plugin from the GitHub release page https://github.com/jogeen/StopCoding/releases/tag/20210104-V1.0 and install it locally.
Usage
Open Tools → StopCoding from the menu bar.
Configure the reminder interval and other parameters, then save.
When the interval elapses, a non‑dismissable dialog appears with a countdown; the IDE loses focus until the break time is completed.
03 Development Tutorial
The plugin is built with basic Java knowledge, using Swing for UI and Timer for scheduling. Its project structure includes:
plugin.xml : Core configuration file.
data package: SettingData (model for configuration) and DataCenter (static runtime data).
service package: TimerService (core timing logic).
task package: RestTask (break timer) and WorkTask (work timer).
ui package: SettingDialog (settings UI) and TipsDialog (break reminder UI).
StopCodingSettingAction : Entry point action.
04 Swing Dialog Creation
Creating dialogs in IntelliJ is straightforward thanks to the IDE's visual designer. The steps are:
Design the dialog layout using the GUI builder.
Add components such as buttons and labels.
Generate event listeners for the buttons.
The default buttons already have click listeners; you can customize them as needed.
public class TestDialog extends JDialog {<br/> private JPanel contentPane;<br/> private JButton buttonOK;<br/> private JButton buttonCancel;<br/><br/> public TestDialog() {<br/> setContentPane(contentPane);<br/> setModal(true);<br/> getRootPane().setDefaultButton(buttonOK);<br/><br/> buttonOK.addActionListener(new ActionListener() {<br/> public void actionPerformed(ActionEvent e) {<br/> onOK();<br/> }<br/> }); // OK button listener<br/><br/> buttonCancel.addActionListener(new ActionListener() {<br/> public void actionPerformed(ActionEvent e) {<br/> onCancel();<br/> }<br/> }); // Cancel button listener<br/> }<br/> // other code ...<br/>}05 Timer Usage
The plugin relies on java.util.Timer to schedule work and break periods. Common APIs include the constructor, schedule to add tasks, and cancel to stop the timer.
With these components, developers can build a lightweight IntelliJ plugin that forces periodic breaks, helping prevent coding fatigue and improve health.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
Java High-Performance Architecture
Sharing Java development articles and resources, including SSM architecture and the Spring ecosystem (Spring Boot, Spring Cloud, MyBatis, Dubbo, Docker), Zookeeper, Redis, architecture design, microservices, message queues, Git, etc.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
