Tim Nelson

I was likewise reading the prompts directory, and thought the same thing, but with the following variations: # AgentRoles AgentRoles should be made (equivalent to the current Agents). They have...

As a side thing, I'd like to see most of function_calls.py turned into .yml files (to make the easy things easier, and to enable better separation of code and data).

According to my scheme, we'd end up with something like the following (note: I'm not yet familiar enough with the code to be sure what to do with all the...

Might want to adjust that README so that you have: * Development.md: For developers * README.md: For people who just want to use the software * Installation.md: If there are...

Note that the wiring diagram idea would also be useful for representing workflows/processes; this would be useful for: - If someone makes a ticketing system, and wants to move tickets...

Sure, agreed; another possibility is maxGraph ( https://github.com/maxGraph/maxGraph ). It's less tailor-made for this purpose, but might be better if it were also deemed useful to have eg. class diagrams...

cf. also https://github.com/saltcorn/saltcorn/issues/2050

As a bonus, this might make it easier to work with PostgREST and Postgraphile.

Thanks! Hopefully I'll get to this eventually. My goal is to hook jsonforms-editor ( https://jsonforms-editor.netlify.app/ ) to this, and hopefully, I'll be able to add queries to Postgres, and forms...

Hi gramian, Thanks for the reply! - Good point about the available HTTP API not having a semantic layer; this is what PostgREST+OpenAPI offers -- automatic generation of the semantic...