2009.02.01 New Words

flinty adj. 堅定不移的

granular adj. 粒狀的

realism n. 寫實主義(文藝創作)

draftsman n. 製圖者; 起草者

boisterous adj. 愛鬧的; 喧鬧的

demanding adj. 高要求的; 苛求的

knack n. 本領; 熟練技巧; 訣竅

insinuation n. 影射; 含蓄的批評

spareness n. 缺乏; 不足

rectitude n. 正直; 公正

inwardness n. 本質, 精神

prelapsarian adj. 墮落前的,(尤指 Adam 和 Eve 犯罪導致)人類墮落前的。

predating adj. 日期上較早的

splay v. 張開

citadel n. 城堡; 堡壘

canon n. (公認的)重要作家、作品

barrister n. 律師

inept adj. 不適當地, 無能的

blustery adj. 吵鬧的; 狂暴的

homespun adj. 簡樸的, 普通的

eloquent adj. 雄辯的, 有說服力的

obscenity n. 猥褻的言語, 令人髮指的事

tart adj. 尖酸的, 刻薄的

scrappy adj. 好鬥的; 愛打架的

episode n. 連續劇的一齣(或一集)

termer n. 服刑者

feudal adj. 封建時代的

oppression n.壓迫, 壓制

Comments

Setting MySQL to Use UTF-8 on MAMP (MySQL 5.5.9, or 5+)

I wanted to setup MySQL to use utf-8 on the MAMP installation on my Mac. I tried the instructions from this article: http://cameronyule.com/2008/07/configuring-mysql-to-use-utf-8/ However, I kept getting error messages that are similar to this one [ERROR] /Applications/MAMP/Library/bin/mysqld: unknown variable 'default-collation=utf8_general_ci' I did some search and realized that several variables are deprecated. Reference: http://dev.mysql.com/doc/refman/5.1/en/server-options.html Therefore, I added the following lines into /Applications/MAMP/conf/my.cnf [mysql] character-set-server=utf8 [client] character-set-server=utf8 [mysqld] character-set-server=utf8 collation-server=utf8_general_ci init-connect='SET NAMES utf8' I restarted the server and mysql run successfully with relevant variables being set correctly. In the "Variables" tab under phpMyAdmin interface (ex. http://localhost:8888/MAMP/?language=English) character set c...

ngrok, a service to help you get a public URL for your local webserver

If you are looking for options to test your web app hosted on your own machine (e.g., laptop) remotely with someone, I recommend using a service called ngrok. https://ngrok.com/ It has many usages, but in the context of testing an app hosted on your own machine, the most important part is giving you a public URL that will redirect all the requests to your local webserver (e.g., Apache, Nginx, or whatever server you are running). You can give this URL to a testing participant without the need to host the app on a remote server. For instance, if you are testing your app using a sever on your machine, typically you can access your app in a URL like: http://localhost:3000/?study=11 Using ngrok, you will have a dynamically generated URL like the following: https://3ebe3c019867.ngrok.io/ The service will redirect requests to https://3ebe3c019867.ngrok.io to http://localhost:3000 You can then share the following link with your testing participant for the participant to use your app. http...

Use NVM to handle Angular-Node.js incompatibility (e.g., Uncaught SyntaxError: Unexpected token 'export')

Overview If you are a fullstack developer, the chances are that you will be creating multiple frontend or Node.js projects along the way. When you are creating new projects using the newest version of the cli (command-line interface) of a particular framework, you might be asked to install the most updated version of Node.js in order to utilize the newest feature. This might involve upgrading your Node.js version, which might not be compatible with other existing projects (e.g., using Angular) you have created before. A potential solution is to use nvm (Node Version Manager) to install multiple versions of Node.js and use a particular version of the Node.js to install the proper version of the cli (e.g., Angular-CLI) that can be used to manage a particular project. Here I will use a problem I run into to explain how to solve it. Problem There is a compatibility issue between Node.js and angular.js. For instance, I run into an error when I was using an incompatible version of Node.js ...

Aventurine Yao

Search This Blog