aata / browsersync

Automatically exported from code.google.com/p/browsersync
Other
0 stars 0 forks source link

No firefox 3 extensions sync #2

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
GBS should be able to sync extensions either by going to to the FF addon's
server and downloading them then installing. Or by saving them in google's
profile.

I think this features is way down on the need to do list. However GBS would
be half done without it. 

Original issue reported on code.google.com by bass...@gmail.com on 27 Jun 2008 at 5:29

GoogleCodeExporter commented 9 years ago
I think, downloading the extensions from the addon server would be better, 
because it
would save a lot of space on the servers of google, because there are not 
thousands
of copies of one extension stored in the profiles. And second: If they are 
downloaded
from the addon server, always the newest version will be installed.

Original comment by Benjamin...@googlemail.com on 1 Aug 2008 at 9:17

GoogleCodeExporter commented 9 years ago
I don't think it would be hard, if google saves a list of all the extentions.
whenever you sync them it goes to the Mozilla servers, grabs all the files and
prompts you to install them. It may even give you a list and you can pick and 
choose
which extensions to install. 

Original comment by bass...@gmail.com on 1 Aug 2008 at 9:32

GoogleCodeExporter commented 9 years ago
what's up with this feature is it up now.

also just a side note.... 

what if i am using a customized version of plugin.... lets say the default 
plugin is not supported on current version of browser just becasue its author 
has abandoned it so i have changed the verson no and its up and running. how 
you will handle such cases.

Original comment by ant201...@gmail.com on 6 Jul 2010 at 8:05

GoogleCodeExporter commented 9 years ago
\Reflector.zip

Original comment by zhouzhou...@gmail.com on 14 Dec 2010 at 11:16

Attachments: