It’s only for FM2009 although may well work with FM2010 (if it’s the same formula). Please let me know if you know the FM2010 coach formula and I’ll make an FM2010 version aswell.

The link is the same as before, please check it out here.

FM2009 Coach Calculator.

Please let me know your thoughts, I may add more functionality too it in the future but the core functionality is there. Please note this is only a beta, so please report and bugs, inconveniences or improvements you note in the comments here.

Cheers.

Enjoy:

FM2009 Coach Calculator.

p.s. If I find time next year I will be updating this for FM2010, and that will most likely be found at the same address, but in ‘fm2010′ rather than ‘fm2009′.

Edit [16/09/09]:

Now includes hover functionality that indicates the formula involved for each skill set.

Have a nice year, probably catch up soon.

Fred.

My favourites include:

Wonderful stuff I’m sure you’ll agree.

Here’s a brief run-down of what I managed to catch from the 80 minute video:

• Email reinvented – Instant messaging and email combine
• Live updates when people post replies to your messages
• Live character by character updates when you’re both online
• Private messaging
• Playback – Skip through a conversation stage by stage.
• Simultaneous editting
• Collaboration – Edit each others posts
• Extract elements of a Wave to a fresh Wave (all images or all text etc.)
• Use tags to organise your Wave catalogue
• Live spell checker
• Blog Interaction – Embed Wave into your blog for live interaction
• Inline Google Search
• Embed Video / Maps
• Use Twave to Tweet through Wave
• Create your own add-ons
• Live Language Translation – Rosey
• Bugee – A debug log
• Polls native to Google Wave – Polly the Pollster
• Play games in Wave
• It’s all opensource. You can make your own version of Wave and compete against Google.

Check it out, we could all be using this in a few years time.

On reflection I didn’t mean it at all, but it brings me to a good point. Anyone can see the venture they could have done, the one that has already materialised through someone elses actions, but we have as many opportunities if not more than each of the previous generations, right now.

Yeah, it’s not easy to get into that mindset and do something that hasn’t been done before, or do it better, but that’s the fantastic challenge we face. Every new day presents us with millions of possibilities, we just need to realise them.

Just remember. Anything you think of, 99.999% of the time will have gone through someone elses mind. Don’t let this put you off however. It may have already been done, you can do it better. Be optimistically realistic. Follow your dream.

The figures may be a little bit off depending on your browser

Working example:

As you may know I’ve been working on a Prime Number Calculator to get to grips with JavaScript. As you can imagine it has been full of highs and lows, dead ends and overcoming them.

Through making this I’ve learnt a few bits and bobs, and here’s another. Ever wondered..

How can I make an input box expand when someone types in it?

Well here I’ll show you just how.

First, set up an external .js file, like so.

Now, lets get down to the JS. Set up the function as per normal. However, we may want to use this function more than once so for versatilities sake we will parse a parameter in.

Now, let’s get into the real code.

This is the preparation first half of the code. First, we set the variable ‘d’ to hold the string document.getElementById(id). Notice the (id) in brackets? That’s one of the places our parameter will fill when we parse it in.

Then we set the variable ‘e’ to hold the length of the element we parsed in. What this means is that the variable ‘e’ will be set to 4, if there’s 4 characters in the input box. 5 if 5, and so on.

This is saying if the characters are less than 4, then set it to 60px. This should be the same size as your default width, before any characters are typed.

However, if the characters become 4 or larger then set it to a figure that will vary depending on how many characters are entered. If you’re not familiar with em’s then either click the link to read more or use the slightly less flexible pixels.

Feel free to edit the values, these worked for me but I’m sure with a tweak you’ll get exactly what you’re looking for.

Now, just call the function with onkeypress or onkeydown and it should have the desired effect.

Be careful when copying and pasting

And there you have it! Here’s the final code CSS code:

Tested in Firefox3, Chrome2 & Safari3

I hope not

Tables for tabular data, we all know that, but here’s 2 interesting viewpoints on the matter that will hopefully clear the murk and help you understand things a little better.

Seybold: Why Tables for Layout is Stupid

And a quote from the DesignForums Harry Roberts:

“You can hold a car up with bricks just as well as you could a jack, but bricks aren’t specifically built for that purpose. Sure the bricks will hold the car up, but it’s gonna be a lot harder to do, and in future the jack will be the easiest to manipulate and alter. And if you’re using bricks to hold up a car, what are you building your house with?”

Check it out by clicking here.

The PNC list input has at the time of writing been tested for the first 10,000 primes, so it’s pretty accurate. If you find any problems though, please do drop me a comment.

I’ll be blogging about the workings behind the PNC soon so look out for that.

:)

Any comments are more than welcome.

Don’t worry about the confusing list of characters, all will be explained.

Here’s the finished code:

Be careful when copying and pasting

But you don’t understand that right? I didn’t. Let me explain:

Here’s an example

We start with a variable that contains a string, in this example “dave”.

Then add the .replace code:

The basic structure is:

Now if we add an alert box to pop up and show us our new string we can see it in action:

Remember, we don’t need quotation marks for variables

Which gives us:

“My name is John”

Going back to our finished code, here’s what the code jargon means.

The blackslash (\) ‘escapes’ the following character. That just means it treats the next character as just that, rather than as part of the JS code.

The comma (,) is what we want to replace, and the dollar sign ($) tells JS to only catch the comma if it’s at the end of the string. Hopefully the rest is self-explanatory, although if not read through the article again and feel free to drop me a comment.

Note: If you want to remove every occurence of a string then use the code:

The ‘g’ after the closing forward slash is the key to that.

Note: With thanks to Joey for the basics behind this post and how2guru for the every occurence fix.