UI-theory of first understanding, ui-theory of first understanding
A good app not only needs good functions, but also has a good interface, so that both internal and external modifications can be regarded as a good App. In fact, just like people, you can't just be handsome, but have a connotation (to be clear, it doesn't mean cool ). Unconsciously, It has been eight years in the garden, and it has been eight years in depth, and. NET has also been doing this for eight years. I have not written many blog posts over the past few years, so I feel ashamed to think about it. There have been no achievements in the past few years. I am going to switch to mobile Android development. It's not long before I leave... after talking about the UI control, let's continue to talk about the UI control. Here we only talk about the theory. Let's have a good understanding first.
ImageView I believe everyone knows what it is. You can use android: src to specify an image, or use the layout_widht and layout_height attributes to specify the width and height.
ProgressBar: This is a progress bar. You can use visible to control whether to display the progress bar. This is useful. When our data is being loaded, We can display it. After loading, hide it to improve user experience.
AlerDialog can pop up a dialog box on the current interface, which is on top of all the elements of the interface. It can hide the interaction capability of other controls and be used for important content.
ProgressDialog is the same as AlerDialog. This displays a progress bar, which is generally used to wait for a prompt.
Imagebtn image button. It can be divided into several major parts, so we will start learning from tomorrow. Until everyone understands it.