> On Jan 27, 2026, at 13:10, Michael Keller <[email protected]> wrote:
>>
>> Of course. The current state was just pushed to the webUI branch.
>> It's actually been there from the very start of this adventure :)
>
> Nice! I like the idea of repurposing the existing application codebase
> in the form of a CLI. But I think we'll also have to make sure we have
> good test coverage that is run in an automated way to ensure that
> changes to the application do not inadvertently break the web UI.
No argument there. Writing tests for this is actually not all that hard, I
think.
> As for organisation, I am not sure if we'd want to move the flask app
> and the web UI styling to a separate repository that consumes the
> subsurface repository as a submodule or by checking it out, in a
> similar way to how this is already done for our website in
> https://github.com/subsurface/new-website/ (or maybe even combine the
> two?).
Anything that isn't in the main repo is far more likely to go stale and bitrot.
Also, please note that the webUI has nothing to do with the website, it would
be the completely wrong place for it. The website is NOT hosted on the cloud
servers - these are completely different properties and I really don't want to
mix them. Life is hard enough as it is.
So while I'm of course open to people saying "this is different", I would claim
that this is simply a third UI. We have the QtWidgets UI (desktop), the QML
UI (mobile), and now the HTML UI that for technical reasons uses the CLI
to integrate with the Qt/C++ core of Subsurface.
/D
_______________________________________________
subsurface mailing list -- [email protected]
To unsubscribe send an email to [email protected]
