3 ms·
Longer-term, we need to move to browser-native GUI, yep. The nice bits though - the entire document loading, rendering & editing works in the browser now.
by thorstenb 5y ago
Longer-term, we need to move to browser-native GUI, yep. The nice bits though - the entire document loading, rendering & editing works in the browser now.
- vasvir 5y agoWhat that means though? A VCL backend that targets HMTL5 instead of Qt? Can you elaborate?
- thorstenb 5y agoWe already use cairo/freetype/skia to do essentially all the document rendering in software (not for the Qt prototype though), so that's not a big leap to get that blitted out. Incrementally then using more of html canvas to speed things up might be next. Most of the work is going to be having the GUI (toolbar/notebook bar, menues, sidebar, dialogs) browser-native of course.
- anonymouse008 5y agoI’ve been seriously impressed with Tokamak for Swift. Is this what you mean for browser native GUI? https://github.com/TokamakUI/Tokamak https://github.com/TokamakUI/Tokamak