Public bug reported: As it stands, I really love the physics of how the unity dock opens from its hidden state. (For clarification, the "dock" I'm speaking of is on the left side of the screen, and has large icons for opening up useful apps.)
For those unfamiliar with its "Physics", the unity dock doesn't open after a mouse-over. Nor does it respond to a direct impact of the mouse, which you can see for yourself by pushing the mouse roughly into the dock and stopping right after it touches. The physics of the dock opening is perhaps most similar to what it's like to raise open blinds via a string handle. (link to what I mean http://www.blindalley.com/portfolios/levolor/images/levolorlift.jpg). It requires you to move the mouse to the edge, and then push it against the edge for some "distance". I think its great, but the one problem is first figuring out how to use it. It took a few hours of casual computer use for me to actually understand how to consistently open the dock with minimal effort. (Something like 10 total, sporadic attempts at opening the dock). I tried mousing-over, got a bit frustrated since that doesn't open the dock, then smashed it into it, which works sometimes. In spite of being an Ubuntu user for over 5 years, I'd call the learning experience a bit of a minor struggle. Perhaps there could be a triggered tutorial of how to use the dock? Some system "pop-up" or message that shows up the first time you inefficiently open the dock, or the first time you enable "hide dock". There could be some reasonable and easy heuristics for exactly what triggers the message. Let's discuss! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,move,resize,compiztoolbox,place,vpswitch,gnomecompat,grid,session,regex,snap,animation,workarounds,mousepoll,imgpng,unitymtgrabhandles,wall,expo,ezoom,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Apr 22 21:06:39 2014 DistUpgraded: 2014-02-27 15:02:05,429 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0007] MachineType: TOSHIBA PORTEGE R705 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-generic root=UUID=e34a4d0a-6d04-42c5-a170-9ff6d2812d56 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-27 (54 days ago) dmi.bios.date: 11/11/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.70 dmi.board.asset.tag: 0000000000 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 0000000000 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.70:bd11/11/2010:svnTOSHIBA:pnPORTEGER705:pvrPT314U-017018:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE R705 dmi.product.version: PT314U-017018 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Apr 22 20:47:22 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 saucy ubuntu -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1311457 Title: feature request: triggered tutorial for opening hidden dock Status in “unity” package in Ubuntu: New Bug description: As it stands, I really love the physics of how the unity dock opens from its hidden state. (For clarification, the "dock" I'm speaking of is on the left side of the screen, and has large icons for opening up useful apps.) For those unfamiliar with its "Physics", the unity dock doesn't open after a mouse-over. Nor does it respond to a direct impact of the mouse, which you can see for yourself by pushing the mouse roughly into the dock and stopping right after it touches. The physics of the dock opening is perhaps most similar to what it's like to raise open blinds via a string handle. (link to what I mean http://www.blindalley.com/portfolios/levolor/images/levolorlift.jpg). It requires you to move the mouse to the edge, and then push it against the edge for some "distance". I think its great, but the one problem is first figuring out how to use it. It took a few hours of casual computer use for me to actually understand how to consistently open the dock with minimal effort. (Something like 10 total, sporadic attempts at opening the dock). I tried mousing-over, got a bit frustrated since that doesn't open the dock, then smashed it into it, which works sometimes. In spite of being an Ubuntu user for over 5 years, I'd call the learning experience a bit of a minor struggle. Perhaps there could be a triggered tutorial of how to use the dock? Some system "pop-up" or message that shows up the first time you inefficiently open the dock, or the first time you enable "hide dock". There could be some reasonable and easy heuristics for exactly what triggers the message. Let's discuss! ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: unity 7.1.2+13.10.20131014.1-0ubuntu1 ProcVersionSignature: Ubuntu 3.11.0-19.33-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic x86_64 .tmp.unity.support.test.0: ApportVersion: 2.12.5-0ubuntu2.2 Architecture: amd64 CompizPlugins: [core,bailer,detection,composite,opengl,decor,move,resize,compiztoolbox,place,vpswitch,gnomecompat,grid,session,regex,snap,animation,workarounds,mousepoll,imgpng,unitymtgrabhandles,wall,expo,ezoom,fade,scale,unityshell] CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Tue Apr 22 21:06:39 2014 DistUpgraded: 2014-02-27 15:02:05,429 DEBUG enabling apt cron job DistroCodename: saucy DistroVariant: ubuntu GraphicsCard: Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0007] MachineType: TOSHIBA PORTEGE R705 MarkForUpload: True ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-19-generic root=UUID=e34a4d0a-6d04-42c5-a170-9ff6d2812d56 ro quiet splash vt.handoff=7 SourcePackage: unity UpgradeStatus: Upgraded to saucy on 2014-02-27 (54 days ago) dmi.bios.date: 11/11/2010 dmi.bios.vendor: TOSHIBA dmi.bios.version: Version 1.70 dmi.board.asset.tag: 0000000000 dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Version A0 dmi.chassis.asset.tag: 0000000000 dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: Version 1.0 dmi.modalias: dmi:bvnTOSHIBA:bvrVersion1.70:bd11/11/2010:svnTOSHIBA:pnPORTEGER705:pvrPT314U-017018:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0: dmi.product.name: PORTEGE R705 dmi.product.version: PT314U-017018 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.10+13.10.20131011-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.46-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 9.2.1-1ubuntu3 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 9.2.1-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.14.5-1ubuntu2~saucy1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu3.1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.2.0-0ubuntu10 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.904-0ubuntu2.1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.9-2ubuntu1 xserver.bootTime: Tue Apr 22 20:47:22 2014 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.14.5-1ubuntu2~saucy1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1311457/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
