Xen VPS Hosting

Deploy your Linode cloud servers worldwide, including our newest facility in Tokyo, Japan.

url : http://www.linode.com/

結婚習俗 - 結婚紅包行情

結婚紅包行情價：
　
600元---一般訂婚習俗和結婚習俗，紅包是由600元開始起跳，但那是指非常不熟悉的禮金數。
1200元---就是一般辦公室朋友的[價位] ，三分熟交情；只包紅包 祝賀，不出席喜宴。
1600元---是可以一起吃飯逛街的朋友，另外；如果你還可以拿到 一盒新娘的喜餅，那就不好再少於這個數字。
2000~2600元---可以交換一些心事，倒些垃圾的朋友，平日相交已有些推心置腹的感覺。
3600元---親密的姐姐淘，兄弟情，如熟透的親密感。
6000元---親姐妹、親兄弟血濃於水，不容取代的手足情深，自然就從6000元以上起跳。
　 紅包的由來：
　 紅包袋---亦稱為紅封包，是將金錢放置紅色封套內做成的一種小禮物。訂婚結婚包紅包是中國傳統民俗，在各種喜慶場合如過年、小孩滿月及各式送金錢作禮物時都會使用。紅色在中國文化當中象徵著喜慶，紅包當中一般會放入有吉祥數字的金錢，例如有8字或以雙數結尾的數目，而且結婚紅包賀詞寫法也是有重要的象徵意義。
　 　
　 　
　 小叮嚀
　
如果女方是訂婚收禮金，而男方是結婚收禮金；或是訂結婚一起舉辦，男女雙方都在現場擺禮桌收禮金，所以；要包給她，最好跟她說一聲，如果男方那邊收走了，至少她看過禮金簿時，知道你有包紅包給她，日後；你結婚時她才有包紅包的參考值。
紅包討吉利，新郎倌可不要忘了準備紅包給幫忙的親友；諸如：前來開新郎車門的舅爺，及六名隨新郎前去迎娶新娘的親友，捧洗臉水的女方親友、媒婆禮等。金額多為600、1200及2000元等。
　 　
　 紅包賀詞寫法
　
紅包上可寫上結婚賀詞，但紅包左下方寫上自己的名字(例如:xxx賀)
百年琴瑟 花好月圓 天緣巧合 金石同心 白頭偕老 情聯碧合 宜爾室家 花開並蒂 情投意合 天作之合 相親相愛 永浴愛河 緣訂三生......更多結婚賀詞
　 　
　
　 起源 | 訂婚流程 | 迎娶流程 | 歸寧流程 | 南北差異 | 結婚禁忌 | 結婚紅包行情 　


本網站部分相關資料於各大雜誌及網站收集而來，單純為了提供網友方便，不作他用，若原作者不同意引用，請與我們聯絡。

reference : http://www.myloving.com.tw/WedInfo_MoresPacket.asp

結婚紅包行情

最近好日子很多，因此收到不少朋友寄來請帖為此我希望得知包多少才得體，同時(1)顧及情感程度(2)顧及對方是否好回禮，台灣習俗:回禮不能比當初收到禮金少(至少等價)，因此包得好是祝福包不好是負擔，可能是自己的負擔也是對方的負擔。



此圖來自: veryWed討論區







這是PTT網友peegoo7 (瓜瓜瓜)整理出來的價目表




結論(參考朋友的看法):
(1)有分 人到 和 禮到 兩種金額，由於結婚禮金是要補助新人的做法，因此不難看出，扣除每桌費用後多少補貼的做法，好比一桌一萬元，每桌抓5-7個紅包(假設洽好是5對10人)，包2000是剛好餐費，則2200到2600甚至更多是較佳的包法，這樣的算法因人、地而異


(2)人到最少得包1600，如果帶的人數太多要酌量多加一點。


(3)由於只用雙數，不用單數！不用「四」和「八」(八有「別」之意) ！因此能用的數字只有600、1000、1200、1600、2000、2200、2600、3600、6000、6600等組合。


(4)你包3600給別人，碰上台灣習俗:回禮不能比當初收到禮金少(至少等價)，雖可回同樣的禮數，但是由於下個數字是6000，會有你要別人包6000的味道在。




依照景氣不同會有不同的包法，法無定法可由自己的狀態、友好度等做為考量，透過網路資料的整理可提供大家一個參考的方案。

reference : http://im88.tw/?p=1243

Gridow - Presenting Yourself in the simplest way

Make your own Gridow video,
All you need is a laptop,
with a camera and internet access.

Take a BITE out of Bugs and Redundant Labor

In a time when more and more of the web is becoming streamlined, the process of filing bugs for websites remains tedious and manual. Find an issue. Switch to your bug system window. Fill out boilerplate descriptions of the problem. Switch back to the browser, take a screenshot, attach it to the issue. Type some more descriptions. The whole process is one of context switching; from the tools used to file the bug, to gather information about it, to highlight problematic areas, most of your focus as the tester is pulled away from the very application you’re trying to test.

The Browser Integrated Testing Environment, or BITE, is an open source Chrome Extension which aims to fix the manual web testing experience. To use the extension, it must be linked to a server providing information about bugs and tests in your system. BITE then provides the ability to file bugs from the context of a website, using relevant templates.



When filing a bug, BITE automatically grabs screenshots, links, and problematic UI elements and attaches them to the bug. This gives developers charged with investigating and/or fixing the bug a wealth of information to help them determine root causes and factors in the behavior.



When it comes to reproducing a bug, testers will often labor to remember and accurately record the exact steps taken. With BITE, however, every action the tester takes on the page is recorded in JavaScript, and can be played back later. This enables engineers to quickly determine if the steps of a bug repro in a specific environment, or whether a code change has resolved the issue.

Also included in BITE is a Record/Playback console to automate user actions in a manual test. Like the BITE recording experience, the RPF console will automatically author javascript that can be used to replay your actions at a later date. And BITE’s record and playback mechanism is fault tolerant; UI automation tests will fail from time to time, and when they do, it tends to be for test issues, rather than product issues. To that end, when a BITE playback fails, the tester can fix their recording in real-time, just by repeating the action on the page. There’s no need to touch code, or report a failing test; if your script can’t find a button to click on, just click on it again, and the script will be fixed! For those times when you do have to touch the code, we’ve used the Ace (http://ace.ajax.org/) as an inline editor, so you can make changes to your javascript in real-time.

Check out the BITE project page at http://code.google.com/p/bite-project. Feedback is welcome at bite-feedback@google.com. Posted by Joe Allan Muharsky from the Web Testing Technologies Team (Jason Stredwick, Julie Ralph, Po Hu and Richard Bustamante are the members of the team that delivered the product).

reference : http://googletesting.blogspot.com/2011/10/take-bite-out-of-bugs-and-redundant.html

What is it? Raphaël is a small JavaScript library that should simplify your work with vector graphics on the web.

What is it?
Raphaël is a small JavaScript library that should simplify your work with vector graphics on the web. If you want to create your own specific chart or image crop and rotate widget, for example, you can achieve it simply and easily with this library.
Raphaël ['ræfeɪəl] uses the SVG W3C Recommendation and VML as a base for creating graphics. This means every graphical object you create is also a DOM object, so you can attach JavaScript event handlers or modify them later. Raphaël’s goal is to provide an adapter that will make drawing vector art compatible cross-browser and easy.
Raphaël currently supports Firefox 3.0+, Safari 3.0+, Chrome 5.0+, Opera 9.5+ and Internet Explorer 6.0+.
How to use it?
Download and include raphael.js into your HTML page, then use it as simple as:
// Creates canvas 320 × 200 at 10, 50
var paper = Raphael(10, 50, 320, 200);

// Creates circle at x = 50, y = 40, with radius 10
var circle = paper.circle(50, 40, 10);
// Sets the fill attribute of the circle to red (#f00)
circle.attr("fill", "#f00");

// Sets the stroke attribute of the circle to white
circle.attr("stroke", "#fff");

reference : http://raphaeljs.com/