5 ms·

Awesome! Does anyone know if there is any similar framework for RUST?

by jfbaro 7y ago

rhodysurf 7y ago
There is not.
sidewinder128 7y ago
Sadly no. Something like this for Rust would be a game changer. Rust is very nice language I love it. Also I love C++17.
pjmlp 7y ago
First Rust still requires some ergonomic improvements to handle GUI coding in a better way.
- weberc2 7y ago
  Like what? (earnest question)
  - pjmlp 7y ago
    Handling callbacks without piles of Rc<RefCell<>> to access widget data, or having vectors simulating graphs, the most used data structure for UI widgets, having to deal with use-after-free indexes.
    - holy_city 7y ago
      It sounds like you tried to write rust like it's OOP. You're gonna have a bad time if you do that. >Handling callbacks without piles of Rc<RefCell<>> to access widget data That's why you don't let widgets hold program state, they should just propagate deltas and display current state. It's a different way of thinking about how UI can work, but imho it has a lot of benefits aside from just speed and safety. >having vectors simulating graphs, You mean adjacency lists? They're a canonical realization of a graph, and a fast one at that. >having to deal with use-after-free indexes. What do you mean by this?
      - nurettin 7y ago
        >> they should just propagate deltas and display current state. It's a different way of thinking about how UI can work, but imho it has a lot of benefits aside from just speed and safety. That's how delphi does it. Connect widget to a data source and it will update reactively when data source changes. And data source is accessible without touching the widget. When doing a batch update on data, you can also disable widget updates in order to make rendering faster. It also works both ways, so when data is changed from within the widget, the bound data source will be updated accordingly.
      - pjmlp 7y ago
        I have experience with plenty of languages, including doing UI programming in Haskell, just to make your point. If Rust answer to typical UI programming patterns is "you are holding it wrong" then don't expect too much uptake by mainstream UI developers. See Catherine's talk about their game engine implementation, regarding use-after-free indexes, and techniques to avoid it, by binding timestamps to indexes.
        holy_city 7y ago
        I don't think Rust has any one answer to a UI problem, since the UI story is basically the wild west right now. Everyone is doing something a little different. I didn't mean to imply that, just that when I see people complain about the ergonomics of the language and point to using a bunch of Rc<RefCell<T>> stuff usually smells funny, it implies to me that you're either trying to use OO or control flow architectures and patterns, where the type system is able to handle the edge cases that you'd need to think about anyway. There are nicer alternatives, especially in terms of data flow architectures. And I don't know what you mean by "indexes" in this context or which talk you're referring to, do you have any more details or a link? Google isn't finding me anything.
        pjmlp 7y ago
        Catherine is relatively known in the Rust community, hence why I didn't mention anything else. Here is her keynote talk at Rust Conf 2018. https://youtu.be/aKLntZcp27M https://youtu.be/aKLntZcp27M

Awesome! Does anyone know if there is any similar framework for RUST?

by jfbaro 7y ago

Awesome! Does anyone know if there is any similar framework for RUST?

rhodysurf 7y ago

There is not.

sidewinder128 7y ago

Sadly no. Something like this for Rust would be a game changer. Rust is very nice language I love it. Also I love C++17.

pjmlp 7y ago

First Rust still requires some ergonomic improvements to handle GUI coding in a better way.

weberc2 7y ago
Like what? (earnest question)
- pjmlp 7y ago
  Handling callbacks without piles of Rc<RefCell<>> to access widget data, or having vectors simulating graphs, the most used data structure for UI widgets, having to deal with use-after-free indexes.
  - holy_city 7y ago
    It sounds like you tried to write rust like it's OOP. You're gonna have a bad time if you do that. >Handling callbacks without piles of Rc<RefCell<>> to access widget data That's why you don't let widgets hold program state, they should just propagate deltas and display current state. It's a different way of thinking about how UI can work, but imho it has a lot of benefits aside from just speed and safety. >having vectors simulating graphs, You mean adjacency lists? They're a canonical realization of a graph, and a fast one at that. >having to deal with use-after-free indexes. What do you mean by this?
    - nurettin 7y ago
      >> they should just propagate deltas and display current state. It's a different way of thinking about how UI can work, but imho it has a lot of benefits aside from just speed and safety. That's how delphi does it. Connect widget to a data source and it will update reactively when data source changes. And data source is accessible without touching the widget. When doing a batch update on data, you can also disable widget updates in order to make rendering faster. It also works both ways, so when data is changed from within the widget, the bound data source will be updated accordingly.
    - pjmlp 7y ago
      I have experience with plenty of languages, including doing UI programming in Haskell, just to make your point. If Rust answer to typical UI programming patterns is "you are holding it wrong" then don't expect too much uptake by mainstream UI developers. See Catherine's talk about their game engine implementation, regarding use-after-free indexes, and techniques to avoid it, by binding timestamps to indexes.
      - holy_city 7y ago
        I don't think Rust has any one answer to a UI problem, since the UI story is basically the wild west right now. Everyone is doing something a little different. I didn't mean to imply that, just that when I see people complain about the ergonomics of the language and point to using a bunch of Rc<RefCell<T>> stuff usually smells funny, it implies to me that you're either trying to use OO or control flow architectures and patterns, where the type system is able to handle the edge cases that you'd need to think about anyway. There are nicer alternatives, especially in terms of data flow architectures. And I don't know what you mean by "indexes" in this context or which talk you're referring to, do you have any more details or a link? Google isn't finding me anything.
        pjmlp 7y ago
        Catherine is relatively known in the Rust community, hence why I didn't mention anything else. Here is her keynote talk at Rust Conf 2018. https://youtu.be/aKLntZcp27M https://youtu.be/aKLntZcp27M