After 5 years of being an Android Dev I still don't fully understand how theming and styles work. But after watching the video it seems to be getting more clear
@ekoprasetyo3999
2 жыл бұрын
Finally, after a long time learning styles and theming. I still can't figure out why my text color doesn't want to change .💀
@kunalmehta923
5 жыл бұрын
Can you please share one demo for explaining the same. It will be very helpful.
@vit.khudenko
4 жыл бұрын
This is usually such a pain on a typical project where designers use tools that do not support Android theming/styling model. So we, developers, just have to deal with hard-coded colors and sizes. Ok, that would not be such a problem, but usually mockups are not consistent across screens.
@AbhishekBansal14
5 жыл бұрын
Good Talk! Theming and Styling is one area of Android which is overly complex, poorly documented and very less understood. This talk tries to throw light on those grey areas to some extent.
@kalidsherefuddin
9 ай бұрын
Thanks for
@stefannaumoski5151
2 жыл бұрын
You mentioned Primary Light as a replacement for onPrimary, but here we are 4 years later and jetpack compose uses onPrimary... What gives?
@pedromassango
5 жыл бұрын
How we can switch to dark mode via code?
@Verrisin
3 жыл бұрын
Honestly, I wish android had just used some subset of CSS ... it's proven to work well, fast ... the resource/style system they have is ... well, sad to say the least. Very confusing, full of duplication... I've looked through the material library, and it's just *_painful._*
@Verrisin
3 жыл бұрын
I'm not saying CSS is perfect. By no means. But definitely better. Especially with variables (which, I think is what they wanted, and CSS did not have have the mat all, when Android started, but still) - With CSS one can use SASS etc. (- could be a variant for Android, that can get compiled to resources) - But resources have many issues: they are only read while inflating, and there is no way to 'change' 'style' of a parent, such that it would influence children (i.e. adding to 'class' of a layout), etc...
@Verrisin
3 жыл бұрын
I hope styling will get somewhat fixed for Compose...
@nfaical3
3 жыл бұрын
100% right, take for example ReactNative styling
@abdulazizabduqodirov4348
4 жыл бұрын
So how we can switch between themes?
@mg-ht9ir
4 жыл бұрын
Did you find it bro..?
@abdulazizabduqodirov4348
4 жыл бұрын
@@mg-ht9ir I've re-created the Activity, otherwise we should update every ui I think
@mukhtarbimurat5106
5 жыл бұрын
Could anyone explain what was the problem when we set style to only one button via "style attribute on Button in layout XML"? 13:30
@Verrisin
4 жыл бұрын
So, I watched this talk, finally thought I understand it, tried it.... _aaand_ I don't. XD oh well.
@felipepereira3061
4 жыл бұрын
Not alone dude...
@samsulkarim164
3 жыл бұрын
Yes, tough stuff. Try to example GitHub project tho...
@Verrisin
3 жыл бұрын
@@samsulkarim164 Honestly, I wish android had just used some subset of CSS ... it's proven to work well, fast ... the resource/style system they have is ... well, sad to say the least. Very confusing, full of duplication... I've looked through the material library, and it's just *_painful._*
@jan1337
5 жыл бұрын
wait, wait, wait, wait! on the slide @ 18:50 - android:fillColor="?attr/colorPrimary" does crash on pre-21 devices, doesn't it?
@aIexjI
5 жыл бұрын
You can safely use theme attributes inside of AnimatedVectorDrawableCompat and VectorDrawableCompat XML files. The reason why it doesn't crash is because the vector support library parses the XML drawable files as plain text in order to create a "compat" implementation that will work on older platforms.
@NickButcher
5 жыл бұрын
Nope, VectorDrawableCompat supports theme colors on all platform levels.
@verdurakh
5 жыл бұрын
How can I use ?attr with conditionals in the xml? for example textColor=@{if foo ?attr/blue : ?attr/red} seems to only allow @ sematics in there?
Пікірлер: 28