saulmm / coordinatorexamples Goto Github PK
View Code? Open in Web Editor NEWDifferent CoordinatorLayout usages, tips & examples
Home Page: http://saulmm.github.io/mastering-coordinator
License: Apache License 2.0
Different CoordinatorLayout usages, tips & examples
Home Page: http://saulmm.github.io/mastering-coordinator
License: Apache License 2.0
When you update support libraries to 24.0.0, Flexible Space Example will stop working properly. If you scroll fast, the CardView will be displayed under the AppBarLayout for some time which makes annoying snatchy effect. I think it might have something to do with the elevation of CardView and AppBarLayout. It seems that it is working well on older versions of support libraries. See attached video.
In MaterialUpConceptActivity,the scroll flag of Toolbar is "scroll|enterAlways|snap",so it should be pulled down before RecyclerView scroll, but there is a layout_marginTop in Toolbar,it make Toolbar only be pulled partly.I think we should remove the layout_marginTop in Toolbar.Instead we can add "android:layout_marginBottom="-48dp"" in CircleImageView
Can i get details view
like Iflix movie app
Hi,
Regards your example of "Material up profile example"
When using support library 25.4.0:
If you scroll down (Only tabs are pinned to top), and then scroll up you see that the title container is showing - which is the correct behavior.
Now upgrade your support library to > 26.0.0
When you scroll up - everything is being shown
Appreciate if you can suggest with this
While dragging, the card does not move. Anyone else seeing this? Tested it on Android 7.
I'm using MaterialUpConcept, but when I change the fragment using a custom layout, it doesn't scroll anymore. Could you help me?
Hello, I tried one of your tutorial demo app that is simple coordinator example.. The one having nested scrolling view. I understood everything but one thing that why have you used "main.*" (main.appBar,main.collapsing,etc) ids in your xml? Actually I did not use main word in any of the xml element ids. And I am having a problem with the floating action button. The FAB is there in the blueprint but it is not showing up in the design screen in studio. Meaning, that the "app:layout_anchor" attribute is not letting it come up on the screen and when I remove it then it is visible. Can you please guide me why is that so??
This is how I have written my xml code for FAB:
<android.support.design.widget.FloatingActionButton
android:id="@+id/fab"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
android:layout_margin="@dimen/activity_horizontal_margin"
android:src="@drawable/ic_done"
app:layout_anchor="@id/appbar"
app:layout_anchorGravity="bottom|right|end" />
Bellow is the image/link of how it looks:
Please help!
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.