docs.rs failed to build tinyosc-0.0.2
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Please check the build logs for more information.
See Builds for ideas on how to fix a failed build, or Metadata for how to configure docs.rs builds.
If you believe this is docs.rs' fault, open an issue.
Visit the last successful build:
tinyosc-0.0.3
_ _ | |||___ _ _ ___ ___ ___ | | | | | | . | -| | || |||| |||| ||
tinyosc is a small, liberally licensed opensoundcontrol implementation for
rust. it is, at the moment, quite bare-bones, but the gist and spirit are
both there.
currently, only serialization and deserialization of messages is
supported. pattern matching is planned.
tinyosc supports the following type-tags:
'i' => i32,
'f' => f32,
's' => &str,
'T' => true,
'F' => false,
'N' => Argument::None
you can construct argument lists manually, with vec![] like so:
Message {
path: "/where/ever/its/happenin",
arguments: vec![Argument::i(42), Argument::f(32.32), Argument::F]
}
or you could use the handy osc_args![] macro, which automatically wraps
arguments in their corresponding Argument variant:
Message {
path: "/where/ever/its/happenin",
arguments: osc_args![42, 32.32, false]
}
this is identical in effect to the above example with vec![]. the choice
is yours!
simply pair Message serialization/deserialization with std::net::UdpSocket
and you are well on yr way!
questions, comments, and/or ascii art to wrl@illest.net
peace