On Thu, Feb 10, 2011 at 4:39 PM, Remco remc...@gmail.com wrote:
This may not be a good idea from a compatibility point of view. Many
websites expect sans-serif to mean Arial, serif to mean Times New
Roman and monospace Courier New. They expect sentences they write to
be in that font, which has
On Thu, Feb 10, 2011 at 5:31 PM, Remco remc...@gmail.com wrote:
On Thu, Feb 10, 2011 at 22:48, Scott E. Armitage
launch...@scott.armitage.name wrote:
Sorry, but if a website wants to use a specific font, then they should
specify that font in the stylesheet. The terms sans-serif, serif
users to select alternative choices for the generic fonts.
-S
On Thu, Feb 10, 2011 at 5:52 PM, Scott E. Armitage
launch...@scott.armitage.name wrote:
On Thu, Feb 10, 2011 at 5:31 PM, Remco remc...@gmail.com wrote:
On Thu, Feb 10, 2011 at 22:48, Scott E. Armitage
launch...@scott.armitage.name
Places, IIRC, but with no facility to power them down.
On Thu, Aug 26, 2010 at 5:12 PM, David Hamm davidth...@gmail.com wrote:
Aren't plugged in but not mounted devices show in the places list? or
computer folder?
--
Scott Armitage, B.A.Sc., M.A.Sc. candidate
Space Flight Laboratory
Agreed. Users that build GPG networks without proper trust controls could
actually /decrease/ their level of security. Having said that, the current
implementation is someone complicated and poorly documented. I have but one
trusted friend on my current network, and that took the better part of an
On Fri, May 28, 2010 at 4:55 AM, Mark Shuttleworth m...@ubuntu.com wrote:
If we do it at the Unity level, then it's one-progress-per-app, and I
agree with your 5, the App should decide which progress to show, or
amalgamate them into a single one (you have n things downloading,
overall you
On Fri, May 28, 2010 at 5:11 AM, Mark Shuttleworth m...@ubuntu.com wrote:
On 27/05/10 21:51, Scott E. Armitage wrote:
Could we see some mockups with the status bar displaying outside the window
border? I have run into this situation in Chrome on OS X and Windows before
under certain
I like them in general, but I have some reservations.
1. They still seem pretty big (i.e. not very tight, as Mark put it). I
already find many of the controls on those screenshots to be quite large,
and everything starts adding up to eat up our screen space.
2. Do we need them to be
Very well-worded point, Thorsten. This expresses in clean, concise words
(and with references!) my general feelings on the subject.
Thanks,
-Scott
On Fri, May 14, 2010 at 6:57 AM, Thorsten Wilms t...@freenet.de wrote:
On Fri, 2010-05-14 at 11:37 +0200, Jan-Christoph Borchardt wrote:
That is
I think that relying on mouse cursors as notifications is a scary idea. With
the advent of new input methods (and old ones becoming more popular) such as
touch-screens, the role of the mouse cursor does not have a 100% rock-solid
future. Why put the effort into something that may not be there five
2010/5/4 Alex Launi alex.la...@gmail.com
These were certainly helpful. I think you've nailed a lot of the sound
related use cases.
I think the take home message of this is that there are two distinct types
of sound streams. I'm going to use the analogy we've been using in
notifications-
I think a better solution would be for the Search button in the upper menu
to default to searching within your current location. Isn't that already the
default behaviour? I see no value in adding a Search option to the context
menu -- the context menu should be offering quick access to file
One comment off the bat:
On Mon, Mar 15, 2010 at 12:47 PM, Akshay Gupta kital...@gmail.com wrote:
2.) A close button on the corner of the bubble as soon as a mouseover
occurs (like Growl, instead of disappearing away)
This interferes with the idea of notifications being ethereal -- as it
I couldn't agree more; the notification system introduced with NotifyOSD is,
on the whole, awesome, and I couldn't imagine going back to stupid little
balloon tips tat pop up with a distracting noise and demand to be shooed
away.
-S
On Mon, Mar 15, 2010 at 1:46 PM, Mike Rooney mroo...@ubuntu.com
I can sit here and say I don't like the changes, but it's irrelevant.
It's an opinion. What is needed are facts and a cost/benefit analysis.
I think the cost is pretty clear at this point.
Precisely.. and yet for all the people in this thread and others that have
been requesting it, the is
I don't think that mac_v is proposing /automated/ updates, so much as he is
proposing that the current update scheme should not require the
administrator's password. The administrator would still be notified of new
updates as they are now, and they would have to decide when to download and
install
.
-S
On Tue, Dec 15, 2009 at 8:53 AM, Scott Kitterman ubu...@kitterman.comwrote:
On Tue, 15 Dec 2009 07:31:37 -0500 Scott E. Armitage
launch...@scott.armitage.name wrote:
I don't think that mac_v is proposing /automated/ updates, so much as he
is
proposing that the current update scheme should
I think the description of what shutting down does (e.g. all applications
will be closed) belongs in the tooltip for the shut down command. The
dialog itself is not the place for that information -- it should show only
what you need to know, that is 1) you have an option to cancel the shut
down,
It sounds like this is putting the horse before the bit -- there is still a
lot of turmoil out there regarding NotifyOSD's positioning. The Work for
Lucid section *should* say something more like
Positioning: Determine the driving requirements for notification bubble
positioning and separate
19 matches
Mail list logo
