Ultrashock Forums - View Single Post

wraevn · 2007-10-10 #**205**

Okay ... I think I might be starting to get a grip on things here ...

I've created a UML diagram of my RIA based on Nutrox's Neondust framework HERE

If you want to be able to load it into gModeler, HERE is the XML you'll need.

Codemonkey - Nutrox - et al ... could you have a gander and see if I'm on the right track? I may have some association relationships mixed up (I struggle w/ associations) but I think you'll get the idea.

Based on advice from previous posts I have:

1 Model which will contain all data, divided into 3 sections: Department, Product and Design. Model has 2 views: ProductConfig and Design.

1 View, which serves as the base class for many views. View has a Controller.

1 Controller to handle everything

The Design view has a Stage view, ToolBar view, PricingPalette view, LayersPalette view and an OptionsBar view, all of which extend View.

The LayersPalette view has ClipArtTab, StockArtTab and UserArtTab views, all of which extend LayersPalette.

The OptionsBar view has TextOptions, ImageOptions, ShapeOptions and ExtrasOpptions views, all of which extend OptionsBar.

... reading what I've got above, perhaps should not the Model have View, not ProductConfig and Design? Other thoughts?

	wraevn	2007-10-10 #205
	Okay ... I think I might be starting to get a grip on things here ... I've created a UML diagram of my RIA based on Nutrox's Neondust framework HERE If you want to be able to load it into gModeler, HERE is the XML you'll need. Codemonkey - Nutrox - et al ... could you have a gander and see if I'm on the right track? I may have some association relationships mixed up (I struggle w/ associations) but I think you'll get the idea. Based on advice from previous posts I have: 1 Model which will contain all data, divided into 3 sections: Department, Product and Design. Model has 2 views: ProductConfig and Design. 1 View, which serves as the base class for many views. View has a Controller. 1 Controller to handle everything The Design view has a Stage view, ToolBar view, PricingPalette view, LayersPalette view and an OptionsBar view, all of which extend View. The LayersPalette view has ClipArtTab, StockArtTab and UserArtTab views, all of which extend LayersPalette. The OptionsBar view has TextOptions, ImageOptions, ShapeOptions and ExtrasOpptions views, all of which extend OptionsBar. ... reading what I've got above, perhaps should not the Model have View, not ProductConfig and Design? Other thoughts?