the quick version would probably be best. as in #1
could it work as a user activated notification? i guess for replies, it
would be better to have an actual temporary window.
On Wed, Jun 9, 2010 at 11:50 PM, Conscious User wrote:
>
> > The simplest answer would be to say that the click should ta
> The simplest answer would be to say that the click should take you as
> close to the "thing you clicked on" as possible.
>
> So, for example, if the messaging app is saying "Jane Silber 14m"
> (i.e. you got a message from Jane Silber 14 minutes ago) and you click
> on it, you want to see th
On 10/06/10 01:21, Conscious User wrote:
>
>>> And, for both cases, the same question remains: what
>>> should happen when you click on the indicator? This
>>> is particularly hairy when you consider that the
>>> user can have multiple streams being shown, and
>>> there might be intersections am
On 10/06/10 04:20, Sam Spilsbury wrote:
> That is a bad idea.
> You cannot just say "we're going to use [insert technology X], but
> that does not matter since what we care about is design" without
> ignoring the many upstreams who will ultimately be incredibly upset by
> that technical change for
> On Thu, Jun 10, 2010 at 02:21, Conscious User
> wrote:
>
>
> When using the regular Gwibber window, those thread
> windows would be accessed with something like
> right click on broadcast -> "show thread this
> message belongs to" or similar, an
On Thu, 2010-06-10 at 10:28 +0800, Sam Spilsbury wrote:
> If you're talking about reparenting, then pretty much every window
> manager does this. Including metacity and mutter. Compiz sort of does
> in upcoming versions, although for a while now it has used a hack
> where decorations are drawn as a
On Thu, Jun 10, 2010 at 5:38 AM, Mark Shuttleworth wrote:
> On 09/06/10 22:31, Martin Owens wrote:
>> Desktop experience and design studies and such I'd love to see more
>> discussion here in this list.
>
> Yes, I think we should keep implementation issues away from this list.
> The CSD discussion
Once again forwarding for Martin.
On Wednesday, June 09, 2010 05:19:06 pm Martin Gräßlin wrote:
> Am Mittwoch 09 Juni 2010, 20:48:39 schrieb Cody Russell:
> > Anyway, I just wanted to comment on this statement and point out that
> > this is not a hugely difficult problem to solve with some coopera
logo for Ayatana? any thoughts on what kinda logo you had in mind?
___
Mailing list: https://launchpad.net/~ayatana
Post to : ayatana@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ayatana
More help : https://help.launchpad.net/ListHelp
On Thu, Jun 10, 2010 at 2:48 AM, Cody Russell wrote:
>> > From: Martin Gräßlin
>> > It would be unacceptable that windows cannot be closed if they
>> > hung.
>
> Hi Martin,
>
> Sorry I've been absent from this discussion, I haven't really felt I had
> much to say yet. And I generally avoid Ayata
On 9 June 2010 23:51, dani planas armangue wrote:
>
>
>>Something is strange here. Those screenshots are clearly not using
>>the default theme. I thought the default theme was what is being
>>discussed here?
>
>>Also, the difference between gedit and inkscape... isn't this an
>>application setting
Hi there, Conscious ;)
On Thu, Jun 10, 2010 at 02:21, Conscious User wrote:
>
> When using the regular Gwibber window, those thread
> windows would be accessed with something like
> right click on broadcast -> "show thread this
> message belongs to" or similar, and they would
> be the thing that
On Wed, Jun 9, 2010 at 23:38, Mark Shuttleworth wrote:
> On 09/06/10 22:31, Martin Owens wrote:
> > Desktop experience and design studies and such I'd love to see more
> > discussion here in this list.
>
yeah, pretty use cases and such are always useful, mockups, most important
IMO is that a hig
> > And, for both cases, the same question remains: what
> > should happen when you click on the indicator? This
> > is particularly hairy when you consider that the
> > user can have multiple streams being shown, and
> > there might be intersections among those streams
> > (ex: one stream for Twi
> I know perfectly well that is temporary, is precisely why now is the
> time to decide and talk.
>
> as I said before you have to think first and then do, seeing how little
> has been done in progress, I think missing discuss issues generated by
> design.
>
> this is what ayatana list is destin
>You should have made more clear from the beginning.
>You are taking a wrong approach. For something that
>is so obviously a *work in progress*, you should
>*ask* before *assuming* anything.
>Who said the current colors will be kept?
>Who said the different button sizes are not simply
>caused by
> this is not the default theme that comes in lucid, which is working to
> Maverick Merkat
>
> https://launchpad.net/~dashua/+archive/light-themes
You should have made more clear from the beginning.
You are taking a wrong approach. For something that
is so obviously a *work in progress*, you s
>Something is strange here. Those screenshots are clearly not using
>the default theme. I thought the default theme was what is being
>discussed here?
>Also, the difference between gedit and inkscape... isn't this an
>application setting?
this is not the default theme that comes in lucid, which
Le mercredi 09 juin 2010 à 23:50 +0200, dani planas armangue a écrit :
> ok, I created a small image that ilillustrates some of my arguments. it
> is true that these are bugs that must be corrected, but I think there is
> much discusion on the general theme design,
> first need think, then do.
>
On 9 June 2010 22:35, dani planas armangue wrote:
>
> my questions not like o not like to me, if a design things.
> Daniel.P
It's a bit hard to visualise =)
Please take a zoomed screenshot and add red markers of things you
don't like. Or take the svg from your computer and change it to show
app
Yeah, I agree; but I do think these are less items of the theme and
more of system wide decoration rules
On Jun 9, 2010, at 2:50 PM, dani planas armangue
wrote:
> ok, I created a small image that ilillustrates some of my arguments.
> it
> is true that these are bugs that must be corrected, but I
Where are you getting this theme? Last I checked, Maverick hasn't had any
updates to the theming and is still using the Lucid light-themes.
___
Mailing list: https://launchpad.net/~ayatana
Post to : ayatana@lists.launchpad.net
Unsubscribe : https://la
sigh, if only the world could hear your wisdom.
"think, then do."
___
Mailing list: https://launchpad.net/~ayatana
Post to : ayatana@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ayatana
More help : https://help.launchpad.net/ListHelp
ok, I created a small image that ilillustrates some of my arguments. it
is true that these are bugs that must be corrected, but I think there is
much discusion on the general theme design,
first need think, then do.
http://img227.imageshack.us/f/bugse.jpg/
;)
PD: form precedes function.
--
_
>Dani,
>You should try to be a little bit more objective. Your entire post
>goes little beyond "I don't like it", and this is not really enough
>to start a productive discussion.
>You mentioned guidelines and elements of Elementary and Equinox.
>Which are those, specifically? Why are they better,
On 09/06/10 22:31, Martin Owens wrote:
> Desktop experience and design studies and such I'd love to see more
> discussion here in this list.
Yes, I think we should keep implementation issues away from this list.
The CSD discussion, for example, has little to do with the user
experience we wish to
On 09/06/10 16:46, Sense Hofstede wrote:
> However, like you already say in your last line "there isn't an
> overall place where the engineering participation is discussed, other
> than #ayatana on freenode." That is the most important missing piece.
That's because there are perfectly good ways to
>Dani,
>You should try to be a little bit more objective. Your entire post
>goes little beyond "I don't like it", and this is not really enough
>to start a productive discussion.
>You mentioned guidelines and elements of Elementary and Equinox.
>Which are those, specifically? Why are they better,
On Wed, 2010-06-09 at 14:28 -0400, Alex Launi wrote:
> On Tue, Jun 8, 2010 at 12:38 PM, Mark Shuttleworth
> wrote:
> Would an ayatana-dev list be useful place to start sharing
> ideas on
> participation?
>
> All of these projects have launchpad pages, launchpad has mailin
I'm going to go out on a limb and disagree. For every fresh install I've
done myself and also for new users, the new theme blows them away. not that
it can't be improved, specifically with consistency (I've brought up before
the multiple different ways of indicating, such as triangles in the
messen
> > From: Martin Gräßlin
> > It would be unacceptable that windows cannot be closed if they
> > hung.
Hi Martin,
Sorry I've been absent from this discussion, I haven't really felt I had
much to say yet. And I generally avoid Ayatana list because I have the
same problem you have with it.. all t
On Tue, Jun 8, 2010 at 12:38 PM, Mark Shuttleworth wrote:
> Would an ayatana-dev list be useful place to start sharing ideas on
> participation?
>
All of these projects have launchpad pages, launchpad has mailing lists.
Rather than subscribing to an umbrella list, each project should be run as a
I have seen this movie before, and its original title was
"the issues with moving window buttons to the left".
Back when the left-sided buttons were introduced in the
Lucid cycle, I'd feel a lot more confortable if someone
had stepped in and said "we made usability studies and
are confident that
I'm not going to pretend I understand all the issues relating to CSD, but
from here they don't sound like they best way to go. I use Chromium as my
default browser and I switched to native decorations the moment I right
clicked on the taskbar and got a totally unfamiliar menu without "Always on
top
...Pardon my intrusion.
This seems similar to android and linux, they may both want different
things, but they're gonna have to come back together eventually. Would
seem easier to shift the river then build a new one. Gnome imo is
doing more right then wrong.
Please continue...
_
Le mercredi 09 juin 2010 à 17:44 +0200, dani planas armangue a écrit :
> I've recently been looking at changes in the art of ubuntu (light themes
> and new icons) and I think you are doing things wrong.
>
> topics you are only basing the color palette rather than usability:
>
> -colors to satura
On 9 June 2010 16:44, dani planas armangue wrote:
> I've recently been looking at changes in the art of ubuntu (light themes
> and new icons) and I think you are doing things wrong.
>
> topics you are only basing the color palette rather than usability:
>
> -colors to saturate(orange specialy but
Still proxying for Martin.
On Wednesday, June 09, 2010 01:02:14 pm Martin Gräßlin wrote:
> Am Mittwoch 09 Juni 2010, 06:13:17 schrieb Ted Gould:
> > Cool, that is great! But, I'm worried that we're approaching this from
> > different assumptions. My reaction there is "let's figure out how to
> >
Hi Dani
Your feedback is valuable, Otto, Ken and Andrea are the right people to
talk to.
Mark
On 09/06/10 16:44, dani planas armangue wrote:
> I've recently been looking at changes in the art of ubuntu (light themes
> and new icons) and I think you are doing things wrong.
>
> topics you are only
On 8 June 2010 18:38, Mark Shuttleworth wrote:
>
> Would an ayatana-dev list be useful place to start sharing ideas on
> participation?
>
Only if it would be an actual development list and not a discussion
list like this mailing list. If an 'ayatana-dev' mailing list would
only be used by people t
I've recently been looking at changes in the art of ubuntu (light themes
and new icons) and I think you are doing things wrong.
topics you are only basing the color palette rather than usability:
-colors to saturate(orange specialy but same the violet)
-Buttons of different sizes
-progresbars dif
On Wed, Jun 9, 2010 at 9:52 PM, Ted Gould wrote:
> On Wed, 2010-06-09 at 12:28 +0800, Sam Spilsbury wrote:
>> > On Wed, 2010-06-09 at 10:18 +0800, Sam Spilsbury wrote:
>> >> As far as I know, with martin's NETWM idea to have the decorator paint
>> >> the "behind" of the window, this basically mean
On 06/09/2010 08:52 AM, Ted Gould wrote:
> It seems like you'd still need two deeply integrated theme engines
> though. And, in the case of multiple toolkits, deeply integrated
> between them as well if this was ever going to look in anyway
> reasonable.
>
> I just don't understand why having two
"Ted Gould" wrote:
>On Wed, 2010-06-09 at 00:45 -0400, Scott Kitterman wrote:
>> >On Tue, 2010-06-08 at 18:41 +0200, Martin Gräßlin wrote:
>> >> As mentioned in my open letter: I want to help you. I am willing to spend
>> >> my
>> >> time and expertise on this issue to ensure that we don't e
Le mercredi 09 juin 2010 à 08:59 -0500, Ted Gould a écrit :
> On Wed, 2010-06-09 at 10:34 +0100, Mark Shuttleworth wrote:
> > On 09/06/10 05:20, Ted Gould wrote:
> > > I haven't looked at the full schedule for Me Menu yet, but I would
> > > imagine most of the Canonical developer time is going to
On Wed, 2010-06-09 at 10:34 +0100, Mark Shuttleworth wrote:
> On 09/06/10 05:20, Ted Gould wrote:
> > I haven't looked at the full schedule for Me Menu yet, but I would
> > imagine most of the Canonical developer time is going to be sucked up
> > into the switching of networks and character count f
On Wed, 2010-06-09 at 00:45 -0400, Scott Kitterman wrote:
> >On Tue, 2010-06-08 at 18:41 +0200, Martin Gräßlin wrote:
> >> As mentioned in my open letter: I want to help you. I am willing to spend
> >> my
> >> time and expertise on this issue to ensure that we don't end with an
> >> utterly
>
On Wed, 2010-06-09 at 12:28 +0800, Sam Spilsbury wrote:
> > On Wed, 2010-06-09 at 10:18 +0800, Sam Spilsbury wrote:
> >> As far as I know, with martin's NETWM idea to have the decorator paint
> >> the "behind" of the window, this basically means that the window can
> >> be reparented at 0x0 in the
On 09/06/10 05:20, Ted Gould wrote:
> I haven't looked at the full schedule for Me Menu yet, but I would
> imagine most of the Canonical developer time is going to be sucked up
> into the switching of networks and character count features for
> Maverick. So, unless a contribution comes from the com
49 matches
Mail list logo
