All seats have been taken. Please write a comment to be put on a waiting list, there are always a number of cancellations, so there’s still a chance.
Douglas and I have talked about him speaking at Geek Meet a few times when we’re ran into each other at different conferences in the world, and we’ve said that if he’s nearby Sweden, we just make it happen. Now is that time!
Being able to easily specify what to post with XMLHttpRequest is quite a powerful way of sending things to the server, using key/value pairs and FormData. However, many seem to have missed this gem, so I thought I’d outline it here.
One thing which has been very important when it comes to creating special end user experiences have been the ability to show something fullscreen, effectively hiding all the other content etc.
First idea was to publish these posts on a regular schedule, but I’ve realized now it will be when I have enough good links (and time :-). Tons of links now, so, here goes – another issue of Robert’s read!
Forms on the web. They are literally everywhere, and there seem to really be all kind of flavors for them. From day one they have been a great mean for users to input data and information and interact with various services. And what comes with that is every implementation under the sun to offer validation for them, custom display and functionality if they aren’t native in that specific web browser, and much much more. Therefore, during the development phase of HTML5, one of the important things that have been looked into is making forms on the web evolve into what both end users and developers need to make things easier. Why would every web developer have to invent the wheel again or include tons of JavaScript code just to make something very basic like a datepicker work?
When the AJAX wave came in 2005 when Jesse James Garrett coined the term and then everyone wanted it, one of the major shortcomings was that dynamic updates of only portions of a web page lead to inconsistent history handling and back/forward navigation button problems in web browsers and poor end user experiences. Enter the HTML5 History API.
People are creating amazing things with HTML5 canvas, especially combined with other HTML5 features. I thought I’d touch on a handy method that some people don’t seem to know about: canvas clip.
HTML5 is here to save us all: it has the cool functions, eye-dazzling features and APIs to go around. I get to see a lot of great things developed with HTML5, but I’d like to issue a word of caution as well.
With HTML5 video and the current support in web browsers, we need to cater to different codecs, and fallbacks for web browsers with no native video support. This is where Video JS steps in.
To me, something about HTML5 that makes it quite interesting is all the new support for file interaction. I’ve written about the File API and reading file information before, and I thought I’d expand on that and add uploads and progress bars.
With a blog it’s great getting comments, but as any blogger need to realize, there are other channels that people like to express their reactions in to – especially Twitter.
I continually talk about HTML5 and how progressive enhancement is a simple approach to make any new behavior possible in web browsers that haven’t implemented it yet. I thought I’d show you a simple example how to do this with the new placeholder attribute for input elements.
When writing JavaScripts for a web page, since the beginning of time, web developers have had the need to store extra data for HTML elements. I remember reading about custom data attributes in HTML5 some time ago, and recently Remy reminded me about them – they are here to save us!
A constant drag when developing web sites have been when the end user wants to upload files to it. Luckily, though, those problems are to come to an end due to the File API.
When performing advanced load-heavy operations in a web browser, both the web page it is run in as well as the web browser UI becomes unresponsive till it’s finished. However, there’s a way to address that with HTML5 Web Workers.
Ever had the need to communicate between windows or the current window and an inner iframe? Across domains as well? I bet you have, but now we have a nice option for doing that!
More and more services around us focus on where we physically are located at the moment, and how we can be assisted in the best fashion depending on that. Today I’d like to introduce the geolocation possibilities we developers have, and also play around a little with Google maps.
Week before last, I had the pleasure of attending and speaking at two conferences. With even more conferences in the pipe, last week was pretty intense, work-wise, to cover up for that, but now I thought I’d take the time to talk about them, starting in this post with the Øredev 2009 conference.
It seems like everyone is talking about HTML5 now, but the discussion is spread out and seldom gives the background, explanation what HTML5 really is and if/when it’s usable.
Late last night I came home from the fantastic event that was Mozilla Camp Europe Prague, 3-4 October 2009, and I thought I’d tell you how my Prague visit was, what I thought of the event and my thinking about the sessions.
When a developer writes code, it is usually for the challenge, the obstacles to beat and the rush of solving a problem. But also, when your code becomes popular is quite a kick as well.
When I released Firefinder back in May, I had some ideas with what more I wanted to do with it. Now I can happily say that I have implemented those ideas!
Firefox 3.5 was released yesterday, and it has already reached 5 and a half million of downloads (at the time of writing). Therefore, I thought I’d answer some common questions, especially from a web developer perspective about the new version and which web developer extensions which will work with it.
I’ve had a few versions of my PictureSlides to create JavaScript slideshows, but now it has been completely rewritten and jQuery-optimized with some new control and features.
With the impending release of Firefox 3.5, I thought I’d cover the new things in JavaScript 1.8.1 – part of that is the very exciting support for native JSON, and you know what? They’re not the only ones supporting it!
Saving state or values have never been easy on the web, especially on the client-side, and using cookies have been far from ideal. Enter DOM/Web Storage!
I meet lots of developers working with different technologies and tools, and one thing that interests me is which, if any, JavaScript library they use.