-
-
Notifications
You must be signed in to change notification settings - Fork 120
proof‐of‐concept user agent
In order to make a informed decision on which toolkit to use, we need to have a proof-of-concept useragent that can be used to compare the different toolkits. This document describes the requirements for this proof-of-concept.
Can we have a single codebase for multiple platforms (mostly: Linux, OSX, Windows)
This should be optional. It would make more sense to have a native android / ios app.
Does the toolkit support having multiple windows open. Can they "run" in different processes?
Does the toolkit support a tabbed interface, where each tab contains its own render view? Can these tabs be separated as processes?
Can it display a (native) menu bar?
Does it allow dialog and subwindows like a configuration menu etc?
Does it support multiple languages? (can we have text resources in different languages, and can we change the language on-the-fly?)
Does the toolkit support native elements and behaviour you expect from the given platform (resizing, closing, keyboard shortcuts etc)
This section contains a list of all (known) toolkits we like to test and try. Each of them should have a link to a proof-of-concept repository found in the gosub-browser organisation.
| Name | Toolkit 1 |
| Link | https://www.gosub.io |
| Poc Link | https://github.com/gosub-browser/poc-toolkit1 |
| Status | in progress |
(example data)
| Feature | QT | GTK |
|---|---|---|
| Multi platform | yes[^1] | yes |
| Mobile | yes | no |
| Multi window | ||
| Multi tab | ||
| Menu | ||
| Alternate windows | ||
| Multi lingual | ||
| Native elements |
[^1]: QT is multi platform, but the mobile version is a different codebase.