You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Apr 13, 2023. It is now read-only.
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
6
-
7
-
## Our Standards
8
-
9
-
Examples of behavior that contributes to creating a positive environment include:
10
-
11
-
* Using welcoming and inclusive language
12
-
* Being respectful of differing viewpoints and experiences
13
-
* Gracefully accepting constructive criticism
14
-
* Focusing on what is best for the community
15
-
* Showing empathy towards other community members
16
-
17
-
Examples of unacceptable behavior by participants include:
18
-
19
-
* The use of sexualized language or imagery and unwelcome sexual attention or advances
20
-
* Trolling, insulting/derogatory comments, and personal or political attacks
21
-
* Public or private harassment
22
-
* Publishing others' private information, such as a physical or electronic address, without explicit permission
23
-
* Other conduct which could reasonably be considered inappropriate in a professional setting
24
-
25
-
## Our Responsibilities
26
-
27
-
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
28
-
29
-
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
30
-
31
-
## Scope
32
-
33
-
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
34
-
35
-
## Enforcement
36
-
37
-
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at [email protected]. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
38
-
39
-
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
40
-
41
-
## Attribution
42
-
43
-
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
Want to Help? You can help by starring this repo, contributing code, testing and reporting bugs.
4
-
5
-
You can always [Chat on Gitter](https://gitter.im/MathewSachin/Captura) for Questions/Discussions.
6
-
7
-
## Contributing Code
8
-
9
-
When contributing major changes to this repository, please first discuss the change you wish to make via issue, email, or any other method before making a change.
10
-
11
-
## Reporting Issues
12
-
13
-
- Check the [FAQ](docs/FAQ.md)
14
-
- Check if a similar issue is already reported. If so then comment on that issue with details specific to your case.
15
-
- Check if the issue is resolved on the latest commit.
16
-
- If possible, Include **steps** to replicate the problem or a sample project.
17
-
18
-
## Translations
19
-
20
-
See [here](docs/Translation.md).
21
-
22
-
## Donations
23
-
24
-
Captura is made and maintained in personal time and is completely Ad-Free.
25
-
You can support this project by donating.
26
-
27
-
-[Paypal][paypal]
28
-
29
-
### Donation History
30
-
31
-
See [here](https://mathewsachin.github.io/Captura/donate).
32
-
33
-
[paypal]: https://www.paypal.me/MathewSachin
1
+
See [here](https://mathewsachin.github.io/Captura/contributing).
@@ -87,7 +87,7 @@ Dev builds can be unstable and should be used for testing purposes only.
87
87
88
88
-[Visual Studio 2017](https://visualstudio.com) or greater is recommended. Can also be built using Visual Studio 2015 using [Microsoft.Net.Compilers](https://www.nuget.org/packages/Microsoft.Net.Compilers) nuget package to support compilation of C# 7.
89
89
- .Net Framework v4.6.1 is required.
90
-
- For detailed information, see [Building](docs/Building.md).
90
+
- For detailed information, see [Building](https://mathewsachin.github.io/Captura/build).
-[Visual Studio 2017](https://visualstudio.com) or greater is recommended. Can also be built using Visual Studio 2015 using [Microsoft.Net.Compilers](https://www.nuget.org/packages/Microsoft.Net.Compilers) nuget package to support compilation of C# 7.
6
-
- .Net Framework v4.6.1 is required.
7
-
8
-
## Api Keys
9
-
10
-
Api Keys are loaded from user environment variables during development and embedded in Release builds if using Cake.
11
-
12
-
Service | Environment Variable
13
-
--------|----------------------
14
-
Imgur | `imgur_client_id`
15
-
16
-
## FFMpeg
17
-
18
-
FFMpeg can be downloaded from within the app.
19
-
20
-
## Building using Cake
21
-
22
-
We use Cake (C# Make) to automate the build process.
23
-
24
-
To do a Release build, open powershell in project folder and type: `./build.ps1`.
25
-
26
-
The build is then available in the `Output` folder.
27
-
28
-
### Options Supported by build script
29
-
30
-
Option | Description
31
-
-----------------|-------------
32
-
`-version` | Build version. `AssemblyInfo.cs` files are updated with this value during build.
33
-
`-configuration` | Configuration: *Release* or *Debug*
34
-
`-target` | The Task to run in the build script. See `build.cake`
35
-
36
-
e.g. `./build.ps1 -target "Pack-Setup" -version 5.6.0`
37
-
38
-
## Building Manually
39
-
40
-
Some extra things that need to be done when building manually.
41
-
42
-
### NuGet
43
-
44
-
Restore NuGet packages.
45
-
46
-
### Audio
47
-
48
-
Download [BASS Audio library](http://www.un4seen.com/download.php?bass24) and [BASSmix](http://www.un4seen.com/download.php?bassmix24).
49
-
50
-
`bass.dll` and `bassmix.dll` (x86 versions, since Capture runs in `Prefer32Bit` mode) need to be placed in the same directory as `Captura.exe`.
1
+
See [here](https://mathewsachin.github.io/Captura/build).
0 commit comments