Использование: JQuery включается в веб-страницу как один внешний JavaScript-файл: <script></script>. Существует два вида вызова методов jQuery: через функции. Подробное описание о том как подключать jQuery Google. Лучше всего использовать jQuery CDN возможность. JQuery.animate и css transform. 22:24:00 28.01.2011 Комментарии: 1. Похожие записи. Работа с массивами в jquery.Git. Hub - jquery/jquery: j. Query Java. Script Library. Contribution Guides. In the spirit of open source software development, j. Query always encourages community code contribution. JavaScript jQuery:;[. М. Э, 2015. Äýâèä Ìàêôàðëàíä. Javascript è jquery èñ×åðïûâàþùåå ðóêîâîäñòâî. С помощью нашего учебника Вы можете изучить популярную библиотеку jQuery в сжатые сроки. В нем Вы также найдете примеры и упражнения, . JQuery UI Datepicker — добавление возможности выбора нескольких дат на Статья посвящена jQuery UI и его виджету выбора дат. JQuery JavaScript Library. Contribute to jquery development by creating an account on GitHub. Click on the "Try it Yourself" button to see how it works. jQuery Examples. Learn by examples! At W3Schools you will find a lot of jQuery examples to edit and test . To help you get started and before you jump into writing code, be sure to read these important contribution guidelines thoroughly: Getting Involved. Core Style Guide. Writing Code for j. Query Foundation Projects. Environments in which to use j. Query. Browser supportj. Query also supports Node, browser extensions, and other non- browser environments. What you need to build your own j. Query. In order to build j. Query, you need to have the latest Node. Earlier versions might work, but are not supported. For Windows, you have to download and install git and Node. OS X users should install Homebrew. Once Homebrew is installed, run brew install git to install git. Node. js. Linux/BSD users should use their appropriate package managers to install git and Node. По этой причине функция getJSON() определена как метод глобального объекта jQuery (единственный объект с именем jQuery, или $, определяемый библиотекой jQuery). Перед вами онлайн учебник по jQuery. jQuery — библиотека JavaScript, фокусирующаяся на взаимодействии JavaScript и HTML.. Easy- peasy. How to build your own j. Query. Clone a copy of the main j. Query git repo by running: git clone git: //github. Enter the jquery directory and run the build script: cd jquery & & npm run build. The built version of j. Query will be put in the dist/ subdirectory, along with the minified copy and associated map file. If you want to create custom build or help with j. Query development, it would be better to install grunt command line interface as a global package: npm install - g grunt- cli. Make sure you have grunt installed by testing: grunt - V. Now by running the grunt command, in the jquery directory, you can build a full version of j. Query, just like with an npm run build command: grunt. There are many other tasks available for j. Query Core: grunt - help. Modules. Special builds can be created that exclude subsets of j. Query functionality. This allows for smaller custom builds when the builder is certain that those parts of j. Query are not being used. For example, an app that only used JSONP for $. Any module may be excluded except for core, and selector. To exclude a module, pass its path relative to the src folder (without the . Some example modules that can be excluded are: ajax: All AJAX functionality: $. Setup(), . load(), transports, and ajax event shorthands such as . Start(). ajax/xhr: The XMLHTTPRequest AJAX transport only. The < script> AJAX transport only; used to retrieve scripts. The JSONP AJAX transport only; depends on the ajax/script transport. The . css() method. Also removes all modules depending on css (including effects, dimensions, and offset). Hide: Non- animated . Also removes the effects module. Methods documented as deprecated but not yet removed. The . width() and . The . animate() method and its shorthands such as . Up() or . hide("slow"). The . on() and . off() methods and all event functionality. Also removes event/alias. All event attaching/triggering shorthands like . Cross- browser support for the focusin and focusout events. The . trigger() and . Handler() methods. Used by alias and focusin modules. The . offset(), . Parent(), . scroll. Left(), and . scroll. Top() methods. wrap: The . All(), . wrap. Inner(), and . Exclude the ready module if you place your scripts at the end of the body. Any ready callbacks bound with j. Query() will simply be called immediately. However, j. Query(document). Exclude j. Query. Deferred. This also removes j. Query. Callbacks. Note that modules that depend on j. Query. Deferred(AJAX, effects, core/ready) will not be removed and will still expect j. Query. Deferred to be there. Include your own j. Query. Deferred implementation or exclude those modules as well (grunt custom: -deferred,- ajax,- effects,- core/ready). Exclude the attachment of global j. Query variables ($ and j. Query) to the window. Exclude the AMD definition. As a special case, you may also replace Sizzle by using a special flag grunt custom: -sizzle. The Sizzle selector engine. When this module is excluded, it is replaced by a rudimentary selector engine based on the browser's query. Selector. All method that does not support j. Query selector extensions or enhanced semantics. See the selector- native. Note: Excluding Sizzle will also exclude all j. Query selector extensions (such as effects/animated. Selector and css/hidden. Visible. Selectors). The build process shows a message for each dependent module it excludes or includes. AMD name. As an option, you can set the module name for j. Query's AMD definition. By default, it is set to "jquery", which plays nicely with plugins and third- party libraries, but there may be cases where you'd like to change this. Simply set the "amd" option: grunt custom - -amd="custom- name"Or, to define anonymously, set the name to an empty string. Custom Build Examples. To create a custom build, first check out the version: git pull; git checkout VERSIONWhere VERSION is the version you want to customize. Then, make sure all Node dependencies are installed: Create the custom build using the grunt custom option, listing the modules to be excluded. Exclude all ajax functionality: Excluding css removes modules depending on CSS: effects, offset, dimensions. Exclude a bunch of modules: grunt custom: -ajax,- css,- deprecated,- dimensions,- effects,- event/alias,- offset,- wrap. For questions or requests regarding custom builds, please start a thread on the Developing j. Query Core section of the forum. Due to the combinatorics and custom nature of these builds, they are not regularly tested in j. Query's unit test process. The non- Sizzle selector engine currently does not pass unit tests because it is missing too much essential functionality. Running the Unit Tests. Make sure you have the necessary dependencies: Start grunt watch or npm start to auto- build j. Query as you work: Run the unit tests with a local server that supports PHP. Ensure that you run the site from the root directory, not the "test" directory. No database is required. Pre- configured php local servers are available for Windows and Mac. Here are some options: Building to a different directory. To copy the built j. Query files from /dist to another directory: grunt & & grunt dist: /path/to/special/location/With this example, the output files would be: /path/to/special/location/jquery. To add a permanent copy destination, create a file in dist/ called ". Inside the file, paste and customize the following: {. Absolute/path/to/other/destination": true. Additionally, both methods can be combined. Essential Git. As the source code is handled by the Git version control system, it's useful to know some features used. Cleaning. If you want to purge your working directory back to the status of upstream, the following commands can be used (remember everything you've worked on is gone after these): git reset - -hard upstream/master. Rebasing. For feature/topic branches, you should always use the - -rebase flag to git pull, or if you are usually handling many temporary "to be in a github pull request" branches, run the following to automate this: git config branch. Handling merge conflicts. If you're getting merge conflicts when merging, instead of editing the conflicted files manually, you can use the feature. Even though the default tool xxdiff looks awful/old, it's rather useful. The following are some commands that can be used there: Ctrl + Alt + M - automerge as much as possibleb - jump to next merge conflicts - change the order of the conflicted linesu - undo a mergeleft mouse button - mark a block to be the winnermiddle mouse button - mark a line to be the winner. Ctrl + S - save. Ctrl + Q - quit. Test methodsexpect( num. Assertions ). start(); Note: QUnit's eventual addition of an argument to stop/start is ignored in this test suite so that start and stop can be passed as callbacks without worrying about their parameters. Test assertionsok( value, [message] ). Equal( actual, expected, [message] ). Equal( actual, expected, [message] ). Deep. Equal( actual, expected, [message] ). Equal( actual, expected, [message] ). Strict. Equal( actual, expected, [message] ). Test Suite Convenience Methods Reference (See test/data/testinit. Returns an array of elements with the given IDs. Example: q("main", "foo", "bar"). Asserts that a selection matches the given IDst( test. Name, selector, [ "array", "of", "ids" ] ); Example: t("Check for something", "//[a]", ["foo", "bar"]); Fires a native DOM event without going through j. Queryfire. Native( node, event. Type )Example: fire. Native( j. Query("#elem")[0], "click" ); Add random number to url to stop caching. Example: url("data/test. Run tests in an iframe. Some tests may require a document other than the standard test fixture, and. The actual test code and assertions. Query's main test files; only the minimal test fixture markup. Iframe( test. Name, file. Name. functiontest. Callback(. assert, j. Query, window, document. This loads a page, constructing a url with file. Name "./data/" + file. Name. The iframed page determines when the callback occurs in the test by. Test. js" script and calling. Iframe. Test( [ additional args ] ) when appropriate. Often this. will be after either document ready or window. The test. Callback receives the QUnit assert object created by test. Iframe. for this test, followed by the global j. Query, window, and document from. If the iframe code passes any arguments to start. Iframe. Test. they follow the document argument. Questions? If you have any questions, please feel free to ask on the. Developing j. Query Core forum or in #jquery on irc.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |