Messages
Reply
Edit
Delete11:12 am
3RG0O1E0G
| From: | Tuvia Vinitsky |
| To: | FoxInCloud support |
Maybe just do the copy, but work on the original using the copy as a backup.
FAA is designed to copy all dependencies and redirect any full path to the copy location.
We need to think of a global strategy to avoid copy, in which cases, with what safety, etc.
Quite a task ...
thanks anyway for any suggestion
Philisophic difference. In our apps we try and let the user have choices how to do those type of things and we try not to force it, although I admit there are times we do indeed force it when the user has too much riding on the opton.
I would prefer the FAA make a backup rather than forcing me to have it copy my entire project and folders elsewhere. The problem with copy mode is twofold: it takes a long time to copy and it is unlikely that al the parameters and environent wou;ld be replicated sufficiently enough to let the copy project actually work. I would assume most developers use source control as well. which cn mame a mess when you just copy things. OTOH I understand your fear of somebody emailing you "how do I undo this when I hae no backup".
we prefer that the user has a chance to test the adapted application in copy mode before switching to source mode
When you add a new project to the FAA, it autiomatically switches to copy mode and starts copying without prompting the user. ER to disallow this behavior.