As a general note Please try not to create a component for every single use case. I'm also started to remove some of the currently defined unnecessary components to keep them more organized.
Please put a short description of your component and explain what it does and where it can be used. Since it is a specific or compound component and is not a general component like a just a Slider or Progressbar, it helps to understand the use case of the component.
A test should be self-contained. QTest supposes to call this test function automatically. so what happens to the parameter view? If this test needs an object it has to be created in the test function.
Hey Peter, You're right I removed them to easier do the merge. Since the task DEN-4690: Doxygenization has been changed to story and there is a code review sub-task for that, let's address all the documentation in that stoy.
These are all the FW specific values and terms I don't know about them much and not all of them are used. So I don't know the specific definition for them to put them. We need to ask the FW team to provide us more descriptive definitions than the one in the Messaging List. Or dig deep into the FW SDD to find them out.
I looked into subclassing MAbstract at the time and again today but there's some incompatibility there that needs to be worked through. How about I work on subclassing MAbstract in my current story? I don't think it would be good to change too much structure against these revisions as the code has been sitting for awhile and other things have changed quite a bit. Also, I think the MAbstract class may have been added near the end of my development on DEN-3605. I'd like to make sure our models and code structure are all aligned too. I think it's better to do that on the latest code rather than the branch this code is sitting on which is outdated at this point.
