Hi guys, I'm thinking about how to accelerate the saving of the mitk scenes. The slowest part for my scenes is definitely saving the image every time the scene is saved. But the image normally doesn't change in my case so it's a huge waste of time.
So it seems rather straightforward how project saving should be modified: - introduce the idea of currently open project - replace the open action with "open project" action and "import file" action that would be equivalent to what open action does now - open project action should take note of the original project file and record the data time stamps at project opening time - on project saving, check if we are saving to same file and if yes, then save only datas that were modified and use poco's zipmanipulator to update the scene file. The last step could also be represented by two actions - save and "save as". The question to you is: should I implement this in my local application code -or- inside MITK code so that it could be integrated into MITK? Rostislav. PS: one more thing is possibly support for "external references" - i.e. just save the path to imported files and use it at load time without saving the data to the scene file. However I feel that this approach would have more potential pitfalls and would require more changes to the MITK code. ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ mitk-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mitk-users
