在线观看亚洲一区,国产偷国产偷亚洲高清97cao,久久国产精品高清一区二区三区

Android Application Architecture 安卓APP架构[译]

paulwong — Fri, 18 Dec 2015 05:07:00 GMT

�?/h2>
本文介绍�?ji��n)文章作者从事了(ji��n)几年android应用的开发，�l�历2�ơ架构变革，�W�一�ơ集成了(ji��n)RxJava�W�二�ơ集成了(ji��n)MVP�Q��ƈ��RxJava与MVP完美�l�合�Q�实��C��(ji��n)低耦合�Q�代码简单，��试方便的架构�?/p>
其实我们在开发中也遇到过�Q�Android入门门槛较低�Q�如果前期对APP规划不清晎ͼ�Coder们对未来变化把握不准�Q�技术架构经验不够强大，最�l�导致就是一个Activity几千行，里面写了(ji��n)大量的Private�Ҏ(gu��)��Q�拆成几个Fragment、封装出来几个类都是无法解决�Q�结果就是看Activity隑֏�的要死，�U�结�Q�看�?ji��n)不爽改也不是不改也不是�Q�严重媄(ji��ng)响看的�h的心(j��)情。�ƈ且怨天��h�q�个是��品�h员规划App不好�Q�没有前��L��，�Ҏ(gu��)��改去。。�?/p>
�q�篇文章��是使用新的�l�构解决该问题�?/p>

安卓APP架构

Android Application Architecture

Our journey from standard Activities and AsyncTasks to a modern MVP-based architecture powered by RxJava.

�q�篇文章主要目的是讲�q�如何将传统的Activities �?AsyncTasks 模式向目前主��的MVP架构基础的响应式�~�程框架�q�度�?/p>

Different parts of a software codebase should be independent, yet perfectly work together like a well-oiled machine — photo by Chester Alvarez.

先畅享一下：(x��)~~~如果松耦合架构�Q�分工明��，然后完美的组合在一起工作是一个很吊的事情�?br style="padding: 0px; margin: 0px;" />�Q��{个图片还要写明白谁拍的，版权意识真强�Q?/p>

The Android dev ecosystem moves very quickly. Every week new tools are created, libraries are updated, blog posts are written and talks are given. If you go on holiday for a month, by the time you come back there will be a new version of the support library and/or Play Services.

最�q�几�q�Android的生态链变化非常�q�速，从底层的Android Api到应用层的各�U�开源的�c�d��、工��h��新非常迅速。一不留��就落后�?ji��n)�?/p>

I’ve been making Android apps with the ribot team for over three years. During this time, the architecture and technologies we’ve used to build Android apps have been continuously evolving. This article will take you through this journey by explaining our learnings, mistakes and the reasoning behind these architectural changes.

我在Ribot团队从事Android应用开发工作三�q�多�Q�伴随着公司技术的不断创新�Q�积累了(ji��n)很多�l�验、错误以�?qi��ng)在技术选型背后的故事�?/p>

旧的应用架构

The old times
Back in 2012 our codebases used to follow a basic structure. We didn’t use any networking library and AsyncTasks were still our friends. The diagram below shows approximately how the architecture was.

2012�q�那个时候，我们的代码都是用的原生Android�Q�没有��用�Q何的�|�络��h��框架�Q�而是��Z��AsyncTasks书写�?br style="padding: 0px; margin: 0px;" />>The code was structured in two layers: the data layer that was in charge of retrieving/saving data from REST APIs and persistent data stores; and the view layer, whose responsibility was handling and displaying the data on the UI.
The APIProvider provides methods to enable Activities and Fragments to easily interact with the REST API. These methods use URLConnection and AsyncTasks to perform network calls in a separate thread and return the result to the Activities via callbacks.

代码分�ؓ(f��)两层�Q�Data与View,Data层主要是用来从API获取数据�Q�保存到持久化的db当中。View层主要就是把Data的数据显�C�到UI上。APIProvider提供�Ҏ(gu��)��出来�Q�用于在Activity或者Fragment中方便的�q�行控制与交互。技术上��，使用URLConnection与AsyncTasks实现�?ji��n)一个异步的�|�络��h��q�将�l�果�q�回到调用的回调�Ҏ(gu��)��里面�?/p>

In a similar way, the CacheProvider contains methods that retrieve and store data from SharedPreferences or a SQLite database. It also uses callbacks to pass the result back to the Activities.

相同的原理CacheProvider提供一�p�d��Ҏ(gu��)��Q�将SharedPreferences或者SQLite的数据取出来�Q��ƈ且返回给到Activity

问题

The problems
The main issue with this approach was that the View layer had too many responsibilities. Imagine a simple common scenario where the application has to load a list of blog posts, cache them in a SQLite database and finally display them on a ListView. The Activity would have to do the following:

主要问题是View层有太多的篏赘，以一个博客列表�ؓ(f��)例来讲述�Q�比如博客需要显�C�Z��个ListView�Q�从SQLite��d��数据�Q�Activity需要做��C��下几点：(x��)

Call a method loadPosts(callback) in the APIProvider
Wait for the APIProvider success callback and then call savePosts(callback) in the CacheProvider.
Wait for the CacheProvider success callback and then display the posts on the ListView.
Separately handle the two potential errors callback from the APIProvider and CacheProvider.

执行APIProvider里面的loadPosts的方法，里面传入回调参数内容�?/li>
�{�待loadPosts执行成功后，执行回调里面的CacheProvider中的savePosts�Ҏ(gu��)��Q�savePosts也要传入回调参数�?/li>
�{�待savePosts执行成功后，执行回调里面的方法刷新ListView
分别书写代码处理2 3 两步的错误回调内宏V�?/li>

This is a very simple example. In a real case scenario the REST API will probably not return the data like the view needs it. Therefore, the Activity will have to somehow transform or filter the data before showing it. Another common case is when the loadPosts() method takes a parameter that needs to be fetched from somewhere else, for example an email address provided by the Play Services SDK. It’s likely that the SDK will return the email asynchronously using a callback, meaning that we now have three levels of nested callbacks. If we keep adding complexity, this approach will result into what is known as callback hell.

�q�还是一个比较简单的例子�Q�在一些真实的场景中，�q�程的API可能没有�q�回�E�序的必��d��|��但是activity必须把数据处理完成之后才能显�C�结果。再一个例子就是如果loadPosts�Ҏ(gu��)��需要借助一些其他地方的�q�回参数�Ӟ��c�M��用多�U�程��d��现同步请求，��Z��证数据正常请求，意味着必须做一个三层的回调�Q�如果再复杂一些，想理清楚�q�些回调?y��u)��是很蛋疼的事情�?/p>

In summary:
Activities and Fragments become very large and difficult to maintain
Too many nested callbacks means the code is ugly and difficult to understand so painful to make changes or add new features.
Unit testing becomes challenging, if not impossible, because a lot of the logic lives within the Activities or Fragments that are arduous to unit test.

��M��Q�回调多�?ji��n)之后，Activity与Fragment�?x��)�ؕ的要死，�q�且一般�h无法直视�?/p>

牛逼的新架构出来了(ji��n)

A new architecture driven by RxJava
We followed the previous approach for about two years. During that time, we made several improvements that slightly mitigated the problems described above. For example, we added several helper classes to reduce the code in Activities and Fragments and we started using Volley in the APIProvider. Despite these changes, our application code wasn’t yet test-friendly and the callback hell issue was still happening too often.

我们在蛋疼的架构中煎熬了(ji��n)2�q�_(d��)��当然也尝试过很多方式�Q�最�l�也只能是缓和一下�ؕ的问题。我们在APIProvider使用�?ji��n)Volley�Q�代替了(ji��n)AsyncHttpClient�Q�但是其实是一个吊栗��?/p>

It wasn’t until 2014 when we started reading about RxJava. After trying it on a few sample projects, we realised that this could finally be the solution to the nested callback problem. If you are not familiar with reactive programming you can read this introduction. In short, RxJava allows you to manage data via asynchronous streams and gives you many operators that you can apply to the stream in order to transform, filter or combine the data.

不到2014�q�我们就开始进行RxJava的预研，然后��试�?ji��n)一批简单的��目�Q�感觉RxJava的方式是解决我们嵌套回调的终极解军_��法。简单的��_(d��)��RxJava允许你通过异步��的方式��理你的数据�Q��ƈ且还可以通过操作�W�（Operators�Q�对Observable对象的变�?/p>

Taking into account the pains we experienced in previous years, we started to think about how the architecture of a new app would look. So we came up with this.

我们用了(ji��n)几年的经验痛定思痛�Q�搞�?ji��n)下面这么个东西�Q�新的APP的架构图

Similar to the first approach, this architecture can be separated into a data and view layer. The data layer contains the DataManager and a set of helpers. The view layer is formed by Android framework components like Fragments, Activities, ViewGroups, etc.

与第一�U�方法相��|��q�个架构也是分�ؓ(f��)Data层与View层，Data层包含DataManager与一堆Helper�Q�View层是包含Fragments, Activities, ViewGroups�{��?/p>

Helper classes (third column on diagram) have very specific responsibilities and implement them in a concise manner. For example, most projects have helpers for accessing REST APIs, reading data from databases or interacting with third party SDKs. Different applications will have a different number of helpers but the most common ones are:

Helper主要是集成第三方的类库，以便于在代码中几行代码就可以清晰的实现某个功能，比如��h��API�Q�访问数据库�{�，虽然不同的应用程序都有不同的�c�d��Q�但是他们无非就是以下这些内容：(x��)

PreferencesHelper: reads and saves data in SharedPreferences.
DatabaseHelper: handles accessing SQLite databases.
Retrofit services: perform calls to REST APIs. We started using Retrofit instead of Volley because it provides support for RxJava. It’s also nicer to use.

从SharedPreferences中读取或者写入数�?/li>
��d��SQLite数据�?/li>
�c�M��与square的Retrofit服务�Q�也��是Http Client,我们用Restrofit替代�?ji��n)Volley因�ؓ(f��)他支持Rxjava,�q�且更吊�?/li>

Most of the public methods inside helper classes will return RxJava Observables.
The DataManager is the brain of the architecture. It extensively uses RxJava operators to combine, filter and transform data retrieved from helper classes. The aim of the DataManager is to reduce the amount of work that Activities and Fragments have to do by providing data that is ready to display and won’t usually need any transformation.

RxJava最核心(j��)的两个东西是Observables�Q�被观察者，事�g源）(j��)和Subscribers�Q�观察者）(j��),在Helper�c�M��的Public�Ҏ(gu��)��Q�一般都�?x��)返回一个RxJava的Observables;DataManager是整个架构的大脑�Q�他大量的��用Rxjava的operators对Helper�q�回来的数据�q�行的整合过滤、二�ơ处理�?/p>

The code below shows what a DataManager method would look like. This sample method works as follows:

下面用一个例子来说明DataManager是做什么的:

Call the Retrofit service to load a list of blog posts from a REST API
Save the posts in a local database for caching purposes using the DatabaseHelper.
Filter the blog posts written today because those are the only ones the view layer wants to display.

调用Retrofit的服务，去请求一个博客列表的API
用DatabaseHelper保存�q�些数据到数据库
�q��o(h��)�?gu��)��些BLOG哪些是今天写的，然后昄��到UI界面上�?/li>

Components in the view layer such as Activities or Fragments would simply call this method and subscribe to the returned Observable. Once the subscription finishes, the different Posts emitted by the Observable can be directly added to an Adapter in order to be displayed on a RecyclerView or similar.

Observables发出一�p�d��事�g�Q�Subscribers�Q�例�?Activities or Fragments�Q�处理这些事�?可以直接��数据显�C�到一些可以回收、重用的View上面�?br style="padding: 0px; margin: 0px;" />【BTW:如果一个Observerble没有��M��的的Subscriber�Q�那么这个Observable是不�?x��)发��Z�Q何事件的�?/p>

The last element of this architecture is the event bus. The event bus allows us to broadcast events that happen in the data layer, so that multiple components in the view layer can subscribe to these events. For example, a signOut() method in the DataManager can post an event when the Observable completes so that multiple Activities that are subscribed to this event can change their UI to show a signed out state.

�q�个架构的另外一个模块是event bus�Q�event bus可以让我们在Data层发出广播（不是Android的Broadcast�Q�然后不同的模块��L��册�ƈ接收不同的广播事�?/p>

Why was this approach better?
RxJava Observables and operators remove the need for having nested callbacks.

��Z��么这个方式这么牛��|��是因为Observables与operators可以��L��那一堆必��ȝ��回调�Ҏ(gu��)��

The DataManager takes over responsibilities that were previously part of the view layer. Hence, it makes Activities and Fragments more lightweight.
Moving code from Activities and Fragments to the DataManager and helpers means that writing unit tests becomes easier.

DataManager替代�?ji��n)传�l�架构中很多代码�Q�从而��得Activity与Fragment变得更加轻量�U�。�ƈ且��得单元测试变得更加简单�?/p>

Clear separation of responsibilities and having the DataManager as the only point of interaction with the data layer, makes this architecture test-friendly. Helper classes or the DataManager can be easily mocked.

DataManager成�ؓ(f��)�?ji��n)唯一的数据交互部分，�q�样清晰的架构��得更方便�q�行代码自测�?/p>

What problems did we still have?
For large and very complex projects the DataManager can become too bloated and difficult to maintain.
Although view layer components such as Activities and Fragments became more lightweight, they still have to handle a considerable amount of logic around managing RxJava subscriptions, analysing errors, etc.

我们�q�有什么问题？
- 如果对于非常庞大�q�且复杂的项目来��_(d��)��DataManger也会(x��)变得非常臃肿�q�且难以�l�护�?br style="padding: 0px; margin: 0px;" />- ��管Activity与Fragment已经变得更加轻量�U�，但是对于错误异常的处理还是要在subscriptions的地方去书写�?/p>

一体化的MVP模式

Integrating Model View Presenter
In the past year, several architectural patterns such as MVP or MVVM have been gaining popularity within the Android community. After exploring these patterns on a sample project and article, we found that MVP could bring very valuable improvements to our existing approach. Because our current architecture was divided in two layers (view and data), adding MVP felt natural. We simply had to add a new layer of presenters and move part of the code from the view to presenters.

前几�q�开始，很多�c�M��MVP与MVVM在Android的一些社区比较流行，�l�过研究之后�Q�我们发现MVP模式是对我们目前的方案最有�h(hu��n)值的改动。我们的两层架构View-Data与MVP�?Model-View架构天然融合�Q�理念一致。我们只需要增加一个presenters层，然后把之前在view实现的代码移��C��面就可以�?ji��n)�?br style="padding: 0px; margin: 0px;" />

The data layer remains as it was but it’s now called model to be more consistent with the name of the pattern.
Presenters are in charge of loading data from the model and calling the right method in the view when the result is ready. They subscribe to Observables returned by the data manager. Therefore, they have to handle things like schedulers and subscriptions. Moreover, they can analyse error codes or apply extra operations to the data stream if needed. For example, if we need to filter some data and this same filter is not likely to be reused anywhere else, it may make more sense to implement it in the presenter rather than in the data manager.

之前的Data层就是现在的MVP中的Model�Q�Presenter现在负责从Model中加载数据，加蝲完成后后再去调用左边的在Activity、ViewGroup中的�Ҏ(gu��)��。Presenters的subscribe��L��收data manager中的Observables�q�播出来的数据�?br style="padding: 0px; margin: 0px;" />举例说明�Q�如果我们需要增加数据的�q��o(h��)操作但是�q�不是所有地斚w��需要的那种�Q�那��可以在presenter里面写这些代码，而不用写在公��q��datamanager里面�?/p>

Below you can see what a public method in the presenter would look like. This code subscribes to the Observable returned by the dataManager.loadTodayPosts() method we defined in the previous section.

我们定义的dataManager.loadTodayPosts()�?x��)广播出数据�l�到对应的subscribes

The mMvpView is the view component that this presenter is assisting. Usually the MVP view is an instance of an Activity, Fragment or ViewGroup.

MVP的View�q�不是指的Android的View�Q�而是一个界面组件的的实例，例如Activity, Fragment �Q?ViewGroup 在注册presenter的时候，需要把自己当前的实例传递进厅R�?/p>

// Activity onCreate 中的代码�D? if (presenter == null)         presenter = new Presenter1();         presenter.onTakeView(this);

Like the previous architecture, the view layer contains standard framework components like ViewGroups, Fragments or Activities. The main difference is that these components don’t subscribe directly to Observables. They instead implement an MvpView interface and provide a list of concise methods such as showError() or showProgressIndicator(). The view components are also in charge of handling user interactions such as click events and act accordingly by calling the right method in the presenter. For example, if we have a button that loads the list of posts, our Activity would call presenter.loadTodayPosts() from the onClick listener.

�q�个架构与上一个架构不同的是，ViewLayer 也就是Activity�q�些�Q�不�?x��)直接去订阅接收Observables发出的这些事件。而是只在Activity实现几个��单的昄��错误、显�C��度的�Ҏ(gu��)��Q�用接口interface来规范统一�Q�，然后把当前实例以参数形式传递给到对应事件的Presenter�Q�由Presenter��L��行这些显�C�错误、显�C��度的�Ҏ(gu��)��?br style="padding: 0px; margin: 0px;" />当然对于用户交互部分的按钮点��M��件还是要在Activity中进行处理�?/p>

If you want to see a full working sample of this MVP-based architecture, you can check out our Android Boilerplate project on GitHub. You can also read more about it in the ribot’s architecture guidelines.

关于MVP的文章可以自行百度一下，MVP Android 关键�?/p>

Why is this approach better?

��Z��么这个又最�?/strong>

Activities and Fragments become very lightweight. Their only responsibilities are to set up/update the UI and handle user events. Therefore, they become easier to maintain.
We can now easily write unit tests for the presenters by mocking the view layer. Before, this code was part of the view layer so we couldn’t unit test it. The whole architecture becomes very test-friendly.
If the data manager is becoming bloated, we can mitigate this problem by moving some code to the presenters.

Activity与Fragment代码量大大降低，逻辑代码全部都丢�l�了(ji��n)Presenter,�l�果��是Activity只需要负责UI交互的按钮等代码�?/li>
对于Presenter可以写单独的单元��试代码�Q�只需要对Presenter提供的方法测试即�?/li>
如果DataManager变得臃肿庞大�?ji��n)，我们可以分离�q�些代码到各自的Presenter中去�?/li>

What problems do we still have?
现在�q�有遗留什么问�?/strong>
Having a single data manager can still be an issue when the codebase becomes very large and complex. We haven’t reached the point where this is a real problem but we are aware that it could happen.

只有一个DataManager仍旧是一个问题，��其是当代码��目比较庞大的时候，当然我们�q�没有到达这个庞大的地步�Q�尽��我们知道这个将来某天会(x��)发生�?/p>

It’s important to mention that this is not the perfect architecture. In fact, it’d be naive to think there is a unique and perfect one that will solve all your problems forever. The Android ecosystem will keep evolving at a fast pace and we have to keep up by exploring, reading and experimenting so that we can find better ways to continue building excellent Android apps.

如果��x��个完��的架构解决你所有问题是不可能的。TMD Android的整个生态圈变化太快�Q�又TM的不标准�Q�就��D��我们不断的去探烦(ch��)探烦(ch��)。。。以致于��L��到更吊的�Ҏ(gu��)��d��Android apps�?/p>

I hope you enjoyed this article and you found it useful. If so, don’t forget to click the recommend button. Also, I’d love to hear your thoughts about our latest approach.

希望��M��(ji��n)之后�Ҏ(gu��)��们的最新解��x��案能有些��x��?/p>

【本文翻译的目的是在闲暇旉��Q�研�I�新技术，用通俗技术语�a�写给自己看，便于日后方便查阅为目�?br style="padding: 0px; margin: 0px;" />原文�Q?a style="padding: 0px; margin: 0px; color: #ff8373; outline: 0px; font-size: 12px;">https://medium.com/ribot-labs/android-application-architecture-8b6e34acda65
MVP介绍�Q?a style="padding: 0px; margin: 0px; color: #ff8373; outline: 0px; font-size: 12px;">http://www.jcodecraeer.com/a/anzhuokaifa/androidkaifa/2015/0425/2782.html
RxAndroid:https://github.com/ReactiveX/RxAndroid
Eventbus:https://github.com/greenrobot/EventBus

paulwong 2015-12-18 13:07 发表评论

paulwong — Wed, 09 Jul 2014 08:56:00 GMT
1、volley

��目地址 https://github.com/smanikandan14/Volley-demo
(1) JSON�Q�图像等的异步下载；
(2) �|�络��h��的排序（scheduling�Q?br /> (3) �|�络��h��的优先��处理
(4) �~�存
(5) 多��别取消请�?br /> (6) 和Activity和生命周期的联动�Q�Activity�l�束时同时取消所有网�l�请求）(j��)

2、android-async-http

��目地址�Q�https://github.com/loopj/android-async-http
文档介绍�Q�http://loopj.com/android-async-http/
(1) 在匿名回调中处理��h��l�果
(2) 在UI�U�程外进行http��h��
(3) 文�g断点上传
(4) ��重试
(5) 默认gzip压羃
(6) 支持解析成Json格式
(7) 可将Cookies持久化到SharedPreferences

3、Afinal框架

��目地址�Q�https://github.com/yangfuhai/afinal
主要有四大模块：(x��)
(1) 数据库模块：(x��)android中的orm框架�Q��用了(ji��n)�U�程池对sqlite�q�行操作�?br /> (2) 注解模块�Q�android中的ioc框架�Q�完全注解方式就可以�q�行UI�l�定和事件绑定。无需findViewById和setClickListener�{��?br /> (3) �|�络模块�Q�通过httpclient�q�行��装http数据��h��Q�支持ajax方式加蝲�Q�支持下载、上传文件功能�?br /> (4) 囄��~�存模块�Q�通过FinalBitmap�Q�imageview加蝲bitmap的时候无需考虑bitmap加蝲�q�程中出现的oom和android容器快速滑动时候出现的囄��错位�{�现象�?br /> FinalBitmap可以配置�U�程加蝲�U�程数量�Q�缓存大��，�~�存路径�Q�加载显�C�动�ȝ��。FinalBitmap的内存管理��用lru��法�Q?br /> 没有使用弱引用（android2.3以后google已经不徏议��用弱引用�Q�android2.3后强行回收��Y引用和弱引用�Q�详情查看android官方文档�Q�，
更好的管理bitmap内存。FinalBitmap可以自定义下载器�Q�用来扩展其他协议显�C�网�l�图片，比如ftp�{�。同时可以自定义bitmap昄��器，
在imageview昄��囄��的时候播攑֊��ȝ��Q�默认是渐变动画昄��Q��?br />

4、xUtils框架

��目地址�Q�https://github.com/wyouflf/xUtils
主要有四大模块：(x��)
(1) 数据库模块：(x��)android中的orm框架�Q�一行代码就可以�q�行增删�Ҏ(gu��)��Q?br /> 支持事务�Q�默认关闭；
可通过注解自定义表名，列名�Q�外键，唯一性约束，NOT NULL�U�束�Q�CHECK�U�束�{�（需要�؜淆的时候请注解表名和列名）(j��)�Q?br /> 支持�l�定外键�Q�保存实体时外键兌��实体自动保存或更斎ͼ�
自动加蝲外键兌��实体�Q�支持�g时加载；
支持铑ּ�表达查询�Q�更直观的查询语义，参考下面的介绍或sample中的例子�?
(2) 注解模块�Q�android中的ioc框架�Q�完全注解方式就可以�q�行UI�Q�资源和事�g�l�定�Q?br /> 新的事�g�l�定方式�Q��用�؜淆工��h؜淆后仍可正常工作�Q?br /> 目前支持常用�?0�U�事件绑定，参见ViewCommonEventListener�c�d��包com.lidroid.xutils.view.annotation.event�?br /> (3) �|�络模块�Q�支持同步，异步方式的请求；
支持大文件上传，上传大文件不�?x��)oom�Q?br /> 支持GET�Q�POST�Q�PUT�Q�MOVE�Q�COPY�Q�DELETE�Q�HEAD�Q�OPTIONS�Q�TRACE�Q�CONNECT��h��Q?br /> 下蝲支持301/302重定向，支持讄��是否�Ҏ(gu��)��Content-Disposition重命名下载的文�g�Q?br /> �q�回文本内容的请�?默认只启用了(ji��n)GET��h��)支持�~�存�Q�可讄��默认�q�期旉��和针对当前请求的�q�期旉��?
(4) 囄��~�存模块�Q�加载bitmap的时候无需考虑bitmap加蝲�q�程中出现的oom和android容器快速滑动时候出现的囄��错位�{�现象；
支持加蝲�|�络囄��和本地图片；
内存��理使用lru��法�Q�更好的��理bitmap内存�Q?br /> 可配�|�线�E�加载线�E�数量，�~�存大小�Q�缓存�\径，加蝲昄��动画�{?..

5、ThinkAndroid

��目地址�Q�https://github.com/white-cat/ThinkAndroid
主要有以下模块：(x��)
(1) MVC模块�Q�实现视图与模型的分��R�?br /> (2) ioc模块�Q�android中的ioc模块�Q�完全注解方式就可以�q�行UI�l�定、res中的资源的读取、以�?qi��ng)对象的初始化�?
(3) 数据库模块：(x��)android中的orm框架�Q��用了(ji��n)�U�程池对sqlite�q�行操作�?
(4) http模块�Q�通过httpclient�q�行��装http数据��h��Q�支持异步及(qi��ng)同步方式加蝲�?br /> (5) �~�存模块�Q�通过��单的配置�?qi��ng)设计可以很好的实现�~�存�Q�对�~�存可以随意的配�|?br /> (6) 囄��~�存模块�Q�imageview加蝲囄��的时候无需考虑囄��加蝲�q�程中出现的oom和android容器快速滑动时候出现的囄��错位�{�现象�?br /> (7) 配置器模块：(x��)可以对简易的实现配对配置的操作，目前配置文�g可以支持Preference、Properties寚w��|�进行存取�?br /> (8) 日志打印模块�Q�可以较快的��L��的是实现日志打印�Q�支持日志打印的扩展�Q�目前支持对sdcard写入本地打印、以�?qi��ng)控制台打�?br /> (9) 下蝲器模�?可以��单的实现多线�E�下载、后��C��载、断点箋传、对下蝲�q�行控制、如开始、暂停、删除等�{��?br /> (10) �|�络状态检��模块：(x��)当网�l�状态改变时�Q�对其进行检

6、LoonAndroid

��目地址�Q�https://github.com/gdpancheng/LoonAndroid
主要有以下模块：(x��)
(1) 自动注入框架�Q�只需要��承框架内的application既可�Q?br /> (2) 囄��加蝲框架�Q�多重缓存，自动回收�Q�最大限度保证内存的安全性）(j��)
(3) �|�络��h��模块�Q��承了(ji��n)基本上现在所有的http��h��Q?br /> (4) eventbus�Q�集成一个开源的框架�Q?br /> (5) 验证框架�Q�集成开源框�Ӟ��(j��)
(6) json解析�Q�支持解析成集合或者对象）(j��)
(7) 数据库（不知道是哪位写的忘记�?ji��n)�?j��)
(8) 多线�E�断点下载（自动判断是否支持多线�E�，判断是否是重定向�Q?br /> (9) 自动更新模块
(10) 一�p�d��工具�c?br />
其中�?volley �Q?3 �q�有研究�q�，扩展性非常好�Q�个人比较喜�Ƣ的风格。其他如 android-async-http、Afinal 也相当不错�?img src ="http://www.aygfsteel.com/paulwong/aggbug/415632.html" width = "1" height = "1" />

paulwong 2014-07-09 16:56 发表评论

paulwong — Thu, 09 Jan 2014 03:03:00 GMT

分类整理�?50个比较好的Android开源项目，已汇��d��AndroidOpenProject@Github�Q�欢�q�Star和Fork^_*

目前包括�Q?/span>
Android开源项目第一��?#8212;—个性化控�g(View)��?/a>
  包括ListView、ActionBar、Menu、ViewPager、Gallery、GridView、ImageView、ProgressBar�{�等
Android开源项目第二篇——工具库篇
  包括依赖注入框架、图片缓存、网�l�相兟뀁数据库ORM建模、Android公共库、高版本向低版本兼容库、多媒体�{�等
Android开源项目第三篇——优秀��目��?/a>
  比较有意思的完整的Android��目
Android开源项目第四篇——开发及(qi��ng)��试工具��?/a>
  包括开发自��、自动化��试、编译打包相兛_��?/em>
Android开源项目第五篇——优秀个�h和团体篇
  乐于分��n�q�且有一些很不错的开源项目的个�h和组�l�，包括JakeWharton、Chris Banes、Koushik Dutta�{�大�?/em>

paulwong 2014-01-09 11:03 发表评论

�U�d��讑֤�抓包�Ҏ(gu��)��

paulwong — Mon, 30 Dec 2013 03:23:00 GMT

ios抓包�Ҏ(gu��)��Q?a target="_blank">http://www.99css.com/archives/1272

android抓包�Ҏ(gu��)��Q?a target="_blank">http://www.cnblogs.com/xyzlmn/p/3168065.html

paulwong 2013-12-30 11:23 发表评论

ANDROID APPS DATA资源

paulwong — Tue, 25 Jun 2013 14:11:00 GMT
http://stackoverflow.com/questions/10272155/getting-data-from-android-play-store

https://developer.android.com/distribute/googleplay/promote/linking.html

http://www.scriptrr.com/data-scrapping-get-android-google-play-app-info/

paulwong 2013-06-25 22:11 发表评论

paulwong — Sat, 25 May 2013 16:59:00 GMT
ANDROID APP �?WEB APP有相��g��处，都是需要在容器内运行，都可以对事�g�q�行响应�?

WEB APP的核�?j��)组件是SERVLET�Q�这是对游览器事件进行响应的一个类�Q�事件有GET/POST�{�事�Ӟ��不同的URL对应不同的SERVLET�?/div>
如果要输��Z��同的内容�Q�则输出不同的HTML卛_��?br />WEB APP的配�|�文件是WEB.XML�Q�当容器启动�Ӟ��?x��)从�q�读取有多少个SERVLET。当��览器发�q�来不同的URL��h��Ӟ��?x��)从中选择相应的SERVLET执行�?/div>

ANDROID APP的核�?j��)组件是ACTIVITY�Q�这是一个对�pȝ��事�g�q�行响应的一个类�Q�事件有启动事�g�Q�菜单点��M��件等�Q�点��M��同的地方对应不同的ACTIVITY�?/div>
如果要输��Z��同的内容�Q�则输出不同的VIEW卛_��?br />ANDROID APP的配�|�文件是MAINFRE.XML�Q�当应用被部�|�到�pȝ��Ӟ��pȝ��?x��)从�q�读取有多少个ACTIVITY。当不同的事件发生时�Q�系�l�会(x��)�?x��)从中选择相应的ACTIVITY执行�?/div>

paulwong 2013-05-26 00:59 发表评论

演化理解 Android 异步加蝲囄��

paulwong — Tue, 15 May 2012 14:27:00 GMT
     摘要: 在学�?Android异步加蝲囑փ��结"�q�篇文章�? 发现有些地方没写清楚�Q�我��根据我的理解，把这��文章的代码重写整理�?ji��n)一遍，下面��是我的整理。下面测试��用的layout文�g�Q�简单来说就�?LinearLayout 布局�Q�其下放�?个ImageView�?Code highlighting produced by Actipro CodeHighlighter (freeware)http://...  阅读全文

paulwong 2012-05-15 22:27 发表评论

在线观看亚洲一区,国产偷国产偷亚洲高清97cao,久久国产精品高清一区二区三区

Android Application Architecture 安卓APP架构[译]

安卓APP架构

旧的应用架构

牛逼的新架构出来了(ji��n)

一体化的MVP模式

�U�d��讑֤�抓包�Ҏ(gu��)��

ANDROID APPS DATA资源

演化理解 Android 异步加蝲囄���

演化理解 Android 异步加蝲囄��