-
Notifications
You must be signed in to change notification settings - Fork 74
RFC - simplify UI package? #207
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
Comments
What exactly will be in the docs directory? There are no docs in either the ui or mobile repos currently. |
|
A little simplification would be nice. Do we really need to have the minified files in the development bundle dir? Either you use the minified, merged files (in js and css) or you building your own packed files from the non minified files. |
I agree @fnagel, if we can make |
Do we need the version numbers in the files in the css and js folders? I'd prefer to get rid of them, since that makes it easier to copy over the files into a project. Assuming the reason for having those was the same for having the version in our copy of As for "shallow copy of the source repository": Would that include all widgets? Or still be filtered down to the selected ones? We should have a useful readme file in the root, as suggested in #158. As for the list of question that aren't answered yet by your suggested approach:
We could add it to the
Same here, the bundle should be in the |
👍
I'm in favor of no special manipulation, but including all widgets as they are. I don't know why we include the development-bundles files in the download package. But, I assume it's there to give users the original source files, so they can run their own build scripts or do whatever customizations they want to on them. Following that line of thought, I assume including them as they are without filtering or without any manipulation makes no hurt. Actually, it makes it even more reliable.
It's already in the js folder. My question regards to development-bundle. On jQuery UI source (aka development-bundle), we have all dependencies (third libraries) under external except for jquery.js. Why? This is what I am asking... Changes to that should occur on https://github.com/jquery/jquery-ui/ not in Download Builder.
👍 |
At this point, I'm actually in favor of reducing this down to just jquery.js, jquery-ui.js, jquery-ui.min.js, jquery-ui.css, jquery-ui.min.css, and theme images. If you want individual files you can use Bower, clone the repo, or use GitHub releases. If you want docs, use api.jqueryui.com. We should figure out a good offline docs solution separate from download builder and have it available for all API sites. i18n bundles are kinda pointless; I don't think anybody would ever want to load all locales. i18n files won't be included in the repo in the future anyway, so dropping them now seems fine. If you want third party plugins, you should go through the third party or a package manager like Bower. |
Wonderful On Monday, May 5, 2014, Scott González notifications@github.com wrote:
http://www.rafael.xavier.blog.br/+55 (16) 8138-1583, skype: rxaviers |
I'm in favor as well this is basically what mobile has right now |
Could we implement this for 1.11? |
I'm ok with that. I'd like to get another beta out this week. Do you think we could get the changes in time for that? |
Yeap, I think so. Will keep you updated via IRC. |
Everything else is resolved now, so this would be the only thing holding up the next beta. |
Welcome to the jQuery UI 1.11 download package:
There are 51 directories, and 690 files.
Questions
1) Which JavaScript bundle to use?
a.
js/jquery-ui-1.11.0.custom.js
b.
development-bundle/ui/jquery-ui.custom.js
Both are identical.
2) Which Style bundle to use?
a.
css/ui-lightness/jquery-ui-1.11.0.custom.css
b.
development-bundle/themes/base/jquery-ui.css
c.
development-bundle/themes/ui-lightness/jquery-ui.css
(a) and (c) are the structure + ui-lightness theme. (b) is the structure + base theme, ie. smoothness theme. Replace
ui-lightness
for custom-theme, no-theme, or a different named theme when appropriate.3) What's the difference between
development-bundle/themes/base/accordion.css
anddevelopment-bundle/themes/ui-lightness/accordion.css
?None. The same is valid for every single component css between both directories.
4) If I select a different set of UI components, do I need to regenerate my theme style?
No. You use the same theme style
<style-dir>/theme.css
for any component set you choose.5) Why isn't
jquery.js
with other third libraries inexternal
?Maybe, because jquery is the only unanimous dependency across every UI component? Note that Globalize and jquery.mousewheel.js are also dependencies of some components.
6) Why don't we expose i18n bundle in
js
?User may use
js/jquery-ui-1.11.0.custom.js
to get UI bundle. But, user needs to reachdevelopment-bundle/ui/i18n/jquery-ui-i18n.js
to get UI I18n bundle.7) Why do we place docs inside development-bundles?
Could we place it in the package's root for easier access?
8) Community has other questions on #158
Goal / Solution
Can we simplify our package?
Can we make
css
andjs
the main entries of the customizations? I mean: user will find customizable bundles in there.Can we simplify
development-bundle
as being a shallow copy of the source repository?Can we move
docs
into the package's root?The text was updated successfully, but these errors were encountered: