-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
idiom for interfaces #4
Comments
My current thoughts on interfaces are that these are functions in headers that look like: void declare_video_device_outputs(tendrils& outputs)
{
//set outputs
outputs.declare<cv::Mat> ("image", "A video frame.", cv::Mat());
outputs.declare<int> ("frame_number", "The number of frames captured.", 0);
} And these are used by clients like: struct VideoCapture
{
//....
static void declare_io(const tendrils& params, tendrils& inputs, tendrils& outputs)
{
//set outputs
declare_video_device_outputs(outputs);
}
//....
};
struct OpenNICapture
{
//...
static void declare_io(const tendrils& params, tendrils& inputs, tendrils& outputs)
{
//declare standard video device outputs
declare_video_device_outputs(outputs);
//nonstandard just for openni cameras.
outputs.declare<cv::Mat> ("depth", "The output depth map", cv::Mat());
outputs.declare<cv::Mat> ("valid", "The output valid mask", cv::Mat());
outputs.declare<cv::Mat>("K","The camera intrinsic matrix.");
}
//...
}; |
Need to add this to a tutorial... |
|
Just needs an idiums page in docs. |
i'll take this one |
Cool, take it. |
I heard you were working on this at home, any progress? |
Yes but I need to integrate, and I'm stuck under a nasty roscpp On Tue, Jul 12, 2011 at 10:04 AM, ethanrublee
|
kicked |
Not too useful right now. Its easy enough to write some functions that declare interface... |
Come up with an ecto interface definition idiom.
e.g. static functions that declare io names/types for a face detector, or tracker, etc...
The text was updated successfully, but these errors were encountered: