<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Alexey Boyko on Medium]]></title>
        <description><![CDATA[Stories by Alexey Boyko on Medium]]></description>
        <link>https://medium.com/@alexey-boyko?source=rss-abf66e846ea1------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*ru-ZcWtC2cscqFvd4qu-HA.jpeg</url>
            <title>Stories by Alexey Boyko on Medium</title>
            <link>https://medium.com/@alexey-boyko?source=rss-abf66e846ea1------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 10:47:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@alexey-boyko/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[DGRM is seeing a surge of interest on GitHub]]></title>
            <link>https://alexey-boyko.medium.com/dgrm-is-seeing-a-surge-of-interest-on-github-e50ebc520ecc?source=rss-abf66e846ea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/e50ebc520ecc</guid>
            <category><![CDATA[github]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Alexey Boyko]]></dc:creator>
            <pubDate>Fri, 14 Aug 2026 08:26:36 GMT</pubDate>
            <atom:updated>2026-08-14T08:26:36.090Z</atom:updated>
            <content:encoded><![CDATA[<p>Just discovered that for three days in a row, developers have been giving 30 stars a day on GitHub. This hasn’t happened in two years. Thanks to you and them.</p><figure><img alt="DGRM GitHub stars statistic" src="https://cdn-images-1.medium.com/max/1024/1*hiCLZOuGTsJPGuk3Qc6UJQ.png" /><figcaption>DGRM GitHub stars statistic</figcaption></figure><p>More news: The project is now supported by a strong partner. We’re working hard on the update.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e50ebc520ecc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript: Working with Large Files in the Browser. Creating 5GB Files in the Browser]]></title>
            <link>https://levelup.gitconnected.com/javascript-working-with-large-files-in-the-browser-creating-5gb-files-in-the-browser-9b236a42731d?source=rss-abf66e846ea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b236a42731d</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Alexey Boyko]]></dc:creator>
            <pubDate>Mon, 08 Jun 2026 04:17:55 GMT</pubDate>
            <atom:updated>2026-06-08T04:17:55.438Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="http://dgrm.net/">Online board DGRM.net</a> caches files in a persistent cache. The persistent cache isn’t deleted when you close a tab. I’ll explain how to store large files in your browser.</p><figure><img alt="Fig. 1. Memory consumption when a file is fully loaded into memory" src="https://cdn-images-1.medium.com/max/945/1*BcP-S9JixXJRp7QnbbMZyQ.png" /><figcaption><em>Figure 1. Memory consumption when a file is fully loaded into memory</em></figcaption></figure><h3>File cache on origin private file system (OPFS)</h3><p>A persistent file cache can be created using the cache API, indexedDB, or OPFS. OPFS is considered the fastest. OPFS is a virtual file system. You can create files and folders. Other websites will not have access to your files.</p><h3>Writing files to OPFS</h3><p>You can get a link to a file on the user’s device using HTMLInputElement. This will prevent the file data from being loaded into memory.</p><pre>/**<br> * @param {string} [accept]<br> * @returns {Promise&lt;File&gt;}<br> */<br>const fileInputOpen = accept =&gt; new Promise((resolve, reject) =&gt; {<br>    const input = document.createElement(&#39;input&#39;);<br>    input.type = &#39;file&#39;;<br>    input.multiple = false;<br>    input.accept = accept;<br>    input.style.display = &#39;none&#39;;<br>    document.body.appendChild(input);<br><br>    const dispose = () =&gt; input?.remove();<br><br>    input.oncancel = () =&gt; {<br>        resolve(null);<br>        dispose();<br>    };<br>    input.onchange = () =&gt; {<br>        resolve((!input.files?.length) ? null : input.files[0]);<br>        dispose();<br>    };<br><br>    input.click();<br>});</pre><p><em>Listing 1. Getting a link to a file</em></p><p>Writing a file to OPFS — Listing 2.</p><pre>/**<br> * @param {string} fileName<br> * @param {Blob} blob<br> */<br>const fileAdd = async (fileName, blob) =&gt; {<br>    const dir = await navigator.storage.getDirectory();<br><br>    const writable =<br>        await (await dir.getFileHandle(fileName, { create: true }))<br>            .createWritable();<br><br>    // (1)  FireFox will load all file into memory<br>    //      Chrome drop exception<br>    // await writable.write(await blob.bytes());<br><br>    // (2)  very slow in FireFox<br>    // await writable.write(blob);<br><br>    // (3)  works in Chrome and FireFox.<br>    //      In Chrome slower then (2)<br>    await blob.stream().pipeTo(writable, { preventClose: true });<br><br>    await writable.close();<br>};</pre><p><em>Listing 2. Writing a file to OPFS</em></p><p>Listing 2 shows three file copy options in OPFS. I tested this on a 5 GB file on Windows 11 and Ubuntu.</p><h3>Option (1) blob.bytes()</h3><p>Option (1) shows loading the entire file into memory. RAM consumption is clearly visible (Figure 2). Firefox on Windows will load the entire file into memory, while on Ubuntu it will load 2 GB into memory and throw an exception. Chrome will throw an exception.</p><figure><img alt="Fig. 2. FireFox (1) file.bytes(). Memory consumption when loading a file into memory." src="https://cdn-images-1.medium.com/max/945/1*BcP-S9JixXJRp7QnbbMZyQ.png" /><figcaption><em>Figure 2. FireFox (1) file.bytes(). Memory consumption when loading a file into memory.</em></figcaption></figure><h3>Option (2) writable.write(blob)</h3><p>(2) Works quickly in Chrome — 23 seconds. In Firefox, it’s very slow — over a minute. The file isn’t loaded into memory entirely, but is copied in chunks — see Figures 3 and 4. The graphs are similar in Chrome and Firefox, only the time in Firefox is stretched.</p><figure><img alt="Figure 3. Chrome (2) writable.write(file). Memory usage" src="https://cdn-images-1.medium.com/max/937/1*oGIC6LvjlyA2c4zGC73MVw.png" /><figcaption><em>Figure 3. Chrome (2) writable.write(file). Memory usage</em></figcaption></figure><figure><img alt="Figure 4. Chrome (2) wr.writable(file). Disk accesses" src="https://cdn-images-1.medium.com/max/932/1*R6BtxF6TyjvEoH7iGBPchA.png" /><figcaption><em>Figure 4. Chrome (2) wr.writable(file). Disk accesses</em></figcaption></figure><h3>Option (3) blob.stream().pipeTo(writable)</h3><p>Works well in Chrome and Firefox. In Chrome, it’s slower than (2). The graphs are similar to (2). Option (3) with pipeTo turned out to be better (Table 1).</p><figure><img alt="Table 1. Comparison of file creation methods in OPFS" src="https://cdn-images-1.medium.com/max/1024/1*PS8Mq6J0uonSXYpcUBzCaA.png" /><figcaption><em>Table 1. Comparison of file creation methods in OPFS</em></figcaption></figure><h3>Writing a portion of a file to OPFS</h3><p>To write a portion of a file to OPFS, use blob.slice(). Listing 3 — writing a portion of a file to OPFS without loading the entire file into memory.</p><pre>const file = await fileInputOpen(); <br>if (!file) { return; } <br> <br>await fileAdd(<br>    file.name, <br>    // upload second byte <br>    file.slice(1, 2));</pre><p><em>Listing 3. Writing part of a file to OPFS without loading the entire file into memory</em></p><p>For information on how to store a lot of different data in one large file, see <a href="https://medium.com/codex/javascript-handling-large-files-in-the-browser-part-1-2-reading-large-files-4e820f59d97f">the first part of the article</a>.</p><h3>Reading from OPFS</h3><p>A file from OPFS can be output to an image, &lt;audio&gt;, &lt;video&gt; — listing 4.</p><pre>const img =<br>    /** @type {HTMLImageElement} */(document.getElementById(&#39;img&#39;));<br><br>const dir = await navigator.storage.getDirectory();<br>img.src = URL.createObjectURL(<br>    await (await dir.getFileHandle(&#39;1.png&#39;)).getFile()<br>);<br><br>// don&#39;t forget to revoke object url when delete img<br>// URL.revokeObjectURL(img.src)</pre><p><em>Listing 4. Displaying an image from OPFS</em></p><p>Downloading a file from OPFS — Listing 5.</p><pre>/**<br> * @param {Blob} blob<br> * @param {string} name<br> */<br>const fileDownload = (blob, name) =&gt; {<br>    const link = document.createElement(&#39;a&#39;);<br>    link.download = name;<br>    link.href = URL.createObjectURL(blob);<br>    link.click();<br>    URL.revokeObjectURL(link.href);<br>    link.remove();<br>};<br><br>//<br>// usage<br><br>const dir = await navigator.storage.getDirectory();<br>fileDownload(<br>    await (await dir.getFileHandle(&#39;big.zip&#39;)).getFile(),<br>    &#39;big.zip&#39;<br>);</pre><p><em>Listing 5. Downloading a file from OPFS</em></p><p>Google claims you can download files up to 1 GB this way. In reality, 5 GB downloads are no problem in Chrome and Firefox on Windows and Ubuntu. RAM consumption doesn’t increase.</p><h3>Creating files on the user’s device</h3><p>Chrome can write files directly to the user’s file system. Writing to a file can be done in chunks; the API is the same as in OPFS — Listing 6.</p><pre>if (window[&#39;showSaveFilePicker&#39;]) {<br>    /** @type {FileSystemFileHandle} */<br>    const file =<br>        // @ts-ignore<br>        await window.showSaveFilePicker({<br>            suggestedName: &#39;my.png&#39; });<br><br>    const writable = await file.createWritable();<br><br>    // write your data<br>    // await blob1.stream().pipeTo(writable, { preventClose: true });<br>    // await blob2.stream().pipeTo(writable, { preventClose: true });<br><br>    await writable.close();<br>}</pre><p><em>Listing 6. Creating a file on the user’s device</em></p><p>In other browsers, you will have to create a temporary file in OPFS and download it using a link — see Listing 5.</p><h3>Self-promotion</h3><p>Recently added to <a href="http://dgrm.net/">DGRM.net</a> audio and video. I use it for guitar lessons — it’s convenient. Give it a try.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*b18SzJ-vZM1d9clGX-5HMw.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b236a42731d" width="1" height="1" alt=""><hr><p><a href="https://levelup.gitconnected.com/javascript-working-with-large-files-in-the-browser-creating-5gb-files-in-the-browser-9b236a42731d">JavaScript: Working with Large Files in the Browser. Creating 5GB Files in the Browser</a> was originally published in <a href="https://levelup.gitconnected.com/">Level Up Coding</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DGRM.net whiteboard: You can now add audio and video to the board]]></title>
            <link>https://alexey-boyko.medium.com/dgrm-net-whiteboard-you-can-now-add-audio-and-video-to-the-board-09913f0b06c8?source=rss-abf66e846ea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/09913f0b06c8</guid>
            <category><![CDATA[collaboration]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[whiteboards]]></category>
            <category><![CDATA[miro]]></category>
            <dc:creator><![CDATA[Alexey Boyko]]></dc:creator>
            <pubDate>Sun, 10 May 2026 07:56:54 GMT</pubDate>
            <atom:updated>2026-05-10T07:56:54.415Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/888/1*cXpWKMJ8-VsZNp5q-BQFpA.png" /><figcaption>Audio and video on DGRM.net whiteboard</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=09913f0b06c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[JavaScript: Handling Large Files in the Browser. Part 1/2: Reading Large Files]]></title>
            <link>https://medium.com/codex/javascript-handling-large-files-in-the-browser-part-1-2-reading-large-files-4e820f59d97f?source=rss-abf66e846ea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/4e820f59d97f</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[typescript]]></category>
            <dc:creator><![CDATA[Alexey Boyko]]></dc:creator>
            <pubDate>Sun, 26 Apr 2026 04:52:00 GMT</pubDate>
            <atom:updated>2026-04-27T11:30:47.258Z</atom:updated>
            <content:encoded><![CDATA[<p>The <a href="https://dgrm.net/">DGRM.net online whiteboard</a> stores data in PNG images. With attachments, the files become large. I’ll explain how data is stored in PNG files.</p><figure><img alt="Fig. 1. DGRM.net opens diagrams from PNG images." src="https://cdn-images-1.medium.com/max/1024/1*uvN-umZQWtHyMP1dt2D8Bg.gif" /><figcaption><em>Fig. 1. DGRM.net opens diagrams from PNG images.</em></figcaption></figure><h3>PNG file format</h3><p>A PNG file consists of blocks. These blocks contain various information. For example, the tIME block contains the editing date.</p><p>At the end comes the required IEND block. After the IEND, you can append your own data to the file without breaking the image. This is what DGRM uses: it appends its data to the end of the PNG file.</p><p>The resulting file looks like this: Figure 2.</p><figure><img alt="Fig. 2. Image file with DGRM data" src="https://cdn-images-1.medium.com/max/1024/1*wgOb76M8MVoLRJ67Yl_Vrg.png" /><figcaption><em>Fig. 2. Image file with DGRM data</em></figcaption></figure><p>PNG block structure — Fig. 3.</p><figure><img alt="Fig. 3. PNG block structure" src="https://cdn-images-1.medium.com/max/1024/1*mLkfa01Up4bi0Xm7fJ87pA.png" /><figcaption><em>Fig. 3. PNG block structure</em></figcaption></figure><p>Storage in DGRM Data is also organized into blocks, albeit in a slightly different format. The first block is for JSON figures, followed by attachments.</p><h3>Reading from a file without loading the entire file into memory</h3><p>You can get a reference to a file on the user’s device using HTMLInputElement. This method will not load the file data into memory (Listing 1).</p><pre>/**<br> * @param {string} accept<br> * @param {FileCallback} callBack<br> * @param {(evt:Event)=&gt;void} cancelCallBack<br> */<br>const fileInputOpen = (accept, callBack, cancelCallBack) =&gt; {<br>    const input = document.createElement(&#39;input&#39;);<br>    input.type = &#39;file&#39;;<br>    input.multiple = false;<br>    input.accept = accept;<br>    input.style.display = &#39;none&#39;;<br>    document.body.appendChild(input);<br><br>    const dispose = () =&gt; input?.remove();<br><br>    input.oncancel = evt =&gt; {<br>        cancelCallBack(evt);<br>        dispose();<br>    };<br>    input.onchange = () =&gt; {<br>        callBack((!input.files?.length) ? null : input.files[0]);<br>        dispose();<br>    };<br><br>    input.click();<br>}<br><br>Listing 1. Getting a link to a file</pre><p>When opening a file, you need to find where the DGRM data begins, i.e., the IEND block.</p><p>To search, you need to iterate through the blocks from the beginning of the file to the desired block. However, it’s not advisable to load the entire file into memory.</p><p>The pngChunkDataPositionGet function reads only 8 bytes at a time (length + header) and scrolls to the next block until it finds the desired one (Listing 2).</p><pre>// IEND<br>const PNG_CHUNK_END_NAME_UINT32 = 1229278788;<br><br><br>/**<br> * @param {Blob} pngFile, @param {number} chankNameUint32<br> * @returns {Promise&lt;[startBytePosition:number, endBytePosition:number]&gt;}<br> */<br>const pngChunkDataPositionGet = async (pngFile, chankNameUint32) =&gt; {<br>    /** @param {number} pos */<br>    const uint32Get =<br>        async pos =&gt; uint32From4BytesBlob(pngFile.slice(pos, pos + 4));<br><br>    /** @type {number} */ let chunkPosition = 8; // 8 byte - png signature<br>    /** @type {number} */ let chunkLenght;<br>    /** @type {number} */ let chunkName;<br>    /** @type {number} */ let chunkDataStart;<br>    /** @type {number} */ let chunkDataEnd;<br><br>    do {<br>        chunkLenght = await uint32Get(chunkPosition);<br>        chunkName = await uint32Get(chunkPosition + 4);<br>        chunkDataStart = chunkPosition + 8;<br>        chunkDataEnd = chunkDataStart + chunkLenght;<br><br>        if (chunkName === chankNameUint32) {<br>            return [chunkDataStart, chunkDataEnd];<br>        }<br><br>        chunkPosition = chunkDataEnd + 4;<br>    } while (chunkName !== PNG_CHUNK_END_NAME_UINT32);<br><br>    // looking for end chunk<br>    if (chunkName === chankNameUint32) {<br>        return [chunkDataStart, chunkDataEnd];<br>    }<br><br>    return null;<br>};<br><br>Listing 2. Searching for a block in a PNG file</pre><p>Scrolling large PNGs to the IEND is slow. Therefore, it makes sense to add a custom block at the beginning of the file. In this block, specify the number of bytes to the end of the DGRM Data, i.e., the size of the PNG image without the additional DGRM Data.</p><figure><img alt="Figure 4. Custom dgRp block at the beginning of the PNG file. Indicates the beginning of the DGRM data.." src="https://cdn-images-1.medium.com/max/1024/1*KxTXfsSX6Pi4pxaylLdShw.png" /><figcaption><em>Figure 4. Custom dgRp block at the beginning of the PNG file. Indicates the beginning of the DGRM data..</em></figcaption></figure><p>In DGRM Data, the first block is JSON figures, then come the attachment blocks — Fig. 5.</p><figure><img alt="Figure 5. DGRM Data blocks" src="https://cdn-images-1.medium.com/max/1024/1*pyRA-fy8fJFYt4j9z8FS4Q.png" /><figcaption><em>Figure 5. DGRM Data blocks</em></figcaption></figure><p>The JSON block is loaded into memory in its entirety. Attachments are loaded only if they aren’t in the cache.</p><p>Attachments can be large, so loading them entirely into memory is also not recommended. More details in the second part of the article.</p><p>The second part of the article discusses generating large files in the browser.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4e820f59d97f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/codex/javascript-handling-large-files-in-the-browser-part-1-2-reading-large-files-4e820f59d97f">JavaScript: Handling Large Files in the Browser. Part 1/2: Reading Large Files</a> was originally published in <a href="https://medium.com/codex">CodeX</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DGRM.net whiteboard / Now flowcharts from a computer open 15 times faster]]></title>
            <link>https://alexey-boyko.medium.com/dgrm-net-whiteboard-now-flowcharts-from-a-computer-open-15-times-faster-b8f7f2f3be63?source=rss-abf66e846ea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/b8f7f2f3be63</guid>
            <category><![CDATA[whiteboarding]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[flowchart]]></category>
            <dc:creator><![CDATA[Alexey Boyko]]></dc:creator>
            <pubDate>Tue, 21 Apr 2026 16:37:55 GMT</pubDate>
            <atom:updated>2026-04-21T16:37:55.411Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uvN-umZQWtHyMP1dt2D8Bg.gif" /><figcaption>DGRM.net opens flowcharts from PNG images</figcaption></figure><p>If you store large diagrams on your computer (not in the cloud), you’ll definitely notice.<br>Loading is 15 times faster. Saving hasn’t gotten much faster, but it uses fewer resources. Files with large image content have become 20% smaller.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b8f7f2f3be63" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DGRM.net whiteboard / Blocks have become more compact]]></title>
            <link>https://alexey-boyko.medium.com/dgrm-net-whiteboard-blocks-have-become-more-compact-714246169e03?source=rss-abf66e846ea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/714246169e03</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[flowchart]]></category>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[whiteboarding]]></category>
            <dc:creator><![CDATA[Alexey Boyko]]></dc:creator>
            <pubDate>Thu, 19 Mar 2026 05:15:54 GMT</pubDate>
            <atom:updated>2026-03-19T05:15:54.504Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Now the blocks are more compact Previously, blocks were expanded by 2 cells, now by 1." src="https://cdn-images-1.medium.com/max/855/1*9le2pahBaAIzfMDurmV1Dg.png" /><figcaption>Now the blocks are more compact</figcaption></figure><p>Previously, blocks were expanded by 2 cells, now by 1.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=714246169e03" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DGRM.net whiteboard / You can now set text alignment]]></title>
            <link>https://alexey-boyko.medium.com/dgrm-net-whiteboard-you-can-now-set-text-alignment-bb6396894d8d?source=rss-abf66e846ea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb6396894d8d</guid>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[flowchart]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[whiteboards]]></category>
            <dc:creator><![CDATA[Alexey Boyko]]></dc:creator>
            <pubDate>Sat, 31 Jan 2026 04:02:53 GMT</pubDate>
            <atom:updated>2026-01-31T04:02:53.375Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_zZDpUKriPk0QGQchItdyw.png" /><figcaption>Text alignment settings</figcaption></figure><p>You can now set text alignment. Useful for large blocks.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb6396894d8d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DGRM.net whiteboard / Now the small figures are always on top]]></title>
            <link>https://alexey-boyko.medium.com/dgrm-net-whiteboard-now-the-small-figures-are-always-on-top-6f50a031f0d6?source=rss-abf66e846ea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f50a031f0d6</guid>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[flowchart]]></category>
            <category><![CDATA[whiteboards]]></category>
            <dc:creator><![CDATA[Alexey Boyko]]></dc:creator>
            <pubDate>Wed, 07 Jan 2026 06:40:00 GMT</pubDate>
            <atom:updated>2026-01-07T06:40:00.610Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*5_Qy_hsV46eSpS_aEbZ5Fw.gif" /><figcaption>When big background shape became small — it goes to the top.</figcaption></figure><p>The position of the figures is determined automatically. No extra buttons.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f50a031f0d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Flowchart editor DGRM.net has become even more productive]]></title>
            <link>https://alexey-boyko.medium.com/flowchart-editor-dgrm-net-has-become-even-more-productive-9d488b0ff4cd?source=rss-abf66e846ea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d488b0ff4cd</guid>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[flowchart]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Alexey Boyko]]></dc:creator>
            <pubDate>Wed, 10 Dec 2025 10:03:46 GMT</pubDate>
            <atom:updated>2025-12-10T10:03:46.885Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Flowchart editor DGRM.net has become even more productive" src="https://cdn-images-1.medium.com/max/1024/1*yxSE-ebvaowJ_-3NHjmkJQ.png" /><figcaption>Flowchart editor DGRM.net has become even more productive</figcaption></figure><p>For diagrams with images, memory savings reach 10x.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d488b0ff4cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Diagramming Tool DGRM.net / Move the diagram by holding down the mouse wheel]]></title>
            <link>https://alexey-boyko.medium.com/diagramming-tool-dgrm-net-move-the-diagram-by-holding-down-the-mouse-wheel-3ed19659c0c8?source=rss-abf66e846ea1------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ed19659c0c8</guid>
            <category><![CDATA[diagrams]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[flowchart]]></category>
            <category><![CDATA[whiteboarding]]></category>
            <category><![CDATA[whiteboards]]></category>
            <dc:creator><![CDATA[Alexey Boyko]]></dc:creator>
            <pubDate>Fri, 21 Nov 2025 16:19:18 GMT</pubDate>
            <atom:updated>2025-11-21T16:19:18.333Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*GB30bCafmgPY2eBBduByQg.gif" /><figcaption>Move the diagram by holding down the mouse wheel</figcaption></figure><p>You can now move the diagram by holding down the mouse wheel.</p><p>This is useful if there’s not enough space on the diagram.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ed19659c0c8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>