Unity
|
Size: 2991
Comment:
|
Size: 3728
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| = Unity = [[http://unity.ubuntu.com|Unity Homepage]] - This wiki area is for technical work See [[attachment:Unity_Architecture.pdf|Unity Architecture]] |
||<style="width: 600px; background-color: #FFFFAA;">/!\ '''Notice:''' The information on this page is likely to change soon as we switch our development focus to the !UnityNext project. For more information about !UnityNext, please read [[UnityNextSpec|the spec]].|| |
| Line 10: | Line 7: |
| = How to test Unity = | ##= Unity = H1/titles are redundant in the Ubuntu Wiki. This is already the page name and will be rendered as the top-most H1 as a result. (Note that it won't show up on the preview, but will after you save.) |
| Line 12: | Line 9: |
| == On Maverick (10.10) == | The wiki documentation is targeting technical users, if you want to get an overview of Unity you might be interested ready those: |
| Line 14: | Line 11: |
| [[https://wiki.ubuntu.com/Unity/InstallationGuide|Installation Guide]] for Unity 3.0 (experimental) | * [[http://unity.ubuntu.com|Unity Homepage]] * [[attachment:Unity_Architecture.pdf|Unity Architecture]] * [[Unity/Lenses | Unity Lenses]] - Information for developers for implementing Unity Lenses, which are plugabble elements to the Unity Dash. * [[Unity/HUD | Unity HUD]] - '''[Experimental]''' Information for developers for integrating with the Unity HUD, which is an intent-driven alternate interface to application menus. * [[Unity/Bitesize|Unity Bitesize Bugs]] - A great place for new hackers to contribute improvements and fixes. * [[Unity/CodingStyle|Coding Style Guidelines]] * [[Unity/CodeReviews|Standards for Unity Code Reviews (Merge Proposals)]] * [[Unity/LauncherAPI|Launcher Integration]] - For application developers that want to add progress bars and other "overlays" onto their icon in the Unity Launcher |
| Line 16: | Line 21: |
| === on UNE edition === | == Frequently Asked Questions == |
| Line 18: | Line 23: |
| Unity is the default UI for Ubuntu Netbook Edition on 10.10. The easiest way to test it is to install the Netbook Edition of the 10.10 development cycle from the daily built iso [[http://cdimage.ubuntu.com/ubuntu-netbook/daily-live/current/|available here]] or use [[https://edge.launchpad.net/testdrive|testdrive]]. | * [[https://wiki.ubuntu.com/DemystifyingUnityGraphicsHardwareRequirements|Hardware Requirements]] * [[http://askubuntu.com/questions/29553/how-can-i-configure-unity|How to configure Unity]] - For Natty we're concentrating on shipping good defaults, however you can still change some things around. * [[http://askubuntu.com/questions/10228/whats-the-right-terminology-for-unitys-ui-elements/19166#19166|Unity Terminology]] - this page explains what we call the different parts of the UI * [[http://askubuntu.com/questions/28086/unity-keyboard-mouse-shortcuts|Keyboard Shortcuts]] * [[https://wiki.ubuntu.com/Unity/InstallationGuideFromSource|Building Unity from Source]] - For developers who want to learn how to build Unity and Nux. * [[http://askubuntu.com/tags/unity/faq|Full FAQ]] |
| Line 20: | Line 30: |
| === with a standard ubuntu-desktop edition === | == How and where to file bugs == |
| Line 22: | Line 32: |
| 1. Run just `sudo apt-get install ubuntu-netbook` 1. This will add in GDM a "Ubuntu Netbook Edition" menu option when you click on your username. Select it and login to get the Unity interface. |
=== Crash bugs === The most valuable bug reports are crash reports. |
| Line 25: | Line 35: |
| == on lucid (10.04 LTS) == | After installing, enable apport: edit /etc/default/apport, set enabled=1 and restart you computer. Once activated the system should detect crashes and prompt you to report those. |
| Line 27: | Line 37: |
| Unity is primarily built for maverick (10.10), but we are conscious that some people want to test it on lucid. For those, we have setup a PPA and backport unity component to lucid. | === Non crash bugs === |
| Line 29: | Line 39: |
| ||<style="background:Peru">Note: The Unity PPA brings in some lower level components that we need like a new GTK and some new libraries. You should be comfortable with being able to downgrade multiple packages if you want to go back to a stable Lucid, otherwise we recommend a virtualization tool like [[http://launchpad.net/testdrive|testdrive]] to test Unity.|| | The best way to log a bug is to use this command: |
| Line 31: | Line 41: |
| 1. If you are on Lucid, load a terminal and run `sudo add-apt-repository ppa:canonical-dx-team/une` and `sudo apt-get update`. 1. Run `sudo apt-get install ubuntu-netbook-unity-default-settings`. 1. Logout and choose in GDM your "Ubuntu Unity Netbook Edition" menu option when you click on your username |
{{{ ubuntu-bug unity }}} |
| Line 35: | Line 45: |
| == How can I get the old Lucid (10.04) interface back on Maverick (10.10)? == | It will collect the required details and send you to launchpad to write your bug description. |
| Line 37: | Line 47: |
| How can I restore the old 10.04 interface in UNE Maverick? The section above just explains the opposite way (running 10.04 with the 10.10 Unity interface). |
(If you build Unity from source or want to open a bug without using ubuntu-bug please follow [[Unity/FilingBugs|this guide]]) |
| Line 40: | Line 49: |
| == is there a difference from the maverick version? == | === Window matching problems === |
| Line 42: | Line 51: |
| Apart from the fact we have a different session name "Unity" instead of "UNE" and a fake metapackage "ubuntu-netbook-unity-default-settings", the behavior is the same. The only other difference is that you still can have netbook-launcher (the 10.04 LTS UNE interface) in a parallel install than Unity. | If you notice a problem with an application icon in the launcher (blurry icon, pinning not working, etc.), Unity is probably having some problems matching the window to the correct .desktop file. Please edit [[https://wiki.ubuntu.com/Unity/WindowMatching|this wiki page]] with the details of any problems of this kind you find. == How to Contribute to Unity == http://unity.ubuntu.com/getinvolved/ has instructions on how to get the code and hack on it. |
| Line 47: | Line 60: |
| * To report bugs: see [[UnityFilingBugs]] | * To report bugs: see [[Unity/FilingBugs]] |
| Line 49: | Line 62: |
| == Measuring Power Consumption == It's important to ensure that we're power efficient. We recommend that you also install [[apt://powertop|Powertop]] and run it in a terminal to gather information. [[http://www.lesswatts.org/projects/powertop/|Powertop Homepage]] http://www.lesswatts.org/projects/powertop/ |
---- CategoryDocumentation CategoryDocteam |
/!\ Notice: The information on this page is likely to change soon as we switch our development focus to the UnityNext project. For more information about UnityNext, please read the spec. |
The wiki documentation is targeting technical users, if you want to get an overview of Unity you might be interested ready those:
Unity Lenses - Information for developers for implementing Unity Lenses, which are plugabble elements to the Unity Dash.
Unity HUD - [Experimental] Information for developers for integrating with the Unity HUD, which is an intent-driven alternate interface to application menus.
Unity Bitesize Bugs - A great place for new hackers to contribute improvements and fixes.
Launcher Integration - For application developers that want to add progress bars and
other "overlays" onto their icon in the Unity Launcher
Frequently Asked Questions
How to configure Unity - For Natty we're concentrating on shipping good defaults, however you can still change some things around.
Unity Terminology - this page explains what we call the different parts of the UI
Building Unity from Source - For developers who want to learn how to build Unity and Nux.
How and where to file bugs
Crash bugs
The most valuable bug reports are crash reports.
After installing, enable apport: edit /etc/default/apport, set enabled=1 and restart you computer. Once activated the system should detect crashes and prompt you to report those.
Non crash bugs
The best way to log a bug is to use this command:
ubuntu-bug unity
It will collect the required details and send you to launchpad to write your bug description.
(If you build Unity from source or want to open a bug without using ubuntu-bug please follow this guide)
Window matching problems
If you notice a problem with an application icon in the launcher (blurry icon, pinning not working, etc.), Unity is probably having some problems matching the window to the correct .desktop file. Please edit this wiki page with the details of any problems of this kind you find.
How to Contribute to Unity
http://unity.ubuntu.com/getinvolved/ has instructions on how to get the code and hack on it.
Support
Please consult the Hardware Requirements for Unity.
To report bugs: see Unity/FilingBugs
Unity (last edited 2014-01-21 18:49:47 by 3v1n0)