最前端

我的工作,我的生活,点点滴滴...

归档: ‘ 2011 年五月

Aptana的SVN插件Subclipse版本引起的问题

subversion logo

今天早上提早了快一个小时到公司,打开Aptana准备折腾一下,没想到Aptana的SVN插件subclipse彻底的罢工了,提示:

aptana svn error

Errors occurred while updating the change sets for SVNStatusSubscriber
org.tigris.subversion.javahl.ClientException: Unsupported working copy format
svn: This client is too old to work with working copy ‘F:\ecp’. You need
to get a newer Subversion client, or to downgrade this working copy.
See http://subversion.tigris.org/faq.html#working-copy-format-change
for details.

org.tigris.subversion.javahl.ClientException: Unsupported working copy format
svn: This client is too old to work with working copy ‘F:\ecp’. You need
to get a newer Subversion client, or to downgrade this working copy.
See http://subversion.tigris.org/faq.html#working-copy-format-change
for details.

回想了一下周末,我也没做过特别坏的事啊,怎么RP骤降了?!仔细看了看官方的FAQ:

Sometimes the working copy metadata format changes incompatibly between minor releases. For example, say you have a working copy created with Subversion 1.4.4, but one day you decide to try out Subversion 1.5.0. Afterwards, you attempt to switch back to 1.4.4, but it doesn’t work — it just gives the above error.
This is because 1.5.0 upgraded your working copy format to support some new features (in this case, changelists, the keep-local flag, and variable-depth directories). Although 1.4.4 doesn’t know anything about these new features, it can at least recognize that the working copy format has been upgraded to something higher than it can handle.
1.5.0 upgraded the working copy for a good reason: it realizes that 1.4.4 does not know about these new features, and that if 1.4.4 were to meddle with the working copy metadata now, important information might be lost, possibly causing corruption (see issue #2961, for example).
Subversion 1.7.0 and newer will not upgrade working copies unless you explicitly ask them to do so. (Upgrading the working copies is, however, required; Subversion 1.7.0 cannot operate on working copies created or used by earlier Subversions.)
Subversion 1.6.x and earlier automatically upgrade working copies when they first touch them. This behavior can be annoying, if you just want to try out a new release of Subversion without installing it permanently. For this reason, we distribute a script that can downgrade working copies when doing so is safe:
http://svn.apache.org/repos/asf/subversion/trunk/tools/client-side/change-svn-wc-format.py
Run that script with the “–help” option to see how to use it. (It can downgrade 1.6.x working copies to formats usable by Subversion 1.4.x and 1.5.x, but cannot downgrade 1.7.x working copies.)
As future versions of Subversion are released, we will try to keep this FAQ entry up-to-date with potential downgrade scenarios and their implications.

估计是上周五手痒惹的祸,回家前升级了一下公司电脑的SVN客户端TortoiseSVN,好吧,我Subclipse用的是1.4版本,貌似,再瞄一眼本机的TortoiseSVN,天煞的,都Version 1.6.14了,赶紧更新吧插件吧:

  1. 工具栏>‘Window’->‘Preferences’,展开树‘Install/Update’->’Available Software Sites’,然后就是把Subclipse安装/更新地址改为http://subclipse.tigris.org/update_1.6.x;available software sites
  2. 工具栏->’help’->’Check for Updates’,然后就是和安装时一样的步骤了,全选,一路的next,然后restart Aptana;check for updates
  3. 成功!

关于博客的font-family

font-family

最近没事折腾了下本博客,主要是为了养眼点,虽然文章不多。设计咱不专业啊,就修改一下css了,其中为了body的一个font-family属性来来回回修改了不下十次,自己觉得不错了,给同事一看,完了!每个人都有不同的审美观啊。算了,大道至简这是我的经典借口之一吧,于是乎找到了很久之前读到的一遍关于font-family的系列文章谈谈网页设计中的字体应用 并且重新温习了一遍,选了一套比较经典的且适合自我感觉本博客的font-family。

font-family: Tahoma, Helvetica, Arial, sans-serif;

这套font-family之所有经典,有以下几个特点:

  1. Tahoma是Windows 2000、Windows XP、Windows Server 2003的默认字体,圆滑,修正了Arial字体的一些令人难以阅读的毛病,比如大写I,小写i和l的视觉上的混淆。
  2. Helvetica是苹果电脑的默认字体,简洁优雅,它甚至还有一部记录片–《赫维提卡体》;Helvetica
  3. Arial是一般系统都有安装的字体,即使Mac OS,虽然它不是很完美;
  4. Sans-serif在以上字体都没有的时候,提供一个无衬线的通用字体类族名称作为最后的选择。通用字体类族有:”serif”、”sans-serif”、”cursive”、”fantasy”、”monospace”等,这一点好像腾讯cdc也没有注意到可能问题不大?
    font-family:Tahoma,"宋体";/*腾讯cdc的font-family*/

CSS类是HTML标签的扩展?

sexy css

CSS类的命名是一件麻烦的事,有人提到了CSS类命名的语义化[1],这个建议从某些方面来说确实比以结构来命名CSS类好多了。而且我发觉语义化的CSS类甚至成为了HTML标签的一个扩展,HTML标签是有限的,而网页有语义的部分是无限的,使用HTML的语义化只能是基于有限的HTML标签及其属性来实现语义化。比如:

<div class="logo">
<h1 class="blog-name"><a href="http://www.bq69.com">最前端的生活</a></h1>
<h2 class="blog-description">关注web前端,关心web前端工程师</h2>
</div>

h1的语义能说明这是一个一级标题,h2的语义能说明这是一个二级标题,如果我需要一个详细的语义呢,比如:“博客的名字”,“博客的描述”等,显示h1,h2是不足够的。从上面的代码HTML标签h1,h2的语义,搜索引擎知道了两个标题;而从CSS类logo,blog-name,blog-description得知这个博客的logo,标题和博客描述(注:请先忘记header的部分标签,另外我我相信google能做到这个)。

不知道CSS类从这个方面来看,能不能算是HTML标签的扩展,但我相信CSS类的语义化的确有利于SEO的。

参考资料