Autocomplete HTML/CSS/JavaScript/python/xml/php/c with CTRL-X CTRL-O – parsed.org – Add autocomplete features to Vim. Wish I’d come across this sooner.
Tags: vim autocomplete php javascript html python
OpenID Splash – Looks like Yahoo has taken major dive into the OpenID pool.
Tags: openid yahoo
Cross-Site XMLHttpRequest – MDC – More details on how this works in Firefox 3.
Tags: firefox javascript xmlhttprequest
John Resig – Cross-Site XMLHttpRequest – Basic example of how Cross Site XMLHttpRequest’s work in Firefox 3.
Tags: firefox johnresig javascript xmlhttprequest
Recover Truncated PHP Serialized Arrays // ShaunInman.com – Another example of why databases should NEVER silenty truncate data. If the data doesn’t fit in the field then the insert/update needs to fail.
Tags: php database
Facebox 1.0 – Another lightbox clone in the style of Facebook. Requires JQuery.
Tags: facebox jquery javascript lightbox
Beastie Blog | Using Screen to log yourself. – I’ve never used the logging feature of screen, might use it next time I setup a new server though.
Tags: screen
GrabFS: The Screenshot File System – Not sure I’ll ever use it, but this is just an awesome hack.
Tags: macosx screenshot grabfs fuse macfuse
PuTTY Tray – Always important to have a good ssh client for your Windows box.
Tags: putty puttytray ssh
ImageFlow 0.8 – Another Cover Flow style image browser in Javascript.
Tags: imageflow javascript coverflow gallery
Movable Type Goes Open Source Today – “Based on my personal experiences, another major advantage for WordPress would be that it doesn’t suck.” (Aaron Hockley)
Tags: wordpress movabletype
DragonStyle: Page Support in Windows Live Writer – Good point, if you haven’t heard already, WLW can edit pages in WordPress.
Tags: wordpress windowslivewriter
Julien Lecomte?s Blog > The Problem With innerHTML – Ah innerHTML, seems to be so wrong, but so right. But then wrong again.
Tags: javascript innerhtml
Javascript base64 encoding – Encode and decode base64 in Javascript.
Tags: javascript base64
It’s been 18 months since I first released the editinplace Javascript code. And many months since I’d really done anything new with it.
So I finally put together two things, a new version and new home for EditInPlace. First, the new home, editinplace.org. There’s documentation, a blog, downloads and forums. The main push for me to do this was to try out the forums. I’m still amazed at the number of people contacting me expressing interest in this, so I’m hoping that the forums will provide a better way for people to ask questions and get answers. If nothing else it moves from my inbox and out on the web, where Google can index it for all to see.
Next, a new version, 0.5.0. This is a rewrite based on the 0.3.3 code that uses more Prototype specific features. If you’ve used EIP before you’ll want to review the example.html and save.php files to see how things have changed in the new version. Nothing earth shattering, but it is different. You can get it now at the download page.
Go check it out and let me know what you think.
Tobie Langel pulled out an interesting little JavaScript nugget from the recent Background Music post on the Webkit/Safari Blog:
Some Web pages specify repeating timers with an extremely small timeout. In fact they often use the value 0 to mean “Fire as soon as you can.” Safari 2 does not throttle these timeouts, and so a poorly-constructed page that specifies a repeating timer under 10ms will actually hog a lot of CPU. Aggressive timers were actually a problem in Mozilla for a long time before being fixed, and they are currently a problem in Safari 2. WinIE, Firefox, and WebKit nightlies basically error-correct the badly constructed page and ignore timer values of < 10ms by changing them to be 10ms.
So don’t bother using setTimeout or setInterval for something less than 10ms.
The Javascript library framework Prototype has a new home at Prototypejs.org. With API docs, tutorials and a blog.
Oh, and version 1.5.0 of Prototype is now available for download
Why JSON isn’t just for JavaScript – Simon Willison.
The sweet spot for JSON is serializing simple data structures for transfer between programming languages. If you need more complex data structures (maybe with some kind of schema for validation), use XML. If you want to do full blown RPC use SOAP or XML-RPC. If you just want a light-weight format for moving data around, JSON fits the bill admirably.
What do we lose from not using XML? The ability to use XML tools. If you’re someone who breathes XSLT that might be a problem; if like me your approach when faced with XML is to parse it in to a more agreeable data structure as soon as possible you’ll find JSON far more productive.
Emphasis mine.