Android Open Source Component Summary _android

Objective

Android 's self-contained components are rather ugly (personal), they're complex to write, and you have to be familiar with some of the Android application-layer development mechanisms, such as drawing and callback, so you don't have to write your own components without compelling, Because it's a matter of performance or abnormality, it takes a lot of time for you to write yourself. I think It's a good choice to adopt a Third-party UI, especially if you need more complex UI components, and you're more in the rush.

Disadvantages

Of course, third-party UI components are not all good, the personal summary is as follows: (certainly far more than that, welcome to discuss)

Advantages: Good scalability, more general (of course, there are bad writing, not discussed here), easy to use, development speed.

Cons: Most are not as stable as Google's official components, and there are even minor problems. Once you have a problem debugging it is very troublesome. Performance needs to be improved.

Share several excellent open source third party projects

1, Greendroid

Demos Effect Chart:

Use experience

Personally, it's not easy to use this project, especially if you have to inherit gdapplication when you use the activity he provides . (Beginning not to know these, debugging for a long time). In fact , the UI interface is also very general, and most of the functions inside can be found in other Third-party libraries to find similar. Inside the actionbar default style is very general, to be beautified.

If you need more information, you can go to the official to see: http://android.cyrilmottier.com/?p=240

2, Actionbarsherlock

Demos Effect Chart:

Personal experience

The UI for this project is beautiful and easy to use,demos provides a good example of reference. Actionbar can be implemented on a lower version (the Actionbar of the system is above 3.0).

If you need more information, you can go to the official to see:http://actionbarsherlock.com/

3, Slidingmenu

Demos Effect Chart:

Personal experience

You need to use the push-pull effect, this is a good project. But you may not be able to use it directly, it is dependent on the Actionbarsherlock project. There is also a problem in the code that needs to be changed to inherit Sherlockfragmentactivity (that is, actionbarsherlock in the slidingfragmentactivity). Because this question I also looked for for a long time did not solve (has not doubted the code problem), then really did not look at the code to discover.

If you need more information, you can go to the official to see:https://github.com/jfeinstein10/SlidingMenu

Attention matters

The referenced project must be placed in the same hard disk partition as the referenced item, such as your new project test, you need to reference Actionbarsherlock, then test and Actionbarsherlock need to be placed in the same partition, that is, at the same time in D or E disk. It's been a long time since the problem, and the details are very important.

Summarize

Of course, excellent UI open source projects are far more than these, but these are very useful and very famous. Others are android-misc-widgets, Quickaction, Viewbadger, Viewflow ... Too much. According to the personal need to understand it. Okay, so that's it, if you need it, you can just sort out a few of the UI components you've been talking about.

PS: There are some irregularities in the article please note that the reader is welcome to exchange.