Thanks again for your work. I'm not a big fan of Java, but it's cool to see someone sharing code to interact with the X-Air!
Maybe you should consider setting a clear name for the project, maybe something like X-Air Java Toolkit if you want to provide more than one thing, or x-air-proxyfriends or what not (careful about potential trademarks from Behringer though ).
Then, path to the config file seems to be hardcoded to ~/xtouch/xtouch.properties. A more usual path would be ~/.config/x-air-proxy (though it supposes a clearer name than x-air or x-touch I'm afraid ;)). You can read about the XDG specs here: . More specifically this part:
$XDG_CONFIG_HOME defines the base directory relative to which user-specific configuration files should be stored. If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used.
I may help through a pull request there, but maybe the discussion before-hand is worth it ;)
Thanks again for your work. I'm not a big fan of Java, but it's cool to see someone sharing code to interact with the X-Air!
Maybe you should consider setting a clear name for the project, maybe something like X-Air Java Toolkit if you want to provide more than one thing, or x-air-proxyfriends or what not (careful about potential trademarks from Behringer though ).
Then, path to the config file seems to be hardcoded to ~/xtouch/xtouch.properties. A more usual path would be ~/.config/x-air-proxy (though it supposes a clearer name than x-air or x-touch I'm afraid ;)). You can read about the XDG specs here: . More specifically this part:
$XDG_CONFIG_HOME defines the base directory relative to which user-specific configuration files should be stored. If $XDG_CONFIG_HOME is either not set or empty, a default equal to $HOME/.config should be used.I may help through a pull request there, but maybe the discussion before-hand is worth it ;)