Switching to CEF
Nobody has claimed this yet.
- Dominant language
- Objective-C++
- Stars
- 2.7k
- Forks
- 734
- Avg merge
- 11h 39m
- Merged PRs (30d)
- 1
Description
Hey @KojiNakamaru,
Seeing some problems, incomplete platform support (no Windows and no Linux) and somewhat poor performance, I was wondering if we should start looking into CEF as a definitive answer to most (if not all) of them?
I know you said you might not have time for that but I was wondering what you think would be the steps to make the full switch. Having some sort of checklist, would make it easier for you and other people to work on this task, which I think is very important to make this project be even more useful.
Let me know :)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue mentions switching unity-webview to CEF because of incomplete Windows and Linux support and poor performance, but names no files, tests, or entry points. Start by mapping the existing platform integrations and CEF's integration requirements; done would be a concrete migration checklist covering the supported platforms and performance concerns.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, objective-c
- Domain
- desktop-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100