Render-able Annotation types - 2, 3, 4, 5...n point relations

View: New views
4 Messages — Rating Filter:   Alert me  

Render-able Annotation types - 2, 3, 4, 5...n point relations

by Daniel Scott Matthews :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

I'd like to be able to use a node type that took point selections
across one or more other nodes (mesh etc.) and output a set of
floating point values that described the relationships between the
points. These relationships would at a minimum include distance,
angle, normal and center. This data could then be used by special
annotation nodes that used established CAD standards to represent the
relationships numerically and diagrammatically. These annotations (and
ideally all annotations) would be render-able.

I have notices there is some code in the API to do some of this, is it
an existing WIP?

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development

Re: Render-able Annotation types - 2, 3, 4, 5...n point relations

by Timothy M. Shead :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Daniel Scott Matthews wrote:
> I'd like to be able to use a node type that took point selections
> across one or more other nodes (mesh etc.) and output a set of
> floating point values that described the relationships between the
> points. These relationships would at a minimum include distance,
> angle, normal and center. This data could then be used by special
> annotation nodes that used established CAD standards to represent the
> relationships numerically and diagrammatically. These annotations (and
> ideally all annotations) would be render-able.

Taking a simple example, if you mean "make dimension lines a primitive
type, and provide painters for them", that's what I've had in mind.

> I have notices there is some code in the API to do some of this, is it
> an existing WIP?

Not sure what you're referring to here ...

Cheers,
Tim

[tshead.vcf]

begin:vcard
fn:Timothy Shead
n:Shead;Timothy
org:www.k-3d.org
email;internet:tshead@...
title:Founder
x-mozilla-html:FALSE
version:2.1
end:vcard



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development

Re: Render-able Annotation types - 2, 3, 4, 5...n point relations

by Daniel Scott Matthews :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

On Tue, Oct 27, 2009 at 3:59 PM, Timothy M. Shead <tshead@...> wrote:

> Daniel Scott Matthews wrote:
>>
>> I'd like to be able to use a node type that took point selections
>> across one or more other nodes (mesh etc.) and output a set of
>> floating point values that described the relationships between the
>> points. These relationships would at a minimum include distance,
>> angle, normal and center. This data could then be used by special
>> annotation nodes that used established CAD standards to represent the
>> relationships numerically and diagrammatically. These annotations (and
>> ideally all annotations) would be render-able.
>
> Taking a simple example, if you mean "make dimension lines a primitive type,
> and provide painters for them", that's what I've had in mind.

Yes, but split the data calculation from the representation because
the data is handy for other tasks such as parametrics or animation.

The code needs to be smart enough to handle sets of 1-n selected
points across multiple nodes.
1 point could have XYZ absolute position and polar coordinates
2 points can have distance, center, vector, as well as the 1 point
data for each point.
3 points has center, plus the data for three sets of two points.

Then there are the calculation of angles for the combinations of all
set of three points in the selected points and bounding rectangles and
boxes.

The idea being that there is a set of routines for calculating useful
geometric data from sets of points and that data can be used by a set
of nodes that present the data in appropriate ways.

>> I have notices there is some code in the API to do some of this, is it
>> an existing WIP?
>
> Not sure what you're referring to here ...

I thought I saw some relevant routines for calculating some of
required data. It was probably just part of something else like the
physics stuff.

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development

Re: Render-able Annotation types - 2, 3, 4, 5...n point relations

by Timothy M. Shead :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Daniel Scott Matthews wrote:
> On Tue, Oct 27, 2009 at 3:59 PM, Timothy M. Shead <tshead@...> wrote:
>> Taking a simple example, if you mean "make dimension lines a primitive type,
>> and provide painters for them", that's what I've had in mind.
>
> Yes, but split the data calculation from the representation because
> the data is handy for other tasks such as parametrics or animation.

Sure, with this model, you have a modifier that takes geometry as input,
and produces geometry + dimension lines as output.  As always, you can
have as many different modifier types as you like.

Cheers,
Tim

[tshead.vcf]

begin:vcard
fn:Timothy Shead
n:Shead;Timothy
org:www.k-3d.org
email;internet:tshead@...
title:Founder
x-mozilla-html:FALSE
version:2.1
end:vcard



------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development