This decision is really bothering me. Despite your claims otherwise
Browser Actions are a decidedly _not_ elegant solution.

Consider the case that I want to build an extension that checks the
current page for a variety of different web analytics script tags
(Google analytics, Omniture, Website Optimizer, others), parse them
for useful info (acct number, check implementation errors, etc), and
if found display an icon with an optional text snippet for each.

Now, imagine GA code and Omniture codes both exist on a given page.
Let's take it from a user's perspective. In the ideal scenario two
icons would be displayed side by side alerting the user with a simple
glance that both are found. This is a zero click operation. If I want
to add a unique onClick to each icon, let's say to pull up that user's
account for each tool, it would be a 1 click operation.

There is no way to get the same user experience with the current
implementation. To accomplish the same with BrowerActions at best I
would have to have many many permutations of icons and a minimum two
click experience - one to find out both codes existed and another to
jump to the account.

This seems like a rather Apple-like move. *You are sacrificing utility
for the sake of asthetics!* The user has made a conscious decision to
download and install this plug-in. It's not as if I'm doing some
driveby irreversable plug/in installation that will rapidly consume
precious screen realestate. If they don't like my design decisions
they can uninstall it. By limiting my development options this way you
are also limiting user choice. Consider the Google Android analogy.
Isn't one of the Android selling points to developers it is more
flexible than the iPhone? (The recent Droid commercials mockingly say
so). And by extension more flexibility means more developers means a
healthier plugin ecosystem means more users?

Please please consider my use case above.

Gabe

On Oct 13, 3:07 pm, Harutyun Amirjanyan <[email protected]> wrote:
> > We actually do have an option to hide the toolstrip in the current
> > implementation (ctrl+alt+b).
>
> it's really hard to access
>
> > people who do want their extensions visible, but don't want to lose
> > the entire strip of vertical real-estate.
>
> but there are extensions which don't need to be always at top, so
> it would be better to have smaller toolstrip on the right side of
> screen
> similar to statusbar on the left, which will appear on mouseover
> and users will be able to move extension buttons between main toolbar
> and this small one

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Chromium-extensions" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/chromium-extensions?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to