Crawljax gets a face lift. Web UI in Crawljax 3.5

Crawljax is an open source tool for crawling Ajax-based modern web applications by analyzing DOM state changes. Latest feature that will be available with Crawljax 3.5 is a Web front end for Crawljax. It supports all the major functionality of crawljax like, adding/editing crawl configurations, installing plugins, viewing crawl logs in real time and displaying plugin output. This is implemented using the common java web application stack and ember.js MVC framework. Kudos to developers, @jeremyhewett and @ryansolid.
To run it, simply unzip the web distribution archive and run the command java -jar crawljax-web-3.5-SNAPSHOT.jar. You can customize the port and output directory using -p and -o arguments. Here are some screen-shots of the web interface in action. More usage tutorials will follow.

Crawljax Web UI Home - You can start by adding a 'New Configuration' as shown

'Edit Configuration' Page

'Add Plugin' Page

Crawl status log with real-time updates

Output of the Crawl Overview plugin

Read the original post at crawljax.com

Related links

• Crawljax source on github
• Tutorial on Common Java Web Application Stack

Set svn to ignore auxiliary LaTeX files globally

There are certain intemediary files (.aux, .log, etc.) that are best not put under version control because they change very often. In SVN, to stop svn status complain about them, you can add those patterns to the global-ignores property in your ~/.subversion/config file (or "%APPDATA%\Subversion\config" on Windows).

If you just want to set it for one repository, you can use svn propedit svn:ignore . or svn propset as explained here.

PS: Read Configuration Area Layout in the red bean book or this SO question for more information.

tcsh/csh tips for the bash user

The official shell in FreeBSD is tcsh/csh, and in Debian/Ubuntu, it's dash or bash. The back-story is, these fall into two families of shells: Ones derived from the original bourne shell (sh) which include bash, ksh etc. and those derived from the C shell which include csh, tsch, etc. These use slightly different commands for setting environment variables etc.

• You can check the type of shell you are using by the commands echo $shell or echo $0
  Note: $0 is actually the name of the running process. It will return the name of the shell or shell script according to the context. Read more on that here: http://www.tldp.org/LDP/abs/html/othertypesv.html#CHILDREF2
  
• You can get a list of all the shells installed on your system by typing

cat /etc/shells 

• ..and also change the default one to a different shell (if you have the permissions) using the command chsh.
• If you are moving from bash to tcsh, you will find your .bashrc file (or even .bash_profile, .profile) doesn't work anymore. It's the ~/.cshrc file in tcsh instead. And for setting environment variables, rather than the old command.. PATH= $PATH:$HOME/bin; export PATH you will have to use something like.. 

setenv PATH ${PATH}:${HOME}/bin

 Note the missing '='.

More related reading:

• bash and tcsh commands comparison table
• Setting Environment Variables
• C Shell. Why Not?