I kind of want a "Perl Standard Polygon Mesh Object" so that I can have modules pass those around without being especially dependent on eachother. Though, it's hard to have that when people want so many differing things from a mesh, like surface normals per polygon, or normals per vertex, or texture coordinates, texture references etc. On top of that, the most interesting meshes are the dynamic ones made by tools like Blender, and I have no idea how those are stored or processed. So, I probably don't have the expertise to define one that fits all use cases. I briefly investigated wrapping OpenCASCADE, but it's probably the most awkward C library I've ever tried to make into a CPAN module, mostly due to size and compilation speed and dependencies; even Debian divides that collection into 7 different packages. PDL can load STL files, so that seemed like a good place to focus, in the meantime.

If I knew more about Blender models, I might try to create a standalone CPAN dist for 3D objects and then make them all PDL-compatible, and add support for them in Math::3Space and OpenGL::Sandbox and Geo::SpatialDB.

In reply to Re^5: Creating X BitMap (XBM) images with directional gradients by NERDVANA
in thread Creating X BitMap (XBM) images with directional gradients by kcott

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.