OpenAero / OpenAero/main

3D coding can be improved

Open
#97 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component-Logic enhancement Priority-Low
Dominant language
JavaScript
Stars
18
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Currently the algorithm relies on several if-then routines involving checking 
for 45 deg lines. Also a seperate True_Drawing_Angle is calculated in different 
places depending on such comparisons.
It would be more elegant if this were adapted to handle all possible angles 
(e.g. 30 deg) with a minimum of if-then uses.

Original issue reported on code.google.com by openaero...@gmail.com on 26 Jun 2013 at 2:18

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. First locate the 3D angle-handling algorithm and the separate True_Drawing_Angle calculations, then trace the existing 45-degree conditionals. Done means supporting arbitrary angles with fewer conditional branches while preserving current drawing behavior, but the issue does not define tests or exact acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
computer-graphics
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.