Is MMX better than Delphi's own modelling?

Question

I'm using 2010 Enterprise, so I have all the modeling tools available. But I still seldom use them. I write the objects myself, setters, getters... I want to start using modeling besides class diagrams. Should I opt for Delphi's own implementation or perhaps try MMX. What other features does it bring to the table? Thnx.

Answer 1

MMX is a great tool for coding OOP, it improves the productivity when you get used to this features.

I don't think it replaces a Modeling Tool, I think MMX help you to write OOP code, refactory, navigate and inspect code, I can't imagine another tool to improve OOP coding in Delphi IDE like MMX does.

Delphi Templates can help you coding, is great and I do like, but MMX have a lot of "wizards" done, and I can't imagine how to implement some MMX actions using templates.

I use Delphi Modeling and MMX for coding, not only OOP, but to study and undertand 3th party units.

My favorites features:

• Unit visualization and navigation
• Class/properties creating/editing
• method parameter editing
• copy/cut/past classes/properties/methods
• local var creation and editing
• scope renaming
• Live Metrics, "I use this a LOT"
• Sometimes I use live documentation

To me, MMX is a must have expert.