9076dbaadc
With this PR, when JS is activated and WASM supported, the article editor will be dynamically replaced with `contenteditable`s elements. This makes the editing interface simpler and less like a regular form. It will also allow us to easily add visual formatting with native browser APIs (and to insert images or videos directly). Here is a little demo:  There is still a lot to do, but it is a good first step. Fixes #255
24 lines
1.0 KiB
Rust
24 lines
1.0 KiB
Rust
extern crate ructe;
|
|
extern crate rsass;
|
|
use ructe::*;
|
|
use std::{env, fs::*, io::Write, path::PathBuf};
|
|
|
|
fn main() {
|
|
let out_dir = PathBuf::from(env::var("OUT_DIR").unwrap());
|
|
let in_dir = PathBuf::from(env::var("CARGO_MANIFEST_DIR").unwrap())
|
|
.join("templates");
|
|
compile_templates(&in_dir, &out_dir).expect("compile templates");
|
|
|
|
println!("cargo:rerun-if-changed=static/css");
|
|
let mut out = File::create("static/css/main.css").expect("Couldn't create main.css");
|
|
out.write_all(
|
|
&rsass::compile_scss_file("static/css/main.scss".as_ref(), rsass::OutputStyle::Compressed)
|
|
.expect("Error during SCSS compilation")
|
|
).expect("Couldn't write CSS output");
|
|
|
|
println!("cargo:rerun-if-changed=target/deploy/plume-front.wasm");
|
|
copy("target/deploy/plume-front.wasm", "static/plume-front.wasm")
|
|
.and_then(|_| read_to_string("target/deploy/plume-front.js"))
|
|
.and_then(|js| write("static/plume-front.js", js.replace("\"plume-front.wasm\"", "\"/static/plume-front.wasm\""))).ok();
|
|
}
|