perhaps? Any load speed disadvantage? Example below:
> Why I needed it? For the sake of easy management, perhaps?
I do not need it. I do not know know why you did.
> Any load speed disadvantage?
There is no load speed advantage in this to begin with: Provided that it
works, a script needs to be loaded, compiled and interpreted in order to
load another script.
> Example below:
You do not need to escape ETAGO's within external script resources as they
are not parsed by a markup parser (however, escaping them always can ease
You might want to escape `libraryName'. Anyway, you cannot be sure if and
where this `script' element is inserted if the statement is in an external
With internal scripts, you simply put the script element where it belongs
(before the `script' element that includes code that uses features defined
in the former) and forget about the document.write() nonsense.
-- Richard Cornford, cljs, <email@example.com>
There is one possible disadvantage with including files externally
concerning debugging. This only really concerns Internet explorer.
If you have an error in one of your scripts, you'll get a line number,
but the number will not correspond to the correct line unless all the
JS code is inline with the HTML.
To explain this, if you have the following code...
and somescript.js looks like
You would normall get an error on line 2, but as the script is
included on line 3, the error message will tell you its on line 5, and
when multiple scripts are included it can be a nightmare to find the
|All times are GMT. The time now is 10:25 PM.|
Powered by vBulletin®. Copyright ©2000 - 2014, vBulletin Solutions, Inc.
SEO by vBSEO ©2010, Crawlability, Inc.