Activity (RSS)

The general consensus seems to be in favor of keeping the existing Class API due to performance concerns and compatibility with the Prototype API. Closing as in...

Add Spec unit tests for the ECMAScript 5 compatibility functions.

Add Spec unit tests for fuse.Class.

Create a QUnit-style UI for displaying the Spec test results.

Add Spec unit tests for fuse.Array.

Add Spec unit tests for fuse.Class.mixins.enumerable.

Add inline documentation for fuse.String in lang/string.js

Add inline documentation for fuse.RegExp in lang/regexp.js

Add inline documentation for fuse.Number in lang/number.js

Add inline documentation for fuse.Object in lang/object.js

Add inline documentation for fuse.Hash in lang/hash.js

1. Overview
   
   • The inline documentation efforts are going to allow us to generate API documentation. This is the first user story for documentation efforts over the...

An earlier documentation effort for fuse.Class.mixins.enumerable can be found @ https://github.com/jgornick/fusejs/blob/a1f8c6e9a6f05ae603b82db4408...

Add inline documentation for fuse.Class.mixins.enumerable in lang/enumerable.js

Add inline documentation for fuse.Function in lang/function.js

An earlier documentation effort for fuse.Array can be found @ https://github.com/jgornick/fusejs/blob/a1f8c6e9a6f05ae603b82db4408...

Add inline documentation for fuse.Array in lang/array.js

In order to complete the massive rework, we'll need to create some unit tests that also validate some of the new features in the massive rework:

• innerHTML upda...

We'll have to validate that after the massive rework commit that none of the variables used for FuseJS leak to the global namespace. If they do, then we will ne...

In order to get FuseJS to build after the initial rework commit, we'll need to do trial and error of building and finding new syntax errors. Track these down, b...

1. Overview
   
   • A commit was started back in October which contained a major rework of exposing FuseJS private methods for our emulation layer. This rework needs to ...

• Follow our source directory structure as it will be easier to map source to unit test
• Move all fixtures to root test directory
• We'll continue to need unit and ...

Since we are able to benchmark much better, there are some areas that we need to remove the micro-optimizations so we can shave off more kb on the built file.

Convert using String#split in favor of using RegEx#exec.

That's pretty cool. Maybe it could also support HSB(a), HSL(a).

var myColor = new Color('#ff0000');
myColor.toHsb(); // 'hsb(0%, 100%, 50%)'
myColor.deSaturate...

Special color object is a good idea.

I use something similar in fabric.js (http://github.com/kangax/fabric.js/blob/gh-pages/src/color.class.js) — fabric.Color c...

From minimal testing, getComputedStyle will automatically convert all values to rbg/rgba as a string.

I would suggest some sort of special color object, with all convert methods on it. This object should behave like string or something like it.

The idea of parsing colors means we always want to return a standard color format. We've talked about standardizing on HEX, however, with the addition of specif...

Committed @ http://github.com/jgornick/fusejs/commit/bdc3769b81a2e2ab6763628be6...

getClassNames will stay the same and not be renamed to getClass.

John-David and I decided to not allow a callback option but rather instead iterate through the list and apply the styles that way. However, the commit above inc...

I don't know what I was thinking here, but setStyle and getStyle both already support hyphenated and camelCased.

Initial commit can be found @ http://github.com/jgornick/fusejs/commit/6ffbd94313666154b0dbc47a7c...

Still need to write the callback approach.

Committed @ http://github.com/jgornick/fusejs/commit/6ffbd94313666154b0dbc47a7c...