New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
XRNX plugin #2
XRNX plugin #2
Conversation
Removed files that won’t or can’t be used in the XRNX/Lua version of the plugin
Added the basics required to have a working XRNX plugin.
Added Pixelmator format of the icon and colored it Renoise maroon.
Renoise complains that the Homepage URL is HTTPS, so changing it to HTTP.
As an alternative to the LibGit (which is written in C and therefore needs to be wrapped) based LuaGit, there are all-Lua alternatives like this and this. They seem incomplete and rought, but might just have enough functionality for what we need here. They will also have a greater chance of working cross platform, I think. |
Please read this on how to do development in Renoise. The simplest way is to find the Installing will actually copy the files into Renoise's Library folder, so you will need to either continue hacking inside the Library folder, set up your git repository there, or uninstall and reinstall every time you want to make a change. I haven't figured out the best workflow yet. |
I don't understand this pull request. If there is to be a Lua/xrnx version it should be in a separate project. rnsgit is a standalone command-line tool. Having a single repo that is both a ruby-based CLI tool and a seperate Lua-based Renoise tool is confusing. |
I agree that having a single repository maintaining two separate languages doesn't make sense. I'm sorry, but I got the impression that you would like to move the project from Ruby and CLI to Lua and XRNX. I take it from your comment and rejection that I've misunderstood? |
I've created a basic XRNX plugin that hooks into the
app_new_document
andapp_saved_document
notifiers. It doesn't do much else useful yet, but I have had a look at adding LuaGit and it unfortunately doesn't seem trivial to just drop it into the plugin without requiring anything installed on the computer. We need to explore that in more detail.