TeamCo AntHill

Tooltip.js

2009-11-09T03:45:00.000-08:00

jQuery:
tip.init(object) #tooltip will be taken from object "helper" attribute
img src="..." helper="..."
tip.init('img[helper]')

var tip = {
init : function(e){
   $(e).bind("mouseenter", this.createTip);
   $(e).mouseleave(function(){$("#tip").remove()});
   $(e).click(function(){$("#tip").remove()});
   $(e).mousemove(function(e){$("#tip").css({left:e.pageX+30,
                                             top:e.pageY-16})});
},
createTip : function(e) {
    var obj=$(e.currentTarget),
        title=$.trim(obj.attr("helper"));
    if(title.length>0){        
       return $("#tip").length === 0 ?
          $("<div>").html("<span>"+$.trim(obj.attr("helper"))+"</span>").
                     attr("id","tip").
                     css({left:e.pageX+30,
                          top:e.pageY-16,
                          position:'absolute',
                          border:'1px solid #FFE222',
                          background:'#FFFBC2',
                          color:'#514721',
                          padding:'5px 10px',
                          textTransform:'lowercase',
                          fontVariant:'small-caps',
                          zIndex:9000}).
                     appendTo("body") : null;
        } else {return false}
    }
};

Prototype:
tip.createTip(container,object) #tooltip will be taken from object "title" attribute
<div id="container">
<img src="..." title="..." />
</div>
tip.createTip($('container'),'img[title]')

var tip = {
 title  : '',
 opacity: .8,
 marginX: 30,
 marginY: -46,
 position : function(i,e){
     return i.setStyle({left:e.clientX+this.marginX+'px',
                        top:e.clientY+this.marginY+'px'})
 },
 enter : function(i){
     var tip=this;
     $(i).observe(antHill.events.menter,function(e){
         var div,obj=$(e.currentTarget);
         tip.title=obj.readAttribute("title");
         obj.writeAttribute("title",'');
         if($("tip")===null){
             div=new Element('div',{id:'tip'});
             div.addClassName('tooltip').
                 setOpacity(tip.opacity).
                 innerHTML="<span>"+tip.title+"</span>";
             tip.position(div,e);
             $($$('body')[0]).insert({bottom:div});
         }
         Event.stop(e)}.bindAsEventListener($(i)));
 },
 leave : function(i){
     $(i).observe(antHill.events.mleave,function(e){
         $("tip").remove();
         $(i).writeAttribute("title",tip.title);
         Event.stop(e)}.bindAsEventListener($(i)));
 },
 move : function(i){
     $(i).observe(antHill.events.mmove,function(e){
         antHill.tip.position($("tip"),e);
         Event.stop(e)}.bindAsEventListener($(i)));
 },
 init : function(i){
     this.enter(i);
     this.leave(i);
     this.move(i);
 },
 createTip : function(c,i){c.select(i).
                             each(function(i){tip.init(i)})}
};

AutoMySQLBackup

2009-11-05T03:56:00.000-08:00

A script to take daily, weekly and monthly backups of your MySQL databases using mysqldump. Features - Backup mutiple databases - Single backup file or to a seperate file for each DB - Compress backup files - Backup remote servers - E-mail logs ...

http://sourceforge.net/projects/automysqlbackup/

7 Free Tools to Minify your Scripts and CSS

2009-11-05T03:48:00.000-08:00

JSMin (JavaScript Minifier) - removes comments and unnecessary whitespace from JavaScript files
JSO (JavaScript Optimizer) - allows you to manage your JavaScript and CSS resources and to reduce the amount of data transfered between the server and the client.
Packer – An online JavaScript Compressor
JSCompress.com – Online tool that uses either JSMin or Packer to compress your files
CSS Compressor – Online tool that compresses your CSS file
DigitalOverload JavaScript Minifier – Online tool that minifies your JavaScript files
YUI Compressor – A JavaScript minifier designed to be 100% safe and yields a higher compression ratio than most other tools.

http://www.devcurry.com/2009/11/7-free-tools-to-minify-your-scripts-and.html

Caja

2009-11-01T05:00:00.000-08:00

Caja allows websites to safely embed DHTML web applications from third parties, and enables rich interaction between the embedding page and the embedded applications. It uses an object-capability security model to allow for a wide range of flexible security policies, so that the containing page can effectively control the embedded applications' use of user data and to allow gadgets to prevent interference between gadgets' UI elements.

Today, some websites embed third-party code using iframes. This approach does not prevent a wide variety of attacks: redirection to phishing pages which could pretend to be a login page for the embedding application; stopping the browser from working until the user downloads malware; stealing history information about which sites a user has visited so that more target phishing attacks can be done; and port scanning the user's local network. Finally, even though a website can choose not to give data to an iframe app, once it has done so it can place no further restrictions on what the iframe app can do with it — it cannot stop the iframe app from sending that data elsewhere.

Caja addresses these problems which are not addressed by iframe jails; and it does so in a very flexible way. If a container wishes to allow an embedded application to use a particular web service, but not to send arbitrary network requests, then it can give the application an object that interacts with that web service, but deny access to XMLHttpRequest. Under Caja, passing objects grants authority, and denying access to objects denies authority, as is typical in an object-capability environment. Information leakage can be prevented by allowing user data to be encapsulated in objects that can be rendered in user-readable form but not read by scripts ; we can prevent leakage without solving the problem of covert channels.

http://code.google.com/p/google-caja/

Accordion.js

2009-10-13T06:19:00.000-07:00

accordion.init params (accordion.init(5,1,"ul.menu","slow"):

5: opened section index (numeric)
1: autohide (bool)
"ul.menu": container element
"slow": speed

On each page can be rendered "#navid" parameter (section name) to focus setting.

HTML

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="accordion.js"></script>
<script type="text/javascript">
$(document).ready(function(){accordion.init(5,1,"ul.menu","slow")});
</script>
</head>
<body>
<ul class="menu">
<li rel="category">
<h3 rel="title">parent</h3>
<ul level="0">
 <li rel="category">
    <h3 rel="title">category 1</h3>
    <ul level="1">
       <li class="sub_items"><a href="#">link 1</a></li>
       <li class="sub_items"><a href="#">link 2</a></li>
       <li class="sub_items"><a href="#">link 3</a></li>
    </ul>
 </li>
 <li rel="category">
    <h3 rel="title">category 2</h3>
    <ul level="1">
       <li class="sub_items"><a href="#">link 1</a></li>
       <li class="sub_items"><a href="#">link 2</a></li>
    </ul>
 </li>
 <li rel="category">
    <h3 rel="title">category 2</h3>
    <ul level="1">
       <li class="sub_items"><a href="#">link 1</a></li>
       <li class="sub_items"><a href="#">link 2</a></li>
    </ul>
 </li>
</ul>
</li>                  
<li rel="category">
<h3 rel="title">parent</h3>
<ul level="0">
 <li rel="category">
    <h3 rel="title">category 1</h3>
    <ul level="1">
       <li class="sub_items"><a href="#">link 1</a></li>
       <li class="sub_items"><a href="#">link 2</a></li>
       <li class="sub_items"><a href="#">link 3</a></li>
    </ul>
 </li>
 <li rel="category">
    <h3 rel="title">category 2</h3>
    <ul level="1">
       <li class="sub_items"><a href="#">link 1</a></li>
       <li class="sub_items"><a href="#">link 2</a></li>
    </ul>
 </li>
<li rel="category">
<h3 rel="title">parent</h3>
<ul level="1">
 <li rel="category">
    <h3 rel="title">category 1</h3>
    <ul level="2">
       <li class="sub_items"><a href="#">link 1</a></li>
       <li class="sub_items"><a href="#">link 2</a></li>
       <li class="sub_items"><a href="#">link 3</a></li>
    </ul>
 </li>
 <li rel="category">
    <h3 rel="title">category 2</h3>
    <ul level="2">
       <li class="sub_items"><a href="#">link 1</a></li>
       <li class="sub_items"><a href="#">link 2</a></li>
    </ul>
 </li>
 <li rel="category">
    <h3 rel="title">category 2</h3>
    <ul level="2">
       <li class="sub_items"><a href="#">link 1</a></li>
       <li class="sub_items"><a href="#">link 2</a></li>
    </ul>
 </li>
</ul>
</li>
 <li rel="category">
    <h3 rel="title">category 2</h3>
    <ul level="1">
       <li class="sub_items"><a href="#">link 1</a></li>
       <li class="sub_items"><a href="#">link 2</a></li>
    </ul>
 </li>
</ul>
</li>
</ul>
<span id="navid" style="display:none">category 1</span>
</body>
</html>

Javascript

$.fn.equals = function(compareTo) {
       if (!compareTo||!compareTo.length||this.length!=compareTo.length){return false}
       for(var i=0;i       return true;
}
var menu = function accordion(l,h,c,s){
 var accordion = {
    init : function(){
       this.autohide=h;
       this.speed=s;   
       this.parents=[];   
       this.container=$(c);   
       this.focus=$("#navid");
       this.initMenu(l)}, 
    categories : function(){return this.getH3(this.getLi(this.container))},   
    getLi : function(e){return $(e).find("li[rel=category]")},   
    getH3 : function(e){return $(e).find("h3[rel=title]")},      
    close : function(e){$(e).find("h3:first").addClass("close")},      
    findParents: function(p){
       var c=this.container,a=this.parents;
       $.each(p.parents("ul"),function(){
  if($(this).equals(c)){return}
  else {a.push($(this))}})
       return a},
    up : function(p,e,h){
       var u=p.find("ul");
       h?u.hide():u.slideUp(this.speed);
       this.getH3(p).removeClass("close")},
    down : function(p,e){
       var b=$.browser.msie&&$.browser.version=='7.0',
    o=this.findParents(p),
    s=this.speed, 
    u=p.parent().find("ul[level="+e.attr("level")+"]"),
    h=$.grep(u,function(a){return a!=e[0]});     
       b?e.show(s):e.slideDown(s);
       if(this.autohide)$.each(h,function(){accordion.up($(this).parent())});
       this.close(p);      
       $.each(o, function(){
  accordion.close($(this).parent());
  b?$(this).show(s):$(this).slideDown(s)})},
    anime : function(t,e,h){this[t](e.parent(),e,h)},
    setFocus : function(i) {
       var f=this.focus,t=f.text();
       if(f.length>0){$.each(this.categories(),function(k,v){if($(v).text()==t)i=k})}
       return i},
    initMenu : function(i,init){
       var p,e=this.container.find("ul");
       if(i==-1)this.setEvents(e);
       if(init){e=$(e[i]);e.is(':visible')?this.anime("up",e):this.anime("down",e)}
       else{this.setEvents(e);i=this.setFocus(i);this.anime("down",$(e[i]))}},
    setEvents : function(e){
       var h=this.categories();
       h.bind("click",function(e){accordion.initMenu(h.index($(e.target)),1);});
       this.anime("up",e,1)}
 }
 return accordion.init();
}

iPhone & Rails

2009-10-08T06:50:00.000-07:00

ObjectiveResource is an Objective-C port of Ruby on Rails' ActiveResource. It provides a way to serialize objects to and from Rails' standard RESTful web-services (via XML or JSON) and handles much of the complexity involved with invoking web-services of any language from the iPhone.

http://iphoneonrails.com/

Cross-Domain Ajax with Flash

2009-10-07T07:40:00.000-07:00

flXHR is a *client-based* cross-browser, XHR-compatible tool for cross-domain Ajax (Flash) communication. It utilizes an invisible flXHR.swf instance that acts as sort of a client-side proxy for requests, combined with a Javascript object/module wrapper that exposes an identical interface to the native XMLHttpRequest (XHR) browser object, with a few helpful additions and a couple of minor limitations (see the documentation for more details).

flXHR requires plugin v9.0.124 for security reasons. See the documentation for a configuration flag "autoUpdatePlayer" which will attempt to automatically inline update the plugin if need be.

The result is that flXHR can be used as a drop-in replacement for XHR based Ajax, giving you consistent, secure, efficient cross-domain client-to-server cross-domain Ajax communication, without messy workarounds such as IFRAME proxies, dynamic script tags, or server-side proxying.

flXHR brings a whole new world of cross-domain Ajax and API-consistency to any browser with Javascript and Flash Player plugin v9+ support (Adobe claims Flash has 99% browser support now External Link). No other methods or workarounds can claim that kind of wide-spread support or consistency. In addition, flXHR boasts the ability to be dropped-in to many different Javascript frameworks (Dojo, Prototype, jQuery, etc) for even easier and more robust Ajax usage.

http://flxhr.flensed.com/

An Introduction to JavaScript’s “this”

2009-10-01T01:07:00.000-07:00

JavaScript is an amazing little language, but it’s got some quirks that turn a lot of people off. One of those quirks is this, and how it’s not necessarily what you expect it to be. this isn’t that complicated, but there are very few explanations of how it works on the internet. I find myself constantly re-explaining the concept to those who are new to JavaScript development. This article is an attempt to explain how this works and how to use it properly.

http://justin.harmonize.fm/index.php/2009/09/an-introduction-to-javascripts-this/

BugMash

2009-10-01T01:05:00.000-07:00

Have you ever wondered how you could get started contributing to the core Rails code? Have you been watching the growth of RailsBridge and wondering where you could fit in? Well, wonder no longer: we have an answer to both of those questions. Announcing:

The First Rails and RailsBridge BugMash

The idea is simple: RailsBridge has a lot of energy. The Rails Lighthouse has a lot of open tickets. With the help of some Rails Core team members, we're going to see what we can do to cut down the number of open tickets, encourage more people to get involved with the Rails source, and have some fun.

Confirm that the bug can be reproduced
If it can't be reproduced, try to figure out what information would make it possible to be reproduced
If it can be reproduced, add the missing pieces: better repro instructions, a failing patch, and/or a patch that applies cleanly to the current Rails source
Bring promising tickets to the attention of the Core team

Some of the Bridgers will be organizing a face-to-face way for BugMash participants to come together (Teams), but there's no need to be there to be a part of it. We'll also have a room open on IRC, and people who are familiar with the Rails internals will be available to help point you in the right direction. We're going to do everything we can to make it easy to start contributing to Rails.

We'll be adding more details to this bare outline over the coming week, including a checklist of what you can do to get ready to work in the Rails source and details on a scoring system and rewards for the most active participants. For now, though, there are two things for you to do:

Reserve at least a chunk of that weekend to roll up your sleeves and work on the BugMash
Speak up if you can contribute prizes, familiarity with the Rails source, or other help to the project.

Official BugMash hours

Rails contributors are located all over the world, so we're going to define an extended weekend for the BugMash. So we're going to run from Saturday noon in New Zealand (00:00:00 September 26 GMT) to Sunday midnight on the US West coast (07:00:00 September 28 GMT). That should give everyone who wants to be involved plenty of time to participate.

Resources

Pre-flight Checklist
BugMashFlowchart
BugMashCheatSheet
Contributing to Rails
Tickets tagged with 'bugmash'
There are official Rails Continuous Integration servers which test against multiple interpreters and databases. See the Continuous Integration section in the BugMashFlowchart
The Rails Continuous Integration Server Setup Notes can be helpful in getting the various databases configured
http://railscasts.com/episodes/113-contributing-to-rails-with-git
BugMashStats

http://railsbridge.org/
http://wiki.railsbridge.org/projects/railsbridge/wiki/BugMash

YUI 3 Is Out!

2009-10-01T01:01:00.000-07:00

This is a ground-up redesign of YUI:

Selector-driven: YUI 3 is built around one of the lightest, fastest selector engines available, bringing the expressive power of the CSS selector specification into actions that target DOM nodes.
Syntactically terse: Without polluting the global namespace, YUI 3 supports a more terse coding style in which more can be accomplished with less code.
Self-completing: YUI 3’s light (6.2KB gzipped) seed file can serve as the starting point for any implementation. As long as this seed file is present on the page, you can load any module in the library on the fly. And all modules brought into the page via the built-in loader are done so via combo-handled, non-blocking HTTP requests. This makes loading the library safe, easy and fast.
Sandboxed: YUI modules are bound to YUI instances when you use() them; this protects you against changes that might happen later in the page’s lifecycle. (In other words, if someone blows away a module you’re using after you’ve created your YUI instance, your code won’t be affected.)

http://ajaxian.com/archives/yui-3-is-out
http://developer.yahoo.com/yui/3/

Ruby on Rails application with Adobe Flex & RestfulX Framework

2009-09-15T06:49:00.001-07:00

A simple tutorial on how to create a Ruby on Rails application with Adobe Flex and the RestfulX Framework in 10 minutes and 10 steps.

Ultimate IE6 Cheatsheet: How To Fix 25+ Internet Explorer 6 Bugs

2009-09-15T05:58:00.000-07:00

Written by Benjamin / September 15, 2009

The best strategy for dealing with Internet Explorer 6 is not to support it.

Stop. Ok, I feel your frustration. You're a web developer and you're ready to tear your hair out because you have to support Internet Explorer 6, but, to put it tactfully, IE6 doesn't support you. You've spent hours on it, but you just can't seem to get your layout right. I can empathize. I can also help.

This isn't one of those rants about IE6 or a campaign to try to kill it. There are enough of those around the web, but they don't help if you need to support IE6 because it still has a significant enough marketshare that you can't ignore it for business reasons. No, this is the resource you've been hoping for.

I've scoured the web for resources and also included some of my own fixes for IE6 and now I've put it all together in this cheetsheet/reference manual as a resource for anyone who has to deal with Internet Explorer 6. Where possible, I've done my best to provide the cleanest and valid solutions to each bug instead of ugly hacks. I've also tried to give proper credit for each case, but some of the solutions have been shared so many times that finding the original discover of each fix is difficult. If you see a missing credit or if I missed a bug and fix, please contact me and let me know and I'll update this page.

This massive IE6 guide took a while to put together, so bookmark it, share it, tweet it, and use it to save yourself and your coworkers hours of screaming at your monitor and banging your head against your desk or other inanimate objects. Don't be fooled, however, this cheatsheet is as much for me as it is for you.

http://www.virtuosimedia.com/tutorials/ultimate-ie6-cheatsheet-how-to-fix-25-internet-explorer-6-bugs

Mac Central

2009-09-15T05:40:00.000-07:00

Keyboard Shortcuts
Multi-Touch Gestures
Tips & Tricks
Recommended programs

http://www.danrodney.com/mac/index.html

LightningDOM

2009-09-13T06:16:00.000-07:00

Why on earth would you re-implement the DOM?

And in Javascript?? You’ve got to be out of your minds! Well, it turns out there is actually a sane reason: speed. Most web developers know that the DOM is dog slow, particularly in IE-land. There are plans to fix this in IE8, Chrome and possibly Firefox 3.1, but for at least the next few years, we’ll be supporting browsers with a slow DOM.

But is it really too slow? I mean, can’t users wait a couple seconds for the page to load? After all, they’ve been doing it for years! No, they can’t wait. At least, not anymore. Google taught us the competitive advantage of speed and we’ve been trying (though it’s been tough in Web 2.0 land) to not look back.

http://blog.cornerstonenw.com/2008/09/10/donating-lightningdom/

Formaldehyde

2009-09-13T01:59:00.000-07:00

PHP and Web Development are perfectly married but Ajax interactions have always been difficult to debug. Applications like Firebug are extremely useful to deploy, debug, and generally for Web Applications development. These kind of softwares are still running via browser but both JavaScript and PHP require hard test, being dynamic programming languages, as dynamic is an Ajax interaction. There are several ways to debug Ajax calls but honestly I have never found one able to be integrated without effort and easy to manage directly via JavaScript and/or Firebog or whatever console is there ... This is the reason I have created a single, well tested, widely compatible and fast Error Debugger, where all we need to do is to require_once this single file for each Ajax called page. Everything else will become so natural that you will ask yourself why on earth nobody created such simple solution before. Most advanced PHP frameworks integrate an error manager able to make deploy and debug easier. Unofrtunately, too often these frameworks are not that simple to configure or are not scalable enough, even if what we are trying to do is extremely simple. For these cases and every other, Formaldehyde could be integrated without effort, at all! To better understand how Formaldehyde will change our daily WTF during Ajax interactions, words cannot compete with code and images.

http://code.google.com/p/formaldehyde/
http://code.google.com/p/formaldehyde/wiki/FirePHP

Master slave adapter

2009-09-06T03:02:00.000-07:00

This simple plugin acts as a common ActiveRecord adapter and allows you to setup a master-slave environment using any database you like (and is supported by ActiveRecord).

This plugin works by handling two connections, one to a master database, that will receive all non-"SELECT" statements, and another to a slave database that that is going to receive all SELECT statements. It also tries to do as little black magic as possible, it works just like any other ActiveRecord database adapter and performs no monkeypatching at all, so it’s easy and simple to use and understand.

http://agilewebdevelopment.com/plugins/master_slave_adapter

IxEdit

2009-09-03T04:56:00.000-07:00

IxEdit is a JavaScript-based interaction design tool for the web. With IxEdit, designers can practice DOM-scripting without coding to change, add, move, or transform elements dynamically on your web pages. Especially, IxEdit must be useful to try various interactions rapidly in the prototyping phase of your web application.
Interactions are visual changes of the screen which occur when users act on user interface elements. In other words, interactions are the behaviors of the user interface. For instance, when a user click a button, an image switches to another, or when a user drags an edge, the viewport expands. Those are interactions. Users are doing their jobs with a computer through various interactions generally.
To implement interactions on a web page, programming with JavaScript is needed. However, it is hard to manage JavaScript for many designers. Therefore, making well-designed web interactions is difficult in general. IxEdit solves this problem. If you have basic knowledge about HTML and CSS, you can create interactions as you like. JavaScript coding is no longer needed.

http://www.ixedit.com

roo

2009-09-02T06:42:00.000-07:00

This gem allows you to access the content of

Open-office spreadsheets (.ods)
Excel spreadsheets (.xls)
Google (online) spreadsheets
Excel’s new file format .xlsx

http://roo.rubyforge.org/rdoc/index.html
http://roo.rubyforge.org/

Prototype 1.6.1 released

2009-09-02T01:07:00.000-07:00

Full compatibility with new browsers. This version of Prototype fully supports versions 1.0 and higher of Google Chrome, and Internet Explorer 8 in both compatibility mode and super-standards mode.
Element metadata storage. Easily associate JavaScript key/value pairs with a DOM element. See the blog post that started it off.
New mouse events. Internet Explorer’s proprietary “mouseenter” and “mouseleave” events are now available in all browsers.
Improved performance and housekeeping. The frequently used Function#bind, String#escapeHTML, and Element#down methods are faster, and Prototype is better at cleaning up after itself.
Built with Sprockets. You can now include the Prototype source code repository in your application and use Sprockets for dependency management and distribution.
Inline documentation with PDoc. Our API documentation is now stored in the source code with PDoc so it’s easy to send patches or view documentation for a specific version.

http://prototypejs.org/2009/9/1/prototype-1-6-1-released

YAML Debug

2009-09-01T04:14:00.000-07:00

... an assistive tool for web developers, that allows you to quickly review code quality and semantic structure of any website (particularly those based on YAML) as well as testing it against common oversights.

This tool is not intended to be a reliable test environment for the accessibility of websites!

Supported Browsers

YAML Debug fully supports Firefox 3.x, Opera 9.x and Webkit browsers. There are some minor problems with Safari 3.x, which doesn't allow disabling imported style sheets.

There is only limited support for Internet Explorer 7 due to the fact that most highlighting features are based on CSS 2.1 selectors.

Get the Bookmarklet

Drag the following link to your favourites (or right-click and choose: «add to favourites» in the context menu)

YAML Debug

http://debug.yaml.de

CKEditor v3.0 - A Complete Rewrite of FCKeditor

2009-08-31T01:26:00.000-07:00

CKEditor is a Version 3.0 of FCKeditor. After almost two years of intensive development, the first stable version of CKEditor 3.0 has finally released.

CKEditor is a complete rewrite of our so loved FCKeditor, which got a bit old after six years of great success. Not to say that FCKeditor is doing bad, but there are some new things we could bring to it, and CKEditor is the result of it. There are dozens of new features in CKEditor.

CKEditor is fast to load and fast to use. The development team stayed focused to bring the best performance you can have, using all modern best practices. You’ll be amazed with it.

You’ll note that they have also a brand new UI based on the Kama skin. Other than modern, Kama is colorful like a chameleon, so you can precisely match its color to your needs. This is an innovative and unique feature you’ll find in CKEditor only.

The CKEditor code is also much different now. It’s up to date with the new JavaScript development requirements, offering a rich and powerful integration and interaction API. The editor is totally plugin based, and it can be extended and modified in all senses to fit all needs.

Requirements: Internet Explorer, Mozilla Firefox, Google Chrome, Safari and Opera
Demo: http://ckeditor.com/demo
License: GPL, LGPL, MIT License

http://ckeditor.com
http://www.webappers.com/2009/08/26/ckeditor-v30-a-complete-rewrite-of-fckeditor/

Snow Leopard Upgrade

2009-08-31T00:56:00.000-07:00

RVM: Ruby Version Manager

2009-08-30T01:49:00.000-07:00

You want to try out all of the different ruby interpreters and versions including different patchlevels, but you don't want to break what's working for you now. No time to waste?

Use rvm. Easy installation and switching between available Ruby versions and runtimes, without messing up your current Ruby install! rvm also allows you to use multiple versions of ruby in separate terminals concurrently!

http://rvm.beginrescueend.com

httpeyes

2009-08-27T03:19:00.000-07:00

httpeyes is an application that will show the http headers sent and received by different applications on your Windows box. It is very similar to ieHTTPHeaders with the difference in that httpeyes is a standalone application that does not only work for Microsoft Internet Explorer. So if you want to have a look at those headers for Opera, Firefox, Google Chrome, Flock, Microsoft Internet Explorer or any other app for that matter, just fire up httpeyes and look.

This is a first beta relase. It is currently not feature rich, but what is in there should both work and perform well. Please feel free to contact me if you have issues or would like to request a feature to be implemented.

http://www.blunck.se/httpeyes/httpeyes.html

Building a Video Portal in Rails

2009-08-26T23:51:00.000-07:00

http://blog.envylabs.com/2009/08/building-a-video-portal-in-rails/