I’m going to phase out the development of CabbageLite en lieu of a standalone export option. The CabbageLite version became bit of a pain to maintain. You can use an external editor with the main Cabbage IDE now by selecting ‘auto-update from disk’ in the File menu. I think most use cases for the Lite version will be catered for shortly. Note it’s still part of the installer, and will be until everyone is happy that the time has come for it to be removed.
thanks for clarifying, makes sense too
Hey Rory, thanks again for maintaining the Lite build… it’s been a huge help and has really become an integral part of my workflow.
I use CabbageLite as a build target for sublime, it launches using a command line interface and passes the filename as an argument. I can open any .csd in sublime and when I’m ready to render I just hit fn+f7, and CabbageLite renders the file in a small window, barely larger than the form size of the instrument.
So I think the most important two things for me right now are:
1: Render file from CLI: I need to be able to launch cabbage from a command line with a filename argument, and have cabbage open and render (not export!) that file. If this is achieved with an extra argument to render, that would be fine too… for example “Cabbage.app MyFile.csd” would open a file, “Cabbage.app -render MyFile.csd” would render, but that’s not really a requirement of mine. It might make things a little easier/more flexible for you?
2: Suppress/Minimize UI: Again, if this is achieved with an option like -suppress or whatever, that would be fine… I’m ok with it being the default behavior too, but I can see a use case for it being optional. I will sometimes leave the rendered window floating sticky on top of sublime while I edit code, so minimal is preferred.
So in the end, I would be launching from sublime via a command line, perhaps with a final command looking like:
Cabbage.app -surpress -render MyFile.csd
And the end result would look and feel similar to the current Lite offering, with regards to suppressed UI etc. Hopefully that makes sense… and even more hopeful that it’s feasible. Let me know if you have any questions, I’m glad to help where I can!
I think you should already be able to launch it from the command line. But note that you might have to use some OSX wizardry. I think your previous setup accounted for that. The fact that you must launch the Cabbage binary, which is located within Cabbagea.app…?
I didn’t think that was an issue at this point… but I wanted to make sure that I was being specific with the use case so there wasn’t any confusion as the merge progresses.