效果(点开看动图)：

演示效果:https://demo.goodmemory.cc/demo/floatnav/

代码很简单，主要是利用css实现 hover事件

代码：https://github.com/hiproz/floatnav

/etc/sysconfig/nginx

1. CODE： 密码工具。进去后，每条密码是明文，特点是每条记录按用户名和密码分开存储显示     评价 ：一般
2. keeper：密码工具。记录是明文存储，支持  faastfill ，支持 keeper DNA    评价：中
3. 隐私卫士：app隐私锁 评价：高
4. 私密锁：app锁，评价：一般
5. 应用程序锁：评价：一般
6. 隐私应用锁：app锁。评价低
7. 密码本：密码工具，每个字段分开存储。 评价 ：中
8. NS Wallet ：分文件夹-item 对字段做了详细的分类。 ：一般
9. safeincloud ：有详细的模板 ，支持云同步 评价：高
10. SSE  功能强大，支持密码管理 ，文件本加密 ，文件加密  评价 ：高
11. password keepox： 简单的字段记录，支持同步到dropbox ，评价：低
12. 秘密管理器：简单的字段记录：评价：极低
13. sis密码管理：同上

js代码：

返回并刷新

<script>alert("恭喜您，操作成功！"); window.location.href=document.referrer; </script>

返回不刷新

<script>alert("恭喜您，操作成功！"); window.history.back(-1); </script>

参考：http://stackoverflow.com/questions/20423037/warning-mysql-fetch-assoc-expects-parameter-1-to-be-resource-boolean-given-i

本质就是没有对入参做异常判断。

参考：https://www.zybuluo.com/lanxinyuchs/note/33551

说明：以Windows系统下查看C++代码为例。因为Source Insight(以下简称SI)是收费软件，且界面丑陋，所以考虑其替代方案，发现Sublime Text3(以下简称ST3) + Ctags + Cscope 可以取得很好的效果。使用ST3基本可以实现全键盘操作，同时它又没有学习Vim的陡峭曲线。

安装方法：

1. 安装Package Control for ST3

2. 安装Ctags插件

(1) 通过 Preference -> Package Control -> Install Package安装Ctags插件
(2) 下载 Ctags.exe, 通过 Preference -> Package Settings -> Ctags -> Settings Default 中的内容拷贝到 Setting User中，将 command": "" 中的 "" 填入Ctags.exe的路径位置
(3) 在工程根目录上点击右键，选择Ctags:Rebuild tags

3. 安装Cscope插件

(1) 通过 Preference -> Package Control -> Install Package安装Cscope插件
(2) 下载 Cscope.exe, 并在工程根目录下生成cscope.out文件
(3) 打开CscopeSublime.sublime-settings文件(可能需要添加到 Package -> User 目录下)，将 "executable": "" 中的"" 填入Cscope.exe的路径位置,将 "database_location": "" 中的 ""填入cscope.out的路径位置

功能实现：

(1) 对于symbol函数的定义查询，ST3自带此功能Go to Definition，且搜索结果有多个时可以预览，不用跳转到另一个文件。Ctags也有此功能navigate_to_definition，搜索结果比ST3要准确一些，但多结果时不支持预览。Csope也有此功能 Cscope: look up function defintion，但搜索结果不支持双击点开。因此实际中多用ST3和Ctags来实现此功能
(2) 对于symbol变量的定义查询，ST3不支持，Ctags有此功能，方法同其查询symbol函数的定义一致。Cscope也可以用查询symbol函数定义的方法实现此功能，搜索结果不支持双击点开。因此实际中多用Ctags来实现此功能
(3) 对于函数caller的查询，只有Cscope有此功能Cscope: look up function calling this function
(4) 全局搜索, ST3可通过Ctrl+Shift+F实现，但搜索耗时较长。Cscope可通过Cscope: look up symbol实现，因为已经通过cscope.out建立了索引，所以结果很快，但结果不一定全面

注：使用Cscope的功能时，需按enter键确定才会执行

比较：ST3 + Ctags + Cscope的方案基本可以实现Source Insight的常用有效功能（除了查看类继承关系的Relation Windows），且其速度更快，界面也更为清爽。ST3相比于SI的其他优点还包括：
(1)ST3使用Ctrl+P搜索文件时，使用的是模糊匹配，不像SI必须顺次拼写正确才行
(2)ST3支持tab模式，可方便的在多个文件间切换

ST3实用技巧：

(1) Alt+O可以实现头文件和源文件之间的快速切换
(2) 通过 View -> Side bar 可在左侧显示当前打开的文件列表
(3) ST3虽然不像notepad++可以在sidebar上显示函数列表，但是可通过Ctrl+R查看
(3) 通过 Preference -> Key binding user 可根据个人操作习惯自定义快捷键（包括ST3自带的和插件的）
(4) 双击可选中光标所在单词，三击可选中光标所在行
(5) Ctrl+Shift+T可以打开之前关闭的tab页，这点同chrome是一样的

参考：http://www.ibm.com/developerworks/cn/opensource/os-eclipse-javadebug/

在启动脚本startup.bat前加上：

SET CATALINA_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,address=8765

然后在eclipse里面设置：

很好的文章，就mobile 空socket 的耗电状态做了深入的分析.

更完整的内容参见：trepn-whitepaper-apps-power

from：https://developer.qualcomm.com/blog/hanging-sockets-and-power-consumption-basics-part-3

Continuing our series on mobile apps and their effect on battery drain, I’ll pick up where the three guidelines in Wayne Lee’s last post left off, especially #3: “Know what your app is doing with the hardware and when it’s doing it.”

One common way that mobile apps use too much power is through hanging sockets –network connections that the app is no longer using, but which the server thinks are still alive because the app has not closed them. The subsequent query from the server results in needless battery drain.

Here’s more background on the problem and how you can deal with it.

“Wake up. It’s time to go to sleep.”

Applications often “forget” to close their socket after they are done with it. Then, after some amount of time without data activity, the server times the socket out and closes it.

Socket termination in TCP requires a four-way handshake, so the server has to send a FIN packet to the device, which usually takes the device from the low-power dormant state to the higher-power active state. The device goes idle for a bit, then back to dormant. It’s like waking somebody up to tell them that it’s time to go to sleep.

Look at the example in the diagram. The red (1) shows the device jumping from dormant to active mode to send and receive data normally for a few seconds. Once finished, the cellular radio drops to a power-saving idle mode (2) in case that it’s needed again. After about 15 seconds of inactivity, the radio goes dormant (3).

But the app has left the socket open (hanging). The server doesn’t like loose ends, so it sends its FIN packet to the device. This rouses the radio from dormant to active again (4), the same as if it were sending/receiving data for the app. Worse yet, the radio follows the normal curve back down to idle for another 15 seconds, wasting more power (5).

Begin to get the idea?

The phone has to bring up the radio for a simple, easily avoidable handshake because the server has asked the device for something that the app should have provided in the first place. If no other traffic moves between the device and the network, the connection is a complete waste of several hundred milliamperes.

Assuming that the app uses the network four times in an hour, the simple fix of having the app close the socket when finished can reduce network power consumption by about 20 percent, which would be the difference between eight and ten hours of standby power.

The lesson is: Program your app to close sockets when it has finished with them. Otherwise, the phone consumes power to bring up the radio for a needless handshake with the server.

Next Steps

So, to paraphrase Wayne, you need to know what your app is doing with the cellular radio, when it’s doing it and how to turn it off when the app no longer needs it.

• Watch Wayne’s Uplinq presentation, “Minimum Power Usage, Maximum Performance.”
• Read our white paper, "When Mobile Apps Use Too Much Power: A Developer Guide for Android App Performance,” for more background and ideas on mobile apps and power consumption.

Questions? Visit the Trepn Profiler Support Forum or let me know in the comments below.

ps -ef | grep perl | wc -l

/etc/sysconfig/i18n

LANG="zh_CN.UTF-8"