plugin:jokuwiki
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| plugin:jokuwiki [2015-09-05 05:59] – Aleksandr | plugin:jokuwiki [2019-01-13 15:29] (current) – Added bugtracker LarsDW223 | ||
|---|---|---|---|
| Line 6: | Line 6: | ||
| email : colin.mckinnon@gmail.com | email : colin.mckinnon@gmail.com | ||
| type : syntax | type : syntax | ||
| - | lastupdate : 2013-06-24 | + | lastupdate : 2016-07-06 |
| compatible : Adora Belle, Weatherwax | compatible : Adora Belle, Weatherwax | ||
| depends | depends | ||
| conflicts | conflicts | ||
| similar | similar | ||
| - | tags : javascript, | + | tags : javascript, |
| - | downloadurl: | + | downloadurl: |
| + | bugtracker : https:// | ||
| + | sourcerepo : https:// | ||
| ---- | ---- | ||
| Line 73: | Line 75: | ||
| - Since processing of the content (arguments to the initiator) is deferred, the javascript need not be loaded before the Jokuwiki tag is declared in the html - i.e. script tags can be moved to the bottom, and/or use the defer/async tags or be loaded via AJAX. In short, the page is not blocked loading javascript content. | - Since processing of the content (arguments to the initiator) is deferred, the javascript need not be loaded before the Jokuwiki tag is declared in the html - i.e. script tags can be moved to the bottom, and/or use the defer/async tags or be loaded via AJAX. In short, the page is not blocked loading javascript content. | ||
| - Even without the overhead of jQuery, the amount of content which is different between individual pages is often less than 50% of the data downloaded from the server. Jokuwiki provides hooks to integrate [[https:// | - Even without the overhead of jQuery, the amount of content which is different between individual pages is often less than 50% of the data downloaded from the server. Jokuwiki provides hooks to integrate [[https:// | ||
| - | - Actually, halving the content size isn't really a //great// performance saving - with HTTP it's all about the latency. But eliminating the need to re-fetch (even from cache), re-parse and re-compile the javascript on each page (along with parsing the CSS) does represent a big performance boost - on a bare installation of Weatherwax on my development machine this saves between 250 and 350 milliseconds per page load. | + | - Actually, halving the content size isn't really a //great// performance saving - with HTTP it's all about the latency. But eliminating the need to re-fetch (even from cache), re-parse and re-compile the javascript on each page (along with parsing the CSS) does represent a big performance boost - on a bare installation of Weatherwax on my development machine this saves around 450 milliseconds per page load. |
| ===== Security Enhancement ===== | ===== Security Enhancement ===== | ||
plugin/jokuwiki.1441425546.txt.gz · Last modified: 2015-09-05 05:59 by Aleksandr