> So do you mean, adding no depth to the annotations or adding depth in a
> separate coordinate system exclusive to annotations? Because what I thought
> was of adding depth to the annotations, aiming for view independent geometry.
While it could be useful in some contexts for annotations to have depth, this
is entirely secondary to their intended purpose. That is, any depth
parameterization should be optional and probably not default.
There is a need for both dependent and independent view interaction. A linear
dimension (e.g., bounding box dimensions) might be aligned with the principal
coordinate system planes. A text label will often be aligned to the view.
Example of both:
http://www.engineersrule.com/wp-content/uploads/2016/10/image007-2.png
<http://www.engineersrule.com/wp-content/uploads/2016/10/image007-2.png>
“Anodized per company standard 123” is a simple leader annotation (with an
awkward oval box drawn around it) aligned to the view. The other two blue
annotations are aligned with a modeling plane, not the view.
> Do you expect to enter the location for the placement in the "in" command
> itself ? Correct me if I'm thinking differently.
It would probably be a good idea to have some user-defined way to create
annotations, but whether that is the ‘in’ command or an ‘annotate’ command or
some other means is secondary to implementing basic support for representing
and displaying them.
> Considering "annotation" as the head primitive. I feel the need to create
> some "sub-primitives", which comprise of options like "text", "leader line",
> "GD", "Tolerances" , "Hatches" etc. where each sub-primitive has its own
> desired parameters.
…[snip]...
> I'm trying hard to go deep into the project, but that is of no use unless I
> come to know about the community's expectation from the project.
I’m getting the sense that you still need to read the top-level TODO file.
Search for “annotation” in there and you’ll find a big section on desirable
annotation primitive features. You should read the other references listed on
the wiki as well.
Cheers!
Sean
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
BRL-CAD Developer mailing list
brlcad-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/brlcad-devel
