Skip to content

Commit 9cb73e9

Browse files
SvetoslavTsenovSvetoslavTsenov
committed
Add 'tns-core-modules-widgets/' from commit '4d29082e49a85187f50ede98fb634e6ae6f6ef46'
git-subtree-dir: tns-core-modules-widgets git-subtree-mainline: e6486f6 git-subtree-split: 4d29082
2 parents e6486f6 + 4d29082 commit 9cb73e9

94 files changed

Lines changed: 15416 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎tns-core-modules-widgets/.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,29 @@
1+
---
2+
name: Bug report
3+
about: 'We really appreciate your effort to provide feedback. Before opening a new
4+
issue, please make sure that this case is not already reported in GitHub as an
5+
issue or in StackOverflow as a question.'
6+
7+
---
8+
9+
**Environment**
10+
Provide version numbers for the following components (information can be retrieved by running `tns info` in your project folder or by inspecting the `package.json` of the project):
11+
- CLI:
12+
- Cross-platform modules:
13+
- Android Runtime:
14+
- iOS Runtime:
15+
- Plugin(s):
16+
17+
**Describe the bug**
18+
<!-- A clear and concise description of what the bug is. Please, explain whether it's a build time error or a runtime error. More detailed logs can be easily obtained by following the instructions in this guide: https://docs.nativescript.org/get-support#how-to-obtain-diagnostic-reports. -->
19+
20+
**To Reproduce**
21+
<!-- Add commands used or steps taken to reproduce the behaviour. -->
22+
23+
**Expected behavior**
24+
25+
**Sample project**
26+
<!-- If possible, provide a link from the [Playground](https://play.nativescript.org) with reproduction of the problem. If not, consider attaching a sample project or link to a repository with such project. -->
27+
28+
**Additional context**
29+
<!-- Add any other context about the problem here. -->

‎tns-core-modules-widgets/.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
5+
---
6+
7+
**Is your feature request related to a problem? Please describe.**
8+
<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]. -->
9+
10+
**Describe the solution you'd like**
11+
<!-- A clear and concise description of what you want to happen. -->
12+
13+
**Describe alternatives you've considered**
14+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
15+
16+
**Additional context**
17+
<!-- Add any other context or screenshots about the feature request here. -->

‎tns-core-modules-widgets/.github/pull_request_template.md‎

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
<!--
2+
We, the rest of the NativeScript community, thank you for your
3+
contribution!
4+
To help the rest of the community review your change, please follow the instructions in the template.
5+
-->
6+
7+
<!-- PULL REQUEST TEMPLATE -->
8+
<!-- (Update "[ ]" to "[x]" to check a box) -->
9+
10+
## PR Checklist
11+
12+
- [ ] The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/CONTRIBUTING.md#commit-messages.
13+
- [ ] There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
14+
- [ ] You have signed the [CLA](http://www.nativescript.org/cla).
15+
- [ ] All existing tests are passing
16+
- [ ] Tests for the changes are included
17+
18+
## What is the current behavior?
19+
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
20+
21+
## What is the new behavior?
22+
<!-- Describe the changes. -->
23+
24+
Fixes/Implements/Closes #[Issue Number].
25+
26+
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below. -->
27+
28+
<!--
29+
BREAKING CHANGES:
30+
31+
32+
[Describe the impact of the changes here.]
33+
34+
Migration steps:
35+
[Provide a migration path for existing applications.]
36+
-->
37+

‎tns-core-modules-widgets/.gitignore‎

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
/dist
2+
/build
3+
4+
*.iml
5+
6+
# Proguard folder generated by Eclipse
7+
proguard/
8+
9+
# Log Files
10+
*.log
11+
12+
# Android Studio Navigation editor temp files
13+
.navigation/
14+
15+
# Android Studio captures folder
16+
captures/
17+
18+
# Built application files
19+
build/
20+
21+
## File-based project format:
22+
*.ipr
23+
*.iws
24+
25+
# Crashlytics plugin (for Android Studio and IntelliJ)
26+
com_crashlytics_export_strings.xml
27+
crashlytics.properties
28+
crashlytics-build.properties
29+
fabric.properties
30+
31+
## Directory-based project format:
32+
.idea/
33+
34+
# Local configuration file (sdk path, etc)
35+
local.properties
36+
37+
# Gradle generated files
38+
.gradle/
39+
40+
# Signing files
41+
.signing/
42+
43+
# OS-specific files
44+
.DS_Store
45+
.DS_Store?
46+
ios/TNSWidgets/TNSWidgets.xcodeproj/project.xcworkspace/xcuserdata/
47+
ios/TNSWidgets/TNSWidgets.xcodeproj/xcuserdata/
48+
ios/TNSWidgets/DerivedData/
49+
50+
android/widgets/bin
51+
android/widgets/.settings
52+
android/.project
53+
android/widgets/.project
54+
android/.settings

‎tns-core-modules-widgets/.travis.yml‎

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
env:
2+
global:
3+
- DATE=$(date +%Y-%m-%d)
4+
- PACKAGE_VERSION=$DATE-$TRAVIS_BUILD_NUMBER
5+
language: objective-c
6+
osx_image: xcode8.3
7+
install:
8+
- brew update
9+
- brew cask install android-sdk
10+
# Suppress output of sdkmanager to keep log under the 4MB limit of travis-ci
11+
- yes | sdkmanager "platforms;android-23" >/dev/null
12+
- yes | sdkmanager "build-tools;23.0.3" >/dev/null
13+
- yes | sdkmanager "extras;android;m2repository" >/dev/null
14+
before_script:
15+
- export ANDROID_HOME=/usr/local/share/android-sdk
16+
script: ./build.sh $PACKAGE_VERSION

‎tns-core-modules-widgets/CODE_OF_CONDUCT.md‎

Lines changed: 83 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,83 @@
1+
# NativeScript Community Code of Conduct
2+
3+
Our community members come from all walks of life and are all at different stages of their personal and professional journeys. To support everyone, we've prepared a short code of conduct. Our mission is best served in an environment that is friendly, safe, and accepting; free from intimidation or harassment.
4+
5+
Towards this end, certain behaviors and practices will not be tolerated.
6+
7+
## tl;dr
8+
9+
- Be respectful.
10+
- We're here to help.
11+
- Abusive behavior is never tolerated.
12+
- Violations of this code may result in swift and permanent expulsion from the NativeScript community channels.
13+
14+
## Administrators
15+
16+
- Dan Wilson (@DanWilson on Slack)
17+
- Jen Looper (@jen.looper on Slack)
18+
- TJ VanToll (@tjvantoll on Slack)
19+
20+
## Scope
21+
22+
We expect all members of the NativeScript community, including administrators, users, facilitators, and vendors to abide by this Code of Conduct at all times in our community venues, online and in person, and in one-on-one communications pertaining to NativeScript affairs.
23+
24+
This policy covers the usage of the NativeScript Slack community, as well as the NativeScript support forums, NativeScript GitHub repositories, the NativeScript website, and any NativeScript-related events. This Code of Conduct is in addition to, and does not in any way nullify or invalidate, any other terms or conditions related to use of NativeScript.
25+
26+
The definitions of various subjective terms such as "discriminatory", "hateful", or "confusing" will be decided at the sole discretion of the NativeScript administrators.
27+
28+
## Friendly, Harassment-Free Space
29+
30+
We are committed to providing a friendly, safe, and welcoming environment for all, regardless of gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics.
31+
32+
We ask that you please respect that people have differences of opinion regarding technical choices, and acknowledge that every design or implementation choice carries a trade-off and numerous costs. There is seldom a single right answer. A difference of technology preferences is never a license to be rude.
33+
34+
Any spamming, trolling, flaming, baiting, or other attention-stealing behaviour is not welcome, and will not be tolerated.
35+
36+
Harassing other users of NativeScript is never tolerated, whether via public or private media.
37+
38+
Avoid using offensive or harassing package names, nicknames, or other identifiers that might detract from a friendly, safe, and welcoming environment for all.
39+
40+
Harassment includes, but is not limited to: harmful or prejudicial verbal or written comments related to gender identity, sexual orientation, disability, ethnicity, religion, age, physical appearance, body size, race, or similar personal characteristics; inappropriate use of nudity, sexual images, and/or sexually explicit language in public spaces; threats of physical or non-physical harm; deliberate intimidation, stalking or following; harassing photography or recording; sustained disruption of talks or other events; inappropriate physical contact; and unwelcome sexual attention.
41+
42+
## Acceptable Content
43+
44+
The NativeScript administrators reserve the right to make judgement calls about what is and isn't appropriate in published content. These are guidelines to help you be successful in our community.
45+
46+
Content must contain something applicable to the previously stated goals of the NativeScript community. "Spamming", that is, publishing any form of content that is not applicable, is not allowed.
47+
48+
Content must not contain illegal or infringing content. You should only publish content to NativeScript properties if you have the right to do so. This includes complying with all software license agreements or other intellectual property restrictions. For example, redistributing an MIT-licensed module with the copyright notice removed, would not be allowed. You will be responsible for any violation of laws or others’ intellectual property rights.
49+
50+
Content must not be malware. For example, content (code, video, pictures, words, etc.) which is designed to maliciously exploit or damage computer systems, is not allowed.
51+
52+
Content name, description, and other visible metadata must not include abusive, inappropriate, or harassing content.
53+
54+
## Reporting Violations of this Code of Conduct
55+
56+
If you believe someone is harassing you or has otherwise violated this Code of Conduct, please contact the administrators and send us an abuse report. If this is the initial report of a problem, please include as much detail as possible. It is easiest for us to address issues when we have more context.
57+
58+
## Consequences
59+
60+
All content published to the NativeScript community channels is hosted at the sole discretion of the NativeScript administrators.
61+
62+
Unacceptable behavior from any community member, including sponsors, employees, customers, or others with decision-making authority, will not be tolerated.
63+
64+
Anyone asked to stop unacceptable behavior is expected to comply immediately.
65+
66+
If a community member engages in unacceptable behavior, the NativeScript administrators may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the community without warning (and without refund in the case of a paid event or service).
67+
68+
## Addressing Grievances
69+
70+
If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the administrators. We will do our best to ensure that your grievance is handled appropriately.
71+
72+
In general, we will choose the course of action that we judge as being most in the interest of fostering a safe and friendly community.
73+
74+
## Contact Info
75+
Please contact Dan Wilson @DanWilson if you need to report a problem or address a grievance related to an abuse report.
76+
77+
You are also encouraged to contact us if you are curious about something that might be "on the line" between appropriate and inappropriate content. We are happy to provide guidance to help you be a successful part of our community.
78+
79+
## Credit and License
80+
81+
This Code of Conduct borrows heavily from the WADE Code of Conduct, which is derived from the NodeBots Code of Conduct, which in turn borrows from the npm Code of Conduct, which was derived from the Stumptown Syndicate Citizen's Code of Conduct, and the Rust Project Code of Conduct.
82+
83+
This document may be reused under a Creative Commons Attribution-ShareAlike License.

‎tns-core-modules-widgets/CONTRIBUTING.md‎

Lines changed: 78 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,78 @@
1+
# Contributing to NativeScript Core Modules Widgets
2+
3+
:+1: First of all, thank you for taking the time to contribute! :+1:
4+
5+
Here are some guides on how to do that:
6+
7+
<!-- TOC depthFrom:2 -->
8+
9+
- [Code of Conduct](#code-of-conduct)
10+
- [Reporting Bugs](#reporting-bugs)
11+
- [Requesting Features](#requesting-features)
12+
- [Submitting a PR](#submitting-a-pr)
13+
- [Where to Start](#where-to-start)
14+
15+
<!-- /TOC -->
16+
17+
## Code of Conduct
18+
Help us keep a healthy and open community. We expect all participants in this project to adhere to the [NativeScript Code Of Conduct](https://github.com/NativeScript/codeofconduct).
19+
20+
21+
## Reporting Bugs
22+
23+
1. Always update to the most recent master release; the bug may already be resolved.
24+
2. Search for similar issues in the issues list for this repo; it may already be an identified problem.
25+
3. If this is a bug or problem that is clear, simple, and is unlikely to require any discussion -- it is OK to open an issue on GitHub with a reproduction of the bug including workflows and screenshots. If possible, submit a Pull Request with a failing test, entire application or module. If you'd rather take matters into your own hands, fix the bug yourself (jump down to the [Submitting a PR](#submitting-a-pr) section).
26+
27+
## Requesting Features
28+
29+
1. Use Github Issues to submit feature requests.
30+
2. First, search for a similar request and extend it if applicable. This way it would be easier for the community to track the features.
31+
3. When requesting a new feature, please provide as much detail as possible about why you need the feature in your apps. We prefer that you explain a need rather than explain a technical solution for it. That might trigger a nice conversation on finding the best and broadest technical solution to a specific need.
32+
33+
## Submitting a PR
34+
35+
Before you begin:
36+
* Read and sign the [NativeScript Contribution License Agreement](http://www.nativescript.org/cla).
37+
* Make sure there is an issue for the bug or feature you will be working on.
38+
39+
Following these steps is the best way to get you code included in the project:
40+
41+
1. Fork and clone the tns-core-modules-widgets repo:
42+
```bash
43+
git clone https://github.com/<your-git-username>/tns-core-modules-widgets.git
44+
# Navigate to the newly cloned directory
45+
cd tns-core-modules-widgets
46+
# Add an "upstream" remote pointing to the original repo.
47+
git remote add upstream https://github.com/NativeScript/tns-core-modules-widgets.git
48+
```
49+
50+
2. Read our [development workflow guide](DevelopmentWorkflow.md) for local setup:
51+
52+
3. Create a branch for your PR
53+
```bash
54+
git checkout -b <my-fix-branch> master
55+
```
56+
57+
4. The fun part! Make your code changes. Make sure you:
58+
- Follow the [code conventions guide](https://github.com/NativeScript/NativeScript/blob/master/CodingConvention.md).
59+
- Write unit tests for your fix or feature.
60+
61+
5. Before you submit your PR:
62+
- Rebase your changes to the latest master: `git pull --rebase upstream master`.
63+
- Ensure all unit test are green. Check [running unit tests](DevelopmentWorkflow.md#running-the-tests).
64+
- Ensure your changes pass tslint validation. (run `npm run tslint` in the root of the repo).
65+
66+
6. Push your fork. If you have rebased you might have to use force-push your branch:
67+
```
68+
git push origin <my-fix-branch> --force
69+
```
70+
71+
7. [Submit your pull request](https://github.com/NativeScript/tns-core-modules-widgets/compare). Please, fill in the Pull Request template - it will help us better understand the PR and increase the chances of it getting merged quickly.
72+
73+
It's our turn from there on! We will review the PR and discuss changes you might have to make before merging it! Thanks!
74+
75+
76+
## Where to Start
77+
78+
If you want to contribute, but you are not sure where to start - look for issues labeled [`help wanted`](https://github.com/NativeScript/tns-core-modules-widgets/issues?q=is%3Aopen+is%3Aissue+label%3A%22help+wanted%22).

‎tns-core-modules-widgets/DevelopmentWorkflow.md‎

Lines changed: 63 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,63 @@
1+
# Development Workflow
2+
3+
<!-- TOC depthFrom:2 -->
4+
5+
- [Prerequisites](#prerequisites)
6+
- [How to Build the Package](#how-to-build-the-package)
7+
- [How to Build Android](#how-to-build-android)
8+
- [How to Build iOS](#how-to-build-ios)
9+
- [How to Use in an Application](#how-to-use-in-an-application)
10+
11+
<!-- /TOC -->
12+
13+
## Prerequisites
14+
15+
Install your native toolchain and NativeScript as described in the docs: https://docs.nativescript.org/setup/quick-setup. In order to open the native Android and iOS project, you need Android Studio and Xcode respectively.
16+
17+
## How to Build the Package
18+
19+
On macOS you can execute:
20+
21+
```shell
22+
$ ./build.sh
23+
```
24+
25+
This script builds both Android and iOS, assembles the package at `./dist/package` and packs it as `./dist/tns-core-modules-widgets-*.tgz`.
26+
27+
## How to Build Android
28+
29+
On Unix-like operating systems you can execute:
30+
31+
```shell
32+
$ ./build.android.sh
33+
```
34+
This script builds only the Android project, assembles the package at `./dist/package` and packs it as `./dist/tns-core-modules-widgets-*.tgz`. The output file is available at `./android/widgets/build/outputs/aar/widgets-release.aar`.
35+
36+
**NOTE:** To run bash script on Windows you can install [GIT SCM](https://git-for-windows.github.io/) and use Git Bash.
37+
38+
## How to Build iOS
39+
40+
On macOS you can execute:
41+
42+
```shell
43+
$ ./build.ios.sh
44+
```
45+
This script builds only the Xcode project, assembles the package at `./dist/package` and packs it as `./dist/tns-core-modules-widgets-*.tgz`. The output native iOS framework is available at `./ios/TNSWidgets/build/TNSWidgets.framework`.
46+
47+
## How to Use in an Application
48+
49+
You could link the `tns-core-modules-widgets` plugin package to your application through the steps listed below.
50+
51+
In the `./dist/package` folder execute:
52+
53+
```
54+
npm link
55+
```
56+
57+
In your application project folder execute:
58+
59+
```
60+
npm link tns-core-modules-widgets
61+
```
62+
63+
Build the plugin with the above-mentioned commands after each change you would like to test.

0 commit comments

Comments
 (0)