From 10fb7bca38c320730a0dff82951e5b71e0fc7b25 Mon Sep 17 00:00:00 2001 From: ente Date: Mon, 22 Apr 2024 12:10:06 +0200 Subject: [PATCH] edited README.md --- README.md | 19 ++++++++++++++----- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index 9b79b1c..52992c4 100644 --- a/README.md +++ b/README.md @@ -22,21 +22,30 @@ Basically this is a simple Javascript (no framework used here). It loads all the While loading the site the script loads the JSON file and processes all the entries. I have chosen a JSON simply because it is a well known file format and can be easily used in other programs. Feel free to use the parts folder and the `parts.json` for any other project (CC-BY-SA-NC 4.0) The rest is just a normal Javascript that responds to `onCLick()` events on the various buttons. +The colour of the arms is determined by the last of the three entries named `"color"` in the JSON of `"body"` and `"arms"`. So only arms will be displayed who match the colour of the base neomoji (e.g. orange for neofox, yellow for neocat, etc). The data is structured in a way that the same arms will have the same position in every Array, so besides a colour change there shouldn't be any visible changes. I try my best to have every arm part ready in everz colour. + The export works in a way that in the background all the parts are drawn onto a canvas and then exported into a PNG that is then displayed. Direct canvas download isn't supported on the most mobile browsers so I chosen to got that little bit longer route, to make it more easily to download any of the mixed neomojis. +## I dowoloaded it localy, but it doesn't work?!? + +Welcome to the world of Javascript! +Due to security reasons javascript that is displayed in a Brwoser can't access files diretly, so to speak on the PC the JavaScript si executed one. The solutions is relativly simple: Run a small http server locally. +I used [lighttpd](https://www.lighttpd.net/) on an Linux laptop, that I started manually every time I worked on the project and had no issues. + ## You need help! YES! I actually do! creating the first 95 elements took me over six hours to make. Some parts where as easy as simply two clicks, others had to be manually extracted, so any help is welcome, especially when you ask yourself the following questions: -1.`partX` looks wonky/ doesn't work with `partY` +**`partX` looks wonky/ doesn't work with `partY` ** As stated it took me quite some work to edit all the parts. So if you are good in editing PNG graphics or have more patience with GIMP, feel free to improve the files! -2. I am missing `partZ` -I haven't and can't add all of the parts the neomojis are made of. For example the `flop` or `up` variants are a little bit tricky because I have to flip the other three layers of the image and adjust for their position to make it fit. Maybe I will work on a solution later, but at the moment its not my main goal. +** I am missing `partZ` ** +I haven't and can't add all of the parts the neomojis are made of. For example the `flop` or `up` variants are a little bit tricky because I have to flip the other three layers of the image and adjust for their position to make it fit. Maybe I will work on a solution later, but at the moment its not my main goal. -3. That isn't Javascript, that is an illness! or That HTML is ugly as fuck! +**"That isn't Javascript, that is an illness!" or "That HTML is ugly as fuck!"** I am not a professional programmer or webdev of any kind. So if you can improve any of my code, to make it faster or better to read, feel free to send me a pull request. Every help in this way is welcome. -4. Why isn't `$neomoji` available? + +** Why isn't `$neomoji` available?** Probably I don't know about the existence of the neomoji, couldn't reach the original author or they just didn't allowed the usage of it for the neomojimixer. ## Thanks to the following people