1.6 KiB
1.6 KiB
The Task list for Lumina
- Develop ui for libraries
- Develop ui for settings
- Find a way for text to pass through a service item to a slide i.e. content piece
- Develop library system for slides that are more than images or video i.e. content
- Functions for text alignments
- Use Rich Text instead of normal text for slides
- Find a way to load and discover every font on the system for slide building
- Build library to see all available songs, images, videos, presentations, and slides
- Build editors for each possible item
TODO Develop ui for libraries
TODO Develop ui for settings
TODO Find a way for text to pass through a service item to a slide i.e. content piece
TODO Develop library system for slides that are more than images or video i.e. content
TODO Functions for text alignments
This will need to be matched on for the TextAlignment from the user
TODO Use Rich Text instead of normal text for slides
This will make it so that we can add styling to the text like borders and backgrounds or highlights. Maybe in the future it'll add shadows too.
TODO Find a way to load and discover every font on the system for slide building
This may not be necessary since it is possible to create a font using Box::leak().
let font = self.current_slide.font().into_boxed_str();
let family = Family::Name(Box::leak(font));
let weight = Weight::Normal;
let stretch = Stretch::Normal;
let style = Style::Normal;
let font = Font {
family,
weight,
stretch,
style,
};
This code creates a font by leaking the Box to a 'static &str. I just am not sure if the &str stays around in memory after the view function. If it does, then it's not on the stack anymore and should be fine, but if it isn't cleaned up then we will have a memory leak.
Krimzin on Discord told me that maybe the update method is a better place for this Box to be created or updated and then maybe I could generate the view from there.