transform catart-mubu into a Max package #47
Comments
diemoschwarz
added
enhancement
|
I'm up for it! Another step perhaps to add: make an overview patch to display in the Max Extras menu. |
|
I'm up for it too; it'd be great to polish things up. Admittedly a little busy, but let's try to make it happen! |
|
I finally have some time to devote to this over the next few months, so let me know how I can be most helpful! |
|
Great to hear that, Chris! I guess a brainstorming/suggestions/patch snippets about what should be in the "main" package intro/overview patch and the package description would be great. |
|
Hi again, rethinking this, there are a few larger tasks I foolishly opened, like:
Should we better finalize all these before releasing a package, or rather get the package out there with all the WIP patches removed, and then issue updates? |
|
Hi Diemo, I agree we should resolve those before CaMu is package-ready. I am pretty busy with deadlines until Sept. but I hope I can advance on some of those issues in the autumn!
I hope you’re keeping cool, or maybe the heat in Paris reminds you of Marseille! Cheers, Aaron
… On Jul 22, 2022, at 1:14 PM, diemo ***@***.***> wrote:
Hi again, rethinking this, there are a few larger tasks I foolishly opened, like:
#43 <#43>
#49 <#49>, with a parallel set of process modules
#53 <#53>, which needs reworking of the poly voice modules
and related #48 <#48>, #56 <#56>, #58 <#58>
Should we better finalize all these before releasing a package, or rather get the package out there with all the WIP patches removed, and then issue updates?
What are your thoughts on this, @einbond <https://github.com/einbond> and @christophertrapani <https://github.com/christophertrapani>?
—
Reply to this email directly, view it on GitHub <#47 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADRCSBNRERFQHGCQDOMQNL3VVJ7CTANCNFSM5HMQDQBQ>.
You are receiving this because you were mentioned.
|
|
Hi guys — I've just returned to the US and am happy to do some work on
this. Maybe a bit more free than usual these days...
Of the issues Diemo mentioned, maybe we could start with working on
segmentation issues? Some things (snapshots) are a bit beyond me but I am
happy to help...
C
…On Fri, Jul 22, 2022 at 7:14 AM diemo ***@***.***> wrote:
Hi again, rethinking this, there are a few larger tasks I foolishly
opened, like:
- #43 <#43>
- #49 <#49>, with a
parallel set of process modules
- #53 <#53>, which
needs reworking of the poly voice modules
- and related #48 <#48>,
#56 <#56>, #58
<#58>
Should we better finalize all these before releasing a package, or rather
get the package out there with all the WIP patches removed, and then issue
updates?
What are your thoughts on this, @einbond <https://github.com/einbond> and
@christophertrapani <https://github.com/christophertrapani>?
—
Reply to this email directly, view it on GitHub
<#47 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRYDCZBFXOQV36JC5V5OVTVVJ7CTANCNFSM5HMQDQBQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Hiya, here in Normandy I've encountered temperatures under 25º for the first time since 5 months, I'm freezing! I think we can advance in parallel, doing the package thing on github (so people can download it), while deciding on which issues are blocking the official release on the PM (to be added to https://github.com/Ircam-RnD/catart-mubu/milestone/11). I fear trying to do all of them could delay this for a long time... |
|
Hi @christophertrapani and @einbond, I made good progress sketching the camu package structure (#61) and content (#59). It lives in branch wip-max-package. Beware: none of the bubble texts are updated yet, I'll need help with these once everything is there. Any remarks on the structure (#59)? Any suggestions for a more self-standing overview patch design / typography / color scheme, without overdoing it (I copied the mubu one for now). Any favourite packages for an example? Best! |
|
Just downloaded and had a first look at the simple patch, which I think is
pretty much optimized already for straightforward presentation! A logo and
simple color scheme / typography standardization is a great idea, but I
can't say I have any real preferences. Same for license and readme...
…On Mon, Aug 22, 2022 at 8:37 AM diemo ***@***.***> wrote:
Hi @christophertrapani <https://github.com/christophertrapani> and
@einbond <https://github.com/einbond>, I made good progress sketching the
camu package structure (#61
<#61>) and content (#59
<#59>). It lives in branch
wip-max-package
<https://github.com/Ircam-RnD/catart-mubu/tree/wip-max-package>. Beware:
none of the bubble texts are updated yet, I'll need help with these once
everything is there.
Any remarks on the structure (#59
<#59>)? Any suggestions
for a more self-standing overview patch design / typography / color scheme,
without overdoing it (I copied the mubu one for now). Any favourite
packages for an example?
Any opinions on the other points (logo #60
<#60> , license #62
<#62>, readme)?
Best!
—
Reply to this email directly, view it on GitHub
<#47 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIRYDCZU3HMQU3ZCAL3TU33V2N7BPANCNFSM5HMQDQBQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
All it took was asking... to get more info on the package-info.json. |
this could augment adoption through the package manager, and make it easier to handle dependencies (on Mubu mainly, but also bach?). Any enthousiastic encouragements?
A guesstimate of the necessary steps:
If you plan to submit your Package for consideration for Cycling '74's Package Manager, you will need to have both a ReadMe and a License in your package.
Cycling resources:
The text was updated successfully, but these errors were encountered: