Anything we can merge to upstream? #69
Comments
|
It's all pretty clean I'd say. Here is everything in one single commit, if you want to have a look: I think we could get away with removing some of those options from the server command line if needed, possibly having a single |
|
excellent! i think we can merge in the driver and command-line changes (with |
|
In the language there is the move of the GUI classes to somewhere where
it won't compile. That needs a more elegant solution still.
The BELA UGen class files are useful to have on regular SC, in case you
are remote controlling a Bela running SC. That is a common practice
while developing code for Bela.
So that is a case where you'd want the UGen class files, but not the
UGen plugin.
…On 09/09/18 01:24, Nathan Ho wrote:
excellent! i think we can merge in the driver and command-line changes
(with |--bela| prefixes preferably) and keep the bela-specific server
plugins as a third-party plugins directory. @brianlheim
<https://github.com/brianlheim> has been working on a generator for
plugins repositories
<https://github.com/brianlheim/cookiecutter-supercollider-plugin> that
will help with that.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMS3geKy3fkTIpObcRDt6t5mQuLgdtvks5uZFHAgaJpZM4Wf-Fw>.
|
|
@sensestage I guess you are referring to the list of files below, right? Could we not leave them in place and either: a) avoid installing them when no GUI is installed (change to CMake I guess), or b) avoid loading them when |
I believe we solved that on our end in this PR: supercollider#3456 but maybe I am misunderstanding |
|
Yes, that will probably fix it.
…On 09/09/18 23:55, Brian Heim wrote:
In the language there is the move of the GUI classes to somewhere
where it won't compile. That needs a more elegant solution still
I believe we solved that on our end in this PR: supercollider#3456
<supercollider#3456>
but maybe I am misunderstanding
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#69 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAMS3qK2idelIKKhoixDeWkLi0qppJzwks5uZY5AgaJpZM4Wf-Fw>.
|
|
it does indeed |
|
superseded by #73 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
hi all! i saw the discussion at #67 about upgrading to 3.10.
i think SuperCollider could be making some efforts to make bela+SC development smoother. we've sorta started this discussion before, but i'd like to revive it.
what are the differences between this fork and upstream? i'd especially like to look at patches to the non-user-extensible parts of SC such as the language and the server — i see belaSC has a lot of
#ifdef BELA, so i think a lot of them could be safely merged without causing any disruption for non-Bela users.The text was updated successfully, but these errors were encountered: