areweguiyet / areweguiyet Goto Github PK

https://github.com/microsoft/windows-rs
Both Win32 UI and XAML UI

The crate link should be changed to https://crates.io/crates/conrod-core, and the docs link should be changed to https://docs.rs/conrod_core/latest/conrod_core/ to reflect the latest version.

OrbTK does not use WebRender but still has the WebRender tag.

Gtk link currently goes to https://github.com/gtk-rs/gtk which is deprecated. New link should be https://github.com/gtk-rs/gtk-rs

https://github.com/servo/core-foundation-rs

Right now CI just builds the CLI and verifies/publishes after merge.

The CLI logs errors when it finds an issue with any of the source files.

The publish command currently panics if there are errors.

The problem with panicking is that the cache is not written when there are errors! This should be fixed.

Add license for the repository

I think WinSafe is a good candidate for the win32 category.

Please let us know if you have any suggestions for tags! We should do a pass on all the crates currently listed.

My quick thoughts:

• Soft real time suitable
• Flexbox-like layout
• Functional UI
• DSL (these libraries use a custom DSL for layout or formatting)
• Backend agnostic
• Backend
• Native

https://github.com/sixtyfpsui/sixtyfps

Hello!

I ask you to add the project https://peterlane.codeberg.page/rstk

Sincerely
Artem

I was using the site recently and I noticed the webserver doesn't automatically redirect HTTP requests to HTTPS. Might be a good security feature to implement.

I've just put out a blog post about the Druid ecosystem: https://poignardazur.github.io/2022/12/09/druid-ecosystem/

I think some of the information mentioned in it should be updated in areweguiyet, including:

• Xilem, Masonry and Panoramix should be added to the list.
• Druid should be marked as deprecated.

Just pointing it out, I'm not motivated enough to implement the changes myself.

There are official bindings to sciter.
Sciter enables to write a gui with web tec, like Elektron.

PR already made: #79

The original plan for this repo in May 2018 was to simply collect notes on how one might approach a GUI in Rust, and then catalog the benefits and drawbacks of each approach.

Should we still attempt to do this? Or should it be relegated to blog/news posts?

It may be beneficial to have a central community hub for recording developments in a chapter by chapter "book" form. The "book" would describe different approaches without "choosing" one.

The book would evolve over the coming months and years as people learn what works, what doesn't, what's fun, and what's not. It would ideally contain lots of working code and reference a lot of active projects as examples.

I saw this talk on YouTube, presenting the (very alpha) moxie library. It might belong in the list of gui libraries, although it seems like it still is mostly the original author working on it.

The list of crates is not loaded, and this error seems to be caused by the version returned by the CDN. It returns the version 3.2 instead of the version 2.6 before.

Error

Uncaught TypeError: Vue.component is not a function
    <anonymous> https://www.areweguiyet.com/main.js:5

https://www.reddit.com/r/rust/comments/hu1s7v/nativewindowsgui_is_back_and_ready_to_kick_some/

It's even marked "1.0".

redirect the current domain of "http://areweguiyet.com/" to the new website for launch

Proposing possible removal of IMGUI-RS as it looks unmaintained and unused.

Removal may not be the most appropriate action though?

https://github.com/lucidscape/imgui-rs

I am currently preparing a Blogpost for the Rust2019 community blog call out. Things have a little died out – but we should consider a restart :)

I'm not sure who best to report this to, so filing as an issue here. Feel free to route and close.

If I open https://areweguiyet.com/ I get a cert error, saying it's a *.github.com cert (and also including *.github.io). This is probably a very simple misconfiguration.

The http still works, but I always try to prefer https.

Do we want something like an official forum and/or chat? What other options do we have to bring people(users/developers/potential contributors) together to show of the current stage of their lib, app and to contact us. Making issues has a high barrier if you don't want plan to participate in a serious manner and just want to say hello and hang around.

https://rust-qt.github.io/

#30 ( https://github.com/MoAlyousef/fltk-rs )

https://github.com/bodil/vgtk

https://github.com/lykhonis/terramach

https://github.com/bodil/vgtk

A number of potential approaches to GUI, potential problems and potential solutions have been raised in discussion. Those need to be documented for reference.

https://github.com/servo/core-foundation-rs

In Approaches section, it doesnt talk about azul.rs and other GUI frameworks, and doesnt haves a section for existing Rust graphical apps.

If we're going to consider rust ready for use with guis, we would have to support screen readers, and if your site helped filter by that it would be very helpful. Thanks!

Context: I wanted to use rust to make a simple gui app but I wanted one that actually supports screen readers well. From my investigations this is a very limited subset of the gui libraries. Only Qt and Gtk as far as I can tell are fully screen reader accessible which is a shame because I started my search to avoid those two engines.

https://github.com/seed-rs/seed is an Elm-inspired web frontend framework, written in Rust and compiled to WebAssembly.

I would really like to see this framework be mentioned on the areweguiyet.com page, and it is already fairly developed and shows great efforts. Here are some example sites written using this framework:

https://seed-rs.org/
https://realworld.seed-rs.org/

https://github.com/seed-rs/awesome-seed-rs#examples

I would like to add this to this website, so if there is anything next to the README of this repo, that I should know, or any objections, please let me know :)

Without regards to implementation, we can sketch versions of what we'd like the API surface to look like, or just plain simply the available possibilities. This can guide initial investigation into both ergonomics and feasibility of implementation.

This looks like something that @shivshank proposed in #1 but I don't see any other mentions of it. I think this would be helpful to see which GUI crates are actually being used. I suppose a crates.io download count could proxy for this as well.

If others want this, I'd be happy to try to contribute to push it forward as well.

Thoughts?

https://www.reddit.com/r/rust/comments/gtqnsh/rust_bindings_for_littlevgl_embedded_gui_library/

So the page apparently uses flexbox for a pleasant resolution independent layout. Nice. Ironically the main body of the page has a fixed width of 1200px, defeating the point of using flexbox in the first place and causing the text to get cut off on my laptop. Unless I effectively fullscreen my browser, that is. I get that modern web design is meant to "encourage" people to interact more with their browsers, but for people stuck in their windowed ways this is quite bothersome.






_{/s, but the rant still applies}

Currently both Firefox and Chrome reject the SSL certificate when trying to connect to www.areweguiyet.com. If I remove the www from the URL, it works.

Hi,

a couple of days ago I released the first version of azul: https://github.com/fschutt/azul/releases/tag/1.0.0-alpha1

Not sure if this is news-worthy, just a thought that you might want to add it to the website

Thanks

I want to flesh out V2 plans for the site more, but here are some good ideas courtesy of @mardab we should consider doing ASAP.

• Store all crate JSON TOML as separate files
• Flag crates that should be delisted (initial criteria: no active branch and no crate publication within last year)
• Highlight examples - link to examples directory if one exists in crate repo, and add support for listing other demos
• Add some sort of checking if a listed example is too far out of date
• Develop some system for metal ratings - a possible alternative is alpha | beta | prod and version badges - we'd define some sort of standard where crate developers can include some dot file in their repo to specify what they wanted to be shown as. TODO: Research prior art.
• Add pipeline to check if someone is a contributor to a crate they're adding (this is less relevant if we start indexing crates.io directly)

This is probably related to #4, but it seems to be a separate issue. If the "Approaches" section currently does not exist, then a link to it should not appear in the navigation bar.

Link in navbar that leads to 404: https://www.areweguiyet.com/approaches

Freshly announced and promising (IMHO):

• https://github.com/sixtyfpsui/sixtyfps
• https://sixtyfps.io/releases/0.1.1/docs/rust/sixtyfps/
• https://sixtyfps.io/blog/announcing-sixtyfps-0.1.html

https://www.cmyr.net/blog/gui-framework-ingredients.html

Lays out a pretty broad but necessary set of items for a full featured gui framework.

Developers evaluating whether Rust is areweguiyet would do well to read this before they begin looking at Rust frameworks.

As a feature request for areweguiyet, what about a feature matrix based around this list?

https://github.com/tauri-apps/tauri

https://github.com/retep998/winapi-rs

Feature request: be able to sort by name, popularity or release date

I am currently working on a library to improve GTK app development with rust here. I'd like to place it here to make others aware of it if thats possible.

If you think my library is of any interes I would like to contribute it as stated in the Contribution section in the readme.

1password has recently released a new Linux client written with Electron (React.js) & Neon Bindings. Looks like it can be added to the list.

It's ok to discontinue projects, but this should never happen silently.

Yet, this repository has been more or less unmaintained for over a year now.

This means stale links and an outdated representation of what's the actual state of GUI development in Rust.
And to fork is not an option, as the domain is important, too, and a lot of resources already link here.

@pythoneer and @dxenonb what are your thoughts on this situation? If you are not willing to maintain this repository, please ask for others to help instead of letting this project become stale silently.

Some libraries gonna support Android/IOS in the future (OrbTK, Slint, Tauri...).

upd:
OrbTK is dead
SixtyFPS is now Slint