[Ayatana-dev] Compiz Community Module Maintainers
Hi everyone, At UDS I discussed the idea of having community module maintainers for the various bits in compiz, so that we can delegate community members who are interested in the vision of one particular module or plugin (or many of them, if they choose) to be the maintainer for it. They will be responsible for developing the code to fit their vision, doing pre-commit code review (another mail coming about that shortly), maintaining the bug list and being the contact person for questions about that module. The reason that I am doing this is because I've found that I've had limited time to be the maintainer of everything and I've found that certain modules are suffering from bitrot because nobody has time to work on them. I think that if nobody has time to work on a module or a plugin or something, it needs to become unsupported and we need to let distributions know about this. However, I believe that to a certain extent, we should have a category for modules where we will at least work to keep them supported with API changes and the like. So here is the deal. 1) All modules will be marked us unmaintained from this point in. If someone wants to claim maintainership of a module, they'll need to post a mail here explaining why they want to be the maintainer for that module and what they think their qualification is for doing so. Note here that since we need maintainers more than anything else right now, I would imagine that the qualification bar here will be quite low for modules that are already effectively unmaintained. 2) There will be certain modules (such as core and plugins main) that I would imagine would have multiple maintainers. In this case, to get code upstream, it needs to be reviewed by ALL the maintainers within some timeframe 3) I'll start by saying that I'll claim maintenance of the stuff in plugins-main and core, subject to whatever that will be (another mail coming about that one shortly). If anybody else wants to claim for that, just send me an email to the list. Furthermore, I'll be starting to reach out to external contributors who might be interested in maintaining various plugins. I think with a more diverse development community focused on the little things Compiz can grow as a project. Regards, Sam -- Sam Spilsbury ___ Mailing list: https://launchpad.net/~ayatana-dev Post to : ayatana-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana-dev More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Dash Idea – Easy Lens Switcher
The results of this list and launchpad are often contradictory, or not in conjunction with Unity design ideas. It seems very helpful to collect, filter, and formalize the good ideas floating around and create one document, where the developers can look. It saves them time, and gives them more detail than separate mailing list threads do. 2011/5/26 Ed Lin edlin...@gmail.com On Thu, May 26, 2011 at 9:26 PM, Arian van Gend aria...@gmail.com wrote: I've started a Unity 11.10 design document to formalize the contributions of the community to Unity design. It also covers improving the lenses and the Dash. Maybe you could read it, and if someone feels like it, improve the idea described there? The document can be found here: https://docs.google.com/document/d/13d-82URPS09y7KU2JntbvT_JkFXYxccNKFWOUj0Mhdw/edit?hl=en_GBauthkey=CPXZ690J# It should be regarded as a work in progress. Yet another place to keep track besides the list and launchpad? Do we really need that? I'm already doing more information micromanagement (and a lot of copy/pasting URLs) than actual design discussion. ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp -- http://avond.schemering.nl ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
[Ayatana] Understanding the menu problem.
Since I've only recently joined this list and community, I'm sure to have missed out on some good discussions. I have some ideas for improving the menus, but if they've already been discussed and ruled out, then I don't want to waste time jabbering on about them. So please help me catch up. I appreciate it. And just to emphasize; it's not my intention to start a discussion. I only want a thorough understanding of the situation. When a window is maximized, the menu and window buttons are moved to the top panel and the window title shares space with the window menu, displaying the menu when you hover and the title when you don't. I don' think I've read any arguments against this. Are there any? When a window is not maximized, for example when you drag it away from the top panel, the menu remains on the top panel, but instead of showing the window title, it shows the applications name. There are a few arguments for and aganst this: Pros: * Having a menu next to the screen edge makes it easier to hit with the mouse according to Fitts' Law. * Hiding the menu when you're not using it, makes the desktop feel less cluttered and technical. * When the menu is always located at the same place, it's easier for users to find it. Cons: * Having a hidden global menu for a window that is not maximized, makes it difficult to find, specially for new users. * If the window is far away from the top panel, then you have to make a long mouse-journey to get to the menu. * If you use focus follows pointer, then you can focus a different window on your way to the menu, changing the menu before you get there. * The global menu itself creates a mental disconnection between the window and its menu, whether its hidden or not. Have I missed something, or is that pretty much it? Next. What is the main reason for wanting the global menu in the first place? Is it to conserve screen space and remove clutter, or is is it more about Fitts' Law and similar considerations? What exactly are the current plans? Thank you. Jo-Erlend Schinstad ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Understanding the menu problem.
On Fri, 2011-05-27 at 14:45 +0200, Jo-Erlend Schinstad wrote: Next. What is the main reason for wanting the global menu in the first place? Here, there reason was explained: http://design.canonical.com/2010/05/menu-bar/ ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
[Ayatana] A realistic vision of the next iteration of Unity
Hello everybody! After I've taken part in a lot of discussions since the release of Ubuntu 11.04 I've finally come up with a complete list (for the moment) of features and changes which I and hopefully the rest of the Ubuntu community would like to see implemented. Since it's a rather extensive list have I grouped every topic into sections and accompanied all the features/changes with mockups. I had problems with taking screenshots of the dash and context menus, I later found that this was a bug, so I made many of the UI-elements from scratch by referencing some Natty Alpha screenshots I found (until I thought of taking pictures in a virtual machine). If you need a Unity photoshop template you can download the PSD-file here: http://tests.nsrosenqvist.com/resources/Unity-2.0.psd.zip - *Lenses - Dash* * * As the lenses are currently implemented they are not as effective little applications as they were originally planned to be. First of all, the lenses inhabiting the launcher are just wasting launcher space. By searching in the dash you still get the results from the lenses which are installed by default on a Ubuntu 11.04 installation, without needing to go through their respective launchers. When I first heard of lenses I was intrigued but later when I learned that every lens would take up valuable launcher space they just felt unnecessary. I wouldn't want to explore new lenses if they were going to occupy my launcher bar. But I think that by including them into the dash we would more effectively handle lenses. There would only be one lens - the dash - and within it you could specify further which lens you would like to use if you aren't happy with the search results. My guess is that most people are using the dash to search for files and applications, much like they do with programs as Gnome-Do so this would be the default search feature. But as you can see in the image provided below you can see how easy it would be to search from another lens: http://i.imgur.com/76Jge.jpg (Note: The icons used for other services are taken off the internet and I haven't looked up the license terms for them) - *Launcher bottom area* * * In the previous mockup you might have noticed that in the bottom of the launcher is a bar with the same height as the top panel and the same width as the Ubuntu button (Sorry for not knowing the correct terminology). I've removed the trash/wastebasket from the launcher since it has been noted several times in the ayatana discussions that it can just as easily be accessed from within Nautilus and isn't important enough to take up a whole launcher. Though it's very important that new users to Ubuntu are finding familiar elements to their previous OS of choice (e.g. OS X or Win) and both provide a clear trash launcher/shortcut. So instead of removing it completely I integrated it into the bottom area of the launcher together with the most important part of this area...* * I don't know what to call the button farthest down in the left corner since it's a multifunction button. As default it triggers the workspace switcher, this enables us to remove it from the launcher, and to be fair it wasn't a very good place for it to be to begin with. Sure it's on the edge of the screen but having it in the bottom corner makes it incredibly easy to access (Fitt's Law), very much like the show desktop-button in Win7. Now you can just through the cursor into the corner and almost always hit it instead of having to aim for it on the launcher. But since there are so many ways of switching windows I figured that it should be configurable to trigger the function which the current user prefer. By providing a context menu to it together with options to set one of the following (are there more alternatives?) as default: Workspace Switcher, Spread, Expo mode, Alt+Tab, and Show desktop. - *Toggle background lighting as default and window management* You might also have noticed that the launchers have their background lighting set to toggle. In a default Ubuntu 11.04 installation all launchers have brightly colored backgrounds, this has been shown confusing for new users (source email: [Ayatana] Fwd: Re: People expect the backlight colours on the unity launcher to mean something) since they expect the color to mean something. I also like that running applications are shown more clearly instead of just the arrow on the left side of the launcher. It's much easier to switch between running applications by the launcher with this. I know that the launcher behaves more like a dock than a task bar but we have had bunch of discussions on app-centric vs window-centric and I think in everyone of them we've agreed on that we should make users coming from both OS X and Win should be somewhat familiar with how it all works. It's also incredibly frustrating to work with many open windows of the same application and expose or scale doesn't provide any information of what the different windows contain if
Re: [Ayatana] A realistic vision of the next iteration of Unity
Forgot about removing the display on hover feature of the global menu. It should without a doubt be set to always visible by default! 2011/5/27 Niklas Rosenqvist niklas.s.rosenqv...@gmail.com Hello everybody! After I've taken part in a lot of discussions since the release of Ubuntu 11.04 I've finally come up with a complete list (for the moment) of features and changes which I and hopefully the rest of the Ubuntu community would like to see implemented. Since it's a rather extensive list have I grouped every topic into sections and accompanied all the features/changes with mockups. I had problems with taking screenshots of the dash and context menus, I later found that this was a bug, so I made many of the UI-elements from scratch by referencing some Natty Alpha screenshots I found (until I thought of taking pictures in a virtual machine). If you need a Unity photoshop template you can download the PSD-file here: http://tests.nsrosenqvist.com/resources/Unity-2.0.psd.zip - *Lenses - Dash* * * As the lenses are currently implemented they are not as effective little applications as they were originally planned to be. First of all, the lenses inhabiting the launcher are just wasting launcher space. By searching in the dash you still get the results from the lenses which are installed by default on a Ubuntu 11.04 installation, without needing to go through their respective launchers. When I first heard of lenses I was intrigued but later when I learned that every lens would take up valuable launcher space they just felt unnecessary. I wouldn't want to explore new lenses if they were going to occupy my launcher bar. But I think that by including them into the dash we would more effectively handle lenses. There would only be one lens - the dash - and within it you could specify further which lens you would like to use if you aren't happy with the search results. My guess is that most people are using the dash to search for files and applications, much like they do with programs as Gnome-Do so this would be the default search feature. But as you can see in the image provided below you can see how easy it would be to search from another lens: http://i.imgur.com/76Jge.jpg (Note: The icons used for other services are taken off the internet and I haven't looked up the license terms for them) - *Launcher bottom area* * * In the previous mockup you might have noticed that in the bottom of the launcher is a bar with the same height as the top panel and the same width as the Ubuntu button (Sorry for not knowing the correct terminology). I've removed the trash/wastebasket from the launcher since it has been noted several times in the ayatana discussions that it can just as easily be accessed from within Nautilus and isn't important enough to take up a whole launcher. Though it's very important that new users to Ubuntu are finding familiar elements to their previous OS of choice (e.g. OS X or Win) and both provide a clear trash launcher/shortcut. So instead of removing it completely I integrated it into the bottom area of the launcher together with the most important part of this area...* * I don't know what to call the button farthest down in the left corner since it's a multifunction button. As default it triggers the workspace switcher, this enables us to remove it from the launcher, and to be fair it wasn't a very good place for it to be to begin with. Sure it's on the edge of the screen but having it in the bottom corner makes it incredibly easy to access (Fitt's Law), very much like the show desktop-button in Win7. Now you can just through the cursor into the corner and almost always hit it instead of having to aim for it on the launcher. But since there are so many ways of switching windows I figured that it should be configurable to trigger the function which the current user prefer. By providing a context menu to it together with options to set one of the following (are there more alternatives?) as default: Workspace Switcher, Spread, Expo mode, Alt+Tab, and Show desktop. - *Toggle background lighting as default and window management* You might also have noticed that the launchers have their background lighting set to toggle. In a default Ubuntu 11.04 installation all launchers have brightly colored backgrounds, this has been shown confusing for new users (source email: [Ayatana] Fwd: Re: People expect the backlight colours on the unity launcher to mean something) since they expect the color to mean something. I also like that running applications are shown more clearly instead of just the arrow on the left side of the launcher. It's much easier to switch between running applications by the launcher with this. I know that the launcher behaves more like a dock than a task bar but we have had bunch of discussions on app-centric vs window-centric and I think in everyone of them we've agreed on that we should
Re: [Ayatana] Understanding the menu problem.
On Fri, May 27, 2011 at 2:45 PM, Jo-Erlend Schinstad joerlend.schins...@gmail.com wrote: When a window is maximized, the menu and window buttons are moved to the top panel and the window title shares space with the window menu, displaying the menu when you hover and the title when you don't. I don' think I've read any arguments against this. Are there any? Basically yes. With the one exception that some apps maximized might benefit from a different layout (e.g. tabs on top). The second idea was to make the app and window title and the menu always visible side by side (see OS X or some mockups posted here). Pros: * Having a menu next to the screen edge makes it easier to hit with the mouse according to Fitts' Law. This only applies to a menu that is visible all the times. * Hiding the menu when you're not using it, makes the desktop feel less cluttered and technical. this applies less if the menu is visible all the times... * When the menu is always located at the same place, it's easier for users to find it. Usability testing has shown repeatedly that this is not the case, at least not if the menu is hidden. Even then, this directly conflicts with your con point 4 below. Cons: * Having a hidden global menu for a window that is not maximized, makes it difficult to find, specially for new users. see above, a better con would be that the menu is confusing to some users (it changes if you click on the desktop for example) and the ugly maximized window behind windowed window case. * If the window is far away from the top panel, then you have to make a long mouse-journey to get to the menu. This is not a given. We've analyzed this theoretically based on Fitts's Law but only came to the conclusion that we needed to test this. It's very much possible that even on a 30 the global menu is faster to access under a few conditions: the user is able and willing to quickly accelerate the mouse (laziness and inertia as I called it), he doesn't constantly switch between a few applications, he doesn't after executing a command from the menu immediately have to click on a small target within the window and finally: he actually uses the menu at all and not just keyboard shortcuts and in-window buttons in which case he'd benefit more from having controls he actually accesses at the screen edge. IMO this kind of makes the whole speed argument moot and leaves clutter and screen estate savings for tiled windows as the only pros. The first is problematic because it only hides complexity not solve the actual problem, the second is not a very common user case... * If you use focus follows pointer, then you can focus a different window on your way to the menu, changing the menu before you get there. This can be ignored, it's a corner case that doesn't apply to the general user base. We should first focus on making the interface work right in its default configuration. * The global menu itself creates a mental disconnection between the window and its menu, whether its hidden or not. For example on a busy desktop with many open apps you first need to leave the window, search through the menu and then search for the window. Have I missed something, or is that pretty much it? Yes, multi-tasking, tabs on top and the problem of useless fall back menus that are just there for the sake of consistency. Next. What is the main reason for wanting the global menu in the first place? Is it to conserve screen space and remove clutter, or is is it more about Fitts' Law and similar considerations? The former, Fitts's Law does not apply to hidden targets and in modern apps menus aren't very frequently accessed to warrant this special position. What exactly are the current plans? Good question. Thanks for the post, it forced me to recap everything and serves as a good summary which was badly needed. Hope I haven't left out anything important. ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Understanding the menu problem.
On Fri, May 27, 2011 at 3:21 PM, Omer Akram om26er.l...@gmail.com wrote: On Fri, 2011-05-27 at 14:45 +0200, Jo-Erlend Schinstad wrote: Next. What is the main reason for wanting the global menu in the first place? Here, there reason was explained: http://design.canonical.com/2010/05/menu-bar/ This was when Unity was still only planned for netbooks. Also it's focusing on basically one aspect of many, not a very helpful post at all. ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] A realistic vision of the next iteration of Unity
Hi Niklas! We seem to have a similar idea on unifying all the ideas floating around and getting more developer feedback on them. I made a google doc to start and collect the best ideas floating around and merging them into one unified design document to offer the Ubuntu developers. Two people frequenting this mailing list have already added their own pieces to it. You can find it here: https://docs.google.com/document/d/13d-82URPS09y7KU2JntbvT_JkFXYxccNKFWOUj0Mhdw/edit?hl=en_GBauthkey=CPXZ690Jhttps://docs.google.com/document/d/13d-82URPS09y7KU2JntbvT_JkFXYxccNKFWOUj0Mhdw/edit?hl=en_GBauthkey=CPXZ690Jpli=1# I see your ideas seem to take a somewhat different approach to Unity, but perhaps we can still discuss the differences and move towards a unified effort? Let me know what you think. Kind regards, Arian 2011/5/27 Niklas Rosenqvist niklas.s.rosenqv...@gmail.com Forgot about removing the display on hover feature of the global menu. It should without a doubt be set to always visible by default! 2011/5/27 Niklas Rosenqvist niklas.s.rosenqv...@gmail.com Hello everybody! After I've taken part in a lot of discussions since the release of Ubuntu 11.04 I've finally come up with a complete list (for the moment) of features and changes which I and hopefully the rest of the Ubuntu community would like to see implemented. Since it's a rather extensive list have I grouped every topic into sections and accompanied all the features/changes with mockups. I had problems with taking screenshots of the dash and context menus, I later found that this was a bug, so I made many of the UI-elements from scratch by referencing some Natty Alpha screenshots I found (until I thought of taking pictures in a virtual machine). If you need a Unity photoshop template you can download the PSD-file here: http://tests.nsrosenqvist.com/resources/Unity-2.0.psd.zip - *Lenses - Dash* * * As the lenses are currently implemented they are not as effective little applications as they were originally planned to be. First of all, the lenses inhabiting the launcher are just wasting launcher space. By searching in the dash you still get the results from the lenses which are installed by default on a Ubuntu 11.04 installation, without needing to go through their respective launchers. When I first heard of lenses I was intrigued but later when I learned that every lens would take up valuable launcher space they just felt unnecessary. I wouldn't want to explore new lenses if they were going to occupy my launcher bar. But I think that by including them into the dash we would more effectively handle lenses. There would only be one lens - the dash - and within it you could specify further which lens you would like to use if you aren't happy with the search results. My guess is that most people are using the dash to search for files and applications, much like they do with programs as Gnome-Do so this would be the default search feature. But as you can see in the image provided below you can see how easy it would be to search from another lens: http://i.imgur.com/76Jge.jpg (Note: The icons used for other services are taken off the internet and I haven't looked up the license terms for them) - *Launcher bottom area* * * In the previous mockup you might have noticed that in the bottom of the launcher is a bar with the same height as the top panel and the same width as the Ubuntu button (Sorry for not knowing the correct terminology). I've removed the trash/wastebasket from the launcher since it has been noted several times in the ayatana discussions that it can just as easily be accessed from within Nautilus and isn't important enough to take up a whole launcher. Though it's very important that new users to Ubuntu are finding familiar elements to their previous OS of choice (e.g. OS X or Win) and both provide a clear trash launcher/shortcut. So instead of removing it completely I integrated it into the bottom area of the launcher together with the most important part of this area...* * I don't know what to call the button farthest down in the left corner since it's a multifunction button. As default it triggers the workspace switcher, this enables us to remove it from the launcher, and to be fair it wasn't a very good place for it to be to begin with. Sure it's on the edge of the screen but having it in the bottom corner makes it incredibly easy to access (Fitt's Law), very much like the show desktop-button in Win7. Now you can just through the cursor into the corner and almost always hit it instead of having to aim for it on the launcher. But since there are so many ways of switching windows I figured that it should be configurable to trigger the function which the current user prefer. By providing a context menu to it together with options to set one of the following (are there more alternatives?) as default: Workspace Switcher, Spread, Expo mode, Alt+Tab, and
Re: [Ayatana] A realistic vision of the next iteration of Unity
Great post! Thank you for the nice mockups too! Absolutely no idea if this is considered realistic but lets hope so. I really have no critical feedback (so far) just a few amendments: Compiz should get some love see Remember window positions https://lists.launchpad.net/ayatana/msg05613.html https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/124315 minimize/close/windows titles for the spread view: https://bugs.launchpad.net/ayatana-design/+bug/783498 and finally, less important: Unity should be completely theme-able, including panel, launcher and dash. I can't help it but I don't like Ambiance and anything else looks out of place (if it doesn't outright break something, just an example: https://bugs.launchpad.net/unity/+bug/776697) All of this is already in LP so how do we proceed with the stuff that isn't? For this reason your last point (A unified Ubuntu design and development platform) should actually be the first ;) ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] 11.04 Comboboxes
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jonathan Meek wrote on 06/05/11 19:18: On Tue, Apr 26, 2011 at 5:58 AM, Matthew Paul Thomas m...@canonical.com ... The Check for updates menu is a combo box, and should not be. Someone has just reported this bug. http://launchpad.net/bugs/750507 Or not, it seems that is the wrong bug? Sorry, my mistake. http://launchpad.net/bugs/770507 - -- mpt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk3fpmEACgkQ6PUxNfU6ecrJyQCbBhHfhGI6mPYxHERu1gRtvJjY pxEAoLiVKTRgdYiiDlZF1cPaJPvg7FPA =Yvhv -END PGP SIGNATURE- ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
[Ayatana] Two key issues to fix in Unity
Sorry about the pun, but there are a few keyboard issues that I think requires some attention. 1. If you press super+w (what is that view called?) and then press alt+f2, then you can work with the window without bringing it into the foreground. For instance, I pressed alt+f2, typed a few words and pressed enter. Those words were sent to an IRC channel because Xchat had focus. What on earth is the purpose of that? 2. When you press and hold super, then the launcher appears almost immediately. If you hold it another second, then the icons get numbers on them to show what number key to press in order to launch an application or switch to it. My question is: why is there a waiting period before those numbers are displayed? The one second without those numbers doesn't seem to serve any purpose? There is a reason why I think this is important but I'll save that for another post. 3. Is there an easy way to find all keyboard combinations in the different modes of Unity? I mean normal desktop, lenses and super+w? Thanks. Jo-Erlend Schinstad ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
Re: [Ayatana] Two key issues to fix in Unity
On Sat, May 28, 2011 at 3:48 AM, Jo-Erlend Schinstad joerlend.schins...@gmail.com wrote: Sorry about the pun, but there are a few keyboard issues that I think requires some attention. 1. If you press super+w (what is that view called?) and then press alt+f2, then you can work with the window without bringing it into the foreground. For instance, I pressed alt+f2, typed a few words and pressed enter. Those words were sent to an IRC channel because Xchat had focus. What on earth is the purpose of that? Sounds like a bug where the application launching lens can receive focus while the workspace switcher is open. File a bug on launchpad with instructions to reproduce. 2. When you press and hold super, then the launcher appears almost immediately. If you hold it another second, then the icons get numbers on them to show what number key to press in order to launch an application or switch to it. My question is: why is there a waiting period before those numbers are displayed? The one second without those numbers doesn't seem to serve any purpose? There is a reason why I think this is important but I'll save that for another post. If you press super + num, it launches the application or brings its windows to focus for the number that appears over that launcher icon. 3. Is there an easy way to find all keyboard combinations in the different modes of Unity? I mean normal desktop, lenses and super+w? Not at the moment. The designers are trying to figure out keyboard shortcuts that are intuitive for everyone so we don't have to ship big manuals with what all the shortcuts do for everyone. If you can think of better ones, please suggest them by all means :) Thanks. Jo-Erlend Schinstad ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp -- Sam Spilsbury ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
[Ayatana-commits] [Merge] lp:~rodrigo-moya/evolution-indicator/port-to-3-0 into lp:evolution-indicator
Rodrigo Moya has proposed merging
lp:~rodrigo-moya/evolution-indicator/port-to-3-0 into lp:evolution-indicator.
Requested reviews:
Indicator Applet Developers (indicator-applet-developers)
For more details, see:
https://code.launchpad.net/~rodrigo-moya/evolution-indicator/port-to-3-0/+merge/62653
Make it build with evolution 3.0 stack
--
https://code.launchpad.net/~rodrigo-moya/evolution-indicator/port-to-3-0/+merge/62653
Your team ayatana-commits is subscribed to branch lp:evolution-indicator.
=== modified file 'configure.ac'
--- configure.ac 2011-02-25 18:17:25 +
+++ configure.ac 2011-05-27 11:02:30 +
@@ -11,6 +11,8 @@
AC_STDC_HEADERS
AC_PROG_LIBTOOL
+PKG_PROG_PKG_CONFIG
+
AC_ARG_ENABLE([deprecations],
[AS_HELP_STRING([--enable-deprecations],
[allow deprecated API usage @:@default=yes@:@])],
@@ -25,11 +27,20 @@
with_localinstall=no
+PKG_CHECK_EXISTS(evolution-plugin-3.0,
+ EVOLUTION_PLUGIN=evolution-plugin-3.0
+ GTKHTML_EDITOR=gtkhtml-editor-4.0,
+ PKG_CHECK_EXISTS(evolution-plugin,
+ EVOLUTION_PLUGIN=evolution-plugin
+ GTKHTML_EDITOR=gtkhtml-editor-3.14,
+ AC_MSG_ERROR(You need evolution-plugin to compile evolution-couchdb))
+ )
+
AC_ARG_ENABLE(localinstall, AS_HELP_STRING([--enable-localinstall], [install in the local build directory instead of the system one (for distcheck)]), with_localinstall=$enableval, with_localinstall=no)
if test x$with_localinstall = xyes; then
EVO_PLUGIN_DIR=${libdir}/evolution/2.26/plugins
else
- EVO_PLUGIN_DIR=`pkg-config --variable=plugindir evolution-plugin`
+ EVO_PLUGIN_DIR=`pkg-config --variable=plugindir $EVOLUTION_PLUGIN `
fi
AC_SUBST(EVO_PLUGIN_DIR)
@@ -60,18 +71,18 @@
PKG_CHECK_MODULES(DEPS,
indicate-0.5 = 0.4.91
- evolution-plugin
+ $EVOLUTION_PLUGIN
dbus-1
dbus-glib-1
libnotify
libcanberra
- gtkhtml-editor-3.14
+ $GTKHTML_EDITOR
unity
)
AC_SUBST(DEPS_CFLAGS)
AC_SUBST(DEPS_LIBS)
-EVO_I18N_DOMAIN=`pkg-config --modversion evolution-plugin | sed -e 's/\(.*\)\..\+$/\1/'`
+EVO_I18N_DOMAIN=`pkg-config --modversion $EVOLUTION_PLUGIN | sed -e 's/\(.*\)\..\+$/\1/'`
AC_DEFINE_UNQUOTED(EVO_I18N_DOMAIN,
evolution-$EVO_I18N_DOMAIN,
[Define to the translation domain for Evolution])
=== modified file 'src/evolution-indicator.c'
--- src/evolution-indicator.c 2011-02-25 18:17:25 +
+++ src/evolution-indicator.c 2011-05-27 11:02:30 +
@@ -155,7 +155,11 @@
}
xwindow = None;
- res = _wnck_get_window (GDK_WINDOW_XWINDOW (root),
+#if GTK_CHECK_VERSION(2, 91, 0)
+ res = _wnck_get_window (GDK_WINDOW_XID (root),
+#else
+ res = _wnck_get_window (GDK_WINDOW_XWINDOW (root),
+#endif
gdk_x11_get_xatom_by_name (_NET_ACTIVE_WINDOW),
xwindow);
if (res)
@@ -291,7 +295,7 @@
if (notification == NULL)
{
- notification = notify_notification_new ( , , mail-unread, NULL);
+ notification = notify_notification_new ( , , mail-unread);
}
trans = g_dngettext (PACKAGE,
@@ -917,10 +921,17 @@
label2 = gtk_label_new ( );
+#if GTK_CHECK_VERSION(2, 91, 0)
+combo = gtk_combo_box_text_new ();
+gtk_combo_box_text_append_text (GTK_COMBO_BOX_TEXT (combo),
+n_accounts 1 ? _(any Inbox) : _(Inbox));
+gtk_combo_box_text_append_text (GTK_COMBO_BOX_TEXT (combo), _(any Folder));
+#else
combo = gtk_combo_box_new_text ();
gtk_combo_box_append_text (GTK_COMBO_BOX (combo),
n_accounts 1 ? _(any Inbox) : _(Inbox));
gtk_combo_box_append_text (GTK_COMBO_BOX (combo), _(any Folder));
+#endif
gtk_combo_box_set_active (GTK_COMBO_BOX (combo),
only_inbox ? 0 : 1);
g_signal_connect (combo, changed, G_CALLBACK (on_combo_changed), NULL);
___
Mailing list: https://launchpad.net/~ayatana-commits
Post to : ayatana-commits@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ayatana-commits
More help : https://help.launchpad.net/ListHelp
Re: [Ayatana-commits] [Merge] lp:~rodrigo-moya/evolution-indicator/port-to-3-0 into lp:evolution-indicator
Review: Needs Information The changes seems good, but evolution is now using libgtkhtml-editor-4.0.pc and not 3.14 anymore. Can you make the change so that we can drop 3.14 from the CD? -- https://code.launchpad.net/~rodrigo-moya/evolution-indicator/port-to-3-0/+merge/62653 Your team ayatana-commits is subscribed to branch lp:evolution-indicator. ___ Mailing list: https://launchpad.net/~ayatana-commits Post to : ayatana-commits@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana-commits More help : https://help.launchpad.net/ListHelp
Re: [Ayatana-commits] [Merge] lp:~rodrigo-moya/evolution-indicator/port-to-3-0 into lp:evolution-indicator
just to be a little bit more clear, 22 +GTKHTML_EDITOR=gtkhtml-editor-3.14, is in PKG_CHECK_EXISTS(evolution-plugin, which seems to be the 2.0 version, but this PKG_CHECK_EXISTS is itself in 17 +PKG_CHECK_EXISTS(evolution-plugin-3.0, hence the fact I'm puzzled :) -- https://code.launchpad.net/~rodrigo-moya/evolution-indicator/port-to-3-0/+merge/62653 Your team ayatana-commits is subscribed to branch lp:evolution-indicator. ___ Mailing list: https://launchpad.net/~ayatana-commits Post to : ayatana-commits@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana-commits More help : https://help.launchpad.net/ListHelp
Re: [Ayatana-commits] [Merge] lp:~rodrigo-moya/evolution-indicator/port-to-3-0 into lp:evolution-indicator
Review: Approve after discussion on IRC, approved then :) -- https://code.launchpad.net/~rodrigo-moya/evolution-indicator/port-to-3-0/+merge/62653 Your team ayatana-commits is subscribed to branch lp:evolution-indicator. ___ Mailing list: https://launchpad.net/~ayatana-commits Post to : ayatana-commits@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana-commits More help : https://help.launchpad.net/ListHelp
[Ayatana-commits] [Branch ~indicator-applet-developers/evolution-indicator/trunk] Rev 79: [0.2.16] New release
revno: 79 tags: 0.2.16 committer: Didier Roche didier.ro...@canonical.com branch nick: evolution-indicator timestamp: Fri 2011-05-27 14:37:31 +0200 message: [0.2.16] New release modified: configure.ac -- lp:evolution-indicator https://code.launchpad.net/~indicator-applet-developers/evolution-indicator/trunk Your team ayatana-commits is subscribed to branch lp:evolution-indicator. To unsubscribe from this branch go to https://code.launchpad.net/~indicator-applet-developers/evolution-indicator/trunk/+edit-subscription === modified file 'configure.ac' --- configure.ac 2011-05-27 12:28:21 + +++ configure.ac 2011-05-27 12:37:31 + @@ -1,5 +1,5 @@ AC_PREREQ(2.53) -AC_INIT(evolution-indicator, 0.2.14, []) +AC_INIT(evolution-indicator, 0.2.16, []) AM_INIT_AUTOMAKE() m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])]) AC_CONFIG_SRCDIR(src/evolution-indicator.c) ___ Mailing list: https://launchpad.net/~ayatana-commits Post to : ayatana-commits@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana-commits More help : https://help.launchpad.net/ListHelp
[Ayatana-commits] [Branch ~indicator-applet-developers/evolution-indicator/trunk] Rev 78: Merge from Rodigo: Make it build with evolution 3.0 stack
Merge authors:
Rodrigo Moya (rodrigo-moya)
Related merge proposals:
https://code.launchpad.net/~rodrigo-moya/evolution-indicator/port-to-3-0/+merge/62653
proposed by: Rodrigo Moya (rodrigo-moya)
review: Approve - Didier Roche (didrocks)
revno: 78 [merge]
committer: Didier Roche didier.ro...@canonical.com
branch nick: evolution-indicator
timestamp: Fri 2011-05-27 14:36:53 +0200
message:
Merge from Rodigo: Make it build with evolution 3.0 stack
modified:
configure.ac
src/evolution-indicator.c
--
lp:evolution-indicator
https://code.launchpad.net/~indicator-applet-developers/evolution-indicator/trunk
Your team ayatana-commits is subscribed to branch lp:evolution-indicator.
To unsubscribe from this branch go to
https://code.launchpad.net/~indicator-applet-developers/evolution-indicator/trunk/+edit-subscription
=== modified file 'configure.ac'
--- configure.ac 2011-02-25 18:17:25 +
+++ configure.ac 2011-05-27 12:28:21 +
@@ -11,6 +11,8 @@
AC_STDC_HEADERS
AC_PROG_LIBTOOL
+PKG_PROG_PKG_CONFIG
+
AC_ARG_ENABLE([deprecations],
[AS_HELP_STRING([--enable-deprecations],
[allow deprecated API usage @:@default=yes@:@])],
@@ -25,11 +27,20 @@
with_localinstall=no
+PKG_CHECK_EXISTS(evolution-plugin-3.0,
+ EVOLUTION_PLUGIN=evolution-plugin-3.0
+ GTKHTML_EDITOR=gtkhtml-editor-4.0,
+ PKG_CHECK_EXISTS(evolution-plugin,
+ EVOLUTION_PLUGIN=evolution-plugin
+ GTKHTML_EDITOR=gtkhtml-editor-3.14,
+ AC_MSG_ERROR(You need evolution-plugin to compile evolution-indicator))
+ )
+
AC_ARG_ENABLE(localinstall, AS_HELP_STRING([--enable-localinstall], [install in the local build directory instead of the system one (for distcheck)]), with_localinstall=$enableval, with_localinstall=no)
if test x$with_localinstall = xyes; then
EVO_PLUGIN_DIR=${libdir}/evolution/2.26/plugins
else
- EVO_PLUGIN_DIR=`pkg-config --variable=plugindir evolution-plugin`
+ EVO_PLUGIN_DIR=`pkg-config --variable=plugindir $EVOLUTION_PLUGIN `
fi
AC_SUBST(EVO_PLUGIN_DIR)
@@ -60,18 +71,18 @@
PKG_CHECK_MODULES(DEPS,
indicate-0.5 = 0.4.91
- evolution-plugin
+ $EVOLUTION_PLUGIN
dbus-1
dbus-glib-1
libnotify
libcanberra
- gtkhtml-editor-3.14
+ $GTKHTML_EDITOR
unity
)
AC_SUBST(DEPS_CFLAGS)
AC_SUBST(DEPS_LIBS)
-EVO_I18N_DOMAIN=`pkg-config --modversion evolution-plugin | sed -e 's/\(.*\)\..\+$/\1/'`
+EVO_I18N_DOMAIN=`pkg-config --modversion $EVOLUTION_PLUGIN | sed -e 's/\(.*\)\..\+$/\1/'`
AC_DEFINE_UNQUOTED(EVO_I18N_DOMAIN,
evolution-$EVO_I18N_DOMAIN,
[Define to the translation domain for Evolution])
=== modified file 'src/evolution-indicator.c'
--- src/evolution-indicator.c 2011-02-25 18:17:25 +
+++ src/evolution-indicator.c 2011-05-27 10:57:30 +
@@ -155,7 +155,11 @@
}
xwindow = None;
- res = _wnck_get_window (GDK_WINDOW_XWINDOW (root),
+#if GTK_CHECK_VERSION(2, 91, 0)
+ res = _wnck_get_window (GDK_WINDOW_XID (root),
+#else
+ res = _wnck_get_window (GDK_WINDOW_XWINDOW (root),
+#endif
gdk_x11_get_xatom_by_name (_NET_ACTIVE_WINDOW),
xwindow);
if (res)
@@ -291,7 +295,7 @@
if (notification == NULL)
{
- notification = notify_notification_new ( , , mail-unread, NULL);
+ notification = notify_notification_new ( , , mail-unread);
}
trans = g_dngettext (PACKAGE,
@@ -917,10 +921,17 @@
label2 = gtk_label_new ( );
+#if GTK_CHECK_VERSION(2, 91, 0)
+combo = gtk_combo_box_text_new ();
+gtk_combo_box_text_append_text (GTK_COMBO_BOX_TEXT (combo),
+n_accounts 1 ? _(any Inbox) : _(Inbox));
+gtk_combo_box_text_append_text (GTK_COMBO_BOX_TEXT (combo), _(any Folder));
+#else
combo = gtk_combo_box_new_text ();
gtk_combo_box_append_text (GTK_COMBO_BOX (combo),
n_accounts 1 ? _(any Inbox) : _(Inbox));
gtk_combo_box_append_text (GTK_COMBO_BOX (combo), _(any Folder));
+#endif
gtk_combo_box_set_active (GTK_COMBO_BOX (combo),
only_inbox ? 0 : 1);
g_signal_connect (combo, changed, G_CALLBACK (on_combo_changed), NULL);
___
Mailing list: https://launchpad.net/~ayatana-commits
Post to : ayatana-commits@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ayatana-commits
More help : https://help.launchpad.net/ListHelp
[Ayatana-commits] [Merge] lp:~rodrigo-moya/evolution-indicator/port-to-3-0 into lp:evolution-indicator
The proposal to merge lp:~rodrigo-moya/evolution-indicator/port-to-3-0 into lp:evolution-indicator has been updated. Status: Needs review = Merged For more details, see: https://code.launchpad.net/~rodrigo-moya/evolution-indicator/port-to-3-0/+merge/62653 -- https://code.launchpad.net/~rodrigo-moya/evolution-indicator/port-to-3-0/+merge/62653 Your team ayatana-commits is subscribed to branch lp:evolution-indicator. ___ Mailing list: https://launchpad.net/~ayatana-commits Post to : ayatana-commits@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana-commits More help : https://help.launchpad.net/ListHelp
