For those of you using git - I just commited p46 with a working autoimporter. One little issue is that it freezes the interface (ie. you have to kill it) - does anyone know how to fix that? In the meantime just open fpdb a second time to use the table viewer or whatever. Since the table viewer will be obseleted soon I won't update it to use the auto importer.
Also note that I made more table changes based on feedback from ray in particular for use by HUDs in the last few commits.
Oh, and I changed the naming from alphaX gitY to alphaX pY to match Gentoo's rules.
For those of you not using git - Don't worry, alpha2 will be out shortly
Quote:
Originally Posted by _dave_
well, the "clone" command worked and now I've got a git / fpdb tree in my home folder.
I'm kinda unclear on "make your changes" - I just edit the fies direct from my local tree, and git will figure out what has changed / allow me to revert / create a new "revert point"?
I'm gonna read some git tutorials tomorrow, and play about - I think I've read enough python docs to be dangerous now
Fozzy - this git stuff is cool - you guys could possibly get great benefit running it for version control / backup of all your mods, if it deals with PSD / 3ds as easily as .py files
Yep, you can just edit the files with whatever you want. I use nedit and occasionally Eclipse but anythin will do.
You can use git-diff to show you what changes you made since the last commit (or between past commits - even between past commits by other people ie. me).
There are also ways to use git to create a kind of patchset to email but I'm not sure how. In any case, the best way is to just get your own public repository at that URL i mentioned (or anywhere else) and drop me a line when you pushed something I should add to the main tree.
Note that you do NOT need to be online to make a commit, that happens locally. You can do one or more commits, and then you have to be only to push it to your public tree. In other words, the commit creates your "revert point", and the push publishes your changes to your public git tree. I believe this is the "default" way of using git.
Git is great, my housemate even started using it for his one-off single-person coursework. Another useful thing about is that (unlike svn) it guarantees file integrity. It will handle any text-based format like python, but it will also take binary files (this includes things like gif or jpeg). I'm not sure how effective it is with them though, obviously many features that are useful for normal files are useless on binaries.