-
Notifications
You must be signed in to change notification settings - Fork 74
Make DB not dependent on jquery-ui generating a build #146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…ion (default: ".custom")
- also rename release -> jquery-ui;
- rename Builder#writeTo to Builder#zipTo;
…tiate themeGallery
…iles not included)
…ass, show, switchClass, toggle, and toggleClass demos
…eClass, show, switchClass, toggle, and toggleClass demos are included when effect core is
… on selected components
- Add ';' separator between copyright and licenses, eg. "Copyright 2013 jQuery Foundation and other contributors; Licensed MIT"; - Add a line break between banner and code; - Add `jquery.ui.theme.css` in the includes list of bundle css'es (it was missing);
- Unbinds ThemeRoller from JqueryUi.find(), ie. from the prepared files of the config file. Therefore, it can be used independently;
… cleaner add( src, dst ) -> add( src, dst, [ data ] )
…nd its manifest files
…y methods and inlining it
… chaining more straightforward - Along with related changes, builder helper add method changed as below: add( src, dst, [ data ] ) -> add( file ) or add( src, data )
@scottgonzalez @jzaefferer some commits for your appreciation :) |
} | ||
}); | ||
|
||
module.exports = Files; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried not to use proto (which is a non-standard). But, in my alternatives, length doesn't work properly, and therefore .map, .forEach, .concat, ... don't work properly too.
We need to check whether we are ok using this code, knowing we only use it in a controlled environment. After all, the above code works like a charm. :)
I've talked with @rwldrn and I learned ES6 will have a smarter object initialization. On ES5, it is not possible to subclass a built-in. But, ES6 will eventually make it possible.
I wonder if we can leave a TODO note above stating that as soon as our env supports ES6, we rewrite it in the proper way OR we use an alternative code that isn't too much complex.
- JqueryUiFiles_<version> inherit from JqueryUiFiles;
…variable instead (fix).
], function( err ) { | ||
// Make grunt to quit properly. Here, a proper error message should have been printed already. | ||
// 1: true on success, false on error | ||
done( !err /* 1 */ ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
remove comment
Closed by 84b5074 |
Summary: (the goal)
@VERSION
variable, etc) by our own. This is: drop requirement to prepare the jquery-ui files by running itsbuild
, andrelease
tasks. (Obs: DB still requires to prepare the jquery-ui files running itsmanifest
task.)Tests: (making sure this PR is good)
npm test
, of course. Actually, they pass in each commit separately.grunt generate_themes
andgrunt release_themes
passes.grunt build-download build-packages
needs a slight change PR Grunt: Change db path fromrelease
tojquery-ui
jqueryui.com#55.Changes: (the details)
release
path forjquery-ui
), so we don't make confusion with the release procedure.into()
, andrename()
).Related PRs
release
tojquery-ui
jqueryui.com#55