Primary Objectives based on Specs .2:
1. Alarm: in three steps various ways (there is some difference in setting this for track/playlist)
  I) Select track/playlist(in playlistnode)
  II) Click on Alarm Button/rightclick/D&D to Button
  III) Completes UI Alarm Form or similar acording to specifications in Description of Implementation section F (Editing Event Dialog)
  
  Note: Abbility to export List of Alarms Via Script.

2. Supress Silence: Abbility to enable Supress and set Silence time in Options. Other things is needed to be more discusted like What if Player is set on rotation, how to set default and how to change it.

3. Pro Version: Need to be more specified which events are for Pro only, which will be partial supported, which are not supported.

Description of implementation :
-------------------------------

a) The functionality should be accessible by:
  - Alarm/schedule Button on advanced Toolbar (like Search Button with PopUp list to select approc. event)
  - Main Menu - view: Auto DJ (Toggle). I must say that I dissagree with Implementing new UI inside MM. If may I suggest Schedule events no matter what they are Alarms, Scheduled Events, AD/Jingles be in separate node (in files to edit or in main Named 'Scheduled') explained in Appendix A Section a. Main reason for my suggestion is a Question "Why introduce and force user to learn new user Interface if we can use existen om which are users familiar with?"
  - Plugin???? Little bit understandable?
  
  Regarding 'Send to' I agree with Idea as this is the best way to implement Scheduled events.
  
b) if Scheduled/Auto-DJ is a plugin MM should note in what LNG is localized l.e. like path to Lng (Sr - serbian, De - German, ....

c) This is same as 'b)' but name of theme will be used.

d) Please elaborate. Little bit confusing

e) It seems Ok as an idea I think that UI need to be simplier/familier for user. all other are Ok and more than OK.

f) Basicly OK, with all the functions needed for any of templates, but not all templates needs all of them.
 
Appendix A
-----------

a) Node look:
  ---------------------------------
  Scheduled->
             |Scheduled Playlist 1 (First next Scheduled date time)
             |Scheduled Playlist 2 (First next Scheduled date time)
             |Scheduled Playlist 3 (First next Scheduled date time)
             |Scheduled Playlist 4 (First next Scheduled date time)
             |...
  ---------------------------------
  Note: - When user clicks on root of node in Track list is shown Single Scheduled Tracks. 
        - When User Clicks on Scheduled Playlist in track list are shown tracks that are in coresponding Playlist.
        - When user clicks/rightclick/D&D on Show Proporties (Track/Playlist) it opens Form with proporties of that event with editing capabilities or if this track/playlist has multiple events a list with them with focus on selected one (like in section Q)