With the Helper specification, We can "pile up" a database based on it.
Qwrap In which helper or util? The following table lists the main tables.
Moduleh |
Core/module. H. js |
For module Management |
Stringh |
Core/string. H. js |
For strings |
Objecth |
Core/object. H. js |
For JSON or any type of objects or values |
Arrayh |
Core/array. H. js |
For arrays |
Dateh |
Core/date. H. js |
For date |
Functionh |
Core/function. H. js |
For functions |
Classh |
Core/class. H. js |
For Class (class) |
Helperh |
Core/helper. H. js |
For Helper Objects |
Domu |
DOM/DOM. U. js |
Some dom-related methods, the first parameter is not targeted |
Nodeh |
DOM/node. H. js |
Target Element |
Eventh |
DOM/event. H. js |
Native event for browsers |
Eventtargeth |
DOM/eventtarget. H. js |
Targeting browser event carriers |
The qwrap trunk (that is, the core/core_base.js defining the QW root namespace) and the Helper are a big function library.
All the methods in it are static functions, which constitute the basic static compaction library of qwrap.
When building this database, you only need to pursue standards and rigor, rather than thinking too much about how to make it easier for users to call.
The whole building process is a bit mechanical, but there are also many bright spots in it. If you are interested, you can view them.Code.
Some helper will be selected later for some introduction.