博客园_冰冻三尺，非一日之寒

Silverlight 5几个不错的新特性

2011-12-10T08:59:00Z

1、PivotViewer（透视视图，具体什么作用没详细了解，没找到更详细的介绍）

The PivotViewer control enables you to display a large amount of data at once in a way that is easily consumable by the user. Users can browse the data in such a way that helps them see the trends and quickly find information they need. For more information see, PivotViewer.

2、DrawingSurface

DrawingSurface is a new control in Silverlight 5. DrawingSurface defines an area where 3-D content can be composed and rendered. You implement the rendering behavior through the event data of the Draw event. For more information, see 3-D Graphics Overview and Walkthrough: Creating and Animating a 3-D Textured Cube in Silverlight.

3-D绘图板，提供了方便的三维图形的绘制能力，令人心动的特性啊。

     3、本地文件的访问能力，在受信任环境中可以访问本地操作系统的文件，太强了。

     4、多窗口，只能在非浏览器的环境中使用，能提供多监视器显示不同窗口的能力。在监控类软件中可能特别有用。感觉与WPF有点儿趋同化。

     5、Windows API的访问能力，赤裸裸的诱导开发人员只为Windows的用户提供服务。

     6、矢量打印，Silverlight 4中提供了基于图像的打印，新版本升级啦。

     7、鼠标双击的判断，这么小的功能也作为新特性列出来，有点儿奇怪。

     8、XAML扩展，允许开发自定义格式的XAML解析器，可以开发一个WPF的解析器，在Silverlight里直接使用WPF的开发成果，岂不是很棒？
本文链接

无光驱采用U盘安装完整版xp

2011-11-17T19:51:00Z

这几天闲着没事折腾老机器，因为老机器的光驱扔了，本着也学习一下使用U盘装系统的技巧，就直接开始了，没想到这一折腾就是好几天。一开始网上找了不少资料，也没看完全就开始装系统了，最后发现这些教程大多是安装克隆版的，根本无法安装完整版xp，后面专门找了安装完整版xp的教程又开始了新一轮的折腾。教程里讲的需要安装过程中拔出u盘，在我这里也行不通，大概是每个人使用的winpe版本和硬件版本不一样导致的吧。

最后实在没办法，我只有采取U盘启动，然后将安装文件拷贝到硬盘的方式安装。下面是具体的安装步骤：

1、首先是选择winpe, 安装xp一定要选用xp内核的pe, win2003和win7内核的pe无法启动安装程序。而且最好是专门为u盘启动制作的winpe，我采用的是【老九 WinPE 老毛桃修改 1111 版】。光盘版的winpe没做过完全测试。

2、使用USB-HDD或者USB-HDD+格式将下载到winpe的iso文件写入到u盘。

3、开机进入BIOS设定，设定第一启动顺序为USB-HDD或USB-HDD+，保存设定后自动重启，进入winpe

4、如果硬盘没有分区，最好分一下，目的在于有两个以上的盘符，这样安装文件可以拷贝到C盘以外的盘符，我没有尝试将安装程序放在c盘下安装。

5、分区完成后将安装程序拷贝到C盘以外的盘符，由于我采用的这个版本的winpe的启动u盘占用了D盘符，我将安装文件拷贝到了E盘。

6、特别注意这时候还不能直接启动安装，因为启动U盘占用了D盘，而安装完成后再次启动时原先的E盘会成为D盘，所以需要做额外的工作，有的winpe的启动u盘占用的是Z盘符则没有此问题。首先将u盘中的磁盘管理工具拷贝到c盘或者非拷贝了xp安装程序的其它盘符。然后运行拷贝后的磁盘管理工具，将D盘和E盘卸载掉，然后再将原先的E盘加载为D盘。

7、启动winpe下的dos窗口，进入d盘存放安装程序的i386目录，运行命令：winnt32 /syspart:c ，一定要采用这种方式，我曾尝试在winpe下运行安装程序数次，统统失败。

8、等待安装程序拷贝文件，中间有几次用户交互信息，输入相应的信息即可，完成后会自动回到winpe界面，这时候拔掉u盘重新启动计算机即可。

9、硬盘启动后进入xp的安装程序直到安装完成。

本文链接

javascript 日期格式化（转）

2011-08-03T13:19:00Z

原文及附件：http://blog.stevenlevithan.com/archives/date-time-format

Mask	Description
`d`	Day of the month as digits; no leading zero for single-digit days.
`dd`	Day of the month as digits; leading zero for single-digit days.
`ddd`	Day of the week as a three-letter abbreviation.
`dddd`	Day of the week as its full name.
`m`	Month as digits; no leading zero for single-digit months.
`mm`	Month as digits; leading zero for single-digit months.
`mmm`	Month as a three-letter abbreviation.
`mmmm`	Month as its full name.
`yy`	Year as last two digits; leading zero for years less than 10.
`yyyy`	Year represented by four digits.
`h`	Hours; no leading zero for single-digit hours (12-hour clock).
`hh`	Hours; leading zero for single-digit hours (12-hour clock).
`H`	Hours; no leading zero for single-digit hours (24-hour clock).
`HH`	Hours; leading zero for single-digit hours (24-hour clock).
`M`	Minutes; no leading zero for single-digit minutes. Uppercase M unlike CF `timeFormat`'s m to avoid conflict with months.
`MM`	Minutes; leading zero for single-digit minutes. Uppercase MM unlike CF `timeFormat`'s mm to avoid conflict with months.
`s`	Seconds; no leading zero for single-digit seconds.
`ss`	Seconds; leading zero for single-digit seconds.
`l` or `L`	Milliseconds. `l` gives 3 digits. `L` gives 2 digits.
`t`	Lowercase, single-character time marker string: a or p. No equivalent in CF.
`tt`	Lowercase, two-character time marker string: am or pm. No equivalent in CF.
`T`	Uppercase, single-character time marker string: A or P. Uppercase T unlike CF's t to allow for user-specified casing.
`TT`	Uppercase, two-character time marker string: AM or PM. Uppercase TT unlike CF's tt to allow for user-specified casing.
`Z`	US timezone abbreviation, e.g. EST or MDT. With non-US timezones or in the Opera browser, the GMT/UTC offset is returned, e.g. GMT-0500 No equivalent in CF.
`o`	GMT/UTC timezone offset, e.g. -0500 or +0230. No equivalent in CF.
`S`	The date's ordinal suffix (st, nd, rd, or th). Works well with `d`. No equivalent in CF.
`'…'`or`"…"`	Literal character sequence. Surrounding quotes are removed. No equivalent in CF.
`UTC:`	Must be the first four characters of the mask. Converts the date from local time to UTC/GMT/Zulu time before applying the mask. The "UTC:" prefix is removed. No equivalent in CF.

And here are the named masks provided by default (you can easily change these or add your own):

Name	Mask	Example
default	ddd mmm dd yyyy HH:MM:ss	Sat Jun 09 2007 17:46:21
shortDate	m/d/yy	6/9/07
mediumDate	mmm d, yyyy	Jun 9, 2007
longDate	mmmm d, yyyy	June 9, 2007
fullDate	dddd, mmmm d, yyyy	Saturday, June 9, 2007
shortTime	h:MM TT	5:46 PM
mediumTime	h:MM:ss TT	5:46:21 PM
longTime	h:MM:ss TT Z	5:46:21 PM EST
isoDate	yyyy-mm-dd	2007-06-09
isoTime	HH:MM:ss	17:46:21
isoDateTime	yyyy-mm-dd'T'HH:MM:ss	2007-06-09T17:46:21
isoUtcDateTime	UTC:yyyy-mm-dd'T'HH:MM:ss'Z'	2007-06-09T22:46:21Z

本文链接

jQuery URL Parser 帮助

2011-07-18T11:35:00Z

jQuery URL Parser v2.0

A jQuery plugin to parse urls and provide easy access to their attributes (such as the protocol, host, port etc), path segments, querystring parameters, fragment parameters and more.

The core parser functionality is based on the Regex URI parser by Steven Levithan.

Please note that version 2 is not backwards compatible with version 1.x of this plugin. v1.1 is still available for download should you need it for some reason.

This plugin requires jQuery to work. Tested on 1.4 and above but will probably work on older versions, too.

License: http://unlicense.org/ - i.e. do what you want with it :-)

Specifying the URL to parse

There are a few different ways to choose what URL to parse:

var url = $.url(); // parse the current page URL
var url = $.url('http://allmarkedup.com'); // pass in a URI as a string and parse that
var url = $('#myElement').url(); // extract the URL from the selected element and parse that - will work on any element with a `src`, `href` or `action` attribute.

URL attributes

The .attr() method is used to return information on various parts of the URL. For example:

var url = $.url('http://allmarkedup.com/folder/dir/index.html?item=value');
url.attr('protocol'); // returns 'http'
url.attr('path'); // returns '/folder/dir/index.html'

The attributes available for querying are:

source - the whole url being parsed
protocol - eg. http, https, file, etc
host - eg. www.mydomain.com, localhost etc
port - eg. 80
relative - the relative path to the file including the querystring (eg. /folder/dir/index.html?item=value)
path - the path to the file (eg. /folder/dir/index.html)
directory - the directory part of the path (eg. /folder/dir/)
file - the basename of the file eg. index.html
query - the entire querystring if it exists, eg. item=value&item2=value2
fragment (also available as anchor) - the entire string after the # symbol

There are also a few more obscure ones available too if you want to dig about a bit ;-)

If you don't specify an attribute then this method will return an object literal with all the available attribute key:value pairs in it.

Query string parameters

The .param() method is used to return the values of querystring parameters.

Pass in a string to access that parameter's value:

$.url('http://allmarkedup.com?sky=blue&grass=green').param('sky'); // returns 'blue'

If no argument is passed in it will return an object literal containing a key:value map of all the querystring parameters.

$.url('http://allmarkedup.com?sky=blue&grass=green').param(); // returns { 'sky':'blue', 'grass':'green' }

Note that the .param() method will work on both ampersand-split and semicolon-split querystrings.

URL segments

The .segment() method is used to return values of individual segments from the URL's path.

Pass in an integer value to get the value of that segment - note however that the count is not zero-indexed like an array - i.e. .segment(1) returns the firstsegment, not the second one.

You can also pass in negative values, in which case it will count back from the end of the path rather than forwards from the start.

var url = $.url('http://allmarkedup.com/folder/dir/example/index.html');
url.segment(1); // returns 'folder'
url.segment(-2); // returns 'example'

If no argument is passed in it will return an array of all the segments (which will be zero-indexed!).

$.url('http://allmarkedup.com/folder/dir/example/index.html').segment(); // returns ['folder','dir','example','index.html']

Fragment parameters and/or segments

Some sites and apps also use the hash fragment to store querystring-style key value pairs (eg. http://test.com/#sky=blue&grass=green), or slash-delimited paths (eg. http://test.com/#/about/us/).

There are two methods available for extracting information from fragments of these types - .fparam() and .fsegment(), both of which behave indentically to their .param() and .segment() counterparts but act on the fragment rather than the main URL.

$.url('http://test.com/#sky=blue&grass=green').fparam('grass'); // returns 'green'

$.url('http://test.com/#/about/us/').fsegment(1); // returns 'about'

Enabling strict mode

Internally this plugin uses Steven Levithan's excellent Regex URI parser, which has two modes - loose and strict. This plugin uses the loose mode by default (i.e. strict mode set to false), which deviates slightly from the specs but produces more intuitive results. If for some reason you prefer to use the strict parser and so be fully spec-compatible, then you can enable this when calling the plugin as follows:

var url = $.url(true); // parse the current page URL in strict mode
var url = $.url('http://allmarkedup.com',true); // pass in a URI as a string and parse that in strict mode
var url = $('#myElement').url(true); // extract the URL from the selected element and parse that in strict mode

A note on improperly encoded URLs

If you attempt to use this plugin to parse a URL that has an invalid character encoding in it, it will throw a URIError Exception. This will happen if the URL has a percentage sign followed by either a non-numeric character or a numeric value of greater than 80 (i.e. 128 in decimal).

If there is a chance you may end up parsing a badly encoded URL you should probably wrap your calls to this plugin in a try/catch block to prevent this causing unforseen problems.

Thanks to steve78b for pointing this out.

本文链接

.net环境下的javascript引擎汇总

2011-07-17T17:56:00Z

Jint –比较早的引擎，不依赖于DLR, 性能较差，且有缺陷，没有全部支持ECMAScript 3.0, http://jint.codeplex.com/

Jurassic – 基于.net 4的引擎，编译为CLI执行，但性能比不上V8, http://jurassic.codeplex.com/

Ironjs - 基于DLR的引擎，据说性能能与V8相提并论，但仍在开发中，https://github.com/fholm/IronJS，博客：http://ironjs.wordpress.com/

Rhino JavaScript 这是Java语言的引擎，但通过IKVM.NET可以编译到.net下。

RemObjects Script for .NET 一个基于DLR的引擎，但免费使用有限制。

以上引擎在老赵的博客（http://blog.zhaojie.me/2010/11/execute-javascript-at-server.html）中有较详细介绍。

其它还有：

jish 包括一个js.net，这是对V8引擎的一个.net封装。https://github.com/gatapia/jish

javascript.net 这是一个对V8引擎的封装，不过作者最后一次更新是在2010-9-16号，仍然是Beta版 http://javascriptdotnet.codeplex.com/

V8sharp是另一个对V8引擎的封装，不过至今尚无可下载版本，可以下载源码研究一下，http://v8sharp.codeplex.com/ （从2010开始没有更新了）

本文链接

使用ANTLR进行命令行参数解析

2009-03-28T17:38:00Z

关于命令行参数的解析没有特定的规则，目前比较流行的有unix风格和微软风格。其实除了unix风格的比较一致外，微软自己提供的命令行参数解析就有很多种风格。在.net平台下的main函数中，仅仅把参数分解为以空格分割的数组，这对需要加开关，并且有的开关有自己的参数的情况是不够的，而且为了解析这些参数需要学习部分词法分析的知识，这对用处不是很大的命令行参数显得有些“鸡肋”，当然...

使用VSTA定制二次开发IDE（一）

2009-03-27T08:39:00Z

Visual studio tools for application是微软免费提供的方便开发人员定制应用程序的工具。通过在开发人员发布的应用程序中集成.Net framework和可再次分发的IDE，我们的最终用户可以使用VB.net和C#开发插件，最终改变应用程序的行为。其效果与office的VBA是一样的，而且office2007就是基于VSTA做的扩展。想在应用程序中集成IDE主要的步骤...

探讨Antlr中文文法与英文文法的差异

2009-03-21T07:09:00Z

Antlr是一个很好的词法和语法分析器，而且可以直接生成Tree walker，解决了编译器设计中的大麻烦。最近在利用Antlr开发自己的领域语言（DSL）的时候发现了一个问题，就是中文文法与英文文法的差异问题。目前在领域语言的设计中，趋向于采用类似于自然语言的设计方式，例如：I eat apple.其中I是一个对象，eat 是对象I的方法，apple是传入到eat方法中的参数。这句话转换为面向对...

.net与java中关于访问性的差异

2006-10-21T14:35:00Z

在.net下如下的代码是允许的 class Program { static void Main(string[] args) { B b = new B(); b.X = 20; b.Print(b); Console.ReadLine(); } } class A { int x; public void Print(B b) { Console.Write(b.x); //可以通过编译 }...

老罗语录

2006-10-11T10:32:00Z

http://www.weigang.com/新东方罗永浩音频/传统论.mp3 http://www.weigang.com/新东方罗永浩音频/毒品.mp3 http://www.weigang.com/新东方罗永浩音频/恶心的春晚.mp3 http://www.weigang.com/新东方罗永浩音频/怪问题.mp3 http://www.weigang.com/新东方罗永浩音频/反封建迷信.m...