Currently, every deploy configuration has its own instance of the MaemoDeployables class. This is silly, because that information is only dependent on the current target, which is the same for all deploy steps. The same goes for the associated widget. So we waste space and, much more importantly for big projects, parsing time.
Possible solution: The first deploy step allocates the MaemoDeployables object, the others retrieve it from there. If the first deploy step is deleted, the ownership is transferred to the next one (or the object is deleted, if no deploy steps are left).