© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
73416ba
(Get the code!)
I should have explained what design work is needed. What we need now is two things.
First, ideas, in the form of wireframe sketches, about how USC should present console applications differently from graphical ones. Some points to start off with:
* For most people, most of the applications they see in USC will be graphical ones. So, using text or any obvious marker to say that they're graphical could get annoyingly repetitive.
* In some subsections (for example, "Developer Tools" > "OCaml"), all -- or nearly all -- of the items are for use at the console. So any obvious marker for those could get annoyingly repetitive within those sections too.
* Maybe there could be a marker just for console applications, not for graphical ones.
Second, a more specific plan about how USC should tell the difference between the types of package in the first place. Could Launchpad set the flag automatically when building a package, e.g. by examining the package for executable files vs. .desktop files? Or would the maintainer need to do it manually? If so, how would they do it?