tl;dr
传送门: music.samsonw.info
Prerequisite: 网速要给力……
目前只在最新版本的firefox,safari和chrome下测试通过 i,虽然不是必须,但还是推荐用webkit内核浏览器 ii 访问.
[Footnotes]tl;dr
传送门: music.samsonw.info
Prerequisite: 网速要给力……
目前只在最新版本的firefox,safari和chrome下测试通过 i,虽然不是必须,但还是推荐用webkit内核浏览器 ii 访问.
[Footnotes]今天两篇post之后,还是对wordpress 3.2的full screen editor爱不释手 i,所以再来一篇……;这不是0day,所以请expect一切都会可能有延迟.
话说这还是上周一的事情了……
插入一个闪回:
我平时一般工作或是自己开发都开着两个editor,一个是macvim,这个目前看来是完全为了vim-task了,我用它来GTD;另外一个是textmate,我大部分的code,除了java和obj-c外 ii都是在textmate里面完成;可能你会觉得好奇,话说这已经牵涉到信仰的问题了,要知道textmate是我两年前我买mac的first bullet,如果抛弃textmate,我两年前的行为就似乎失去了意义;请不要告诉我mac的ui怎么怎么fancy,界面怎么怎么友好,我不是果粉,这些对我其实都没有杀伤力;我更不是那些个喜欢抱着macbook pro在星巴克靠窗的座位前展现各种独特品味的伙计,话说我到非常希望我能有如此的定力……
闪回完了回来,回到上周一;如果你像我这样用textmate编辑维护总和超过10000+行的 sql stored procedure (单文件3000+行)iii 代码,你会明白textmate默认自带的SQL.tmbundle其实做的蛮烂的,作为一种语言的bundle,它竟然不支持symbol list,这让本身在TM里面navigate就不方便的用户情何以堪……
一般语言定义的function或是method都会被作为symbol list的item,方便用户直接跳转到该function/method的definition处;没有symbol list的情景下,这意味着你只能search,还要人为或自动的filter掉一些不是definition的match字串,这在你debug的正high,正心急如焚抑或火冒三丈的时候,无疑不是种尴尬,接下来便是不情愿的敲上 ⌘ + F,然后嘴里嘀咕着:”人生啊”;这,就是我上周一之前一直的状态……
Continue reading →
此次release主要来源于两个trigger:
1. wordpress 3.2 release了;
2. grid archives 1.2.0 实现了一个只在某些page或post页面load资源文件 (css, js etc) 的feature,就如人家建议的,这个feature,douban collections也值得拥有;
[Live Demo]
[Changelog]
[Screenshots]
WordPress 3.2 is released today with “Refreshed Administrative UI”, “Full Screen Editor” i and a couple of other enhancements and bug-fixes.
To be fully compatible with this latest release, only a couple of minor tweaks ii was made in this grid archives 1.3.0 release.
[ChangeLog]
As always, please visit the plugin home page for more details.
[Footnotes]Continue with our CDD i process :)
As indicated in this comment, before 1.2.0 grid archives resource files (css, js etc) are loading on every page. This is actually a common plugin issue as that’s the default behavior of wordpress’s 2 API functions: wp_enqueue_script() and wp_enqueue_style().
To avoid loading resources on every page and thus improve the load speed of the whole site, Grid Archives 1.2.0 added an option to allow user to enable loading plugin resources only in specific pages and posts. The page/post name can be configured in the grid archives settings page.
[ChangeLog]
[Screenshots]
[Footnotes]Grid Archives now seems work pretty good with the CDD (Comment Driven Development) process :)
This release is driven by this comment. As I said, the plugin is now totally driven by comments, so as always, thanks for these who trying this plugin out and giving back the precious feedback.
In this release, grid archives now support displaying posts from one specific category, just input [ grid_archives category="Category name" ] i in your page/post, the category is the category name you want to display. For backward compatibility, the old [ grid_archives ] will still work and will still show all the posts as it did before.
[ChangeLog]
Please visit the plugin home page for more details.
[Footnotes]好吧,这回中文,亚历山大……
其实英文有英文的好处,比如英文会使本人比较focus,因为没兴趣也没能力瞎扯,于是主题明确而不拖泥带水;中文的坏处便是我会常常迷失主题,跑题千里后蓦然回首,那人竟然还在灯火阑珊处……
anyway……
前几天看到sunng的take my coffee,一看title以为必是coffeescript,结果竟偏是如此纯结(纯是纯净水的纯),看来还是哥多虑了…… 想来最近的blog title里面随便带个coffee都会让人浮想联翩,coffee script的“火”冒三丈也就可见一斑。
标题起源于上周想到一个idea,便是让live fortune定时publish到新浪微博或是twitter,目前新浪的publisher已经实现,并顺便refactor了一下code,让之后twitter publisher的加入变的十分简单(在plan中);实现的过程中再次发现了sina clone的迹象,因为其oauth实现竟然连url抄的都一模一样,倒是方便了实现,因为twitter oauth的sample code基本上改个site base url后就能完全照搬,暂且认为这是新浪有意而为之的吧,目的便是方便第三方开发人员……
本来这篇文章一直draft着,再加上周末一直不available,所以拖到现在,为了应景,还特地决定一大早先跑去喝杯咖啡后再来奋笔疾书,无奈公司咖啡机几近坏掉,我修了半天搞的满身都是最后还是勉强喝到了一点味道有稍许异样的不知道还能不能叫做coffee的”coffee”,看来杯具如我辈是永远达不到sunng那种小资情调的呵呵;
吃葡萄不吐葡萄皮,不吃葡萄倒吐葡萄皮. i
[Footnotes]Here we will use Nginx to serve static resources and reverse proxy dynamic requests to the Node server. We will also use Monit to monitor the Node server and restart it automatically in case it crash. This is also the deployment I did at fortune.crash4.us.
[Nginx: Static Resources]
livefortunes use express.static to server static resources, but for better performance we will use nginx to do the job that it’s designed and built to do.
Config nginx to server all the static resources which located under /public :
Do you enjoy reading interesting or funny sentences like below?
A nuclear war can ruin your whole day.
He who knows, does not speak. He who speaks, does not know.
– Lao Tsu
If you do, check out:
http://fortune.crash4.us/ i
For the record, this is a project built with Node.js, Express and Faye. One fortune will be pushed from server to each client every 2 mins thanks to the html5 WebSocket. Client can trigger a server push/broadcast as well ii. All the source code is available at github.
Next step is to convert this project to CoffeeScript.
[Footnotes]