Use Tables!

So, first stop: I finally got and pointed the domain name www.gijsk.com to this site. WordPress has been updated to that effect, or so I think, and hopefully all you people’s DNS servers will be, too, within a few hours/days.

Seconds stop: I’ve published a convenience page with my patches and some handy-dandy xpi files. You might find it interesting, or so I hope .

Now I’m off to go packing and do some last-minute shopping for my holiday. I just checked in (and picked perfect seats) from my desk chair – SAS are great so far!

Yesterday someone rang my doorbell, asked if I wanted to buy dvd’s from him, and upon my negative answer forced the door open wider (I’d only put it ajar) and pointed a knife at me. Me being unarmed and not much of a fighter, I didn’t do much but trying to stay calm, and he eventually left with my digital camera, an mp3 player and 40 euro in cash (but not my wallet (bank cards, creditcard…) or my laptop (which had been hiding under an empty shopping bag, by pure chance)).

Obviously I called the cops later on, and spent much of yesterday recounting the story to various people, roughly half of them police officers. I didn’t sleep much tonight, and I’m taking a break for two days to calm down and such… James Ross found a small Venkman bug that I want to squash on sunday if I feel more normal psychologically. In the meantime I’m at my parents. Mail will reach me.

Task List

And I’m happy. But it doesn’t end here, I still want to fix 2 more things on that list, and obviously I need to get all those patches reviewed and checked in. After which, right now, things look as if I’ll end up with 2/3 of my original list finished (the security issues popped up during the whole thing, and in the end turned out to be out of my league for the most part), and 3/4 of it resolved (1 worksforme, 1 wontfix). Additionally, it’s the top 15 items, so that hopefully means I’ll have stuck to my priorities pretty well.
I hope people feel that’s enough (for now), and we’ll see how things work out, won’t we?

On a separate note, I’ll be going on a holiday to Sweden the early morning of August 22 (yes, that’s the day after the deadline). Speaking of deadline, I have a little counter on my home pc that I’ll try to hack into this wordpress thing. By the time you read this is it should hopefully be there.

I’m back from my away time. I still have to get into a good daily rhythm after so much time in what’s really a different world, I suppose, but I’ll be alright within the coming week. I’ve caught up with email and such, just need to start being productive again.

As of tomorrow morning 4am I’m on holiday, vacation or sabbatical if you prefer that word. I’ll be off to France and will be without internet access in the coming week. I will return on July 16, and you can expect me to start replying to email (and generally being alive in the ‘net sense of things) again on July 17. If you need me for Summer of Code or Mozilla stuff, you can send me email and I’ll get back to you ASAP on July 16 or 17.

bug 341764 is now fixed on both trunk and the 1.8 branch, meaning you can now debug from the slow script warning dialog if you have a debugger like Firebug or Venkman open. Woo!

On the title: The Dialog of death just sounds so much better than the “Slow Script warning”. Regardless, if a developer encounters a dialog like it unexpectedly, it generally means they screwed up. Unfortunately, right now they can’t in any way check why that happened. If they stop the script, then that’s just that and they have no way of going back into the slow state. If they choose to continue running the script they won’t get anywhere either because usually in cases like that all other UI is hung.

Solution? Add a debug script button to the dialog if and only if there’s an active debugger open. The debugger can be Firebug or Venkman, but it should work just as well if an external debugger is in use (like the ATF one that you get when developing XUL stuff in Eclipse). There’s a patch for branch and for trunk on bug 341764, but I would definitely prefer if this solution only ended up on branch (permanently), given that creating an optional dependency in DOM on JSD seems not that right (in this case optional means that DOM will still build fine without JSD (–disable-jsd) and will just use it if it can).

So now the waiting is for the review people to notice my requests and hopefully have time soon.

technorati tags:javascript, soc, mozilla, slow-script-dialog, google, jsd, venkman, firebug, webdevelopment

So the last few days I’ve been trying to get a profile of Venkman/JSD startup. First I’ll talk about the hurdles I met along the way for a bit. I decided that the results and conclusions I took from them are probably better off on a wiki page. Please feel free to let me know what you think about them. (more…)

So, 3 days after barcamp ended, Google gave me official word that I’ve been accepted in the Google Summer of Code. I will be working to improve the JS Debugging experience in Mozilla Firefox, specifically for webdevelopers. In order to do so, I need input from the (other) people who debug their own javascript on a daily basis.

• What’s missing?
• What’s been done wrong? What’s been done exceptionally right?
• What tools do you use? Why?
• Do you use Venkman? Why, or why not?
• Do you use the MS Script debugger? Why, why not?
• Is either tool better than the other, and if so, why?
• What kind of problems do you spend the largest amount of time on, and how can a debugger help you change that (or at least shorten that amount of time)?

You can email me a response to those questions, but you can also comment on the tracking bug for my project, or on this blogpost. Thanks in advance!