ruby lesson2

File.open("s1.txt") do |filed|
while lined = filed.gets
fh = File.new("out.txt", "a") #是追加
if lined=~/^>/
fh.puts lined
else
require 'watir'
include Watir

ie = Watir::IE.new
ie.goto("http://www.imtech.res.in/raghava/eslpred/submit.html")
ie.text_field(:name, "seq").set(lined)
ie.button(:value, "Submit sequence").click

aFile = File.new("lei.htm" , "w")
aFile << ie.html
aFile.close
ie.close
#2
File.open("lei.htm") do |file|
while line = file.gets
if line=~/Reliability Index|Expected Accuracy/

line=line.gsub(/

|\ \;|<\/B><\/LI><\/UL><\/FONT><\/TD><\/TR>|<\/B>/,'')
fh.puts line

end
end
end
end
end
end

MYSQL远程连接问题

MYSQL远程连接问题
GRANT ALL PRIVILEGES ON *.* TO 用户名@"%" IDENTIFIED BY '密码' WITH GRANT OPTION;

%表示所有。也可以限制成：10.10.10.10 （IP）

FireWatir，可以控制浏览器，包括输入东西超级简单，强大！支持linux, Mac machine,windows

http://code.google.com/p/firewatir/downloads/list
所有文件都在上面：
Installation guide for FireWatir:
1.Install JSSh XPI using following steps:
firefox 插件，用firefox打开就可以了。
2.gem install firewatir.gem


命令：
require 'firewatir'
include FireWatir

ff = Firefox.new
ff.goto 'www.google.com'
ff.text_field(:name, 'q').set('keyword')
ff.button(:name, 'btnG').click

语法：
http://wtr.rubyforge.org/watir_user_guide.html

Text Mode Browser 文本浏览器大全ELinks offers the beginnings of Javascript support

CURL --- 命令行浏览器CURL

CURL --- 命令行浏览器

CURL? 嗯，说来话长了~~~~

这东西现在已经是苹果机上内置的命令行工具之一了，可见其魅力之一斑

Lynx

Ported to almost every current system under the sun and available on most general purpose SSH-accessible systems in the world, Lynx is a mature piece of software. As such, it has accumulated well over a hundred command-line options and obscure features. It still does the basics well, including SSL these days, and it is quick compared to any graphical browser.

Lynx renders pages in color or monochrome, based on your preference. It can display pages in any of a few dozen character sets--Arabic, Hebrew and Japanese, to name a few--and can be integrated into any printing and storage regime. This is due to supporting user/administrator-defined commands on print and download requests. Lynx comes with extensive documentation, including a speech-friendly set of help files tailored for blind and visually handicapped users. Lynx also has a kiosk mode, so you can restrict the set of allowable actions and URLs.

Lynx does have a few shortcomings, however. It downloads only one file at a time and does so in the foreground, so you cannot continue browsing while the download is underway. Lynx also does not render frames, and it lays out tables strangely. Finally, Javascript links will frustrate you every time you encounter them on less-accessible Web sites.
Emacs/W3

At the time of its release, Emacs/W3 was touted as yet another reason why a user would never have to leave Emacs. It can do UTF-8 as well as Emacs can, and it understands simple CSS. Emacs/W3 has suffered bit rot since 1999, and it is hard to get up and running these days. It does not understand XHTML, so modern pages have bits and pieces of code sticking out all over the place. Currently, Emacs/W3 needs quite a bit of rework and is not recommended for use.
W3M

W3M originally was intended to be a pager, like the less pager but with HTML support. The original author felt Lynx was big and slow and wanted a quick, light replacement. Thus, W3M came into being. Over time, W3M has grown, and nowadays it has a somewhat bigger memory image than Lynx does while viewing the same page.

W3M was the first text browser to handle table rendering well, and it transforms frames to tables for convenient viewing. Coming from Japan, it has good support for exotic scripts and UTF-8. At first W3M was purely bilingual, offering good support for English and Japanese scripts, but improvements to support the broader world languages is ongoing. In addition, the browser offers the unexpected feature of being able to render images in-line on your xterm or framebuffer console. This feature is not really relevant to this comparison, but it is worth a mention. W3M also offers tabbed browsing.

W3M's shortcomings are few. W3M does not do incremental rendering. Also, you cannot do anything else while W3M is loading a page, even if you have several tabs open.
Links

As the name suggests, Links was created as a Lynx replacement to offer saner table renderings and a smaller footprint. In these areas, Links has succeeded; Links 1.0.0pre12 has the smallest footprint of the tested browsers discussed here. On a side note, Links2 seems to be a mostly graphical fork and thus was not considered for this review.

Links does offer saner table rendering than Lynx does; Links rendering is on par with W3M's. Development is frozen, so only bug fixes are being accepted. As a result, Links is both fast and stable. It can run downloads in the background, and it does incremental rendering. Like Lynx, Links has an anonymous/kiosk mode for use on public computers.

As for drawbacks, Links does not support HTTP authentication. UTF-8 support is partial, and no support is offered for Chinese, Japanese or Korean languages (CJK), even when the page is UTF-8-encoded.
ELinks

ELinks started out as a feature patch set to Links. ELinks became a fork when it became clear that no further features would be accepted into Links. As such, it inherits Links' features and flaws and adds a few of its own.

ELinks sports the most features of any text browser--good table rendering, background downloads, incremental rendering--all inherited from Links. Tabbed browsing has been added for convenience. Some CSS support is present, but little more than highlighting text seems to be honored; alignment and positioning mostly are ignored. Alone among text browsers, ELinks offers the beginnings of Javascript support as a standard feature, using Mozilla's SpiderMonkey Javascript engine. With this feature, finally some less-accessible pages can be used in text mode. ELinks' behaviour can be customized by way of Guile, Perl, Ruby and Lua scripts.

As is typical with development forks, ELinks has a large footprint compared to all the other tested browsers. It also has the most visible bugs. Due to its Links inheritance, ELinks has no support for Chinese, Japanese and Korean languages and limited support for UTF-8.

Table 1. Text Mode Browser Feature Comparison Lynx Emacs/W3 w3m Links ELinks
Tables Y Y Y Y Y
Frames N N Y Y Y
SSL/TLS Y Y Y Y Y
CSS N CSS1 N N Y
Javascript N N N N Y
UTF-8 Y Y Y N N


Erik Inge Bolsø is a UNIX consultant and epee fencer who lives in Molde, Norway, and who has been running Linux since 1996. Another of his hobbies can be found by doing a Google search for "balrog genealogy", and he can be reached at ljcomment@tvilsom.org.

CURL --- 命令行浏览器CURL

CURL --- 命令行浏览器CURL

CURL --- 命令行浏览器

CURL? 嗯，说来话长了~~~~

这东西现在已经是苹果机上内置的命令行工具之一了，可见其魅力之一斑

1)
二话不说，先从这里开始吧！

curl http://www.yahoo.com

回车之后，www.yahoo.com 的html就稀里哗啦地显示在屏幕上了~~~~~

2)
嗯，要想把读过来页面存下来，是不是要这样呢？
curl http://www.yahoo.com > page.html

当然可以，但不用这么麻烦的！
用curl的内置option就好，存下http的结果，用这个option: -o
curl -o page.html http://www.yahoo.com

这样，你就可以看到屏幕上出现一个下载页面进度指示。等进展到100%，自然就OK咯

3)
什么什么？！访问不到？肯定是你的proxy没有设定了。
使用curl的时候，用这个option可以指定http访问所使用的proxy服务器及其端口： -x
curl -x 123.45.67.89:1080 -o page.html http://www.yahoo.com


4)
访问有些网站的时候比较讨厌，他使用cookie来记录session信息。
像IE/NN这样的浏览器，当然可以轻易处理cookie信息，但我们的curl呢？.....
我们来学习这个option: -D <-- 这个是把http的response里面的cookie信息存到一个特别的文件中去
curl -x 123.45.67.89:1080 -o page.html -D cookie0001.txt http://www.yahoo.com

这样，当页面被存到page.html的同时，cookie信息也被存到了cookie0001.txt里面了


5）
那么，下一次访问的时候，如何继续使用上次留下的cookie信息呢？要知道，很多网站都是靠监视你的cookie信息，
来判断你是不是不按规矩访问他们的网站的。
这次我们使用这个option来把上次的cookie信息追加到http request里面去： -b
curl -x 123.45.67.89:1080 -o page1.html -D cookie0002.txt -b cookie0001.txt http://www.yahoo.com

这样，我们就可以几乎模拟所有的IE操作，去访问网页了！


6）
稍微等等~~~~~我好像忘记什么了~~~~~
对了！是浏览器信息~~~~

有些讨厌的网站总要我们使用某些特定的浏览器去访问他们，有时候更过分的是，还要使用某些特定的版本~~~~
NND，哪里有时间为了它去找这些怪异的浏览器呢！？

好在curl给我们提供了一个有用的option，可以让我们随意指定自己这次访问所宣称的自己的浏览器信息： -A
curl -A "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)" -x 123.45.67.89:1080 -o page.html -D cookie0001.txt http://www.yahoo.com

这样，服务器端接到访问的要求，会认为你是一个运行在Windows 2000上的IE6.0，嘿嘿嘿，其实也许你用的是苹果机呢！

而"Mozilla/4.73 [en] (X11; U; Linux 2.2; 15 i686"则可以告诉对方你是一台PC上跑着的Linux，用的是Netscape 4.73，呵呵呵


7）
另外一个服务器端常用的限制方法，就是检查http访问的referer。比如你先访问首页，再访问里面所指定的下载页，这第二次访问的referer地址就是第一次访问成功后的页面地址。这样，服务器端只要发现对下载页面某次访问的referer地址不 是首页的地址，就可以断定那是个盗连了~~~~~

讨厌讨厌~~~我就是要盗连~~~~~！！
幸好curl给我们提供了设定referer的option： -e
curl -A "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)" -x 123.45.67.89:1080 -e "mail.yahoo.com" -o page.html -D cookie0001.txt http://www.yahoo.com

这样，就可以骗对方的服务器，你是从mail.yahoo.com点击某个链接过来的了，呵呵呵


8）
写着写着发现漏掉什么重要的东西了！----- 利用curl 下载文件

刚才讲过了，下载页面到一个文件里，可以使用 -o ，下载文件也是一样。
比如， curl -o 1.jpg http://cgi2.tky.3web.ne.jp/~zzh/screen1.JPG
这里教大家一个新的option： -O
大写的O，这么用： curl -O http://cgi2.tky.3web.ne.jp/~zzh/screen1.JPG
这样，就可以按照服务器上的文件名，自动存在本地了！

再来一个更好用的。
如果screen1.JPG以外还有screen2.JPG、screen3.JPG、....、screen10.JPG需要下载，难不成还要让我们写一个script来完成这些操作？
不干！
在curl里面，这么写就可以了：
curl -O http://cgi2.tky.3web.ne.jp/~zzh/screen[1-10].JPG

呵呵呵，厉害吧？！~~~

9）
再来，我们继续讲解下载！
curl -O http://cgi2.tky.3web.ne.jp/~{zzh,nick}/[001-201].JPG

这样产生的下载，就是
~zzh/001.JPG
~zzh/002.JPG
...
~zzh/201.JPG
~nick/001.JPG
~nick/002.JPG
...
~nick/201.JPG

够方便的了吧？哈哈哈

咦？高兴得太早了。
由于zzh/nick下的文件名都是001，002...，201，下载下来的文件重名，后面的把前面的文件都给覆盖掉了~~~

没关系，我们还有更狠的！
curl -o #2_#1.jpg http://cgi2.tky.3web.ne.jp/~{zzh,nick}/[001-201].JPG

--这是.....自定义文件名的下载？
--对头，呵呵！

#1是变量，指的是{zzh,nick}这部分，第一次取值zzh，第二次取值nick
#2代表的变量，则是第二段可变部分---[001-201]，取值从001逐一加到201
这样，自定义出来下载下来的文件名，就变成了这样：
原来： ~zzh/001.JPG ---> 下载后： 001-zzh.JPG
原来： ~nick/001.JPG ---> 下载后： 001-nick.JPG

这样一来，就不怕文件重名啦，呵呵


9）
继续讲下载
我们平时在windows平台上，flashget这样的工具可以帮我们分块并行下载，还可以断线续传。
curl在这些方面也不输给谁，嘿嘿

比如我们下载screen1.JPG中，突然掉线了，我们就可以这样开始续传
curl -c -O http://cgi2.tky.3wb.ne.jp/~zzh/screen1.JPG

当然，你不要拿个flashget下载了一半的文件来糊弄我~~~~别的下载软件的半截文件可不一定能用哦~~~

分块下载，我们使用这个option就可以了： -r
举例说明
比如我们有一个http://cgi2.tky.3web.ne.jp/~zzh/zhao1.mp3 要下载（赵老师的电话朗诵 :D ）
我们就可以用这样的命令：
curl -r 0-10240 -o "zhao.part1" http:/cgi2.tky.3web.ne.jp/~zzh/zhao1.mp3 &\
curl -r 10241-20480 -o "zhao.part1" http:/cgi2.tky.3web.ne.jp/~zzh/zhao1.mp3 &\
curl -r 20481-40960 -o "zhao.part1" http:/cgi2.tky.3web.ne.jp/~zzh/zhao1.mp3 &\
curl -r 40961- -o "zhao.part1" http:/cgi2.tky.3web.ne.jp/~zzh/zhao1.mp3

这样就可以分块下载啦。
不过你需要自己把这些破碎的文件合并起来
如果你用UNIX或苹果，用 cat zhao.part* > zhao.mp3就可以
如果用的是Windows，用copy /b 来解决吧，呵呵

上面讲的都是http协议的下载，其实ftp也一样可以用。
用法嘛，
curl -u name:passwd ftp://ip:port/path/file
或者大家熟悉的
curl ftp://name:passwd@ip:port/path/file



10)
说完了下载，接下来自然该讲上传咯
上传的option是 -T

比如我们向ftp传一个文件： curl -T localfile -u name:passwd ftp://upload_site:port/path/

当然，向http服务器上传文件也可以
比如 curl -T localfile http://cgi2.tky.3web.ne.jp/~zzh/abc.cgi
注意，这时候，使用的协议是HTTP的PUT method

刚才说到PUT，嘿嘿，自然让老服想起来了其他几种methos还没讲呢！
GET和POST都不能忘哦。

http提交一个表单，比较常用的是POST模式和GET模式

GET模式什么option都不用，只需要把变量写在url里面就可以了
比如：
curl http://www.yahoo.com/login.cgi?user=nickwolfe&password=12345

而POST模式的option则是 -d

比如，curl -d "user=nickwolfe&password=12345" http://www.yahoo.com/login.cgi
就相当于向这个站点发出一次登陆申请~~~~~

到底该用GET模式还是POST模式，要看对面服务器的程序设定。

一点需要注意的是，POST模式下的文件上的文件上传，比如

这样一个HTTP表单，我们要用curl进行模拟，就该是这样的语法：
curl -F upload=@localfile -F nick=go http://cgi2.tky.3web.ne.jp/~zzh/up_file.cgi

罗罗嗦嗦讲了这么多，其实curl还有很多很多技巧和用法
比如 https的时候使用本地证书，就可以这样
curl -E localcert.pem https://remote_server

再比如，你还可以用curl通过dict协议去查字典~~~~~
curl dict://dict.org/d:computer

Ref ：http://spaces.msn.com/members/j5/Blog/cns!1pZg82u3mPDMPEPUbr4uX_lQ!134.entry

另外的介绍：http://www.cnblogs.com/abiao/articles/33170.html

ruby rails 开发环境搭建

1.安装ruby，ruby -v
ruby 1.8.6 (2007-03-13 patchlevel 0) [i386-mswin32]

2.gem 安装rail: gem install rails --remote
Bulk updating Gem source index for: http://gems.rubyforge.org
Install required dependency activesupport? [Yn] y
Install required dependency activerecord? [Yn] y
Install required dependency actionpack? [Yn] y
Install required dependency actionmailer? [Yn] y
Install required dependency actionwebservice? [Yn] y
Successfully installed rails-1.2.3
....

3.MySQL Server and MySQL Clinet:
MySQL:
http://dev.mysql.com/downloads/mysql/5.0.html#downloads
不需要选择，Congfigure the MySQL Sever now

MySQl Clinet:
http://dev.mysql.com/downloads/gui-tools/5.0.html