In a previous article I took an example of bad metaprogramming and I pushed people to think twice before using metaprogramming. My main points were that: you might make your code way slower if you don't know what you are doing readability might drop considerably maintainability can become an issue People left some very good comments about how to write the same module using metaprogramming and keep
updated Nov 26 to reflect the recent low pro changes. (please use low pro 0.5 and Prototype 1.6) Recently one of my client asked me to add 'ajax' pagination to his application. His site already had a very nice pagination using the excellent will_paginate from Mislav and the guys(PJ & Chris) from err the blog but since my client had a special need where he had to have Ajax. It took me virtually no
Lindsay from the Integrum hall of fame wrote 3 nice (short) articles about Extreme Programming (XP). XP part I - XP values XP part II - XP principles XP part III - practices I really enjoyed reading her posts and I can really recommend you spend few minutes going through her explanations. If you are in San Diego, check the XP San Diego group. Unfortunately, the XPSD group meets at the same time
def CreateChart pipe = IO.popen "java -cp C:\\InstantRails\\rails_apps\\project\\jfree\\src;C:\\InstantRails\\rails_apps\\project\\jfree\\lib\\jcommon-1.0.0-rc1.jar;C:\\InstantRails\\rails_apps\\project\\jfree\\lib\\jfreechart-1.0.0-rc1.jar; CreateChart" pipe.close redirect_to "/graph/report" end Anyway, none of these solutions would let us create our charts in less than 5 minutes so let's cut t
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く