Summary of the lexitong project and lexitong Project

Summary of the lexitong project and lexitong Project
1.Project Background

Tesco is an app that combines eating, drinking, and playing games, similar to group buying apps for Meituan and glutinous rice. The biggest difference is that this app is only used in Lhasa. This is a small market app.

2. Project Technology

The main technology used in this project is the idea of mixed programming. Both ios and android use the [BeeFramework] framework. This framework uses the idea of mixed programming, which encapsulates many excellent third-party libraries. The interface layout is written in xml and css.
The background is written using the open-source Ecshop framework. The advantage of this framework is that the development cycle is short.

2.1 BeeFramework Introduction Introduction

Beeframework is a fast ios development framework, mainly active in the github open-source community. The typical MVC Model is clearly divided into three layers: Model, View, and Controller. The business data, business logic, interface display, and interaction logic are completely separated.

Event-driven

The Controller and Model are independent of the Stateless. Therefore, they are driven by three types of events: Message, Request, and Notification. View discards the old Delegate and introduces the new concept UISignal to drive interface Interaction Events or state changes.

2.2 Ecshop

Ecshop is an open-source B2C mall framework with complete functions. It is very suitable for the background of rapid development of mall applications.

3. Project Problems Project framework analysis

Using BeeFramework for programming greatly shortens the development cycle, because BeeFramework is a mature framework and network data requests are encapsulated well, however, since the interface is written in xml and CSS, the time required for writing the interface is a little longer than that for the network request interface. However, the beeframework framework of the latest version integrates the LiveLoad mode and only needs to be set in Bee_Precompile.h.

#define __BEE_DEVELOPMENT__             (__ON__)#define __BEE_LOG__                     (__BEE_DEVELOPMENT__)#define __BEE_ASSERT__                  (__BEE_DEVELOPMENT__)#define __BEE_PERFORMANCE__             (__BEE_DEVELOPMENT__)#define __BEE_UNITTEST__                (__OFF__)#define __BEE_MOCKSERVER__              (__OFF__)#define __BEE_WIREFRAME__               (__OFF__)#define __BEE_LIVELOAD__                (__ON__)

Then, you can import bee. services. liveload in services to write a visual interface. Every time you modify the xml code, save it. The interface in the simulator will be changed accordingly.

Background Analysis

The background framework uses the open-source ecshop framework, which is outdated. The php version only supports versions earlier than php5.3. Then, ecshop functions are comprehensive. You need to be familiar with ecshop when using this framework for secondary development.

Interface writing

The biggest problem in the development process is interface writing. I personally think a normal process should be: when a project begins to design a prototype diagram after the project discussion needs are completed, one person should be responsible for writing interfaces, ios and android users can build a framework first. After the framework is built, the interface definition is almost complete. At this time, the background program and the ios and android end should write the interface at the same time. You can test the interface first when writing the interface in the background. The test passes the subsequent writing of the next interface. It is best to keep the order of interfaces written in ios and android in order to ensure the development progress is the same.

Personnel communication problems

In the process of project development, communication is still important, especially between the background and the front-end, because in many cases, the interface is not successfully called once, during the development process, data cannot be obtained at the front-end when an interface call fails. In this case, the problem can be found only when the background program and the foreground program are jointly tuned. However, for special reasons (many students in schools want to attend classes during the day), the backend and front-end cannot communicate with each other at any time. When an error is reported in the background, no one can solve the problem. .