Arko

2022-01-29T00:00:00+00:00

arko is a small library providing three pixel manipulation algorithms :

Brush : Create some kind of brush effect</li>
Slim : Copy a pixel over a ramdom numbers of pixel on the same line or column</li>

Sort : A classic pixel sorting</li> </ul>

The library also contains a minimal image convertion tool (supporting png and jpg).

How to use it</h2>

All of the algorithms can be used in four directions :

bottom to top</li>
left to right</li>
right to left</li>

top to bottom</li> </ul>

For algorithms using colors here are the complete list of available colors : "white", "black", "grey", "red", "yellow", "green", "cyan", "blue", "magenta".

Brush</h3>

Params :

in_img(str) : path to the input image</li>
out_img(ste) : path to the output image</li>
force_ouput_overwrite(bool) : flag to allow overwriting of the output image if present</li>
proba(i32) : the probability for the algorithm to have effect on a pixel</li>
min(i32) : the minimum of pixel affected when the algorithm starts</li>
max(i32) : the maximum of pixel affected when the algorithm starts</li> </ul>
Examples :
arko::brush_bottom_to_top("input.png", "btt.png",true, 100, 4, 20); arko::brush_left_to_right("input.png", "ltr.png",true, 100, 4, 20); arko::brush_right_to_left("input.png", "rtl.png",true, 100, 4, 20); arko::brush_top_to_bottom("input.png", "ttb.png",true, 100, 4, 20); </code></pre> Slim</h3> Probability global</h4> When using these functions the probability is the same applyed to all colors. Params : in_img(str) : path to the input image</li> out_img(ste) : path to the output image</li> force_ouput_overwrite(bool) : flag to allow overwriting of the output image if present</li> proba(i32) : the probability for the algorithm to effect the next pixel when activated</li> colors(Vec < Colors >) : the list of colors affect by the algorithm</li> </ul> Examples : arko::slim_bottom_to_top_per_color("input.png", "btt.png",true, vec![(Colors::Red, 20), (Colors::Yellow, 34), (Colors::Green, 56), (Colors::Cyan, 45), (Colors::Blue, 64), (Colors::Magenta, 23)]); arko::slim_left_to_right_per_color("input.png", "ltr.png",true, vec![(Colors::Red, 20), (Colors::Yellow, 34), (Colors::Green, 56)]); arko::slim_right_to_left_per_color("input.png", "rtl.png",true, vec![(Colors::Green, 56), (Colors::Cyan, 45), (Colors::Blue, 64)]); arko::slim_top_to_bottom_per_color("input.png", "ttb.png",true, vec![(Colors::Cyan, 45), (Colors::Blue, 64), (Colors::Magenta, 23)]); </code></pre> Probability per colors</h4> When using these functions the probability is provided per color. Params : in_img(str) : path to the input image</li> out_img(ste) : path to the output image</li> force_ouput_overwrite(bool) : flag to allow overwriting of the output image if present</li> colors_proba(Vec<(Colors, i32)>) : affected colors with their probability</li> </ul> Examples : arko::slim_bottom_to_top_per_color("input.png", "btt.png",true, vec![(Colors::Red, 20), (Colors::Yellow, 34), (Colors::Green, 56), (Colors::Cyan, 45), (Colors::Blue, 64), (Colors::Magenta, 23)]); arko::slim_left_to_right_per_color("input.png", "ltr.png",true, vec![(Colors::Red, 20), (Colors::Yellow, 34), (Colors::Green, 56)]); arko::slim_right_to_left_per_color("input.png", "rtl.png",true, vec![(Colors::Green, 56), (Colors::Cyan, 45), (Colors::Blue, 64)]); arko::slim_top_to_bottom_per_color("input.png", "ttb.png",true, vec![(Colors::Cyan, 45), (Colors::Blue, 64), (Colors::Magenta, 23)]); </code></pre> Sort (Brut)</h3> These functions will affect the entire image and sort pixels either horizontally either vertically. Params : in_img(str) : path to the input image</li> out_img(ste) : path to the output image</li> force_ouput_overwrite(bool) : flag to allow overwriting of the output image if present</li> </ul> Examples : arko::sort_brut_bottom_to_top("input.png", "btt.png", true); arko::sort_brut_left_to_right("input.png", "ltr.png", true); arko::sort_brut_right_to_left("input.png", "rtl.png", true); arko::sort_brut_top_to_bottom("input.png", "ttb.png", true); </code></pre> Sort (Smart)</h3> Params : in_img(str) : path to the input image</li> out_img(ste) : path to the output image</li> force_ouput_overwrite(bool) : flag to allow overwriting of the output image if present</li> detection_type(i32) : 0 : detection by lightness</li> 1 : detection by color group</li> </ul> </li> detection_min(i32) : the minimum of pixel affected when the algorithm starts (first range)</li> detection_max(i32) : the maximum of pixel affected when the algorithm starts (first range)</li> multiple_range(bool) : either use one or two ranges</li> detection_min_2(i32) : the minimum of pixel affected when the algorithm starts (second range)</li> detection_max_2(i32) : the maximum of pixel affected when the algorithm starts (second range)</li> sorting_by(i32) : 0 : sorting by hue</li> 1 : sorting by saturation</li> </ul> </li> </ul> Examples : arko::sort_bottom_to_top("input.png", "btt.png", true, 0, 50, 360, false, 0, 0, 1); arko::sort_left_to_right("input.png", "ltr.png", true, 0, 50, 360, false, 0, 0, 0); arko::sort_right_to_left("input.png", "rtl.png", true, 0, 50, 60, true, 70, 80, 1); arko::sort_top_to_bottom("input.png", "ttb.png", true, 0, 50, 60, true, 90, 100, 0); </code></pre> Converter</h3> Params : in_img(str) : path to the input image</li> out_img(ste) : path to the output image</li> force_ouput_overwrite(bool) : flag to allow overwriting of the output image if present</li> </ul> Examples : arko::convert("input.png", "output.jpg", true); </code></pre>

Danish memo

2022-01-05T00:00:00+00:00

</div>

Pronunciation</h2>

Æ Ø Å</h3>
Æ is pronounced like [ai] (lait)
Ø is pronounced like [eu] (heureux)
Å is pronounced like [o] (bol)

Soft D</h3>
When to use the soft d :

A vowel followed by -d or -dd</li>
A word ends with -et</li> </ul>
Exceptions :

A single syllable containing a vowel followed by -ds : the d become silent</li>
A single syllable containing a vowel followed by -dt : the d become silent</li> </ul> Here's a pretty good video</a> to help with the pronunciation.
Grammar</h2>
Grammatical gender</h3>
en : common gender
et : neutral gender
Group</th> Singular indefinite</th> Singular definite</th> Plural indefinite</th> Plural definite</th></tr></thead>

1</td> en bil</td> bilen</td> biler</td> bilerne</td></tr>
2</td> en dame</td> damen</td> damer</td> damerne</td></tr>
3</td> et hus</td> huset</td> huse</td> husene</td></tr>
4</td> en film</td> filmen</td> film-</td> filmene</td></tr> </tbody></table>
Possessive pronouns</h3>
Person</th> Singular common gender</th> Singular neutral gender</th> Plural</th></tr></thead>

jeg</td> min bil</td> mit hus</td> mine biler/huse</td></tr>
du</td> din bil</td> dit hus</td> dine biler/huse</td></tr>
han/hun</td> sin bil</td> sit hus</td> sine biler/huse</td></tr>
han</td> hans bil</td> hans hus</td> hans biler/huse</td></tr>
hun</td> hendes bil</td> hendes hus</td> hendes biler/huse</td></tr>
vi</td> vores bil</td> vores hus</td> vores biler/huse</td></tr>
i</td> jeres bil</td> jeres hus</td> jeres biler/huse</td></tr>
de</td> deres bil</td> deres hus</td> deres biler/huse</td></tr> </tbody></table>
When to use hans and hendes :

The possessive pronoun is alos the subject of the sentence (or part of the subject) : `Hans børn kommer i morgen</code> - His children come tomorrow.</li>`
When the subject is not the owner : Lisbeth kører hendes bil</code> - Lisbeth drive her car (in this case the car of someone else).</li> </ul> Attributive adjective</h3> Gender</th> Attributive adjective</th> Example</th> Translation</th></tr></thead> Singular common</td> Base form</td> vinen er god</td> the wine is good</td></tr> Singular neutral</td> Base form + -t</td> teaterstykket er godt</td> the theatre piece is good</td></tr> Plural common/neutral</td> Base form + -e</td> teaterstykkerne er gode</td> the wines are good</td></tr> </tbody></table> Doubling last consonants</h3> A name finishing by a brief vowel followed by a consonant will double the consonant in singular definite and plural forms. Group</th> Singular indefinite</th> Singular definite</th> Plural indefinite</th> Plural definite</th></tr></thead> 1</td> en søn</td> sønnen</td> sønner</td> sønnerne</td></tr> 2</td> en bus</td> bussen</td> busser</td> busserne</td></tr> 3</td> en nat</td> natten</td> nætter</td> nætterne</td></tr> 4</td> en kop</td> koppen</td> kopper</td> kopperne</td></tr> </tbody></table> Short answers</h3> Used to avoid answering a question by Yes or No only. If the question contains a modal verb (vil, skal, må, kan) or an auxiliary verb : the verb is reused in the answer. Construction : Ja + det + verb + subject.</li> Nej + det + verb + subject + ikke.</li> </ul> Example : Har du en kæreste? Ja, det har jeg.</code> - Do you have a girlfriend? Yes, I do. If the question doesn't contain such verb : the verb gør is used instead. Construction : Ja + det + gør + subject.</li> Nej + det + gør + subject + ikke.</li> </ul> Example : Arbejder du i weekenden? Je det gør jeg.</code> - Are you working on the weekend? Yes, I do. Subject inversion</h3> There are three scenarios for wich the subject is inverted : When asking a question (see Conjugation section below).</li> When starting a sentence with a complement or adverb : I weekenden arbejder jeg.</code> - On weekends I work.</li> When starting a sentence with a subordinate proposal : Når jeg arbejder, drikker jeg meget kaffe.</code> - When I work, I drink a lot of coffee.</li> </ol> Dynamic and static prepositions</h3> When there's an idea of movement the preposition to use is til : Jeg skal til Århus på lørdag.</code> - I go to Århus saturday.</li> When there's an idea of staticity the preposition to use is i : Lisa er I Berlin</code> - Lisa is in Berlin.</li> </ul> Vocabulary</h2> Short sentences</h3> Ja, det gør jeg : Yes, I do Vi ses senere : See you later Hvor skal du hen ? : Where are you going ? hen is an adverb that indicates movement Hvor arbejder du henne ? : Where are you working ? henne is an adverb that indicates immobility Hvornår kommer du hjem ? : When are you coming home ? hjem is an adverb that indicates movement Er du hjemme ? : Are you home? hjemme is an adverb that indicates immobility Om en halv time : In hal an hour Nogle : Some I weekenden : The weekend Jeg er 28 år : I'm 28 Hvad et der galt : What's wrong? Interrogative words</h3> Danish</th> English</th></tr></thead> Hvor</td> Where</td></tr> Hvem</td> Who</td></tr> Hvad</td> What</td></tr> Hvornår</td> When</td></tr> Hvofor</td> Why</td></tr> Hvordan</td> How</td></tr> Hvilken</td> Which</td></tr> Hvad for en</td> Which one</td></tr> Hvor mange</td> How many</td></tr> Hvor længe</td> How long</td></tr> Hvor gammel</td> How old</td></tr> Hvis</td> Whose</td></tr> Hvor lang tid</td> How much time</td></tr> </tbody></table> Useful words</h3> Mange : Many Meget : Much Altid : Always Normalt : Usually Tit : Often Nogle gang : Sometimes Ikke så tit : Not so often Aldrig : Never Numbers</h3> Number</th> Danish</th> Cardinal</th></tr></thead> 1</td> en /et</td> første</td></tr> 2</td> to</td> anden</td></tr> 3</td> tre</td> tredje</td></tr> 4</td> fire</td> fjerde</td></tr> 5</td> fem</td> femte</td></tr> 6</td> seks</td> sjette</td></tr> 7</td> syv</td> syvende</td></tr> 8</td> otte</td> ottende</td></tr> 9</td> ni</td> niende</td></tr> 10</td> ti</td> tiende</td></tr> 11</td> elleve</td> ellevte</td></tr> 12</td> tolv</td> tolvte</td></tr> 13</td> tretten</td> trettende</td></tr> 14</td> fjorten</td> fjortende</td></tr> 15</td> femten</td> femtende</td></tr> 16</td> seksten</td> sekstende</td></tr> 17</td> sytten</td> syttende</td></tr> 18</td> atten</td> attende</td></tr> 19</td> nitten</td> nittende</td></tr> 20</td> tyve</td> tyvende</td></tr> </tbody></table> Days</h3> Danish</th> English</th></tr></thead> Mandag</td> Monday</td></tr> Tirsdag</td> Tuesday</td></tr> Onsdag</td> Wednesday</td></tr> Torsdag</td> Thursday</td></tr> Fredag</td> Friday</td></tr> Lørdag</td> Saturday</td></tr> Søndag</td> Sunday</td></tr> </tbody></table> Conjugation</h2> Personal pronouns</h3> Danish</th> English</th></tr></thead> jeg</td> I</td></tr> du</td> you</td></tr> han / hun / den / det</td> he / she / it</td></tr> vi</td> we</td></tr> i</td> you</td></tr> de</td> they</td></tr> </tbody></table> Infinitive</h3> Most of the time finishing with -e and preceded by at. Example : at komme</code>. Present</h3> Most of the time finishing with -r. Example : jeg kommer</code>. Questions</h3> To ask a question, invert subject and verb position in the sentence. Negation</h3> To use the negation use ikke after the verb. Negative questions</h3> Construction : Verb + subject + ikke. Modal verbs</h3> At skulle (should) : Can be used to express the future. Construction : Present form of at skulle + infinitive of main verb. Example : Jeg skal arbejde i weekenden</code> - I will work this weekend. At kunne (could/know) : Is used to express possibility and knowledge. Example for possibility : Jeg kan ikke komme i dag</code> - I can't come today. Example for knowledge : Jeg kan tale dansk</code> - I can talk danish. At måtte (to be allowed to) : Is used for : Ask for a permission.</li> </ul> Construction : Må + subject + infinitive of the verb + object Example : Må jegryge en cigaret ?</code> - Can i smoke a cigarette ? Express a logical obligation.</li> </ul> Example : Det regner så jeg må tage bilen.</code> - It's raining therefor I need to take the car. At burde (should) : Is used to give advices. Construction : Present form of at burde + infinitive of main verb Example : Du bør arbejde mindre.</code> - You should work less. Cistercian 2021-12-10T00:00:00+00:00 </div> A couple of months ago I came across a post on Reddit talking about the Cistercian numerals</a>. I found the concept interesting and wanted to create a small script to generate all the numbers as a separated svg file. The script generates the 9999 svg files usings lines</a> but there's also a version of the same numerals using paths</a>. I might use the second one to create a font at some point. To create them I used oslllo-svg-fixer</a>. Ruby http requests 2021-11-26T00:00:00+00:00 </div> GET query with ssl</h2> require 'net/http' def perform_query(target_url) uri = URI.parse(target_url) http = Net::HTTP.new(uri.host, uri.port) http.use_ssl = true request = Net::HTTP::Get.new(uri.request_uri) http.request(request) end </code></pre> GET query with headers</h2> require 'net/http' def perform_query(target_url) uri = URI.parse(target_url) http = Net::HTTP.new(uri.host, uri.port) request = Net::HTTP::Get.new(uri.request_uri) request['header-key'] = 'header-value' http.request(request) end </code></pre> Yoctolio 2021-11-24T00:00:00+00:00 </div> Backstory</h2> A couple of months ago my friend had the need for a quick web page containing a selection of his work. As the requirements was pretty simple I decided to create a small prototype directly in good'ol HTML + CSS, as all the videos featured on the website are hosted on YouTube this took me a couple of minutes and everyone was happy. Now of course my friend kept on working and therefore producing more videos, videos that he wanted to showcase. Adding a small html snippet every time was of course not a problem but there was always a delay and that when I thought "Is there a way to over-engineer that process and to increase my Rust knowledge at the same time ?" Requirements</h2> To fit this use case Yoctolio needs to have the following features : Display Youtube videos : ¯\_(ツ)_/¯.</li> Compartmentation of videos : by categories and years inside those categories.</li> Tags for videos</li> Editable only with csv files : as my friend will add his videos I don't want to use a markup language that he will need to learn just for this project.</li> </ul> Constraints</h2> Because this project is also about learning there are some self imposed constraints : Written in Rust : as said before I wanted to learn a bit more of this language and a small project like this one is perfect for that.</li> Create a static site : there's no need for a CMS here, I want to keep the first approach using HTML and CSS.</li> Create more than one page : it's always good to have a little about page in there.</li> Having as few dependencies as possible : there's no point in trying to learn a technologie if it's to rely on an already made solution.</li> </ul> Getting started</h2> Installation</h3> Using Cargo : cargo install yoctolio</code> Initialize project</h3> Once yoctolio installed you can run yoctolio init</code> to initialize a new project. After configurating everything to your liking you can simple run yoctolio build</code> to compile your website. Configuration</h2> Add video content</h3> The first step needed to add content on your portifolio is to create a file at the following path : config/config.txt</code> As well as the config/tags.txt</code> file with the following content : 1, directing 2, editing </code></pre> The words directing</code> and editing</code> can be changed and any tag can be added as long as their id (the number in front of the name) is uniq. Inside this file you can now add one line per section on the index page of the portfolio : Name of the section, file_name_of_the_section.txt</code> Yoctolio will now generate a section called Name of the section</code>, the videos you wish to include in this section need to be listed in the file you defined. In this case config/file_name_of_the_section.txt</code> To add a video you need to follow this pattern : Name of the video, youtube_url, tag_number, year, description</code> Where : Name of the video</code> is self explenatory</li> youtube_url</code> is the full youtube url example : https://www.youtube.com/watch?v=79T8c0vW0ik</code></li> tag</code> the id of the tag of the video, to use multiple tags add -</code> between two tags example 1-3</code></li> year</code> the year of the production example : 2021</code></li> description</code> a small explanation, the one is optional and can be left out</li> </ul> Changing the template</h3> The default templates are visible in the project repository</a>, to create your own you can simply create a templates</code> folder with an index.html</code> inside and it will be used by default. Adding a page</h4> If you want another page you can create a folder at the following path templates/pages</code> containing any html page that will be included in you portfolio. Adding assets</h4> Whenever you want to include css, js, images or any asset to you projects you can simply create a folder at the following path templates/assets</code>, the content of this folder will be copied to public/assets</code> during compilation. Adding partials</h4> A partial is a small html snippet that can be easilly reused in different pages and template, it can be useful for header, footer, navigation... To add partials to your porfolio you need to create the folder templates/partials</code>, then inside create any html file. To call a partial from a page of the index.html you just have to include the following snippet : {{!partial_name}}</code>. So if you create templates/partials/footer.html</code> it is called by using {{!footer}}</code> in any template. Live reload</h3> When working on your templates you probably want to regenerate automatically the website as doing it manually can be quickly become annoying. To do so I usually use entr</a> like that : ls templates/* | entr yoctolio build</code> Shattered machine 2021-11-23T00:00:00+00:00 </div> The Shattered Machine is a gem that aim to create glitched png images easily. Features</h2> Converter : Convert a single jpg images or a directory full of jpg image into png</li> Seven algorithms : Seven different algorithm with their own settings giving you lots of freedom to mess with your images</li> Sampler : Giving you a quick overview of all algorithms effect on your image</li> Folder glitching : Glitch easily all png images contained in a folder</li> </ul> Usage/Examples</h2> Glitcher</h3> require 'shattered_machine' io = ShatteredMachine::Io.new('input_image.png', 'output_folder', 'output_filename') ShatteredMachine::Glitcher.new('Slim', io).call </code></pre> Sampler</h3> require 'shattered_machine' io = ShatteredMachine::Io.new('input_image.png', 'output_folder', 'output_filename') ShatteredMachine::Sampler.new(io).call </code></pre> Converter</h3> require 'shattered_machine' io = ShatteredMachine::Io.new('input_image.jpg', 'output_folder', 'output_filename') ShatteredMachine::Converter.new(io).call </code></pre> Development</h2> Install locally</h3> The Shattered Machine using two main libraries for glitching : pnglitch</a></li> rusty engine</a></li> </ul> The rusty engine is written in rust and a compiled version for Windows, Mac os and Linux is already included in the gem. To install the needed dependencies you need to install the Ruby language</a> and Bundler</a>. Then run bundle install</code> to fetch the needed gems. Create new version</h3> Fill the CHANGELOG with the changes contained in the new version</li> Ensure the specs are green</li> Change the versions in lib/shattered_machine.rb</code> and shattered_machine.gemspec</code></li> Create git tag</li> Compile the gem : gem build shattered_machine.gemspec</code></li> Push the new version : gem push shattered_machine-x.x.x.gem</code></li> </ul> Specs</h3> This project uses Rspec</a> for writing specs, to run them simply run bundle rspec</code> Acknowledgements</h2> This gem is relying heavily on the pnglitch gem</a> and the rusty engine gem</a>. The png image used in the specs has been created with Ronin</a> while the jpg one is painting from Karl Wiener. Icons made by Freepik</a> from www.flaticon.com</a> Tiny conveyor 2021-11-23T00:00:00+00:00 </div> This gem is a tiny wrapper for async</a> that can create and execute a queue of tasks, each of the task run in a separated thread. Setup</h2> To use this gem you can simply install it with gem : gem install tiny_conveyor </code></pre> or add the following line to your Gemfile : gem 'tiny_conveyor' </code></pre> Usage</h2> Instantiation</h3> require 'tiny_conveyor' conveyor = TinyConveyor.new </code></pre> Run task</h3> action = proc { puts 'Run in a separated thread' } conveyor.add_parcel('first action', 'a simple task that print a sentence', action) conveyor.start_belt </code></pre> Remove unstarted task</h3> conveyor.remove_parcel_by_uuid('uuid_of_the_parcel') </code></pre> Check if a task is running</h3> conveyor.running? </code></pre> Check current pending tasks</h3> conveyor.parcels </code></pre> Acknowledgements</h2> Icons made by xnimrodx from flaticon</a> Rusty engine 2021-11-22T00:00:00+00:00 </div> This project is a tiny image manipulation library with four different functions and provides an efficient way to perform CPU intensive tasks. It's written in Rust but is precompiled for Linux, macos and windows that can be called from a Ruby file through FFI. Ruby setup</h2> The project is already precompiled in three different c libraries (stored in lib/bin</code>) : librusty_engine.dll (windows)</li> librusty_engine.dylib (macos)</li> librusty_engine.so (linux)</li> </ol> Therefore if you want to use it in a ruby script you can simply install the rusty_engine</code> gem and simply require 'rusty_engine_ffi'</code>. Usage</h2> Converter</h3> Example : require 'rusty_engine_ffi' RustyEngine.convert('images/input.jpg', 'images/output.jpg') </code></pre> Arguments : input file path</li> output path file</li> </ol> Slim</h3> Example : require 'rusty_engine_ffi' RustyEngine.slim('images/input.jpg', 'images/output.jpg', '90', 'global', '3', 'red', '99') </code></pre> Arguments : input file path</li> output path file</li> probability</li> probability area</li> direction</li> colors</li> colors probabilities</li> </ol> Brush</h3> Example : require 'rusty_engine_ffi' RustyEngine.brush('images/input.jpg', 'images/output.jpg', '90', '5', '10', '2') </code></pre> Arguments : input file path</li> output path file</li> probability</li> min</li> max</li> direction</li> </ol> Pixel sorting</h3> Example : require 'rusty_engine_ffi' RustyEngine.sort('images/input.jpg', 'images/output.jpg', '1', 'true', '0', '0', '30', 'true', '60', '100', '0') </code></pre> Arguments : input file path</li> output path file</li> smart sorting</li> detection type</li> min</li> max</li> multiple range</li> min 2</li> max 2</li> sorting by</li> </ol> Development</h2> Project architecture</h3> src/</code> contains the Rust code</li> target/</code> contains the compiled rust code (this directory is not present in git)</li> lib/</code> contains the files included in the gem</li> lib/bin/</code> contains the compiled rust libraries for osx, linux and windows</li> lib/rusty_engine.rb</code> is the ruby file that uses FFI to call the libraries inside lib/bin/</code></li> </ul> Compilation</h3> To compile this project you need the following softwares installed on you machine : Rust and Cargo</a></li> Docker</a></li> Cross</a></li> </ul> For compiling the rust code for your architecture : cargo build --release</code> For cross compilation, use cross : Windows cross build --release --target x86_64-pc-windows-gnu</code> Linux cross build --release --target x86_64-unknown-linux-gnu</code> The compiled library is now available in the target/release/</code> directory. Icon</h2> Icons made by Freepik</a> from www.flaticon.com</a> Piddly 2021-11-21T00:00:00+00:00 After realizing I always used the same set of CSS rules for a new project it's easier to just create some kind of skeleton app that can be reused. Inspiration</h2> The rules from this css file are higly inspired (or stolen, as you want) from the following projects : Skeleton</a></li> Normalize</a></li> Stack exchange's font rules</a></li> Emoji as favicon trick</a></li> </ul> Three monkeys 2021-11-20T00:00:00+00:00 </div> A small in browser .obj viewer and manipulation tool created with ThreeJS</a>. This project was created for a website of a design studio, originally the two faces were the ones of the members of this studio, but for this archived version of the project I decided to replace them by the good old Suzanne from Blender</a>. (legacy) Glitched factory 2021-11-20T00:00:00+00:00 </div> About</h2> This project contains the code for compiling the GlitchedFactory as well as the current version of the binaries (windows, linux and osx). To get an older version you can find them in the git repo. This project is created using Shoes. Since Shoes is now an abandonware this project will not be continued but a new version is in progress of rewritting using Glimmer. Specs</h2> Initialization</h3> You need Rspec to run the specs for the project, to install it run bundle install</code> in the root folder. Running</h3> To run the specs simply run the following command bundle exec rspec</code> Compile the project</h2> Linux</h3> .deb package</h4> For creating a .deb package you need to copy script/utils/merge-lin.rb</code> inside ~/.shoes/package/</code> on the linux setup then run the following commands from the root folder of glitched factory: scp script/utils/linux_packager.sh user@host:linux_packager.sh ssh user@host: ./linux_packager.sh </code></pre> OSX</h3> cd script/ mkdir dmg cd dmg ruby ../utils/dmg_packager_osx.rb ../utils/dmg_info_osx.yml </code></pre> Window</h3> Copy script/utils/compile_glitched_factory.bat</code> to the vm and run it as administrator Create new release</h2> cd script ./create_new_version.sh <version number> </code></pre> Thrived 2021-11-19T00:00:00+00:00 </div> For the album cover of their EP Anthea</a>, the band Thrived decided to generate an image of a flower using an AI. To train this AI they asked their listeners to pick an image of a flower among a preselected set and to crop it as they wanted. This project is the website that allows the selection and cropping of the images. It was quickly developed because of the scheduled release date so the technologies used are not top notch but something that allowed me quick prototyping (flask and jquery). Datamosher 2021-11-18T00:00:00+00:00 This project was an attempt to create a small gui around aviglitch</a> using Shoes. Since Shoes is now an abandonware this project will not be continued. Aviglitch is a great little library created by the same author as pnglitch</a> and allows a quick and easy way to create datamoshed videos</a> by destroying oon purpose the .avi format. This is still an area that interests me and I will probably (one day...) create another version of this tool. Unfortunately this library is written in Ruby, at first it was great because it allowed me to quickly understand it and play with it but Ruby is not made for creating small and portable binaries. Therefore to create an interesting software that can be easily distributed this library should be rewritten in a compiled language. At the moment I'm thinking about Rust to do this job but that can always change as long as I didn't start to work on it. Gitlab search engine 2021-11-18T00:00:00+00:00 </div> This repository contains the work done for the dissertation module of my MSc in computer science at the Oxford Brookes University, including a search engine written in Haskell using the Scotty web framework</a> and several documents created alongside the engine. Documentation</h2> The documents are : Dissertation proposal</a> : Created after the development stage, describe the future project.</li> Interim Report</a> : A mid-term document explaining the current state of the project.</li> Presentation</a> : A support for the oral presentation.</li> Short paper</a> : A small document that linger over the scientific side of the project.</li> Final report</a> : The larger document explaining the creation process of the entire project.</li> </ul> Each of these documents can be viewed in their raw formats (LaTex or Mardown). Abstract</h2> The goal of this dissertation is to create a search engine capable of gathering information autonomously about open source projects hosted on several Gitlab servers, and retrieve this information to fit a search query performed by a user while being the most accurate and quick as possible. A literature review is conducted about the Trie and B-tree data structures and their efficiency within the scope of search engines as well as a study of the current state of web Git servers. Finally the main decisions taken during the development process will be explained. Search Engine</h2> The search engine is composed by the following scripts : CustomTypes.hs</a> : Containing each type declaration and functions related to them.</li> DbSql.hs</a> : Containing every CRUD function for the SQL database.</li> JSONParser.hs</a> : Containing functions for JSON parsing (JSON files are created from Gitlab API response).</li> Main.hs</a> : Containing the Scotty routing and templates functions.</li> Query.hs</a> : Containing function for creating JSON files by querying Gitlab's API.</li> Research.hs</a> : Containing search functions used for the comparison between SQL and Trie performances.</li> Session.hs</a> : Containing functions creating and managing the Scotty's sessions.</li> TestDb.hs</a> : Containing benchmark creation functions.</li> Trie.hs</a> : Containing every CRUD function for the Trie.</li> </ul> PNG glitcher 2021-11-18T00:00:00+00:00 Goal</h2> This project is composed by three scripts created with pnglitch</a>, each of them can be used to create glitched version of a png image : glitch_sample.rb : create a folder glitched</code> containing an image for each glitch algorithm.</li> glitch_directory.rb : create an glitched version of every images contained by a directory.</li> glitch_animation.rb : create an animate (.gif) from a .png image</li> </ul> Requirements</h2> In order to use this project you need the following software installed on your computer : ffmpeg</a></li> ruby</a></li> </ul> Usage</h2> glitch_sample.rb</h3> Usage: glitch_sample.rb [options] -i, --input I Input png file (default: image.png) -v, --verbose Run verbosely -h, --help Show this message </code></pre> glitch_directory.rb</h3> Usage: glitch_directory.rb [options] -i, --input-folder I Input folder storing png imges to glitch (default: input) -v, --verbose Run verbosely --random Add a random factor to the generated glitch (works with exchange algorithm) --glitch-folder F Name of the folder where the glitched images are stored (default: glitched) --frames F F glitched frames created (default: 1) --filter FILTER Select glitching filter : (none,sub,up,average,paeth,random) (default: sub) --algorithm ALGORITHM Select glitching algorithm : (exchange ,transpose) (default: exchange) --range R Range of the glitch area (0 for full range, default: 0) -h, --help Show this message </code></pre> glitch_animation.rb</h3> Usage: glitch_animation.rb [options] -i, --input I Input png file (default: image.png) -o, --output O Output gif file (default: output.gif) -v, --verbose Run verbosely --random Add a random factor to the generated glitch (works with exchange algorithm) --glitch-name N Name of the glitched image created (default: glitch) --glitch-folder F Name of the folder where the glitched images are stored (default: glitched) --full-glitch create a gif with only glitched images --frames F F glitched frames created (default: 1) --delay D D ticks between each frames (1s is 100 ticks, default: 2) --first_delay D D ticks after the first frame (default: 300) --filter FILTER Select glitching filter : (none ,sub ,up ,average ,paeth ,random ,random_consistent) (default: sub) --algorithm ALGORITHM Select glitching algorithm : (exchange ,transpose) (default: exchange) --range R Range of the glitch area (0 for full range, default: 0) -h, --help Show this message </code></pre> Examples</h2> An animation and several glitched images can be found in the images</code> directory. µjava compiler 2021-11-17T00:00:00+00:00 This repository contain two different projects : A compiler for the µjava language written in java</li> Two Coco</a> configuration files, those files will not be explained as their importance and complexity are rather low compared to the compiler.</li> </ul> This project was created during my studies, which means that I will not work more on this but I wish to keep it for future references if needed. µjava Compiler</h2> A complete documentation with explanations on the implementation of the result of the tests can be found here</a>. The compiler can be found in the Code/Compiler/ directory. The goal of this software is to be able to read and parse µjava files in order to create bytecode files that can be executed. The compiler is composed of two main components. Scanner</h3> The goal of the scanner is to be able to read a file, detect each character written in the file and be able to distinguish them. However this compiler aims to compile μjava code meaning that the scanner has to understand only the syntax of this language therefore should return an error when the scanned text contains any non μjava character. Furthermore it should be able to differentiate the keywords of the scanned code as such so it needs to translate the content of the scanned file into several tokens. A token is a scanned bit of code, it could be a number or a letter but can also be any identifier like ’if’, ’else’... The proper functioning of the scanner will be tested with the help of the given java class named TestScanner available in the TestData directory. The purpose of this script is simply to run the scanner on an input file then print some information returned by the scanner. For each detected token the information will be the following : The line on which the token has been detected.</li> The column on which it starts.</li> The kind of the token.</li> The value of the token.</li> </ul> The TestScanner script is going to print a formatted version of that information. For example when the scanner detect a semicolon at the line 1 column 1 this is the expected output : line 1, col 1: ; </code></pre> As the scanner returns the kind of the token using keywords the test script is able to translate it on the corresponding character. For the previous example the scanner would return ’semicolon’ as the kind of token. Finally when the token is a number or an identifier the value of the token will be printed, for example : line 2, col 1: number 5 line 3, col 5: ident size </code></pre> Tests</h4> This part as been tested with three different provided input files : sample.mj : This file contains a syntactically correct μjava program, the test should return a formatted line for each token of the program as shown before. </li> Eratos.mj : Again this file is a working μjava program, therefore the wanted output is the same kind as sample.mj. </li> BuggyScannerInput.mj : This time the file is deliberately incorrect. The first part of the file doesn’t contain any error therefore should be scanned like the two previous files. On the other hand, it’s finished by six errors that need to be smartly handled by the scanner which imply to read the full document without crashing and report the correct number of errors and their positions. The scanner is expected to return four kind of error messages for the BuggyScannerInput.mj : ”Overflow” for the illegal number.</li> ”Apostrophe missing” for the illegal character constants with only one apostrophe.</li> ”Unknown character” for the unknown token.</li> ”Invalid character” for the three remaining illegal character constants.</li> </ul> </li> </ul> By testing the scanner with the three files we can be confident in the good working state of the scanner. The content of those files are available in the appendices of this document. Parser</h3> The second part of this compiler is the parser which needs to fulfill two different tasks. The symbol table is going to store and retrieve all declared names and properties of the μjava program being parsed. The parser should therefore be able to add a new entry in the table anytime the program declares one with it’s properties but also be capable of fetching it whenever the program calls it. μjava like most programming languages uses scopes for variables, our symbol table should then be able to store the corresponding scope for each stored variable. This will be imperative when the code is going to be executed by the μjava virtual machine. Finally once the table management is done we want the parser to be able to generate machine instructions, in our case μjava virtual machine bytecodes. Tests</h4> This part as been tested with three different provided input files : sample.mj : Here again as this program is correct our parser should be able to generate the content of the file and compile it. </li> Eratos.mj : Like for sample.mj the parser should be able to parse it and compile it without any error. </li> BuggyParserInput.mj : Like for the scanner this file is intentionally incorrect and should produce several errors. We also need the parser to be able to read the entire file and don’t stop when encountering an error as we want to inform the user of all errors in only one run. The program contains eight errors that should be returned by the parser. Their are only four different kind of errors and therefore error messages that should be returned : ””{” expected” In this case the brace is only an example as we need to handle every missing character of the program.</li> ”invalid assignment or call” This occurs when the program uses an assignment or call symbol that is not recognised by the μjava syntax.</li> ”invalid expression” Should be returned every time an expression in invalid, like a function call without an attribute.</li> ”incompatible type in assignment” Should be returned when the type of the value is not compatible with the type of the variable in an assignment.</li> </ul> </li> </ul> Tetris 2021-11-16T00:00:00+00:00 </div> The goal of this project is to create two versions of the game Tetris in two different paradigms: imperative and functional. The two programming languages chosen for this task are respectively Java and Haskell. This project was created during my studies, which means that I will not work more on this but I wish to keep it for future references if needed. A document containing a complete explanation of the choices made for this project as well as a detailed comparison of the two programs using a compiler can be found in the Doc/ diretory</a>. What is Tetris</h2> For the few that don't know this game, Tetris is a cult puzzle type video game created by Alexey Pajitnov in 1984. The goal of the game is to create horizontal lines organizing small pieces together. Those pieces are called tetrominos. The available tetrominos will be called by the following names in this document: i-tetromino</li> o-tetromino</li> t-tetromino</li> j-tetromino</li> l-tetromino</li> z-tetromino</li> s-tetromino</li> </ul> Each tetromino is a layout of four blocks. The game will create one of those tetrominos and make it go down a 20/10 matrix, during the fall the user can change the tetromino’s orientation and it’s position but once it reach the bottom of the matrix or another tetromino it will be fixed. Finally if one horizontal line is full of blocks it will disappear and give the user some points. Features</h2> Tetrominos</h3> The program should be able to randomly choose between one of the seven tetrominos. The current tetromino should move one square to the right or to the left when the user presses a specific key. Blocks</h3> Each tetromino is composed of four blocks, those blocks need to act independently. The main reason is that when a line is completed we don’t want the entire tetromino to disappear but only the block contains on the line. That’s why when a tetromino is fixed we need the program to take only into account blocks. Nonetheless when the tetromino is still moving the block should behave as a whole. Matrix</h3> The program needs to create the matrix of the game of the user; this matrix will have twenty horizontal lines and ten vertical ones. The matrix needs to show the fixed tetrominos, the current one which can be laterally moved and which direction can be switched by the user. When the user fills an entire horizontal line it should disappear and when a vertical one is filled the game must stop. Drop</h3> Every x seconds the current falling piece should drop 1 cell vertically. The value of x is defined by the current level. Level</h3> Each time the user reachs 10 000 points the game changes the level which means that the falling speed of the current tetromino will be increased. Score</h3> Following the original Nintendo scoring system here are the scores : Level</th> 1 line</th> 2 lines</th> 3 lines</th> 4 lines</th></tr></thead> 1</td> 40</td> 100</td> 300</td> 1200</td></tr> n</td> 40 * (n + 1)</td> 100 * (n + 1)</td> 300 * (n + 1)</td> 1200 * (n + 1)</td></tr> </tbody></table> Each 1000 point the game level is upgraded. Gravity</h3> When a line is destroyed, each line above goes down one line, yet the gravity is a little bit specific, which means that even when a block is above a hole it won’t go down further than one line. Interface</h3> The interface should contain on the left the matrix and a side panel on the right showing the score and the next tetromino. Hangman 2021-11-15T00:00:00+00:00 A simple hangman game with a custom dictionary, the repository contains a binary for linux as well as the sources that can be compiled using Ghc (Haskell's default compiler). This project was created during my studies, which means that I will not work more on this but I wish to keep it for future references if needed. The Dictionary file contains all words that can be asked by the game. The content of this file can be edited in an editor but it's preferable to use the in-game function to add a word. The goal of this game is to discover a word chosen by the script. The user needs to input a letter each turn as a guess. If the letter is contained in the secret word the script will show the word with the letter(s) visible for the user otherwise the user will lose one of its 8 lifes. If the word is fully discovered the user wins the game but if the number of lives is 0 the user loses the game. Mastermind 2021-11-14T00:00:00+00:00 This project was created during my studies, which means that I will not work more on this but I wish to keep it for future references if needed. The project is a game of mastermind in console. The goal of this game is to discover a combination of several marble chosen by the script among the following colors : g : green</li> r : red</li> b : blue</li> y : yellow</li> w : white</li> o : orange</li> </ul> There are three level of difficulty : Level</th> Marble to discover</th></tr></thead> Easy</td> 4</td></tr> Medium</td> 5</td></tr> Hard</td> 6</td></tr> </tbody></table> The user has 8 guesses to find the correct combination, each time the script will return one of those three symbols for each marble : Symbol</th> Meaning</th></tr></thead> .</td> The marble is present in the combination but in another place</td></tr> 0</td> The marble is at this place</td></tr> x</td> The marble isn't in the secret combination</td></tr> </tbody></table> Shoes 3 documentation 2021-10-01T00:00:00+00:00 </div> Shoes is a GUI library for Ruby, I used it when creating the now legacy glitched factory</a>. The documentation was embeded in the software needed to create the binaries but it wasn't practical to browse, first of all because the search field was useless but mostly because the software had to bad habit to randomly crash. This website was my attempt to migrate this documentation to the browser. Shoes 3 has since been abandonned so this website has no real use. Mruby 2020-03-07T00:00:00+00:00 </div> mruby</a> is a ruby implementation that allows compiling ruby code, unfortunately there's not so much documentation around therefore this is a dump of the info I gather for my personal use. Compile mruby with require support</h2> Why ?</h3> In order to compile a ruby library that uses the require</code> syntax. Compiling</h3> Clone mruby project git clone https://github.com/mruby/mruby.git</code></li> Change build_config/default.rb</code> to :</li> </ol> MRuby::Build.new do |conf| if ENV['OS'] != 'Windows_NT' then conf.cc.flags << %w|-fPIC| # needed for using bundled gems end conf.toolchain conf.gembox 'default' conf.enable_bintest conf.enable_test conf.gem :github => 'mattn/mruby-require' end </code></pre> Compile using rake</code> in the root folder</li> The binaries are compiled into build/host/bin</code></li> </ol> Compile a simple ruby file with mruby</h2> What is this document for ?</h3> mruby is an emdedded version of ruby, here's how to compile a simple ruby file into C file. This memo is using mruby's official compiling guide</a>. Install mruby</h3> Using rbenv : look which version of mruby is available to install : rbenv install -l</code></li> at the time I'm writing this memo the version is mruby-2.1.2</code> : rbenv install mruby-2.1.2</code></li> </ol> Create project folder</h3> mkdir my_project cd my_project rbenv local mruby-2.1.2 </code></pre> Create the needed files</h3> You need the following files in the project folder: Your ruby file to compile, in this case called test.rb</code> :</li> </ol> puts "this is a test" </code></pre> A file that will handle your c code here called test_stub.c</code> :</li> </ol> #include <mruby.h> #include <mruby/irep.h> #include "test.c" int main(void) { mrb_state mrb = mrb_open(); if (!mrb) { / handle error */ } mrb_load_irep(mrb, test_symbol); mrb_close(mrb); return 0; } </code></pre> Compile your ruby file to C</h3> Compiling to c file is straight forward : mrbc -Btest_symbol test.rb</code> should produce a file named test.c</code> Compile your C file</h3> using gcc you can compile you test.c</code> like that : gcc -std=c99 -I /Users/username/.rbenv/versions/mruby-2.1.2/include/ test_stub.c -o test_program /Users/username/.rbenv/versions/mruby-2.1.2/lib/libmruby.a -lm </code></pre> Execute your newly compiled program</h3> ./test_program</code> should print this is a test</code>

Duckpuck

Spectrogram

Logseq time tracking

Setup</h2>

Create time_tracking page</h3> Again for now an empty page, this will later contains the log of hours tracked.</p>

How to use it</h2>

Log hours</h3> Now that everything is setup I simply add now entry in the time_tracking page using the /template</code> command and use the Time tracking entry template. Once added I adjust date and hours as needed and take make project I want to tracking time for.</p>

Instax mini evo

Step 4 - Snap it</h3> </div> </div> </div> Step 5 - Print it</h3> </div> </div> </div> </p> Sources</h2> The pixel art are created in a software call aseprite</a>, the sources files for this project are available in the meta links at the top of this page.</p>

Step 5 - Print it</h3> </div> </div> </div> </p> Sources</h2> The pixel art are created in a software call aseprite</a>, the sources files for this project are available in the meta links at the top of this page.</p>

Sources</h2> The pixel art are created in a software call aseprite</a>, the sources files for this project are available in the meta links at the top of this page.</p>

Dithor

What is this library</h2>

High resolution</h4> The content of the square is then filled with the following pattern (depending on the level):</p> </div> Here's a picture showing the same patterns on a bigger surface:</p>

Low resolution</h4> The content of the square is then filled with the following pattern (depending on the level):</p>

Using colors</h3> When the third parameter is true the output will be in color, the brightest and darkest colors from the 25 or 225 pixels are used to fill the patterns showed above.</p> Example in high res:</p>

Berlin guide

Tips</h2> Always have a bit of cash on you, a lot of shops in Berlin don’t accept the card.</li> Convenience stores are called Späti, they are everywhere and usually open late. It’s common for them to have some tables in front for people to enjoy a drink.</li>

Food</h2>

Beers and cocktails</h2> In Berlin like everywhere in Germany there's a big choice of delicious beers, don't be shocked to see someone opening a beer in the s-bhan after leaving their workplace. To my knowledge, Berlin has two main kinds:</p>

Cocktails bars</h2> Those are my three favorite cocktails bars, sorted by my most favorite to my lest favorite</p>

Museums</h2>

Color palettes

Wikipedia articles

Glitched factory log

Glitched factory

Pnglitcher

Duplicate</h3>

Replace</h3>

Wrong filter</h3>

Png glitch art tools

Libraries</h2> Libraries used by the two softwares above, you can use them from a Rust or Ruby code base.</p>

Rust</h3> Those libraries may be used to create glitched images directly in Rust.</p>

Ruby</h3> These libraries may be used to create glitched images directly in Ruby.</p>

Arko

Slim</h3>

Danish memo

Pronunciation</h2>

Æ Ø Å</h3> Æ</strong> is pronounced like [ai] (lait)</p> Ø</strong> is pronounced like [eu] (heureux)</p> Å</strong> is pronounced like [o] (bol)</p>

Vocabulary</h2>

Useful words</h3> Mange</strong> : Many</p> Meget</strong> : Much</p> Altid</strong> : Always</p> Normalt</strong> : Usually</p> Tit</strong> : Often</p> Nogle gang</strong> : Sometimes</p> Ikke så tit</strong> : Not so often</p> Aldrig</strong> : Never</p>

Conjugation</h2>

Infinitive</h3> Most of the time finishing with -e</strong> and preceded by at</strong>.</p> Example : at komme</code>.</p>

Negation</h3> To use the negation use ikke</strong> after the verb.</p>

Cistercian

Ruby http requests

Yoctolio

Requirements</h2> To fit this use case Yoctolio needs to have the following features :</p>

Constraints</h2> Because this project is also about learning there are some self imposed constraints :</p>

Getting started</h2>

Installation</h3> Using Cargo :</strong> cargo install yoctolio</code></p>

Changing the template</h3> The default templates are visible in the project repository</a>, to create your own you can simply create a templates</code> folder with an index.html</code> inside and it will be used by default.</p>

Shattered machine

Usage/Examples</h2>

Development</h2>

Tiny conveyor

Usage</h2>

Check if a task is running</h3> conveyor</span>.</span>running? </span></code></pre> Check current pending tasks</h3> conveyor</span>.</span>parcels </span></code></pre> Acknowledgements</h2> Icons made by xnimrodx from flaticon</a></p>

Check current pending tasks</h3> conveyor</span>.</span>parcels </span></code></pre> Acknowledgements</h2> Icons made by xnimrodx from flaticon</a></p>

Acknowledgements</h2> Icons made by xnimrodx from flaticon</a></p>

Rusty engine

Create time_tracking page</h3>
Again for now an empty page, this will later contains the log of hours tracked.</p>

Log hours</h3>
Now that everything is setup I simply add now entry in the time_tracking page using the `/template</code> command and use the Time tracking entry template. Once added I adjust date and hours as needed and take make project I want to tracking time for.</p>`

Step 4 - Snap it</h3> </div>
</div> </div>

Step 5 - Print it</h3> </div>
</div> </div> </p>
Sources</h2>
The pixel art are created in a software call aseprite</a>, the sources files for this project are available in the meta links at the top of this page.</p>

Step 5 - Print it</h3> </div>
</div> </div> </p>
Sources</h2>
The pixel art are created in a software call aseprite</a>, the sources files for this project are available in the meta links at the top of this page.</p>

Sources</h2>
The pixel art are created in a software call aseprite</a>, the sources files for this project are available in the meta links at the top of this page.</p>

Libraries</h2>
Libraries used by the two softwares above, you can use them from a Rust or Ruby code base.</p>

Æ Ø Å</h3>
Æ</strong> is pronounced like [ai] (lait)</p>
Ø</strong> is pronounced like [eu] (heureux)</p>
Å</strong> is pronounced like [o] (bol)</p>

Useful words</h3>
Mange</strong> : Many</p>
Meget</strong> : Much</p>
Altid</strong> : Always</p>
Normalt</strong> : Usually</p>
Tit</strong> : Often</p>
Nogle gang</strong> : Sometimes</p>
Ikke så tit</strong> : Not so often</p>
Aldrig</strong> : Never</p>

Infinitive</h3>
Most of the time finishing with -e</strong> and preceded by at</strong>.</p>
Example : `at komme</code>.</p>`

Negation</h3>
To use the negation use ikke</strong> after the verb.</p>

Installation</h3>
Using Cargo :</strong> `cargo install yoctolio</code></p>`

Changing the template</h3>
The default templates are visible in the project repository</a>, to create your own you can simply create a `templates</code> folder with an index.html</code> inside and it will be used by default.</p>`

Check if a task is running</h3>
`conveyor</span>.</span>running? </span></code></pre> Check current pending tasks</h3> conveyor</span>.</span>parcels </span></code></pre> Acknowledgements</h2> Icons made by xnimrodx from flaticon</a></p>`

Check current pending tasks</h3>
`conveyor</span>.</span>parcels </span></code></pre> Acknowledgements</h2> Icons made by xnimrodx from flaticon</a></p>`

Acknowledgements</h2>
Icons made by xnimrodx from flaticon</a></p>