Add the following to ~/.bashrc

export PS1='\[\033[01;32m\]\h\[\033[01;34m\] \w\[\033[31m\]$(__git_ps1 "(%s)") \[\033[01;34m\]$\[\033[00m\] '

http://www.holubmichal.cz/2011/03/indicate-git-branch-in-prompt-ubuntu/

3 more days until Chinese New Year!

Spent 4 hours practising my rusty calligraphy yesterday, but hey, effort counts! The new year fai chun will be posted to parents tomorrow. Happy Chinese New Year!

> sudo gem install yard
Successfully installed yard-0.5.8
1 gem installed
Installing ri documentation for yard-0.5.8...

RDoc failure in lib/yard/core_ext/hash.rb at or around line 13 column 11

Before reporting this, could you check that the file
you're documenting compiles cleanly--RDoc is not a
full Ruby parser, and gets confused easily if fed
invalid programs.

The internal error was:

ERROR:  While generating documentation for yard-0.5.8
... MESSAGE:   Name or symbol expected (got #)
... RDOC args: --ri --op /var/lib/gems/1.8/doc/yard-0.5.8/ri --quiet lib --title yard-0.5.8 Documentation
(continuing with the rest of the installation)
Installing RDoc documentation for yard-0.5.8...

RDoc failure in lib/yard/core_ext/hash.rb at or around line 13 column 11

Before reporting this, could you check that the file
you're documenting compiles cleanly--RDoc is not a
full Ruby parser, and gets confused easily if fed
invalid programs.

The internal error was:

ERROR:  While generating documentation for yard-0.5.8
... MESSAGE:   Name or symbol expected (got #)
... RDOC args: --op /var/lib/gems/1.8/doc/yard-0.5.8/rdoc --quiet lib --title yard-0.5.8 Documentation
(continuing with the rest of the installation)

sudo apt-get remove rdoc

Then uninstall yard and rdoc gems if you have installed them already

sudo gem uninstall rdoc

sudo gem uninstall yard

Then re-install rdoc and yard gems

sudo gem install rdoc

sudo gem install yard

This worked for me.

A selection of my art work is available from http://jennyfong.daportfolio.com/gallery/321365

Ciao, my old website

Global commands are independent of any editor instance (focusing a specific editor or adding a new editor to a textarea, for example). Instance commands are for a specific editor instance (making the current selection in a specific editor bold, for example).

http://wiki.moxiecode.com/index.php/TinyMCE:Commands

The wiki page has a good range of instance commands covered, but I was unable to locate those I wanted and some took me a while to find, in this post I’m going to list the typical instance commands, this is particular useful if you are building elements outside the editor, e.g. An external toolbar. The list applies to TinyMCE version 3.

tinyMCE.execCommand(command, user_interface, value)

tinyMCE.activeEditor.execCommand('mceSave', false, null)

For any other commands or calling a custom plugin, it’s pretty easy to find, go to the plugins directory – javascript/tinymce/jscrips/tinymce/plugins
And find the editor_plugin_src.js, and in that file find the line

ed.addCommand('mceExample', function() {
..

This line registers the command, so that you can call

tinyMCE.activeEditor.execCommand('mceExample');

to trigger this.

For example when using Prototype together with jQuery:

<script src="prototype.js" type="text/javascript"></script>
<script src="jquery.js" type="text/javascript"></script>
<script type="text/javascript>
jQuery.noConflict();
</script>
<script src="myfile.js" type="text/javascript"></script>

jQuery(document).ready(function($) {
// We can use $ like normal here
});

Reference: Page 38, Learning jQuery 1.3 by Jonathan Chaffer, Karl Swedberg

Download a Virtual PC – This only supports machines up to 32 bits
http://www.microsoft.com/downloads/details.aspx?FamilyId=6D58729D-DFA8-40BF-AFAF-20BCB7F01CD1&displaylang=en

For 64 bits machines or windows 7 machines
http://www.microsoft.com/windows/virtual-pc/download.aspx

Download VPC Image for IE6, IE7 and IE8
http://go.microsoft.com/fwlink/?LinkId=70868

Alternatively, you can download a software called IEtester which has all IE versions included, but the build versions are different from the VPC images above.

IETester: http://www.my-debugbar.com/wiki/IETester/HomePage

I always use both to test IE6 as they can behave differently with just one minor version apart.

IE6 Build version on IETester is 6.0.2800.1314
http://www.my-debugbar.com/forum/p1401-2009-04-14-08:25:25.html

desc 'Create YAML test fixtures from data in an existing database.
Defaults to development database.  Set RAILS_ENV to override.'

task :extract_fixtures => :environment do

sql  = "SELECT * FROM %s"
skip_tables = ["schema_info"]
ActiveRecord::Base.establish_connection
(ActiveRecord::Base.connection.tables - skip_tables).each do |table_name|
i = "000"
File.open("#{RAILS_ROOT}/test/fixtures/#{table_name}.yml", 'w') do |file|
data = ActiveRecord::Base.connection.select_all(sql % table_name)
file.write data.inject({}) { |hash, record|
hash["#{table_name}_#{i.succ!}"] = record
hash
}.to_yaml
end
end

end

Install Rcov

You have two options:

1. Gem install (lightweight and very easy to install):

sudo gem install rcov

2. Full install from tarball (claimed to be over 100 faster but requires Ruby 1.8.3 or above, this is great if you’re running RCov continuously. E.g.√Ǭ† On cruise control):

Download RCov from:

http://eigenclass.org/hiki.rb?rcov#l1

Run the following command to fire the setup:

sudo vender/plugins/rcov/setup.rb

If you cannot compile extensions for some reason, or you have an older Ruby (<1.8.3), try:

ruby setup.rb all --without-ext
Run tests

Macintosh:trunk jennyfong$ rcov test/*.rb

Loaded suite /usr/bin/rcov
Started
Finished in 0.000256 seconds.
0 tests, 0 assertions, 0 failures, 0 errors

You will probably notice the test coverage includes your gems directory, you can use the exclude argument to exclude it from the list:

rcov test/*.rb --exclude gems

require 'rcov/rcovtask'
desc 'Measures test coverage using rcov'
namespace :rcov do
desc 'Measures test coverage'
task :coverage do
rm_f "coverage"
rm_f "coverage.data"

rcov = "rcov --rails --aggregate coverage.data --text-summary -Ilib  --exclude osx\/objc,gems\/,spec\/"
system("#{rcov} --no-html test/unit/*_test.rb")
system("#{rcov} --no-html test/functional/*_test.rb")
system("#{rcov} --html test/integration/*_test.rb")
system("open coverage/index.html") if PLATFORM['darwin']
end

desc 'Measures unit test coverage'
task :unit do
rm_f "coverage"
rm_f "coverage.data"
rcov = "rcov --rails --aggregate coverage.data --text-summary -Ilib  --exclude osx\/objc,gems\/,spec\/"
system("#{rcov} --no-html test/unit/*_test.rb")
system("open coverage/index.html") if PLATFORM['darwin']
end

desc 'Measures functional test coverage'
task :functional do
rm_f "coverage"
rm_f "coverage.data"
rcov = "rcov --rails --aggregate coverage.data --text-summary -Ilib  --exclude osx\/objc,gems\/,spec\/"
system("#{rcov} --no-html test/functional/*_test.rb")
system("open coverage/index.html") if PLATFORM['darwin']
end

end

The codes above are extracted from: http://clarkware.com/cgi/blosxom/2007/01/05 with modifications.

4. Troubleshoot

Segmentation fault when trying to run ‘rcov test/*.rb’ on Ubuntu 9.10

jfong@netty:~/website$ rcov test/*.rb

/home/jfong/.gem/ruby/1.8/gems/rails-2.2.2/lib/ruby_version_check.rb:2: [BUG] Segmentation fault<br/>
ruby 1.8.7 (2009-06-12 patchlevel 174) [i486-linux]<br/>
Aborted

Then I tried to un-install the gem and I got:

sudo gem uninstall rcov
ERROR:  While executing gem ... (Gem::InstallError)
Unknown gem rcov <= 0

Now the gem is removed successfully and when I tried to install rcov again there was no error, but .. it was still not working! Somehow the gem directory was messed up and I ended up replacing my ruby directory under /opt/ with a working copy from my colleague and it all works again.

Make sure you add it to your path if the ruby directory is changed:
export PATH=/opt/enterprise-ruby/bin/:$PATH
I’m afraid this might not be the best solution and if you know a better way to resolve this please let me know.

References:

http://eigenclass.org/hiki.rb?rcov#l1

http://clarkware.com/cgi/blosxom/2007/01/05

http://thelucid.com/2007/08/24/using-rcov-to-measure-the-test-coverage-of-rails-plugins/