今日: 276|昨日: 1777|帖子: |会员: 693393|欢迎新会员:
煲耳机为什么要用户来做而不是厂家做好再拿出来卖？反 ...
耳朵真的是可以训练的更灵敏吗？我支持正方，有些人听 ...
特价/团购信息汇总版主:
6645 / 8万
新手入门及低价位耳塞/耳机讨论版主:
5万 / <span title="万
耳机、耳机放大器、HIFI理论等综合讨论版主: ,
<span title="万 / <span title="3万
高端耳机/音响系统讨论(包括线材/电源等),高烧友自娱自乐,初烧新手慎入！版主:
5564 / <span title="万
耳塞、随身听综合讨论区版主: ,
<span title="万 / <span title="6万
MP3/MP4/录音笔/音乐手机/传统磁带、md、cd随身听版主: ,
1万 / <span title="万
耳机论坛的精华帖子版主:
主题: 889, 帖数: 6650
最后发表: 入手denon mm400说说 ...
主题: 4326, 帖数: 5万
最后发表: k701煲机
主题: 2789, 帖数: 2万
最后发表: 新手求助：准备入HD80 ...
主题: 1758, 帖数: 1万
最后发表: 出去戴个MSR7感觉好傻 ...
主题: 476, 帖数: 4057
最后发表: 创新的声卡连国内乐之 ...
主题: 846, 帖数: 6264
最后发表: 这个牌子是做啥的
主题: 879, 帖数: 6928
最后发表: 入坑dt990，求推荐一 ...
主题: 11, 帖数: 22
最后发表: 关于KEF
主题: 2, 帖数: 7
最后发表: 德国Teufel的Hi-Fi耳 ...
主题: 1683, 帖数: 2万
最后发表: 出 YULONG Audio 旗舰 ...
主题: 8326, 帖数: <span title="万
最后发表: 借楊老師寶地出MK8+GE ...
主题: 844, 帖数: 6179
最后发表: DN2K塞子硅胶粒太容易 ...
主题: 605, 帖数: 3648
最后发表: 目前大部分线材已支持 ...
主题: 2537, 帖数: 2万
最后发表: 稍试对比C4与SONY黑砖
主题: 918, 帖数: 6933
最后发表: MR1第二批发货延期补 ...
主题: 474, 帖数: 2404
最后发表: i5 热门问答！各种技 ...
主题: 121, 帖数: 769
最后发表: 请教：如果往欧博X1里 ...
主题: 81, 帖数: 418
最后发表: 旷世音响通过国家高新 ...
主题: 85, 帖数: 987
最后发表: 凯音66套推LCD3F只听 ...
主题: 134, 帖数: 634
最后发表: 盼望android版的Light ...
主题: 57, 帖数: 233
最后发表: 【资料】EROS H06拆机 ...
主题: 71, 帖数: 356
最后发表: 过保truth偏音，求解 ...
主题: 26, 帖数: 91
最后发表: CHORD
主题: 134, 帖数: 445
最后发表: 年终回顾（上部）| 7 ...
主题: 14, 帖数: 48
最后发表: 恭喜新区成立，该发点 ...
主题: 29, 帖数: 120
最后发表: 音乐装备之煲耳机曲目 ...
主题: 15, 帖数: 35
最后发表: #TFZ品牌全系列作品_ ...
主题: 8, 帖数: 26
最后发表: 会出hifi耳机吗？
主题: 34, 帖数: 145
最后发表: Mateix X-SABRE Pro已 ...
主题: 12, 帖数: 23
最后发表: 个人对HelloEar的最高 ...
主题: 6, 帖数: 16
最后发表: 新韩流吹袭 Opus#2播 ...
主题: 23, 帖数: 111
最后发表: 双阶音频的由来
主题: 663, 帖数: 4158
最后发表: 麻烦PM MDR-1A底价。 ...
主题: 415, 帖数: 2000
最后发表: 拜亚动力T1 T1二代 T5 ...
主题: 1699, 帖数: 9477
最后发表: ～圆声带～统一询价帖 ...
主题: 499, 帖数: 1745
最后发表: pm 老人家DP100底价
主题: 363, 帖数: 1931
最后发表: 〖无锡百胜百〗统一询 ...
主题: 388, 帖数: 789
最后发表: 情人节即将到来，HIFI ...
主题: 470, 帖数: 1546
最后发表: 北京本地，烦请PM
主题: 723, 帖数: 2580
最后发表: 【讯禾HIFI】全球限量 ...
主题: 403, 帖数: 2180
最后发表: 求mason v2底价
主题: 38, 帖数: 469
最后发表: 只需要48小时制作定制 ...
主题: 166, 帖数: 674
最后发表: 甲本杭州每日一歌
主题: 48, 帖数: 235
最后发表: 求pm 天龙400底价
主题: 33, 帖数: 110
最后发表: 杭州米通统一询价贴（ ...
主题: 21, 帖数: 56
最后发表: 加拿大 惊雷 SimAudio ...
主题: 1万, 帖数: <span title="万
最后发表: 小白，电脑音箱的RCA ...
主题: 8017, 帖数: 6万
最后发表: 4000左右推荐桌面音响
主题: 3万, 帖数: <span title="万
最后发表: Discrete AD797 Clone ...
主题: 5191, 帖数: 2万
最后发表: 各品牌大耳机维修 AKG ...
主题: 2万, 帖数: <span title="万
最后发表: 自己收集的一些无损资 ...
主题: 1万, 帖数: <span title="万
最后发表: DSD资源分享
主题: 9095, 帖数: <span title="万
最后发表: （大肠音乐分享137期 ...
主题: <span title="万, 帖数: <span title="4万
最后发表: 出1月18号到手的99新U ...
主题: 1718, 帖数: 9万
最后发表: 处理几套可以太阳能充 ...
主题: 4656, 帖数: 6万
最后发表: 几张正版CD（邓丽君、 ...
主题: 1万, 帖数: <span title="万
最后发表: zw和jinjiao ...
主题: 2435, 帖数: 4万
最后发表: 【团购价】享声MR1 Hi ...
主题: 406, 帖数: <span title="万
最后发表: 超值发烧线材定做&n ...
主题: 2054, 帖数: 9万
最后发表: 出自己手工定制公模发 ...
1万 / <span title="万
各城市、地区网友交流与活动召集版主:
2万 / <span title="万
公告发布及站内事务的建议、投诉版主:
3万 / <span title="万
- 总计 4997 人在线
- 最高记录是 22000 于 .
) 粤公网安备 98号
Powered byAn enhanced event bus with emphasis on Android support
Introduction
Otto is an event bus designed to decouple different parts of your application while still allowing them
to communicate efficiently.
Forked from Guava, Otto adds unique functionality to an already refined event bus as well as specializing
it to the Android platform.
Otto is designed with Android-specific use cases in mind and is intended for use as a singleton
(though that is not required). Create an instance of an event bus with
Bus bus = new Bus(); Because a bus is only effective if it is shared, we
recommend obtaining the instance through injection or another appropriate mechanism.
Publishing
Event publishing is the most important part of the bus as it allows you to tell subscribers that an
action has occurred. An instance of any class may be published on the bus and it will only be dispatched to
subscribers for that type.
To publish a new event, call the post method:
bus.post(new AnswerAvailableEvent(42));
Posting to the bus is a synchronous action so when program execution continues it is guaranteed that all
subscribers have been called.
Subscribing
Subscription is the complement to event publishing&it lets you receive notification that an event
has occurred. To subscribe to an event, annotate a method with @Subscribe. The method should
take only a single parameter, the type of which will be the event you wish to subscribe to.
To listen for the event published in the previous section we would need the following:
@Subscribe public void answerAvailable(AnswerAvailableEvent event) {
// TODO: React to the event somehow!
The name of the method can be anything you like. The annotation, single argument, and public accessor
are all that is required.
In order to receive events, a class instance needs to register with the bus. If this refers
to an instance of the class in which the previous method was present, we can register using the
following:
bus.register(this);
Registering will only find methods on the immediate class type. Unlike the Guava event
bus, Otto will not traverse the class hierarchy and add methods from base classes or interfaces that are
annotated. This is an explicit design decision to improve performance of the library as well as keep your
code simple and unambiguous.
Remember to also call the unregister method when appropriate. See the sample application,
, for a complete example.
When subscribing to events it is often desired to also fetch the current known value for specific events
(e.g., current location, active user, etc.). To address this common paradigm, Otto adds the concept of
'Producers' which provide an immediate callback to any subscribers upon their registration.
To create a producer, annotate a method with @Produce. The method should take no parameters
and its return type will be used as the type of event for which it can produce initial values. If we are
keeping track of the last answer event somewhere from above we can register to produce its initial
@Produce public AnswerAvailableEvent produceAnswer() {
// Assuming 'lastAnswer' exists.
return new AnswerAvailableEvent(this.lastAnswer);
Producers, like subscribers, must also be registered:
bus.register(this);
When registering, the producer method will be called once for each subscriber previously registered for
the same type. The producer method will also be called once for each new method that subscribes to an event
of the same type.
You may only have one producer per event type registered at a time on a bus.
Thread Enforcement
Since at times it may be ambiguous on which thread you are receiving callbacks, Otto provides an
enforcement mechanism to ensure you are always called on the thread you desire. By default, all interaction
with an instance is confined to the main thread.
// Both of these are functionally equivalent.
Bus bus1 = new Bus();
Bus bus2 = new Bus(ThreadEnforcer.MAIN);
If you are not concerned on which thread interaction is occurring, instantiate a bus instance with
ThreadEnforcer.ANY. You can also provide your own implementation of the
ThreadEnforcer interface if you need additional functionality or validation.
The source code to the Otto, its sample, and this website is .
dependencies {
compile 'com.squareup:otto:+'
&dependency>
&groupId>com.squareup&/groupId>
&artifactId>otto&/artifactId>
&version>(insert latest version)&/version>
&/dependency>
Once you've installed Otto, add the following lines to your proguard-project.txt file:
-keepattributes *Annotation*
-keepclassmembers class ** {
@com.squareup.otto.Subscribe public *;
@com.squareup.otto.Produce public *;
This ensures your annotated methods aren't removed by ProGuard.
Contributing
If you would like to contribute code you can do so through GitHub by forking the repository and sending a pull request.
When submitting code, please make every effort to follow existing conventions and style in order to keep the code as readable as possible. Please also make sure your code compiles by running mvn clean verify.
Before your code can be accepted into the project you must also sign the .
Copyright 2013 Square, Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.