uBlock/src/about.html

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<title>µBlock — About</title>
<link rel="stylesheet" type="text/css" href="css/common.css">
<link rel="stylesheet" type="text/css" href="css/dashboard-common.css">
<link rel="stylesheet" type="text/css" href="css/about.css">
</head>

<body>

<h2 id="aboutNameVer"></h2>
<ul>
    <li><a href="https://github.com/gorhill/uBlock/releases" data-i18n="aboutChangelog"></a>
    <li><a href="https://github.com/gorhill/uBlock" data-i18n="aboutCode"></a>
    <li><span data-i18n="aboutContributors"></span>
        <ul>
            <li><a href="https://github.com/gorhill/uBlock/graphs/contributors">Github</a>
            <li><a href="https://crowdin.net/project/ublock">Crowdin</a>
        </ul>
</ul>

<div style="margin:3em 0;border-top:1px solid #ccc;"></div>

<div style="margin:1em 0 0 0;">
<p><button type="button" id="export" data-i18n="aboutBackupDataButton"></button>
  <button type="button" id="import" data-i18n="aboutRestoreDataButton"></button>
  <input id="restoreFilePicker" type="file" accept="text/plain" style="display:none;">
<p>
<p><button type="button" id="reset" data-i18n="aboutResetDataButton"></button>
</div>

<script src="js/js-loader.js" data-jsList="
js/vapi-common.js
js/vapi-client.js
js/vapi-appinfo.js
js/udom.js
js/i18n.js
js/dashboard-common.js
js/about.js
"></script>

</body>
</html>
first commit 2014-06-24 00:42:43 +02:00			`<!DOCTYPE html>`
			`<html>`
			`<head>`
Avoid using Chrome's @@bidi_* type i18n messages ... for the sake of portability. When including vapi-common.js in an HTML file, then the body element there will have a "dir" attribute filled with the current locale's direction (ltr or rtl). The following languages are considered right-to-left: ar, he, fa, ps, ur. Everything else is left-to-right. After the "dir" attribute is set, we can decide in CSS which elements should have different styling for rtl languages (e.g., body[dir=rtl] #id). 2014-10-21 16:45:54 +02:00			`<meta charset="utf-8">`
first commit 2014-06-24 00:42:43 +02:00			`<title>µBlock — About</title>`
			`<link rel="stylesheet" type="text/css" href="css/common.css">`
			`<link rel="stylesheet" type="text/css" href="css/dashboard-common.css">`
this fixes #137 and #272 2014-10-07 14:59:35 +02:00			`<link rel="stylesheet" type="text/css" href="css/about.css">`
first commit 2014-06-24 00:42:43 +02:00			`</head>`

			`<body>`

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-10-20 22:10:59 +02:00			`<h2 id="aboutNameVer"></h2>`
this fixes #137 and #272 2014-10-07 14:59:35 +02:00			`<ul>`
code review (lot more needed), jshint 2014-08-20 05:01:36 +02:00			`<li><a href="https://github.com/gorhill/uBlock/releases" data-i18n="aboutChangelog"></a>`
Work on vendor API abstraction, and near complete Safari support 2014-10-17 21:44:19 +02:00			`<li><a href="https://github.com/gorhill/uBlock" data-i18n="aboutCode"></a>`
code review (lot more needed), jshint 2014-08-20 05:01:36 +02:00			`<li><span data-i18n="aboutContributors"></span>`
			`<ul>`
			`<li><a href="https://github.com/gorhill/uBlock/graphs/contributors">Github</a>`
			`<li><a href="https://crowdin.net/project/ublock">Crowdin</a>`
			`</ul>`
this fixes #138, next: thorough code review 2014-08-20 02:41:52 +02:00			`</ul>`
first commit 2014-06-24 00:42:43 +02:00
this fixes #137 and #272 2014-10-07 14:59:35 +02:00			`<div style="margin:3em 0;border-top:1px solid #ccc;"></div>`

			`<div style="margin:1em 0 0 0;">`
			`<p><button type="button" id="export" data-i18n="aboutBackupDataButton"></button>`
ensure no lost "change" events (#307) 2014-10-12 20:55:20 +02:00			`<button type="button" id="import" data-i18n="aboutRestoreDataButton"></button>`
			`<input id="restoreFilePicker" type="file" accept="text/plain" style="display:none;">`
this fixes #137 and #272 2014-10-07 14:59:35 +02:00			`<p>`
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-10-20 22:10:59 +02:00			`<p><button type="button" id="reset" data-i18n="aboutResetDataButton"></button>`
this fixes #137 and #272 2014-10-07 14:59:35 +02:00			`</div>`

Work on vendor API abstraction, and near complete Safari support 2014-10-17 21:44:19 +02:00			`<script src="js/js-loader.js" data-jsList="`
			`js/vapi-common.js`
			`js/vapi-client.js`
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-10-20 22:10:59 +02:00			`js/vapi-appinfo.js`
Work on vendor API abstraction, and near complete Safari support 2014-10-17 21:44:19 +02:00			`js/udom.js`
			`js/i18n.js`
			`js/dashboard-common.js`
			`js/about.js`
			`"></script>`
first commit 2014-06-24 00:42:43 +02:00
			`</body>`
			`</html>`