Question

ORM Designer 2.1.6.678, MVC Symfony2, ORM Doctrine2

It is possible to create a new project, model and then just click export. Without expert knowledge I don't know where to set export settings (yeah, module settings ... but I'm a novice for the sake of this bug report). GUI says "Export complete" although no files are listed at all.

This needs a warning "You do not have set any export settings, go to ..."

Comments

As usual thank you for testing and all comments. You're right. We will add some guide when no module is selected to export.

---

And when any module does not have export settings, please. It's not so much about module selection as the fact that you could exclude a module from export just by forgetting to set what to export where in that module.

---

I didn't notice your message until now. So you're suggesting to check if any of available modules has export settings, and without that don't allow export?

Maybe a better solution would be display list of not-exported modules in the result screen?
Now we have implemented only check that at least one module has export settings.

---

Next version of ORM Designer will have this feature.

---

Grrrreat! (I need 12 chars)

Answer 1

This issue was fixed in latest version 2.1.7.679. You can download this version here http://support.orm-designer.com/31/download-orm-designer2-here

Comments

Answer to your question above "So you're suggesting to check if any of available modules has export settings, and without that don't allow export?" (No more comments possible because I selected an answer already)
No, just a warning. We have 15 modules in our big project and recently I added a new one but forgot to set the export settings. It should not halt the export but produce a warning.

Follow-up question: What's the use of a Quick Model?
Is there a plan to support changing MVC and ORM configuration later on? Or is the Quick Model just useable for visual modeling and export to PDF?

---

The usage of Quick model is exactly what you wrote. Create ERD diagram prototype during brainstorming without any additional logic.

We already discuss about feature for changing MVC/ORM several times but still without any result. It isn't possible write rules which converts for example Doctrine1 ORM attributes (behaviors) to Doctrine2.

So only way how to perform conversion is remove all ORM properties and convert only core model. But I'm not sure if feature like this will be useful. The only usage of this feature would be in converting Quick model to Doctrine2 model for example.

---

Yeah, my thoughts exactly. It wouldn't be feasible to convert between ORMs, especially seeing all the features that Doctrine2 does and does not support in contrast to D1 or Propel.

I'm just thinking that maybe some user will model their whole schema with the Quick Model type and only when they are done will it be apparent that there is no export and they have to start from scratch. Maybe a little info screen as to the purpose and caveats of the Quick Model?
You could include a default comment in the Quick Model "Simple module" template.

---

Good idea! I will insert model comment and discus model conversion.

---

Next quick project template:

---

Perfect! That should suffice.