Open elfenpiff opened 7 months ago
Hi,
I'd like to work on this. On what types should Display
implemented?
@hydroid7 I assigned you the issue (so that you have dibs on the issue ;) ) but before you start working on this I suggest waiting until latest 4th December, until elkodon is moved into eclipse-iceoryx/iceoryx-ng
and is also renamed to iceoryx-ng
.
Otherwise, you may encounter a lot of merge conflicts.
Also we could not merge your work before elkodon
is part of eclipse-iceoryx
due to the licensing issue. At the moment, your work would be published under the GPL 3.0 but this is only a temporary construct and then we need your explicit agreement to re-license your code under a different license.
Still, I am totally happy that you are on board here, so lets focus on the more interesting technical details. The idea came from the example in these two files:
So it would be nice if these two port factories would implement Display and the nice overview that the example is showing would be just a single line of code like:
let event_name = ServiceName::new(b"MyEventName")?;
let event = zero_copy::Service::new(&event_name)
.event()
.open_or_create()?;
// this line instead of all the lines from the example
println!("{}", event);
Ok, thank you for the information. I'll wait until Dezember.
@hydroid7 Here is the issue in the new iceoryx2 repo: https://github.com/eclipse-iceoryx/iceoryx2/issues/18 if you are still interested.
(Code) Example Of Cumbersome API
If one would like to print a state overview of a service it would be nice if the
port_factory::{event|publish_subscribe|...}
would have implementedDisplay
to show the overview from the example.