Written by rouge568 the 29 Feb 08 at 00:39.

Have a drop-down menu display when I right-click on an item, with choices such as "edit this item" "delete this item", and "add a new menu item". Also, if I click and hold on an item, it should hover and I should be able to drag it through the menus to reposition it.

Have a drop-down menu display when I right-click on an item, with choices such as "edit this item" "delete this item", and "add a new menu item". Also, if I click and hold on an item, it should hover and I should be able to drag it through the menus to reposition it.

Written by robertjlee the 29 Mar 09 at 16:50.

When you right-click on a submenu's menu item, it should not close the submenu. Instead, it should bring up a context menu with additional options to edit this submenu in the menu editor, and to hide this submenu (as well as the existing options you would get from right-clicking on a menu item within that sub-menu).

For a menu item, add extra context menu options to edit this menu item in the menu editor, to directly edit the menu item's launcher's properties, and to hide the menu item.

It should also be possible to drag menu items (including entire sub-menus), within each menu. Additionally, each sub-menu item should have a "lock to menu" checkbox option on its context menu to prevent it from being dragged (similar to panel items' "lock to panel" checkbox option).

It may even be possible to use panels and drawers to build the menus and use common code to handle the behaviour of both consistently.

The edit menus item would still be needed to remove items, and would still be useful for "bulk" changes where the user may not want to open the applications menu each time.

When you right-click on a submenu's menu item, it should not close the submenu. Instead, it should bring up a context menu with additional options to edit this submenu in the menu editor, and to hide this submenu (as well as the existing options you would get from right-clicking on a menu item within that sub-menu). For a menu item, add extra context menu options to edit this menu item in the menu editor, to directly edit the menu item's launcher's properties, and to hide the menu item. It should also be possible to drag menu items (including entire sub-menus), within each menu. Additionally, each sub-menu item should have a "lock to menu" checkbox option on its context menu to prevent it from being dragged (similar to panel items' "lock to panel" checkbox option). It may even be possible to use panels and drawers to build the menus and use common code to handle the behaviour of both consistently. The edit menus item would still be needed to remove items, and would still be useful for "bulk" changes where the user may not want to open the applications menu each time.

Written by leael the 18 Apr 09 at 13:48.

To be consistent with the panels, the user has to unlock the menu in order for the drag'n'drop to become possible. Possible implementations could be a global "Unlock Menu Elements" or better "Allow Dragging of Menu Elements".

To be consistent with the panels, the user has to unlock the menu in order for the drag'n'drop to become possible. Possible implementations could be a global "Unlock Menu Elements" or better "Allow Dragging of Menu Elements".

Written by leael the 18 Apr 09 at 13:58.

To be consistent with the panels, each item gets an "Move" entry in its context menu, thus locking the item in the mouse and let the user drag it to other locations as also into submenus, until the mouse button is clicked again.

To be consistent with the panels, each item gets an "Move" entry in its context menu, thus locking the item in the mouse and let the user drag it to other locations as also into submenus, until the mouse button is clicked again.

Written by samtatr the 22 Feb 11 at 11:43.

This would make it more obvious as to what it does, and looks a lot cleaner when the notification pops up too. This has already been done for wireless networks (e.g. "Connected to NETGEAR"), so it shouldn't be too hard for wired ones.

This would make it more obvious as to what it does, and looks a lot cleaner when the notification pops up too. This has already been done for wireless networks (e.g. "Connected to NETGEAR"), so it shouldn't be too hard for wired ones.

Written by evanplaice the 25 Feb 11 at 19:57.

Because a network can represent a lot of things (mostly external to the computer) and don't accurately represent a computer's NIC, I'm proposing "Ethernet Connection" to be more precise while maintaining simplicity.

Call it what it is (or what the 802.3 spec calls it) but make it more recognizable to users (ie, don't start indices at 0).

Because a network can represent a lot of things (mostly external to the computer) and don't accurately represent a computer's NIC, I'm proposing "Ethernet Connection" to be more precise while maintaining simplicity. Call it what it is (or what the 802.3 spec calls it) but make it more recognizable to users (ie, don't start indices at 0).

Written by sivanmyl the 5 Mar 11 at 05:00.

Combined word looks more attractive while easy to understand.

Combined word looks more attractive while easy to understand.

Written by phix the 7 Mar 11 at 21:47.

Names are important, especially because commandline tools use the real name of the connection, Auto eth0. It's simple, symbolic, and descriptive. A longer name runs the risk of sounding dumbed-down and vague, like the dreaded "Wireless Connection 2" nonsense from windows. A description keeps the name short, while providing new users more information.

If the user had to do anything through the command line later on, they'll already be used to seeing "auto eth0" as their wired connection.

Names are important, especially because commandline tools use the real name of the connection, Auto eth0. It's simple, symbolic, and descriptive. A longer name runs the risk of sounding dumbed-down and vague, like the dreaded "Wireless Connection 2" nonsense from windows. A description keeps the name short, while providing new users more information. If the user had to do anything through the command line later on, they'll already be used to seeing "auto eth0" as their wired connection.

Written by juanjosepablos the 8 Mar 11 at 03:00.

This is a mix of Solution #1 and #4

This is a mix of Solution #1 and #4

Written by turbolad the 8 Mar 11 at 11:13.

Newbies see "Wired Network" and advanced users see "Auto eth0" in brackets/parenthesis.

I explain in the comments why this helps EVERYONE.

Newbies see "Wired Network" and advanced users see "Auto eth0" in brackets/parenthesis. I explain in the comments why this helps EVERYONE.

Written by mtrudel the 24 Mar 11 at 16:08.

I'm suggesting the name of the profile to be something like "Default". It should not be tied to any particular adapter.
This way, any new connection use that profile which will have default settings to use DHCP and the usual (as Auto eth0 is set). All adapters could share it, so adding a new interface to a computer would still just "work".

For notifications, I suggest the following changes:

- The title should mention "Wired network", and probably the same of the interface (eth0 in most cases).
- The text of the notification should say:

Connection established, using profile "Default"

or whatever profile in use.

I'm suggesting the name of the profile to be something like "Default". It should not be tied to any particular adapter. This way, any new connection use that profile which will have default settings to use DHCP and the usual (as Auto eth0 is set). All adapters could share it, so adding a new interface to a computer would still just "work". For notifications, I suggest the following changes: - The title should mention "Wired network", and probably the same of the interface (eth0 in most cases). - The text of the notification should say: Connection established, using profile "Default" or whatever profile in use.

Written by cheesehead the 24 Mar 11 at 17:56.

Interface names like 'eth0' and 'wlan0' are assigned by udev based on the interface's mac address (or other criteria you can specify in /etc/udev/rules/d).

Machine-readable interface names (like 'eth0') are an essential part of making networking work properly, and messing with the structure of those names is opening a can 'o bugs.

But *adding* an additional human-readable field (DESCRIPTION=='ethernet jack') makes the human-readable name accessible to all network applications. It also means the name is user-editable without upsetting the whole network stack.

So Network manager can show 'ethernet jack' (description) instead of 'eth0' (name). And the name can be changed by the user (or script) at any time, for example to match the name of the current network ('SpamNet [ethernet]')

Interface names like 'eth0' and 'wlan0' are assigned by udev based on the interface's mac address (or other criteria you can specify in /etc/udev/rules/d). Machine-readable interface names (like 'eth0') are an essential part of making networking work properly, and messing with the structure of those names is opening a can 'o bugs. But *adding* an additional human-readable field (DESCRIPTION=='ethernet jack') makes the human-readable name accessible to all network applications. It also means the name is user-editable without upsetting the whole network stack. So Network manager can show 'ethernet jack' (description) instead of 'eth0' (name). And the name can be changed by the user (or script) at any time, for example to match the name of the current network ('SpamNet [ethernet]')

Written by kiko_ubuntu the 26 Feb 11 at 21:34.

Independent volume settings internally, The same master slider is used but levels restored accordingly on the hardware switch.

Independent volume settings internally, The same master slider is used but levels restored accordingly on the hardware switch.

Written by fred_t the 1 Mar 11 at 10:45.

To avoid having to plug and unplug headphones, which is wearing the jack and is not always easy due to accessibility factors, it would also be possible to switch from headphones to speakers via a keyboard shortcut -- maybe special + s ? -- or an icon.

To avoid having to plug and unplug headphones, which is wearing the jack and is not always easy due to accessibility factors, it would also be possible to switch from headphones to speakers via a keyboard shortcut -- maybe special + s ? -- or an icon.

Written by sivanmyl the 5 Mar 11 at 05:27.

Normally the headphone socket cuts off speakers mechanically. At times, many people feel convenient to connect speakers while the headphone is connected. Hardware should change to an electronic switch and then it should be possible to make any selection in the software.

Normally the headphone socket cuts off speakers mechanically. At times, many people feel convenient to connect speakers while the headphone is connected. Hardware should change to an electronic switch and then it should be possible to make any selection in the software.

Written by mencey the 1 Mar 08 at 13:15.

Ubuntu Brainstorm was updated in January 2009. Since the idea #2160 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution. Thanks!

<i>Ubuntu Brainstorm was updated in January 2009. Since the idea #2160 was submitted before this update, its rationale and solution are not separated. Please vote accordingly, and if you have the necessary rights, please separate the rationale from the solution.</i><br /> Thanks!

Written by ParmuzinAlexandr the 2 Feb 11 at 20:27.

Example:

Example: <a target="_blank"; href="http://itmages.com/image/view/116288/1d02c654"><img src="http://storage7.static.itmages.com/i/11/0202/h_1296678251_1d02c654c1.png" /></a>

Written by ParmuzinAlexandr the 2 Feb 11 at 20:41.

Just text as in 10.04.

Just text as in 10.04. <a target="_blank"; href="http://itmages.com/image/view/117186/3e9f0a65"><img src="http://storage7.static.itmages.com/i/11/0204/h_1296824764_3e9f0a6522.png" /></a>

Written by Akerbos the 3 Feb 11 at 21:39.

Bring back the possibility to have country flags as icon.

Bring back the possibility to have country flags as icon. <a target="_blank"; href="http://itmages.com/image/view/117185/7a3becb4"><img src="http://storage6.static.itmages.com/i/11/0204/h_1296824654_7a3becb4c3.png" /></a>

Written by MIH1406 the 13 Feb 11 at 20:15.

Same as in solution #1 plus that I suggest that all languages have fixed width and, of course, height.

Same as in solution #1 plus that I suggest that all languages have fixed width and, of course, height.

Written by philip the 15 Feb 11 at 21:16.

Add a small colored flag next to the text cursor anywhere where text can be entered, or color the cursor itself. This would make it much easier for the user to know what keyboard mode they are in, without having to take away their focus from their work. Essentially it would remove the keyboard language mode because it would be obvious what state the keyboard is in at any time. (I don't know how technically feasible it is.)

Add a small colored flag next to the text cursor anywhere where text can be entered, or color the cursor itself. This would make it much easier for the user to know what keyboard mode they are in, without having to take away their focus from their work. Essentially it would remove the keyboard language mode because it would be obvious what state the keyboard is in at any time. (I don't know how technically feasible it is.)

Written by Oleksa the 17 Feb 11 at 21:03.

I propose to add a special user interface for the WiMAX wireless network connection to the Network Manager similar to wifi, when a user can switch on/off, get specific information about the signal level, close base station, set up IP address, try to locate existing channels (providers), share the connection with others, possibility to change the power mode for the device etc. A special tab should be added in the Network Manager, as well.

Related link: http://cgit.freedesktop.org/NetworkManager/NetworkManager

I propose to add a special user interface for the WiMAX wireless network connection to the Network Manager similar to wifi, when a user can switch on/off, get specific information about the signal level, close base station, set up IP address, try to locate existing channels (providers), share the connection with others, possibility to change the power mode for the device etc. A special tab should be added in the Network Manager, as well. Related link: http://cgit.freedesktop.org/NetworkManager/NetworkManager

Written by mydoghasworms the 10 Feb 11 at 19:04.

As a general rule, I think one ought to try avoid throwing up a lot of errors where a friendly message could tell you what the matter is.

What is the harm in stating the obvious to the user: "You cannot update because you are offline". It's way more elegant that throwing a bunch of errors in someone's face.

If there is no Internet connection, tell the user, so that there is no guesswork as to why packages could not be downloaded.

As a general rule, I think one ought to try avoid throwing up a lot of errors where a friendly message could tell you what the matter is. What is the harm in stating the obvious to the user: "You cannot update because you are offline". It's way more elegant that throwing a bunch of errors in someone's face. If there is no Internet connection, tell the user, so that there is no guesswork as to why packages could not be downloaded.

Written by lemuelinchrist the 22 Feb 11 at 01:58.

This isn't just a problem for Update Manager, but also for Firefox and just about any other App that requires an Internet connection.

If Ubuntu isn't connected and Firefox is opened, instead of showing an error, Firefox (or Update Manager, or any other app) should just show a list of available connections for the user to choose.

This isn't just a problem for Update Manager, but also for Firefox and just about any other App that requires an Internet connection. If Ubuntu isn't connected and Firefox is opened, instead of showing an error, Firefox (or Update Manager, or any other app) should just show a list of available connections for the user to choose.

Written by mat128 the 9 Mar 11 at 15:24.

Instead of simply checking if you are online, check if you can access the servers listed in the configuration. If access is impossible (servers are down, you are offline, or anything else), simply tell the user and offer him the possibility to retry.

Instead of simply checking if you are online, check if you can access the servers listed in the configuration. If access is impossible (servers are down, you are offline, or anything else), simply tell the user and offer him the possibility to retry.

Written by gregbenson314 the 21 Feb 11 at 22:03.

When you go to change the user account picture (system--> Preferences--> about me) and click to change the icon, a nautilus file browser pops up, and allows you to choose a picture.

I think it would be good to have a "Take a picture now" option, that uses the webcam to take a picture. If the user likes it, it could be used as the account picture. If the user doesn't like it, another picture could be taken (discarding all previous attempts) until the user is happy. They could cancel at any time.

When you go to change the user account picture (system--> Preferences--> about me) and click to change the icon, a nautilus file browser pops up, and allows you to choose a picture. I think it would be good to have a "Take a picture now" option, that uses the webcam to take a picture. If the user likes it, it could be used as the account picture. If the user doesn't like it, another picture could be taken (discarding all previous attempts) until the user is happy. They could cancel at any time.

Written by CydeSwype the 27 Jul 09 at 19:14.

Add option to evolution to allow sync with Empathy

Add option to evolution to allow sync with Empathy

Written by Mike_IronFist the 8 Aug 09 at 06:18.

No matter what the developers of Empathy are PROMISING, currently it's in no shape to replace Pidgin as the default instant messenger. This problem itself further proves that replacing Pidgin with Empathy in its current state is detrimental to the quality of Ubuntu.

No matter what the developers of Empathy are PROMISING, currently it's in no shape to replace Pidgin as the default instant messenger. This problem itself further proves that replacing Pidgin with Empathy in its current state is detrimental to the quality of Ubuntu.

Written by epritchett the 10 Aug 09 at 16:22.

Create a plugin for both Evolution and Empathy that utilize Meta-contacts using People Project and/or Soylent (coalesce multiple IM contacts into one contact when belonging to the same person). This is already on Empathy's 3.?? Roadmap. This would allow both programs (as well as others in teh future) to utilize the same contact database rather than creating synced copies everywhere.

Create a plugin for both Evolution and Empathy that utilize Meta-contacts using People Project and/or Soylent (coalesce multiple IM contacts into one contact when belonging to the same person). This is already on Empathy's 3.?? Roadmap. This would allow both programs (as well as others in teh future) to utilize the same contact database rather than creating synced copies everywhere.

Written by jerzyo the 1 Feb 11 at 06:53.

In screens configuration make an option "Use separate workspaces on separate devices"

In that case I see 2 options:

1.User will have Separate full desktop on different devices (full option) and an applet to switch mouse between them

2. On one device user will have an empty screen with the ability to display (an applet?) a copy of a specific workspace. I mean Something like dual screen but with the possibility to copy a screen from a workspace that you don't use


The idea is to make it work for every laptop, despite the graphics card used. Graphics card will be only able to accelerate the system

In screens configuration make an option "Use separate workspaces on separate devices" In that case I see 2 options: 1.User will have Separate full desktop on different devices (full option) and an applet to switch mouse between them 2. On one device user will have an empty screen with the ability to display (an applet?) a copy of a specific workspace. I mean Something like dual screen but with the possibility to copy a screen from a workspace that you don't use The idea is to make it work for every laptop, despite the graphics card used. Graphics card will be only able to accelerate the system

Written by drnessie the 19 Feb 11 at 09:00.

Provide a dialogue that says "Use as Secondary Workspace" or "Extend Workspace"

Provide a dialogue that says "Use as Secondary Workspace" or "Extend Workspace"

Written by Darwin Survivor the 25 Feb 11 at 05:06.

#1 but Add 3 radio buttons:
1) Just this once (always ask)
2) Always do this
3) Always do this for this monitor (using some basic monitor tracking system like S/N or something)

#1 but Add 3 radio buttons: 1) Just this once (always ask) 2) Always do this 3) Always do this for this monitor (using some basic monitor tracking system like S/N or something)