Closed pq closed 3 years ago
Current message types (string, int, float) are sufficient for my usual needs and I assume the needs of most users; I think a minimal 1.0 release should, however, include the remaining two types from the OSC spec (blobs and timestamps). I've not really used the timestamp-scheduling features of OSC, not sure if its use is prevalent or not. I think that covers the OSC 1.0 spec...?
fyi @jeffmikels, please chime in if there are other things you would value in a 1.0
.
I don't know much about timestamps, but I think 1.0
should cover whatever is in the basic OSC spec. It currently has everything I need as is, though.
Also, 1.0
should land this package on pub.dev
Also, 1.0 should land this package on pub.dev
Really I should do that sooner. (Are you using a git dependency? Gross to have to resort to that.)
I'll look at timestamps but also consider pushing a 0.8 to pub.
Thanks for following up!
@pq would it be possible to have the current version published on pub as it would be bit nicer than using via git.
For me I think the current functionality would be enough, as my usecase is just to communicate from a Dart cli app on a headless RPI (but initially Flutter app too) with a PD patch, as I'm finding it's quite a lot of work wrapping libPD via FFI, especially dealing with ALSA. With OSC I could just run PD itself headless and communicate (send messages text, receive timing ticks) between PD and a Dart app.
I'll take a look in the next few days. I should really sort out #8 but features can wait. Thanks for the nudge!
EDIT: looks like I did wrap up licensing and contributing docs already but forgot to update the issues 😬. This should be good to go after I update some deps.
Published. 👍
@pq the package is working really well for my project, thank you again for publishing it! 👍🏻
So glad to hear. Have fun!
Follow-up from https://github.com/pq/osc/pull/3#issuecomment-450179637, a meta-issue to track features for a basic
1.0
release.In general, one view 1.0-readiness might be associated w/ OSC spec completeness which leaves:
Plus some general tidying up:
Slipped to next release:
/cc @monkeyswarm for thoughts?