DearPy3D VS gradio

Dear PyGui is awesome and supports creating node editors. 3D is not really supported yet (although matrix functions are), but future versions will support 3D. The core developers are very much interested in 3D rendering. As a little test, Hoffstadt created DearPy3D. He is currently working on Pilotlight, which is still early stages and eventually will be the core of Dear PyGui version 3.

Just a quick update since then is that Dear PyGui has reached version 1.0 and the API is now stable with a proper deprecation policy. Additional features include support for extremely dynamic tables, became faster still, introduction of the first steps into 3D and drawing transformations, support for multiple fonts, node editor and many small improvements and bug fixes. There are still many ideas for future development, including more 3D.

With regard to 3D, are you aware of DearPy3D by the same developers (still under development, also available under the MIT license)?

hoffstadt/Marvel: Dear PyGui 3D Engine (early development) (github.com)

There's also that library all the AI models started using that gives you a public URL to share. After researching it: https://www.gradio.app/ is the link.

It's used specifically for making simple UIs for machine learning apps. But I guess technically you could use it for anything.

What is the business model for https://www.taipy.io/, https://streamlit.io/, or https://www.gradio.app/? These are nice tools - but how will the sponsoring businesses support themselves? I didn't see any mention of enterprise plans, etc. Is the answer simply that "we've not announced our revenue model yet"? What should one expect?

Repo : https://github.com/gradio-app/gradio

There's TensorFlow.js for running machine learning on JavaScript, but personally, I'd prefer using the Python Gradio package, which is designed for creating UIs for machine learning inference demos.

I found an issue on gradio github but looks like it's closed so I am not sure if it's still a common issue or only I am facing it due to certain settings/absence of a fix. ( https://github.com/gradio-app/gradio/issues/3060 )

I disagree hard with this – for instance I've recently needed to dig into the code for the Gradio library, and when PRs are like https://github.com/gradio-app/gradio/pull/3300 (and the merge commit's message is what it is) it's hard to understand why some decisions have been made when doing `git annotate` later on.

Gradio for a ui that your commanderGPT can visit and use

gradio is documented, it doesn't seem very complex, it would be something like moving this block under the other one. i think it's ui_extra_networks.py, the file you are looking to edit. (if you do it make a copy to restore when you go to update)

Gradio did have an issue for a while where your URL was guessable, so unless you had a password it was pretty easy to find, but as far as I know they've increased the complexity so much that it's no longer an issue.

My script wouldn't work on the langchain because it was literally made within the gradio "docs builder" script that afaik was made specifically for their website (repo)