掲示板 Forums - Mnemonics - visual upgrades

税、椿

Good news, think I'm down to just a few at the moment:
暗 - not yet
都 - not yet

You Sure about that? Things like さんずい and にんべん don't work. 東 is missing a stroke, 桜 and several others are also incomplete. 

OK!

I've fiddled with it a lot. I think all terms that

a) Have pieces mentioned in their mnemonic
and
b) All pieces mentioned are listed in the boxes in the editor

have colors now. There are many, though, which have user-entered pieces, and these will have to be marked up using a manual tool that Ihave not yet made. So, if you have any mnemonics which follow the above rules and are not appearing correctly, let me know!

Speaking of the tool, I'm trying to think of the best way to create it. So, if there is a piece that isn't recognized, it could do one of the following:
1) List all stroke numbers, and the users chooses them by clicking the numbers (this would be the most compact). It would almost instantly highlight the strokes in the image, so you could easily tell what you are doing.
2)List all the strokes (just like the stroke diagram in the dictionary). This would take up much more space, and would be much harder on mobile, but it would be clearer what strokes you are entering.

The brain should pop up if it cannot fulfill all requirements. When this tool is finished, though, it will alert you before saving that you need to do extra, and give you a chance to do things then.

In regards to the rest, let's use this example:
This kindling fire 火 burns vividly 戠 and makes as much noise 音 as clashing halberds 戈.

It is true that you have broken it down, but there is nothing in the system to say "any time you see音 and 戈, you should assume it is being put together to make戠. That might be obvious to us, but Iwould need to explicitly make pairings from the components to the whole, and then each time that was done, we'd have to hope that those are not used in a different combination/arrangement in other kanji. It feels too much like "let's write exceptions each time it comes up", instead of building a system that handles everything more gracefully.

Iwill probably also add an option that says "just don't color ones that are not found", so in the case of the example Igave, it would just ignore the "missing"one, color the rest, and save it like that. In your case, that would be very effective, but I'll still need a way out for other people, or for people who are choosing to forgo the available parts to just make something new out of scratch (which I've seen in a number of mnemonics, especially when they choose the strokes to visually represent something).

We'll see how quickly/slowly work goes on this new part, and then we can test it out and see if it is convenient enough.

It's up! Hopefully it is self explanatory. It feels a bit rickety at the moment, so some bugs might pop up, but Ihaven't been able to find any yet!

Interestingly, when I hit the edit button, the colours in the text and in the kanji match. But when I hit save, the text colours are different from the kanji colours. (蝶)
And I have a problem editing 幟. On my edit page, the entire right part has the same colour as 音. Now I want to separate 戈, but the editor only allows me to edit the compound part. How can I get around that?

蝶 looks fine now. Thanks.

Basically there are only 5 kanji using that particular compound. As far as I can tell, all the other 4 kanji had no problem.

I like it better if the long stroke is with 戈.