code/alchemy
Archived
1
0
Fork 0
Code Issues 2 Pull requests 1 Projects Releases Packages Wiki Activity Actions

A basic website. Can be redone later, just enough to fill the domain and point people in the right direction.

Browse source
This commit is contained in:
Ryan McGrath 2019-05-24 17:20:52 -07:00
parent 1ba17c9a37
commit 2044ab7fc7
No known key found for this signature in database
GPG key ID: 811674B62B666830
29 changed files with 202 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
README.md
View file

@ -21,7 +21,7 @@ Alchemy will, ideally, support the platforms listed below. At the moment, the `C
- `qt`, which affords a `Qt` layer. This is mostly indended for `KDE` users; if you'd like to run it elsewhere, you're on your own.
- `uwp`, which affords a `"UWP"` layer for Microsoft platforms that support it. This is a bit of a hack, provided by linking into the [microsoft/WinObjC](https://github.com/Microsoft/WinObjC/) framework, originally intended for porting `iOS` applications to `UWP`. Down the road, if or when a proper `UWP` library for Rust surfaces, I'd be happy to look at replacing this.
Support for more platforms is desired - for example, I think an [`OrbTk`](https://gitlab.redox-os.org/redox-os/orbtk) or [`Piston`](https://www.piston.rs) backend could be cool to see. A [`winapi-rs`](https://github.com/retep998/winapi-rs) backend could be cool, too!
Support for more platforms is desired - for example, I think an [`OrbTk`](https://gitlab.redox-os.org/redox-os/orbtk) or [`Piston`](https://www.piston.rs) backend could be cool to see. A `web` backend would be awesome to support. A [`winapi-rs`](https://github.com/retep998/winapi-rs) backend could be cool, too!
## What Currently Works...?
At the moment, the following is implemented:
@ -78,19 +78,19 @@ fn main() {
}
});
alchemy::shared_app().run(AppState {
app.run(AppState {
window: Window::new("Le Appy App", (0., 0., 600., 600.), WindowState {})
});
}
```
## Does it support custom Components?
Alchemy implements the React component lifecycle. It does not (currently) implement Hooks, and may or may not implement them in the future. The class-based lifecycle maps fairly well to Rust idioms already, as you really never wanted to subclass in React anyway.
Yes. Alchemy implements the React component lifecycle - although it does not (currently) implement Hooks, and may or may not implement them in the future. The class-based lifecycle maps fairly well to Rust idioms already, as you really never wanted to subclass in React anyway.
A custom component would look like the following:
``` rust
use alchemy::{Component, Error, rsx, RSX};
use alchemy::{Component, Error, Props, rsx, RSX};
pub struct MySpecialWidget {
your_special_value_or_whatever: i32