As this question arose, I will probably get to the point. There is a request for a server, it has 26 parameters. (cute true?) Requests to the server can be about 350! in each from 5 to the heap of transmitted parameters.

The point is this, that’s the question.

Each request is broken into my Action. Each action is in a separate file.

// upd_start

Why was chosen precisely partitioning actions on files. The project is big enough. So that all developers do not expand the controller itself, but simply add 1-2 lines to it to connect the new action + it is convenient to edit the project with such pieces, and not with a whole file that would constantly tolerate changes. For me, this is correct.

// upd_end

example:

public function actions() { /* All actions in this controller * are located in folder * application.controllers.frontend.requests */ return array( 'gf' => 'application.controllers.frontend.requests.gf', // и т.д. ); }

First question:

In what language should I write a description for the whole project?

At the moment I am trying to describe in ENG, as can be seen from the above function, the description in ENG.

The gf.php description is also on ENG

 @NumSeats - The total number of passengers for which availability is being requested @StartDt - Date of Departure or Arrival. @StartPt - Airport or city code of the customer embarkation. @EndPt - Airport or city code of the customer Destination. @StartTm - Requested departure in 24-hour clock

In principle, I think that this is correct! In terms of the development of the project by other participants, both Russian and English speaking.

But there is one thing. There are people in the company who do not understand the ENG language very much and are therefore asked to comment on the code in Russian.

What's the catch? Well, it's easier to read Russian! I agree that translating Technical ENG is a Kick-Ass as "fun", I’m quietly going crazy + to everything it’s not always possible to translate ENG into RUS correctly due to various circumstances (lack of knowledge of some turns, etc.) In general, there are enough fun things to do. languages.

There are solutions, to score on ENG to write only on RUS, the second solution to write only on ENG, the third to write in 2 options and in ENG / RUS that decides the troubles of both cases, but will increase the number of descriptions to the code, which in my opinion is not good .

Here at the design stage of the project and I want to find out how best to do. On the one hand, I want to give everyone the pleasure of developing and writing a description for everyone, you still have to translate the manual of the system to RUS, on the other hand, writing a descriptor in 2 languages ​​is a chore and somehow too much code in the file.

Will a great description affect code performance?

last edited by 06/11/2013 15:32 There will be additions voiced while everything is.

Waiting for your interesting reviews on the topic.

Naturally I will continue to open new questions on the topic of development.

    1 answer 1

    @Shrek , did not quite understand what kind of people they want in Russian.

    If they accompany the project, it is better to make comments on RUS.

    If this is just someone from curious customers, then how is more convenient for you (apparently, leave ENG).

    And to write comments in 2 versions, it is useless. Then it is better not to write them at all, because after six months, one of the options will not exactly match the code.

    • @avp I now wanted to write in ENG for closer to the developers, I would call it that. This is not a curious customer, this is the boss who is currently starting to understand Yii and wants RUS comments :) Yes, and ENG looks better, and somehow closer to the heart. In 2 variants in half a year they will correspond, since The xml server will not fix it. In the worst case, one parameter will be added. - Artem
    • 2
      @Shrek, if there are only 2 people in development - you and the boss, and the project is only local in perspective, you can do better on RUS. And if some terms are poorly translated, then leave them on ENG. Many do not like this, but for me, so normal. In the comments the main thing that was clear. Therefore, if there is no established translation of the term, it is better to leave the native (or slang) word. And yet, it is unlikely that you yourself will always accompany these programs, and new people in Russian may be. simpler. - avp
    • Yes, so I think, who will continue to oversee the project. Yes, it will probably be more correct to RUS and leave ENG in hard-to-reach places :) - Artem