Quoting Bryen M Yunashko <[email protected]>:

On Tue, 2012-05-22 at 10:02 +0100, Andrew Wafaa wrote:

I read somewhere, although I seem to be missing this email now, that
someone proposed making e.g.o a bookmark when we ship Firefox.  If
that's a legitimate proposal, I'm against this as the answer to
extensions.  Why would a user think to configure his/her desktop by
going to a browser instead of some settings area?

https://bugzilla.novell.com/show_bug.cgi?id=742166

I'd rather see something in our menu, such as "Desktop Extensions" or
"Extend your Desktop."   Something like that.  Although I can see a few
problems with this idea as well, such as your default chosen browser may
not support the e.g.o plugin, thus clicking on the menu item bringing up
your browser may not be effective.  Or, if your browser is already open
but buried under other windows, a user might keep clicking and clicking
on the menu item wondering why nothing's happening.  :-)

The 'settings' entry might be an option by providing a 'web application' (which is possible with epiphany!) which would do that...

Another drawback is how to keep your extensions updated when people are
less likely to revisit e.g.o to check on the status of their installed
extensions?  I haven't visited e.g.o in months.

That is indeed an issue... Package management facilitates that a lot.

On a side note, and this is not meant to disparage Cinnamon, I find the
way Cinnamon ships extensions problematic for standard GNOME.  I tried
Cinnamon once a few months ago for only like 5 minutes (just to see) and
when I quickly went back to GNOME, ugh, all those new extensions were
enabled and I had to try to weed through and figure out which ones were
extensions *I* enabled versus ones that Cinnamon forced on me.

That's an interesting observation indeed. Cinnamon should make sure to use an own 'configuration style for which extensions it needs / enables. Seems 'too much code is shared' in this case.

Dominique
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to