Character Vault
Any Concept / Any System
Compendium
Your System Come To Life
Roll20 for Android
Streamlined for your Tablet
Roll20 for iPad
Streamlined for your Tablet

Personal tools

Difference between revisions of "Browser Developer Tools"

From Roll20 Wiki

Jump to: navigation, search
m
m
Line 11: Line 11:
 
==Uses in Roll20==
 
==Uses in Roll20==
 
* Get extra info to send with a [[Bug|Roll20 bug report]]
 
* Get extra info to send with a [[Bug|Roll20 bug report]]
 +
* For [[Macro purposes, identify attribute names in character sheets
 
* Tweaking Roll20 looks with [[Stylus]]
 
* Tweaking Roll20 looks with [[Stylus]]
 
**as long as something isn't part of the {{c|<canvas>}}, one can write & edit {{wiki|CSS|CSS}} snippets that changes the look for yourself if you save it as a userstyle with Stylus.
 
**as long as something isn't part of the {{c|<canvas>}}, one can write & edit {{wiki|CSS|CSS}} snippets that changes the look for yourself if you save it as a userstyle with Stylus.

Revision as of 07:14, 25 August 2022

Using the Firefox dev tools to inspect live sheet code

Using the built in Web Dev tools in your browser helps a lot with figuring things out. Both Firefox & Chrome (others) have their own versions.

Open it: pressing F12 or Right Click anywhere & select "Inspect".

Uses in Roll20

  • Get extra info to send with a Roll20 bug report
  • For [[Macro purposes, identify attribute names in character sheets
  • Tweaking Roll20 looks with Stylus
    • as long as something isn't part of the <canvas>, one can write & edit CSS Wikipedia-Black-W.png snippets that changes the look for yourself if you save it as a userstyle with Stylus.

Macros

Character Sheet Development

  • make live edits on you sheet and see how things change(like adjusting the width of a number input to look good)
  • inspecting other's sheets to se how they achieved some specific effect.
  • HTML/CSS debugging: figure out why something works or doesn't work in your code, to narrow down the problem, like why a css class is not working.
  • sheetworkers/javascript debugging: reading the web console to figure out what's going on with your sheetworkers. Open the console and keep an eye on it when you use the sheet like normally & see what it reports.
    • Example: If you add something like console.log("ifWounded is trigger") or console.log("Set strength mod to" + strmod)() in your sheetworkers, you can see what steps that take place, what is left out, and know what values your variables have at different stages.)
    • JS Debugging in Chrome, and in Firefox

Related Pages