Skip to content

Provider customization improvements #91

@calejvaldez

Description

@calejvaldez

Summary

There's some existing preloading functionality in the palliaview branch, but it has to get improved.

What is the expected correct behavior?

Preloading should be more thought out, especially for deployment purposes.

Steps to reproduce

Most preloading happens when the app is launched for the first time.

Relevant logs and/or screenshots

Code snippet in the palliaview branch:

fn preload_content(conn: &Connection) {
conn.execute_batch(
r#"INSERT INTO resource (label, description, url, organization, category, last_updated) VALUES ("Support Email", "Have an issue with your device? Email contact@ojosproject.org for support! Ojos Project is the group behind Palliaview and the Iris software. We're here to help.", "mailto:contact@ojosproject.org", "Ojos Project", "DEVICE", 1746601200);"#).unwrap();
}
pub fn setup_onboarding(app: &AppHandle) {
let app_data_dir = app.path().app_data_dir().unwrap();
if !app_data_dir.join("iris.db").exists() {
fs::create_dir_all(app_data_dir.join("recordings/")).unwrap();
get_config(&app);
let conn = Connection::open(app_data_dir.join("iris.db")).unwrap();
conn.execute_batch(&combine_schemas()).unwrap();
preload_content(&conn);
}
}

Operating System

Windows

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions