Tree [4cbdf0] master /
History



File Date Author Commit
Configs 2012-10-26 dak180 dak180 [4cbdf0] Use the latest version of autorevision.
English.lproj 2011-04-26 David Burnett David Burnett [285bb5] Merge branch 'topic/buildupdate' of https://git...
OxidizerQTDialogServer 2011-04-26 David Burnett David Burnett [285bb5] Merge branch 'topic/buildupdate' of https://git...
Resources 2011-09-19 dak180 dak180 [75ac98] Merge commit '536fa410242a89883e405e85a831caee5...
ThirdParty 2012-09-13 David Burnett David Burnett [f49721] update flam3, png and zlib libraries
oxidizer.xcodeproj 2012-10-26 dak180 dak180 [4cbdf0] Use the latest version of autorevision.
src 2011-10-16 David Burnett David Burnett [2120a3] Debug conversion of symmetry knid to numeric fo...
test_scripts 2010-11-06 vargol vargol [e299e6] *** empty log message ***
.cvsignore 2006-02-11 vargol vargol [6e2c64] Guards around open filename handling
.gitignore 2011-09-19 dak180 dak180 [75ac98] Merge commit '536fa410242a89883e405e85a831caee5...
COPYING.txt 2006-02-09 vargol vargol [93520b] Initial Release
NOTE.txt 2011-04-26 David Burnett David Burnett [285bb5] Merge branch 'topic/buildupdate' of https://git...
README.txt 2011-04-26 David Burnett David Burnett [285bb5] Merge branch 'topic/buildupdate' of https://git...

Read Me

Oxidizer - fractal flames for OSX.

Getting oxidizer from git.

Getting Oxidizer from git is easy.

Start Terminal.
Go to or make a folder where you want to put Oxidizer, say ~/Source

cd ~/Source

type the following command then press enter 
git clone git://oxidizer.git.sourceforge.net/gitroot/oxidizer/oxidizer
 
and a few seconds later you should get a folder called oxidizer in the Source folder.

If these instructions do not work check Sourceforge's version at 
https://sourceforge.net/apps/trac/sourceforge/wiki/Git

Open the project in XCode 3.2.X and compile.



To keep the git repository up to date use the following command from the oxidizer folder
created by git...

git fetch origin

This will update the repository, but you will still need to update your working copy to see the changes.

New commits to git are generally announced on the developers blog at

http://www.vargolsoft.net