Personal Knowledge Management System version1.0 development record (08)

Entry Point

Previously, we have built a basic structure for the Web end, and three main problems need to be further located:

1. Selection and confirmation of the interface. The preliminary style made by extjs is further changed to jqueryui/HTML, and then to HTML5. We think about a kind of user thinking. As long as there is a place that the user does not like, the user will deny the software. Therefore, the software interface must be simple and exquisite, which can arouse users' interests, meet users' habits and users' thinking.

2. selection and determination of the Framework. Before compiling the core functional modules of the knowledge body, you must complete selection and rewriting.

3. When selecting and determining the direction, each person has a certain amount of time and energy. To choose one thing, you need to give up many other things first. When you know the time, you can choose the direction, you can refer to the social background and business needs, work-related content, personal growth, and so on. The choice of direction is crucial. If you want to learn everything and do everything, you will only be lost in the sea of knowledge, so that you will lose yourself and continue your years. It is best to learn how to focus, how to cooperate, how to communicate, and what you don't know, and what you don't do on the backbone of your knowledge system. We recommend that you use paper pens:

(1) list the functional templates that need to be implemented, and analyze them based on their knowledge. What can we do, what we need to learn to do, and what needs to be refined;

(2) list the module priority, module Association, and the first and available associations;

(3) What can be done as a shelf, and then find a more professional partner to do it.

 

Next, we need to take some time to create a "connection function module" to connect to the Mobile End and build a basic structure of the Mobile End. We can consider the following aspects:

(1) The entry point is simple and practical. It is a connection from a functional module on the Web terminal to a functional module on the app terminal.

(2) data can be interconnected. Whether the interface is different or the database is different, associations can be established for CRM management.

(3) meet user habits and have commercial value.

 

I can't think of it. Let's look at advertisements, elevators, subways, media news, on-board TVs, and square advertisements to see what others are doing and what users are watching. Let's simulate a scenario without considering whether it can be implemented:

(1) we add a functional module on the web interface, "Contact Us", some contact information and a QR code;

(2) The user pays attention to our number, and obtains basic user information and geographical location through the public number;

(3) Conduct CRM management, associate the basic user information with the basic user information of the system, use this application to connect to the mobile end, and develop their own independent (database and Software Interface) and third-party mobile software. For how to collect such information, consult your business partner.

 

Right or wrong. Time flies, hurry up. The idea is as follows:

 

1. Check the APIs and some help information on the public platform to find out how to play, what conditions, what to pay attention to, and what knowledge to use. It is server-based data transmission and processing.

 

2. Write the control layer. (1) The user interface is: (2) the user sends the information to the server, (3) the server sends the information to the control layer we wrote, (4) the control layer receives, processes, and sends processing information to the server. (5) The server sends the information to the user.

 

3. Information sent from the user to the server, including text, images, links, geographical locations, sound, and video; Information sent from the service number to the server, including text, images, links, sounds, and videos. According to API information parameter descriptions

And encapsulate them into objects.

 

4. The data exchange format is XML. The control layer converts the XML sent by the server into a Java object, and the control layer sends messages to the server by converting Java into XML. Use Dom and xstream.

 

5. Open the service number "get user location" and write some business processing logic, such as receiving, processing, and sending messages. We obtain the geographical location of the user and send the data to the user as is.

 

 

6. Customize the service number menu, compile the menu object based on the API, and generate a custom menu based on the developer creden. There are two types of buttons: Click and view.

 

7. Data Storage. If you only process the information in real time, You can temporarily store the data in the memory. If you need CRM management and some tracing functions, you should consider using the database.

 

8. I don't want to use a mobile phone or let the service number know our real location. How can I do this? Therefore, we must consider where the geographic location data of the mobile end comes from? Mobile Terminal System. OK. Download the android simulator and GPS software, and set the geographical location to Tiananmen, Beijing. Log on with a simulator. The service number sends us the geographic location of Tiananmen, Beijing because she receives the geographic location.

 

We need to do this later. (1) generate a two-dimensional code with parameters, or use similar functions. (2) Improve custom menus. (3) Write intelligent robots that can interact with users, (4) Implementation of the tracing function, (5) Implementation of Data intercommunication, and open bridges for mobile terminals.

Recently, when watching global events, there seems to be a trace of fate. In fact, she has been in front of us all the time. When we started to understand her, we saw her existence, she had been waiting for a long time. OK. We will see you next time.