readme中的最后一段为什么没有翻译呢?

Tips: This project is not an official.This project collect some documents about HarmonyOS in the Internet.This is not a commercial project.This project just introduce HarmonyOS and all documents and codes come from Internet.If you use this project for business or something about make money, or in the event of any disputes arising from the usage of, or in connection with t

The input system usually includes a mouse and a key-board, while the output system usually consists of a monitor that can display a large mount amount of pixels.

Is your feature request related to a problem? Please describe.

more documentation and tutorial about how can be used
Describe the solution you'd like

video tutorials
**Describe alternatives you've consider

When opening a manual page the Help app sets the window title based on the currently selected tree view node, not the actual manual page path passed to the open_page function. This causes incorrect window titles when following hyperlinks in the document or navigating through the history.

If I rattle on the keyboard I get ControlLeft coming up regularly, even though I am far from the control keys. Upgrading pc_keyboard to 0.5.0 seems to fix it.

The vagrant box does not support vmware; it only supports virtualbox.

If a different box is chosen, then either vagrant provider can be used.

For instance, this is the error that I get (since I do not have virtualbox installed):

$ vagrant up
Bringing machine 'IncludeOS' up with 'vmware_desktop' provider...
==> IncludeOS: Box 'ubuntu/bionic64' could not be found. Attempting to find 

While we're coming up with a policy in the dark sanctuary of the gitter room, we'd still like input on what people think we should decide here.

Right now, we're leaning towards mostly ignoring possible issues involving spectre, but allowing users to run untrusted code inside a hardware-protection domain, similar to singularity.

As noted in #1452, SPI is a bit of an outlier in not including a buffer size in the capsule.

OS creates many virtual network interfaces if there is virtualization installed and running like Hyper-V or VirtualBox. If we can get which network interface is a real physical device it will be helpful for real device detection. As an example, the following is printed by SystemInfoText.java when run on one of our windows laptop. eth2 and wlan0 are physical network interfaces however there are hyp

• To the JTAG fritzing wiring image, add a red dot indicating the LED on the Olimex HW for easier orientation
• OpenOCD spews lots of errors while debugging. Check if they are harmless or can be fixed.
• CPSR in GDB seems to show wrong EL. Maybe other fields as well?
• Build GDB from source in the Docker container to be more bleeding edge regarding Rust support?
• The rea

Following should be mapped in uncached or at least write back marked pages to decrease latency

• VBE

Note: need to complete this list

In-place relocation is convenient for assembly programmers but a more robust solution would be the traditional relocation tables found in other executable formats like ELF. Adding this would be convenient for C programs as well and would help us simplify the compiler.

1. Add a new KEXC header which points to a relocation table, simply a list of program-relative addresses at which additional pro

Not strictly a requirement for a bootable disk, but we've now got 6 GO9P* scripts with a lot of similar code, and 2 have been added while working on image creation. (There are other files in util/ that look related too...)

We should consolidate them all into a single .go script with sensible args.

I've found that a clean install of Fedora 30 is pretty lacking when it comes to building the project. I'm using this issue to document all of the packages I need to install as I work towards a build. Going forward it may make sense to create a nix or guix configuration, or perhaps split the custom components into their own repositories with clear documentation.

Packages:
llvm-devel
pcre-devel

The Slax URL which explains the boot internals is here:

https://www.slax.org/internals.php

The corresponding URL in the tutorials should be updated. Also, the websites should be updated (put the new tutorial document) as well in order to reflect this change.