https://github.com/alecmce/RacetrackStats

We can infer the relative weight of the code-base, pre-render and render portions of the AS3 racetrack, so why not monitor those like we monitor framerate?
https://github.com/alecmce/RacetrackStats

Last synced: 3 months ago
JSON representation

We can infer the relative weight of the code-base, pre-render and render portions of the AS3 racetrack, so why not monitor those like we monitor framerate?

• Host: GitHub
• URL: https://github.com/alecmce/RacetrackStats
• Owner: alecmce
• Created: 2010-02-25T20:12:35.000Z (over 14 years ago)
• Default Branch: master
• Last Pushed: 2010-05-22T17:08:41.000Z (over 14 years ago)
• Last Synced: 2024-07-30T02:23:52.615Z (3 months ago)
• Language: ActionScript
• Homepage:
• Size: 170 KB
• Stars: 19
• Watchers: 2
• Forks: 1
• Open Issues: 2
• Metadata Files:
  • Readme: README

Awesome Lists containing this project

• awesome-actionscript-sorted - RacetrackStats - We can infer the relative weight of the code-base, pre-render and render portions of the AS3 racetrack, so why not monitor those like we monitor framerate? (Unsorted / Other API)

README

        
@see http://alecmce.com/uncategorized/introducing-racetrackstats

== TODO ==

> Create more real-use test situations

> Investigate trend-line overwriting text bug

> Use the RacetrackStatsStyle more fully to define size, text

> Customise which graphs are displayed through the RacetrackStatsStyle

== TOTHINKABOUT ==

> Put some sort of scale on the graphs?

> Add minimise functionality?

> possibly 'magic keyword' functionality?

> Is it too heavy?