EonerCMS-CMS (1) for a desktop-like system)

Opening

A month ago, I suddenly had an idea: Can CMS do something like webQQ? The whole background is like a desktop system, which classifies functions into a desktop icon, after clicking an icon, you can perform operations on it as easily as operating a folder on your computer. So I wrote an idea article: see my personal opinions on CMS background display/operation methods, but few people agree with my ideas.

After the article was published, I also wondered whether this method is applicable to CMS. I have discussed it with several colleagues and CEOS. Some people also mentioned the issue of development costs. I said this is not a problem. Now we don't need the company to spend manpower on dedicated development. I will first make a prototype and encapsulate some calling methods, for example, some common operations such as window operations (maximization, minimization, and closure) and right-click operations are written as a class. If they are feasible, continue development. In this way, the methods are encapsulated and called conveniently. Subsequent development will be the same as general CMS development.

At that time, our boss (CEO) gave me the advice to lay a good foundation first. Because my JS capabilities are not strong, although I have previously written a jQuery plug-in (jQuery. hooRay), but it is still not enough. So this month I have been strengthening my js capabilities, and I have also studied some websites accessing the desktop system, these include webQQ and 115 in China, and some foreign cloud operating systems, which provide a small analysis of their interfaces and operating modes.

So today, a month later, I decided to officially start the development of my EonerCMS. I decided to first copy the 115 Application Center interface because of its simplicity, because I would not design it, so now the simpler the better, and then let the design unify the interface design, the replacement is also convenient.

This article is here first, and I will write an article every week. On the one hand, I will summarize the Problems and Solutions encountered in the next week, and on the other hand, I will give myself a task schedule, check how much things you have done in a week.

PS: In fact, I made a little bit today and completed the "shortcut" on the interface. The shortcut is generated through js loading instead of directly writing it on the page. As for the reason, first, I will describe it next week. Let's take a look at the results of the test.