An Icicle Department Company

So, once upon a time, several ages ago, I started learning blender. This led to me being introduced to python, finally, after having been told about it by nsane back in 1997, as THE LANGUAGE I SHOULD LEARN.

Since, at the time of my introduction to python, I hadn’t actually learned it, I stopped doing much with blender and instead explored the world of python, revolving around blender mainly as an ide, with built-in data-displayer.
At that time, blender was on version 2.48, and I learnt the heck out of that python as well as I could, which warn’t much, I reckon, but at least I was usin` __init__’s and __call__’s…

…never could figure out those __new__ things until I was older, though. Them __new__ things is @classmethods not regular ones, and I kindly shied away from big words I dudn’t understand. But i knew what go __init__ and i knew how to __call__ it was however i seen most fit-like at the time.

Back on track: There was this semi-tedious process involving setting up all the callbacks for all the buttons and stuff that you was gonna do. You usually ended up making a big old whole long list of actual numbers, for gods sake, and then you had to give them names. or more like give them TO names. but it was like you handed out tickets to all the stuff and that was that. That was nothing.

Then there was the chore. Every dadgum sucker-pluckin thing had to have corners. two of em was enough but you had to put them exactly where you wanted them, so now you got two piles of numbers, callbacks and corners.

AND, well that was freakin IT and it WAS OK.

I am not the best coder by a long freaking shot, but even I had myself an automagic Abstract-Syntax Tree, Recursively-Self-Parsed, Dynamically-Reconfigurable User-Interface-Generating-Based_on_FuncTools-Decorated-Introspective-Macro-Recording-Topology-Mapping-Keyframable-READ_EVAL_PRINT-loop-to-tty-Alternating-Row-Major-Modulo-Nested-ness-Hotkeys-from-docstringsTURINGCOMPLETEABILITYTOSELFREPLICATETOUTF8 everything.

I’m just saying, here i am struggling to get goat turds out of the 2.5 api, and then i go thinking wonder what they have in under the hood and i find bpyml.py and bpyml_ui.py and i am astonished. It has never been mentioned but its right there, and its the functional IDEAL to my project that i just essentially wasted half of half a year trying to do. And it was probably there all along. Which brings me to my major grip of the day/minute/now:
Where is the actual source for all of this information?
Why I do beee-leev that they have not edited much of their home page for shit in a very long time and it is like a vast catacomb of outdated information, interspersed with totally up-to-date stuff that seems to be linked to from nowhere.
I just wish i could help, really. I mean, its ok, but is it too much to ask that at least some of the 2.39 era stuff be removed? I swear. SMH
Its totally just strewn about stuff like architectural roadmaps and api diagrams that are not at all helpful.
The programming thing is a wierd maze to make it into the current manual from the homepage i have to lead myself to the somewheres else i know wont have it but links to a page with an out of date analogue which i then change the digit 7 to an eight and bookmark immediately. There is no other way i am aware of to get there on that website, starting at the homepage.
And now we have a bazillion things more it seems like, to worry about when coding *just the ui* but i guess im happy with it, its just that i was pretty happy before and now that i finally have a declarative way to build the ui, i have not one but two options at my disposal, which is incomplete in its robustion quotient but i at least feel like *i* •_• made it up, or i can use the secret-not-so-secret one hidden in there and have some sort of compatibility factor- which i dig also. So Im going to sleep pretty hopeful this morning, to wake up drag in some actual functionality and not give myself too much of a headache due to the fact that template_color_ramp is never going to accept any data or property i give it, no matter how many times I read the manual.