Do this a minute Jason; Go to my repo of your version of Squire 3 and tell me you cant easily see the exact changes you made after the first "release" when you fixed a few things.
Actually I can't, because the UI for shithub is worse than most GUI wrappers for git. I can't find a damned thing in it as it's one of the most counterintuitive interfaces ever.
Again, I suspect the problem is much akin to my issue with RAD's. There's some sort of disconnect between my workflow and how I do things, and how it works.
And once I start setting milestones -- this code is FAR too "in flux" for that yet -- it's called "diff". You ever use "diff" or under DOS/Windows "fc"? If one REALLY needs that sort of thing there's gui tools for doing it too. NOT that it's something I usually if ever need or would want or have seen anyone have a need for at THIS stage of it. You actually have to finish writing the starting code before things like diff matters.
I'm also used to the "need" for tools like that indicating there's a problem with the entire development process.
Though I think that's a complexity mismatch between how you and I do things, and the complete misunderstanding of what you were even asking in the initial thread. I went back and re-read and I still don't get where at the start you said what you later explained; your "clear intent" as you said being utter murk for me.
The fact people are jumping the gun because they didn't understand what was Squire and what was not certainly not helping matters, much less usually when I use the part that's ACTUALLY squire it's customized or adjusted on a per client basis. (again why I uploaded that new standalone squire.lib.php to make it clear what is squire and what is not!)
It's almost like we're talking two different languages, but as I said before I think our entire process of doing things is 180 degrees from each-other. A LOT
of what you've said and claimed is utter gibberish to me.
Click on the zip down load and tell me how hard it was to download a zip file of the code.
Was one of the first things I had to ASK how to do, because I couldn't flipping find it because a NEAR INVISIBLE white-on-green down arrow pointing at a line with the word "code" next to it doesn't make me think the download link is going to be in a dropdown.
One might think they were using the broken halfwit inaccessible trash framework known as "primer", which much like bootcrap and tailwind tells users like myself to go F*** ourselves with their nonexistent
accessibility and usability. It's very hard to be friendly to something that's tells me I don't count as a user on those grounds.
Right click on a line of code and tell me how hard it was to create an issue with a direct link to that exact spot in code.
You mean the broken shit "..." to the side where the menu is half off the blasted screen because they scripttarded it badly so it doesn't scale on large-font systems? Lemme guess, I'm supposed to set my 1440p display to 16px fonts and plaster my face 2" from it? F*** that.
Your "problem" with git is blinding you to many of the very simple benefits of using it.
Once again I feel like John Adams when Dickinson talked about the "benefits" of being part of England.
John Dickinson: For myself, I have no objection of all to being part of the greatest empire on Earth, to enjoying its protections and sharing its benefits.
John Adams: Benefits? What benefits? Crippling taxes? Cruel repressions? Abolished rights?
John Dickinson: Is that all England means to you, sir? Is that all the pride and affection you can muster for the nation that bore you?
"The difference between patriotism and nationalism is that the patriot is proud of his country for what it does, and the nationalist is proud of his country no matter what it does.” -- Sydney J. Harris
As such when people talk about the "benefits of Git"? Benefits? What benefits?
Slowed development? Extra pointless time-wasting steps? Task complexity mismatch? Dicking around with crap that you really SHOULDN'T need in the first blasted place?!?