This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
angular.module('myMdl', []).config(['$httpProvider', function($httpProvider) { | |
$httpProvider.responseInterceptors.push([ | |
'$q', '$templateCache', 'activeProfile', | |
function($q, $templateCache, activeProfile) { | |
// Keep track which HTML templates have already been modified. | |
var modifiedTemplates = {}; | |
// Tests if there are any keep/omit attributes. | |
var HAS_FLAGS_EXP = /data-(keep|omit)/; |
- Log into BF4 Battlelog.
- Visit the Customize emblem page.
- Select the emblem you wish to export.
- Open the console (Ctrl-Shift-J).
- Enter the following code snippet to copy the raw emblem data to the clipboard:
copy('emblem.emblem.load('+JSON.stringify(emblem.emblem.data,null,2)+');');
- Paste somewhere useful, like a gist. Whatever.
- Close the console (Ctrl-Shift-J).
All custom modules should have a Namespace and Module Name.
These are used below as {Namespace}
and {Module}
.
Caution: The Magento autoloader is known to have problems with CamelCase namespaces and/or modules between Windows and *nix systems. If your module requires more than one word for either of these, it is best to just concatenate them to avoid any issues (Example:
{Namespace}_{Examplemodule}
).