On 12/02/2011 02:26 PM, Manu Gupta wrote:
On Fri, Dec 2, 2011 at 2:05 PM, Nelson Marques<[email protected]>  wrote:
https://bugzilla.gnome.org/show_bug.cgi?id=665370

2011/12/2 Sankar P<[email protected]>:
On 12/2/2011 at 01:54 PM, in message
<cahwxqkpr9dujszv+9gnoxfcbu8svxo8igdfzkpzqbczgk25...@mail.gmail.com>, Nelson
Marques<[email protected]>  wrote:
On my work computer (Fedora 16) it's not really working, it claims I
don't have GNOME3 installed (might be a browser issue though, using
Chrome). I'll test this over today when I go home on openSUSE.


+1

Didn't work with Chrome saying that I do not run the latest GNOME 3. With FF, I 
didn't get the button that Vincent was getting. May be we should try after few 
days.

Worked for me.. Try installing gnome-shell-browser-plugin first it
should work then

Also I have a question perhaps more suited upstream. Some json files
for extensions describe the workable versions as 3.2 and some as
3.2.0, so do we have a standard defining it or is it possible to have
both versions working together I am not sure.
The reason  I ask this because of the following link
http://forums.opensuse.org/blogs/knurpht/getting-dock-extension-gnome-3-2-work-73/
and the dock extension from extensions.gnome.org shows incompatibility
with gnome3.2
and the extension site showing

Sankar

Looks nice... I hope malcolm gets the no a11y extension there... I
really hate GNOME suggesting I'm somehow disabled :/

NM

2011/12/2 Vincent Untz<[email protected]>:
Go test this, it's amazing! :-)

Vincent

----- Forwarded message from "Jasper St. Pierre"<[email protected]>
-----
Date: Thu, 1 Dec 2011 16:16:26 -0500
From: "Jasper St. Pierre"<[email protected]>
To: gnome-shell-list<[email protected]>,
        [email protected], [email protected]
Subject: extensions.gnome.org - Public Alpha Now Available

We're happy to announce that extensions.gnome.org is now in
public alpha testing at:

  https://extensions.gnome.org

If you have GNOME Shell 3.2 on your system, you should be able to
install extensions from the website via your browser. This uses the
"GNOME Shell Integration" browser plugin which is likely already
installed on your system if you have GNOME 3.2. The plugin only works
with Firefox currently - see "Known Bugs" below.

We've seeded the site with a small set of extensions, including
the extensions from gnome-shell-extensions. If you are the author
of an extension that has been uploaded, and you want to take over
uploading future releases, please contact us, and we'll get you
access.

The set of extensions on the site is still small compared to the total
number of extensions available. We expect more extensions to be
available over the next few weeks as authors upload them and they
are reviewed.

About GNOME Shell Extensions
============================

GNOME Shell extensions are small pieces of code written by third party
developers that modify the way GNOME works. (If you are familiar with
Chrome Extensions or Firefox Addons, GNOME Shell extensions are
similar to them.)

Since extensions are created outside of the normal GNOME design and
development process, they are are supported by their authors, rather
than by the GNOME community.

Extensions provide a way to prototype out new possible features for
future versions of GNOME, and for advanced users to make
customizations in ways that aren't necessarily compatible with the
overall design vision of GNOME, but are still cool and useful to
a subset of users.

Since extensions become part of the core operating system, they need
to be checked for potential security problems. Extensions uploaded
to extensions.gnome.org go through code review before they are
made available for download. More information can be found at
https://extensions.gnome.org/about/.

Known Bugs and Problems
=======================

* There are some bugs that currently cause the browser plugin to
  not work correctly in WebKit-based browsers like Epiphany
  or Chrome. We will fix these bugs in subsequent releases of
  GNOME Shell, but for now using Firefox to access
  extensions.gnome.org is advised.

* Extensions that use GSettings to store user settings cannot be
  currently installed as a user; this limitation will be fixed
  for GNOME 3.4. In the mean time, extension authors should
  avoid the use of GSettings if they want to make their extension
  available via extensions.gnome.org.

* Due to a bug in GNOME Shell 3.2.1 code, the uninstall button
  will not work for some extensions. Disabling extensions still
  works, but if you want to remove an extension entirely, you'll
  need to manually delete it from ~/.local/share/gnome-shell/extensions.

Reporting Problems
==================

If you find problems with the site, please file them in
bugzilla.gnome.org against the 'extensions.gnome.org' component
of the website product.

Problems with individual extensions should be reported using
the "Help! It didn't work!" link on the extension's page.

Thanks to everybody that made this happen!

--
   Jasper St. Pierre
_______________________________________________
desktop-devel-list mailing list
[email protected]
http://mail.gnome.org/mailman/listinfo/desktop-devel-list


----- End forwarded message -----

--
Les gens heureux ne sont pas pressés.
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]



--
Nelson Marques

/* http://www.marques.so
   [email protected] */
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]





--
Nelson Marques

/* http://www.marques.so
   [email protected] */
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]




I used the extensions using firefox and I have some observations:

* Some extensions didn't install saying they were incompatible with my system. It would be better if it informed me that my system was not updated or extra dependencies were required. It could be done by putting a more button beside the message.

* Second, why were the extensions and the extension page not compatible with epiphany? (Oh I see now "There are some bugs that currently cause the browser plugin to not work correctly in WebKit-based browsers like Epiphany or Chrome."). I hope they fix it. That way we could run the extensions as a web app! That way the web app feature could be nicely utilized. Or the extensions could be served as an application like Documents or Contacts which would be better.
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to