| function fetchPageAssets() { | |
| let images = document.querySelectorAll('img[src*=files]'); | |
| images.forEach(function(image) { | |
| files.push('<a href="' + image.src.replace(/_60x60/, "") + '"><img src="' + image.src.replace(/_60x60/, "") + '">'); | |
| }); | |
| } | |
| function downloadListFile() { | |
| let button = document.createElement("a"); | |
| let data = 'data:application/octet-stream;base64,' + window.btoa(files.join('\n')); |
Making multiple MySQL versions work with Homebrew was tricky to say the least. Fortunately there are 2 new easy ways that I learned of to achieve this.
As @4unkur and @henrytirla commented below, there is this extremely easy to use app called DBngin, which lets you setup multiple databases (not only MySQL) simultaneously using different ports:
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| <ul class="prev-next cf"> | |
| {% set params = {section: 'blog', order: 'postDate desc', limit: null} %} | |
| {% set entry_prev = entry.getPrev(params) %} | |
| {% set entry_next = entry.getNext(params) %} | |
| {% if entry_prev %}<li class="prev"><a title="{{ entry_prev.title }}" href="{{entry_prev.url}}">Previous Post</a></li>{% endif %} | |
| {% if entry_next %}<li class="next"><a title="{{ entry_next.title }}" href="{{entry_next.url}}">Next Post</a></li>{% endif %} | |
| </ul> |