-
Notifications
You must be signed in to change notification settings - Fork 35
Step By Step Dev Setup
xpdota edited this page Dec 8, 2021
·
4 revisions
This is a step-by-step guide for setting yourself up for development from 100% scratch. It is assumed that the only thing you have installed is an OS.
- Fork the Github repository ("Fork" in the top right).
- Download IntelliJ Community Edition
- Install it
- On the Welcome screen, select "Plugins" and make sure that the following plugins are installed (they should be installed by default):
- Maven
- Git
- Github
- TestNG
- On the Welcome screen, select "Projects" and then "Get from VCS"
- On the left, select "GitHub" and log in.
- Select the event-trigger project.
- Click "Clone"
- If you see a warning in the bottom left, click it and install Git when asked, and then repeat the last few steps.
- Click "Trust Project" unless you don't trust me.
- In the top right toolbar, there will be a dropdown with some pre-configured launch options. Try selecting "GuiLaunch" from the list, then click the play button next to it.
- You should get a warning that "The SDK is not specified for modules" with a link to "Configure...". Click the link.
- In the "SDK" dropdown, select Add SDK > Download JDK... and choose Version 11, Vendor Azul Zulu Community.
- Select "11" as the language level.
- Click OK.
- If you are asked about shared indexes, select "always download".
- When the download and indexing is complete, the play button should now correctly launch the GUI. If the play button is not enabled, click the hammer button to the left. If that still doesn't work, restart IntelliJ.
- If you do not have ACT open, it is normal to see websocket-related warnings since it won't be able to connect to ACT. To see dummy data, in the dropdown, select "GuiWithTestData" instead of "GuiLaunch".
- If you want to launch with the rough equivalent of browser dev tools, select "GuiLaunchSwexp".