humbletim

How about porting the inline code comments from OimoPhysics.as (into JSdocs for Oimo.js)? The main classes still seem to line up between projects so in theory this could even done...

OK, had a few moments to test out automated porting of the comments; several quirks to it, but the overall classes and properties do seem to map-over pretty well still....

@jetschni Sounds interesting! What else do we need to get this group off the ground? Also do you imagine collaborative research leading to formal specifications (at some point)? If so...

@jsealt's related notes from 7/21/2021 OMI Weekly Meeting 13: https://hackmd.io/e4RBv8H6TnKfud7ebrvmNQ?view#Virtual-Space-Update ## Virtual Space Update We created [#44](https://github.com/omigroup/OMI/issues/44) in an effort to call for submissions for virtual spaces for OMI. -...

here is another cc-sa template to consider: https://github.com/processing/p5.js/blob/main/CODE_OF_CONDUCT.md ... not as exhaustive as contributor-covenant, but i really like how accessible the p5js versions feels -- and they way it captures...

thanks for the issue report. i was able to replicate the issue locally and suspect a small bug in parsing of the branch/tag/commit information from the config JSON. not sure...

Thanks for the follow-ups (it is also started working for me suddenly). Root cause apparently interim changes on LunarG's side, but checking their bug tracker, I don't see any recent...

having been unable to repro again, closing this given #12 merges better error reporting that theoretically will help catch these kinds of nuances moving forward. thanks!

hi samuel, thanks for the PR and your ongoing work on shaderc integration! i've noticed a lot of commits coming in -- is there anything i can do to help...

hey @sjcobb2022 no worries re: work-in-progress. :) last year when briefly looking into shaderc i recall hitting similar challenges. i didn't get as far but seem to recall one thing...