Retrieve list of Backup Items from Database

We are now able to retrieve the backup items directly from the database.
This means that we are going to be able to use the model for requesting
all items for either display or the actual backup process. It will be
expanded to be a list of tuples that will contain all the backup list
data: source, backup frequency, relevent settings, name of the source,
source type, anythign else needed. It also sorts the list as of now so
that it will be easier for us to read.
Remove Added, Returning list of items works, bugs fixed

The remove function allows us to remove a backup item
from our backup list. The return list now returns a dictionary
that contains a tuple of all data associated with each backup
item. Various bug fixes are included to help check if we
are making valied queries.

The remove function works through takign a name and a type
for a given node and finding it in the backup list. We then
just remove it from the tree. This works. We have to manually
save as I don't want users to feel that they must redo everything
incase they mess up. Working so far.

The returnlist function is goign to be an expandable dictionary
of tuples. We will use the text as the key because it is what the user
will see and I __THINK__ it will be easier to access via ttk.
Also, since the actual backup script won't care about names we can
just for loop over it and get all relevent information out of the tuple.
This is perfect for my purposes.

Bug fixes mainly focus around the checking to make sure we didn't get a
None element. Also there are a few try catch blocks added to allow us
to abort the project on the event that we have a corrupt xml scheme.
I want to try to catch those as soon as possible so that they aren't written.
If we can abort and not write our xml without it being clean then we
will save loss of data for the users who can't fix xml manually.

Signed-off-by: Barrett Lewis <musikal.fusion@gmail.com>
Using doxygen - fixed bumodel.py

Pushing the doxy information as well as the new bumodel with doxygen
style comments.

I have changed the name from Python Back Up to Python Bakup Utility:PyBakUP.

The new html documentation has been pushed with the project so that it is easy to access to those working on the code.
I know this might be premature but I want to use doxygen throughout the project since it is new ^_^
Switched to cleaner doxygen style

This means that '\' has been replaced with '@'.
cleaner code
Started Work on update for db

The work has begun for updating elements in the db. Doxyfile moved to
Doxyfile.doxy to fit with the dumb windows need for extensions.

The doxygen needs to be re run.
redoing xml

I am redoing how we manage the xml structure of the db
Updated the xml structure to make way more sense

The xml structure has been updated to be less error prone. Namely,
source and file have been moved to attributes of the bi tag.

The main problem was this, files and folders had unique tags. This made
no sense because we had to guess which was being backed up. The new
structure makes much more sense because tags are more meaningful.  I
tried to encapsulate meaningful things into their own tags so they can
be accessed as needed. I am not sure I am at an optimal set up yet but
it is orders of magnitude better than the last setup. Everything is
beginning to come together for the database interactions.
Updated the xml structure to make way more sense

The xml structure has been updated to be less error prone. Namely,
source and file have been moved to attributes of the bi tag.

The main problem was this, files and folders had unique tags. This made
no sense because we had to guess which was being backed up. The new
structure makes much more sense because tags are more meaningful.  I
tried to encapsulate meaningful things into their own tags so they can
be accessed as needed. I am not sure I am at an optimal set up yet but
it is orders of magnitude better than the last setup. Everything is
beginning to come together for the database interactions.

Signed-off-by: Barrett Lewis <musikal.fusion@gmail.com>
Updated the xml structure to make way more sense

The xml structure has been updated to be less error prone. Namely,
source and file have been moved to attributes of the bi tag.

The main problem was this, files and folders had unique tags. This made
no sense because we had to guess which was being backed up. The new
structure makes much more sense because tags are more meaningful.  I
tried to encapsulate meaningful things into their own tags so they can
be accessed as needed. I am not sure I am at an optimal set up yet but
it is orders of magnitude better than the last setup. Everything is
beginning to come together for the database interactions.

Signed-off-by: Barrett Lewis <musikal.fusion@gmail.com>
Merge branch 'feature-Backup_Model' of https://github.com/thebearbear/PyBakUP.git into feature-Backup_Model
Merge branch 'feature-Backup_Model' of https://github.com/thebearbear/PyBakUP into feature-Backup_Model
Merge branch 'feature-Backup_Model' of https://github.com/thebearbear/PyBakUP into feature-Backup_Model

Signed-off-by: Barrett Lewis <musikal.fusion@gmail.com>
Merge branch 'feature-Backup_Model' of https://github.com/thebearbear/PyBakUP into feature-Backup_Model

Signed-off-by: Barrett Lewis <musikal.fusion@gmail.com>
Merge branch 'feature-Backup_Model' of https://github.com/thebearbear/PyBakUP into feature-Backup_Model
Merge branch 'feature-Backup_Model' of https://github.com/thebearbear/PyBakUP into feature-Backup_Model
cleaned up output for temporary menu
Ran Doxygen to update api for the model
Moved the model into the main stream.

The model I think is finished now. I thinkt hat for at least the most
part it is ready to use, but if this is incorrect we can always add more
to it.