766485 - GCLI should have better "command not available" UX

Status: RESOLVED WONTFIX

(DevTools Graveyard :: Graphic Commandline and Toolbar, defect)

Description

[Joe Walker [:jwalker]]

Rather than just saying 'not found' or similar we could have some action the user could take to request a command.
The user could then provide us with notes as to what the command should do.

I wonder if we could use input.mozilla.org as a way to collect and collate this?

Comment 1

[Kevin Dangoor]

input.mo is not a great way to collect feedback like this, because it's limited to ~140 characters. There's the Tell Us More project that aims to step from input.mo-sized input to actual bugzilla bugs: https://wiki.mozilla.org/Firefox/TellUsMore

One option would be to provide a link to a page describing:

1. how to find add-ons with commands (perhaps what they want already exists?0
2. how to file a bug for a command (probably with a link that has the component prepopulated)
3. where to go to learn about writing commands

Comment 2

[Tomislav Jovanovic :zombie]

since this is in response to my idea, i can volunteer to implement it, if it's in fact something you intent to do..

Comment 3

[Joe Walker [:jwalker]]

New component triage. Filter on "Lobster Thermidor aux crevettes with a Mornay sauce"

Comment 4

[Joe Walker [:jwalker]]

Resetting priorities because these P* levels are very out of date.
Sorry for the bug spam. Filter on Lobster Thermidor

Comment 5

[Joe Walker [:jwalker]]

Triage. Filter on Lobster Thermidor.
Nice idea, but no need to keep on file.