jobs
http://alljobsbasics.blogspot.com/2009/05/work-from-home-2.html
java jobs
http://freehrquestions.blogspot.com/2009/06/java-jobs.html
oracle jobs
http://freehrquestions.blogspot.com/2009/06/oracle-jobs.html
dotnet jobs
http://freehrquestions.blogspot.com/2009/06/dotnet-jobs.html
sap jo
I was having a poke around under the hood of the latest RC and noticed
some changes to event handling (I think the changes were actually made
for RC1, but none the less).
The event handling system now uses the new Element Storage to cache
handlers, and I'm interested to learn the rationale for th
The former, I believe. I would tend to think that these changes would
actually cause higher memory consumptions on one-paged applications
(handlers of removed DOM nodes cannot be garbage collected).
On Jun 23, 11:53 pm, Mike Rumble wrote:
> I was having a poke around under the hood of the latest
I detest the way setInterval() looks, so I came up with this... have been
using it my personal JS for some time.
Object.extend(Function.prototype, {
repeat: function() {
var __method = this, args = $A(arguments), interval = args.shift() *
1000;
return window.setInterval(function() {
Why you can't use closure or Function#curry based on it?
(new PeriodicalExecuter(function(someData){
var x = someData.num;
//
}.curry({ num: 1, text: "string" })));
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
I used a inherit class to implement that functionality:
var PeriodicalExecuterUserData = Class.create(PeriodicalExecuter,
{
initialize: function($super, callback, frequency, userdata)
{
this.userdata = userdata;
$super(callback, frequency);
2009/6/22 Elit :
>
> Earlier today I ran into a little problem.
> I have this XHTML page which I create with an XML/XSL transformation.
> When the page is loaded, I tried to add an element to it using
> prototype's 'new Element()'. That created an element which I could add
> to the page, but after
