<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Jansman.eu / Ealanrian.nl</title>
		<description>A blog/portfolio/random posts gathering thing</description>
		<link>http://ealanrian.github.io</link>
		<atom:link href="http://ealanrian.github.io/feed.xml" rel="self" type="application/rss+xml" />
		
			<item>
				<title>Cmake for Arduino and Clion</title>
				<description>&lt;h1 id=&quot;cmake-for-arduino-and-clion&quot;&gt;Cmake for Arduino and Clion&lt;/h1&gt;

&lt;p&gt;For a project I just started working on I wanted to use Clion with Arduino, since there is no
Arduino plugin or support for Clion yet I had to figure out a way to do this with Cmake. In this
post I&amp;#39;ll try to explain what to do.&lt;/p&gt;

&lt;h2 id=&quot;required-resources&quot;&gt;Required resources&lt;/h2&gt;

&lt;p&gt;Ofcourse the Arduino SDK needs to be installed and a Cmake library is required. For this I found 
Arduino Cmake which can be found at &lt;a href=&quot;https://github.com/queezythegreat/arduino-cmake&quot;&gt;https://github.com/queezythegreat/arduino-cmake&lt;/a&gt;.&lt;/p&gt;

&lt;h2 id=&quot;the-project&quot;&gt;The project&lt;/h2&gt;

&lt;p&gt;So lets get started. First create a project directory, mkdir ~/workspace/ArduinoCmake and move into the directory.
cd ~/workspace/ArduinoCmake. Let&amp;#39;s get the toolchain by going a git clone &lt;a href=&quot;mailto:git@github.com&quot;&gt;git@github.com&lt;/a&gt;:queezythegreat/arduino-cmake.git
This will get the CmakeFiles needed to do arduino related tasks like uploading it to the Arduino.
Next we create a source file: nano main.cpp in this file we put a simple demo:&lt;/p&gt;
&lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-text&quot; data-lang=&quot;text&quot;&gt;#include &amp;lt;HardwareSerial.h&amp;gt;

#include &amp;lt;Arduino.h&amp;gt;

int incomingByte = 0;    // for incoming serial data

void setup() {

    Serial.begin(9600);    // opens serial port, sets data rate to 9600 bps

}

void loop() {
    // send data only when you receive data:

    if (Serial.available() &amp;gt; 0) {

        // read the incoming byte:

        incomingByte = Serial.read();

        // say what you got:

        Serial.print((char)incomingByte);

        }

}
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;This demo will do a serial echo so we can send data to the Arduino which it will echo back.
Next we create the CmakeLists.txt: nano CMakeLists.txt and in this file put the following:
    cmake_minimum_required(VERSION 2.8.4)&lt;/p&gt;
&lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-text&quot; data-lang=&quot;text&quot;&gt;set(CMAKE_TOOLCHAIN_FILE arduino-cmake/cmake/ArduinoToolchain.cmake)

project(projectName)

set(ARDUINO_DEFAULT_BOARD mega)

set(ARDUINO_DEFAULT_PORT /dev/ttyUSB0)

link_directories(arduino-libraries)

generate_arduino_firmware(projectName

    SRCS main.cpp

)
&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;
&lt;p&gt;I will highlight the important lines:
The set(CMAKE_TOOLCHAIN_FILE line tells Cmake where the Arduino toolchain is located. This line must be before the project line.
The next lines, ARDUINO_DEFAULTs, tell the Arduino toolchain which board is used and on which port it is located.
In the generate_arduino_firmware command we tell the toolchain which sourcfiles to use.&lt;/p&gt;

&lt;h2 id=&quot;building-the-project&quot;&gt;Building the project&lt;/h2&gt;

&lt;p&gt;To build the project create a build directory: mkdir build and move into it: cd build. 
Next use cmake to build the project: cmake ../ and this creates make file. To build the project use make and to upload the project use make upload&lt;/p&gt;
</description>
				<pubDate>Sat, 14 Feb 2015 16:30:00 +0000</pubDate>
				<link>http://ealanrian.github.io/2015/02/Cmake-for-Arduino-and-clion</link>
				<guid isPermaLink="true">http://ealanrian.github.io/2015/02/Cmake-for-Arduino-and-clion</guid>
			</item>
		
			<item>
				<title>Honours Weekend</title>
				<description>&lt;h1 id=&quot;the-honours-weekend&quot;&gt;The Honours weekend&lt;/h1&gt;

&lt;p&gt;This weekend the IT students and alumni participated in a hackaton like weekend. A weekend filled with fun, drinks, programming, presentations and more.
In this post, which will be updated during the weekend I&amp;#39;ll try to capture the vibe we have here on the island called Terschelling.&lt;/p&gt;

&lt;p&gt;This post is work in progress and will be updated multiple times this weekend.&lt;/p&gt;

&lt;h1 id=&quot;the-location&quot;&gt;The Location&lt;/h1&gt;

&lt;p&gt;One of our sponsors offered us the location namely Hotel De Walvisvaarder on Terschelling. They kindly offered us the rooms and meals to use.
This beautiful location on the Island of Terschelling. This is one of the island in the Netherlands.&lt;/p&gt;

&lt;h1 id=&quot;the-program&quot;&gt;The program&lt;/h1&gt;

&lt;p&gt;To have some guideline on what would happen during the weekend the guys organizing it created a program. The program started on Friday the 13th at 09:55 with the departure of the boat and during the rest of the day presentations were planned as well as the pitching of some idea&amp;#39;s. Friday night after diner teams formed and the hacking started, more on that later.&lt;/p&gt;

&lt;p&gt;On Saturday one more presentation interrupted the work-flow, even though this presentation was on the subject of work-flows namely agile working. The rest of the day was filled with programming, hacking, games and other stuf which happens when you put 16 programmers in one room.&lt;/p&gt;

&lt;h1 id=&quot;the-projects&quot;&gt;The Projects&lt;/h1&gt;
</description>
				<pubDate>Sat, 14 Feb 2015 00:00:00 +0000</pubDate>
				<link>http://ealanrian.github.io/2015/02/Honours-Weekend</link>
				<guid isPermaLink="true">http://ealanrian.github.io/2015/02/Honours-Weekend</guid>
			</item>
		
			<item>
				<title>This is the first post using Jekyll and github pages.</title>
				<description>&lt;h2 id=&quot;this-is-the-first-post-using-jekyll-and-github-pages.&quot;&gt;This is the first post using Jekyll and github pages.&lt;/h2&gt;

&lt;p&gt;As of now the site has been migrated to github pages. The main language will be English, though some posts might be written in Dutch due to the subject or if they are older&lt;/p&gt;

&lt;h3 id=&quot;migration-and-updates&quot;&gt;Migration and updates&lt;/h3&gt;

&lt;p&gt;In the coming days and weeks the old posts will repear here and the site will be updated.&lt;/p&gt;
</description>
				<pubDate>Sun, 25 Jan 2015 00:00:00 +0000</pubDate>
				<link>http://ealanrian.github.io/2015/01/first-jekyll-post</link>
				<guid isPermaLink="true">http://ealanrian.github.io/2015/01/first-jekyll-post</guid>
			</item>
		
			<item>
				<title>Google summer of code [Dutch]</title>
				<description>&lt;h4&gt;Google summer of code, wat is het&lt;/h4&gt;

&lt;p&gt;Google Summer of Code (GSOC) is een project van Google om studenten te betrekken bij opensource projecten. Door studenten te betalen om aan uitdagende projecten te werken met mentoren uit de projecten word er geprobeerd om de studenten in de community&amp;#39;s te krijgen.&lt;/p&gt;

&lt;!--more--&gt;

&lt;h5&gt;Hoe werkt het?&lt;/h5&gt;

&lt;p&gt;Tijdens GSOC werk je voor een periode aan een project, in mijn geval Apache Celix event admin, en word je begeleid door een mentor vanuit de organisatie. Om te mogen deelnemen aan GSOC moet je je inschrijven, deze inschrijving bestaat uit een project idee en een motivatie waarom je mee wilt doen. Er zijn verschillende organisaties die van te voren al vast staande projecten aanleveren waarop je dus kan solliciteren of er is een idee waarop je een plan schrijft hoe je het wilt uitvoeren.&lt;/p&gt;

&lt;p&gt;Je inschrijving word beoordeeld door de organisatie waar je voor gaat werken en ze zullen eventueel nog vragen stellen om opheldering te krijgen. Als alles goed gaat word je geaccepteerd en mag je dus mee doen aan GSOC.
&lt;h5&gt;Tijd&lt;/h5&gt;
Officieel duurt GSOC 3 maand, van mei tot augustus, heel toevallig lopen die gelijk met de Amerikaanse zomervakantie. In die 3 maand is het de bedoeling dat je programmeert en actief deel bent van de community. Ik kom verder op nog terug op hoe ik de tijd heb ingedeeld.
&lt;h5&gt;Controle&lt;/h5&gt;
Google heeft tijdens GSOC twee controle momenten, ongeveer halverwege en aan het eind. De halfweg controle bestaat uit een enquête die jij en je mentor invullen en wanneer dit positief is mag je door met het project. De eind controle bestaat weer uit een vragen lijst en er word verwacht dat je code samples upload. Dit is om te controleren of je ook daadwerkelijk hebt geprogrammeerd.
&lt;h5&gt;De beloning&lt;/h5&gt;
Google betaald dus studenten voor het werk wat er aan de projecten word gedaan. In totaal was het dit jaar $5000 voor de student en $500 voor de mentor. Dat was dit jaar een totaal bedrag van ongeveer $5000000 wat betaald werd. Hierbij komen dan nog de goodies en de overhead kosten voor controle en dergelijke bij. Google gooit dus redelijk met geld.
&lt;h6&gt;Het geld&lt;/h6&gt;
Als je geaccepteerd word voor GSOC krijg je al direct een deel van het geld. Je krijgt namelijk een prepaid credit card toegestuurd, met het Google logo er op, waarop $500 staat. Je hebt dus nog niks gedaan en al $500 dollar in de pocket. Als je de halfweg evaluatie door komt krijg je de tweede betaling, $2250 word op de creditcard bij geschreven. En als laatste krijg je bij het succesvol afronden van de eind evaluatie nogmaals $2250 dollar.
&lt;h6&gt;De echte beloning&lt;/h6&gt;
Die $5000 is natuurlijk allemaal leuk en aardig maar daar doe je het niet voor. Het zijn de goodies waar je voor werkt. Samen met de creditcard krijg je aan het begin een Pen, een notebook en een sticker met de logo&amp;#39;s van het jaar er op. Als je de eind evaluatie haalt krijg je echter het meest belangrijke object, het T-Shirt, Oja je krijgt ook nog een certificaat van deelname leuk voor naast al je andere certificaten &lt;img alt=&quot;:P&quot; src=&quot;http://tweakimg.net/g/s/puh2.gif&quot; width=&quot;15&quot; height=&quot;15&quot; /&gt;.
&lt;h4&gt;Apache Celix en de event admin&lt;/h4&gt;
Ik heb zelf mee gedaan aan GSOC op een project waar ik tijdens mijn stage mee te maken heb gekregen, Apache Celix. Apache Celix is een project wat als doel heeft een OSGi implementatie te maken in C. Tijdens mijn stage heb ik aan de Remote Service Admin gewerkt en mijn stage begeleider leek het wel leuk om als GSOC project de event admin te bouwen.
&lt;h5&gt;De aanmelding&lt;/h5&gt;
Voor mij was de aanmelding relatief simpel, ik heb namelijk zelf mee geschreven aan de opdracht omschrijving en ik werd beoordeeld door mijn stage begeleider. Ik was dus ook vrij snel klaar met de aanmelding en ik heb ook maar 1 aanmelding geschreven. Ik kan helaas mijn aanmelding niet meer bekijken dus deze komt niet in het topic terug.
&lt;h5&gt;De tijdsindeling&lt;/h5&gt;
Zoals al gezegd is het project afgestemd op de Amerikaanse zomer vakantie. Dit was best lastig aangezien ik nog moest stage lopen tot 1 juli. Omdat ik dus geen tijd zou hebben om al in mei te beginnen heb ik in mijn aanmelding vermeld dat ik van 1 juli tot en met 31 augustus zou gaan programmeren en daar tussen 1 week vakantie zou hebben. In totaal heb ik dus maar 8 weken gewerkt aan GSOC. Dit was echter geen probleem en zelfs redelijk normaal aangezien er ook mensen zijn die wel mee doen maar geen vakantie hebben, de mensen op het zuidelijk halfrond.
&lt;h5&gt;Het project&lt;/h5&gt;
Dus 8 weken werken aan een project in C waar je nog niet heel veel ervaring in hebt. Leuke uitdaging. Ik heb de eerste 3 weken verpruts, er is echt niks fatsoenlijks uit gekomen in die weken en ik heb ook alles weg gegooid. Mijn mentor was namelijk een klein detail vergeten te melden. Hoe de spec, geschreven voor Java, geport kon worden naar C. Nadat dit eenmaal duidelijk was ging het als een speer en het resultaat is te vinden op bitbucket [1].
&lt;h4&gt;Wat heeft Google er aan&lt;/h4&gt;
Google smijt tijdens GSOC behoorlijk met geld. Er word $500 dollar aan elke student gegeven voor er ook maar een letter code staat. Hier moet dus iets achter zitten en dat klopt. Google gebruikt GSOC om potentiele recruits te vinden. Ook maakt Google gebruik van de projecten of een deel van de projecten die meedoen aan GSOC.
&lt;h4&gt;Volgend jaar&lt;/h4&gt;
Volgend jaar is de tiende editie van GSOC. Er zullen wat dingen veranderen, de beloning word met $500 verhoogd, er worden meer studenten toegelaten en meer projecten toegelaten. Of ik zelf mee ga doen weet ik nog niet zeker. Misschien nogmaals als student maar misschien ook wel als mentor, er van uit gaand dat ik voor die tijd commitor kan worden bij Celix.
&lt;h4&gt;Dit topic&lt;/h4&gt;
Het lijkt me leuk om dit topic te gebruiken om ervaringen uit te wisselen, projecten op te zetten en om te praten over GSOC. Ook discussiëren over het ethische van een dergelijk programma is interessant.&lt;/p&gt;

&lt;p&gt;[1]: &lt;a title=&quot;https://bitbucket.org/Ealanrian/gsoc-celix-eventadmin&quot; href=&quot;https://bitbucket.org/Ealanrian/gsoc-celix-eventadmin&quot; target=&quot;_blank&quot; rel=&quot;external nofollow&quot;&gt;&lt;a href=&quot;https://bitbucket.org/Ealanrian/gsoc-celix-eventadmin&quot;&gt;https://bitbucket.org/Ealanrian/gsoc-celix-eventadmin&lt;/a&gt;&lt;/a&gt;&lt;/p&gt;
</description>
				<pubDate>Sun, 27 Oct 2013 19:21:00 +0000</pubDate>
				<link>http://ealanrian.github.io/2013/10/google-summer-of-code</link>
				<guid isPermaLink="true">http://ealanrian.github.io/2013/10/google-summer-of-code</guid>
			</item>
		
			<item>
				<title>High performance message queues in clustered environments</title>
				<description>&lt;p&gt;To complete my bachelor course in Computer science, I have to complete an internship. Since I wanted a challenging project and a project in an inspiring environment I ended up at a High tech company, which was surprisingly close to my home. Sadly the public transport system isn&amp;#39;t very good in this part of the Netherlands so I bought my first car, but that&amp;#39;s for another post. The internship assignment consisted of research into message systems and a part implementation. So far I have completed most of the research into message systems. In this post I&amp;#39;ll talk about the message queue systems researched in this project and the different ways of working with messages they have.&lt;/p&gt;

&lt;p&gt;First&lt;/p&gt;
</description>
				<pubDate>Sun, 28 Apr 2013 19:31:00 +0000</pubDate>
				<link>http://ealanrian.github.io/2013/04/</link>
				<guid isPermaLink="true">http://ealanrian.github.io/2013/04/</guid>
			</item>
		
			<item>
				<title>Kraków 2012 - DIMA</title>
				<description>&lt;p&gt;So it&amp;#39;s time to talk about my trip to Kraków. For those who don&amp;#39;t want to read the whole story: it was awesome.&lt;/p&gt;
</description>
				<pubDate>Sat, 14 Apr 2012 16:43:00 +0000</pubDate>
				<link>http://ealanrian.github.io/2012/04/</link>
				<guid isPermaLink="true">http://ealanrian.github.io/2012/04/</guid>
			</item>
		
			<item>
				<title>Sending signed e-mails using php</title>
				<description>&lt;p&gt;Last term we had to build a &amp;quot;secure&amp;quot; website. This included using SSL/https and signed e-mails.
Since we were going to build a website and I&amp;#39;m an experienced PHP web developer we decided to go to work with PHP. This gave us a small problem, how do we sign e-mail messages using PHP. Using multiple how-to’s and tutorials I was able to figure it out. Helping others being able to find it quicker I’m writing yet another tutorial hoping to help people to get it working in an hour instead of a few days. In this tutorial I’m not going into details about creating certificates and keys to use, I’ll only talk about how to sign emails using PHP. I will include some quirks you could encounter when using Xampp or some other form of apache on windows.&lt;/p&gt;

&lt;!--more--&gt;

&lt;p&gt;There are a few things important to know when signing emails and doing this on windows. Windows does not like relative paths, use absolute paths. The headers and the content of the email send should not be changed after signing. If you do the verification, the thing it’s all about, will fail. You should know a thing or two about PHP before using this tutorial, it’s not hard but if you don’t know PHP it is. Having said that lets get to work.&lt;/p&gt;

&lt;p&gt;The first part is creating files to read from and write to, why need them will become clear later. In the folder you are working create two files, msg.txt and signed.txt and make sure they are writeable by PHP, in Windows create them as the same user running apache, on Linux chown them to apache or chmod them to 777. After that create a file called mail.php or something. This file will contain the class.&lt;/p&gt;

&lt;p&gt;In the file you should create a class and a method, I have called them mail and sendSignedMail. The method has $toAdr, $subject, $message as parameters, these will be used later. First create a few variables in the method.
&lt;ol&gt;
    &lt;li&gt;$prfile, this will be the private key pointer. I have placed it in the same folder as the file so the path is $prfile = &amp;#39;file://&amp;#39;.realpath(dirname(&lt;strong&gt;FILE&lt;/strong&gt;)).&amp;#39;/key.pem&amp;#39;;&lt;/li&gt;
    &lt;li&gt;$pufile, this will be the public key pointer, $pufile =  &lt;a href=&quot;file:///\\&#39;.realpath(dirname(__FILE__)).&#39;\cert.pem&quot;&gt;file://&amp;#39;.realpath(dirname(&lt;strong&gt;FILE&lt;/strong&gt;)).&amp;#39;/cert.pem&lt;/a&gt;&amp;#39;;&lt;/li&gt;
    &lt;li&gt;$msg, this is a pointer to the previous create msg.txt, $msg = realpath(dirname(&lt;strong&gt;FILE&lt;/strong&gt;)).&amp;quot;/msg.txt&amp;quot;;&lt;/li&gt;
    &lt;li&gt;$sign, this is a pointer to sign.txt, $sign = realpath(dirname(&lt;strong&gt;FILE&lt;/strong&gt;)).&amp;quot;/signed.txt&amp;quot;;&lt;/li&gt;
&lt;/ol&gt;
&amp;nbsp;&lt;/p&gt;

&lt;p&gt;Having those variables is just to prevent typing those paths all the time. Now let’s start with some code.
&lt;pre lang=&quot;php&quot;&gt;$fp = fopen($msg,&amp;#39;w&amp;#39;);&lt;/p&gt;

&lt;p&gt;fwrite($fp,&amp;#39;Content-Type: text/html;charset=&amp;quot;us-ascii&amp;quot;Content-Transfer-Encoding: 7bit&lt;/p&gt;

&lt;p&gt;&amp;#39;.$message);&lt;/p&gt;

&lt;p&gt;fclose($fp);&lt;/pre&gt;
Do not copy this code but type it since it won’t work because of whitespace problems.  First I open the msg.txt and create a filepointer. After that I write the message and a content header. This header is to tell mail clients how to read this message. After that I close the file again since it is not needed to keep open.
&lt;pre lang=&quot;php&quot;&gt;openssl_pkcs7_sign($msg, $sign,$pufile, array($prfile,&amp;#39;onzebank&amp;#39;),array(&amp;quot;To&amp;quot;=&amp;gt;$toAdr,&amp;#39;subject&amp;#39;=&amp;gt;$subject));&lt;/pre&gt;
Using openssl_pkcs7_sign will sign the message. What it does is take the content from the msg.txt file create a hash from it using the private key, the public key and also including the subject and the destination address.&lt;/p&gt;

&lt;p&gt;Now you have a signed message, but it is on your server and not in the destination email box. Let’s make that last part work. I could open signed.txt get the content and mail that to the destination. That will get the message to the destination but not usable. Since the signature won’t be correct. To do it correctly we first have to get the content from signed.txt with:
&lt;pre lang=&quot;php&quot;&gt;$data = file_get_contents($sign);&lt;/pre&gt;
Now we have all the data we now have to separate the message form the headers which are also in the data variable. This is also the part where a lot can go wrong because of white spacing.
&lt;pre lang=&quot;php&quot;&gt;$parts = explode(‘&lt;/p&gt;

&lt;p&gt;’,$data);&lt;/pre&gt;
This will explode the data on triple new line sequence, if you get verification errors this is the part to look for trouble.&lt;/p&gt;

&lt;p&gt;Now we have the headers and the message, $parts[0] and $parts[1] respectively, now we can send the email.
&lt;pre lang=&quot;php&quot;&gt;Mail($toAdr,’’,$parts[1],$parts[0]);&lt;/pre&gt;
I am not setting the subject using the mail function since that would mess up the headers and thus the signature. After this I clean up the files to prevent data to be stored or lost or messing around with the next mail.
&lt;pre lang=&quot;php&quot;&gt;$fp = fopen($msg,&amp;#39;w&amp;#39;);
fwrite($fp,&amp;#39; &amp;#39;);
fclose($fp);
$fp = fopen($sign,&amp;#39;w&amp;#39;);
fwrite($fp,&amp;#39;&amp;#39;);|
fclose($fp);&lt;/pre&gt;
Just to be nice I also added the file containing the class: &lt;a href=&quot;http://www.jansman.eu/wp-content/uploads/2012/03/mail.php_.txt&quot; target=&quot;_blank&quot;&gt;mail.php&lt;/a&gt;&lt;/p&gt;
</description>
				<pubDate>Sun, 11 Mar 2012 14:47:00 +0000</pubDate>
				<link>http://ealanrian.github.io/2012/03/sending-signed-e-mails-using-php</link>
				<guid isPermaLink="true">http://ealanrian.github.io/2012/03/sending-signed-e-mails-using-php</guid>
			</item>
		
			<item>
				<title>The cave project</title>
				<description>&lt;p&gt;So I have been talking about the Cave project a while ago. And I promised to give more information about it, in this post I will tell a little bit more about the project and the outcome.&lt;/p&gt;

&lt;!--more--&gt;

&lt;p&gt;Let me start with saying that we didn&amp;#39;t get to the point where we wanted to be. In the beginning of the project the plans where big and expectations high. The project was about creating a room for dementing elders to relive and re-experience past events and memories to help them become calmer and hopefully help to slow down the loss of intelectual capacity. The Cave, computer aided virtual enviroment, was supposed to work with video, audio, light, sent and more to help them relive those events.&lt;/p&gt;

&lt;p&gt;Since I already told you that we didn&amp;#39;t get to that point what did we do? Well we created a base for the next project group to work with. We searched for the hardware and software and figured out how to make it work. We have written plans and recommendations and build a skelleton for the next group to work with. We all feel sad because we didn&amp;#39;t get to work with all the hardware and cool stuff, but this is how it works in real life and I&amp;#39;m proud of what we did.&lt;/p&gt;

&lt;p&gt;So why did we not get to the point where we wanted to be? Well first of all communication was a problem. None of us had ever worked for a real contracter before and we didn&amp;#39;t know how to get information when we needed that. We have been waiting for nearly 5 weeks before we figured out that we should just go instead of wait for info and do nothing. This gave us the freedom to do what we do best, improvise. This resulted in us creating something which is to form a base for the Cave project. We sure hope it&amp;#39;s going to get somewhere soon.&lt;/p&gt;
</description>
				<pubDate>Mon, 13 Feb 2012 19:46:00 +0000</pubDate>
				<link>http://ealanrian.github.io/2012/02/the-cave-project</link>
				<guid isPermaLink="true">http://ealanrian.github.io/2012/02/the-cave-project</guid>
			</item>
		
			<item>
				<title>Hanze mail in Windows Live mail 2011</title>
				<description>&lt;p&gt;After posting the how to for &lt;a title=&quot;Hanze mail in mail client&quot; href=&quot;http://www.jansman.eu/article/hanze-mail-in-mail-client&quot; target=&quot;_blank&quot;&gt;getting hanze mail in a mail client&lt;/a&gt; I recieved a lot of comments on how to do this in windows live mail. So here is the how to to get Hanze mail in windows live mail 2011.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;go to the accounts window, options button left side top of the window-&amp;gt; options-&amp;gt; email accounts&lt;/li&gt;
&lt;li&gt;press the add button&lt;/li&gt;
&lt;li&gt;Select E-mail account.&lt;/li&gt;
&lt;li&gt; fill in your hanze mail adres, i.e. &lt;a href=&quot;mailto:somename.somelastname@st.hanze.nl&quot;&gt;somename.somelastname@st.hanze.nl&lt;/a&gt;, your password, your real name and select the manual server configuration box.&lt;/li&gt;
&lt;li&gt;now you will see the serverconfiguration screen. This screen looks complicated but I&amp;#39;ll try to talk you through it.
&lt;ol&gt;
&lt;li&gt;set the servertype select box to IMAP&lt;/li&gt;
&lt;li&gt;bellow the servertype selectbox fill in webmail.hanze.nl as server adress&lt;/li&gt;
&lt;li&gt;set port number to 993&lt;/li&gt;
&lt;li&gt;Select the secure connection(SSL) select box&lt;/li&gt;
&lt;li&gt;Select password verification in the verification select box&lt;/li&gt;
&lt;li&gt;fill in your username which is not the same as your email adress. For students this is the student number and for teachers the 4 letter code.&lt;/li&gt;
&lt;li&gt;on the righthand side of the screen is the part for outgoing mail. Set this to the out going mail server of your internet provider for example ziggo uses smtp.ziggo.nl on port 2&lt;/li&gt;
&lt;/ol&gt;
press next and there you have it.&lt;/li&gt;
&lt;/ol&gt;
</description>
				<pubDate>Fri, 13 Jan 2012 18:59:00 +0000</pubDate>
				<link>http://ealanrian.github.io/2012/01/hanze-mail-in-windows-live-mail-2011</link>
				<guid isPermaLink="true">http://ealanrian.github.io/2012/01/hanze-mail-in-windows-live-mail-2011</guid>
			</item>
		
			<item>
				<title>Folding bike</title>
				<description>&lt;p&gt;As some people might know I ride a folding bike. This is because it&amp;#39;s free to take with you in the train and it&amp;#39;s a lot quicker as riding the bus from the station to college.
My first folding bike was/is a Ventos folding bike as shown below. It&amp;#39;s a prety good bike but after me abusing it for nearly 2 years now it starts to twist and bend.
Already had a broken securing pin and the chain tends to run of a lot.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.jansman.eu/wp-content/uploads/2012/01/vouwfiets-alu-3-speed.jpg&quot; target=&quot;_blank&quot;&gt;&lt;img class=&quot;alignnone size-thumbnail wp-image-106&quot; title=&quot;ventos&quot; src=&quot;http://www.jansman.eu/wp-content/uploads/2012/01/vouwfiets-alu-3-speed-150x150.jpg&quot; alt=&quot;&quot; width=&quot;150&quot; height=&quot;150&quot; /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The replacement:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;http://www.jansman.eu/wp-content/uploads/2012/01/beixo-compactLG.jpg&quot; target=&quot;_blank&quot;&gt;&lt;img class=&quot;alignnone size-thumbnail wp-image-107&quot; title=&quot;beixo-compactLG&quot; src=&quot;http://www.jansman.eu/wp-content/uploads/2012/01/beixo-compactLG-150x150.jpg&quot; alt=&quot;&quot; width=&quot;150&quot; height=&quot;150&quot; /&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;It&amp;#39;s a &lt;a href=&quot;http://www.beixo.com/nl/compact&quot; target=&quot;_blank&quot;&gt;Beixo compact &lt;/a&gt; a folding bike without a chain. It uses a cardan shaft to transfer the energy from the pedals to the wheel.
This should be a maintanance free system and also it is no longer possible to have a lose chain.
I&amp;#39;ll probably get the Beixo this week and hope to review it next week.&lt;/p&gt;
</description>
				<pubDate>Mon, 09 Jan 2012 19:43:00 +0000</pubDate>
				<link>http://ealanrian.github.io/2012/01/folding-bike</link>
				<guid isPermaLink="true">http://ealanrian.github.io/2012/01/folding-bike</guid>
			</item>
		
	</channel>
</rss>
