Just save a project you have to xml format and then provide it to AI (the latest chatGPT4 o4 is fantastic for code).
No need to add any text. It will give you full report of the project. Including things you could improve, optimise or do differently - including code to do so.
Even suggestions to add features (and of course can provide code for this too).
Yes, it sometimes mixes API1 and 2 but this is easy to fix (even by asking it).
It’s all copy/paste/create UI controls/… now. It would be fantastic if this implemented in the IDE.
Just take a look at how it is implemented in Xcode!
Well, it wouldn’t be the first time I was wrong about something.
Nevertheless, I’ll hang onto my critical thinking skills for as long as I’m capable and hope that if Xojo Inc. does incorporate direct AI features into the IDE - that it has an “off” switch. Otherwise, it’s adiós mis amigos.
I really want the ability to turn GPT or other models loose on my entire code base if I choose. I want to be able to ask AI about a bug in particular source code without the need to export that source code and take it to an external web page to use AI. I want to be able to ask questions of AI about my code base and the AI have all the context it needs because it has access to the source. This is already possible and works incredibly well on certain tasks in other IDE’s. It currently makes my mandatory-work time in Xojo feel antiquated when I switch over from VSCode or Cursor.. I definitely vote in favor of bringing AI into Xojo in meaningful ways, not just auto completers’..
I’m really surprised that no one has done this with IDE automation yet. You can easily get the source of the current editor and set it later. The IDE Communicator socket would be an easy way to connect.
I have great respect for you and don’t mean to sound rude, but perhaps it’s because no one here is convinced that the current capabilities of the Xojo IDE API offer what would be necessary to even come close to what, for example, the Xcode Editor offers. And the Xcode Editor only offers the bare minimum when it comes to predictive coding.
Hacking something that should be a basic functionality is kind of a waste of time, it is easier to use that time porting to another tool. Also, a hack can be broken on the very next release