Cliqz for iOS
Localization works as described in the Apple Documentation or this helpful tutorial. Strings files are included in the project and can be exported to and imported from Xliff files if necessary for translation by external translation agencies.
Strings files live in the
To test localization, you can edit your currently active scheme, and in "Options", set the "Application Language". Don't commit this change please.
Everything below this line is taken from the FIrefox Readme and should be checked if it still applies, and if yes, moved to above this line
Building the code
- Install the latest Xcode developer tools from Apple.
- Install Carthage
brew update brew install carthage
- Clone the repository:
git clone https://github.com/mozilla-mobile/firefox-ios
- Pull in the project dependencies:
cd firefox-ios sh ./bootstrap.sh
- Build the
Fennecscheme in Xcode.
Building User Scripts
WKWebView) are compiled, concatenated and minified using webpack. User Scripts to be aggregated are placed in the following directories:
/Client |-- /Frontend |-- /UserContent |-- /UserScripts |-- /AllFrames | |-- /AtDocumentEnd | |-- /AtDocumentStart |-- /MainFrame |-- /AtDocumentEnd |-- /AtDocumentStart
This reduces the total possible number of User Scripts down to four. The compiled output from concatenating and minifying the User Scripts placed in these folders resides in
/Client/Assets and are named accordingly:
To simplify the build process, these compiled files are checked-in to this repository. When adding or editing User Scripts, these files can be re-compiled with
webpack manually. This requires Node.js to be installed and all required
npm packages can be installed by running
npm install in the root directory of the project. User Scripts can be compiled by running the following
npm command in the root directory of the project:
npm run build
Creating a pull request
- All pull requests must be associated with a specific Issue. If an issue doesn't exist please first create it.
- Swift code should generally follow the conventions listed at https://github.com/raywenderlich/swift-style-guide.
- Exception: we use 4-space indentation instead of 2.
- This is a loose standard. We do our best to follow this style
- New code should not contain any trailing whitespace.
- We recommend enabling both the "Automatically trim trailing whitespace" and "Including whitespace-only lines" preferences in Xcode (under Text Editing).
git rebase --whitespace=fixcan also be used to remove whitespace from your commits before issuing a pull request.
- Each commit should have a single clear purpose. If a commit contains multiple unrelated changes, those changes should be split into separate commits.
- If a commit requires another commit to build properly, those commits should be squashed.
- Follow-up commits for any review comments should be squashed. Do not include "Fixed PR comments", merge commits, or other "temporary" commits in pull requests.