search

rainbyte / haskell-ide-chart

Haskell state of editor/IDE support
https://rainbyte.github.io/haskell-ide-chart/
Creative Commons Attribution Share Alike 4.0 International
249 stars 12 forks source link

More intuitive symbols #20

Open piaste opened 6 years ago

piaste commented 6 years ago

From #19

@piaste:

I found the emojis hard to read at a glance, I was constantly having to glance down to the documentation.

@rainbyte:

This received some discussion earlier, and the result was the current emojis. I'm not sure if these new emojis are more intuitive than the old ones.

Maybe they should give the idea of steps and the idea of greater support? I mean, being able to order them is important too.

Compare this order (based on how fast you can move): … ->🚶-> 🚲 -> 🚗->🚀

With this one: ❔ -> ❌ -> ❕ -> ➕ -> ✔️

It is not clear why they are higher level than the others.

Maybe we could just use numbers instead? ? -> 0 -> 1 -> 2 -> 3 In this way zero means nothing, and the rest mean higher level by steps.

Using letters is other option too, in this way: ? -> X -> C -> B -> A But I think numbers are easier, they are universal.

piaste commented 6 years ago

Using numbers or letters would be great, I think colours are more important though to be able to parse the table at a glance.

rainbyte commented 6 years ago

It is also important being able to see links to websites when they are provided. Colored emojis hide links (see issue #6), which already is confusing.

rainbyte commented 6 years ago

Some ideas using only ascii chars:

IDE Syntax highlight Code Completion Error Reporting Lint Code Format
Current … :walking_man: 🚲 🚗 :rocket:
Op1 ? 0 1 2 3
Op2 ? - C B A
Op3 … - + ++ +++
pascalpoizat commented 6 years ago

I think Op3 is more clear. Yet, it could also come with detailed information / criteria on why one uses + / ++ / +++ for a given feature.

rainbyte commented 6 years ago

There is a description about the levels below the table. Please, tell me if it is not clear enough.

pascalpoizat commented 6 years ago

Let me first precise that the table is already very good. I was able to choose Haskero using it and I am very happy with this choice (keeping also the Spacemacs Haskell Layer for other things). Most of the descriptions are ok but what makes for example having a car vs a bicycle for Error Reporting, or for Code Format? Precisions that I think could be useful are: