|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: Full release of FRC Dashboard
While this is certainly a cool idea, I think it could benefit from better addon integration - copying and pasting code isn't really the best way to do addons IMO.
Self-contained addons could include all of their own html, css, and javascript code, and your dashboard could do the heavy lifting to import them instead of the user ![]() |
|
#2
|
||||
|
||||
|
Re: Full release of FRC Dashboard
I've looked at doing this a lot of times, but I can't figure out a good way to do it while preserving the customizability of the addons.
Also, since most of the addons require adding a case to a switch statement, I haven't figured out how to begin. Any ideas? |
|
#3
|
||||
|
||||
|
Re: Full release of FRC Dashboard
Welcome to software design! Where you try to make sure to retain features while nailing things down into a concrete framework.
You can create an add-ons folder, and within that a folder for each add-on you want to load. In each add-on folder you put an html file with the add-on snippet, a css file, and a js file with the code. Each js file could look like this Code:
module.exports = {
name: "MyAddon",
tag: "my-addon",
init: function(htmlNode, etc) {
// js code here
}
}
Code:
<!-- other dash stuff --> <my-addon></my-addon> Just an idea |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|