[Split] let's talk about the background things.

[Split] let's talk about what we do in the background! At the end of this post, mu_rain edited the drool notes on the background at, September 30, 2012-11-. The following are my personal opinions. /// // Click interaction. /// [scatter] do those things in the background!
At the end of this post, mu_rain edited and wrote the drool notes on the background at 11:18:30 on January 11,. the following are my personal opinions.

//////////// ////////
// 1 the login interface must be pretty good. at first glance, it decided a lot. [I won't explain it]
// 2 select a suitable front-end interactive package. I use easyui, which focuses on layout. the visual effect should not be too deep. just use a fresh color like csdn, interaction should not be too dizzy. for a long-term worker, too much excessive effect will make people vomit. only when important processing is required.
// 3 I don't have much idea about background layout. I basically follow the layout of ide.
// 4 the internal mailbox is a fast communication method and a good means of notification Publishing and work reminder. if you are interested, you can also use sns. [for example, your xxx was logged on to the background at xxx. Today, he did ***]. here, we encountered a problem that we don't accept or want to use. there is a way, the direct mode dialog box pops up, click OK, no harassment, and idle when nothing happens, with the administration, the boss, promote this thing. besides, the data is all on your own, so it is convenient to search. it is very fast to find anything.
// 5 menu interaction. after you click it, the workspace tab is displayed. this colleague is very happy to accept it. [it's the same as ide.]
// 6 Add Upload processing [requires firefox browser support], html version for html5 display. See the post http://topic.csdn.net/u/20121018/10/16e8f8d2-2955-4680-9e69-167681f0363c.html
// 7. table data. the color of each row is alternating. it is light-colored when sliding. the selected color is dark. although small, the effect on the business staff is obvious.
// 8. ajax processing is complete. after the batch operation is complete, the query conditions are held. [For example, to review the data of today, the query condition is today, not reviewed, and sorted by time] in this way, reload the data for each operation, instead of selecting the query condition twice.
// 9. The last point is also the most important thing. after the basic implementation of the technology is no big problem, the service is a good place to show different levels of capabilities, the service is good, and everyone is optimistic about you, as long as you encounter a wise, normal boss, happiness will come. also, don't worry. sometimes, the business will pull unreasonable things, slowly guide and communicate with each other. after a long time, you will understand.


//////////// ////////
// 1. in the permission management section, I use a simplified culture to associate roles with menus. complete basic role permission control through visibility. then add a filter table to the hook of the controller to prevent illegal intrusion. I would like to say a few more words to this piece and grasp one principle. less is more. the difficulty is not the technology, but the right person. Therefore, we recommend that you make a good agreement from the very beginning, and do not meet too many personalized integration requirements. once there is a bad start, the changes in human desires will directly cause you to crash. for the demand side, it is hard for your kid to write faster and think faster. of course, it is strict, and there is a mature business system. we have used some bug management and oa products. if you want to do more details, it is more appropriate. in, I also worked on something similar to the permission tree, a sub-node role, and a file. it goes up to three levels. you can see the node of the direct link and go up to three levels, next, the sub-nodes are traversed, and then connected to the project owner. people with historical project access can look at similar demands. now, it hurts to think about it. The final suggestions should not give too much space to boring people. the purpose of their project is not In order to get out of the product, but for the existence of the so-called value, think deeply, this is troublesome, so less is more!
// 2 do not write a query like where 'name' = '$ name' & pwd =' $ pwd' during login. First, check the user and then compare the password. perform the necessary xss processing for each submission. use 360 to check website security and handle some basic security vulnerabilities. of course, there are still many things that require the collaboration of server engineers to clarify this concept as early as possible. it is a sad reminder to be an all-round warrior.
// 3 use lang to process the language and text. in this way, the text is changed in one piece, which is more convenient. [the principle of central control has always been mentioned in the code Daquan]
// 4 add user action tracking, trace each controller by hook, and write useraction logs. data-centric, tracing and processing of each data, and tracking of important data and data links.
// 5 The backend is Configuration-based and based on the principle that the conventions are greater than the configurations. for solidified things, the more agreed schemes are adopted, and for things with changing requirements, the configuration is adopted, the data list displays the keywords, fields, and user behaviors.
// 6 generate a pie chart, column chart, and so on, and directly use google's api to save trouble and find N php production charts, which are mostly difficult to use. of course, when the google Api cannot meet the requirements, it is hard to use phpchart-related classes. fortunately, this kind of thing hasn't happened yet.
// Write more excel files, such as batch data import and batch data export.
// 8 swfupload, editor, and other things are packed. you can add them directly when using them. when writing, use the css style to control whether the changes are converted between the two. for json data, the select radio generated by the database table is wrapped in form_helper. I noticed that every framework has a place where form is generated. however, for only one input, it's okay if you are idle, and you don't need to create form_helper. unless you want the entire form to be generated by the configuration. however, based on the project experience, this is the fastest change in TMD business requirements. writing by hand is indeed the most practical method. direct Perception and convenient maintenance. when you want to encapsulate a large number of things that are unpredictable, you need to think about the necessity of encapsulation and whether it is over-designed.
// 9 for each data, the mainstream beforeInsert afterInsert frameworks are supported before and after insertion. In fact, there are quite a lot of data to be written here.



/// // Click the code //////////// ////////
// When combining your own classes, autoload may be involved. do not directly change the autoload of the framework to [I like this when I was young] and put my own code, put it in a suitable place and combine it to facilitate loading and unloading. research can do. don't tamper with the code of someone else's framework. Although the framework may be bad in some places, remember, don't do it yourself, don't do it. first, what you write is not supported by teams and a large number of qa engineers. tester is prone to problems. Second, if the framework is upgraded, will you go over it again ???
// 2 do not over-design when writing code, do not abuse design dashboard, pay attention to the code experience, and experience it from multiple perspectives when writing an architecture, in the future, how can code be written, how can the code be well written, and how can we communicate with our team members. for large frameworks, the learner is born, the learner is dead, and the essence is exhausted. when using it, do not blindly follow.
// 3 when you are familiar with and understand the business of your company, you must rebuild the basic class of the controller and model based on the features. you are familiar with the business and naturally feel how to write it.
// 4 there must be a set of naming standards. for example, userModel (model) user (controller) has _user (configuration) v_user_index (view. phpstorm has a good command of ctrl + shift + n to quickly find the file based on the file name, which is very helpful to improve efficiency.
// 5 common hotkeys. the shortcut keys are packed. for example, if you write foreach and press fe + to press enter, all of them will come out. lm + press enter is all the code for load model. there was a cool man last time, and there was a post. editplus can be used like this. the essence must be more attractive. I use phpstorm and also have a large number of fast cut keys. editplus can be implemented, and ide can also be implemented. view the structure of the class, review the code, integrate svn, phpunit, and syntax Check. the code prompts that the editplus is not powerful.