sorted by: recent | see :
popular
Content Tagged with future + JavaScript
Simplified Javascript: Cruft Reduced
Scripting
Programming
JavaScript
internet
parsing
future
languages
norah'# : nsIPrem と nsIContentPref
CouchDb - The future of web storage
John Resig - Future of Firefox and JavaScript
Future of Firefox and JavaScript
JSONRequest
JavaScript
xmlhttprequest
JSON
future
proposal
crockford
jsonrequest
OSCON 2007 - Steve Yegge
opensource: del.icio.us tag/opensource
presentation
JavaScript
video
business
opensource
future
marketing
OSCON 2007 - Steve Yegge
opensource: del.icio.us tag/opensource
Programming
JavaScript
Google
developers
opensource
future
marketing
Advogato: The browser wars are once again upon us
Flash
Programming
JavaScript
Web2.0
Interesting
technology
future
eyeOS Home | Web Desktop - Web OS - Web Office - your files and applications everywhere
open-source: del.icio.us tag/open-source
Ajax
PHP
JavaScript
open-source
future
webdeveloping
coolnessfactor5
Array Extras - only available in Firefox - New in JavaScript 1.6 - MDC
Firefox: del.icio.us/tag/firefox
Documentation
JavaScript
Firefox
future
array
foreach
javascript1.6
Ajaxian » Dojo Offline Toolkit Kicks Off
Shrinking Accordion Size
If you have been watching the current_build, you will have noticed that the accordion is getting smaller and smaller.
The original version from 1.1 was over 200 lines of js code. The first version we put into our partial 2.0 build was not much over 50 lines. The latest version consists of two methods with a single line of code each. This shrinkage of size is contributed to the behaviors that are being abstracted out to allow easier construction of custom components (btw, the latest version is better at managing nested contents on IE and Firefox).
As more content gets added to the 2.0 build, you will see more emphasis in these behaviors. We will be showing how to use these to build custom components as well as how the behaviors can be used on a page where a component might be too heavy handed.
Future Direction
I will be talking about the future direction for Rico over my next few posts. Here is what I plan on covering.
- Goals
- Rico’s Future With Other Javascript Libraries
- Upcoming Behaviors and Features
OK, lets start with the general goals.
Goal 1 - Stay out of the web developers way.
I think this is very important area that Rico can provide a lot of value. The integration with Rico should be simple and should not cause the developer to change their entire web app.
Goal 2 - Keep it simple.
This is a bit obvious, but I thought it to be worth repeating. I want to err on the side of being too simple of an interface and add those things that are really needed. Rico will focus on helping with the real needs. It will not try to be a kitchen sink.
Goal 3 - Pleasure to use.
The developer should have both a joyful and yet brief usage of Rico. It should not take long to get the desired behaviors and yet should be a joy
to work with.
Goal 4 - Should work well with the simplest of technologies.
Rico should not try to replace the act of creating html and css. It should simply enhance the experience.
Goal 5 - Should be easy to expand.
This is an area that 1.1 is a bit weak in. The library should be simpler to expand without having to rip and tear.
Goal 6 - Should be inovative.
Well duh… However, I really feel that there is a lot of value for Rico to be a platform for exploring rich interaction øf content on the web. It will not be ‘just another widget library’ duplicating the desktop. Rico will continue to have unique behaviors that will push the envelope.
Goal 7 - Should complement not compete.
This should be evident based on the other goals, but I think it is worth repeating.
