Re: [Ayatana] [ubuntu-art] Chocolate Color Scheme
> On Sunday 21 June 2009 15:17:46 Allan Caeg wrote: >> Perfectska04 has a famous GNOME theme suite. Probably, a lot of you are >> familiar to it and are using it. He has a set of icon themes, GDM >> themes, and gtk themes that have different color schemes. His latest >> color scheme is the "Dust" variant. This scheme's look and feel is based >> on the color of chocolate. Prior to that, he always had a "Human" >> variant, which is orange. The Dust variant feels more earthy and looks >> much more elegant. For some reason, I am much more comfortable with the >> chocolate feel. Maybe because orange really feels cheaper. It has always >> been associated with low end products and services while a dark shade of >> brown, in my opinion, reminds the user of chocolate and leather. FYI, GNOME-Colors, Shiki-Colors, and Arc-Colors are all sitting in Debian NEW right now and will be in Karmic. They were packaged by me and Benjamin Drung. You can find a PPA and Bzr branches with the packaging here: https://edge.launchpad.net/~gnome-colors-packagers - Andrew Starr-Bochicchio Ubuntu Developer ___ 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] MI idea suggestion
On Thu, Sep 10, 2009 at 7:18 PM, Jan Claeys wrote: > Op maandag 07-09-2009 om 17:24 uur [tijdzone +0300], schreef Alex > Lourie: >> 1. MI will present me the simple *content*-based view of what I've >> missed; >> not applications. For example: >> >> Email Messages >> Inbox >> Gmail >> Other Mailboxes >> Twitter Messages >> a...@twitter >> Identica Messages >> a...@identi.ca >> Jabber Messages >> a...@ubuntuisgreat.com >> ICQ Messages >> 987654321 - alourie >> News (RSS) >> NY Times >> Planet Ubuntu >> Phone >> Missed Calls >> Missed Messages >> >> 2. MI would be able to *present* me any messages I have missed without >> me having application running (I only have IDE opened during coding >> session, but I still would like to get email notifications). > > That sounds like you want to reinvent Telepathy... > > But maybe that's a good idea: why not build this indicator as a > telepathy-based application instead of reinventing stuff? That would > also solve the current issue that for most people the indicator applet > just duplicates information that's already visible elsewhere. You snipped it out, but he explicitly said that there are libraries that exist that can already pull this information. It doesn't sound like he's talking about reimplementing a backend but simply using the MI as a frontend for existing technology, be it Telepathy or something else. I certainly think there is some merit to this idea. I would have suggested something like this before, but it had seemed like it might have been out of the scope of the MI applet. Though as already mentioned in other threads, the scope now seems a bit unclear. Although this would require a configuration menu, which seems to be the one thing that has been clearly stated as unacceptable Who knows? One issue I've had with the MI applet is that in its current state it misses one of the largest messaging use cases, webmail. - Andrew ___ 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] Gallery
On Thu, Apr 1, 2010 at 3:21 PM, Martin Owens wrote: > On Thu, 2010-04-01 at 07:48 -0400, Jim Rorie wrote: >> If you are going to create a contest concept, there needs to be some >> small possibility that their creations would make it into the distro. >> Without Canonical's blessing, the best I could offer was a personal >> PPA >> that might go ignored. >> >> Not exactly an exciting prize. > > Even so, you have the trust that people will see the great results > you've produced and common sense of utilising the results will almost > guarantee it. > > I admit that's not a guarantee, but then again sound themes would be > useful to more than one distro and useful to more users if they could be > installed say through a deb. There's no reason that quality sound themes that don't get chosen for the default install couldn't be distributed in universe. We already offer the community-themes package with GTK+ and Metacity themes contributed by the community. As the person doing most of the packaging end stuff for community-themes, I'd be willing to do the same for a community-sound-themes package. - Andrew SB ___ 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] Gallery
On Thu, Apr 1, 2010 at 12:40 PM, Jim Rorie wrote: > What media licenses are compatible with an Ubuntu distro? > http://www.ubuntu.com/community/ubuntustory/licensing doesn't > specifically mention media, but then again IANAL. Most of the current icon and theme work seems to be distributed under the Creative Commons Attribution Share-Alike License v3.0 > How many unique sound cues are considered part of a theme? (IOW, are you > adding stuff?) Are these specified somewhere? The Freedesktop Sound Naming Specification can be found here: http://0pointer.de/public/sound-naming-spec.html - Andrew SB ___ 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] Reducing Resistance to Change
On Wed, Apr 28, 2010 at 2:40 AM, Mario Vukelic wrote: > The experience is that as an interested > user you are running the development version for months during the > alphas with great expectations but nothing much to see UI-wise, and > suddenly sweeping and often problematic changes land late in the cycle. > > This, I think, gives the impression that the design team is not really > interested in user discussion/feedback. It also seems to me that this > way of doing things gives very little time for users to get used to the > changes, form a considered opinion and give feedback. It also gives > developers little time to consider the feedback or identify problems in > other ways, and to implement appropriate iterations to fix them. > > To give a recent example, I was open to the question of having the > window buttons on the left, but it's only now - a few days before > release - that I feel I have used them enough to get somewhat used to > them and really decide if I like them or not. > > On the other hand it's understandable, if you stop to think about it > (often neglected on discussion boards), that the development cycle is > actually used for development, and it's impossible to include some > changes very early in the cycle for the simple fact that they are not > done yet. There would also be the danger that earlier inclusion would > just drag out the public discussions and with time let them deteriorate > into senseless trolling even more. I think that a lot of this has to do with simply working out project management kinks in what is a fairly new team. My understanding is that most of the folks on the Canonical design team don't come from a distribution development background but from upstream application development and non-Linux design backgrounds. And that's great! They have the kind of experience that is going to push Ubuntu forward. But it does raise issues with fitting their work into the our release cycle. I know that in the Karmic cycle there were some problems with the design team respecting the various freezes, but from where I sit this was much better in Lucid. Hopefully it will be even better going forward as people fit into Ubuntu's development rhythm (dare I say cadence?). The application indicator and software center (although I suppose that one fall under the rubric of the Foundations team) work seemed to land fairly early in the cycle. I think we need to continue to embrace the release early and often philosophy. Though this is much harder with artwork. But do I think that it is important to remember that Lucid saw an entire re-branding of our image, no small task and something that more or less had to be rolled out all at once. Despite that, the team still managed to get their work in on time for the UI freeze. - Andrew SB ___ 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] Unity's "desktop"
On Thu, Aug 19, 2010 at 8:29 PM, Joern Konopka wrote: > On Thu, Aug 19, 2010 at 1:27 AM, Mark Shuttleworth wrote: >> >> On 08/08/10 20:49, Apoorva Sharma wrote: >> > I like all these ideas, but why not do what KDE4 did, and present a >> > desktop of files, a zeitgeist timeline, etc. as widgets, so you could >> > have access to files and useful information? >> >> I do think a gadget story is interesting. There's no really compelling >> framework out there today, though. Google's implementations have a lot >> of rendering and usability problems, and the gadgets are not attractive. >> Yahoo's is closed source. The others are marginal. > > I was thinking more on the lines of desktop implementations, not web > implemtation, like KDE4's Plasma. > >> Am I missing a good candidate? > If I may lead attention to SeedKit for a second: > http://live.gnome.org/SeedKit > In a nutshell it's a gtkWidget holding a (optionally) transparent webkit > container, it ties strongly with the Seed JavaScript Implementation, GObject > Introspection and DBUS (all the sweet stuff everyones looking at right now). > I think by putting WebTechnology in the front row we'll have the highest > possible developer base. Just imagine something like A Ubuntu Widget Website > not unlike Android Market or the App Store ( or a tie in with the USC ) > where people can upload new Widgets which provide them with capabilities > like : > 1. Easy to learn and get into ( any other guy could write a basic Widget > within under a Day) > 2. Are easily portable to other Mobile Devices, Websites and Distributions > 3. Offers Devs of f.e. iPhone HTML5 Apps a very convenient way to bring > their Apps to a new Audience in form of a Widget. > The sweet thing about it, it's already working and would only need the > WM_CLASS treatment (meaning a window class for widgets of course). > One could even go as far as supplying the Widget with a pull and push > function (Pull= a "real" GTKWindow, push=move back to widget space) and you > could even "listen" to the window state via CSS Media Queries. > Proof of concept: > http://dl.dropbox.com/u/1890515/MiniPlayerPreview.ogv > I pulled this off in just a couple hours even though I never used Seedkit > before. Thanks for point that out! I hadn't come across that yet. It looks very promising, and I can't wait to dig into it more. What I'd really like to see is something like this in a sandboxed environment. There's been a lot of talk about making it easier for "opportunistic" developers to get apps out to Ubuntu users, and the comparison is always iPhone|Android. In some ways the discussion of the new "Post Release App" process is putting the cart before the horse. Developing a framework like this paired with something like the "Post Release App" process could be very interesting... - Andrew SB ___ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
