Difference: 1. uniapp is a framework, and HTML is a markup language. 2. There are differences in components/labels; for example, p is changed to view, span and font are changed to text, a is changed to navigator, and img is changed to image. 3. Uniapp does not support DOM operations, but HTML does.
The operating environment of this tutorial: windows7 system, uni-app2.5.1&&HTML5 version, thinkpad t480 computer.
The difference between uni-app and HTML
##Changes in components/tags
It used to be an html tag, but now it is a mini program tag
p changed to view- span, font changed to text
- a was changed to navigator
- img was changed to image
- input is still there, but the type attribute was changed to confirmtype
- form, button, checkbox, radio, label, textarea, Canvas and video are still there.
- select is changed to picker
- iframe is changed to web-view
- ul and li are gone, use view instead
- audio is no longer recommended. Change to api mode, background audio api document
- In fact, old HTML tags can also be used in uni-app. The uni-app compiler will convert the old tags into new tags during compilation. However, this usage is not recommended. It is easy to get confused when debugging the H5 side, and there will also be problems with element-based selectors.
Recommended: "
uni-app Development Tutorial"
In addition to changes, a number of new components commonly used on mobile phones have been added
- scroll-view Area scrollable view container
- swiper Swipeable area view container
- icon icon
- rich-text rich text (cannot execute js, but can render various text formats and images)
- progress progress bar
- slider slider indicator
- switch switch selector
- camera camera
- live-player Live broadcast
- map map
- cover-view View container that can cover native componentscover-view needs to emphasize a few more words. The video, map, canvas, and textarea on the non-h5 side of uni-app are native components and are higher level than other components. If you need to cover native components, such as adding a mask to the map, you need to use the cover-view component
In addition to built-in components, there are many open source extension components that cover common operations. For encapsulation, DCloud has established a plug-in market to include these extension components. For details, please see the plug-in market
Changes in js
The running environment changes from the browser Cheng v8 engine
Standard js syntax and API are supported, such as if, for, settimeout, indexOf, etc.- But the browser-specific window, document, navigator, and location objects are only It is only available in browsers and is not supported by apps or mini-programs. This means that many HTML libraries that rely on document, such as jqurey, cannot be used. However, apps and small programs support web-view components, which can load standard HTML. This kind of page still supports browser-specific objects window, document, navigator, location
-
The previous dom operation was changed to vue The MVVM mode
alert,confirm is changed to uni.showmodel- ajax is changed to uni.request
- cookie and session are gone, local.storage is changed to uni .storage
- There are many js apis of uni-app, but they are basically the apis of small programs. Just change wx.xxx to uni.xxx
-
css changes
The selector has 2 changes: *The selector is not supported; there is no body in the element selector, changed to page- In terms of unit, px cannot dynamically adapt to screens of different widths, rem It can only be used for h5 and rpx can only be used for WeChat mini programs. For this purpose, uni-app has added upx, a dynamic unit that applies to all terminals and all screen widths upx
- uni-app recommends using flex layout, and the default is flex layout
-
For more programming-related knowledge, please visit:
programming video! !
The above is the detailed content of What is the difference between uniapp and HTML. For more information, please follow other related articles on the PHP Chinese website!
Statement:The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn