What went wrong was as simple as using type=”text/javascript” for javascripts in stead of type=”application/javascript”. gah.

As allways, feedback is appreciated!

the new version is located here.

The old versions can still be found here if anything stops working for you:

version 0.1

version 0.2

Related posts:

1. Neptune’s Pride Battle Calculator

The game uses some simple math to calculate the outcome of battles, and since I am lazy I got tired of doing that math and started working on a battle calculator.

This is my first attempt on php, and it is a work in progress… so feedback is appreciated.

Try it out here: Neptune’s Pride Battle Calculator

UPDATE:

I have ditched php, and gone for javascript in v0.2 of the calculator… Now the workflow is more streamlined since you don’t have to go between different pages to get to results.  Seems to be some css-problems though. And javascript issues with IE. Working on it.

…And apparently IE doesn’t care about height / min-height unless you add an !important to it.

the old version can still be found here

Related posts:

1. Neptune’s Pride Battle Calculator v0.3

After some tweaking around in analytics it turned out that most of the new bouncing traffic came from Safari, from a machine with the same screen resolution as mine, from my city, my broad band provider and so on.

It turns out that this is because my blog had appeared on Safaris “Top Sites”, a grid of often visited web pages on the welcome screen of Safari. And every time you open safari, it contacts the webpage for an updated snapshot of the page.  This is recorded by analytics and regarded as a bounce visit, decreasing your average time on site and increasing your bounce rate.

So far, it doesn’t seem like there is any other solution to this except removing the site from “Top Sites”, until Google or Apple figure something out.  This of course does not solve the, for me not yet existing, problem of bogus traffic from other Safari users.

No related posts.

\usepackage[T1]{fontenc}

Now everything (at least for norwegian documents) should be working as expected.

Related posts:

1. Citing / displaying source code in LaTeX

word on the street has it Saiboten may in fact be geeky enough to have accomplished this feat

No related posts.

Thanks, Peder 2.

No related posts.

It is based on the listings package, we define a lstset that handles the code.  This in combination with a nice caption makes for a nice presentation of source code.

Here is the final result:

LaTeX Source Code Screenshot

“Read more” for the rest of the article

The packages needed are:

• \usepackage{listings}
• \usepackage{cite}
• \usepackage{caption}
• \usepackage{upquote}
• \usepackage{xcolor}
• \usepackage{xcolor}

We now define the caption as:

\DeclareCaptionFont{white}{\color{white}}
\DeclareCaptionFormat{listing}{\colorbox{gray}{\parbox{\textwidth}{#1#2#3}}}
\captionsetup[lstlisting]{format=listing,labelfont=white,textfont=white}

This makes a gray box for the caption, with white text.

Now define the lstset with the following:

\lstset{
language=Java,
keywordstyle=\bfseries\ttfamily\color[rgb]{0,0,1},
identifierstyle=\ttfamily,
commentstyle=\color[rgb]{0.133,0.545,0.133},
stringstyle=\ttfamily\color[rgb]{0.627,0.126,0.941},
showstringspaces=false,
basicstyle=\small,
numberstyle=\footnotesize,
numbers=left,
stepnumber=1,
numbersep=10pt,
tabsize=2,
breaklines=true,
prebreak = \raisebox{0ex}[0ex][0ex]{\ensuremath{\hookleftarrow}},
breakatwhitespace=false,
aboveskip={1.5\baselineskip},
columns=fixed,
upquote=true,
extendedchars=true,
frame=bottomline,
inputencoding=utf8
}

The language must obviously be changed to the language  you are using, to provide the correct syntax coloring.

the numbers parameter chooses whether to show line numbers or not, the prebreak parameter adds an arrow to indicate that the line is broken.  The upquote parameter ensures that no fancu “‘s are used, so that you can copy the code and still be able to run it.  The other parameters should be self-explanatory, and can be modified as you see fit.

To use this in your document, you can insert code directly with:

\begin{lstlisting}[label=some-samplecode, caption=Example for code straight from the .tex file]

<insert code here>

\end{lstlisting}

or you can insert code from an external file using:

\lstinputlisting[label=samplecode,caption=Example for code from a file]{sourceCode/K53.java}

all of these can now be referenced from other places in the document with the \ref{labelname} command, and will show up in your overview of listings.

Related posts:

1. Making international characters searchable in LaTeX documents

Read his article at http://truben.no/journal/auto-hide-tab-bar-in-mozilla-thunderbird-3/

No related posts.

Wireshark

Wireshark, a really cool network analyzer I’m planning to write more about later. What happened was that at startup you get a long list of error messages, and then no network interfaces could be found.

Luckily, Michael Gracie has scavenged the net for a solution, and found it.

Basically, all you need to do is follow the normal instructions, Dragging the app to the Application folder, the ChmodBPF folder in utilities to the StartupItems alias and the contents of the commandLine folder to /usr/local/bin.

Open a terminal and type:

cd /Library/StartupItems
sudo chown -R root:wheel ChmodBPF

enter your password and hit enter.

Now start up Wireshark, close the list of error messages, hit edit -> preferences -> name resolution, click the edit button next to “SMI (MIB and PIB paths)”, click “new” and type /usr/share/snmp/mibs/ in the text field.  Now click apply / OK, all your way out, exit, and reboot your computer.

After the reboot, everything should be working like a charm.

Related posts:

1. Spoofing your MAC-address in Snow Leopard

OWASP

“Application Security – Awareness.”  Martin works for OWASP, The Open Web Application Security Project, and they have created a lot of cool stuff.  On the workshop we got an introduction to WebScarab and WebGoat, and for learning how a lot of software vulnerabilities work, they are great tools, and fun to play with.

WebScarab is a tool to analyze HTTP and HTTPS communication, and intercepts traffic as a proxy between your browser and the application you are analyzing, and let you look at and modify requests. WebScarab itself is not a training tool, but is supposed to be used for serious application analysis.

WebGoat is a Java web application hosted on a local tomcat server, which contains a lot of flaws and vulnerabilities. The application consists of a series of challenges, in which you use WebScarab to crack your way into the application.

The challenges range from very simple stuff like scanning through source code to look for hardcoded passwords, to more interesting things like Cross Site Scripting and SQL-injection for stealing credit card numbers.

Both tools can be downloaded for free from the OWASP download page, and since it is written in Java, it works on all platforms.

Just be sure to disconnect from the internet before starting WebGoat, since it opens up your computer to all the vulnerabilities it contains while it is running.

Related posts:

1. Citing / displaying source code in LaTeX
2. Installing Wireshark on Mac OS X 10.6 Snow Leopard