GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — raytrace/README.md at master · lpython/raytrace

Expand file tree

/

README.md

Copy path
More file actions
More file actions

Latest commit

 

History

History
History
9 lines (9 loc) · 980 Bytes
/

README.md

Copy path

File metadata and controls

9 lines (9 loc) · 980 Bytes
Raw
Copy raw file
Download raw file
Edit and raw actions

A learning project utilizing raytracing as 'work' with the following goals:

  • Adapt raytracer from typescript samples for use as long duration workload
  • Create single library to be used in either browser or node environment (scene-xml and raytrace)
  • Frontend is written using vanilaJS for DOM manipulation.
  • Backend uses express
  • Both front and backend use scene-xml and raytrace without having to be explicit in code. That is, both use the same import statement: import { Parse, basicSceneXML } from '@python36/scene-xml'
  • However, scene-xml delievers different code to front and back. In short, frontend uses browsers DOMParser to parse XML, while backend uses JS dependency. Uses webpack.NormalModuleReplacementPlugin to remove JS dependency. Either way, scene-xml uses one API.
  • Libraries provide bundles and es6 modules for consumers.
  • (TODO) Front end uses web worker to remain responsive.
You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.