DisplayManager has great potential to become great, but currently it ehm sucks.
But we need to plan out how to make it "Great Again" (though it never was).
Design Concept
The definition would be adjusted to look like DisplayManger.Display(DisplayObject, [DisplayProp])
where DisplayProperty is an Enum. A useful cool proper use of Enum.
We'd use it as the following:
DisplayManger.Display(displayObject, DisplayProp.Stretch | DisplayProperty.Animate_FadeIn | DisplayProperty.Animate_SlideOut)
DisplayProp.Stretch would extend the object to it's parent.
DisplayProp.Animate_FadeIn theoretically animate in the object (just idea, no intention to implement)
DisplayProperty.Animate_SlideOut theoretically would slide the object off screen. (just idea, no intention to implement)
Design Implementation
I'm thinking we either let every menu display/dismiss itself (obviously we don't want) or have SelectionManager do that for every pushed menu, and dismiss popped menus. But with this. every display object would have a property of type DisplayProperty. Which is cool actually.
Implementation Cost
We currently have Stretch functionality only. So we don't have worry about time, but the concept here it to plan ahead, and have an adjustable design for animations. This would not be considered refactoring since would have default DisplayProperty be set to DisplayProperty .None as an optional param.
Disagree, agree? I want disagreements because without flows, it's perfect. So let me know if there are any possible issues or anything i might've missed.
DisplayManagerhas great potential to become great, but currently it ehm sucks.But we need to plan out how to make it "Great Again" (though it never was).
Design Concept The definition would be adjusted to look like
DisplayManger.Display(DisplayObject, [DisplayProp])whereDisplayPropertyis an Enum. A useful cool proper use of Enum.We'd use it as the following:
DisplayManger.Display(displayObject, DisplayProp.Stretch | DisplayProperty.Animate_FadeIn | DisplayProperty.Animate_SlideOut)DisplayProp.Stretchwould extend the object to it's parent.DisplayProp.Animate_FadeIntheoretically animate in the object (just idea, no intention to implement)DisplayProperty.Animate_SlideOuttheoretically would slide the object off screen. (just idea, no intention to implement)Design Implementation I'm thinking we either let every menu display/dismiss itself (obviously we don't want) or have
SelectionManagerdo that for every pushed menu, and dismiss popped menus. But with this. every display object would have a property of typeDisplayProperty. Which is cool actually.Implementation Cost We currently have
Stretchfunctionality only. So we don't have worry about time, but the concept here it to plan ahead, and have an adjustable design for animations. This would not be considered refactoring since would have default DisplayProperty be set toDisplayProperty .Noneas an optional param.Disagree, agree? I want disagreements because without flows, it's perfect. So let me know if there are any possible issues or anything i might've missed.