You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't entirely intuitive, especially for the time conversions. Even I, as the creator of Sandpiper, get confused about how to use this.
Alternative syntaxes
I suggest the following two alternative syntaxes which should be able to be added backwards-compatibly:
->
This is more of a bandage on top of the existing >, to change the implication from a greater-than relationship to a from-to relationship.
5cm -> in
3pm -> seoul
3pm dubai -> seoul
to
to is more linguistically intuitive and would probably be the new preferred way to do conversions. It should be noted that the use of alphabet characters does introduce the potential for parsing ambiguities, and I don't know the implications of that yet. However, I think the benefits of adding this are very important for UX reasons.
5cm to in
3pm to seoul
3pm dubai to seoul
Add in?
This is getting into dangerous parsing-ambiguity territory, but it could be even more intuitive to add in:
5 in cm to in
3pm to seoul
3pm in dubai to seoul
The text was updated successfully, but these errors were encountered:
Current situation
Currently, we only accept conversion strings like
5cm > in
3pm > seoul
3pm dubai > seoul
This isn't entirely intuitive, especially for the time conversions. Even I, as the creator of Sandpiper, get confused about how to use this.
Alternative syntaxes
I suggest the following two alternative syntaxes which should be able to be added backwards-compatibly:
->
This is more of a bandage on top of the existing
>
, to change the implication from a greater-than relationship to a from-to relationship.5cm -> in
3pm -> seoul
3pm dubai -> seoul
to
to
is more linguistically intuitive and would probably be the new preferred way to do conversions. It should be noted that the use of alphabet characters does introduce the potential for parsing ambiguities, and I don't know the implications of that yet. However, I think the benefits of adding this are very important for UX reasons.5cm to in
3pm to seoul
3pm dubai to seoul
Add
in
?This is getting into dangerous parsing-ambiguity territory, but it could be even more intuitive to add
in
:5 in cm to in
3pm to seoul
3pm in dubai to seoul
The text was updated successfully, but these errors were encountered: