10 Best Online XML Sitemap Generators Websites And Tools

10 Best Online XML Sitemap Generators Websites And Tools

Sitemap is a most important part of any website or blog. A Sitemap is an XML file that lists URLs for a site along with additional metadata about each URL when it was last updated, how often it usually changes, and how important it is, relative to other URLs in the site, so that search engines can more intelligently crawl the site.

Sitemap makes any website more SEO friendly and helps to index on…

View On WordPress

Load Movie-Metadata from IMDB with Processing and OMDB API

I think it was around autumn 2014 that I decided to compile a list of all movies I have seen. At least the ones I could still remember and roughly recall the plot. Compiling the list to a temporary state was lot of work but once I had that done I just kept on adding always after I watched a new movie.

The output of my adding procedure:

added Only God Forgives, 2013 to the list
added Jobs, 2013 to the list
added Silver Linings Playbook, 2012 to the list
added Immortals, 2011 to the list
added The Interview, 2014 to the list
5 new Movies were added to the list. 0 were duplicates.
In total the list features now 1234 titles.

Since I want to use the data for some kind of info-visualization a plain list of titles isn’t enough. I need meta-data. Runtimes, ratings,years of publication, directors etc. OMDB API does a pretty got job at supplying the data. It returns XML or JSON and I am going to show you the very basic usage with processing and XML as response Data.


// The XML Object that will store our moviedata
XML myMovie;
// Pulp Fictions IMDB id 
String myMovieID = "tt0110912";
// The PImage that will hold the poster
PImage poster;
String title, year, runtime, director, actors, rating;

void setup() {
	// load the Data with the passed id see the method below
	// get all the Data from the myMovie XML Object
	poster = loadImage(myMovie.getString("poster"));
	title = myMovie.getString("title"); 
	year = myMovie.getString("year"); 
	runtime = myMovie.getString("runtime"); 
	director = myMovie.getString("director");  
	actors = myMovie.getString("actors");  
	rating = myMovie.getString("imdbRating");
	// set the size of the processing window to the postersize + 100px for a description
	size(poster.width, poster.height+100);

void draw() {
	// draw the poster to the screen
	image(poster, 0, 0, poster.width, poster.height);
	// create a string with all the loaded data
	String movieDescription = title+", "+year+"\n"+
			"Directed by: "+director+"\n"+
			"IMDB Rating: "+rating+"\n"+
			"Starring Actors: "+actors;
	// print the data below the poster with a padding of 10px
	text(movieDescription, 10, poster.height+10, width - 20, 80);

// here we load the data
void loadMovieData(String id){
	// here we use the omdb api. inserting our id and setting the response to XML
	XML responseData = loadXML("http://www.omdbapi.com/?i="+id+"&r=XML");
	// here we check if there is data available with the passed id 
	if (responseData.getString("response").equals("True")) {
		// if there is data in the response we load it into our myMovie Object
		myMovie = responseData.getChild("movie");
	}else {
		// if there is no data available (maybe a wrong id or no network?) we quit the sketch
		println("no Data Available");

Result of the code and a style-study for my info-visualization:

Physics and the Future of Books
It’s hard to see the future of the book when our current model is centuries old. To look ahead, we have to look within—at the materials and forms now at our disposal. A review of some key digital media properties suggests how we might design books for the kinds of readers we are all becoming.
6 Tips From Pragmatic Programming You Can Use Right Now

Lately, I’ve been reading the classic, The Pragmatic Programmer by Andrew Hunt and David Thomas. I think it’s one of the most recommended books I’ve come across, and after a few chapters, I could see why. 

I have mixed feelings about self-help books and particular educational books that don’t necessarily teach you anything technical. Sometimes, I feel like half of what they’ve said, you already know. Then the other half, you won’t really learn until you experience them. But this book is different. 

I feel like The Pragmatic Programmer teaches you everything you never learned in the classroom but should have. 

Some are tips I’m sure I’ll need when I start working, but here’s a list of the interesting tips I can use today:

1. DRY. Don’t Repeat Yourself.

Most of the book seems to come back to this point. In my head, I say, “Be Lazy”. Don’t code anything that’s already been done before. If there’s a shortcut, take it. It goes against every life lesson I’ve ever learned, but for programming, it works.

2. Program close to the problem domain.

They teach us to name our variables well in our first programming class. Don’t use x, y, and z, if they can be bags, balls, or boxes. It’s an important basic lesson, one that I’ve found seems to get harder and harder as a program’s complexity increases. 

3. Keep data in plain text.

Somehow, I we never discussed plain text in any of my classes. I only encountered it at work (and this book). Plain text, like XML files, are easier to read. It will make the work simpler for other programmers to read your data, and allows data to be read and manipulated by most languages and tools.

4. Learn more than just IDEs.

I have barely ever used a shell. I primarily use IDEs like Netbeans or Visual Studio. The book talks a lot about the benefits of learning to program outside these tools. Shells allow you to create macros to help do different tasks. 

5. When in trouble, rubber duck! 

Forums, comments, and the internet in general (at least, the technical side of it), keep on talking about a rubber duck, and I never got it. Now I do. 

When you encounter a problem while programming, explain it to someone else. Explain it step by step, as if you were explaining to a rubber duck. 

6. Learn a text manipulation language

Here’s another tip I have yet to encounter. It mentions a number of things text manipulation languages would be beneficial for, including working with databases or creating documentation. It’s something I’ll have to look into.

The book is really interesting. I’m glad I got a hold of it. Watch out for my post for the second part of the book and more in-depth posts on some of these topics here.

I’m definitely going to try coding in a shell (and maybe buy a rubber duck) after this book!

50 Fifty Brand website launching soon!
#advertise #AJAX #branding #coding #developer #dream #dreamweaver #DOM #entrepreneur #inspiration #javascript #JSON #marketing #responsive #responsivewebsites #startups #sublime #web #webdesign #webdeveloper #webdevelopment #wordpress #php #plugins #jQuery #HTML5 #CSS #CSS3 #bootstrap #XML