Open juzerali opened 10 years ago
interesting idea.
Before proceeding to write the extensions themselves we should identify the areas where same code will be repeated number of times because of different APIs exposed by browsers. For those browsers that allows writing extensions in javascript, we should write abstractions which will provide a uniform API for writing the business logic. Providing a way to persist configuration will be trivial after writing these abstractions. We can even write a generic library separate from the project. Otherwise writing code for each and every browser will be cumbersome.
If focus is on a single browser then we should proceed that way.
I am thinking of starting an independent project that will act as an adapter to browser extension (chrome) APIs, @nb333 @ZDroid, do you think this library will have a place in this extension? Moreover, will you be interested in adopting that project once it reaches beta by openfaux? Or else we can start that project as part of openfaux organization only. Let me know.
I'm ok with it, no problem to make new repository. If want, I can add it to #25.
do add it. and also create a repo.
See the api branch. Thoughts!
Browsers provide different APIs to persist user configuration settings which can sync across devices. Rather than writing methods for each and every platform we should use an abstraction which can detect the platform and use the available API.