Enjoy Life

[Code]Sql选择字段唯一值并上后面的字段

2006-10-25T22:54:00.000+08:00

需求：选择A字段唯一值，并上B字段，如果A字段相同B字段不同，则取第一次出现的B字段的值。

表
A B Id
--------------------------------------
1 A 1
1 B 2
2 C 3
2 D 4
3 E 5
3 F 6

选择结果：
A B Id
--------------------------------------
1 A 1
2 C 3
3 E 5


SELECT *
FROM TEST
WHERE (ID IN
          (SELECT MIN(id)
         FROM TEST
         GROUP BY A))

[Fun]Total广告歌

2006-10-21T10:02:00.000+08:00

link:

http://www.jinweijie.com/jinweijie.com/total.mp3

[Software]SourceForge Enterprise Edition

2006-10-13T11:16:00.000+08:00

SourceForge 推出了 SourceForge Enterprise Edition

看起来不错! 有空去试试看

15 USERS FREE FOREVER

[Software]一个很不错的浏览器

2006-10-08T14:01:00.000+08:00

K-Meleon

http://kmeleon.blogspot.com/

Gecko引擎，windows native interface

速度快，占资源少，绿色免安装

[Software]将物理机转换成vm

2006-10-03T12:15:00.000+08:00

周一，VMware发布了VMware Converter 3 Beta版，它可以利用物理计算机系统并将其转换为虚拟机器镜像。新版结合了两个以前独立的两个工具：VMware P2V Assistant 和 Virtual Machine Importer。

除物理机向虚拟机转换外，Converter 3还可以将第三方VM格式转为VMware兼容的镜像，这包括微软的Virtual Server 、Virtual PC 和 Symantec Backup Exec System Recovery。

Converter 3将可以免费获取，下载地址：

http://www.vmware.com/products/beta/converter/

[Software]一些下载电子书的站点

2006-10-03T10:02:00.000+08:00

http://www.chmpdf.com/
http://www.chmpdf.com/archives/ebooks/addison wesley/

http://www.templatecn.com/

http://www.vvsoft.net/vvbksd/index.asp

http://book.httpcn.com/

http://www.chinesebook.com.cn/bjbookfair/index.asp

http://www.eshunet.com/

http://www.manyi100.com/

http://www.52ebook.com/

http://www.pcbookcn.com/

http://www.itebook.net/download.asp

http://www.ebookcn.net

http://www.chinaz.com/DownLoad/L/8_...time_Desc_1.asp

http://soft.winzheng.com/SoftList/C...Time_Desc_1.htm

http://www.gd00.com/SoftList/Catalo...ime_Desc_1.html

http://soft.0zones.com/SoftList/Cat...ime_Desc_1.html

补充：

http://ianzag.megasignal.com/ftp/pub/doc/books/Development/

[Life]Ryan on CZTV

2006-09-30T14:07:00.000+08:00

[Life]有一句话

2006-09-30T09:25:00.000+08:00

“我觉得做一件事，经历就是一种成功，你去闯一闯，不行你还可以掉头；但是你如果不做，就像晚上想想千条路，早上起来走原路，一样的道理。”
--马云

AJAX框架汇总（转）

2006-09-26T16:22:00.001+08:00

基于浏览器的应用框架一般分为两种：

Aplication frameworks:提供了浏览器功能，但其最著名的还是在于通过窗口生成组件建立桌面GUI。
Infrastructural frameworks:提供基本的框架功能和轻便式浏览器端操作，让开发者去创建具体应用，主要功能包括：
- 基于XMLHttpRequest组件的浏览器交互功能
- XML解析和操作功能
- 根据XMLHttpRequest的返回信息进行相应的DOM操作
- 一些特殊情况下，和其他的浏览器端技术如Flash（或Java Applets）等集合到一起应用

基于服务器端的应用框架通常以下面两种方式工作(尽管它们根据不同的语言进行了分类)

HTML/JS Generation(HTML/JS生成)：通过服务器端生成HTML和JS代码在传递给浏览器端进行直接运行
远程交互：JavaScript调用服务器端函数(例如调用Java函数)并返回给JavaScript的回调句柄，或者请求服务器端数据信息，例如Session信息，数据库查询等。

1. Pure Javascript: Application Frameworks

1.1 Bindows (成立于2003年)

Bindows是一个通过DHTML、JavaScript、CSS和HTML等技术强劲联合起来的一套完整的Windows桌面式的WEB应用程序解决方案。Bindows无需下载安装客户端支撑组件（如Java、ActiveX或Flash），仅需一个浏览器。纯OO的理念体现在Bindows任何地方，Bindows或许是笔者见过的最完整最强大的AJAX应用程序平台。
Bindows是商业程序的，使用了来自于MB的技术(总部位于GA USA，主要开发中心在瑞典，成立于2002年)。

Bindows框架提供的功能和特性有：

基于面相对象技术的类和API
一套完整的Windows桌面系统，支持各种特性窗口模式，包括菜单、表单、表格、滑动条、测量仪器窗口和其他一些Windows窗口特性支持。
是开发zero-footprint(零空间占用)SOA客户端应用程序首选工具包
本机的XML，SOAP和XML-RPC支持
单用户到企业级开发的支持
内建的完美的AJAX支持

Bindows开发环境：

支持企业级规模的项目开发
跨浏览器、跨OS平台的支持
不受服务器结构限制
良好的与新的、现有的资源互操作性
统一的开发接口

1.2 BackBase (成立于2003年)

BackBase是一个完整的浏览器端框架，提供了丰富的浏览器操作功能，以及对.NET和JAVA平台的集成。
商业化产品，来自于Backbase B.V(总部在Amsterdam，成立于2003年)。

1.3 DOJO (开发中,成立于2004年9月)

DOJO提供完整的轻量级窗口组件和浏览器-服务器消息映射支持

提供创建自定义Javascript窗口组件的框架支持
预制的丰富的窗口类型库
B/S消息映射支持——XMLHttpRequest和其他机制
支持浏览器中的URL操纵功能
开源许可(Academic Free License 2.1)，由JotSpot的Alex Russell所领导。

1.4 Open Rico (开发中;成立于2005年5月;基于早期的一个proprietary 框架)

Open Rico是一个支持Ajax架构和用户交互的多用途框架。

一个XMLHttpRequest response能被一个或多个的DOM对象，或者Javascript对象调用。
支持拖拽操作
支持基于AJAX的动画模式，如缩放和变换等
基于Behaviors的操作库
使用指南，由RussMirimar的Yonah提供
开源。源于Sabre航空公司解决方案，由Bill Scott，Darren James及另外一些人维护。

1.5 qooxdoo (开发中; 成立于2005年5月)

qooxdoo，是另一个发展迅猛的应用框架，提供广泛的UI支持，正在开发基础架构等特性。

基础结构特性：
- 能轻易的捕获和操纵DOM事件
- 支持调试
- 支持一个时间操作的Timer类
- Getter/Setter支持
UI:
- 窗口组件库和框架
- 界面布局管理
- 图像缓存和透明PNG图片处理
开源(LGPL).

1.6 Tibet (开发中; 创建于2005年6月)

Tibet提供了大量的易移植和完整的JavaScript API，通过这些可以快速生成大量的客户端代码，Tibet自称是企业级AJAX。

远程脚本调用封装在XMLHttpRequest中
URI支持
支持所有的HTTP事件，不再仅仅是GET和POST
低级的协议-File://和WebDav也可以当作HTTP正常使用
Web Services调用支持，包括SOAP、XML-RPC等等
大型的Javascript对象库
多种多样的XML操作支持
IDE和开发工具
开源协议(OSI)

1.7 AJFORM (创建于2005年6月)

AJFORM是一个极易上手的AJAX框架，被用来编写入门级的AJAX代码，提供有以下功能：

三步安装
自动支持任意HTML表单元素
几乎无需编码即可实现AJAX

2 Pure Javascript: Infrastructural Frameworks

2.1 AjaxCaller(创建于2005年5月，目前是Alpha版)

AjaxCaller是一个具有多线程安全访问的XMLHttpRequest组件，主要针对Ajax开发新手，目前仍处于alpha开发阶段，仅在AjaxPatterns的在线搜索范例中使用了这个程序。

用明文或者XML结构的数据实现和服务器的交互(GET/POST/PUT/DELETE)
支持XMLHttRequest对象的构析(销毁对象，C++支持内存对象的构析操作)
支持Response的高速缓存(尚在计划中)
简单的库文件代码易于新手学习使用，并且支持脚本调试
开源协议

2.2 Flash JavaScript Integration Kit

The Flash JavaScript Integration Kit可以使Flash和Javascript脚本实现相互集成。

可以实现在JavaScript中调用Flash ActionScript脚本，反之亦然。
几乎支持双方主要数据类型的在不同环境中的传递调用。
开源协议，有几个Flash开源爱好者维护。

2.3 Google AJAXSLT (2005年6月发行)

Google AJAXSLT，是一个Javascript框架，用来执行XSLT转换以及XPath查询。

目前在Google Map上就使用了这个。
开源协议(BSD)

2.4 HTMLHttpRequest(Beta版；创建于2005年)

HtmlHttpRequest最大的特点就是运用XMLHttpRequest对象和标准HTML标签IFrame来实现最大限度的跨浏览跨平台的AJAX支持，其原理是在支持XMLHttpRequest的浏览器上调用XMLHttp，如果不支持，就用IFrame来模拟实现异步交互。

目前支持的浏览器：IE6/Win, IE5.5/Win, IE5/Win, IE4/Win, Mozilla/Win, Opera7/Win, Safari/Mac, IE5/Mac
尚未测试的浏览器：IE4/Mac, Mozilla/Mac, Opera/Other, Konqueror/Linux。
开源协议(LGPL)

2.5 Interactive Website Framework (创建于2005年)

Interactive Website Framework定位在浏览器中支持各种各样的AJAX基础应用的开源项目。自称是通过JavaScript、CSS、XML和HTML实现高性能的交互式WEB框架，包括一个可定制易读的XML解析器。实际上，IWF是一个AJAX的基础框架，并且还包括一些通用脚本代码。

实现了线程安全的XMLHttpRequest
对XML Document进行封装，以便创建更具有可读性的代码：
var node = doc.groceries.frozen[0].pizza[0].size;
封装后的数据读取
var node = doc.documentElement.firstChild.firstChild.getAttribute("size");
原始的DOM操作读取
开源协议

2.6 LibXMLHttpRequest (2003年6月发布)

libXmlRequest是一个小型XMLHttpRequest封装包

用getXML()和postXML()两个事件简化XMLHttpReuqest调用
支持XMLHttpRequest对象池
Response缓存处理
源码可以使用，但是有版权保护。

2.7 MAJAX

MAJAX是另一个非常小巧的HttpRequest封装包，为收发字符型信息提供简单接口，并为每步动作设置回调界面。

2.8 RSLite (x)

RSLite是一个XMLHttpRequest封装组件，作为Brent Ashley的JSRS(JavaScript Remote Scripting)其中的一部分功能单独发布。详情可以看JSRS的介绍

2.9 Sack(开发中，成立于2005年5月)

Sack也是一个很有名字的微型XMLHttpRequest封装包。调用者可以自定义回调函数或者是DOM对象。借助于回调DOM对象，可以把Response回来的数据直接以文本的方式嵌入DOM中。

2.10 Sarissa (发布于2003年2月)

Sarissa是一个JavaScript API，封装了在浏览器端独立调用XML的功能。

可移植的XMLHttpRequest对象创造
可移植的XPath查询
可移植的DOM操控
可移植的XSLT
可移植的XML序列化
开源协议(GPL2.0和LGPL2.1)

2.11 XHConn (2005年4月发布)

XHConn也是一个小型的XMLHttpRequest封装库。笔者也使用改良过的XHConn，其特点就是调用简单，代码也清晰易读。

例子：
new XHConn().connect("mypage.php"，"POST"，"foo=bar&baz=qux"，fnWhenDone);
开源协议许可

3 Server-Side: Multi-Language

3.1 Cross-Platform Asynchronous INterface Toolkit (2005年5月)

CPAINT是一个真正的同时支持PHP和ASP/VBScript脚本的AJAX和JSRS工具包。CPAINT在后台提供你需求的AJAX和JSRS代码，并自动返回到浏览器端相应的Javascript脚本代码，这种方式易于实时反馈需求的WEB应用程序。

支持PHP和ASP
所有功能函数都在统一的JavaScript文件中
支持远程脚本和XML
支持本地和远程函数调用
可以创建单个或多个XMLHttp对象
返回给后台的数据即可以是文本也可以是XML/DOM文档对象
支持POST和GET
用服务端代理的方式实现远程函数和数据的访问操作
大部分浏览器中测试正常使用
在GNU、GPL、LGPL开源协议保护下发行

3.2 SAJAX (2005年3月)

SAJAX的实现方式很独特，例如：调用一个javascript方法x_calculateBudget()，将先把响应传到服务器并调用一个Java calculateBudget()方法，然后以javascript方式把值返回到x_calculateBudget_cb()中。SAJAX的名气不错，估计很多人都听过甚至用过，不过缺点就是它的这套映射理论感觉较繁锁，远不如一些轻量级的封装库好用，不过SAJAX最大的特点就是支持的平台丰富，几乎囊括了WEB下常用的编程语言和平台

很方便从JavaScript函数映射到服务端代理操作
支持多种平台(ASP/ColdFusion/Io/Lua/Perl/PHP/Python/Ruby)
开源协议

3.3 Javascipt Object Notation (JSON) and JSON-RPC

JSON是一个"face-free" XML，而JSON-RPC是一种远程交互协议，类似于XML-RPC，对JavaScript支持较强

支持多服务端平台: Java, Python, Ruby, Perl.
针对不同的平台有不同的包和许可协议, 如JSON-RPC-Java.

3.4 JavaScript Remote Scripting(JSRS)(2000年)

JSRS，较经典的远程脚本访问组件，支持将客户端数据通过服务器做代理进行远程的数据/操作交互。

支持的浏览器：IE4+，NS4.x，NS6.x，Mozilla，Opera7和Galeon。
服务器端脚本语言支持：ASP，ColdFusion，PerlCGI，PHP,Python和JSP(servlet)。
开源协议。由Brent Ashley提供支持。

3.5 Bitkraft for ASP.NET

Bitkraft是个基于(.NET)Web框架的CLR(公共语言运行库)，允许用独特的方式创建和操作分布式Web内容。用C#编写，运行在微软的.NET 1.1和Mono框架下，无缝式的客户端-服务器响应方式是它的最大特点。Bitkraft没有使用XML组织数据，而是用JSON代替。

支持的浏览器： IE5+, Firefox1+, NS6
服务器端要求：ASP.NET, Mono XSP, Cassini, Apache (modMono) .NET Framework 1.1+
事件驱动
支持同步和异步的远程代理
客户端支持所有的.NET类型或自定义类对象映射到JSON中
用JSON取代XML
免费，开源许可协议

4 Server-Side: Java

4.1 WebORB for Java (2005年8月)

WebORB for Java是一个开发AJAX和基于Flash的富客户端应用程序的开发平台。在线例子

WebORB包括一个富客户端开发类库。提供简单的在线式API用来绑定或者调用任何Java对象、XML Web Services和EJB
支持异步或同步的事件驱动
不需要在服务端修改任何代码，不需要自定义方法或属性、变量等。不要求设计时指定代理等。
同步调用不需要回调，异步调用需要一个回调方法。
客户端可以向服务端请求指定的活动方式，不需要任何编程就可以把处理结果轻易的转变为状态。
提供一个特定API来处理数据库查询结果-服务器代码能返回DataSet或者DataTable，而客户端以一个类似于RecordSet的JavaScript对象来显示这个结果。该对象提供检索列名和行数据的方法。
支持数据分页技术。客户应用程序能检索页面中的数据。
支持以参数的方式返回所有服务期端数据类型，如primitives, strings, complex types, arrays, native .net collections, remote references
目前有两个版本：标准版(免费)，专业版(商业许可)

4.2 Echo 2 (2005年3月)

Echo 2允许你用纯Java语言编写AJAX程序。 Demo.

自动生成HTML和Javascript代码
用XML在客户端-服务端传递消息
如果愿意支持自定义Javascript组件
开源协议(Mozilla Public License or GNU LGPL)

4.3 Direct Web Remoting (DWR) (2005)

Direct Web Remoting可以在Javascript代码中直接调用Java方法的应用框架

类似于SAJAX，可以把Javascript中的请求调用转递到Java方法中并将执行结果返回给Javascript
可以和任何Web框架一起使用，如Struts、Tapestry等等
开源(Apache)，目前该产品被加入到WebWork中

4.4 SWATO (2005)

SWATO是一套可重用的和良好集成的Java/JavaScript库，它实现了一种更容易的方式来改变你的web应用程序的交互，通过AJAX方式实现。

服务端Java库可以非常容易的部署到所有Servlet2.3+兼容的容器中
客户端Javascript库可以在所有支持XMLHttpRequest的浏览器中使用
使用JSON技术在服务端组织POJO数据，这样你可以在任何Javascript环境中(HTML、XUL、SVG)访问这些远程数据，这种方式很容易通过硬编码或者某种成熟的Javascript库集成到当前应用中
提供一个简单接口使你能在Javascript中调用远程的POJO数据
使用和灵活的在web.xml中进行配置，并且可以集成(不是必须)到你的Spring框架中
提供了几个可帮助你快速开发web应用程序的组件(如自动完成的文本框，在线表单，在线列表等等)

4.5 AJAX JSP Tag Library

The AJAX JSP Tag Library是一组JSP标签库，用来AJAX程序开发。可以在J2EE下无需Javascript就能轻松开发AJAX模式的Web Form。标签库为比较通用的AJAX功能提供了5个标签：

autocomplete: 用户在文本框中输入字符，自动从指定的数据中匹配用户输入的字符，类似于Google Suggest
callout:可以为A标签加入气泡式的消息提示框，不过是实时的服务端取出数据
Select/dropdown:类似于联动菜单，比如地州市的联动下拉框
toggle:开关闸按钮，比如在一个hidden表单域中存储true和falsh，同时显示相应的img图像
update field:更新数据，也就是无刷新提交了。

4.6 AJAX Java Server Faces Framework

The AJAX-JSF用来把任意的JSF应用程序转变为AJAX应用程序

例子：AJAX组件的 MyFaces JSF Tree(树型目录), table scroller(可滚动的表格), tabbed pane(分页栏)
开源协议(Apache Software License)

Server-Side: Lisp

5.1 CL-Ajax

CL-Ajax实现Javascript直接调用服务端Lisp

生成可带参数的函数
可以回调Javascript函数或者DOM对象
可以集成到SAJAX中
开源许可

6 Server-Side: .NET

6.1 WebORB for .NET (2005年8月)

WebORB for .NET是一个用.NET和XML Web Services方式开发AJAX和基于Flash的富客户端应用程序(在线例子)

WebORB包括一个富客户端开发类库。提供简单的在线式API用来绑定或者调用任何.NET对象、XML Web Services
支持异步或同步的事件驱动
不需要在服务端修改任何代码，不需要自定义方法或属性、变量等。不要求设计时指定代理等。
同步调用不需要回调，异步调用需要一个回调方法。
客户端可以向服务端请求指定的活动方式，不需要任何编程就可以把处理结果轻易的转变为状态。
提供一个特定API来处理数据库查询结果-服务器代码能返回DataSet或者DataTable，而客户端以一个类似于RecordSet的JavaScript对象来显示这个结果。该对象提供检索列名和行数据的方法。
支持数据分页技术。客户应用程序能检索页面中的数据。
支持以参数的方式返回所有服务期端数据类型，如primitives, strings, complex types, arrays, native .net collections, remote references
目前有两个版本：标准版(免费)，专业版(商业许可)

6.2 Ajax.NET (2005年3月)

Ajax.NET是首家支持各种方式通过Javascript访问服务端.net的免费库

类似于SAJAX，能把Javascript请求发送到.NET方法，服务端回传给Javascript，甚至包括串行化自定义类。
可以在Javascript中访问Session和Application数据
缓存查询结果
免费使用源代码
无需更改源代码，允许给Ajax.NET添加和修改方法和属性
所有类支持Javascript客户端返回数据，可以在JavaScript中使用DataSet：res.Tables[0].Rows
使用HtmlControls组件访问和返回数据
页面无需重载，用事件代理(数据访问层)
因为只提供一个调用接口方法，所以服务端CPU占用非常少

6.3 ComfortASP.NET (2005年8月)

ComfortASP.NET可以让开发者在纯.NET下开发类似AJAX(DHTML,JavaScript,XMLHttp)特性的应用程序。

快速应答
减少HTML传输
减少页面重载
无闪烁的浏览器内容更改
AJAX用户体验，

6.4 AjaxAspects (2005年8月)

AjaxAspects是个可以用Javascript调用服务端WebService事件的引擎

用标准的SOAP和WSDL进行服务端-客户端通信
用简单的类型和XML对象支持带参数的返回值
缓存支持
动作队列
免费使用，开源协议

7 Server-Side: PHP

7.1 AjaxAC (2005年4月)

AjaxAC用一个单独类封装了完整的应用程序功能

所有的功能集成在自包含的类中(另外附带一些Javascript库)
调用PHP文件或者HTML页面非常简易，只需创建App类后把类引用传递给需要调用的Javascript对象或者HTML元素即可。
捕获Javascript事件
可以自定义配置数据，并且支持运行时参数更改
无需再Javascript代码中夹杂凌乱的Html代码，所有事件都是被动态附加上的
由于以上两个优点，所以支持良好的模版引擎
容易Hook到PHP类和MySql数据已返回给自己的request
能够容易的用Javascript建立窗口模式应用程序。

7.2 JPSpan

JPSPAN通过Javascript直接调用PHP中的函数。

进行了严谨的单元测试
开源许可(PHP)

7.3 XAJAX

XAjax通过Javascript直接调用PHP中的函数

支持用Javascript调用PHP脚本
开源许可协议

8 Server-Side: Ruby

8.1 Ruby On Rails

Ruby On Rails是一个支持AJAX的完整Web框架，使用Ruby语言编写，严格按照MVC结构开发。

当Ajax出现的时候Rails还处于其发展的早期，因此Ajax可能逐渐成为Rails框架的核心。
生成浏览器中大多数/全部的Window应用组件和动画的Javascript脚本。
支持服务器端调用。
队列支持
开源许可

[Software]User Interface Design for Web Applications

2006-09-24T20:41:00.000+08:00

User Interface Design for Web Applications

It’s a Different World from Web Site Design

In: Articles

By Jean Tillman

Published on November 12, 2003

This article could be also be titled “Things I Wish I'd Known Before Designing My Latest Web-Based Application.” You see, I had experience designing Web sites. I’d mastered the art of creating catchy content. I worked with Web-savvy graphic artists who provided masterful images. I knew the latest HTML coding tricks and could design around the various browser quirks and incompatibilities. Armed with these skills and experiences, I volunteered to design the user interface for one of my company’s Web-based applications—and dove right in.

OK, diving didn’t work. I learned quickly that the design choices one makes for a Web-based application are often quite different from those of a content-based Web site. Why? Because they are used for different purposes. Duh! (Mental head slap.)

I needed to look at each design choice from a different angle—because I was now playing by different rules. As I made my way through the maze of design decisions, I took note of the things I did differently from my Web site projects. This article explores some of the lessons I learned along the way.

Content vs. User Entry Forms

Think about the Web sites you visit. What do you find there? Content. You see lots of text, graphics, color, animation, and sometimes even glitz and gimmicks, right? Most Web sites are designed to encourage browsing, searching, and exploration. Most importantly, they are designed to attract visitors and keep them interested.

Now think about the applications (software products) you use. You use them to complete tasks. Rarely do you see exciting graphics or animation (well, OK, unless you’re using a graphics tool or a game). Rarely do you browse, search, or read lots of text—unless it’s the online Help. You are a fairly captive audience and don’t need glitz or fascinating content to keep you there. What you do need are quick and easy methods to complete your tasks.

The Web-based application I was working on was created for system administrators in an intranet environment. These administrators would perform tasks such as adding user-IDs, configuring network components, and generating diagnostics reports. Unlike the content-based Web sites I had designed, this user interface would consist primarily of user entry forms and the navigation elements needed to find and execute the forms. There would be very little text—just the labels for input fields and other form elements—and only the most functional of graphics.

The first lesson I learned was that each design decision is dictated by the focus of the project. The focus of my previous Web site projects was content; the focus of the application’s user interface was task-based user entry forms.

As I worked through the prototyping, usability testing, and implementation of this user interface, I was constantly reminded that even the most mundane design choice needed to be examined in a different light. Here are some of the design differences I encountered.

User and Task Analysis

Analyzing and organizing content for a Web site is quite different from identifying user tasks and chunking and organizing them into usable pages of forms.

For content-based Web sites, analysis determines things like:

What information is needed/desired? This becomes the list of content topics.
What information is the most important? This goes on the Home page and main pages of the site.
What are the main topics and which are subtopics? These become the main and sub-navigation links.
Within a topic, what are the related topics? These become hypertext links.

For applications, analysis determines things like:

What are the main tasks performed by the intended users?
Which tasks are parts of other tasks?
Which tasks are performed linearly?
Which tasks are performed repeatedly in a single session?
What user assistance (online Help) is needed each step of the way?
Which tasks are performed frequently and which infrequently?
Would users prefer to have the tasks organized by frequency of use or by the order in which they’re performed?

These are some of the questions that need to be asked during the up-front analysis, then again during usability testing. The answers help determine the navigation scheme, the chunking of tasks into pages, and the organization of the pages.

Visited links: Most Web sites use a different color for “unvisited links” than for “visited links”; this enables users to quickly identify pages they’ve seen. But when using an application, users don’t really “visit” pages; they perform tasks such as entering data into forms. A user might fill out the same form many times (for example, to add several user-IDs to the database), so it’s not important to distinguish which pages have been visited. In cases like this, it’s preferable to specify the same color for the unvisited links as for the visited links so all links look the same.

Frames: The use of frames is a hotly debated topic in Web design. Whether this is because frames have been poorly implemented in most Web sites or because they are inherently flawed, I’m not sure. Have you ever clicked on a link in the left frame of a Web page to display an article or story in the right frame, and then tried to bookmark that article using your browser’s menu bar? You can’t. Or have you tried to grab the URL of that article to send it to a friend? You can’t. (Well, OK, with some browsers you can do both of these things with the right-click menu or by calling up the frame in a new window—but both techniques are rather cumbersome and hardly intuitive!) As Jakob Neilsen points out in his classic article “Why Frames Suck (Most of the Time)”, frames wreak havoc with the user’s mental model of Web pages.

So what about using frames in a Web-based application? Some of the problems still apply—but not all. For example, most people wouldn’t bookmark a specific page within an application. (If they did, they might get unexpected results due to security features or additional application processing required for that page.) Same thing for grabbing a URL and sending it to a friend. So, although the use of frames is still subject to debate in the world of Web-based applications, the issues are a bit different. If using frames, you would be well advised to conduct thorough usability testing—well before full implementation.

Searching: Most content-based Web sites are designed with searching in mind. They use specific strategies to increase their relevance rank with the major search engines, and many have their own search capabilities. Well-designed Web sites provide navigation and contextual orientation cues on each page—in case a user searches the Web and lands on a page within the site. In contrast, applications (Web-based products) rarely involve searching—except in the online help system, of course. The skills and strategies used to craft search-friendly Web pages aren’t needed when designing an application. Instead, the focus is on ease of navigation and form design.

Page titles: In Web site design, it’s considered good practice to use a unique page title (the text that appears in the browser title bar) for each page—for several reasons. First, it enables users who bookmark the page to quickly identify it in their Favorites. Second, it provides context for users who land on the page from outside the Web site, such as from a Search engine or hypertext link. But as we’ve already explored, bookmarking pages within an application is generally discouraged. And the concept of landing in the middle of an application while on the Web generally does not apply. For that reason, it might make the most sense to use the same page title on every page—perhaps indicating the application name and version.

Hypertext vs. linear tasks: In most Web sites, users can jump from one page to another using hypertext links. Designing good hypertext requires some thought about how and when to link to related content. But with applications, users perform tasks, which may require linear paths through the pages and additional application processing when a user navigates from one page to the next. This requires a different kind of design, one that focuses on navigation among tasks rather than hypertext among pages of content.

Scrolling: Scrolling is another hotly debated topic in Web design. Would users rather see a small number of long pages or a large number of short pages? As you can see from the multitude of styles out on the Web today, there is no right answer. But how about for applications? The choice depends on how data-entry-intensive is the application and how long the pages take to download. A user who is content to scroll through a lengthy page of text and graphics may find it cumbersome to scroll through a form while filling out the fields. However, if moving from page to page requires lots of background application processing and the pages take awhile to download, users may prefer one long form. This design choice is best made with the help of some usability testing.

Cross-browser considerations: Most Web sites are designed to work properly with all—or at least the most widely used—Web browsers. Designers often use browser-safe colors, avoid browser-specific capabilities, and perform thorough testing of their pages on many browsers and browser levels. Designers of Web-based applications, however, may have more control over the target environment, depending on the situation. They can specify a required browser, much like they specify the required hardware or operating system environment. This gives them more freedom of design and more choices for implementing browser-specific capabilities.

Browser buttons: Web users have come to understand and expect specific behaviors for common browser buttons. The Back button displays the previously visited page. The refresh button reloads the page from the server. But using these buttons with a Web-based application could yield unexpected results. For example, although the Back button may return to the previous page, it might not execute the associated application code, which could mean some of the displayed data is no longer current. For this reason, some applications provide instructions warning users to avoid these buttons—and even to hide the standard toolbar on their browser. And the designers often provide alternate navigation methods so users can move among pages without relying on these browser buttons.

Pulldown navigation menus: Many navigation schemes use cascading menus: The top or side of the page lists choices that, when moused over or clicked on, open successive levels of submenus. This scheme allows users to access pages deeper within the site without having to click through intermediate pages. However, when considering this technique for a user interface that uses forms, designers may encounter a serious technical glitch. Some browsers always display certain form elements, such as dropdown selection boxes, on top of all other page content. This means that part of a navigation menu could be obscured by form elements, preventing users from accessing the pages available from that menu. Before implementing such a scheme, you should be sure to test it with all the form elements that may exist in the user interface to avoid a major SNAFU!

Home page: Typically the first page you see on a Web site is its home page. It often describes the content areas of the site, contains news stories, describes what’s new on the site, promotes a product or service, and so on. What should the Home page of a Web-based application contain? Here are some options, along with considerations for each:

A “main menu” like that of many traditional applications
But note that the widely-used pulldown menu navigation schemes would likely negate the need for a whole page devoted to a menu.
Product overview information or online Help for new users
Although they may be useful for novices, these items would likely annoy advanced users. And this Help information should be readily available from all pages anyway, so taking up prime space on the home page may not be the best choice.
Typical “splash screen” content containing a product graphic, version level, and copyright information
These are typically available from the “Help” or “About” page, and possibly a splash screen that disappears after a few seconds, so including it on the Home page would serve no additional purpose.
System statistics or other live data, if appropriate
Depending on the product, additional application processing can add to the page download time, which is an important factor in deciding whether to include such data on a frequently visited page like a Home page.
Nothing—do not use a Home page
The concept of the Home page came about with the advent of the Web, but does not exist in traditional application design. The fact that an application has a Web-based user interface does not mean it requires a Home page. Designers may find it’s best to leave it out, assuming users can readily understand what to do on the default page that’s displayed and that there is intuitive navigation to other parts of the interface.

As you can see, each option has its drawbacks, and there isn’t one right answer. The decision involves many factors, including download time, ease of navigation, and of course, the purpose of the application.

Help: The online Help on Web sites typically takes the form of Frequently Asked Questions, a welcome/overview for first-time visitors, a site map, and possibly instructions for customizing or using the Web site. In contrast, the online Help for an application typically consists of conceptual or background information about the application and how to use it, as well as context-sensitive help for pages or individual fields of a form. Help can also be found in the wording of system messages and links to more information about how to correct problems. Overall, the online Help for Web-based applications is more like that of traditional (non-Web-based) applications than for content-based Web sites.

Major “Mental Head Slap”

Whew! After taking on this user interface project, I’m a lot more insightful about design issues and, well, rather humbled by the amount of design savvy I have yet to gain. Yes, the project was successful. But I owe its success less to my previous Web design experience than to my willingness to throw out (or at least amend) everything I thought I knew about Web design and look at it from a new angle.

Sometimes the toughest lessons to learn are also the simplest. Whether you’re designing a Web site, a user interface for an application, or anything else, your design decisions should be driven by the purpose of the deliverable and the needs of the user. Well, duh!

form here

[Software]Blogger Beta的用户终于可以正常留言了

2006-09-21T19:31:00.000+08:00

自从升级到Blogger beta以后，一直不能在非beta的blogger上用blogger id留言，搞得很是郁闷

今天终于好了:D

另外，两个小更新：

1 www.jinweijie.com改版
2 Simple Chat：http://www.jinweijie.com/SimpleChat

[Software]windows快捷键

2006-09-13T09:16:00.000+08:00

Accessibility Controls	access.cpl
Add Hardware Wizard	hdwwiz.cpl
Add/Remove Programs	appwiz.cpl
Administrative Tools	control admintools
Automatic Updates	wuaucpl.cpl
Bluetooth Transfer Wizard	fsquirt
Calculator	calc
Certificate Manager	certmgr.msc
Character Map	charmap
Check Disk Utility	chkdsk
Clipboard Viewer	clipbrd
Command Prompt	cmd
Component Services	dcomcnfg
Computer Management	compmgmt.msc
timedate.cpl	ddeshare
Device Manager	devmgmt.msc
Direct X Control Panel (If Installed)*	directx.cpl
Direct X Troubleshooter	dxdiag
Disk Cleanup Utility	cleanmgr
Disk Defragment	dfrg.msc
Disk Management	diskmgmt.msc
Disk Partition Manager	diskpart
Display Properties	control desktop
Display Properties	desk.cpl
Display Properties (w/Appearance)	control color
Dr. Watson System Troubleshooting Utility	drwtsn32
Driver Verifier Utility	verifier
Event Viewer	eventvwr.msc
File Signature Verification Tool	sigverif
Findfast	findfast.cpl
Folders Properties	control folders
Fonts	control fonts
Fonts Folder	fonts
Free Cell Card Game	freecell
Game Controllers	joy.cpl
Group Policy Editor (XP Prof)	gpedit.msc
Hearts Card Game	mshearts
Iexpress Wizard	iexpress
Indexing Service	ciadv.msc
Internet Properties	inetcpl.cpl
IP Configuration (Connection Configuration)	ipconfig /all
IP Configuration (Cache Contents)	ipconfig /displaydns
IP Configuration (Cache Contents)	ipconfig /flushdns
IP Configuration (Release All Connections)	ipconfig /release
IP Configuration (Renew All Connections)	ipconfig /renew
IP Configuration (Refreshes DHCP & DNS)	ipconfig /registerdns
IP Configuration (Display DHCP Class ID)	ipconfig /showclassid
IP Configuration (Modifies DHCP Class ID)	ipconfig /setclassid
Java Control Panel (If Installed)	jpicpl32.cpl
Java Control Panel (If Installed)	javaws
Keyboard Properties	control keyboard
Local Security Settings	secpol.msc
Local Users and Groups	lusrmgr.msc
Logs You Out Of Windows	logoff
Microsoft Chat	winchat
Minesweeper Game	winmine
Mouse Properties	control mouse
Mouse Properties	main.cpl
Network Connections	control netconnections
Network Connections	ncpa.cpl
Network Setup Wizard	netsetup.cpl
Notepad	notepad
Nview Desktop Manager (If Installed)	nvtuicpl.cpl
Object Packager	packager
ODBC Data Source Administrator	odbccp32.cpl
On Screen Keyboard	osk
Opens AC3 Filter (If Installed)	ac3filter.cpl
Password Properties	password.cpl
Performance Monitor	perfmon.msc
Performance Monitor	perfmon
Phone and Modem Options	telephon.cpl
Power Configuration	powercfg.cpl
Printers and Faxes	control printers
Printers Folder	printers
Private Character Editor	eudcedit
Quicktime (If Installed)	QuickTime.cpl
Regional Settings	intl.cpl
Registry Editor	regedit
Registry Editor	regedit32
Remote Desktop	mstsc
Removable Storage	ntmsmgr.msc
Removable Storage Operator Requests	ntmsoprq.msc
Resultant Set of Policy (XP Prof)	rsop.msc
Scanners and Cameras	sticpl.cpl
Scheduled Tasks	control schedtasks
Security Center	wscui.cpl
Services	services.msc
Shared Folders	fsmgmt.msc
Shuts Down Windows	shutdown
Sounds and Audio	mmsys.cpl
Spider Solitare Card Game	spider
SQL Client Configuration	cliconfg
System Configuration Editor	sysedit
System Configuration Utility	msconfig
System File Checker Utility ( Immediately)	sfc /scannow
System File Checker Utility (Next Boot)	sfc /scanonce
System File Checker Utility ( Every Boot)	sfc /scanboot
System File Checker Utility (Default Setting)	sfc /revert
System File Checker Utility (PurgeCache)	sfc /purgecache
System File Checker Utility (size x)	sfc /cachesize=x
System Properties	sysdm.cpl
Task Manager	taskmgr
Telnet Client	telnet
User Account Management	nusrmgr.cpl
Utility Manager	utilman
Windows Firewall	firewall.cpl
Windows Magnifier	magnify
Windows Management Infrastructure	wmimgmt.msc
Windows System Security Tool	syskey
Windows Update Launches	wupdmgr
Windows XP Tour Wizard	tourstart
Wordpad	write

from here

[Code]ie和firefox在img嵌套在div中onclick事件的不同

2006-09-06T21:17:00.000+08:00

ie和firefox在img嵌套在div中onclick事件的不同

为什么一定要这样？


<div id="ryan" style="position:absolute; top:0px; left:0px; border: 0px solid black; width:680px; height:639px">
<img id="imgFloor"  ></img>
 <script language=javascript>
  if (document.getElementById && !document.all)
   $('ryan').onclick =GetImageClick;
  else
   $('imgFloor').onclick =GetImageClick;
</script>
</div>

[Fun]My New Domain

2006-09-05T11:44:00.001+08:00

http://fa.sh.cn

:P

[Code]一些网页技巧

2006-08-30T13:14:00.000+08:00

防护网页

1. 禁止打印本网页

代码：


<style media='print'>body {display:none}</style>

说明：

将这段代码加入html网页的head部分，打印菜单在IE上是使用普通的Java脚本是无法禁止的，通过上面的语句可以使打印的主体部分在打印时隐藏，从而达到无法打印的目的

2. 禁止保存网页
代码：

<SCRIPT LANGUAGE="JavaScript">

//防止全部另存为html和mht，但无法防止仅存本页和txt
if(document.all)document.write('<link rel=stylesheet type="text/css" href="/ehp_null.css">')

//禁止本地查看，不信你可以试试（先另存为，然后直接双击打开）

wside=(window.sidebar)?true:false;
var w456=false;
function f369w()

{

document.location="";w456=true;return;
}
if(window.location.protocol.indexOf("file")!=-1){f369w();}
</SCRIPT>

说明：

另存为菜单在IE上是使用普通的Java脚本是无法禁止的，而且所谓的保存禁止都是像本例一样加入一个不存在的CSS样式表或者图象，从而达到不允许保存全部的html和mht页，本例中后面的那一段函数是用来禁止保存后本地打开时显示原网页的

3. 禁止将网页上的一些公章等机密图片保存下来

代码分两段，第一段如下：

<META HTTP-EQUIV="ImageToolbar" CONTENT="No">

第一段说明：

这一段禁止IE6中出现那个浮动的图片工具栏，因为工具栏上面提供保存功能，这段代码要加入网页的head部分中

第二段代码：
<SCRIPT LANGUAGE="JavaScript">
//禁止选中
document.onselectstart=new Function("return false")
function nsel()
{
if((document.layers)||wside)
{
var qwe= document.getSelection();
if(qwe!=""){window.find(" ")};
setTimeout("nsel()",20);
}
}
nsel();
//禁止拖拉
function disdrag()
{
if(document.all)
{
document.ondragstart= new Function("return false")
for (I = 0; I< document.images.length; I++)
{

z = document.images(I);
z.galleryImg = 'no';
}
}
}
disdrag();
//禁止非法直接选中拷贝网页（不是很好，当打开这个网页时，你就别想在任何一个应用程序中进行Copy&Parse，但是这个可以防止拷贝屏幕）
function ccd(){clipboardData.clearData();}
function cce()

{

ccd();
setTimeout("cce()",30);
}
cce();
</SCRIPT>

说明：

上面这段代码禁止网页右键的弹出菜单，网页上文本和图象选取，拖拽等，最后一段代码禁止拷贝和粘贴，不推荐使用，因为它定期清除剪贴板，打开这个网页在其他程序之间就无法进行拷贝和粘贴操作

4. 禁止缓存

代码：


<META HTTP-EQUIV="Expires" CONTENT="-1">
<META HTTP-EQUIV="Pragma" CONTENT="No-Cache">

说明：

将上述代码加入网页的head段中即可
5. 其他一些功能

代码1：

<META NAME="MSSmartTagsPreventParsing" CONTENT="True">

<META HTTP-EQUIV="Expires" CONTENT="-1">
<META HTTP-EQUIV="Pragma" CONTENT="No-Cache">

<META NAME="Robots" CONTENT="NoIndex">

说明：

上面的代码需要加入到网页的head段中

代码2：

<SCRIPT LANGUAGE="JavaScript">
wside=(window.sidebar)?true:false;
var w456=false;
//禁止Opera用户
if(navigator.userAgent.indexOf('Opera')!=-1)

{

alert("This web page does not support Opera Browser.");

window.location="about:blank";
}
//禁止非发使用Iframe连接本网页
if (top.location != self.location)

{

top.location = self.location;
}
//禁止状态栏看到链接地址
function wwddd()
{
window.status=" ";
setTimeout("wwddd()",10);
}
wwddd();
//禁止非法使用（也就是检查域名不正确就重新导向正确的域名，不过用了没法使用IP直接访问，防火墙内的用户可能会看不到）
ppp34=document.referrer.toLowerCase();
if((ppp34.indexOf("http://www.your-domain.com")<0)

&&(w456==false))

this.location.href ="http://www.your-domain.com";
</SCRIPT>

打造W3C HTML 4.01標準的網站 -[]
目前使用Dreamweaver或其他網頁製作軟體做網站編輯,HTML大部份都是以HTML4.0和HTML4.01為主,但是能完全符合標準的卻不多,有些人有這樣的的想法:[能正常再瀏覽器顯示就好],有些人則不清楚原來還有W3C標準的存在,達到W3C標準其實不難,只要多注意一些細節,拷貝教學網範例語法的時候,詳細檢查一下再貼上,如果能直接編輯HTML更好,避免錯誤的發生。
以下我列出幾點是比較常見的錯誤供參考:

1.不可省略雙引號或單引號
錯誤 style=font-size:9pt
正確 style="font-size:9pt"
錯誤 <img src=bg.gif width=140 height=30 alt=text>
正確 <img src="bg.gif" width="140" height="30" alt="text">
錯誤 <a href=home>text</a>
正確 <a href="home">text</a>

HTML4.01中有些屬性值沒有加引號是可以通過測試
但在XHTML1.0引號就是必須的,所以建議養成加引號的好習慣

2.標籤必須是一對
<p> </p>
<font></font>
<div></div>
<table><tr><td></td></tr></table>

3.圖片標籤加上文字說明alt="說明"錯誤 <img src="bg.gif" height="50" border="0">
正確 <img src="bg.gif" height="50" border="0" alt="說明文字">

4.非標籤一部分的符號以編碼表示
表單內包含以下符號也必須用編碼表示
< 以 < 表示
> 以 > 表示
& 以 & 表示
程式中的連結 & 也要改用 &
錯誤 <a href="foo.cgi?chapter=1§ion=2">
正確 <a href="foo.cgi?chapter=1&section=2">

5.標籤的順序
錯誤 <b><i>文字</b></i>
正確 <b><i>文字</i></b>

6.註解文字不可包含--符號
錯誤 
正確 

7.CSS樣式表的位置與正確寫法
一定要放在<head></head>之間
<link rel="stylesheet" type="text/css" href="style.css">
<style type="text/css">

</style>

錯誤 <style>
正確 <style type="text/css">

8.使用表格常犯的錯誤
我們在做表格通常會指定寬與高,例如:
<table border="1" width="300" height="55">
<tr><td> 內容 </td></tr>
</table>
這樣做是沒有辦法通過,W3C建議使用CSS來控制標籤元素的高度
.table{
height:55px;
}
<table class="table">
<tr><td> TEXT </td></tr>
</table>
但是若使用太多表格,在CSS一一指定不同高,也不是好方法
其實很簡單將高度height屬性指定在儲存格就可以了通過測試
<table border="0" width="300">
<tr><td height="55"> TEXT </td></tr>
</table>
但這不是w3c希望的標準,建議能夠使用div代替不必要的table

9.同一個id選擇器不可重複使用
一個網頁中id="xx"同一個選擇器不能重複使用,若需要重複請用class="xx"
10.JavaScript寫法
Javascript我們通常會寫為
錯誤 <script language="javascript">
W3C標準必須為程式指定類型type=text/javascript,所以要寫為
正確 <script type="text/javascript">
或者 <script language="javascript" type="text/javascript">
載入外部.js獨立檔案的寫法
正確 <script type="text/javascript" src="script.js"></script>

11. <embed>標籤的爭議
<embed>是Netscape的私有標籤,W3C 從HTML3.2 HTML 4.01 到 XHTML 1.0 中都沒有這個標籤,所以使用<embed>的頁面是不能通過標準測試。
W3C推薦使用 <object> 標籤,用<object>插入flash影片的代碼可以寫為:
<object type="application/x-shockwave-flash" data="index.swf" width="400" height="200">
<param name="movie" value="index.swf">
</object>
但這樣的寫法可能IE5/IE6 Win瀏覽器版本會出現問題
想要符合標準又能在任何瀏覽器下正常顯示,以下幾個連結點提供參考:

torresburriel.com
A List Apart
<embed>標籤因為廣大的受到運用,不再標準範圍引起很大的爭議,
想要解決這個問題,只能等IE瀏覽器對<object>有更好的支持
或者W3C願意收錄<embed>標籤。

12.HTML4.01文件類別宣告的正確寫法 (不可小寫)
用於一般網頁
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
用於框架頁
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Frameset//EN"
"http://www.w3.org/TR/html4/frameset.dtd">
W3C標準測試網址 http://validator.w3.org/
網頁自動測試網址 http://validator.w3.org/check?uri=referer
測試時一定要有「12.文件類別宣告」還有指定文件編碼
<meta http-equiv="Content-Type" content="text/html; charset=big5">
才能順利進行測試動作,開始打造一個萬維標準的網站吧!

40种网页常用小技巧 -[]
1. oncontextmenu="window.event.returnValue=false" 将彻底屏蔽鼠标右键
<table border oncontextmenu=return(false)><td>no</table> 可用于Table

2. <body onselectstart="return false"> 取消选取、防止复制

3. onpaste="return false" 不准粘贴

4. oncopy="return false;" oncut="return false;" 防止复制

5. <link rel="Shortcut Icon" href="favicon.ico"> IE地址栏前换成自己的图标

6. <link rel="Bookmark" href="favicon.ico"> 可以在收藏夹中显示出你的图标

7. <input style="ime-mode:disabled"> 关闭输入法

8. 永远都会带着框架
<script language="JavaScript"></script>

9. 防止被人frame
<SCRIPT LANGUAGE=JAVASCRIPT></SCRIPT>

10. 网页将不能被另存为
<noscript><iframe src=*.html></iframe></noscript>

11. <input type=button value=查看网页源代码
onclick="window.location = "view-source:"+ "http://www.pconline.com.cn"">

12.删除时确认
<a href="javascript: if(confirm("确实要删除吗?"))location="boos.asp?&areyou=删除&page=1"">删除</a>

13. 取得控件的绝对位置
//Javascript
<script language="Javascript">
function getIE(e){
var t=e.offsetTop;
var l=e.offsetLeft;
while(e=e.offsetParent){
t+=e.offsetTop;
l+=e.offsetLeft;
}
alert("top="+t+"/nleft="+l);
}
</script>

//VBScript
<script language="VBScript"></script>

14. 光标是停在文本框文字的最后
<script language="javascript">
function cc()
{
var e = event.srcElement;
var r =e.createTextRange();
r.moveStart("character",e.value.length);
r.collapse(true);
r.select();
}
</script>
<input type=text name=text1 value="123" onfocus="cc()">

15. 判断上一页的来源
javascript:
document.referrer

16. 最小化、最大化、关闭窗口
<object id=hh1 classid="clsid:ADB880A6-D8FF-11CF-9377-00AA003B7A11">
<param name="Command" value="Minimize"></object>
<object id=hh2 classid="clsid:ADB880A6-D8FF-11CF-9377-00AA003B7A11">
<param name="Command" value="Maximize"></object>
<OBJECT id=hh3 classid="clsid:adb880a6-d8ff-11cf-9377-00aa003b7a11">
<PARAM NAME="Command" VALUE="Close"></OBJECT>
<input type=button value=最小化 onclick=hh1.Click()>
<input type=button value=最大化 onclick=hh2.Click()>
<input type=button value=关闭 onclick=hh3.Click()>
本例适用于IE

17.屏蔽功能键Shift,Alt,Ctrl
<script>
function look(){
if(event.shiftKey)
alert("禁止按Shift键!"); //可以换成ALT　CTRL
}
document.onkeydown=look;
</script>

18. 网页不会被缓存
<META HTTP-EQUIV="pragma" CONTENT="no-cache">
<META HTTP-EQUIV="Cache-Control" CONTENT="no-cache, must-revalidate">
<META HTTP-EQUIV="expires" CONTENT="Wed, 26 Feb 1997 08:21:57 GMT">
或者<META HTTP-EQUIV="expires" CONTENT="0">

19.怎样让表单没有凹凸感？
<input type=text style="border:1 solid #000000">
或
<input type=text style="border-left:none; border-right:none; border-top:none; border-bottom:

1 solid #000000"></textarea>

20.<div><span>&<layer>的区别？
<div>(division)用来定义大段的页面元素，会产生转行
<span>用来定义同一行内的元素，跟<div>的唯一区别是不产生转行
<layer>是ns的标记，ie不支持，相当于<div>

21.让弹出窗口总是在最上面:
<body onblur="this.focus();">

22.不要滚动条?
让竖条没有:
<body style="overflow:scroll;overflow-y:hidden">
</body>
让横条没有:
<body style="overflow:scroll;overflow-x:hidden">
</body>
两个都去掉？更简单了
<body scroll="no">
</body>

23.怎样去掉图片链接点击后，图片周围的虚线？
<a href="#" onFocus="this.blur()"><img src="logo.jpg" border=0></a>

24.电子邮件处理提交表单
<form name="form1" method="post" action="mailto:****@***.com" enctype="text/plain">
<input type=submit>
</form>

25.在打开的子窗口刷新父窗口的代码里如何写？
window.opener.location.reload()

26.如何设定打开页面的大小
<body onload="top.resizeTo(300,200);">
打开页面的位置<body onload="top.moveBy(300,200);">

27.在页面中如何加入不是满铺的背景图片,拉动页面时背景图不动
<STYLE>
body
{background-image:url(logo.gif); background-repeat:no-repeat;
background-position:center;background-attachment: fixed}
</STYLE>

28. 检查一段字符串是否全由数字组成
<script language="Javascript"></script>

29. 获得一个窗口的大小
document.body.clientWidth; document.body.clientHeight

30. 怎么判断是否是字符
if (/[^/x00-/xff]/g.test(s)) alert("含有汉字");
else alert("全是字符");

31.TEXTAREA自适应文字行数的多少
<textarea rows=1 name=s1 cols=27 onpropertychange="this.style.posHeight=this.scrollHeight">
</textarea>
32. 日期减去天数等于第二个日期
<script language=Javascript>
function cc(dd,dadd)
{
//可以加上错误处理
var a = new Date(dd)
a = a.valueOf()
a = a - dadd * 24 * 60 * 60 * 1000
a = new Date(a)
alert(a.getFullYear() + "年" + (a.getMonth() + 1) + "月" + a.getDate() + "日")
}
cc("12/23/2002",2)
</script>

33. 选择了哪一个Radio
<HTML><script language="vbscript">
function checkme()
for each ob in radio1
if ob.checked then window.alert ob.value
next
end function
</script><BODY>
<INPUT name="radio1" type="radio" value="style" checked>Style
<INPUT name="radio1" type="radio" value="barcode">Barcode
<INPUT type="button" value="check" onclick="checkme()">
</BODY></HTML>

34.脚本永不出错
<SCRIPT LANGUAGE="JavaScript">

</SCRIPT>

35.ENTER键可以让光标移到下一个输入框
<input onkeydown="if(event.keyCode==13)event.keyCode=9">

36. 检测某个网站的链接速度：
把如下代码加入<body>区域中:
<script language=Javascript>
tim=1
setInterval("tim++",100)
b=1
var autourl=new Array()
autourl[1]="www.njcatv.net"
autourl[2]="javacool.3322.net"
autourl[3]="www.sina.com.cn"
autourl[4]="www.nuaa.edu.cn"
autourl[5]="www.cctv.com"
function butt(){
document.write("<form name=autof>")
for(var i=1;i<autourl.length;i++)
document.write("<input type=text name=txt"+i+" size=10 value=测试中......> =》<input type=text
name=url"+i+" size=40> =》<input type=button value=GO

onclick=window.open(this.form.url"+i+".value)><br>")
document.write("<input type=submit value=刷新></form>")
}
butt()
function auto(url){
document.forms[0]["url"+b].value=url
if(tim>200)
{document.forms[0]["txt"+b].value="链接超时"}
else
{document.forms[0]["txt"+b].value="时间"+tim/10+"秒"}
b++
}
function run(){for(var i=1;i<autourl.length;i++)document.write("<img src=http://"+autourl+"/"+Math.random()+" width=1 height=1

onerror=auto("http://"+autourl+"")>")}
run()</script>

37. 各种样式的光标
auto ：标准光标
default ：标准箭头
hand ：手形光标
wait ：等待光标
text ：I形光标
vertical-text ：水平I形光标
no-drop ：不可拖动光标
not-allowed ：无效光标
help ：?帮助光标
all-scroll ：三角方向标
move ：移动标
crosshair ：十字标
e-resize
n-resize
nw-resize
w-resize
s-resize
se-resize
sw-resize

38.页面进入和退出的特效
进入页面<meta http-equiv="Page-Enter" content="revealTrans(duration=x, transition=y)">
推出页面<meta http-equiv="Page-Exit" content="revealTrans(duration=x, transition=y)">
这个是页面被载入和调出时的一些特效。duration表示特效的持续时间，以秒为单位。transition表示使用哪种特效，取值为1-23:
　　0 矩形缩小
　　1 矩形扩大
　　2 圆形缩小
　　3 圆形扩大
　　4 下到上刷新
　　5 上到下刷新
　　6 左到右刷新
　　7 右到左刷新
　　8 竖百叶窗
　　9 横百叶窗
　　10 错位横百叶窗
　　11 错位竖百叶窗
　　12 点扩散
　　13 左右到中间刷新
　　14 中间到左右刷新
　　15 中间到上下
　　16 上下到中间
　　17 右下到左上
　　18 右上到左下
　　19 左上到右下
　　20 左下到右上
　　21 横条
　　22 竖条
　　23 以上22种随机选择一种

39.在规定时间内跳转
<META http-equiv=V="REFRESH" content="5;URL=http://www.51js.com">

40.网页是否被检索
<meta name="ROBOTS" content="属性值">
　　其中属性值有以下一些:
　　属性值为"all": 文件将被检索，且页上链接可被查询；
　　属性值为"none": 文件不被检索，而且不查询页上的链接；
　　属性值为"index": 文件将被检索；
　　属性值为"follow": 查询页上的链接；
　　属性值为"noindex": 文件不检索，但可被查询链接；
　　属性值为"nofollow": 文件不被检索，但可查询页上的链接。

注：出处不明，收集整理

[Code]C# Capital Initial首字母大写

2006-08-29T17:51:00.000+08:00

碰巧用到，记录一下：


using System.Globalization;
using System.Threading;

CultureInfo cultureInfo   = Thread.CurrentThread.CurrentCulture;
TextInfo textInfo = cultureInfo.TextInfo;

Console.WriteLine(textInfo.ToTitleCase(title));
Console.WriteLine(textInfo.ToLower(title));
Console.WriteLine(textInfo.ToUpper(title));

[Code]Rico使用初体验

2006-08-29T11:12:00.000+08:00

Rico真是个好东西！

具体感受过些时候再写:P

[Software]Happy Birthday, GTalk

2006-08-24T13:02:00.000+08:00

GTalk一岁了，Happy Birthday Gtalk!

[Code]用PowerDesigner生成测试数据

2006-08-23T11:50:00.000+08:00

PowerDesigner的确是个好东西，现在用它做数据库的辅助开发感觉很好。

PowerDesigner可以自动或半自动地生成一系列的测试数据，不紧可以用来对系统做压力测试，还可以使得开发人员从输入繁琐的测试数据中解脱出来。

下面介绍一下具体操作：

首先在Model -> Test Data Profile里创建测试数据的Profile，差不多就是指一种数据的档案吧，其中可以规定数据的格式，来源等等。如图一：

图一

未完待续...

[Internet]Cheat Sheet: Web 2.0

2006-08-23T11:31:00.000+08:00

from: here

注：

Cheet Sheet 这里有个Cheat，想当然的话，意思肯定不好。事实上，这个Cheap Sheet ,的原意的确也是小抄的意思，，所以字典的定义是：A piece of paper with information written down on it that an unethical person might create if they weren't prepared for a test.
由于对考试准备不足，夹带写着考试内容的纸条，此为品行不高的人的作为。
然而，曾几何时，Cheat Sheet 这个说法走出了贬义的阴影，成为简单说明，步骤说明书。如We asked the IBM Engineer to develop a cheat sheet for this machine.我们要求IBM公司给我们搞个简单的机器操作说明书。
The cheat sheet was attached to the package of the fancy camera.说明书就贴在高级照相机的包装盒上。

Cheat Sheet: Web 2.0

What on earth is it and should you care?

By Will Sturgeon

Published: Monday 21 August 2006

Web 2.0? I'm learning to spot a buzzword when I hear one and I think I just have...
Web 2.0 is one of those phrases which we're hearing a lot about currently. Everybody says they're very excited about it but do they really know what it is?

So what is it?
Well, in the simplest terms it's the phrase being applied to 'the second coming' of the internet. Dot-com investors are partying like it's 1999 and a number of pioneering online services are very much keeping that party exciting, getting everybody talking about the internet once more and its increasing relevance to our lives.

Such as?
Well, web 2.0 is a bit of a catch-all which covers a broad range of new online services, user-generated content, communities and social networking tools. The most popular are sites such as Blogger, Flickr, MySpace, YouTube and Wikipedia and the Godfather of web 2.0 - Google. The phrase also refers to the creation of far greater levels of interactivity, not just between users, or between users and the internet but between complementary online services through mash-ups and web services.

So this is all consumer stuff - photo-sharing and the like?
That's where a lot of the energy is coming from and the services doing the early running have absolutely been focused on driving and exploiting end-user trends. However, the idea that the web is 'where it's at' is not lost on big business. For example web 2.0 covers 'software as a service' (SaaS) - companies are being told they no longer have to buy software but instead should access applications online. Many people aren't yet ready to embrace that move but investors and advocates of SaaS are certainly convinced.

Where'd the name come from?
The 2.0 name is a clear allusion to the naming convention of software updates - this is the internet version 2.0, get it? - which is slightly ironic given the revolution taking place in software as a service isn't good news for traditional client/server software.

Why's that?
Well, to quote Marc Benioff, CEO of salesforce.com: "All of the action is in services. Web 2.0 is where the action is." His company has embraced this move whole-heartedly, providing a portal for all manner of web 2.0 applications aimed at the enterprise - including online word processors and spreadsheets (nobody said web 2.0 had to be limited to interesting, fun applications).

Gartner is also convinced web 2.0 should be a major consideration for businesses.

But should I care?
Absolutely you Luddite. Two or three years ago there was a feeling that innovation online had failed to emerge from the doldrums of the dot-com boom and bust cycle and had hit something of a dead end but now innovation is arguably at its most frenetic level ever. Never underestimate the effect the internet can have on our lives and now all we need is a browser and a broadband connection and there's very little we can't do.

Isn't there a danger that mistakes will be repeated? We've been here before, haven't we?
We've certainly, very famously, seen an internet boom before and history has shown us that bust follows boom but there is some bedrock here. Of course there are question marks over how YouTube will make money, for example - because great ideas and even popularity don't pay the bills - and the next stage for the investors will be monetising the excitement that surrounds web 2.0. Not every service which launches under that banner will survive but a great many will, probably though acquisition in a lot of cases.

Acquisition by whom?
Well Google for starters. The internet giant is absolutely at the heart of web 2.0 and the ability to bring many of these services together to create vast interlinked content offerings will certainly appeal. For the enterprise and end-user Google already offers a number of Office-style applications as a hosted offering. The company is also readying the finished version of its hosted email Exchange-offering.

The more, dare we say 'interesting' web 2.0 content will also appeal to Google as it puts ever more flesh on its content bones.

[Life]A Great Father

2006-08-21T13:55:00.000+08:00

Really Touching... A Great Father...

因为考虑到载入速度，嵌入播放器已经移除，可以到以下地址下载观看：
http://www.jinweijie.com/ryan/can1986.wmv

A glimpse of the remarkable father-son bond of Dick and Rick Hoyt, and their inspirational journey together in a triathlon and life itself.

the Original Link: Here

[Code]Asp.net CSS问题

2006-08-21T13:20:00.000+08:00

前段时间Sean碰到一个问题，在Html页面里样式都没问题，一旦用到aspx上，就会出现样式丢失的问题。

经过反复调试，终于发现问题所在，css里用的字体设成中文，比如 font-family:黑体; 就会导致当前class当前行下的css失效。

深入的原因没有调查下去，解决办法把css里的中文字体去掉就可以了

我估计可能是因为css的文件编码的问题，css本来就是文本文件，所以存在编码的问题，具体有空再进一步实验。

[Tricks]在线字体测试

2006-08-19T21:14:00.000+08:00

两个在线看字体效果的地址，实用:)

Typetester

Font Tester

[Software]Writely - Now Opened for Registration

2006-08-18T22:54:00.000+08:00

Writely，Google's Online Word Processing Application now opened for registration.

主要功能：

在线文字处理

发布到Blog（包括Blogger）

在线文字协作处理

点击这里马上尝试一下

:D

[Fun]Super Cool Video

2006-08-17T12:52:00.000+08:00

Balancing Point In Reverse

非常cool！

Original Link

[Code]用JavaScript执行PostBack

2006-08-17T11:08:00.000+08:00

早上实现了在子页面更新数据以后，父页面刷新树的功能

思路：

父页面有个隐藏的html button作为proxy，子页面保存完数据以后，用js调用父页面的html button的触发函数click()；

父页面有个asp.net的link button控件，text=""，等于也是隐藏的，它负责调用后台cs代码里的负责刷新树的方法；

父页面的html button onclick的时候，__doPostBack('DoRefresh','');

代码：

父页面apsx：

<input type="button" id="DoRefreshProxy" value="DO" onclick="__doPostBack('DoRefresh','');" style="display:none;" />

<asp:linkbutton id="DoRefresh" runat="server" onclick="DoRefresh_Click"  CausesValidation=False/>

父页面cs：


protected void DoRefresh_Click(object sender, EventArgs e)
{
 this.BindTree(this.tvBuilding.SelectedNodeIndex,1);
}

子页面cs：


Page.RegisterStartupScript("pb","<script>window.opener.document.getElementById('DoRefreshProxy').click();</script>");

[Code]ASP.net按钮提交前执行javascript

2006-08-17T10:27:00.000+08:00

here is the code...


<script language=“javascript“>
function doSomething()
{
   // 执行自己的javascript
   // 继续提交
   this.click();
}
</script>
<asp:button onmousedown=“doSomething()“ id=“someButton” Text="提交" runat="server"></asp:button>

[Software]Software product documentation

2006-08-16T09:23:00.000+08:00

Software product documentation

Learn how to write good documentation for your software

The ideal software would be free of errors and so easy to use that everybody would be familiar with it the minute they start the application. However, this is not the case in real life.

Besides the quality of the software product, there’s something else that makes or breaks the deal: technical support. The better the support software publishers and shareware authors provide, the more users are likely to buy the product.

Technical support for software products can be provided in several ways:

online product documentation
e-mail assistance
access to support forums maintained by software publishers
knowledge bases.

Good documentation may exclude in many cases the need for further forms of technical support. It is, however, not easy to write. One of the reasons why this happens is that it is difficult for shareware authors or other software developers to put themselves into the users’ shoes, since they are already thoroughly familiar with the application.

Read Me file

The first thing every software product should have is a text format "Read Me" file that includes the following:

Product Name and Version
Ship date
Company and Author Name
Description (like "photo organizer")
A What’s New list (this should be a list of fixes and new features)
System requirements (hardware like CPU, RAM, disk space, operating systems supported)
Price, payment options and instructions
Copyright and distribution information (rules for people who want to distribute your product)
Contact details (email, phone, fax website and postal address)

The "Read Me" file is important because everybody that might be interested in your product is expecting it, including reviewers, users, or people who want to put your product on a CD for distribution with a magazine or on their website. The idea here is to minimize frustration associated with the information being too difficult to find, therefore you should put all in one place.

The Manual

The other thing shareware authors and software publishers need to provide with their product is the manual. The first thing you should think about when starting to write it is how your users are going to use it. Few are those that will bother reading it all before attempting to use your product. They are more likely to turn to it later, when they try to do something and cannot figure out how to do it, or when they find something they do not understand.

To help them, it is best to organize your documentation by tasks. "How to…" sections are more useful than merely documenting every command in order. Explanations are easier to understand if they are backed by pictures and diagrams, wherever possible. There should also be a chapter labeled "Troubleshooting", which provides answers to the most common problems. At first you will have to guess where those problems may occur, but a couple of upgrades to your product later, the feedback from the people who tried the product will tell you what the most common problems are.

The manual should be broken down into chapters, the first of which telling what the other chapters contain, so that people could readily find what they need.

The interface

Another point worth mentionning is the interface. User friendly is not enough, the interface needs to be navigatable even if the user does not have an overall systems understanding, so screens need to be self-describing.

Online help or online documentation

There is also online help, or online documentation. The documentation put on the website for users to read has to show up in search results. It has to be organized in such a way that users, who are sure to be asking questions like "How can I…" or "Why can't I…" can find the answers quickly. Lots of examples showing how to do various tasks with the software product are also needed. A good idea is to include links to a glossary of terms that might be more difficult to understand.

Always bear in mind that anyone who has had a bad experience with a product tends to remember it for a long time and software is no different. That is why you should strive to make using your product as smooth an experience as possible, something proper support and documentation can help you achieve.

Published date: August 01, 2006

Copyright © 2006, http://www.avangate.com all rights reserved. This article was written by a Web Marketing Specialist at Avangate B.V. The author has in depth knowledge of internet marketing services and website analysis applied to the software industry and e-commerce development. Avangate is an eCommerce platform for electronic software distribution incorporating an easy to use and secure online payment system plus additional marketing and sales tools, such as an affiliate management system, automated cross selling options, software promotion management, software marketing services as well as consultancy on how to increase online software sales.

This article may be reproduced in a website, e-zine, CD-ROM, book, magazine, etc. so long as the above information is included in full, including the link back to this website. Please e-mail at articles@avangate.com , before using the article.

from:Here

[Code]IE Web Controls Tree View + XML

2006-08-14T22:31:00.000+08:00

搞了一下ie web control的 tree view，用xml绑定数据

记录分享一下

首先，下载ie web control

点击下载

一路安装好以后，它会谈出一个instruction，要我们build一下，有点像ant

编辑build.bat，在C:\Program Files\IE Web Controls 下（默认安装）
把csc.exe 改称 C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\csc.exe（默认安装）
保存，运行build.bat

它会build出一个C:\Program Files\IE Web Controls\build目录，里面有个Microsoft.Web.UI.WebControls.dll

接下来

复制C:\Program Files\IE Web Controls\build\Runtime 下所有文件到iis的程序目录，如果没有改的话，应该是C:\Inetpub\wwwroot\webctrl_client\1_0，webctrl_client和1_0两个目录手动建一下。

至此，安装完毕，接下来，来玩玩tree view

为了方便，可以把ie web controls的按钮添加到toolbox里面 tool -> add/remove toolbox item... browse，选择刚才那个Microsoft.Web.UI.WebControls.dll

toolbox里就多了几个东西，treeview, multipage什么的。

-----------------------------------------------

接下来，是运用tree view的环节，明天再写。

[Tricks]伪装Mac地址

2006-08-12T09:05:00.000+08:00

以前因为某种需要，找了一些修改Mac地址的方法（其实也就是操作系统级别的伪装而已），修改了注册表里的一些值,搞定

昨天又要改，偷懒找了一个软件，不用不知道，一用真方便。

SMAC 2.0

用了它，修改真方便。。。嘿嘿

[Code]JavaScript Selector

2006-08-12T00:36:00.000+08:00

刚做完一个小demo，用js模拟了一个selector的东东，想法是这样的：

假页面里的值先填好
如果没有某个参数（fillData），则将form里的值清空，如果带参数，则不要执行清空
打开一个子页面，点击子页面中的某个链接或按钮执行window.opener.location.href =
window.opener.location.href +'?fillData=true';window.close();
父页面（也就是先前说的假页面）就会刷一下，数据出现了


 <script language="javascript">
            function clearForm(){
                for (i=0; i<document.Form1.elements.length; i++){
                    if (document.Form1.elements[i].type=="text" || document.Form1.elements[i].type=="textarea"){
                        document.Form1.elements[i].value="";
                    }
                }
            }
           
            function checkPara(){
                var urlstr = window.document.URL;
                var parameterString = urlstr.replace(/.*\?(.*)/, "$1");
                var parameterTokens = parameterString.split("&");
                var parameterList = new Array();

                for (i = 0; i < parameterTokens.length; i++)
                {
                    var parameterName = parameterTokens[i].replace(/(.*)=.*/, "$1");
                    var parameterValue = parameterTokens[i].replace(/.*=(.*)/, "$1");

                    parameterList[parameterName] = parameterValue;
                }

                if( !parameterList["fillData"] )
                    clearForm();

            }
            checkPara();
        </script>

后续：真实的实现见：
用JavaScript执行PostBack

[Comment]Blogger解封？

2006-08-09T13:14:00.000+08:00

前段时间就看到部分blogspot.com站点可以访问的消息，但后来又不能访问了

今天突然发现jinweijie.blogspot.com可以访问了。但不知道是暂时的昙花一现呢，还是Google的blogger要杀进中国市场了。

一旦blogspot全面解封，无疑最恐慌的便是微软的space了，相信用space的人对微软的霸道多多少少会感到气愤吧，捆绑live messenger不说，还在用户毫不知情的情况下将msn space升级成live space，而且分辨率支持1024X768以上（反正以下会出现滚动条）。space速度本来就很慢了，升级后竟然在上方还出现了大大的ads banner，微软也应该不是那种靠广告为生的小公司吧，干嘛弄得这么猴急。

微软这种根本不把用户放在眼里的做法是在是让人不敢恭维！

希望blogspot解封，杀杀微软的嚣张气焰！阿门。。。

[Code]程序员和美工的配合问题

2006-08-06T10:06:00.000+08:00

看到Sean Blog的一篇关于美工和程序员的文章，觉得不错。

庆幸和我一起的是Sean，呵呵！我们使用的是解决篇里的第一种方式，因为Sean是那种达到了美工要求极高的那种程度，哈哈:P

程序员和美工存在的矛盾

1. 美工何时参与到项目中来

2. 程序员不懂如何将页面弄得美观，美工也不懂如何向页面中添加代码（即使是使用了Velocity）

3. 程序员和美工是两种完全不同的人，他们关心的事情也完全不同，这就导致两种人对页面代码（html）风格的要求大相径庭??程序员要得是简单易懂，美工要得是美观漂亮

4. 程序员要做的是将数据展现在页面上（使用简单的条件、循环语句），美工要做的是将美丽充满整个屏幕（程序员会叫道：天哪！这么复杂，我怎么用if、else、for来实现）

解决篇：

上面的这几点问题和矛盾从关系上来讲是层层递进的，要一个一个依次解决。先来说说美工何时介入到项目中来，在公司做过的这些项目以及我听说过的项目看，大致有以下几种：1）先有美工制作静态页面，完成后程序员直接向页面中添加程序代码；2）程序员随时和美工沟通，向美工描述页面需求，随要随做；3）程序员自己编写测试页面，然后让美工进行美化。

这3种方式可以说是个有利弊。方式1）对程序员来说绝对是个喜讯，它能使程序员最大限度的远离那些烦人的页面编码，提高程序员工作的含金量。同时，一套完整的页面可以展现全部业务的流程，对程序员开发也起到了规范的作用。但这种方式对美工的要求极高，美工要了解项目的需求，而这一般是达不到的。但可以让了解需求的人为其讲解，或是描绘出希望的页面的样式。这样虽然可以弥补美工对业务了解的不足，但也确实花掉了很多时间（而且是花掉了比较重要的人物的时间，因为了解整体业务的一般都是公司的牛人，他们的时间可是一刻千金呀）。方式2）是一个比较折中的方法，这样做无需太多的准备就可开始编码工作，程序员把握页面内容和样式，向美工详细描述，美工再根据描述设计页面，最后返回给程序员添加代码。这个反馈的过程一般比较迅速，效果也不错，可以达到程序员预期的效果，适用于项目时间要求比较紧的情况。该方式的问题在于没有一个形象化的完整的流程可供程序员参考，一切掌握在程序员手中，容易造成对需求的贪污和系统整体风格的不统一。方式3）一般用于对已有项目的美化上，对美工的要求也很高，她们需要具备在html和其他代码混合体的环境下工作的能力。而且修改的效果一般不是很佳，不到万不得已不推荐使用。

问题2.3.4.虽然表现出来的问题各不相同，但解决的方法却很相似。首先，美工要养成一些程序员编码时惯有的习惯，比如：文件命名要有意义、html代码要根据层次进行缩进等。其次，页面代码的一些细节也要注意，比如，使用居中或右对齐标签来取代空格，必须使用空格时也要用“ ”，不使用
标签，尽量使用表格等。再次，如果在条件允许的情况下，美工也可以学习一下夹杂在页面中的各种程序代码，了解其语义和工作原理，这将对与程序员的合作起到很大的帮助的。最后，就是程序员要在向页面文件中添加代码前先对页面代码做一下审核工作，在这里并不是看美工的页面是否美观，而是看在原有页面代码的基础上是否能够使用简单的条件、循环语句来显示数据（比如，页面布局过于复杂，不能通过简单的循环来显示所有数据），否则就需要修改页面代码直到能满足要求为止。

[Tricks]Accessing blogspot（如何正常访问blogspot）

2006-08-06T08:19:00.000+08:00

Sometimes I got 404 error on www.pkblogs.com. I don't know why but I guess the problem happened on particular network provider because Tracy Tang who is using a different network provider has no problem on this issue.

Pkblogs is not that reliable in China :P. After searching, I got another blogspot Gateway - www.inblogs.net, working as just the same as pkblogs. Need sometime to see whether the www.inblogs.net is stable. :D

Instructions:
if your blogspot address is: somelink.blogspot.com, visit www.inblogs.net/somelink instead.

If you got the problem like me, change the gateway to have a try.

[Tricks]去掉Blogger的Banner（Blogger的广告）

2006-08-03T19:19:00.000+08:00

去掉最上面blogger那个banner的办法：

进入控制台，编辑模版，在标签前<head>加上
<noscript>
<head></head>
</noscript>

在</body>后（</body>在比较后面的地方）加上

<noscript>
<body></body>
</noscript>

保存，发布，就可以了。

:P

--------------------------------------------

补充:（Thank you, Sally）

#b-navbar {
height: 0px;
visibility: hidden;
display: none;
}

copy and paste the CSS code above inside <.head.> section. :)

[Code]IE Bug or ?

2006-08-02T17:20:00.000+08:00

前几天在做一个小东西的时候碰到如下情况：

环境：

IE 6.0.2900.2180.xpsp_sp2_gdr.050301-1519
Visual Studio 2003
IIS 6.0

用了一个ASP.Net的Validator，由于外面的table的宽度是固定的，而Validator是Dynamic出现的，所以当Validator出现时（操作：输入不符合规则的字符，鼠标直接点下面奖金那一行的textbox），把所在的TR撑开，本来，光标的focus应该是落在下面的textbox上，撑开以后，原来focus的位置正好变成Validator的位置，结果就是：原来不能编辑的Validator可以输入字符了。

截图如下：

1. 2. 3. 4.

IE的bug？

[Comment]www.ie7.com

2006-08-01T12:37:00.000+08:00

check out ie7.com:

http://www.ie7.com

How does Microsoft feel about this site? haha

[Code]用Ruby写Fibonacci函数

2006-07-25T21:53:00.000+08:00

Ruby是门好语言，使得编程变得非常优雅

下面一个例子很好体现了这点：

很简单地实现了Fibonacci函数


def fib_up_to(max)
  i1, i2 = 1, 1 
  while i1 <= max
    yield i1
    i1, i2 = i2, i1+i2
  end
end

fib_up_to(1000) {|f| print f, " " }

输出：
1 1 2 3 5 8 13 21 34 55 89 ...

[Comment]Blogger体验

2006-07-25T10:21:00.000+08:00

Blogger可以让用户自己定义blog的外观，几乎可以做出一个和别人完全不一样的样式，只要有一定的html和css基础，这是我开始用Blogger原因之一。

在此以前一直没用Blogger是因为在中国Blogger是被FENG的，原因就不去追究了。现在找到了一个正常访问Blogger的方法，可能也不是什么新鲜的东西，可以通过www.pkblogs.com/xxxxx来访问(xxxxx表示你的blog名字，例如jinweijie.blogspot.com就可以用www.pkblogs.com/jinweijie来访问)。

另外，Blogger和Picasa集成，以后发照片也很方便。

还有很多。

我想说的是，工具再好，没有内容是不行的，嘿嘿:P

[Life]A Newbie Here

2006-07-24T22:39:00.000+08:00

There's a wish, there's a way, finally, I found a way to visit Blogger from China mainland, so i moved here right away.

Actually, in my opinion, MSN space is terrible for bloggers, slow and messy. Many people on MSN spaces forget one thing: Contents is important than those fancy tricks with MSN space, including me.

So, now, I need somewhere to write things, here it is.

Welcome, my friends.

[分类] Fun

2005-01-07T01:01:00.000+08:00

[分类] Software

2005-01-06T01:01:00.000+08:00

[分类] Bookmarks

2005-01-05T01:01:00.000+08:00

[分类] Tricks

2005-01-04T01:01:00.000+08:00

[分类] Code

2005-01-03T01:01:00.000+08:00

[分类] Comment

2005-01-02T01:01:00.000+08:00

[分类] Life

2005-01-01T01:01:00.000+08:00