Scribd Logo
Carica

Benvenuto in Scribd!

  • Lecture 29 - Framework Aside Default Values

    Caricato da

    Tim Pron
    36 visualizzazioni1 pagina
    The document discusses how code from multiple script tags on an HTML page is executed, with the scripts treated as if in a single file and global scope. It demonstrates how variables from different libraries can collide if not namespaced properly, but that libraries can define default values to avoid collisions.

    Descrizione originale:

    Titolo originale

    Lecture 29 - Framework Aside Default Values.txt

    Copyright

    © © All Rights Reserved

    Formati disponibili

    TXT, PDF, TXT o leggi online da Scribd

    Hai trovato utile questo documento?

    Questo contenuto è inappropriato?

    Segnala questo documento
    The document discusses how code from multiple script tags on an HTML page is executed, with the scripts treated as if in a single file and global scope. It demonstrates how variables from different libraries can collide if not namespaced properly, but that libraries can define default values to avoid collisions.

    Copyright:

    © All Rights Reserved
    Scarica in formato TXT, PDF, TXT o leggi online su Scribd
    Segnala contenuti inappropriati
    36 visualizzazioni1 pagina

    Lecture 29 - Framework Aside Default Values

    Caricato da

    Tim Pron
    The document discusses how code from multiple script tags on an HTML page is executed, with the scripts treated as if in a single file and global scope. It demonstrates how variables from different libraries can collide if not namespaced properly, but that libraries can define default values to avoid collisions.

    Copyright:

    © All Rights Reserved
    Scarica in formato TXT, PDF, TXT o leggi online su Scribd
    Segnala contenuti inappropriati
    di 1

    How what we have been discussing is used inside popular frameworks

    for our purposes, a framework and a library are the same thing

    Default Values

    index.html
    <html>
    <head>

    </head>
    <body>
    <script src="lib1.js"></script>
    <script src="lib2.js"></script>
    <script src="app.js"></script>
    </body>
    </html>

    lib1.js
    var libraryName = "Lib 1";

    lib2.js
    var libraryName = "Lib 2";

    app.js
    console.log(libraryName);

    output:
    Lib 2

    what happens:
    a. the 3 script tags are not creating new execution contexts. they are not
    separating the code in any way. They are simply stacking the code one on top of
    another then run them all as if they were inside a single file.

    they were all treated as global variables in the gloabal execution context,
    attached to the window object.

    in the exxample, we have seen that libraries can collide/overwrite.

    edit: in lib2.js
    window.libraryName = window.libraryName || "Lib 2";

    output:
    Lib 1

    Potrebbero piacerti anche