-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
f001b5a
commit f04aced
Showing
1 changed file
with
20 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1 +1,21 @@ | ||
# Native EMWebKit : A Retrospective | ||
|
||
Project Status: Development Halted | ||
|
||
## Project Objective | ||
- The Native EMWebKit project aimed to provide a seamless interface for developers to create GUI applications that leverage native webviews on various systems. By integrating with the system’s webview, developers could effortlessly incorporate web content into their applications. | ||
|
||
## Key Focus Areas | ||
- Native EMWebKit acted as a bridge between applications and the native webview. with one difference than EMWebKit and its having no dependency like whole Chromium project | ||
|
||
## Challenges Encountered | ||
### Quality of Microsoft Edge WebView2: | ||
- Initially, the project relied on the Microsoft Edge WebView2 runtime in Windows. | ||
- Unfortunately, issues related to stability, rendering, and performance hindered progress. | ||
|
||
### Performance Considerations: | ||
- Slow loading times and suboptimal rendering affected the overall user experience. | ||
- The project needed a more robust solution. | ||
|
||
## A New Beginning | ||
- In response to these challenges, a new version of EMWebKit emerged—one powered by the Chromium project. This revamped approach aimed to address limitations and provide a better solution for cross-language GUI development. |