Ubuntu Touch team threw out radio buttons. PROBLEM: How are developers simply supposed to take a previously running qt app with radio buttons on the desktop and get it running on Ubuntu Touch?
Have you got a path to facilitate the migration or are you expecting developers to do a complete rewrite with every dialog containing radio buttons? Once a selection is made, people don't necessarily want to navigate to the next screen automatically. We are indecisive creatures. We like to choose, think about it some more and then go to the next step. Not everything is a list box.(not all options are displayed at the same time after selection. listboxes possibly imply multi-selection which is not a good thing.) Not everything is a button.(non-grouped option) Not everything is a checkbox.(multi-select) I wrote a simple app in go-gtk, c++-gtk, qt for android. All of these have radio buttons/radio button groups. X, Motif, OpenLook, Gnome, KDE, Android all have radio buttons. Please reconsider this. The functionality is qt was already there and you took it out. That wasn't necessary to do unless you have something better to offer and something to facilitate a migration path without resorting to rewriting code that worked on the desktop and on other devices. I don't see the rationale behind this decision. It's not consistent with adopting the qt toolkit that is certain. When adopting qt, one usually adopts all qt controls because their controls are known to display and work on all of their supported os's and devices. Ubuntu Touch is the standing out like a sore thumb with respect to radio buttons not being supported on Ubuntu Touch, but being supported on the desktop. Cheers, David Marceau -- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
