yeah, i dug further and the ctrl-delete/backspace stuff doesn't actually push anything to the undo stack and further, when i added some, it fails to get the right position because multi-line entry doesn't fit with the wrap turned on and the interface for line positions (because it has no vertical component)
the fix is going to be a lot more involved, and unfortunately the project has 667 issues as of when i added mine, so it might be a while. in the meantime i just widened the input to more than enough - but less than an average smartphone screen, and now i have added a state variable that stores the key that gets decoded and validated, as well as the two screens i have created so far, and you can now input an nsec (in hex or bech32) and the "next" button lights up and you click next and the main screen appears
might be a bit slow going building this thing, i dont even know what i should add next, i figure simples, a little multi-line, non-editable text field that logs events and then hook up the bunker signer code and have it establish the subscription to to a relay, oh yes, i will need a configuration to specify the bunker relay, maybe that belongs on the initial screen too, and then probably need to have a button that generates the bunker URL to paste into a login screen for an app, i think #jumble has one of these inputs for login so perhaps in a day or two i will have the MVP that just signs everything that is sent to it
been having a bit of a frustrating time with the GUI stuff... for God only knows what reason, the wasm gio script with the current version of gogio, which generates builds for other platforms (including ios and android) doesn't play nice with my brave browser... probably some crap in the script that brave blocks
well, thankfully i have another one that works: https://images.mleku.dev/birb/ which was the beginnings of a chat app i was going to build
and because using the web-file-serving standard functions didn't seem to actually serve properly, i wrote handlers that just serve up the relevant files that have been embedded in the binary
this also meant i am able to save the working index.html and wasm.js files it needs in different names, and load them instead of the crap ones that the stupid gogio tool creates, and i just set them to ignore on git, point the embeds at the ones that work, and voila
so, 3 hours later, i'm finally in a position to start working on the actual GUI i decided to start working on
thank the Lord i was able to find a path through this abysmal nonsense
presumably once again because gio has such a small, very part time dev group working on it, they are always cocking things up
but i've now got all the latest of everything, without the limitations that made me decide to rage quit the gio slack, after giving them a piece of my mind (this isn't the first time i've complained about their infernal encapsulated but essential parts of their widget toolkit) and it doesn't matter now, i have a path through and i can now build a web app in pure go to interact with #realy
i had a walk up to the shops to buy cigarettes and drink a glass of red wine, and to think
i was like, "what to do next with #realy ?"
it took a while for me to run through options but eventually i figured it out
i had already prepared to be able to build proper custom widgets for https://gioui.org UI, and i remembered that it can do web interfaces, because a lot of the ideas i was pondering was related to making a web interface for the configuration i just built
well, so i can build wasm based UIs that can also be transplanted to run on pc or mobile devices (any of them) so, i'm going to start with building an editor for the dynamic configuration, complete with instant action for toggles and multi-selects
the other thing that occurred to me is it probably won't be that hard to integrate the "window" interface to connect the UI up to browser signer extensions, which means that is the only thing i have to do in order to get the UI to sign the requests to the API and action them
later i will be able to build a full relay event console like the one in #nostrudel - and it would be able to not just publish to the relay but also broadcast to a user's chosen relays, and all kinds of other neat things that don't involve anything more than displaying images and simple plaintext are within easy reach, so, also, a relay-focused chat interface would be another project down the track
so, my afternoon's work is going to be building out a little UI for the configuration and i'll see where i get to
Showing page 1 of
13 pages
