Both sides previous revisionPrevious revisionNext revision | Previous revision |
tweegoeclipse [2018/03/20 17:38] – lee | tweegoeclipse [2018/03/20 19:03] (current) – [Step 7: Set up Auto Building] lee |
---|
Having to use the commandline to build the project after you save your work can be an issue for some. Even for those who possess the technical literacy to develop software in this way, it can still be a time-sink to have to manually build the project every time you save something. This isn't just a Tweego issue, it's something that affects programming in general. | Having to use the commandline to build the project after you save your work can be an issue for some. Even for those who possess the technical literacy to develop software in this way, it can still be a time-sink to have to manually build the project every time you save something. This isn't just a Tweego issue, it's something that affects programming in general. |
| |
The solution to commandline use and manual building it to use an Integrated Development Environment (or "IDE"). An IDE automates and encapsulates many tools and tasks, making your workflow more efficient. Typically file management, text editing, and in many cases even version control are all brought together into one graphical tool. | The solution to commandline use and manual building is to use an Integrated Development Environment (or "IDE"). An IDE automates and encapsulates many tools and tasks, making your workflow more efficient. Typically file management, text editing, and in many cases even version control are all brought together into one graphical tool. |
| |
Additionally, most IDEs provide "autobuild" functionality. That is, whenever you save a file, the IDE detects this and rebuilds your project so that it is immediately available for testing, without having to tab out to a command prompt and build the project by hand. | Additionally, most IDEs provide "autobuild" functionality. That is, whenever you save a file, the IDE detects this and rebuilds your project so that it is immediately available for testing, without having to tab out to a command prompt and build the project by hand. |
Under "Arguments", enter "-o build/KinkyPr0nGame.html src". You can change "KinkyPr0nGame.html" to whatever you want your output .html to be, but make sure that you leave it as being put in the "build/" directory. | Under "Arguments", enter "-o build/KinkyPr0nGame.html src". You can change "KinkyPr0nGame.html" to whatever you want your output .html to be, but make sure that you leave it as being put in the "build/" directory. |
| |
{{ ::main_tab.jpg?direct&600 |}} | {{ ::main_tab.jpg?direct |}} |
| |
**Next we'll set up the "Refresh" tab.** | **Next we'll set up the "Refresh" tab.** |
Ensure that "The entire workspace" radio button is selected, and that "Recursively include sub-folders" is checked. | Ensure that "The entire workspace" radio button is selected, and that "Recursively include sub-folders" is checked. |
| |
{{ :refresh_tab.jpg?direct&600 |}} | {{ :refresh_tab.jpg?direct |}} |
| |
**Next we'll set up the "Environment" tab.** | **Next we'll set up the "Environment" tab.** |
Assuming that you'll be using the Sugarcube story format, there's only one environment variable we need to set up here. Hit the "New" button, and set "TWEEGO_PATH" to whatever path you installed Tweego's story formats to. In my case, it's "D:/Tweego/story-formats". | Assuming that you'll be using the Sugarcube story format, there's only one environment variable we need to set up here. Hit the "New" button, and set "TWEEGO_PATH" to whatever path you installed Tweego's story formats to. In my case, it's "D:/Tweego/story-formats". |
| |
{{ :environment_tab.jpg?direct&600 |}} | {{ :environment_tab.jpg?direct |}} |
| |
**Finally, we'll set up the "Build Options" tab.** | **Finally, we'll set up the "Build Options" tab.** |
Finally, check the "Specify working set of relevant resources" box, and press the "Specify Resources..." button. In the window that pops up, roll open your project and check its "src" folder. Press "Finish". | Finally, check the "Specify working set of relevant resources" box, and press the "Specify Resources..." button. In the window that pops up, roll open your project and check its "src" folder. Press "Finish". |
| |
{{ :build_options_tab.jpg?direct&600 |}} | {{ :build_options_tab.jpg?direct |}} |
| |
{{ :working_set.jpg?direct&600 |}} | {{ :working_set.jpg?direct |}} |
| |
**Done.** | **Done.** |