All geek questions in one place

Design pattern for multiple view states?

I have an application that takes a user through a set of steps, setting up a product, say, on more than 10 screens. With return options, go to a specific point, etc. I need to fade between these steps, and also have language switches at any time.

I was thinking of using the MVC style template, having a wizard view that takes on “the next look and disappears”, removing the old one.

It feels bloated to have 10+ separate look classes using similar components for this task, so I wondered what other approaches I should study? or one that is suitable for this type of application

+6
source share
2 answers

Before you separate your views, first think about what they have in common.

My first instinct would be to create a View class and set the necessary properties for the view itself, namely fading between screens and everything you need that is related to design.

You say that the user will configure the product, so you can create a configuration class solely for this purpose. Be careful not to introduce too much dependency between your objects.

The configuration class should not know too much about the View class, or rather, how it is displayed.

It is difficult to say more without knowing your project, but the idea would be to separate the view and the data, look at what your objects have in common, and then use variables or other objects to introduce more specificity.

+3
source

I used The Gaia Flash Framework for this. http://www.gaiaflashframework.com/

In this video http://tv.adobe.com/watch/fitc/gaia-framework-for-adobe-flash/, you should get an idea why I think this will work for you.

0
source

Source: https://habr.com/ru/post/889186/

More articles:


All Articles