You might be able to use the assistant, I just wanted to say it doesn't work correctly in some cases and breaks in others. In fact, I invested quite some time to generate the needed config entries so that the components and templates show their settable properties in the assistant.
But the assistant is creating a slew of rules and if you mess it up, you might as well start fresh. You can do this with a small project, but not when you have more than a few pages, so I only work with RuleEditor.
And I always look at the source and the .wo, so I see immediately what is supported, but granted, for a simply overview this would be a bit daunting...
I wanted to prepare a webcast with Nathan Walker (we already did one for Eclipse a while back) because this stuff is easily explained when you can show it to people but a pain to write down...
Cheers, Anjo
Am 28.04.2006 um 16:53 schrieb David Holt:
Hi Anjo,
This is the first time I am trying ERD2W and I had the brain wave that the assistant would be a simple way to look at the property level components and the templates that Wonder provides. As you are specifically recommending against using the web assistant, what else can a newbie do to get familiar with the additional features of ERD2W (especially the display components)? I know that with D2W I loaded a model and then went through the options for displaying attributes and relationships to see what worked best. Is there an option to look at display changes on the fly with ERD2W? I am just rereading the WROX book now, so maybe the NetStruxr case study has some recommendations. Thanks,
David
On 27-Apr-06, at 10:12 PM, Anjo Krank wrote:
least not link in ERD2W when running these assistants