Create an automation application to monitor member activities for productivity/research, calendar reminder, and account abandonment. This application will handle all emails and remove user from active status if they are not productivity for 33 days or have not logged in 28 days. Calendar reminder will be fired off between 12 and 16 hours before the meeting is to take place.
Created Button, Canvas, ContentDecorator, Grid, Icontrol, ImageElement, MondalElement, ScrollViewer, StackPanel, TextBlock, and UniformGird classes with is enough to encouple Ui.Panels and must of UI.Controls. Still having issue with EditText and need to add couple more classes.
I have all the abstracts combine into one, removed all the navigation logic class, renamed all the controls, migrates the sync in Package.InterfaceManager, corrected the namespaces, and made sure that Application.Design was only pointing at the ManagerAbstract and the Models. Submitted to TFS
Upload merged project files. I wasn't able to run the project. Looks like their is a package being reference outside the project folder. I was also unable to look at any of the code not part of App.Windows even after I installed xamarin.
[C:\Program Files\Silicon Studio\Paradox\GamePackages\Paradox.1.2.2-beta\Targets\Paradox.targets(166,5)]: Error: Unable to find package decription from path [C:\Users\Owner\Documents\Visual Studio 2015\Projects\Game The Last Stand\Application\Application.pdxpkg]
All the control are models and should be moved to the model folder. I got confused because the Paradox source code does not break out models and logic. As a result there code has a lot of duplicate code which would lead to time wasters.
The interface Manger Package probably won’t and shouldn’t have a data access level.
We are going to have less control over the Interface Manger because we are decorating the Paradox classes rather than creating classes which just happen to use Paradox methods. We could get away from this, but it would cause a lot of scope creep as we would be reinventing the wheel. http://www.tutorialspoint.com/design_pattern/decorator_pattern.htm
We should consider embedding package code libraries in there own Paradox package folders. This will prevent paradox from moving the package libraries into the application folder. In addition, it will let us use package specific assets.
Submit to TFS. Basic functionally works. There is an issue with the click event not working on all the drop down items. Basic formatting like width and height need to be overridden, so that all the parts of the drop down are affected when changed. These could be there own sprint items.