-
Notifications
You must be signed in to change notification settings - Fork 54
WIP: Maliit 3 major refactoring #108
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
dobey
wants to merge
13
commits into
maliit:master
Choose a base branch
from
dobey:maliit-3-refactor
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
8eae0f1
Remove MImPluginSettingsInfo and AbstractPluginSetting
dobey beb3bc9
Drop the setLanguage API as keyboard language is plugin side
dobey 177ad9e
Remove MaliitSettingsEntry usage and settingdata.{cpp,h}
dobey b9069a2
Remove SettingEntryType
dobey 6ce3506
Remove toolbar API and docs
dobey cfaaec2
Remove attribute extensions API
dobey 1454967
Remove extended attribute API
dobey 25cb39a
glib: Remove the plugin settings API from maliit-glib
dobey 248c2de
glib: Remove AttributeExtension API from maliit-glib
dobey 489a8e2
tests: Fix the mimpluginmanager plugin switcher test
dobey ac95819
Separate the library version from the project version
dobey e81c810
Add FormattedNumberContentType separate from NumberContentType
dobey 57b17c2
Remove MImExtensionEvent and related API
dobey File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pondering if we should just use Qt::inputMethodHint which offers more types and hint combinations.
On the history side not entirely sure did we even add this before Qt got that hint of its own.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure how much sense it makes, because the Wayland protocols are so unstable right now, and Phosh devs keep trying to push their own changes which break the existing protocols, and Qt::InputMethodHints doesn't have flags for everything, so I can only see it getting more complicated to keep updated, along with I don't want to have to block on getting things into Qt, maybe backported, etc… if we want to add anything else in the future.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could alternatively be a similar enum. But then again Qt::InputMethodHints should not block adding new extensions, those can be presented with other properties. We already do pass the content type here but also the input method hints.
Actually looks like I've halfway marked this as deprecated in 2013 with the Qt5 port. minputcontext.cpp / MInputContext::getStateInformation()
Also curious on what those wayland changes would be. The input hint side has seemed relatively stable for many years.