├── .circleci
└── config.yml
├── .github
└── PULL_REQUEST_TEMPLATE.md
├── .gitignore
├── CODE_OF_CONDUCT.md
├── CONTRIBUTING.md
├── README.md
├── build.gradle
├── gradle.properties
├── gradle
└── wrapper
│ ├── gradle-wrapper.jar
│ └── gradle-wrapper.properties
├── gradlew
├── gradlew.bat
├── images
├── ss.png
├── ss1.png
├── ss2.png
└── vid.gif
└── settings.gradle
/.circleci/config.yml:
--------------------------------------------------------------------------------
1 | version: 2.1
2 |
3 | orbs:
4 | android: circleci/android@0.2.1
5 |
6 | jobs:
7 | build:
8 | executor: android/android
9 |
10 | steps:
11 | - checkout
12 | - run:
13 | command: ./gradlew build
14 |
--------------------------------------------------------------------------------
/.github/PULL_REQUEST_TEMPLATE.md:
--------------------------------------------------------------------------------
1 |
5 |
6 | ## Explanation
7 |
12 |
13 | ## Checklist
14 |
15 |
16 | - [ ] The PR title starts with "Fix #bugnum: ", followed by a short, clear summary of the changes. (If this PR fixes part of an issue, prefix the title with "Fix part of #bugnum: ...".)
17 | - [ ] The PR explanation includes the words "Fixes #bugnum: ..." (or "Fixes part of #bugnum" if the PR only partially fixes an issue).
18 | - [ ] The PR does not contain any unnecessary auto-generated code from Android Studio.
19 | - [ ] The PR does not break any part of the existing code.
20 | - [ ] The PR creator have carefully read & adher to the contributing guidelines of the project.
21 | - [ ] The PR is made to the branch that's **called** "develop".
22 | - [ ] The PR is made from a branch that is up-to-date with "develop".
23 |
24 |
--------------------------------------------------------------------------------
/.gitignore:
--------------------------------------------------------------------------------
1 | *.iml
2 | .gradle
3 | /local.properties
4 | /.idea/caches
5 | /.idea/libraries
6 | /.idea/modules.xml
7 | /.idea/workspace.xml
8 | /.idea/navEditor.xml
9 | /.idea/assetWizardSettings.xml
10 | .DS_Store
11 | /build
12 | /app
13 | /captures
14 | .externalNativeBuild
15 | .cxx
16 | .idea/
17 |
18 |
--------------------------------------------------------------------------------
/CODE_OF_CONDUCT.md:
--------------------------------------------------------------------------------
1 | # Code of Conduct
2 |
3 |
4 | ### Our Pledge
5 |
6 | In the interest of fostering an open and welcoming environment, we as
7 | contributors and maintainers pledge to making participation in our project and
8 | our community a harassment-free experience for everyone, regardless of age, body
9 | size, disability, ethnicity, gender identity and expression, level of experience,
10 | nationality, personal appearance, race, religion, or sexual identity and
11 | orientation.
12 |
13 |
14 | ### Our Standards
15 |
16 | Examples of behavior that contributes to creating a positive environment
17 | include:
18 |
19 | * Using welcoming and inclusive language
20 | * Being respectful of differing viewpoints and experiences
21 | * Gracefully accepting constructive criticism
22 | * Focusing on what is best for the community
23 | * Showing empathy towards other community members
24 |
25 | Examples of unacceptable behavior by participants include:
26 |
27 | * The use of sexualized language or imagery and unwelcome sexual attention or
28 | advances
29 | * Trolling, insulting/derogatory comments, and personal or political attacks
30 | * Public or private harassment
31 | * Publishing others' private information, such as a physical or electronic
32 | address, without explicit permission
33 | * Other conduct which could reasonably be considered inappropriate in a
34 | professional setting
35 |
36 |
37 | ### Our Responsibilities
38 |
39 | Project maintainers are responsible for clarifying the standards of acceptable
40 | behavior and are expected to take appropriate and fair corrective action in
41 | response to any instances of unacceptable behavior.
42 |
43 | Project maintainers have the right and responsibility to remove, edit, or
44 | reject comments, commits, code, wiki edits, issues, and other contributions
45 | that are not aligned to this Code of Conduct, or to ban temporarily or
46 | permanently any contributor for other behaviors that they deem inappropriate,
47 | threatening, offensive, or harmful.
48 |
49 |
50 | ### Scope
51 |
52 | This Code of Conduct applies both within project spaces and in public spaces
53 | when an individual is representing the project or its community. Examples of
54 | representing a project or community include using an official project e-mail
55 | address, posting via an official social media account, or acting as an appointed
56 | representative at an online or offline event. Representation of a project may be
57 | further defined and clarified by project maintainers.
58 |
59 |
60 | ### Enforcement
61 |
62 | Instances of abusive, harassing, or otherwise unacceptable behavior may be
63 | reported by contacting the project team at rrjain20122000@gmail.com. All
64 | complaints will be reviewed and investigated and will result in a response that
65 | is deemed necessary and appropriate to the circumstances. The project team is
66 | obligated to maintain confidentiality with regard to the reporter of an incident.
67 | Further details of specific enforcement policies may be posted separately.
68 |
69 | Project maintainers who do not follow or enforce the Code of Conduct in good
70 | faith may face temporary or permanent repercussions as determined by other
71 | members of the project's leadership.
72 |
73 |
74 | ### Attribution
75 |
76 | This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
77 | available at [http://contributor-covenant.org/version/1/4][version]
78 |
79 | [homepage]: http://contributor-covenant.org
80 | [version]: http://contributor-covenant.org/version/1/4/
81 |
--------------------------------------------------------------------------------
/CONTRIBUTING.md:
--------------------------------------------------------------------------------
1 | # Contributing Guildelines
2 |
3 | ### 👍🎉 First off, welcome to the project and thanks for taking the time to contribute! 🎉👍
4 |
5 |
6 | #### When contributing to this repository, please first discuss the change you wish to make before making a change.
7 |
8 |
9 | ## Before Getting Started!
10 | Learn how to fork a repo, create an issue, make changes, create pull request.
11 |
12 | For more information, refer to GitHub Documentation
13 |
14 | --------
15 | ## Contributing Process
16 | 1. Go through 'Issues' to ensure whether the said issue has already been raised.
17 |
18 | 2. If you do find a new issue, do not hesitate to open a new one. Make sure to describe any additions required in the message.
19 |
20 | 3. If interested, do mention in the issue that you want to work on it.
21 |
22 | 4. Kindly wait for the approval from the maintainers of this project before starting to work on any issue.
23 |
24 | 5. **Do not make changes to the main branch.** All the changes should be made to the develop branch.
25 |
26 | 6. Make sure that your code is properly formatted and does not contain any commented out code.
27 |
28 | 7. Create a pull request after making the required changes and do mention the issue number that your pull request is related to.
29 |
30 | 8. Finally, wait for it to be reviewed. Make the required changes if the reviewer asks for them.
31 |
32 | 9. Your pull request will be merged once everything seems okay.
33 |
34 | 10. That's it! You have successfully made your contribution to the project.
35 |
36 |
37 | ## GIT AND GITHUB
38 |
39 |
40 | Before continuing we want to clarify the difference between Git and Github. Git is a version control system(VCS) which is a tool to manage the history of our Source Code. GitHub is a hosting service for Git projects.
41 |
42 | We assume you have created an account on Github and installed Git on your System.
43 |
44 | Now tell Git your name and E-mail (used on Github) address.
45 |
46 | $ git config --global user.name "YOUR NAME"
47 | $ git config --global user.email "YOUR EMAIL ADDRESS"
48 |
49 |
50 | This is an important step to mark your commits to your name and email.
51 |
52 | ### FORK A PROJECT -
53 |
54 | You can use github explore - https://github.com/explore to find a project that interests you and match your skills. Once you find your cool project to workon, you can make a copy of project to your account. This process is called forking a project to your Github account. On Upper right side of project page on Github, you can see -
55 |
56 |
57 |
58 | Click on fork to create a copy of project to your account. This creates a separate copy for you to workon.
59 |
60 | ### FINDING A FEATURE OR BUG TO WORKON -
61 |
62 | Open Source projects always have something to workon and improves with each new release. You can see the issues section to find something you can solve or report a bug. The project managers always welcome new contributors and can guide you to solve the problem. You can find issues in the right section of project page.
63 |
64 |
65 |
66 | ### CLONE THE FORKED PROJECT -
67 |
68 | You have forked the project you want to contribute to your github account. To get this project on your development machine we use clone command of git.
69 |
70 | ```$ git clone https://github.com//.git```
71 | Now you have the project on your local machine.
72 |
73 | ### ADD A REMOTE (UPSTREAM) TO ORIGINAL PROJECT REPOSITORY
74 |
75 | Remote means the remote location of project on Github. By cloning, we have a remote called origin which points to your forked repository. Now we will add a remote to the original repository from where we had forked.
76 |
77 | $ cd
78 | $ git remote add upstream https://github.com//.git
79 |
80 | You will see the benefits of adding remote later.
81 |
82 | ### SYNCHRONIZING YOUR FORK -
83 |
84 | Open Source projects have a number of contributors who can push code anytime. So it is necessary to make your forked copy equal with the original repository. The remote added above called Upstream helps in this.
85 |
86 |
87 | $ git checkout master
88 | $ git fetch upstream
89 | $ git merge upstream/master
90 | $ git push origin master
91 |
92 |
93 | The last command pushes the latest code to your forked repository on Github. The origin is the remote pointing to your forked repository on github.
94 |
95 | ### CREATE A NEW BRANCH FOR A FEATURE OR BUGFIX -
96 |
97 | Normally, all repositories have a master branch which is considered to remain stable and all new features should be made in a separate branch and after completion merged into master branch. So we should create a new branch for our feature or bugfix and start working on the issue.
98 |
99 | ```$ git checkout -b ```
100 | This will create a new branch out of master branch. Now start working on the problem and commit your changes.
101 |
102 | $ git add --all
103 | $ git commit -m ""
104 |
105 |
106 | The first command adds all the files or you can add specific files by removing -a and adding the file names. The second command gives a message to your changes so you can know in future what changes this commit makes. If you are solving an issue on original repository, you should add the issue number like #35 to your commit message. This will show the reference to commits in the issue.
107 |
108 | ### REBASE YOUR FEATURE BRANCH WITH UPSTREAM-
109 |
110 | It can happen that your feature takes time to complete and other contributors are constantly pushing code. After completing the feature your feature branch should be rebase on latest changes to upstream master branch.
111 |
112 | $ git checkout
113 | $ git pull --rebase upstream master
114 |
115 | Now you get the latest commits from other contributors and check that your commits are compatible with the new commits. If there are any conflicts solve them.
116 |
117 | ### SQUASHING YOUR COMMITS-
118 |
119 | You have completed the feature, but you have made a number of commits which make less sense. You should squash your commits to make good commits.
120 |
121 | ```$ git rebase -i HEAD~5```
122 | This will open an editor which will allow you to squash the commits.
123 |
124 | ### PUSH CODE AND CREATE A PULL REQUEST -
125 |
126 | Till this point you have a new branch with the feature or bugfix you want in the project you had forked. Now push your new branch to your remote fork on github.
127 |
128 | ```$ git push origin ```
129 |
130 | Now you are ready to help the project by opening a pull request means you now tell the project managers to add the feature or bugfix to original repository. You can open a pull request by clicking on green icon -
131 |
132 |
133 |
134 | Remember your upstream base branch should be master and source should be your feature branch. Click on create pull request and add a name to your pull request. You can also describe your feature.
135 |
136 | Awesome! You have made your first contribution. For any queries join our Discord server [here](https://discord.com/invite/rAz3Eb8fsN) .
137 |
138 | #### BE OPEN!
139 |
140 | -----------------
141 |
142 | ### **Note**: Always comment and provide apt descriptions wherever necessary for efficient running of the project.
143 |
--------------------------------------------------------------------------------
/README.md:
--------------------------------------------------------------------------------
1 | # 💻 An Open Source Android App to Educate people about the right style of getting educated!.📰🔥.
2 |
3 |
Join the Discord Server [here](https://discord.gg/rAz3Eb8fsN)
4 |
5 | 💻💻Follow us on [LinkedIn](https://www.linkedin.com/company/cswala)
6 |
7 | 
8 | 
9 |
10 | [](https://opensource.org/licenses/MIT)
11 | [](https://github.com/ellerbrock/open-source-badges/)
12 | [](http://makeapullrequest.com)
13 | 
14 | 
15 |
16 | 
17 | 
18 | 
19 |
20 |
21 |
22 |
23 |
24 |
25 | ## 🔥 Features
26 |
27 | 📰 Get the Latest Updates about Everything there exists in Computer Science.
28 |
29 | ✨ Search in a Dictionary Style manner.
30 |
31 | 🚀 Get Ahead with the right guidance from the Community.
32 |
33 | ## 🛠 Tech Used
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 | [](https://forthebadge.com)
42 | [](https://forthebadge.com)
43 | [](https://forthebadge.com)
44 |
45 | ## Contribution Guidelines ⚙️
46 |
47 | You can find our Contributing guidelines [here](https://github.com/CSwala/CSwala-android/blob/main/CONTRIBUTING.md).
48 |
49 | ## 😎Maintainers
50 |
51 |
70 |
71 | ## Code Of Conduct:
72 |
73 | You can find our Code of Conduct [here](https://github.com/CSwala/CSwala-android/blob/main/CODE_OF_CONDUCT.md).
74 |
75 | ## License 📝
76 |
77 | This project follows the [MIT License](https://choosealicense.com/licenses/mit/).
78 |
79 | Contributors:
80 |
81 | ### Credit goes to these people:✨
82 |
83 |
92 |
93 |
94 | Made with ❤ by CS wala
95 |
96 |
97 | If you liked the project don't forget to 🌟 and 🍽 the project.
98 |
--------------------------------------------------------------------------------
/build.gradle:
--------------------------------------------------------------------------------
1 | // Top-level build file where you can add configuration options common to all sub-projects/modules.
2 | buildscript {
3 | ext {
4 | kotlin_version = '1.3.72'
5 | }
6 | repositories {
7 | google()
8 | jcenter()
9 | }
10 | dependencies {
11 | classpath 'com.android.tools.build:gradle:4.1.3'
12 | classpath 'com.google.gms:google-services:4.3.5'
13 |
14 | // NOTE: Do not place your application dependencies here; they belong
15 | // in the individual module build.gradle files
16 | }
17 | }
18 |
19 | allprojects {
20 | repositories {
21 | google()
22 | jcenter()
23 | maven { url 'https://jitpack.io' }
24 | }
25 | }
26 |
27 | task clean(type: Delete) {
28 | delete rootProject.buildDir
29 | }
--------------------------------------------------------------------------------
/gradle.properties:
--------------------------------------------------------------------------------
1 | # Project-wide Gradle settings.
2 | # IDE (e.g. Android Studio) users:
3 | # Gradle settings configured through the IDE *will override*
4 | # any settings specified in this file.
5 | # For more details on how to configure your build environment visit
6 | # http://www.gradle.org/docs/current/userguide/build_environment.html
7 | # Specifies the JVM arguments used for the daemon process.
8 | # The setting is particularly useful for tweaking memory settings.
9 | org.gradle.jvmargs=-Xmx2048m
10 | # When configured, Gradle will run in incubating parallel mode.
11 | # This option should only be used with decoupled projects. More details, visit
12 | # http://www.gradle.org/docs/current/userguide/multi_project_builds.html#sec:decoupled_projects
13 | # org.gradle.parallel=true
14 | # AndroidX package structure to make it clearer which packages are bundled with the
15 | # Android operating system, and which are packaged with your app"s APK
16 | # https://developer.android.com/topic/libraries/support-library/androidx-rn
17 | android.useAndroidX=true
18 | # Automatically convert third-party libraries to use AndroidX
19 | android.enableJetifier=true
--------------------------------------------------------------------------------
/gradle/wrapper/gradle-wrapper.jar:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/CSwala/CSwala-android/2d7090f78a4c44f37c948a1076d53dcd00da2867/gradle/wrapper/gradle-wrapper.jar
--------------------------------------------------------------------------------
/gradle/wrapper/gradle-wrapper.properties:
--------------------------------------------------------------------------------
1 | #Tue Feb 02 14:03:24 IST 2021
2 | distributionBase=GRADLE_USER_HOME
3 | distributionPath=wrapper/dists
4 | zipStoreBase=GRADLE_USER_HOME
5 | zipStorePath=wrapper/dists
6 | distributionUrl=https\://services.gradle.org/distributions/gradle-6.5-all.zip
7 |
--------------------------------------------------------------------------------
/gradlew:
--------------------------------------------------------------------------------
1 | #!/usr/bin/env sh
2 |
3 | ##############################################################################
4 | ##
5 | ## Gradle start up script for UN*X
6 | ##
7 | ##############################################################################
8 |
9 | # Attempt to set APP_HOME
10 | # Resolve links: $0 may be a link
11 | PRG="$0"
12 | # Need this for relative symlinks.
13 | while [ -h "$PRG" ] ; do
14 | ls=`ls -ld "$PRG"`
15 | link=`expr "$ls" : '.*-> \(.*\)$'`
16 | if expr "$link" : '/.*' > /dev/null; then
17 | PRG="$link"
18 | else
19 | PRG=`dirname "$PRG"`"/$link"
20 | fi
21 | done
22 | SAVED="`pwd`"
23 | cd "`dirname \"$PRG\"`/" >/dev/null
24 | APP_HOME="`pwd -P`"
25 | cd "$SAVED" >/dev/null
26 |
27 | APP_NAME="Gradle"
28 | APP_BASE_NAME=`basename "$0"`
29 |
30 | # Add default JVM options here. You can also use JAVA_OPTS and GRADLE_OPTS to pass JVM options to this script.
31 | DEFAULT_JVM_OPTS=""
32 |
33 | # Use the maximum available, or set MAX_FD != -1 to use that value.
34 | MAX_FD="maximum"
35 |
36 | warn () {
37 | echo "$*"
38 | }
39 |
40 | die () {
41 | echo
42 | echo "$*"
43 | echo
44 | exit 1
45 | }
46 |
47 | # OS specific support (must be 'true' or 'false').
48 | cygwin=false
49 | msys=false
50 | darwin=false
51 | nonstop=false
52 | case "`uname`" in
53 | CYGWIN* )
54 | cygwin=true
55 | ;;
56 | Darwin* )
57 | darwin=true
58 | ;;
59 | MINGW* )
60 | msys=true
61 | ;;
62 | NONSTOP* )
63 | nonstop=true
64 | ;;
65 | esac
66 |
67 | CLASSPATH=$APP_HOME/gradle/wrapper/gradle-wrapper.jar
68 |
69 | # Determine the Java command to use to start the JVM.
70 | if [ -n "$JAVA_HOME" ] ; then
71 | if [ -x "$JAVA_HOME/jre/sh/java" ] ; then
72 | # IBM's JDK on AIX uses strange locations for the executables
73 | JAVACMD="$JAVA_HOME/jre/sh/java"
74 | else
75 | JAVACMD="$JAVA_HOME/bin/java"
76 | fi
77 | if [ ! -x "$JAVACMD" ] ; then
78 | die "ERROR: JAVA_HOME is set to an invalid directory: $JAVA_HOME
79 |
80 | Please set the JAVA_HOME variable in your environment to match the
81 | location of your Java installation."
82 | fi
83 | else
84 | JAVACMD="java"
85 | which java >/dev/null 2>&1 || die "ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.
86 |
87 | Please set the JAVA_HOME variable in your environment to match the
88 | location of your Java installation."
89 | fi
90 |
91 | # Increase the maximum file descriptors if we can.
92 | if [ "$cygwin" = "false" -a "$darwin" = "false" -a "$nonstop" = "false" ] ; then
93 | MAX_FD_LIMIT=`ulimit -H -n`
94 | if [ $? -eq 0 ] ; then
95 | if [ "$MAX_FD" = "maximum" -o "$MAX_FD" = "max" ] ; then
96 | MAX_FD="$MAX_FD_LIMIT"
97 | fi
98 | ulimit -n $MAX_FD
99 | if [ $? -ne 0 ] ; then
100 | warn "Could not set maximum file descriptor limit: $MAX_FD"
101 | fi
102 | else
103 | warn "Could not query maximum file descriptor limit: $MAX_FD_LIMIT"
104 | fi
105 | fi
106 |
107 | # For Darwin, add options to specify how the application appears in the dock
108 | if $darwin; then
109 | GRADLE_OPTS="$GRADLE_OPTS \"-Xdock:name=$APP_NAME\" \"-Xdock:icon=$APP_HOME/media/gradle.icns\""
110 | fi
111 |
112 | # For Cygwin, switch paths to Windows format before running java
113 | if $cygwin ; then
114 | APP_HOME=`cygpath --path --mixed "$APP_HOME"`
115 | CLASSPATH=`cygpath --path --mixed "$CLASSPATH"`
116 | JAVACMD=`cygpath --unix "$JAVACMD"`
117 |
118 | # We build the pattern for arguments to be converted via cygpath
119 | ROOTDIRSRAW=`find -L / -maxdepth 1 -mindepth 1 -type d 2>/dev/null`
120 | SEP=""
121 | for dir in $ROOTDIRSRAW ; do
122 | ROOTDIRS="$ROOTDIRS$SEP$dir"
123 | SEP="|"
124 | done
125 | OURCYGPATTERN="(^($ROOTDIRS))"
126 | # Add a user-defined pattern to the cygpath arguments
127 | if [ "$GRADLE_CYGPATTERN" != "" ] ; then
128 | OURCYGPATTERN="$OURCYGPATTERN|($GRADLE_CYGPATTERN)"
129 | fi
130 | # Now convert the arguments - kludge to limit ourselves to /bin/sh
131 | i=0
132 | for arg in "$@" ; do
133 | CHECK=`echo "$arg"|egrep -c "$OURCYGPATTERN" -`
134 | CHECK2=`echo "$arg"|egrep -c "^-"` ### Determine if an option
135 |
136 | if [ $CHECK -ne 0 ] && [ $CHECK2 -eq 0 ] ; then ### Added a condition
137 | eval `echo args$i`=`cygpath --path --ignore --mixed "$arg"`
138 | else
139 | eval `echo args$i`="\"$arg\""
140 | fi
141 | i=$((i+1))
142 | done
143 | case $i in
144 | (0) set -- ;;
145 | (1) set -- "$args0" ;;
146 | (2) set -- "$args0" "$args1" ;;
147 | (3) set -- "$args0" "$args1" "$args2" ;;
148 | (4) set -- "$args0" "$args1" "$args2" "$args3" ;;
149 | (5) set -- "$args0" "$args1" "$args2" "$args3" "$args4" ;;
150 | (6) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" ;;
151 | (7) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" "$args6" ;;
152 | (8) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" "$args6" "$args7" ;;
153 | (9) set -- "$args0" "$args1" "$args2" "$args3" "$args4" "$args5" "$args6" "$args7" "$args8" ;;
154 | esac
155 | fi
156 |
157 | # Escape application args
158 | save () {
159 | for i do printf %s\\n "$i" | sed "s/'/'\\\\''/g;1s/^/'/;\$s/\$/' \\\\/" ; done
160 | echo " "
161 | }
162 | APP_ARGS=$(save "$@")
163 |
164 | # Collect all arguments for the java command, following the shell quoting and substitution rules
165 | eval set -- $DEFAULT_JVM_OPTS $JAVA_OPTS $GRADLE_OPTS "\"-Dorg.gradle.appname=$APP_BASE_NAME\"" -classpath "\"$CLASSPATH\"" org.gradle.wrapper.GradleWrapperMain "$APP_ARGS"
166 |
167 | # by default we should be in the correct project dir, but when run from Finder on Mac, the cwd is wrong
168 | if [ "$(uname)" = "Darwin" ] && [ "$HOME" = "$PWD" ]; then
169 | cd "$(dirname "$0")"
170 | fi
171 |
172 | exec "$JAVACMD" "$@"
173 |
--------------------------------------------------------------------------------
/gradlew.bat:
--------------------------------------------------------------------------------
1 | @if "%DEBUG%" == "" @echo off
2 | @rem ##########################################################################
3 | @rem
4 | @rem Gradle startup script for Windows
5 | @rem
6 | @rem ##########################################################################
7 |
8 | @rem Set local scope for the variables with windows NT shell
9 | if "%OS%"=="Windows_NT" setlocal
10 |
11 | set DIRNAME=%~dp0
12 | if "%DIRNAME%" == "" set DIRNAME=.
13 | set APP_BASE_NAME=%~n0
14 | set APP_HOME=%DIRNAME%
15 |
16 | @rem Add default JVM options here. You can also use JAVA_OPTS and GRADLE_OPTS to pass JVM options to this script.
17 | set DEFAULT_JVM_OPTS=
18 |
19 | @rem Find java.exe
20 | if defined JAVA_HOME goto findJavaFromJavaHome
21 |
22 | set JAVA_EXE=java.exe
23 | %JAVA_EXE% -version >NUL 2>&1
24 | if "%ERRORLEVEL%" == "0" goto init
25 |
26 | echo.
27 | echo ERROR: JAVA_HOME is not set and no 'java' command could be found in your PATH.
28 | echo.
29 | echo Please set the JAVA_HOME variable in your environment to match the
30 | echo location of your Java installation.
31 |
32 | goto fail
33 |
34 | :findJavaFromJavaHome
35 | set JAVA_HOME=%JAVA_HOME:"=%
36 | set JAVA_EXE=%JAVA_HOME%/bin/java.exe
37 |
38 | if exist "%JAVA_EXE%" goto init
39 |
40 | echo.
41 | echo ERROR: JAVA_HOME is set to an invalid directory: %JAVA_HOME%
42 | echo.
43 | echo Please set the JAVA_HOME variable in your environment to match the
44 | echo location of your Java installation.
45 |
46 | goto fail
47 |
48 | :init
49 | @rem Get command-line arguments, handling Windows variants
50 |
51 | if not "%OS%" == "Windows_NT" goto win9xME_args
52 |
53 | :win9xME_args
54 | @rem Slurp the command line arguments.
55 | set CMD_LINE_ARGS=
56 | set _SKIP=2
57 |
58 | :win9xME_args_slurp
59 | if "x%~1" == "x" goto execute
60 |
61 | set CMD_LINE_ARGS=%*
62 |
63 | :execute
64 | @rem Setup the command line
65 |
66 | set CLASSPATH=%APP_HOME%\gradle\wrapper\gradle-wrapper.jar
67 |
68 | @rem Execute Gradle
69 | "%JAVA_EXE%" %DEFAULT_JVM_OPTS% %JAVA_OPTS% %GRADLE_OPTS% "-Dorg.gradle.appname=%APP_BASE_NAME%" -classpath "%CLASSPATH%" org.gradle.wrapper.GradleWrapperMain %CMD_LINE_ARGS%
70 |
71 | :end
72 | @rem End local scope for the variables with windows NT shell
73 | if "%ERRORLEVEL%"=="0" goto mainEnd
74 |
75 | :fail
76 | rem Set variable GRADLE_EXIT_CONSOLE if you need the _script_ return code instead of
77 | rem the _cmd.exe /c_ return code!
78 | if not "" == "%GRADLE_EXIT_CONSOLE%" exit 1
79 | exit /b 1
80 |
81 | :mainEnd
82 | if "%OS%"=="Windows_NT" endlocal
83 |
84 | :omega
85 |
--------------------------------------------------------------------------------
/images/ss.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/CSwala/CSwala-android/2d7090f78a4c44f37c948a1076d53dcd00da2867/images/ss.png
--------------------------------------------------------------------------------
/images/ss1.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/CSwala/CSwala-android/2d7090f78a4c44f37c948a1076d53dcd00da2867/images/ss1.png
--------------------------------------------------------------------------------
/images/ss2.png:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/CSwala/CSwala-android/2d7090f78a4c44f37c948a1076d53dcd00da2867/images/ss2.png
--------------------------------------------------------------------------------
/images/vid.gif:
--------------------------------------------------------------------------------
https://raw.githubusercontent.com/CSwala/CSwala-android/2d7090f78a4c44f37c948a1076d53dcd00da2867/images/vid.gif
--------------------------------------------------------------------------------
/settings.gradle:
--------------------------------------------------------------------------------
1 | include ':app'
2 | rootProject.name = "CSwala"
--------------------------------------------------------------------------------