search

Gibberlings3 / iesdp

Jekyllized version of IESDP with imported history
https://gibberlings3.github.io/iesdp/
19 stars 22 forks source link

Labels for actions #85

Closed burner1024 closed 4 years ago

burner1024 commented 4 years ago

I think that notes like "This action has not been seen to produce any results" or "Not tested" would be more visible and better represented by labels similar to github issue labels. Captura de pantalla de 2020-02-23 14-59-09. How about that?

lynxlynxlynx commented 4 years ago

Same for any crashers.

For some of them they may apply to actions that have variants in other engines, so I'm not sure it'd look good after the title. Some are long too. Play with it, I'd put them before the sisters block.

I propose you use another yaml var for freeform warning text, then style it yellow in the layout.

burner1024 commented 4 years ago

Does action color itself carry meaning? Why 98+ are blue, are they also "not seen to produce any result"?

Captura de pantalla de 2020-02-23 16-18-22

lynxlynxlynx commented 4 years ago

Judging from the class of "unknown", I suspect igi had it as a marker of unverified information.

burner1024 commented 4 years ago

OK, so "not tested", then.

burner1024 commented 4 years ago

Here's a sample Captura de pantalla de 2020-02-23 18-38-28 Tooltip on the label says the full "This action has not been seen to produce any results"

lynxlynxlynx commented 4 years ago

Brings up an interesting point — don't forget to add it to the other 97 variant, which requires a separate file.

burner1024 commented 4 years ago

I'll check when I get to variants, but I think everything should work as is, since they are essentially independent.