All Mangas Reader

Chrome now has a storage mechanism that it auto-syncs between browsers and is more robust than Bookmark sync. It would be something nice to look into later to make syncing less error prone as Bookmark Syncing still has many issues plaguing it.

http://developer.chrome.com/dev/extensions/storage.html For more information.

I might have some time to maybe implement this for you guys and just give you the code to test/incorporate into live releases. This functionality was added in Chrome 20, so if you want to be backwards compatible, anything less than version 20 can fallback to bookmark sync.

Another alternative is to sync to a website or a google app engine app. That way it can still be reliable and backwards compatible.

[Edit] This can also allow syncing of settings and configurations making it easier to setup a new browser install or machine.

Hi, I talked with polo about this some time ago (I think when it was first introduced) and he said it was great, we still haven't talk about this since then but it's in the TODO list. If you can develop this we could be more than glad to use it. BTW, we also talked about changing the way we store the manga list, instead using a single key-value pair for all the mangas (we use mangas:{json} to store the actual list giving us lots of bugs because is made synchronously) so we were thinking about opening a new db table and store the values there. Please take this into consideration so we can make the changes to your code to meet this goal.

_________________
Know about me

Well, I tried to take a stab at it for a few hours. It turns out that there are some pretty hard requirements for storage, and that primarily is Manifest Version 2. Which brings a lot of changes, and security restrictions.

In reality a good portion of AMR has to be modified, moved around and refactored for it to work. Primarily, no more Inline JS on HTML pages. After moving all of them out, even with $(document).ready(), I couldn't get most of the pages to work anymore. So i got stuck.

I got a little bit of the Storage Sync implemented, but I have no way of testing it at the moment.

Here is the info related to what the changes, and security restrictions are:

http://developer.chrome.com/extensions/ ... rsion.html

This might have to be a AMR 1.5 or 2.0 change. Manifest Version 2 also has a hard requirement of Chrome 18 or higher, or even more than that. Storage requires Chrome 20 or higher. So whichever release comes out with this functionality will need a Chrome 20 minimum version, if not higher.

I will look into what more I can do, but being unfamiliar with Chrome extension development, and also unfamiliar with most of the AMR code-base, I can only do so much.

The upside, is the new ManifestVersion allows for a pure JS background.js, instead of having to put it all in an HTML file. But that requires some more refactoring.

Stable is on Chrome 23, Beta is on 25, and Dev is on 26. (I run dev, but for some reason I am stuck on 24, need to fix that.)

In the TODO list was already all of that, I asked Polo for some documentation to get amr work as well as is doing now, also I tried to move all the inline js to another file but got stuck as well... we might need some weeks to put this on motion everyone working on it.

_________________
Know about me