Ultrashock Forums - View Single Post

wraevn · 2007-10-10 #**208**

So my thoughts went like this:

When you're configuring a product, you see ProductConfig view. You update the data, other stuff in the view changes, etc.

Then you switch to Design View (so ProductConfig/Design is a toggle).

The Design view is comprised of many different views depending on the state of the design/product/tool selected/layer selected etc.

All the data the view needs is in the Design portion of the Model.

The OptionsBar view for example hosts the generic functions all OptionsBars will need. The TextOptions therefore view will be listening for when a text layer or text object has been selected. Then it can toggle on and others can toggle off.

Basically, I've divided the Design screen into managable components, each of which contains UI elements and interactive elements that alter the view-state of the entire Design. This way, it's more easily skinable, adaptable and extensible.

	wraevn	2007-10-10 #208
	So my thoughts went like this: When you're configuring a product, you see ProductConfig view. You update the data, other stuff in the view changes, etc. Then you switch to Design View (so ProductConfig/Design is a toggle). The Design view is comprised of many different views depending on the state of the design/product/tool selected/layer selected etc. All the data the view needs is in the Design portion of the Model. The OptionsBar view for example hosts the generic functions all OptionsBars will need. The TextOptions therefore view will be listening for when a text layer or text object has been selected. Then it can toggle on and others can toggle off. Basically, I've divided the Design screen into managable components, each of which contains UI elements and interactive elements that alter the view-state of the entire Design. This way, it's more easily skinable, adaptable and extensible.