Choosing pattern when object has view and model properties

I have a problem as to how to model my application. I have an object which has both properties of a model and a view.

To be more specific I allow a user to generate nodes, which have a set of actions like moving them around, clicking on them and so on. Node is a view element but also has model properties within him e.g. position, states etc. How do I go about splitting its responsibilities?