Page MenuHomePhorge

Extract action groups into separate QML files
Needs ReviewPublic

Authored by nannanko on Sat, Aug 22, 11:02 PM.
Tags
None
Referenced Files
F85646476: D358.1787648140.diff
Mon, Aug 24, 1:55 AM
F85646475: D358.1787648120.diff
Mon, Aug 24, 1:55 AM
F85646262: D358.1787617755.diff
Sun, Aug 23, 5:29 PM
F85646255: D358.1787617662.diff
Sun, Aug 23, 5:27 PM
F85646249: D358.1787617632.diff
Sun, Aug 23, 5:27 PM
Subscribers
None

Details

Reviewers
tusooa
Group Reviewers
O1: the Kazv Project
Summary

Extract action groups into separate QML files. No behavior changed intended.

Type: skip

Test Plan

Verify unit tests pass.

Diff Detail

Repository
rK kazv
Branch
nannanko/stacked
Lint
No Lint Coverage
Unit
No Test Coverage
Build Status
Buildable 711
Build 1404: Invoke BuildbotBuildbot build #2549
Build 1403: arc lint + arc unit

Event Timeline

Harbormaster returned this revision to the author for changes because remote builds failed.Sat, Aug 22, 11:04 PM
Harbormaster failed remote builds in B709: Diff 1095!

Finally, it does not seem to me that the shortcuts directory is suitable for individual actions. I feel it is a directory to provide tools to interact with actions rather than actions themselves.

src/contents/ui/Main.qml
228–242

This looks a little bit messy. We can reduce the duplication by changing ActionCollection's children property's type to list<QtObject> and directly specify

children: [KazvShortcuts.GlobalDrawerActions {}, ...]

It would be also good to put the list of children in its own file, say AllActions.qml:

KazvShortcuts.ActionCollection {
  children: [...]
}

and in Main.qml, define the actionCollection to be

AllActions {
  shortcutsConfig: kazvConfig
}
src/contents/ui/shortcuts/BubbleActions.qml
12

I think it will be more appropriate to use an ActionColection here.

Use ActionCollection instead of QtObject