Peter,
Your response is confusing to me. In 'knobs.h' is the following definition:
/*! A histogram knob displays a histogram and lets the user
choose 5 mapping parameters */
inline Knob* Histogram_knob(Knob_Callback f, Histogram_Data* p, NAME n,
LABEL l = 0)
{
return f(HISTOGRAM_KNOB, Custom, 0, n, l, p);
}
Obviously, the Histogram knob itself was designed to be used externally -- it's
included in an NDK .h file. If one of the primary parameters of the call is
'Histogram_Data', than clearly this also was intended to be used externally --
or the entire knob is useless. This is not just the way the Histogram knob
represents the data internally, it's how the knob is defined by users.
Also, I would observe that exposing the data structures required for this knob
does not preclude you from defining new structures and new knob definitions in
the future. If at some point, you want to implement a new and improved
'Histogram_knobX', you can depreciate the old one, still retain its definition,
and encourage your users to use the new knob and interface. There is nothing
that requires us to use one style of knob and data structures forever, and thus
we are never 'locked in' to using any former defined class.
I have to honestly say, that the difficulty of obtaining a simple data
structure from The Foundry is becoming rather perplexing.
Steve
-----Original Message-----
From: nuke-dev-boun...@support.thefoundry.co.uk
[mailto:nuke-dev-boun...@support.thefoundry.co.uk] On Behalf Of Peter Pearson
Sent: Thursday, June 02, 2011 12:26 AM
To: nuke-dev@support.thefoundry.co.uk
Subject: Re: [Nuke-dev] Histogram_Data?
On 01/06/11 17:04, Steven Booth wrote:
> Wouter,
>
> Wow. That's kind of startling, considering how useful Histograms are.
> Oh well.. guess someone had to be the first :)
>
> Given that there's no licensing issues, then, it should be a simple
> thing to specify it's structure (hint, hint ;)
But it currently wasn't designed to be exposed through the NDK in terms of
having an outside interface - that structure is how the Histogram knob
represents its data internally - if we expose that now, we're locked into using
that in the future and can't change how the Histogram knob works internally, so
I don't think that's the way to go.
Peter
--
Peter Pearson, Software Engineer
The Foundry, 6th Floor, The Communications Building,
48 Leicester Square, London, UK, WC2H 7LT
Tel: +44 (0)20 7434 0449 - Fax: +44 (0)20 7434 1550
Web: www.thefoundry.co.uk
The Foundry Visionmongers Ltd.
Registered in England and Wales No: 4642027
_______________________________________________
Nuke-dev mailing list
Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
(CONFIDENTIALITY NOTICE: The information contained in this email may be
confidential and/or privileged. This email is intended to be reviewed by only
the individual or organization named above. If you are not the intended
recipient, or an authorized representative of the intended recipient, you are
hereby notified that any review, dissemination or copying of this email, or the
information contained herein is strictly prohibited. If you have received this
communication in error, please notify the sender by return email and delete
this email from your system. Thank You.)
_______________________________________________
Nuke-dev mailing list
Nuke-dev@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-dev
