polymorphic uniface -- ideas / opinions wanted about mui HOT 3 CLOSED

Hi,

Yes definitely useful I think and a neat way to do things, it's also clear that the current design of either relying on specialism or templates is fairly messy, both in the mui.h file itself and also as a barrier to understanding how to use the code.

This suggestion could be rolled up into a larger piece of work to look at how to best create a single apparent interface class whilst actively discouraging the use of the specialism approach in future versions of the library/demo cases.

from mui.

If not present already I would also consider a factory object for Interface that takes dimension as an argument. This will avoid code duplication for the cases in your listing.

GenericInterface might be a name worth considering.

Nitpicking: we might need an example without new. I think in C++11 and later they frown upon manual memory manipulation like this.

from mui.

I'm going to close this issue for now as generally usage seems to have settled around the templated variant of the uniface class, this would represent a hybrid sort of approach in some ways, we can revisit in the future if needs be.

from mui.