New ratio calculator tool

[Aragorn]

I'm not too familiar with JS, but i've done a bit here and there, and the $(#objectname) syntax they've used seems particularly obscure to me?

The first drop down should just be hard coded into the list, but they've done it like that so all the data is stored in one place. If you want to add another gearbox, you just open the "arrays.js" and add it there, rather than having to add it to both the PHP page and the JS file.

[Bush65]

Wouldn't hard coding list contents prevent those like myself who don't always use Land Rover components in the drive train from entering alternate values?

While I see the need for fixing it to work with all popular browsers (and Dave apparently agrees), why clip it's versatility in other ways?

I found the calculator worked well in that respect, using chrome.

My only criticism (small) is the use of the same output speed range/increment for lo and hi box - with my low gearing (and I don't have an underdrive) the results aren't particularly useful or are not output in 1st and 2nd. As I see this issue it is simply because an inappropriate hard coded increment value of 10 (kph or mph) for lo box (damb there's that hard coding causing more problems )

[FridgeFreezer]

I do like a good geeky conversation

Excellent, know where there is one?

[Retroanaconda]

Wouldn't hard coding list contents prevent those like myself who don't always use Land Rover components in the drive train from entering alternate values?

While I see the need for fixing it to work with all popular browsers (and Dave apparently agrees), why clip it's versatility in other ways?

I found the calculator worked well in that respect, using chrome.

My only criticism (small) is the use of the same output speed range/increment for lo and hi box - with my low gearing (and I don't have an underdrive) the results aren't particularly useful or are not output in 1st and 2nd. As I see this issue it is simply because an inappropriate hard coded increment value of 10 (kph or mph) for lo box (damb there's that hard coding causing more problems )

I was only suggesting hard-coding in the known list of gearboxes, there could easily be an option for custom, at which point the boxes could have the values entered by the user.

Where there is a known list of possibilities and that list is not going to change (ie. a list of boxes, LT77, R380, Custom) there is no reason not to hard-code.

[rtbarton]

The facilty to save custom setups for later recall would be useful.

Why not enter tyre size, pressure and axle weight instead of twice the rolling radius

[Maverik]

Holy monkeys, now all the computer boffins wiggle out the woodwork... each to there own, but if car design goes on like it is, we'll all need to be swift on the old laptop to diagnose our ayling 4x4 machines.

Good tool thought.

[Gromit]

the $(#objectname) syntax they've used seems particularly obscure to me?

It's as shorthand for GetElementByID. It's part of the Prototype/jQuery framework (can't remember which)

[Mo Murphy]

I've got a code but I'm taking hot lemons for it

Mo

[elbekko]

It's as shorthand for GetElementByID. It's part of the Prototype/jQuery framework (can't remember which)

jQuery, although a lot of frameworks are using that syntax these days (not that I like it, but that's another story).

There is no need to hard code anything. The data should be stored in a properly designed database, output by PHP in a format (probably JSON or similar) so that JS can read it. For calculations like these there's absolutely no reason to reload the page (although it's slightly easier), and it would be downright retarded to use AJAX and have PHP calculate it.

Si, I suppose you mean outputting it all and using JS to unhide the appropriate lists. That would work, but wouldn't be very clean.

If I were bored and motivated enough (and I'm only one of those), I'd make one myself

[FridgeFreezer]

Yeah yeah - I've just re-written it in machine code but you'll need an oscilloscope to read the answer

[elbekko]

Obligatory http://xkcd.com/378/