With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js. Learn more â
Top 8 TypeScript WebXR Projects
-
BabylonJS
Babylon.js is a powerful, beautiful, simple, and open game and rendering engine packed into a friendly JavaScript framework.
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
etherealengine
iR Engine - Bringing us together on the open social spatial web. đ¤ đ đ đšī¸ đ§đŋâđ
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Project mention: <model-viewer>: Easily display interactive 3D models on the web and in AR | news.ycombinator.com | 2024-05-28
As someone who has written math libraries over and over again for the last 25 years (no joke - wrote this in 1997: https://github.com/bhouston/BezierCurveDemo1997/blob/master/... and just recently wrote the Threeify math library: https://github.com/bhouston/threeify/tree/master/packages/ma...), I find that operator overloading works only for the simple cases but that for performance and clarify, function names work best.
Function names let you clarify that it is an outside product or inside product (e.g. there are often different types of adds, multiplies, divides), and I can not stand when someone maps cross product onto ^ or dot product onto something else. Also operator overloading often doesn't make clear memory management, rather it replies on making new objects constantly, where as with function names, you can pass in a parameter that will take the result. Lastly, function names allow you to pass in how to handle various conditions, like non-invertible, NANs, etc.
I find word based function more verbose but significant less error prone and also they are more performant. Operator overloading is only good for very simple code and even then people always push it too far so that I can not understand it.
Project mention: I Made A Browser Game Where You Can Use Your Desk To Play Osu Taiko Maps In VR | /r/osugame | 2023-12-09You can try it out here (it's completely free and also open source): https://cadenzavr.com/
TypeScript WebXR related posts
-
JSAR: Open-source edition of Meta Augments:)
-
Write GUIs in 3D space via HTML & CSS
-
The Spatial DOM implementation for XR applications
-
The Spatial DOM implementation for XR applications
-
My own collection so far :)
-
WebGL2 Fundamentals
-
I need a push in the right direction
-
A note from our sponsor - SurveyJS
surveyjs.io | 1 Jun 2024
Index
What are some of the best open-source WebXR projects in TypeScript? This list will help you:
Project | Stars | |
---|---|---|
1 | BabylonJS | 22,613 |
2 | model-viewer | 6,595 |
3 | react-xr | 1,951 |
4 | etherealengine | 696 |
5 | ossos | 363 |
6 | threeify | 195 |
7 | jsar-dom | 37 |
8 | cadenza | 14 |
Sponsored