Polymorphic Design for User Accounts

[pquackenbush]

I've gone ahead and added a UserAccount class with three subclasses in the core module. This will allow us to easily launch the specific UI depending on the UserAccount subclass returned after logging in.

Added this to the tracker to test whether I could still tie a commit to a certain issue. fingers crossed

[pquackenbush]

Note:

This is still on the HomeownerUIBase branch

[pquackenbush]

I had a thought that perhaps we should have another package like ...common.data for the common ADTs that will be utilized like the User Account types, perhaps a JobRequest class, AvailableJobRequest class, and so forth.

This would help keep the core module more organized.

[rsanchez-wsu]

@pquackenbush, good call on both the polymorphic user account types and the core data objects.

[pquackenbush]

I think everyone is on the same page here. No need to keep this open methinks...