4 ms·

Author here - thank you for the feedback! The nand-count is based on how you built the components involved. So optimizing a component will have have cascading

by sergex 6y ago

Author here - thank you for the feedback! The nand-count is based on how you built the components involved. So optimizing a component will have have cascading effects. "This is the simplest solution!" means the solution with fewest individual components on the canvas. I realize the text could be clearer.

ncvytu 6y ago
If I could add a few more suggestions: 1. The blue on purple color scheme is a little hard on the eyes. Changing the blue lines and circles to #0f0 green helped a lot. (Green also has strong "on" semantics) 2. My SO and I both had trouble finding the trash can. We both tried to drag components back to the workbench or off of the mat to delete them. A larger trash can icon or just making it red might help. 3. I ran into some z-layering issues (at least on Firefox). Opening a component info bubble from the workbench displays under the mat. Also the "results" popup displays underneath any components that might be on the far side. Overall great game though! I had a lot of fun with it. Thank you!
- sergex 6y ago
  Thank you very much for the suggestions.
_xoo 6y ago
In that case it would be useful to see which components could still be optimized on the level overview :)
jventura 6y ago
Hi author, cool game, you got me hooked! One thing I could suggest for now (I'm still in the Latch level) is that you could go a bit below and start from the transistor itself, like build the nand gate from the transistors..
- sergex 6y ago
  Yes that would be great!
ALittleLight 6y ago
Love the game. One suggestion I had is that it would be helpful to indicate the number of nand gates in each component. When I'm trying to optimize I'm also trying to remember which is a "cheaper" component - having a number of nand gates associated with each component would help.
Sniffnoy 6y ago
I see, thanks! Yeah if you see my comment below I think really it should always be explicit both about whether you used the fewest components and (separately) about whether you used the fewest NAND gates. Currently it seems like you sometimes only get told about one or the other...

by sergex 6y ago

ncvytu 6y ago

If I could add a few more suggestions: 1. The blue on purple color scheme is a little hard on the eyes. Changing the blue lines and circles to #0f0 green helped a lot. (Green also has strong "on" semantics) 2. My SO and I both had trouble finding the trash can. We both tried to drag components back to the workbench or off of the mat to delete them. A larger trash can icon or just making it red might help. 3. I ran into some z-layering issues (at least on Firefox). Opening a component info bubble from the workbench displays under the mat. Also the "results" popup displays underneath any components that might be on the far side. Overall great game though! I had a lot of fun with it. Thank you!

sergex 6y ago
Thank you very much for the suggestions.

_xoo 6y ago

In that case it would be useful to see which components could still be optimized on the level overview :)

jventura 6y ago

Hi author, cool game, you got me hooked! One thing I could suggest for now (I'm still in the Latch level) is that you could go a bit below and start from the transistor itself, like build the nand gate from the transistors..

sergex 6y ago
Yes that would be great!

ALittleLight 6y ago

Love the game. One suggestion I had is that it would be helpful to indicate the number of nand gates in each component. When I'm trying to optimize I'm also trying to remember which is a "cheaper" component - having a number of nand gates associated with each component would help.

Sniffnoy 6y ago

I see, thanks! Yeah if you see my comment below I think really it should always be explicit both about whether you used the fewest components and (separately) about whether you used the fewest NAND gates. Currently it seems like you sometimes only get told about one or the other...