Comments on: Firefox; FUEL but no FHIG! http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/ GIS, Mac, Interweb, and me! Wed, 16 May 2012 16:38:08 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Norma Manlangit http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/comment-page-1/#comment-87548 Norma Manlangit Tue, 25 Oct 2011 05:11:12 +0000 http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/#comment-87548 Good writing and seriously helps with learning the article much better. Good writing and seriously helps with learning the article much better.

]]> By: Recent Links Tagged With "opacity" - JabberTags http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/comment-page-1/#comment-18861 Recent Links Tagged With "opacity" - JabberTags Mon, 05 Jan 2009 17:42:47 +0000 http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/#comment-18861 [...] public links >> opacity Overlying DIV Saved by samc61694 on Thu 25-12-2008 Firefox; FUEL but no FHIG! Saved by lesterminator on Mon 22-12-2008 Create a Stylized Vector Police Badge with Metal and [...] [...] public links >> opacity Overlying DIV Saved by samc61694 on Thu 25-12-2008 Firefox; FUEL but no FHIG! Saved by lesterminator on Mon 22-12-2008 Create a Stylized Vector Police Badge with Metal and [...]

]]> By: Blair McBride http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/comment-page-1/#comment-16708 Blair McBride Sat, 30 Aug 2008 02:35:18 +0000 http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/#comment-16708 Also, be aware that the final Ubiquity UI is likely to look completely different. We're mostly focusing on the technology and concepts at this stage, so the UI hasn't gotten much attention yet. Also, be aware that the final Ubiquity UI is likely to look completely different. We’re mostly focusing on the technology and concepts at this stage, so the UI hasn’t gotten much attention yet.

]]> By: Yatrik http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/comment-page-1/#comment-16707 Yatrik Sat, 30 Aug 2008 02:35:09 +0000 http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/#comment-16707 "To me the devil is in the detail: different shades of grey, different opacity, different border radii, and in the case of Ubiquity no border radius at all." I agree completely; the standardization of properties throughout the browser would be very helpful. “To me the devil is in the detail: different shades of grey, different opacity, different border radii, and in the case of Ubiquity no border radius at all.”

I agree completely; the standardization of properties throughout the browser would be very helpful.

]]> By: Alex Faaborg http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/comment-page-1/#comment-16625 Alex Faaborg Tue, 26 Aug 2008 09:48:16 +0000 http://spatialviews.com/2008/08/25/firefox-fuel-but-no-fhig/#comment-16625 One of the best things about Firefox extensions is the wide range of creativity and innovation we see in how people develop various interactions and appearances. This means that sometimes extensions are designed better than traditional human interface guidelines, and sometimes they are a lot worse :) Despite the name Human Interface _Guidelines_ people often interrupt HIGs as rules that must be followed. I'm a little reluctant to release a HIG for people developing on top of Firefox since I am scared it might limit people's creativity. However, I think if we framed the document as "some interactions that we have found tend to work pretty well," that might help us raise the bar without forcing everyone to the same level of mediocrity. In terms of visual appearance, since control-tab and Ubiquity are still both experimental interfaces, I'm not as concerned that they don't currently perfectly match the OS. However, if they end up landing in Firefox we will want to make sure they visually integrate as closely as possible (Boriss has some nice OS X control tab mockups here: http://people.mozilla.com/~jboriss/blog/with_quick_large.png ) We also need to make sure that it is as easy as possible for people building interfaces on top of Firefox to leverage these visual styles, if they want to. In the case of command-tab (and possibly other keyboard based UI's in the future like ubiquity), we are using the "KUI-panel" class. One of the best things about Firefox extensions is the wide range of creativity and innovation we see in how people develop various interactions and appearances. This means that sometimes extensions are designed better than traditional human interface guidelines, and sometimes they are a lot worse :) Despite the name Human Interface _Guidelines_ people often interrupt HIGs as rules that must be followed. I’m a little reluctant to release a HIG for people developing on top of Firefox since I am scared it might limit people’s creativity. However, I think if we framed the document as “some interactions that we have found tend to work pretty well,” that might help us raise the bar without forcing everyone to the same level of mediocrity.

In terms of visual appearance, since control-tab and Ubiquity are still both experimental interfaces, I’m not as concerned that they don’t currently perfectly match the OS. However, if they end up landing in Firefox we will want to make sure they visually integrate as closely as possible (Boriss has some nice OS X control tab mockups here: http://people.mozilla.com/~jboriss/blog/with_quick_large.png )

We also need to make sure that it is as easy as possible for people building interfaces on top of Firefox to leverage these visual styles, if they want to. In the case of command-tab (and possibly other keyboard based UI’s in the future like ubiquity), we are using the “KUI-panel” class.

]]>