Remove / Reason behind "placeholder" about skippingstones

[ruedigergad]

IIrc, the rationale for this was to indicate that this field still needs to be filled or handled properly.
Furthermore, another intention was to provide some means for anticipating where and how things will be displayed on the watch.

It might also have been that in some very early versions the handling of empty strings was not properly but I don't recall this exactly anymore.
Apparently, as you found out, empty strings work.

[smurfy]

I plan to work a bit on SkippingStones, i have two main things i want to change.

• Clean up notifications (covers this issue)
• Clean up main ui (Separate developer stuff from consumer)

I would create a pull request for each part.

[ruedigergad]

Cool, this sounds great.

With respect to the "placeholder", maybe add a boolean variable to set whether "placeholder" texts are shown or not.
Reason for this is that it still might be useful at times when developing.
This variable could default to false and thus no placeholder text would be shown unless explicitly set otherwise.

With respect to UI improvements, sure, that sounds good as well.