12 Commits

Author	SHA1	Message	Date
gorhill	1d1a3983e3	syncing with master	2015-01-23 15:36:32 -05:00
gorhill	673b8774be	this fixes #582	2015-01-23 11:32:49 -05:00
gorhill	4edfae4b94	code review: jshint'ed	2015-01-21 08:59:23 -05:00
gorhill	255c68baa4	this fixes #536	2015-01-20 19:39:13 -05:00
gorhill	881e8111d8	"advanced user" flag + rearranging a bit dashboard	2015-01-06 11:44:06 -05:00
gorhill	1597ce7fd9	lot of work related to dynamic filtering + new net requests logger	2015-01-06 08:01:15 -05:00
gorhill	1fe7045b92	too many changes for #433: branching so that I can commit and keep working on it	2014-12-28 10:07:43 -05:00
Raymond Hill	84c069dfaa	continued: corralling platform-specific stuff into their meta folder	2014-11-16 00:21:13 -02:00
Raymond Hill	eafc96859c	further separate platform-specific code	2014-11-15 16:15:11 -02:00
Deathamns	749b6f186d	Use a dedicated file for storing extension info ... Chrome has getManifest(), Safari doesn't have anything, Firefox has an asynchronous API... So, instead of using extension APIs, store the common informations (extension name, version, homepage url) in a file (vapi-appinfo.js), which can be included when it's needed (its data will be available at vAPI.app.____). The file's content is updated each time the extension is being built, so it shouldn't be modified manually.	2014-11-09 17:39:38 +01:00
Deathamns	0886f7e886	Add .jshintrc, and use the "use strict" directive ... .jshintrc's otion-set is a personal choice, merely a suggestion. Beside that, it includes some common globals for specific browsers, so there's no need to set the globals in every .js file. In order to force strict coding, "use strict" directive was added into every .js file.	2014-11-09 17:39:17 +01:00
Deathamns	5b79bf3536	Work on vendor API abstraction, and near complete Safari support	2014-11-09 17:39:12 +01:00