|
Post by Uncle Buddy on Sept 20, 2022 20:50:02 GMT -8
I just pushed the branch `assertions_tab` to the github repository. I wrote the assertions tab feature with the camera running, resulting in a series of 204 videos along the theme of "I'm no programmer, so if I can do it, you can do it better". This feature is the climactic end goal of Chapter One of Treebard Development, a 50-month-long full-time project. While working in this branch I had to create other features, dialogs and rewrite some features: --repository dialog was created from scratch --names tab now has the ability to create new names for an existing person (add person dialog has existed for a long time but currently needs a rewrite) --edit source/citations dialog took a lot of time but was abandoned as an edge case that I'd tried to handle in the wrong place --rewrote places dialog and vastly improved the database structure for storing nested places --rewrote parts of the notes dialog --whatever else I forgot Also I've created a playlist for the video channel since rumble.com doesn't have playlists yet.
|
|
|
Post by Uncle Buddy on Oct 22, 2022 5:13:16 GMT -8
I made a commit just now which includes Treebard's New Look as shown in the new Treebard Tour Part 8 video[/a] that I'm uploading to Rumble.com right now. Also included in this commit is the rewrite of the Gallery class. The source image gallery and place gallery are now in dialogs opened by clicking a big button with a thumbnail on it, same as the person gallery has always worked. A few tiny changes were made to the sample tree database structure which are not yet reflected in the flat importable .sql files. The new video page at the website is a playlist of my rumble.com videos which is better organized than the list at rumble.
|
|
|
Post by Uncle Buddy on Nov 8, 2022 1:07:59 GMT -8
Today's commit includes a new feature for adding the new person's images from any directory on your computer. Multiple images can be added at once (if the originals are all in the same folder) using the normal Windows file-explorer-like dialog that comes with Tkinter. Each image copied to the Treebard project folder can be resized at the same time, each to an individual degree, with 100% (no resizing) selected by default. The originals are not moved or altered in any way.
The next step will be to make it possible to add images to a person that already exists, and to unlink images from a person. It will also be possible to link images to places, sources and ? This should be done now too, before I get back to what I was doing, which is a new video series making a new tree from scratch, "Great Lakes Heatons". There's one video done for this series (but not uploaded yet) and I'm taking a break to write these image-related features and have a nervous breakdown while my house is being renovated and painted.
|
|
|
Post by Uncle Buddy on Nov 23, 2022 4:46:49 GMT -8
Tonight I pushed a commit to the public repo but made a mistake, I deleted the branch before merging it. I will probably be able to recover the repo and get it back on track. Another option, to save time, would be to delete the repo and just push the current app as it now stands as a new repo. This would eliminate all past commits, which would hurt me just about as much as when I deleted my Facebook account a while back: not at all. One person forked it but hasn't made any commits, so I don't think it would hurt anyone else either. This makes me think, wonder, and cogitate upon whether version control is right for me. I don't really see the point, since I'm a one-man team. I could post all the code at treebard.com and renew it from time to time. It would be better for me, because I would not have to wade through memorized/dictated but not understood or helpful git commands and messages to accomplish something that is irrelevant to me. It's easy to share computer files without wading through gobble-de-goop, it could easily be done through dropbox, and what the heck, most of it's just text files, right? So most of it could be shared through email attachments and I could just share the images via Dropbox, for sample trees, so everything would work. I won't admit to being discouraged that no one has come forward to pound me on the back and congratulate me on the grandeur that is Treebard. I need a team of Treebard hacksters about as bad as I needed a Facebook account: not at all. Do not interpret this as unfriendliness. I just have no reason to work with a team and I don't think a team has a reason to work with me. The purpose of Treebard is to demonstrate useful and hopefully superior genieware functionalities, and to inspire genealogists to write their own code. By "genealogists" I don't mean "programmers", I mean "genealogists". The Python/SQLite/Tkinter combo is truly inspirational, it makes you able to accomplish this. And then along comes git. Well I don't see the reason for me making things hard on myself. I'm just the creator of Treebard. You and your team of genealogists should write your own genieware, based on Treebard or just inspired by Treebard or whatever, and you (since you have a team) should have your own repo at Github and don't include me in that. There are aspects of programming that will never interest me. However, before doing anything drastic, I will do a little more research on whether an unmerged-but-deleted branch can be recovered with a reasonable amount of effort. I will also post something tonight about recent additions to Treebard, as I've been very busy on the project recently and really enjoying being able to work on some new features.
|
|
|
Post by Uncle Buddy on Nov 23, 2022 22:16:33 GMT -8
The new repo is here: github.com/ProfessorUdGuru/treebard_gps_2022It's only a README and the Unlicense. The old repo will be deleted if I do in fact decide to keep the code on my website instead of Github. If not, I'll push the whole app as is to the new repo and delete the old one. Seeing how much time it takes from productive work for me to use Github (i.e. pretend to be a team of programmers), I hope I have the sense to stop pushing commits to Github and just FTP them to my website whenever new features are finished. Sorta think I'll get on that new REPO web page right away, before writing more Treebard code. I pay for the website, might as well use it instead of falling for the free services like Github which tend to be a huge waste of time for a little fella like me. But first maybe I'll take a shower, eat some cheese and watch Tucker Carlson's latest rant on utube. What's really calling to me, of course, is that new video series I've started but not posted yet at Rumble.com. "Using Treebard" to create a new tree from scratch. This series will be a long time getting made, because when I bump into something I need to do in Treebard that Treebard can't do yet, then that is the next feature that gets written before the series of videos can proceed. That's what's going on right now.
|
|
|
Post by Uncle Buddy on Nov 24, 2022 2:01:08 GMT -8
I forgot about Python's little indentation problem. This isn't going to be as easy as I thought. No doubt it has been done though. Someone probably has already written a tool that converts a Python file to html with indentation for display on a website. The indentation also has to be preserved when someone copies and pastes the text to their code editor. See what happens when you make a mistake pushing commits to Github? Might have to learn something. It might be easier to keep using Github.
I could just put the code on this blog like I used to. It preserves the code editor's formatting when I paste it in. I was hoping to put it on my website but it would be 100 times easier to just post the code here. However I have no control over whether this website disappears, cancels me for having green skin, or whatever. It seems I need to display a mock code editor or something on a web page, not a real one that can be typed into.
|
|
|
Post by Uncle Buddy on Nov 24, 2022 2:29:31 GMT -8
wordtohtml.net/site/index?tinyeditor converts text to html, displays it well, and it can be copied from the resulting web page and pasted into a Python document. It looks good but unfortunately the end product has had unwanted non-printing characters added to it. This could be cleaned up but I'm looking for something that's easy as playing in the mud. Don't suppose I'll find it. Maybe I'll just go play in the mud.
|
|
|
Post by Uncle Buddy on Nov 24, 2022 2:45:15 GMT -8
I tested a Python file by pasting it into a new post here on the forum, then copying the text from the post and pasting it into my editor. It looks and runs fine, no added illegal characters. I'll just post all my code here, deleting the old versions when they're superceded since there's no reason to keep track of old junk (except for the many backups of everything that I keep on my computer, external hard drive, and USB drive).
I will add a page to my website that will have links to every file in Treebard in a way that reflects the file structure of the app, since the menu in this blog isn't set up for navigating that sort of thing. It will be very easy to do. I will not use Github if I don't have to. Github is for programmers. Treebard is for genealogists who want to write their own app without becoming expert programmers.
|
|
|
Post by Uncle Buddy on Nov 26, 2022 5:16:55 GMT -8
|
|