Here is something that tricked me more than a few times:
When using my Python extension with LOEclipse, debugging (understandably) happens in some file under dist/.ooo-debug (where the extension is installed to).
Now under Python, ".py" files are run, so it is really, really tempting to modify them during / shortly after debugging. But this is a trap: They're not the "source" files (under source/ or classes/) but the distribution files.
This (more or less) leads to losing my edits when I re-run the extension.
It would be great if LOEclipse could prevent me from editing the wrong files.
I'm not sure how to achieve that (making them read-only? making them links to the real file?), but it's really easy to get wrong and I felt very bad when it happened.
Thanks for making LOEclipse!
Here is something that tricked me more than a few times: When using my Python extension with LOEclipse, debugging (understandably) happens in some file under
dist/.ooo-debug
(where the extension is installed to). Now under Python, ".py" files are run, so it is really, really tempting to modify them during / shortly after debugging. But this is a trap: They're not the "source" files (undersource/
orclasses/
) but the distribution files. This (more or less) leads to losing my edits when I re-run the extension.It would be great if LOEclipse could prevent me from editing the wrong files. I'm not sure how to achieve that (making them read-only? making them links to the real file?), but it's really easy to get wrong and I felt very bad when it happened.