I’ve been working on a Flex based component for a Ruby on Rails application I’m doing. So far, I’ve made few decent strides toward integration with the rails framework. The following describes my first pass at integration and build automation.
From Wikipedia:
Internet Protocol version 6 (IPv6) is a network layer protocol for packet-switched internetworks. It is designated as the successor of IPv4, the current version of the Internet Protocol, for general use on the Internet.
The standards for IPv6 were complete in the mid 90’s, yet the adoption rate is next to 0. I can’t even remember the last time I read an article about it. What happened to it? Well, support for IPv6 has been quietly added to Windows, Linux, and OS X. Networks have sprung up all over the world that operate exclusively on IPv6. Unfortunately, most of the world is still schlumping along on the old protocol.
Why is this happening? Why do we build all our shiny new castles on top of a moldy old foundation? Who are the hold outs? Will we ever see IPv6 go mainstream? Time will tell.
This just in: ScrollBox.js v0.6
This latest update includes several bug fixes, some performance improvements, and some new functionality. The code has gone through several iterations and is nearly ready to be called stable.
My goal is to implement al of the functionality provided by the browser’s scrollbars. I expect the next release will be feature complete and I’ll have a 1.0 release by the end of the month.
Any feedback at this point would be greatly appreciated.
From the Bungie website:
The Halo 3 Multiplayer Beta will go live on May 16th at 12:00 AM PDT and run through June 6 th at 11:59 PM PDT. That means that folks who purchased specially marked copies of Crackdown, or won a spot in the Beta through the “Rule of Three” or other regional promotions, will be able to log into their Xbox Live Gold accounts, download and play the Halo 3 Multiplayer Beta and enjoy an early peek at the multiplayer aspect of the game.
I just watched the new trailer. It’s all very exciting. The graphics improvements are massive, though, that’s not really what interests me. To me, graphics are like frosting. They’re worthless unless the product itself is delicious. There are so many interesting new features. I can’t wait to try it out.
After some recent frustrations with a JavaScript scrollbar library I was forced to use, I decided to just up and make a better one myself. And so I have. It’s not totally done yet. Specifically, I haven’t tested it very much. Bit it’s available to anyone who needs a good JS Scroll Bar library on the cheap (free).
Check it out: ScrollBox.js
In my professional life, I often find myself working with JavaScript based scrollbars. While I personally find the approach distasteful, I understand that the decision is not always made by the developer (who knows best). I’ve been continually disappointed by the quality of the available libraries. So, I’ve set out to build my own and make it freely available to others. It’s based on - and requires - prototype.js.
Download: ScrollBox.js v0.8
Simply create a new ScrollBox object and pass in the element you would like to become a scroll box. Note that the element passed used to create the object must be positioned either relative or absolute. The example css file includes this directive on the first line.
Example:
var sb = new ScrollBox($('description_box'));
Full documentation will follow when I have time. For now, there is a complete implementation example included in the zip.
Fully customizable, mostly though simple CSS changes. A sample implementation is included in the download. Supports scrolling with the mouse wheel. The buttons support clicking and holding, the scrollbar has multiple selectable behaviors, and the handle is fully functional. Supports keyboard events up, down, page up, page down, home, and end. Works with named anchors.
If you would like to do some testing, please do. Feedback is greatly appreciated. I expect I’ll have a 1.0 release shortly.
Tested in the following browsers:
Copyright © 2007 Dave Grijalva
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the “Software”), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
It’s been a while, but I decided to go in and get some of the more crucial bugs from the last release.
Fixed in 0.8 beta:
Get it here: Coralize v 0.8 beta
I don’t actually own a Crackberry, but my girlfriend does, which makes me the default technical support representative for RIM. When it was decided that the Blackberry comes without a single reasonable ringtone, I began to look into installing alternatives. Here’s what I found.
Saw the Giants tie the A’s on Friday evening. It was a pre-season game, so they called it after the tenth inning.