Jeremy Soller
Jeremy Soller
I'm planning to maintain no_std and wasm support in cosmic-text no matter what happens.
Could someone summarize the issues with cosmic-text that would be blocking its adoption by egui?
I fixed https://github.com/pop-os/cosmic-text/issues/70 recently. I'll be doing a new release of cosmic-text soon that includes this change.
I released a new version of cosmic-text, 0.12.0, with numerous fixes for use by bevy. Please let me know if there is anything I need to do to support egui.
Yes, I am always open to optimizations, and I am tracking some upstream crate issues that cause the duplicate ttf-parser issue.
I can confirm it is fixed, if you want to leave it open I will
This should be fixed in #271, which allows a Buffer to be created without a defined width and size. `Buffer::layout_runs` can then be used to figure out the actual size....
This is a large set of changes, so it is admittedly hard for me to review and approve. If it could be split into a few more PRs, that would...
> Sure! Here are the separated PRs: > > * [Add IME preedit ranges #261](https://github.com/pop-os/cosmic-text/pull/261) > > * [Add Edit::cursor_position #262](https://github.com/pop-os/cosmic-text/pull/262) > > * [Hide cursor based on selection, preedit,...
This is an issue I am interested in working on, but still need some more information on how it would be used by users of cosmic-text.