Shulou(Shulou.com)06/02 Report--

This article mainly explains "how to install chrome on tinycolinux". The content in the article is simple and clear, easy to learn and understand. Please follow the editor's train of thought to study and learn "how to install chrome on tinycolinux".

An APP is always composed of UI, middleware, and business logic components, but only UI is sufficient to divide an appstack, because UI is a necessary part of APP, even console has TUI. Nowadays we see two main kinds of UI, native GUI released with OS, and WEBPAGE GUI developed with webapp, but in fact, VNC is also a special GUI for remote control. Hardware accelerated GL,DX is also a kind of UI, which is the GUI of game APP. In a nutshell, as long as it mixes other stack elements to form a development and release unit, it can actually be a kind of UI (you can see that project templates in language libraries and large IDE are often organized by appstack and UI types), but in technical implementation, because WEB's UI is often something of a HTML rendering engine. So it is actually an advanced UI based on native UI, but, in any case, it is possible for an OS to use some kind of advanced UI to build a complete APP ecology, and if there is such an OS, then it can legally be called the OS of that UI.

Chromeos,webos is this kind of thing, it shows that webpage uses appmodel to complete web appstack for webapp, users can complete the entire application with a single chrome (of course, webgame is two things compared to hardware-accelerated native cg game), administrators can use chrome to complete maintenance tasks, and developers can develop web programs for browser. Chromeos is a linux system core + webkit UI composed of all available ecology (desktop SHELL,AUI, tools, APP..), if there is no need to play large 3D games in this kind of OS (and there is already a solution like webgl,websocket,html5), it is actually something that is good enough and can be extended to any business areas occupied by native UI and native appstack.

In fact, the linux macro kernel is designed to be released for diversification. It can even per app os. Chrome as os desktop all and AUI is actually reasonable, it can match the mineportal demos mentioned at the end of the article to create an oc-specific enhanced os.

All right, now let's install the GUI environment on tinycolinux, based on this native UI. In fact, our ultimate goal is not that. We are going to install chrome, turn it into something like chrome os, and eventually develop tinycolinux into a dedicated OS for webui and webapp.

Install the x environment on tinycolinux

According to the choice of xvesa and xorg for http://wiki.tinycorelinux.net/wiki:adding_a_desktop_to_microcore, we installed full blown's xorg instead of the compact vesa that comes with tinycore.iso, because chrome requires xorg, and this time we chose to download it from 3.x tcz repos instead of 4.x.

After downloading and decompressing Xlibs.tcz,Xprogs.tcz,pixman.tcz,fontconfig.tcz,Xorg-7.5-bin.tcz,Xorg-7.5-lib.tcz,Xorg-fonts.tcz,Xorg-7.5.tcz,8 files in turn, restart first. Do not execute startx immediately (startx is in Xprogs.tcz). Execute startx under home/tc after restart, prompting that / etc/sysconfig/Xserver cannot be found. Manually prepare / etc/sysconfig/Xserver file. The content is one line of Xorg. Save, re-startx found that you can enter the desktop (and users will enter this desktop every time you restart TC later), but there is no window manager or right-click menu.

The above is the configless configuration of xorg. All the configurations are user configurations, which are generated in home/tc. Every time you restart and enter TC, you will enter the desktop because the startx has generated configuration files under / home/tc for the first time. Restart will automatically enter the original desktop (the effect of xorg and configless in xserver files), and test or restart all home/tc files after adding new things. Re-startx under / home/tc generates a new series of configuration folders.

Now that flwm and wbar.tcz (mac style docker?) are installed in the basic desktop environment, restart still does not have window management and right-click menu, this is because flwm has not been started, and it seems that startx has not added startup flwm logic to it in the home/tc configuration file. Add desktop=flwm to tinycorelinux bootcode, restart, and now have desktop and right-click menus.

Install chrome

I downloaded the 3.x 32.6m chromium-browser.tcz, version 14.0.835.186, and after installing the x interface, all that was left was to install chrome and rely on tczs. Download and install the following 18 tczs in turn:

(since each tc login automatically enters the desktop, you can open an external putty to execute the following command or sudo reboot, or you can right-terminal on the desktop.)

Atk.tcz,cairo.tcz,gtk2.tcz,gdk-pixbuf2.tcz,pango.tczdbus.tczdbus-glib.tczlibasound.tcznss.tczlibevent.tczlibcups.tczlibgcrypt.tczlibgpg-error.tcznspr.tczhicolor-icon-theme.tczshared-mime-info.tczchromium-browser.tczchromium-browser-locale.tcz

(in this process, right-click on the desktop-terminal,/usr/local/bin/ to execute. / chroum-browser test required tczs.)

Restart once after all installation, right-click desktop APPS-chrouim, enter chrome, find that the pop-up dialog box is garbled, click the garbled button in the lower right corner, enter chrome, and find that the title bar and address bar are garbled, even if you enter English in the address bar, it is garbled. This should be the chrome title bar and address bar, the font used in these parts of the toolbar is not available in the system. Lack of webpage font garbled box in non-system coding (is the system also used by en,chrome en,en-us? It is found that there is no en but en-us entry in / usr/local/chromium-browser-addons/locales, it is useless to rename, and it is useless to adjust the system etc/sysconfig/language)

It is found that the options related to font and coding are not available in the chrome settings (enter the wrench icon in the garbled menu). This is supposed to be this prebuilt chrome version of bug.

However, at this time, chrome can browse the website, https can not browse. The source code should be recompiled. Save it for later testing.

The GUI technology for tinycolinux here can be used in places such as turning tinycolinux into virtiope. Mm-hmm

This paper also lays the groundwork for "maximization of web development and release: a set of visual full-stack development and debugging tools centered on browser and paas technology, which supports automatic adaptation of demo in any domain". If all the demos ideas in this article are completed, it will be the bcxszy pt2 mineportal demos assembly, mineportal is a set of demos selection, xaas is diskbios, mineportal platform selection is completed, and the langys part is engitor. Complete the development and release selection of mineportal, the appstack,apps part is deepinoc, and complete the source code selection of mineportal. Finally, in order to make the oc based on big web available, online development, integrate all the necessary learning support. Learners can acquire the knowledge of PHP development by studying its implementation and accumulate their own codebase.

Thank you for your reading, the above is the content of "how to install chrome on tinycolinux". After the study of this article, I believe you have a deeper understanding of how to install chrome on tinycolinux, and the specific use needs to be verified in practice. Here is, the editor will push for you more related knowledge points of the article, welcome to follow!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.