Wait I don't need to store preferences in bookmarks anymore?! How did I miss this? :)
Aaron Boodman wrote: > Yes, and it is enabled by default if --enable-extensions are present. > > (Some details like events are not finished yet, but the basics are there). > > - a > > On Tue, Aug 18, 2009 at 11:44 AM, Jack David > Baucum<[email protected]> wrote: > >> Has localStorage been implemented in Chrome yet? >> >> On Tue, Aug 18, 2009 at 1:59 PM, Antony Sargent <[email protected]> >> wrote: >> >>> I think what Aaron was suggesting is that an option for you is to build >>> the list into your extension. That way you can release updates to the list >>> by just using auto-updates of your extension. This is different from the >>> model of subscribing to a third party list, but might work depending on what >>> you want to achieve. >>> To make it possible to subscribe to third party lists, you'd need to do >>> something like the following: >>> -implement some kind of preferences UI for entering the url or third party >>> lists >>> -write code in a background page to periodically download, parse, and >>> store the lists (using localStorage, most likely) >>> >>> >>> On Tue, Aug 18, 2009 at 8:49 AM, Maxo <[email protected]> wrote: >>> >>>> I am trying to write an adblock extension. The way it works in >>>> Firefox is that a user subscribes to a third party list. That list >>>> gets downloaded semi-regularly. >>>> Will this setup not work with the proposed API for Chrome? >>>> If not what is the best way to proceed to provide the user with the >>>> ability to generically call third party subscriptions? >>>> >>>> On Aug 11, 1:23 am, Aaron Boodman <[email protected]> wrote: >>>> >>>>> There is no need to do this manually. Chrome has its own extension >>>>> update system built-in. You can learn more about it here: >>>>> >>>>> >>>>> http://dev.chromium.org/developers/design-documents/extensions/autoup... >>>>> >>>>> You should avoid doing your own automatic updates as it is difficult >>>>> to do them in a secureway. Instead, use the built in updater if you >>>>> can. >>>>> >>>>> - a >>>>> >>>>> >>>>> >>>>> On Mon, Aug 10, 2009 at 8:04 PM, Maxo<[email protected]> wrote: >>>>> >>>>> >>>>>> This is my first attempt at writing an extension, and I am only just >>>>>> passed being a beginner at Javascript, so forgive me for the newb >>>>>> question. I want my extension to check for anupdatedconfiguration >>>>>> file that resides on the web each time Chrome starts up. I tried >>>>>> using XMLHttpRequest, but that fails because of Cross Site Scripting >>>>>> security. >>>>>> I am also using a content_script, which is not optimal because it >>>>>> fires off each time a new tab is opened, which could cause >>>>>> performance >>>>>> issues and is overkill. I just want togetthe new file each time the >>>>>> browser is loaded. What is thebestwayto tackle this? >>>>>> >>> >>> >> >> -- >> Jack David Baucum >> http://maxolasersquad.com >> http://www.myspace.com/mlsquad >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
