If you’ve ever wanted to slideLeft or slideRight in jQuery, you may have noticed that you…can’t. You can slideUp and slideDown, but not slideLeft or slideRight. Why is this? I don’t know. I do know that getting those effects is a single line, though:
obj.animate({width:'show'}); obj.animate({width:'hide'}); obj.animate({width:'toggle'});
Simple, and easy to use. But why isn’t it in the core?
This is a handy little function I whipped up that will allow you to pass in three dates, and check if one date is between two others.
function dateWithin(beginDate,endDate,checkDate) {
var b,e,c;
b = Date.parse(beginDate);
e = Date.parse(endDate);
c = Date.parse(checkDate);
if((c <= e && c >= b)) {
return true;
}
return false;
}
Enjoy!
This is a problem that was driving me absolutely batty a little while ago.
In ActionScript, there’s an
<menu>
<item>
test
</item>
<item>
testy
</item>
<item>
sixty-eight
</item>
</menu>
Will properly end up as “test”, “testy”, and “sixty-eight” if you were to create an array of
However.
Under Javascript, there is no <menu><item>test</item><item>testy</item><item>sixty-eight</item></menu>
Otherwise, you’ll end up with nodes in places you didn’t expect them to be, and values like “&tab;test” instead of the “test” you were expecting.
With the rising popularity of Ajax, more and more people are starting to build webapps that rely heavily on Javascript. In a lot of cases, the HTML
However, a problem with this style is that, at least in some cases, the new javascript controls mean that the form no longer works as the user expects. This is bad for usability, and I’ve managed to figure out that the whole problem can be resolved (and unobtrusively, no less) by making use of the
If a user submits a form and there is a value for its
When we write
By combining the
<script>
var d = document; // shorthand variable
function handleFormSubmission() {
var inputValue = d.getElementsByTagName('input')[0].value;
alert('The Value of the input is: ' + inputValue);
}
</script>
<form onsubmit='handleFormSubmission(); return false;' action='http://girasquid.com/sample_code/jsdisabled.shtml'>
<input type='text' />
<input type='submit' />
</form>
If you want to see how it turns out in an actual page, take a look at the Hardcoded onsubmit sample code I’ve put up.
This method involves painstakingly hard-coding the
The answer is yes. Here’s the new code:
<script>
var d = document; // shorthand variable
function handleFormSubmission() {
var inputValue = d.getElementsByTagName('input')[0].value;
alert('The Value of the input is: ' + inputValue);
}
// This anonymous function will attach our 'onsubmit' action for us, so that we don't add anything to our HTML markup.
window.onload = function() {
d.getElementsByTagName('form')[0].setAttribute('onsubmit','handleFormSubmission();return false;');
}
</script>
<form action='http://girasquid.com/sample_code/jsdisabled.shtml'>
<input type='text' />
<input type='submit' />
</form>
To see it in action, check out my window.onload onsubmit sample code.
A friend and I are busily sketching out a project idea that, among other things, involves a countdown. For a while, I couldn’t figure out how to do it. But after giving it a little bit more thought, I realized that all we’d need is a little bit of javascript and an initializing function that would begin the countdown, along with refreshing the page when the countdown was finished(most of the real ‘actions’ per se are run by server-side code, not client-side).
This was all well and good, and last night I happily sat down and hacked out a solution. You can see it in the portfolio section of girasquid.com. And it works, and it does what it needs to.
But at the same time, it’s not as … robust as I’d like it to be. It doesn’t do all the cool things. It won’t let me put more than one countdown on a page without hard-coding that. It won’t let me spawn off lots of countdowns at once with all different times, and then independently start and stop them.
For some of my projects, I encounter a problem like this and just go “oh. Well. I’ll do that later.”, and put it on my “torewrite” list(which is growing rather large, unfortunately). But this is a piece of code that’s generally useful, and I think that if I could develop it further so that it was perhaps object-oriented and more flexible, other people would use it. And that would be sweet. Therefore, I’m in the process of redesigning it. This is what I’ve sketched out.
We would have a Countdown object. It would have different member variables, that would make it easy for a separate script to interact with it’s parts. These are the variables and their breakdowns:
And then we would have different methods that we’d be able to call to actually do our counting. Here’s a sketch so far:
There would also be multiple utility functions for things like making sure the hours/minutes display correctly and such. I’m planning on introducing one function that lets a user pass in a string with certain placeholders, and have the object return the string, with the placeholders filled in with their respective values. That would be cool.
I’m going to get to work on this.
You are currently browsing the archives for the javascript category.