Development Notes

Excel: Get cell comments

Categories: Development Notes; Tagged with: Excel; @ August 23rd, 2012 19:05

1. Alt + F11, in the opening window, click: Insert>Module, paste the folling code:
Function getComment(incell) As String On Error Resume Next getComment = incell.Comment.Text End Function

2. Alt + Q to quit the window

3. use the funciton in cell, like:
=getComment(A1) , will fill the cell with A1’s comments

Backup SVN repository using svnadmin dump 使用svnadmin dump备份SVN资料库

Categories: Development Notes • Linux; Tagged with: Subversion • SVN; @ June 27th, 2012 15:40

svnadmin dump ./repository/project > /home/backup/project_backup.svn.dump

manual: http://svnbook.red-bean.com/en/1.7/svn.ref.svnadmin.c.dump.html

Run Shell command using PHPShell in your shared host

Categories: PHP; Tagged with: PHP • PHPShell • Shell; @ June 23rd, 2012 13:19

PHP has a shell_exec command: “Execute command via shell and return the complete output as a string ” http://php.net/manual/en/function.shell-exec.php

And here is a project: http://phpshell.sourceforge.net/

PHP Shell

PHP Shell is a shell wrapped in a PHP script. It’s a tool you can use to execute arbitrary shell-commands or browse the filesystem on your remote webserver. This replaces, to a degree, a normal telnet connection, and to a lesser degree a SSH connection.

You use it for administration and maintenance of your website, which is often much easier to do if you can work directly on the server. For example, you could use PHP Shell to unpack and move big files around. All the normal command line programs like ps, free, du, df, etc… can be used.

Download and config phpShell,, and then upload to your server, then you can run shell!

http://phpshell.sourceforge.net/

CodeReview using Crucible and JIRA 使用Crucible,JIRA进行代码审查

Categories: Development Notes • Java; Tagged with: CodeReview • Crucible • JIRA; @ June 17th, 2012 13:41

Crucible is a tool that facilitates code review. It can be as valuable to organisations that already have a formal inspection process as it is to teams that don’t review at all.

Regular peer review is a proven process with demonstrable return on investment (ROI). The benefits vary from team to team but commonly include:

Identifying bugs and defects early.
Sharing expertise and encouraging knowledge transfer.
Improving system-wide knowledge.
Encouraging adherence to internal standards and style conventions.
Identifying individual strengths and weaknesses.

In my previous post “Link code change list and issue with FishEye and JIRA 关联代码变更与Issue/BacklogItem’’, test report a bug, and I submit my code change, and linked the code changes to the issue. and now, we need to review the codes I submitted before.

[David] Create a new code review by click ‘Create review’, select project, and input name, select the reviewers, and we can config weather anyone can join the review. we invite a guy named ‘admin’ to review my code.
[David] Add content to review: we can add a changeset, a file in the repositorie, or attachements, etc,.

Select the code change, and start the review.
[Admin] ‘admin’ login into curcible, and see the review:

In the left tree, there are the codes need to be review, click one:

Then mark as ‘Complete’
[David] And now, David can check the result:

It’s really cool!
[David ] summarize and close this review by clikc ‘summarize’ :
And what more, JIRA will link this review to the bug: