> > Do you agree that XWT's model is the classes, properties and > methods/constructors of the underlying SWT API, since that's what XAML > is: a serialization format for an object structure that is > (re)constructed with a specific API (classes, properties and > methods/constructors)?
Wrong. It is the case of XSWT, not XWT. XWT has 100% Object Model without methods and constructors. I just you to take a look on XWT or XAML. I know TM. The model in IM defined in EMF is very similar with the model of XWT (I said similar since I didn't compare completely). Best regards Yves YANG > > It may be natural to program against SWT, but I don't think it is > natural to model a UI with such an API-oriented model. A UI model should > represent the _state_ of the UI, while an XWT model represents the > _creation process_. > > Yves, we are repeating ourselves. Until I can think of new pros and > cons, I think I'll be silent. > > Hallvard > _______________________________________________ > e4-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/e4-dev > _______________________________________________ e4-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/e4-dev
