many big changes in this commit
Apr 16, 2024 0:36:42 GMT -8
Post by Uncle Buddy on Apr 16, 2024 0:36:42 GMT -8
The path has changed since "gps" is no longer used in the app name. instead of <drive>/treebard_gps/... we're now using <drive>/treebard/... In other words, the main directory is now called treebard, not treebard_gps.
You don't have to copy the modules one at a time from this repo anymore, when I am simultaneously planning to put out an .exe. The .zip containing the .exe, which will be made available soon on the website, also contains all the code.
This is one of those times when an .exe will be made available, maybe today or tomorrow.
If it so happens that the .exe doesn't work for you, the code is in the .zip so you can just install Python and use the code that way. Complete instructions are on the YouTube channel for doing all the installations. It is very easy.
However, when I make small commits where just a few modules change, I will not put out a new .exe every time that happens. In a case like that, you will want to copy the changed modules from here if you're trying to keep your Treebard code base up to date.
And then again, if you're trying to use Treebard as a genealogist for doing your daily work, I don't recommend it unless you like to do a lot of manual updating. That's not what Treebard is for, at least not yet. Currently Treebard is a working model for developers to use for anything they want. There are no versions, no backward compatibility, so use Treebard for testing, modeling, inspiration, playing around, but don't do your serious work in Treebard and if you do, then don't update it when new code comes out or your tree will be broken.
You don't have to copy the modules one at a time from this repo anymore, when I am simultaneously planning to put out an .exe. The .zip containing the .exe, which will be made available soon on the website, also contains all the code.
This is one of those times when an .exe will be made available, maybe today or tomorrow.
If it so happens that the .exe doesn't work for you, the code is in the .zip so you can just install Python and use the code that way. Complete instructions are on the YouTube channel for doing all the installations. It is very easy.
However, when I make small commits where just a few modules change, I will not put out a new .exe every time that happens. In a case like that, you will want to copy the changed modules from here if you're trying to keep your Treebard code base up to date.
And then again, if you're trying to use Treebard as a genealogist for doing your daily work, I don't recommend it unless you like to do a lot of manual updating. That's not what Treebard is for, at least not yet. Currently Treebard is a working model for developers to use for anything they want. There are no versions, no backward compatibility, so use Treebard for testing, modeling, inspiration, playing around, but don't do your serious work in Treebard and if you do, then don't update it when new code comes out or your tree will be broken.