Hello, tyomchick, you wrote: T> Advise please the exemplary interface of input of the schedule. T> as more as possible general-purpose is necessary, but thus idle time and intuitively the clear. Look on any scheduler, almost everywhere it is made equally. The calendar (some representations), repeating (regular) events are selected with color. The event template (roughly speaking, the information on the schedule and the general for all events of property) + from a template real events (only the changed events sometimes are stored, i.e. at what properties do not coincide with a template) is stored. Sometimes in addition to a calendar additional representations are got some, but they are always ground under a specific target (for example, the adjacent events without conflicts or quickly to enter a heap of events as the text) and always are under construction on specific scenarios of usage. I.e. the general recommendations for them are not present.