Skip to main content

Home/ Groups/ Agency Oasis Developers
1More

arbor.js - 0 views

  •  
    a graph visualization library using web workers and jQuery
1More

Google Code Blog: Google URL Shortener gets an API - 0 views

  •  
    goo.gl API
1More

Subversion Hosting, Git Hosting, Project Management - 0 views

shared by Mark Ursino on 17 Jan 11 - Cached
  •  
    Hosted SVN, including free personal option
1More

HTML5 Video Player | VideoJS - 0 views

shared by Mark Ursino on 17 Jan 11 - Cached
  •  
    - Free & Open Source - Lightweight. NO IMAGES USED - 100% skinnable using CSS - Library independent - Easy to use - Easy to understand & extend - Consistent look between browsers - Full Screen & Full Window Modes - Volume Control - Forced fallback to Flash (even when there is an unsupported source)
1More

Microsoft Web Farm Framework 2.0 - 0 views

  •  
    A new version of the Web Farm Framework
1More

The-M-Project - 0 views

  •  
    Cross-platform mobile apps JS framework
1More

jRating - 0 views

  •  
    very flexible jQuery plugin for quickly creating an Ajaxed star rating system
1More

Simple Serialization - 0 views

  •  
    "Simple Serialization"
1More

XML serialization of read only properties « Coffee => Coder => Code - 0 views

  •  
    "XML serialization of read only properties"
1More

http is deprecated. - 0 views

shared by Mark Ursino on 29 Jan 11 - Cached
  •  
    By default, all popular Web browsers assume the HTTP protocol. In doing so, the software prepends the 'http://' onto the requested URL and automatically connect to the HTTP server on port 80. Why then do many pages explictly set http on all hypertext links? Surely it is easier to type "domain.com" than "http://domain.com". HTTP is also deprecated due to the ever-evolving web: The HyperText Transfer Protocol is no longer used to transfer hypertext. It is increasingly becoming used a means to transfer any content over port 80. Thus the definition "http" no longer means anything in the context of a URL since you are unlikely to be requesting hypertext. As the web evolves, next generation protocols will begin to replace http. By explicitly using "http://domain.com" in your links you are forcing your viewers of the future into using an obsolete protocol. By using "//domain.com" you will guarantee the protocol of tomorrow will work with your pages of today. Succinctly, use of the http protocol is redundant and time consuming to communicate. The internet, media, and society are all better off without it.
1More

The protocol-relative URL - 0 views

  •  
    Remove the protocol from absolute references to respect the current protocol
1More

HTML-Ipsum - 0 views

shared by Mark Ursino on 31 Jan 11 - Cached
  •  
    One-click copy to clipboard access to Lorem Ipsum text that comes wrapped in a variety of HTML.
1More

Fixed Footer - 0 views

  •  
    HTML/CSS for Fixed Footer (and comments for IE6 issues)
1More

F D C C - 0 views

  •  
    "Federal Desktop Core Configuration FDCC"
1More

Web Deployment: Web.Config Transformation - 0 views

  •  
    Mimic multiple web.config with web.config transformations
1More

Sending agents - Sitecore - 0 views

  •  
    Details about web.config agents and passing in method parameters and defining class properties
1More

Calling Cross Domain Web Services in AJAX - 0 views

  •  
    "Calling Cross Domain Web Services in AJAX"
1More

JavaScript Developer Center : Use a Web Proxy for Cross-Domain XMLHttpRequest Calls - YDN - 0 views

  •  
    "JavaScript: Use a Web Proxy for Cross-Domain XMLHttpRequest Calls"
1More

Cross-Domain Proxy - Ajax Patterns - 0 views

  •  
    "Cross-Domain Proxy"
1More

Cross-domain communications with JSONP, Part 1: Combine JSONP and jQuery to quickly bui... - 0 views

  •  
    "Cross-domain communications with JSONP"
« First ‹ Previous 441 - 460 Next › Last »
Showing 20 items per page