http://forum.cubers.net/
Tue, 03 Mar 2015 22:33:45 +0000MyBBhttp://forum.cubers.net/thread-7932.html
Tue, 02 Dec 2014 17:34:55 +0000http://forum.cubers.net/thread-7932.htmlhttps://github.com/ac-stef/AC/commits/mapformat10 I see that the restriction on mapmodel will be removed. How about the clip entities? they will be rotate on all directions as well or..? Because there's some mapmodels that are hard to clip. Clips should rotate as well.

Also, how about the geometry? Can be implemented the "grab geometry" before paste? I mean, when you select and then copy, would be great to move the copied geometry, ex; CRTL + ALT + G (just press, not hold) then move the mouse and when there's no "geo colissions" you can paste it with a single mouse right click.

and the fog glitch. would be great if we can set the fog without seeing that glitch.

http://youtu.be/DtLyZh2V5F8]]>https://github.com/ac-stef/AC/commits/mapformat10 I see that the restriction on mapmodel will be removed. How about the clip entities? they will be rotate on all directions as well or..? Because there's some mapmodels that are hard to clip. Clips should rotate as well.

Also, how about the geometry? Can be implemented the "grab geometry" before paste? I mean, when you select and then copy, would be great to move the copied geometry, ex; CRTL + ALT + G (just press, not hold) then move the mouse and when there's no "geo colissions" you can paste it with a single mouse right click.

and the fog glitch. would be great if we can set the fog without seeing that glitch.

(From time to time we introduce new branches to develop new major features.)

Github has instructions and tutorials on how to clone the repository. There are also a number of forked repositories hosted on github, where some coders commit their own contributions (for everyone to check out) and also most devs, who may use their forks to prepare and test bigger changes. For example, here's a branch on my fork with some changes to the map file format: https://github.com/ac-stef/AC/commits/mapformat10
Once you've cloned the main repository, it is easy to add forked repositories as remote sources in your local setup. This allows you to keep track of any number of forked versions of AC.

PS: pls only post to this thread to report test results or questions related to code testing. Offtopic posts will be deleted.]]>https://github.com/assaultcube/AC

We develop in two main branches, "master" and "next":

master should contain only minor changes and fixes and should be compatible with the latest release version. In general, the master branch is the codebase for minor releases, for example 1.2.0.3.

(From time to time we introduce new branches to develop new major features.)

Github has instructions and tutorials on how to clone the repository. There are also a number of forked repositories hosted on github, where some coders commit their own contributions (for everyone to check out) and also most devs, who may use their forks to prepare and test bigger changes. For example, here's a branch on my fork with some changes to the map file format: https://github.com/ac-stef/AC/commits/mapformat10
Once you've cloned the main repository, it is easy to add forked repositories as remote sources in your local setup. This allows you to keep track of any number of forked versions of AC.

If you want to help to develop and test the next version of AC, you should get yourself a "build environment". The main parts of that are a compiler and a git client. With it, you can get the newest code versions (from the official AC repository and from any forked version) and compile and test them yourself. If you are capable of coding, you will also have everything at hand, that you need to contribute code to the project.

What you need:

* a compiler (or better, a full IDE with editor, compiler and debugger)
* some development libraries, depending on your platform
* a git client and a clone of the official AC repository (from github)

You only need a github account, if you want to contribute code directly. If you only want to help testing, you don't need to sign up on github. You certainly don't need to create a fork of AC on github unless you want to contribute a lot of code. Single commits can easily be contributed by email or IRC+filehoster.

If you need help: there should be several tutorials around somewhere from our SVN days on sourceforge. Those still apply, except that we use git (and github) now. If you need more help: asking on IRC is probably the best way. We will put together more documentation as we go (for example: what to do, once you have compiler + git client installed).

It would be nice, if the first few who set up their build environment would document the required steps and post them here...

PS: please be aware, that off-topic posts will be deleted here. We have plenty of other threads, if you just want to bitch about stuff.
PPS: I'll make a second thread to discuss the actual testing of new features - this thread is only about the setup of build environments.]]>
Soooooo...

If you want to help to develop and test the next version of AC, you should get yourself a "build environment". The main parts of that are a compiler and a git client. With it, you can get the newest code versions (from the official AC repository and from any forked version) and compile and test them yourself. If you are capable of coding, you will also have everything at hand, that you need to contribute code to the project.

What you need:

* a compiler (or better, a full IDE with editor, compiler and debugger)
* some development libraries, depending on your platform
* a git client and a clone of the official AC repository (from github)

You only need a github account, if you want to contribute code directly. If you only want to help testing, you don't need to sign up on github. You certainly don't need to create a fork of AC on github unless you want to contribute a lot of code. Single commits can easily be contributed by email or IRC+filehoster.

If you need help: there should be several tutorials around somewhere from our SVN days on sourceforge. Those still apply, except that we use git (and github) now. If you need more help: asking on IRC is probably the best way. We will put together more documentation as we go (for example: what to do, once you have compiler + git client installed).

It would be nice, if the first few who set up their build environment would document the required steps and post them here...

PS: please be aware, that off-topic posts will be deleted here. We have plenty of other threads, if you just want to bitch about stuff.
PPS: I'll make a second thread to discuss the actual testing of new features - this thread is only about the setup of build environments.]]>http://forum.cubers.net/thread-7872.html
Mon, 20 Oct 2014 09:09:32 +0000http://forum.cubers.net/thread-7872.html
Thank you for everything, grenadier, past and future.]]>
Thank you for everything, grenadier, past and future.]]>http://forum.cubers.net/thread-7669.html
Wed, 11 Jun 2014 11:05:39 +0000http://forum.cubers.net/thread-7669.html