A view is a logical concept, so you cannot create a trigger on a view to track changes. Basically, a view is a stored query. Let's that the view includes ten tables. A change in any of these ten queries can change the result of the view.
You can create INSTEAD OF triggers on a view. This permits you run direct INSERT/UPDATE/DELETE on the view and define what actually is going to happen. This is a fairly advanced feature, only used in special conditions.
I think we need to know what you really want to achieve. That is, what drove you to think that you wanted this trigger and what is your root problem?
By the way, what is the definition of the view?