Use Rust for the front-end too #374

Birleştirildi
elegaanz 2018-12-25 10:51:41 +00:00 wasm içindeki 11 işlemeyi master ile birleştirdi
elegaanz 2018-12-23 21:31:34 +00:00 yorum yaptı (github.com konumundan göç edildi)

Rust can compile to WASM, so let's use it for front-end code as well.

To compile the front-end:

cargo install cargo-web
cd plume-front
cargo web deploy -o ../static
Rust can compile to WASM, so let's use it for front-end code as well. To compile the front-end: ``` cargo install cargo-web cd plume-front cargo web deploy -o ../static ```
trinity-1686a 2018-12-24 00:39:08 +00:00 incelendi
trinity-1686a bir yorum yaptı
Sahibi

I've had a hard time testing this. I think it would be better to cargo web deploy without location, and do some processing (adding static/ to path so the new route is not required) and copying by ourselves in build.rs. Currently the instructions are polluting static/ with an index.html

I've had a hard time testing this. I think it would be better to `cargo web deploy` without location, and do some processing (adding `static/` to path so the new route is not required) and copying by ourselves in build.rs. Currently the instructions are polluting `static/` with an `index.html`
Sahibi

I think this file souldn't be committed, it's auto generated and things like __cargo_web_snippet_199d5eb25dfe761687bcd487578eb7e636bd9650 are probably not reproducible between builds

I think this file souldn't be committed, it's auto generated and things like `__cargo_web_snippet_199d5eb25dfe761687bcd487578eb7e636bd9650` are probably not reproducible between builds
elegaanz 2018-12-24 09:26:07 +00:00 yorum yaptı (github.com konumundan göç edildi)

You can now just use cargo web deploy, build.rs will do the rest.

You can now just use `cargo web deploy`, build.rs will do the rest.
igalic 2018-12-24 10:26:25 +00:00 yorum yaptı (github.com konumundan göç edildi)

how much faster is the resulting wasm compared to the previous Javascript?

how much faster is the resulting wasm compared to the previous Javascript?
Sahibi

@igalic considering our use-case, probably not much. The main advantage is the whole team being able to debug it I think

@igalic considering our use-case, probably not much. The main advantage is the whole team being able to debug it I think
elegaanz 2018-12-24 10:34:11 +00:00 yorum yaptı (github.com konumundan göç edildi)

There may be better performances once with the future editor, especially when writing big articles. Another advantage is that we will be able to share code between backend and frontend if we need it.

There may be better performances once with the future editor, especially when writing big articles. Another advantage is that we will be able to share code between backend and frontend if we need it.
Sahibi

@BaptisteGelez I see Travis failed because of cargo-web installation, you might be interested into this https://github.com/koute/cargo-web#using-cargo-web-on-travis .

@BaptisteGelez I see Travis failed because of cargo-web installation, you might be interested into this https://github.com/koute/cargo-web#using-cargo-web-on-travis .
codecov[bot] 2018-12-24 14:45:05 +00:00 yorum yaptı (github.com konumundan göç edildi)

Codecov Report

Merging #374 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #374   +/-   ##
=======================================
  Coverage   27.86%   27.86%           
=======================================
  Files          63       63           
  Lines        6280     6280           
=======================================
  Hits         1750     1750           
  Misses       4530     4530
# [Codecov](https://codecov.io/gh/Plume-org/Plume/pull/374?src=pr&el=h1) Report > Merging [#374](https://codecov.io/gh/Plume-org/Plume/pull/374?src=pr&el=desc) into [master](https://codecov.io/gh/Plume-org/Plume/commit/22bc8c1d407cd4c3844aaa1161afd2a86f6d349a?src=pr&el=desc) will **not change** coverage. > The diff coverage is `n/a`. ```diff @@ Coverage Diff @@ ## master #374 +/- ## ======================================= Coverage 27.86% 27.86% ======================================= Files 63 63 Lines 6280 6280 ======================================= Hits 1750 1750 Misses 4530 4530 ```
trinity-1686a 2018-12-24 19:09:28 +00:00 incelendi
trinity-1686a bir yorum yaptı
Sahibi

You should also update documentation, something like add "run cargo web deploy -p plume-front"

You should also update documentation, something like add "run `cargo web deploy -p plume-front`"
Sahibi

this line is no longer required

this line is no longer required
trinity-1686a 2018-12-25 10:50:39 +00:00 bu değişiklikleri onayladı
Bu konuşmaya katılmak için oturum aç.
Değerlendirici yok
Kilometre Taşı Yok
Proje yok
Atanan Kişi Yok
2 Katılımcı
Bildirimler
Bitiş Tarihi
Bitiş tarihi geçersiz veya aralık dışında. Lütfen 'yyyy-aa-gg' biçimini kullanın.

Bitiş tarihi atanmadı.

Bağımlılıklar

Bağımlılık yok.

Referans: Plume/Plume#374
Herhangi bir açıklama sağlanmadı.