Skip to content
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

Fixup crazy font sizes in the app switcher #42

Merged
merged 1 commit into from Jan 31, 2016

Conversation

piggz
Copy link
Contributor

@piggz piggz commented Jan 30, 2016

No description provided.

@locusf
Copy link
Member

locusf commented Jan 31, 2016

Thank you!

locusf added a commit that referenced this pull request Jan 31, 2016
Fixup crazy font sizes in the app switcher
@locusf locusf merged commit 1f90803 into nemomobile-ux:master Jan 31, 2016
@faenil
Copy link

faenil commented Feb 1, 2016

we should fix ButtonStyle, if that needs fixing :/

@piggz
Copy link
Contributor Author

piggz commented Feb 1, 2016

OK, I'll take a look..i dont want to break any other applications though. Do we need these custom components on top of standard qt?

@faenil
Copy link

faenil commented Feb 1, 2016

what do you mean?

yes, Glacier UI components are currently using QtQuickControls1, and we have qtquickcontrols-nemo where all the style files live.

(The plan is to move to QtQuickControls2 as a base)

@piggz
Copy link
Contributor Author

piggz commented Feb 1, 2016

I meant why are glacier components needed a all?

@piggz
Copy link
Contributor Author

piggz commented Feb 1, 2016

I guess they are analogous to silica, but it seems like extra burden to maintain on top of qtquick controls.... devs have a target them specifically...from an app writing perspective it seems easier to have a common set of components to develop against

@faenil
Copy link

faenil commented Feb 1, 2016

And then you have to convince everyone to develop using your new unitified components interface? :)
this problem is hard and it's been discussed multiple times on Qt ML as well...

Please note: Glacier components are just QQC+styling (and some extra component), so apps using QQC will just run. If they want the special glacier header (which is not a QQC component) they they'll have to add it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants