Notify user when add phrase failed

[jeffreyhc]

Close #160

When user add phrase fail, there will be a notification tell user the movement is failed: (The phrase still add in editor because of the auto-learning function in libchewing)

Does the notification need to show the content of the phrase add failed?

[david50407]

IMO, showing the reason or some tips is better, eg. "Please enter correct bopomofo and try again" or "Please enter the bopomofo for each words"

[coveralls]

Coverage remained the same at 94.382% when pulling 1ee7156c43e80764ac823973db37552b3e2b343d on jeffreyhc:new into 5fb676f21948b0a50ee8dffad1eea0e7618226d2 on chewing:master.

[jeffreyhc]

@david50407 : I update the message.

[jserv]

@jeffreyhc : Crop your screenshot to focus on what you would like to present.

[jeffreyhc]

@jserv : I update the picture When user add phrase failed, (the terminal shows the failed message) there is a notification to notify user.

[jserv]

@jeffreyhc I meant, you can reorder the windows to be more compact as the tiling presentation.

[jeffreyhc]

@jserv : Like this?

[jserv]

@jeffreyhc much better now. You can trim the white area off.

[jeffreyhc]

@jserv Is this ok?

[jserv]

@jeffreyhc Pretty good to me. Thanks. Please read this article Accessible Design for Users With Disabilities. We should always prepare the content to the disabled as friendly as possible.

[jserv]

@jeffreyhc Wrap the Git commit message body at 72 characters according to How to Write a Git Commit Message.

[jeffreyhc]

@jserv : I remember I should wrap the body at 72 characters, I split the text to two lines because I thought they might exceeded the limit. However, I review the section of How to Write a Git Commit Message and I found I have at most the space of 80 characters.

[coveralls]

Coverage remained the same at 94.382% when pulling 80a009df06f42401a5a1e259a5fc6cc0ae126b92 on jeffreyhc:new into 5fb676f21948b0a50ee8dffad1eea0e7618226d2 on chewing:master.

[jserv]

@jeffreyhc : Thanks for your contribution!