jacksonmj's fork
-
This is a continuation of TPT, and is planned to be (mostly) compatible with TPT++.
Since I am not yet entirely convinced by the official C++ rewrite of Powder Toy (TPT++), I will be doing my own more gradual conversion to C++. Some bits of TPT++ may make their way into it though, once I believe them to be bug free and sensible. No new elements will be added, except those added to the official version. Bugs should be reported in this thread, unless they also exist in the official version.
At the moment, there is no native mac version, because I haven't yet worked out how to cross compile for mac on linux and have no way of testing it. You may be able to run the windows version on a mac using wine.Downloads
Latest version: 84.1, updated 11/11/2012
Linux 32 bit
Windows 32 bit
SourceChanges
- 15/11/2012 Element properties are stored in a similar way to TPT++ (still a work in progress, but coming along nicely - in a separate branch "tptgpp-elements" on github at the moment).
- 12/11/2012 The build system uses CMake. It has been tested with native compiling on Linux, cross compiling for Windows on Linux, and compiling for Windows using MinGW+MSYS in Wine. Please test it and report any problems. Hopefully, it should be able to generate Visual Studio and Code::Blocks project files too, but that hasn't been tested. It may even work on a Mac...
-
bump. Since apparently jacksonmj hasn't. Yay for complete VIBRanium.
@jacksonmj (View Post)
I see you made a converter to convert elements from tpt to tpt++. Is it ok if I compile it sometime for windows (and post a link)? Or were you planning on doing that yourself sometime, when it's finished if it isn't already. I haven't tested it yet. I will probably compile it anyway someday for when I make my tpt++ mod. -
It's not quite the same format as TPT++, but you could adapt it to TPT++ (renaming some of the properties, adding TPT-Directives, etc).
My plan does not involve using a separate class for each element like TPT++. Adding a new element will involve adding one line to a header file (of the form "DEFINE_ELEMENT(THING, 111)"), and an element file. Adding the new line to the header file will cause a full recompile, but update functions and graphics functions can then be added without a full recompile. No TPT-Directives or programs like generator.py will be needed.
If you want to adapt it to TPT++, then go ahead. But if following this fork, don't convert any elements yet, since there will be a few minor changes.
-
whats the difference between c++ & c# [sharp]?
-
I thought this was a powder fork bomb..... Don't know how that's supposed to work but...
-
-
i thought this was about forks like kitchen forks but its about scripting forks which i cant understand what this is supposed be about
-
Necro. Last post was over 2 years ago. Google 'what are forks in programming'.
-
@QuanTech (View Post)
Not to be mean or anything, but answering people's questions by telling them to use google is really annoying for the person asking the question. It's like you are not willing to help or anything, which is not what forums are supposed to be for. Instead, answer their question and you could say nicely at the end of your post that google can be used to get answers to so many questions easily, if that person keeps asking more questions that can be easily searched for :)@CALVIN1390 (View Post)
So there is this thing called a source code, it's the thing with all the files and codes necessary to make a program. Forking the source code means duplicating it so that the developers could experiment on the duplicate instead of the main source code, after they finish, they could merge the fork with the main one if they want, or they could release it as a separate program (just like TPT mods, they are modified forks of the main game).For example, if you had a sheet of paper with useful things you want to keep, but you want to experiment with it, you wouldn't modify it directly, which could mess it up permanently, instead, you would print a copy of it (like forking it) and then do your experiments on the copy instead of the original sheet of paper.
- An example of a source code: TPT's source code
- An example of a fork: jacksonmj's tpt rewrite
Also yeah, necroing (bringing old and dead threads back to life) is bad, unless it's for posting something useful or a serious question.Edited once by Mrprocom. Last: 1st Jan 2017 -
I don't wanna say something bad, Procom, but, in my opinion, he is a thollz.
Answer here: is he a troll, or not? (oops, onclick ain't work)
Edited once by TPT_PL. Last: 2nd Jan 2017
