Anyway is a good practice to give a meaningful name to the views.
Yes, but sometimes, you can't find that "good meaningful name" to name your view...
In my case, this project is a collaboration, and the name I give to a view or a sub may not be as "meaningful" to the other coder as it is to me, so a short description should help greatly.
Like in my example, I could have given the Button a name like Edit_Gps_Card_Btn but then I call some sub named, let's say, Edit_Gps_OK_btn, this, with underscores, makes it readable, EditGpsCardBtn & EditGpsOKbtn could be somewhat easy to mix.
Also, really meaningful names tend to be too long!