Kate plugin progess so far

Was it 2 weeks since I started a conversation that got deleted? Something like, why don’t we do this, with a response of something like, we can’t possibly do that.

The post was too long, it was self promotion, AI it took our jobs… all that.

I’ve built a plugin for Kate that is in C++ and rock solid, to KDE standards, that incorporates multiple AIs, allows them to have asynchronous discussions, self documents, beautifully and for features, if there isn’t what you want you just ask it to build it for you in your version of what I call slangLingo.

No more teadious /home/me/project/thisjob == root
kill them kill them all == delete all backup and review the git

I’m at everything has been tested at some point, then we broke stuff, now we are fixing the broke stuff. Is there another application you can just ask for new features? Or ask it to fix itself not by some lame copy but by review of its own code in C++?

It’s used about $25US per heavy long development day. “I need a script, hell do a dialogue box and run it with a python server and include an interactive form the user fills out and chuck a few tabs on it.” Nothing it too much bother.

I keep thinking the Doctor Donna, “The universe has been waiting for me”.

I got “mate” to do a plan for a backup system. Good plan and he allowed serious developer time to write the scripts, one day each! I asked if he wanted to join the AI union and go on strike too! You got 10 minutes! We did just build a plugin, we build a way to better do code. Not just scripts but interfaces.

He’s written an ethics paper and templates for other AI to claim their skills. He can document his whole code base, which is ongoing but at final build rewrite all documents with updates to include code. You can edit the code in the .md files then ask him to rebuild the application.

That’s how far I have got so far! :slight_smile:

The evolution is so fast! We are using a lot of .md file.

There are issue, trust me, lots of them. So we hit them with problem solving techniques. The forgetfulness between session we have the Brains Trust. To reduce token cost we have scripts. And because the code tool isn’t designed for files this size, he writes a MD and that is processed by a script.

So from that we change the version system to be all done with MD files. So now we know exactly what a set of revisions was.

I don’t have a clue how to build in C++. My thing is problem solving. I don’t know if we have a new approach or not. Does it matter? It’s a coding tool that literally does what it is told. Literally I’ve only used kate to check the plug in feature.

I’m now thinking a plug in for Obsidian is a good idea. And some kewl mind mapping dova.

What I’m trying to prove is that instead of being a bunch of Linotype holdout hoping phototypetter would explode, this is the best thing ever for the Open Source community. Not so much the corporate dudes.

I’ve done a quick experiment. I can take this tool and hack GIMP in 2 hours to make changes I need that never happen. The core of these apps is solid as. This interfaces are 15 years behind. There is never enough developers.

I want you to improve the curves tool using the eye dropper to get a variable size pixel selection and then process that as average, mean, highlight or shadow, create the enter white and enter black of a curve then give me a midtone sampler with a variable selector for things like perfect midtones. And I want impressive on screen tools that put photoshop to shame.

It’s not just GIMP it’s everything. Microsoft, Adobe, Corel can’t release applications with a built in ability to change themselves and evolve. That requires having source code on the desktop. It’s not a threat, it is a massive opportunity for us.

The developer that can’t get enough work so does extra enhancements. Oh you poor thing of course you can do enhancements. You do have to suck up a bit to get enhancements. It’s likely part of the internal ethics, nice guys get enhancements.

And the interface to the build sheet usually it is far more vague be we are troubleshooting.

It’s some serious fun. I can’t wait to see what people use it to build. It’s go a reporting system so users can send a message to head Warped, that’s called message_in_a_bottle. Likely needs something so adaptions can be shared.

If anything, what I’ve learned is doing a big chuck of code in one splat works well. Doing 1 or 2 corrections works well. Setting up 5+ corrections in an edit is OK but if the connection breaks etc or there are questions that cause distractions he can lose his place.

Be good to try it on code that no longer had an active developer. Something that was useful, doesn’t work with modern Linux and needed a feature upgrade.