膘叔　　簡單人生

好象是说这款MSN软件不错（当然是linux下的），先加入源，顺便说一下，我的源是通过ubuntu tweak来进行更新的，这款tweak软件很方便，只要在第三方源里加入再刷新就行了，以下是需要加入的源的内容：

deb http://ppa.launchpad.net/galaxium/ubuntu hardy main
deb-src http://ppa.launchpad.net/galaxium/ubuntu hardy main

然后更新一下：apt-get update
最后运行 安装程序 ：apt-get install galaxium

然后就可以运行 了，界面也和msn差不多。。。

就是，连接的速度和成功率不如MSN，唉，没办法。。。没有先天优势啊

这两个域名在我身边很久了，当初的一些想法最后都没有做。在征得团队成员的同意后，决定出售这两个域名。

有需要的可以在此留言，或者加我QQ或者MSN等 。。。
QQ：１９１２９５４０
msn:ｇｏｕｋｉｘｉａｏ@ｈｏｔｍａｉｌ.ｃｏｍ，学学坏人，用全角，呵呵

by Kevin Yank

The following is republished from the Tech Times #165.

When interviewing a PHP developer candidate for a job at SitePoint, there is one question that I almost always ask, because their answer tells me so much about the kind of programmer they are. Here’s the question: “In your mind, what are the differences between good PHP code and bad PHP code?”

The reason I like this question is because it tests more than just a candidate’s encyclopedic knowledge of PHP’s functions. Zend’s PHP certification does a good job of that (as does the test that Yahoo! issues to applicants for its PHP developer jobs, apparently).

Rather, the answer to this question tells me whether a PHP developer has, for example, experienced the pain of working with poorly-written code inherited from a careless predecessor, and whether he or she will go the extra mile to save the rest of the team from that same pain.

I don’t have a set notion of the perfect answer to the question, but I do know the kinds of things I’m hoping to hear. Just off the top of my head:

Good PHP code should be structured. Long chunks of code can be broken up into functions or methods that achieve sub-tasks with simple code, while non-obvious snippets should be commented to make their meaning plain. As much as possible, you should separate frontend HTML/CSS/JavaScript code from the server-side logic of your applications. PHP’s object oriented programming features give you some especially powerful tools to break up your applications into sensible units.

Good PHP code should be consistent. Whether that means setting rules for the names of variables and functions, adopting standard approaches to recurring tasks like database access and error handling, or simply making sure all of your code is indented the same way, consistency makes your code easier for others to read.

Good PHP code should be portable. PHP has a number of features, such as magic quotes and short tags, that can break fragile code when they are switched on or off. If you know what you’re doing, however, you can write code that works by adapting to its environment.

Good PHP code should be secure. While PHP offers excellent performance and flexibility out of the box, it leaves important issues like security entirely in the hands of the developer. A deep understanding of potential security holes like Cross-Site Scripting (XSS), Cross-Site Request Forgeries (CSRF), code injection vulnerabilities, and character encoding loopholes is essential for a professional PHP developer these days.

Once a candidate has answered this question, I usually have a pretty good idea of whether they’ll be hired or not. Of course, there’s always the possibility that an interviewee simply isn’t able to articulate these types of things, so we also have our candidates sit a PHP developer exam.

Many of the questions in this exam seem straightforward on the surface, but they give candidates plenty of opportunity to show how much they care about the little details.

The following “bad” code is a highly simplified example of the sort of thing we might put in our PHP developer exam. The question might be something like “How would you rewrite this code to make it better?”
 
<?php
    echo("<p>Search results for query: " .
        $_GET['query'] . ".</p>");
?>

<?php
    echo("<p>Search results for query: " .     $_GET['query'] . ".</p>");
?>

The main problem in this code is that the user-submitted value ($_GET['query']) is output directly to the page, resulting in a Cross Site Scripting (XSS) vulnerability. But there are plenty of other ways in which it can be improved.

So, what sort of answer are we hoping for?

Good:
 
<?php
     echo("<p>Search results for query: " .
         htmlspecialchars($_GET['query']) . ".</p>");
?>


<?php
    echo("<p>Search results for query: " .
         htmlspecialchars($_GET['query']) . ".</p>");
?>

This is the least we expect. The XSS vulnerability has been remedied using htmlspecialchars to escape dangerous characters in the submitted value.

Better:
 
<?php
     if (isset($_GET['query']))
     {
       echo '<p>Search results for query: ',
           htmlspecialchars($_GET['query'], ENT_QUOTES), '.</p>';
     }
?>


<?php
    if (isset($_GET['query'])) {
        echo '<p>Search results for query: ',
          htmlspecialchars($_GET['query'], ENT_QUOTES), '.</p>';
    }
?>

Now this looks like someone we might want to hire:

    * The “short” opening PHP tag (<?) has been replaced with the more portable (and XML-friendly) <?php form.
    * Before attempting to output the value of $_GET['query'], isset is used to verify that it actually has a value.
    * The unnecessary brackets (()) around the value passed to echo have been removed.
    * Strings are delimited by single quotes instead of double quotes to avoid the performance hit of PHP searching for variables to interpolate within the strings.
    * Rather than using the string concatenation operator (.) to pass a single string to the echo statement, the strings to be output by echo are separated by commas for a tiny performance boost.
    * Passing the ENT_QUOTES argument to htmlspecialchars to ensure that single quotes (') are also escaped isn’t strictly necessary in this case, but it’s a good habit to get into.

Somewhat distressingly, the number of PHP developers looking for work that are able to give a fully satisfactory answer to this sort of question—at least here in Melbourne—are few and far between. We spent a good three months interviewing for this latest position before we found someone with whom we were happy!

So, how would you do when asked a question like this one? Are there any factors that make PHP code good or bad that you feel I’ve left out? And what else would you look for in a PHP developer?

用javascript+vml来做工作流，确实是第一次看到，所以我在看到有这个新闻的时候，就觉得特别的吃惊。当年的TRS就是因为有一个activex版的工作流控件的CMS，导致他的价格非常的高，今天能够看到有javascript版的，惊讶是难免的。。。

只是并非所有的机器都支持VML，所以它的适用范围还是有限的，不过，话又说回来，activex也只支持IE，但仍然有那么多人在用。看来，只要是好东西，即使你不跨平台，照样有人用的起劲。

闲话不说了，附上原文网址和他的说明，原文：http://www.cssrain.cn/article.asp?id=1192

开发语言;javascript,html,vml,json,css
功能：
1.环节可用鼠标拖拽
鼠标选中环节后不释放，拖拽鼠标，环节将随鼠标移动，释放鼠标后，环节不再移动。
2.路径的两个端点可以通过鼠标拖拽，改变路径指向的环节
鼠标选中路径的端点后不释放，拖拽鼠标，路径被选中的端点将鼠标移动，在选中的环节释放鼠标后，路径被选中的端点将指向该选中的环节。
3.ctrl+a，全选。
4.按住ctrl，鼠标选中对象，可以多选。
5.delete，删除选中对象。
6.使用鼠标多选
鼠标点击空白处不释放，拖拽鼠标，会出现一个长方形虚框，虚框的范围随着鼠标移动而变化，虚框范围内的对象将被选中。
7.动态添加环节和路径的属性

由于对这个东西很吃惊，所以，把图片和附件保存到了本地。需要的朋友可以点上面那个网址或者点本文的附件进行下载

（不好意思，刚发现附件有密码，我也不知道是什么密码，有破解软件的朋友只能辛苦一下了，或者去上面的cssrain.cn问站长去吧，我这里仅仅是作个备份）

下午四五点钟的时候，网站突然不能访问，很紧张，呵呵，PING了一下网址，不通，再PING IP地址仍然不通，不知道怎么回事，可能是机房那边出了问题吧。
看来，我真的是得了那种精神病了，对于网络的故障明显比其他人紧张的多。
不过也难怪，毕竟是自己在做的网站，虽然仅仅是博客，但也是自己的一番心血，总归是显得比别人担心的。。。

晚上回到家访问一下，正常了。oh yeah，很开心啊