1
0
Fork 0
Commit Graph

791 Commits (2adcf8bb0e9f18ac97422fa9c579b3965c4ba063)

Author SHA1 Message Date
Mike Gerwitz 2adcf8bb0e Added verset
After dealing with autoconf, I may decide not to implement it. The build process
is fairly simple as it is and I do not want to over-complicate it. verset solves
one of the issues that autconf would have aided in addressing - setting a
version number.
2012-03-05 22:54:12 -05:00
Mike Gerwitz 22005e396e Added missing closing parenthesis in Visibility Object Implementation section of manual 2012-01-19 23:25:47 -05:00
Mike Gerwitz 0ceffe2146 Visibility Object Implementation doc correction 2012-01-19 23:24:56 -05:00
Mike Gerwitz fa9dbcbf2e [Fix #37] constructor property now properly set on instances 2012-01-19 23:21:04 -05:00
Mike Gerwitz 9dbd0d1fb3 Added constructor property to reserved members list 2012-01-17 23:36:01 -05:00
Mike Gerwitz 958521f673 Created version module to provide additional version information 2011-12-23 18:31:11 -05:00
Mike Gerwitz 4627958247 Updated version in documentation and package.json to v0.1.0
- We are nearly there. Happy holidays and happy new year from ease.js ;)
2011-12-23 00:09:11 -05:00
Mike Gerwitz cdbcada4d2 Copyright year update 2011-12-23 00:09:11 -05:00
Mike Gerwitz f264c1bf63 Added version number to exports 2011-12-23 00:03:08 -05:00
Mike Gerwitz 0dca143bdd Added {Abstract,Final}Class to index test 2011-12-23 00:03:08 -05:00
Mike Gerwitz bc22a9be27 Added reduced license header for minified files and updated copyright 2011-12-22 23:49:53 -05:00
Mike Gerwitz 0739f983c7 Quoting keyword for consistency and to avoid potential minification issues 2011-12-22 23:40:39 -05:00
Mike Gerwitz 05ad90e7f7 Updated README.md to remove npm unavailibility mention
- I had added the project to npm to reserve the name. Besides, the release is soon enough.
2011-12-22 23:36:15 -05:00
Mike Gerwitz 17047b53e9 Getters/setters will now trigger warnings if attempting to override without super getter/setter 2011-12-22 23:36:15 -05:00
Mike Gerwitz bcb0bcbe80 Added static validations for getters/setters 2011-12-22 23:36:15 -05:00
Mike Gerwitz db84c6fc6e Added virtual and override restrictions to getters/setters 2011-12-22 23:36:12 -05:00
Mike Gerwitz 9942ac9743 const getters/setters are unsupported (simply omit the setter) 2011-12-22 22:48:17 -05:00
Mike Gerwitz 4ada84e3b7 Abstract getters/setters are not yet supported
- Perhaps in future versions. The implementation details will not be ironed out before v0.1.0 and we can easily add it in the future without breaking BC. Getters/setters have not had too much attention thusfar in ease.js due to testing with systems that must work across many environments, including pre-ES5.
2011-12-22 22:46:02 -05:00
Mike Gerwitz 6295b83ec7 util.clone() primitive fix (broken in recent commit)
- null is considered to be type "object" by instanceof
2011-12-22 09:37:34 -05:00
Mike Gerwitz 021b67bbff Whoops - abstract member param names may now contain underscores 2011-12-22 09:10:51 -05:00
Mike Gerwitz ac837107c5 Corrected terms in Abstract Members section of documentation
- "Parameters" instead of "arguments"
- "Declaration", not "definition"
2011-12-21 20:13:42 -05:00
Mike Gerwitz a10cf82a12 Abstract member declaration parameter name restrictions now apply to all abstract member declarations, not just interfaces 2011-12-21 20:12:05 -05:00
Mike Gerwitz 50904390da Interface members may now only contain arg names that are valid var names
- This should apply to all abstract definitions. This will be resolved in the next commit. I am tired.
2011-12-20 23:56:46 -05:00
Mike Gerwitz e9cf630d0b AbstractClass.implement().extend() will now properly preserve abstract flag on resulting class
- This is a bug fix. The resulting class was not declared abstract, which is a problem if the resulting class chose not to provide a concrete implementation for each of the abstract members.
2011-12-20 20:06:38 -05:00
Mike Gerwitz 2136ebedd5 Now properly handling extending from objects and properly throwing errors for scalars 2011-12-15 22:58:33 -05:00
Mike Gerwitz d5ef3eb221 Minor documentation correction (>= to >) 2011-12-15 21:21:46 -05:00
Mike Gerwitz 4479ea84af Ignoring webroot
- May be left over from switching branches
2011-12-15 19:20:56 -05:00
Mike Gerwitz 9117b2e4cf Updated package.json to remove deps and correct license
Growing much closer to releasing. Hopefully in the next couple of days; I just
don't want to rush it. Though, at the same time, I've been noticing projects
popping up with very similar / exact names to this one. A project named "ease"
was added to the npm repository and another "ease.js" is on GitHub, although
it's made no progress. As such, I want to ensure I reserve the name in npm.

I've been testing the new library and work and noticed only a couple minor
issues, primiarly due to misuse of the library. Looking good.
2011-12-13 22:03:55 -05:00
Mike Gerwitz e24784529e Resolved majority of Closure Compiler warnings (VERBOSE)
- Ignored warnings from tests for now
- VERBOSE flag removed from Makefile for now until I can figure out how to
  resolve certain warnings
2011-12-13 21:19:14 -05:00
Mike Gerwitz 3922d6874e Added mkexterns for internal externs (see comments within file for information as to why this is necessary) 2011-12-10 16:46:14 -05:00
Mike Gerwitz d1b1d2691a Fixed initial warnings provided by Closure Compiler
Getting ready for release means that we need to rest assured that everything is
operating as it should. Tests do an excellent job at aiding in this, but they
cannot cover everything. For example, a simple missing comma in a variable
declaration list could have terrible, global consequences.
2011-12-10 11:18:41 -05:00
Mike Gerwitz 45f3d62727 Removing toString() call on failAssertion(); string may be passed 2011-12-07 23:14:15 -05:00
Mike Gerwitz e0254f6441 Removed invalid @package tags
Not a valid tag in jsdoc
2011-12-06 20:19:31 -05:00
Mike Gerwitz 66fd2ece83 Switched to Closure Compiler
This is nothing against uglify. Rather, here's the story on this:

Commit e4cd1e fixed an error that was causing minified files to break in IE.
This was due to how IE interprets things, not how UglifyJS was minifying them.
Indeed, Closure Compiler had the exact same problem.

The decision to move to Closure Compiler was due to a variety of factors, which
came down to primarily feature set and tests. Closure Compiler is well tested
and maintained. It also includes a number of additional, beneficial features.
UglifyJS is an excellent project and I would recommend it to anyone, but it is
not tested (no unit tests; it's tested by ensuring common libraries like jQuery
run after minification). It is, however, significantly faster.

It's likely that, in the future, once I add autoconf for the build process to
configure certain settings, that I will add UglifyJS as an option. I'm sure many
people would prefer that, especially those who dislike Java and do not wish to
have it installed. Hopefully those that do decide to install Java will go with
openjdk, not Oracle's proprietary implementation.
2011-12-06 18:28:58 -05:00
Mike Gerwitz 58f2e3afc4 Made necessary changes to tests to prevent Closure Compiler from optimizing them away, causing test failures 2011-12-06 18:28:16 -05:00
Mike Gerwitz a18dedbddb Added missing client-side "fail" assertion 2011-12-06 18:27:41 -05:00
Mike Gerwitz e385a9c8fb MemberBuilderValidator tests now properly wrap certain functions (they were working, but let's be safe) 2011-12-06 18:27:20 -05:00
Mike Gerwitz e4cd1eabe5 Fixed issue with minified files in IE
Ah - you have to love those "ah-ha!" moments. The issue here is that both
uglify-js and closure compiler mangled the names in such a way that the var and
the function name had different values. In the case of closure compiler, the
function name was used to instantiate the constructor if the 'new' keyword was
omitted. This worked fine in all other tested browsers, but IE handles it
differently.
2011-12-06 18:20:43 -05:00
Mike Gerwitz 74dd239de0 Corrected errors/warnings as indicated by Google Closure compiler 2011-12-04 19:26:53 -05:00
Mike Gerwitz f39fc05ae2 test/inc-*.js files will now be recognized by make to rebuild combined file 2011-12-04 19:13:51 -05:00
Mike Gerwitz e86ed63fd8 Fixed trailing comma issue in test
- Caused problems in IE6
- Comma stripping script did not catch it due to trailing comments
2011-12-04 13:06:28 -05:00
Mike Gerwitz 1a3b5f2893 Now using vm module in node instead of process.binding.Script (deprecated in newer versions of node) 2011-12-04 12:55:00 -05:00
Mike Gerwitz 27eea93d6f Now setting mocked console in warn module for tests
- Replacing console broken in newer versions of node/v8
- Replacing console.warn/log works fine, but is a poor choice for testing
2011-12-04 12:54:56 -05:00
Mike Gerwitz 0f4ce6acc1 Warning test workaround for FF
- Note that warnings do work properly in practice in FF
2011-12-04 11:38:24 -05:00
Mike Gerwitz 446aa8d413 Fixed __self assignment for FF
This little experience was rather frustrating. Indeed, it would imply that
the static implementation (at least, accessing protected and private static
members) was always broken in FF. I should be a bit more diligent in my testing.
Or perhaps it broke in a more recent version of FF, which is more likely. The
problem seems to be that we used defineSecureProp() for an assignment to the
actual class, then later properly assigned it to class.___$$svis$$.
Of course, defineSecureProp() makes it read-only, so this failed, causing
an improper assignment for __self, breaking the implementation. As such,
this probably broke in newer versions of FF and worked properly in older versions.

More concerningly is that the implementations clearly differ between Chromium
and Firefox. It may be that Firefox checks the prototype chain, whereas Chromium
(v8, specifically) will simply write to that object, ignoring that the property
further down the prototype chain is read-only.
2011-12-04 00:32:16 -05:00
Mike Gerwitz f2e0bbc2f6 Outputting stack trace in browser tests if available 2011-12-03 15:51:53 -05:00
Mike Gerwitz 599f100cfa Added browser-test-min.html 2011-12-03 12:56:37 -05:00
Mike Gerwitz 075e73e4d1 [#5] Added private naming conflict mention and inheritance information to Inheritance section of manual 2011-12-03 12:26:03 -05:00
Mike Gerwitz e41495c0d1 Added private member name conflict validations 2011-12-03 00:38:41 -05:00
Mike Gerwitz 50da560c1f [#5] Added pre-es5 fallback section to visibility object implementation 2011-11-29 21:07:24 -05:00