Originally posted by Nocifer
View Post
For years there's been the compose key to produce for example £ via tapping WIN followed by L and - to produce the combined character, or O C for ©, or T M for ™ etc. So it stands to reason that to access the emoji codepoints in a similarly intuitive way via the already well-defined and supported interface, then there should be compose key sequences for the emoji as well.
The iBus app is just an ugly example of NIH as far as I'm concerned. Ugly defined as popping a grey box with [e ] some random place on the screen with no obvious way to get rid of it, no obvious way to complete it, no help on the iBus widget, and none of the top 10 search results on Google even provide useful help. And if you do click the iBus icon - it pops a dozen stacked grey boxes on the screen 20px above the cursor with the chosen locale language name short form (ie "EN") in them which much each be clicked in turn to dismiss them, while providing no useful function whatsoever. And the iBus icon colour can't be set, so it fails to meet HIG guidelines since it can't be set to a visible colour. How it managed to make it into a release in its current form beggars belief.
For anyone configuring a distro's desktop to use the iBus app - provide some documentation for users so they can determine how to use it, and blacklist its icon in the notification area. It will work just fine without the icon, whereas the icon is nothing but a hazard to users.
Leave a comment: