#relm4 — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #relm4, aggregated by home.social.
-
After some spontaneous hacking on BitRitters edit mode, i made some good progress: First time i could change values and save them to the database/server.
It really means alot to le because after 2 failed applications for funding i ditched the topic for too long.
It might need a major rework of the UI internals though, but now i am motivated again.#BitRitter #VaultWarden #BitWarden #PasswordManager #LinuxPhone #LinuxMobile #Relm4
-
After some spontaneous hacking on BitRitters edit mode, i made some good progress: First time i could change values and save them to the database/server.
It really means alot to le because after 2 failed applications for funding i ditched the topic for too long.
It might need a major rework of the UI internals though, but now i am motivated again.#BitRitter #VaultWarden #BitWarden #PasswordManager #LinuxPhone #LinuxMobile #Relm4
-
-
-
-
-
-
Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
#BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden -
Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
#BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden -
Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
#BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden -
Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
#BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden -
Since i got back into BitRitter development, i had some success in getting Fluent translations up and running. This is something that will stay, sorry gettext etc.
But a bigger achievement was something i did not understand when designing the architecture: RBW provides a daemon that can do the heavy lifting for me and not decryption etc. needed on my end. I misread some stuff about this since i was just a rookie. Big rewrite incoming.
#BitRitter #RBW #Relm4 #RustLang #BitWarden #VaultWarden -
Since adw::EntryRow does not implement String bindings or similar and i can not (or don't want to, for Relm4 reasons) use get/set methods, is there another approach?
-
Since adw::EntryRow does not implement String bindings or similar and i can not (or don't want to, for Relm4 reasons) use get/set methods, is there another approach?
-
Since adw::EntryRow does not implement String bindings or similar and i can not (or don't want to, for Relm4 reasons) use get/set methods, is there another approach?
-
Since adw::EntryRow does not implement String bindings or similar and i can not (or don't want to, for Relm4 reasons) use get/set methods, is there another approach?
-
Since adw::EntryRow does not implement String bindings or similar and i can not (or don't want to, for Relm4 reasons) use get/set methods, is there another approach?
-
I really need to learn #GTK app development. GUI dev stuff outside the browser always ends up frustrating me.
#Rust people, what are your thoughts on using #Relm4 vs. the regular gtk & libadwaita crates? How is support for #Blueprint? Last I used it, I dont think the blueprint LSP was built yet, so it was pretty tedious because I use #Helix and not #GNOME #Builder.
-
I really need to learn #GTK app development. GUI dev stuff outside the browser always ends up frustrating me.
#Rust people, what are your thoughts on using #Relm4 vs. the regular gtk & libadwaita crates? How is support for #Blueprint? Last I used it, I dont think the blueprint LSP was built yet, so it was pretty tedious because I use #Helix and not #GNOME #Builder.
-
I really need to learn #GTK app development. GUI dev stuff outside the browser always ends up frustrating me.
#Rust people, what are your thoughts on using #Relm4 vs. the regular gtk & libadwaita crates? How is support for #Blueprint? Last I used it, I dont think the blueprint LSP was built yet, so it was pretty tedious because I use #Helix and not #GNOME #Builder.
-
I really need to learn #GTK app development. GUI dev stuff outside the browser always ends up frustrating me.
#Rust people, what are your thoughts on using #Relm4 vs. the regular gtk & libadwaita crates? How is support for #Blueprint? Last I used it, I dont think the blueprint LSP was built yet, so it was pretty tedious because I use #Helix and not #GNOME #Builder.
-
I really need to learn #GTK app development. GUI dev stuff outside the browser always ends up frustrating me.
#Rust people, what are your thoughts on using #Relm4 vs. the regular gtk & libadwaita crates? How is support for #Blueprint? Last I used it, I dont think the blueprint LSP was built yet, so it was pretty tedious because I use #Helix and not #GNOME #Builder.
-
i've been using relm4 for a while and i'm really happy with it. i love the #elm architecture - your app's state is a struct (or object), your user interface is rendered by a function that takes your state and returns a tree of widgets (or similar), widgets emit messages, messages modify state. i find it so much cleaner and easier to wrap my head around than traditional imperative methods or MVVM.
what are some other nice cross-platform #desktop app frameworks that use this architecture? i'm mainly familiar with #relm4 and #iced in #rust. :boost_requested:
-
i've been using relm4 for a while and i'm really happy with it. i love the #elm architecture - your app's state is a struct (or object), your user interface is rendered by a function that takes your state and returns a tree of widgets (or similar), widgets emit messages, messages modify state. i find it so much cleaner and easier to wrap my head around than traditional imperative methods or MVVM.
what are some other nice cross-platform #desktop app frameworks that use this architecture? i'm mainly familiar with #relm4 and #iced in #rust. :boost_requested:
-
i've been using relm4 for a while and i'm really happy with it. i love the #elm architecture - your app's state is a struct (or object), your user interface is rendered by a function that takes your state and returns a tree of widgets (or similar), widgets emit messages, messages modify state. i find it so much cleaner and easier to wrap my head around than traditional imperative methods or MVVM.
what are some other nice cross-platform #desktop app frameworks that use this architecture? i'm mainly familiar with #relm4 and #iced in #rust. :boost_requested:
-
i've been using relm4 for a while and i'm really happy with it. i love the #elm architecture - your app's state is a struct (or object), your user interface is rendered by a function that takes your state and returns a tree of widgets (or similar), widgets emit messages, messages modify state. i find it so much cleaner and easier to wrap my head around than traditional imperative methods or MVVM.
what are some other nice cross-platform #desktop app frameworks that use this architecture? i'm mainly familiar with #relm4 and #iced in #rust. :boost_requested:
-
i've been using relm4 for a while and i'm really happy with it. i love the #elm architecture - your app's state is a struct (or object), your user interface is rendered by a function that takes your state and returns a tree of widgets (or similar), widgets emit messages, messages modify state. i find it so much cleaner and easier to wrap my head around than traditional imperative methods or MVVM.
what are some other nice cross-platform #desktop app frameworks that use this architecture? i'm mainly familiar with #relm4 and #iced in #rust. :boost_requested:
-
Question about #Phosh and OSK:
I have a #Relm4 (GTK4+adwaita) application. I recently migrated from gtk::Dialog to adw::Dialog and now i have the following behavior:
I open the app and open a dialog, which itself renders for about 45% of my screen height, with the Confirm button being at around 20% of the screen height. If i pop up the OSK, the dialog gets moved 5% upwards and the Confirm button is now covered by the OSK.
The app itself is not resized (for example GNOME software is).
1/2 -
Question about #Phosh and OSK:
I have a #Relm4 (GTK4+adwaita) application. I recently migrated from gtk::Dialog to adw::Dialog and now i have the following behavior:
I open the app and open a dialog, which itself renders for about 45% of my screen height, with the Confirm button being at around 20% of the screen height. If i pop up the OSK, the dialog gets moved 5% upwards and the Confirm button is now covered by the OSK.
The app itself is not resized (for example GNOME software is).
1/2 -
Question about #Phosh and OSK:
I have a #Relm4 (GTK4+adwaita) application. I recently migrated from gtk::Dialog to adw::Dialog and now i have the following behavior:
I open the app and open a dialog, which itself renders for about 45% of my screen height, with the Confirm button being at around 20% of the screen height. If i pop up the OSK, the dialog gets moved 5% upwards and the Confirm button is now covered by the OSK.
The app itself is not resized (for example GNOME software is).
1/2 -
Question about #Phosh and OSK:
I have a #Relm4 (GTK4+adwaita) application. I recently migrated from gtk::Dialog to adw::Dialog and now i have the following behavior:
I open the app and open a dialog, which itself renders for about 45% of my screen height, with the Confirm button being at around 20% of the screen height. If i pop up the OSK, the dialog gets moved 5% upwards and the Confirm button is now covered by the OSK.
The app itself is not resized (for example GNOME software is).
1/2 -
Question about #Phosh and OSK:
I have a #Relm4 (GTK4+adwaita) application. I recently migrated from gtk::Dialog to adw::Dialog and now i have the following behavior:
I open the app and open a dialog, which itself renders for about 45% of my screen height, with the Confirm button being at around 20% of the screen height. If i pop up the OSK, the dialog gets moved 5% upwards and the Confirm button is now covered by the OSK.
The app itself is not resized (for example GNOME software is).
1/2 -
My fellow fedizens, i have done it.
I have applied #BitRitter to https://nlnet.nl/propose/ in the category "Open Call". Well at least 2 features i want to implement.
Wish me luck.If you have an awesome Mobile FOSS Project, maybe you want to apply too? Deadline is 2024-06-01 so this friday. Application process took me about half an hour, so that's doable.
-
My fellow fedizens, i have done it.
I have applied #BitRitter to https://nlnet.nl/propose/ in the category "Open Call". Well at least 2 features i want to implement.
Wish me luck.If you have an awesome Mobile FOSS Project, maybe you want to apply too? Deadline is 2024-06-01 so this friday. Application process took me about half an hour, so that's doable.
-
My fellow fedizens, i have done it.
I have applied #BitRitter to https://nlnet.nl/propose/ in the category "Open Call". Well at least 2 features i want to implement.
Wish me luck.If you have an awesome Mobile FOSS Project, maybe you want to apply too? Deadline is 2024-06-01 so this friday. Application process took me about half an hour, so that's doable.
-
My fellow fedizens, i have done it.
I have applied #BitRitter to https://nlnet.nl/propose/ in the category "Open Call". Well at least 2 features i want to implement.
Wish me luck.If you have an awesome Mobile FOSS Project, maybe you want to apply too? Deadline is 2024-06-01 so this friday. Application process took me about half an hour, so that's doable.
-
My fellow fedizens, i have done it.
I have applied #BitRitter to https://nlnet.nl/propose/ in the category "Open Call". Well at least 2 features i want to implement.
Wish me luck.If you have an awesome Mobile FOSS Project, maybe you want to apply too? Deadline is 2024-06-01 so this friday. Application process took me about half an hour, so that's doable.
-
News from #BitRitter:
https://codeberg.org/Chfkch/bitritter
Account creation is now possible via the app, no need to store credentials on disk.
This was a huge step towards the release of the first beta.
Basic usage is covered in my eyes, now i have to polish things up a bit and test integration in distros and on devices.
Got a lot of help from the community and the #Relm4 channel.
If you want to try now, hit me up if you have problems.
#LinuxMobile #MobileLinux #RustLang -
News from #BitRitter:
https://codeberg.org/Chfkch/bitritter
Account creation is now possible via the app, no need to store credentials on disk.
This was a huge step towards the release of the first beta.
Basic usage is covered in my eyes, now i have to polish things up a bit and test integration in distros and on devices.
Got a lot of help from the community and the #Relm4 channel.
If you want to try now, hit me up if you have problems.
#LinuxMobile #MobileLinux #RustLang -
News from #BitRitter:
https://codeberg.org/Chfkch/bitritter
Account creation is now possible via the app, no need to store credentials on disk.
This was a huge step towards the release of the first beta.
Basic usage is covered in my eyes, now i have to polish things up a bit and test integration in distros and on devices.
Got a lot of help from the community and the #Relm4 channel.
If you want to try now, hit me up if you have problems.
#LinuxMobile #MobileLinux #RustLang -
News from #BitRitter:
https://codeberg.org/Chfkch/bitritter
Account creation is now possible via the app, no need to store credentials on disk.
This was a huge step towards the release of the first beta.
Basic usage is covered in my eyes, now i have to polish things up a bit and test integration in distros and on devices.
Got a lot of help from the community and the #Relm4 channel.
If you want to try now, hit me up if you have problems.
#LinuxMobile #MobileLinux #RustLang -
News from #BitRitter:
https://codeberg.org/Chfkch/bitritter
Account creation is now possible via the app, no need to store credentials on disk.
This was a huge step towards the release of the first beta.
Basic usage is covered in my eyes, now i have to polish things up a bit and test integration in distros and on devices.
Got a lot of help from the community and the #Relm4 channel.
If you want to try now, hit me up if you have problems.
#LinuxMobile #MobileLinux #RustLang -
Again, a litte progress on #BitRitter. The Vault Item Detail Page - where passwords, URIs etc. are shown - is coming together nicely. Though i had some initial problems with the 4 different Item Types and their atttibutes, i found a non-elegant working solution.
Merging the changes to main as soon as it is polished a little more.
#LinuxMobile #MobileLinux #Relm4 #RustLang -
Again, a litte progress on #BitRitter. The Vault Item Detail Page - where passwords, URIs etc. are shown - is coming together nicely. Though i had some initial problems with the 4 different Item Types and their atttibutes, i found a non-elegant working solution.
Merging the changes to main as soon as it is polished a little more.
#LinuxMobile #MobileLinux #Relm4 #RustLang -
Again, a litte progress on #BitRitter. The Vault Item Detail Page - where passwords, URIs etc. are shown - is coming together nicely. Though i had some initial problems with the 4 different Item Types and their atttibutes, i found a non-elegant working solution.
Merging the changes to main as soon as it is polished a little more.
#LinuxMobile #MobileLinux #Relm4 #RustLang -
Again, a litte progress on #BitRitter. The Vault Item Detail Page - where passwords, URIs etc. are shown - is coming together nicely. Though i had some initial problems with the 4 different Item Types and their atttibutes, i found a non-elegant working solution.
Merging the changes to main as soon as it is polished a little more.
#LinuxMobile #MobileLinux #Relm4 #RustLang
