Commit Graph

270 Commits

Author SHA1 Message Date
Deathamns c0e11d8182 Safari: fix vAPI.tabs.close() + cleanup 2014-12-01 20:47:23 +01:00
Raymond Hill 2e4c0a2bfe remove depending on vapi-appinfo.js 2014-12-01 14:25:33 -02:00
Raymond Hill 7980996423 fr, de now also on Crowdin 2014-12-01 12:27:08 -02:00
Raymond Hill 6294dea81d "platform" is more accurate 2014-11-29 17:51:19 -02:00
Raymond Hill fb66fd4f36 translation work from Crowdin 2014-11-26 17:34:48 -02:00
Raymond Hill a430e526b6 use "platform" as suggested in #360 2014-11-24 14:49:11 -02:00
Raymond Hill 2ae09084e0 more accurately, it is for chromium 2014-11-24 13:01:39 -02:00
Raymond Hill 369b038f92 jshint 2014-11-24 12:48:33 -02:00
Deathamns 219eddab74 Ports cleanup
- Remove duplicate platform specific (from src/) and other unnecessary
  files
- Fix and update vapi-*.js files for Safari
- Add tools/make-safari.sh
- Move js/vapi-appinfo.js to meta/ (so, every vendor specific file will be
  at the same location)
2014-11-23 18:21:06 +01:00
Raymond Hill 36befae83c cleanup before rebuilding 2014-11-18 13:35:57 -02:00
Raymond Hill 370ff5aee8 updated according to new project layout 2014-11-16 14:41:20 -02:00
Raymond Hill 2b957dc389 respect project layout as set by @Deathamns 2014-11-16 08:47:47 -02:00
Raymond Hill 84c069dfaa continued: corralling platform-specific stuff into their meta folder 2014-11-16 00:21:13 -02:00
Deathamns 41ae0c08c7 Building missed a file for Safari 2014-11-10 12:04:03 +01:00
Deathamns 0d9d285608 Building extension files
Adds possibility to build extension files (Chrome and Safari) from
command line.

To run from the project directory:
python tools/build.py [meta]

If the optional `meta` argument is set, then only the manifest and
language files are uptated.
Without that everything is being built (extension files too) into the
`dist/build/version_number` folder.

For Chrome there will be two files, a crx, and a .zip file which
includes the key.pem private key (so this must not be shared,
it's just a bit help for publishing it to the Chrome Web Store).

Beside the extension files, update-files are generated too (for self
hosting - Safari needs it).
2014-11-09 18:58:46 +01:00
Deathamns 30ef97a678 Fix messaging for Safari 2014-11-09 17:41:07 +01:00
Deathamns 6f2e449e61 Preferences button for Safari
Brings back the possibility to click a checkbox which opens the extension
settings from Safari's Preferences/Extensions.
2014-11-09 17:41:05 +01:00
Deathamns 54749b31fb Building Info.plist was missing 2014-11-09 17:40:46 +01: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 5b79bf3536 Work on vendor API abstraction, and near complete Safari support 2014-11-09 17:39:12 +01:00