WebUI does not support multi-models or pipelines
saddam213 opened this issue · comments
WebUI has fallen behind due to the inclusion of the WPF UI
I am wondering if we even need to keep it, other OS's already have many choices for Stable Diffusion so I think people using OnnxStack on linux and mac will be low
Perhaps time to scrap this project and replace with an API instead, easier to maintain, will still be cross-platform, then other people can make a WebUI or integrate the API into existing SD UI's
Or even go the other direction, add auth etc and make it a fully usable website for creating mid-journey style websites, allowing people to monetize their GPUs if they want
Pros:
- Cross-Platfrom
- Server/Client Based, backend can be installed on GPU server
- ASP.NET Core, so auth can easily be added for a Public facing website
Cons:
- Server/Client Based, security concerns, xss, etc
- Image handling is way harder on web, upload, download etc
Thoughts?
hmm, do u mean to keep standalone gui [the one that has the dark mode] and cancel webui [the one needs browser] ?
that is a nice idea, browsers always use more ram so sending all the power to the standalone gui is much much better imo, not to mention it is very more portable and it is very beautiful now!
hmm, do u mean to keep standalone gui [the one that has the dark mode] and cancel webui [the one needs browser] ? that is a nice idea, browsers always use more ram so sending all the power to the standalone gui is much much better imo, not to mention it is very more portable and it is very beautiful now!
They are very different types of applications, so both have major benefits in different scenarios
true, honestly i love this gui with the dark mode more than anything out there in stable diffusion world right now! i think many will agree, i mean the casual users like me
but everybody hast a taste. let's hear their opinion too
The WebUI have 8 skins, 4 dark 4 light, but how it look is not whats important, its how servers use OnnxStack not desktop users
I have severs with GPUs, the windows app is useless, unless I use it on the server, which you don't do
The WebUI is server/client based, so you setup the web on your server then you can connect and use it form many other PCs at the same time, like mid-journey
so as you can see, its much more powerful than the desktop app, but just not for how you use it.
The Uno project may be a close to drop-in replacement here. It is designed to be cross platform but keep mostly the same API from WinUI.
oh u right Adam, didn't see that point, lots of users wanna be server side too. maybe work on them both? gotta be spend more time to mention both, but hey a little update here and a little update there will be cool for the both world.
I really enjoy native apps, but that is a personal preference.
Blazor could be an option if that is the way forward. Uno can also target WASM.
The Uno project may be a close to drop-in replacement here. It is designed to be cross platform but keep mostly the same API from WinUI.
Im probably faster/better at Web than WPF, so if it was the other way around it would suit :p
This is my first WPF app in about 10 years, and the rust is real deep, lol, but forgot how cool XAML was!!
I really enjoy native apps, but that is a personal preference. Blazor could be an option if that is the way forward. Uno can also target WASM.
Yeah, native apps are way better if you are running a local setup, so the WPF is here to stay
Im probably faster/better at Web than WPF, so if it was the other way around it would suit :p
I'm the opposite 😁
This is my first WPF app in about 10 years, and the rust is real deep, lol, but forgot how cool XAML was!!
Couldn't tell, thought it was WinUI for a while until this thread. I didn't know official WPF was ported to Core/net6. XAML is really nice.
u already did a great favor to the stable diffusion community! even if u stop updating wpf app i will still use this one :D
at the end, go for and do what is easier and better that u think
Im probably faster/better at Web than WPF, so if it was the other way around it would suit :p
I'm the opposite 😁
This is my first WPF app in about 10 years, and the rust is real deep, lol, but forgot how cool XAML was!!
Couldn't tell, thought it was WinUI for a while until this thread. I didn't know official WPF was ported to Core/net6. XAML is really nice.
Yeah they added it to .NET Core, but its weird, still windows only, but you still still get the benefits of .NET Core
But its still about 200lines of code to change the TitleBar color, lol Microsoft man
But its still about 200lines of code to change the TitleBar color, lol Microsoft man
I never want to deal with the Win32 message pump again!
This issue is for the WebUI, not WPF.
I'm definitely keen on an API, but tbh it depends on what the projects goals are or what you aspire for them to be. Is OnnxStack primarily a C# library that developers can use to build generative AI applications in whatever platform/framework suits their goals/needs, or is it more intended to be a Windows-based UI for Stable Diffusion?
Those are two quite different things.
The way I see it, if you build a great library, that unlocks the possibility for lots more C# developers to take that library and build out applications based on it however they see fit, though I recognize it's probably useful to build a UI as a way to dogfood your own library. At minimum it's probably worth it to focus on a single UI rather than try to split the projects limited engineering bandwidth across multiple UIs keeping them in sync.
The project goal was ImageClassification, LOL, have not even got close to that part yet, got hooked on SD
The base projects are my goal and the the WebUI was added for users to test as the first user at the time was a Mac user I started with the WebUI as it was the simplest cross-platform UI I could whip up.
But as more users came a basic windows UI was needed as well, however I really don't want to waste time on UI code, I would rather focus on core code, so an API would be better for me, then users can build their own interfaces.
I will continue the WPF UI here until it is superseded by a future app that will include the Text Generation functions from LLamaStack, but that's another story
So yeah, leaning towards a API as replacement for WebUI
WebUI has been decommissioned