[TOOL] SourceMod: Watcher (auto-compile changed files) (Alpha 0.01)
SourceMod: Watcher (auto-compile changed files) (Alpha 0.01) I worked on a new plugin today and was really tired of always dragging the .sp file on the compiler to get it ready, so I decided to make a tool which does that automatically for me and to share it with you! It is made in Java 7, so you probably need Java JRE (only if you haven't installed it already). It should work for all Windows versions since it uses some console commands, I've tested it only on Windows 8.1 though. Since I made this in a few hours, it is kind of a pre-alpha version, so don't expect it to work perfectly! Also don't be too shy to post your feedback & suggestions here. Features:
Download (via GitHub) Source Code Screenshots: The config/settings dialog: http://i.imgur.com/04N0dRF.jpg The main window: http://i.imgur.com/6CLpaPX.jpg Also outputs compile errors: http://i.imgur.com/jkUd3ro.jpg Last but not least, the succeeded compilation + file moving: http://i.imgur.com/SCP3eeh.jpg |
Re: [TOOL] SourceMod: Watcher (auto-compile changed files) (Alpha 0.01)
This is awesome. I always get tired of testing that 'one thing' until it's right, and this will help with the anxiety of dragging and dropping all the damn time, especially when i run out of mouse pad :P. I also love the open source!
|
Re: [TOOL] SourceMod: Watcher (auto-compile changed files) (Alpha 0.01)
Quote:
|
Re: [TOOL] SourceMod: Watcher (auto-compile changed files) (Alpha 0.01)
Quote:
Quote:
|
Re: [TOOL] SourceMod: Watcher (auto-compile changed files) (Alpha 0.01)
Quote:
|
Re: [TOOL] SourceMod: Watcher (auto-compile changed files) (Alpha 0.01)
Quote:
although uploading to ftp would be nice. |
Re: [TOOL] SourceMod: Watcher (auto-compile changed files) (Alpha 0.01)
CTRL + B and I have it outputted to a easy accessible folder, ready for upload. Compile log shows up in the editor.
|
Re: [TOOL] SourceMod: Watcher (auto-compile changed files) (Alpha 0.01)
Quote:
Edit: and even using this policy, PropHunt has still had 209 commits in the master branch since I started working on it a year ago. Edit 2: 221 commits in the 3.3 branch. Edit 3: However, if I'm switching computers, unfinished changes will be checked in, which is why new versions are developed in branches and then merged back into master. Also because people pull from my master repo and expect a version that actually works. I will also make changes to the current version in master then merge it back to the current version branch for things like configuration file changes. |
| All times are GMT -4. The time now is 18:27. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.