no structure for object differences between App 1 and App 2.

Before this was going to be done with an appOne() and appTwo(). But now it might be a lot less convoluted to have the job prepping done separately and already be ready before the process of launching imacros and using it.

Then with the job order ready, links can be created in a list that is then iterated through. Example list would be a text file like:

http://localhost/thelaunch/app/one
http://localhost/thelaunch/app/three
http://localhost/thelaunch/app/two
http://localhost/thelaunch/app/one
maybe even http://localhost/thelaunch/app/one?config1=blah&config2=nah&amp...

This takes out a lot of the annoying calculating at the beginning of the script and forces more organization and understanding of code since the databases will be known and so the app, focus, task, model, and corresponding classes will be able to be set and known from the start.