IRC log for #brlcad on 20090902

01:10.03*** join/#brlcad talcite (n=Matthew@206-223-179-178.beanfield.net)
01:21.13starseekerthis is interesting - it looks like ON_Mesh only has faces and verticies
01:21.52brlcadlike BoTs
01:22.27starseekerdoes that make nmg->ON_Mesh a lossy conversion?
01:22.29brlcadconnectivity may be implied
01:23.21Yoshi477is there more docs on arbn?
01:23.22brlcadnot 100% sure, but shouldn't be from what I saw in the API for managing them
01:26.04brlcadfaq also says ON_Mesh faces may be non-planar.. which is pretty interesting
01:26.38starseekergrinds his teeth - doggone it, it's so close to working as is...
01:33.40brlcadthe biggest key off is their ON_MeshParameters class that they use for tessellation (and the fact that it's the result of their generalized tessellation interface)
01:33.58brlcadhas some pretty advanced remeshing parameters
01:34.22brlcadwhich are probably only used by the RhinoSDK but maybe not
01:35.25brlcadthe other is ON_MeshTopologyVertex and ON_MeshTopologyEdge and other similar classes that are basically nmg-style stitching connectivity
02:37.30*** join/#brlcad BigAToo (n=BigAToo@pool-96-230-124-159.sbndin.btas.verizon.net)
03:04.32*** join/#brlcad talcite (n=Matthew@206-223-179-178.beanfield.net)
03:29.35*** join/#brlcad talcite_ (n=Matthew@206-223-179-178.beanfield.net)
03:53.21starseekerbrlcad: Yes.  What's not immediately clear to me (at least, not without more digging) is whether those *Topology* structures need to be manually created or whether they are deduced from an ON_Mesh via some routine
04:44.43*** join/#brlcad puddingpimp (n=dave@118-93-244-155.dsl.dyn.ihug.co.nz)
06:20.19*** join/#brlcad PrezKennedy (i=Matthew@208.43.126.194)
06:22.07*** join/#brlcad talcite (n=Matthew@bas2-toronto21-1279332078.dsl.bell.ca)
06:57.33*** join/#brlcad talcite_ (n=matthew@76-10-171-135.dsl.teksavvy.com)
09:48.35*** join/#brlcad yukonbob (i=1000@s142-179-54-198.bc.hsia.telus.net)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.