Tools/Run Parameters storage in .lps/session file instead of lpi
Original Reporter info from Mantis: BigChimp
-
Reporter name: Reinier Olislagers
Original Reporter info from Mantis: BigChimp
- Reporter name: Reinier Olislagers
Description:
Each developer may have their own aspect of the application they're
testing and can therefore have different needs. It may make more sense to store the Tools/Run Parameters in the .lps/session file instead of the lpi file.
Another argument for this: working together in a team using (distributed) revision control software, conflicts/differences may appear in the .lpi file solely because devs changed the run mode.
Additional information:
Adapted from reply by Mattias Gaertner on lazarus ml today:
\- Many developers use both the released IDE and the trunk IDE. So<br/>
if possible try to keep backward compatibility. Simply moving a value
from lpi to lps breaks this.
- Often it is needed to have various sets of run/debug parameters.
Often these are not the same as "build modes", so they should be a
separate set. Maybe they can be called "run modes".
- All settings in the run parameters dialog should go into that.
- the build modes solves the backward issue, by saving the first build
mode always at the old place of the lpi. For every other build
mode the user can choose where to store it - the lpi or lps. We can do the same with the run mode; having the first one as a project default and allowing devs to store additional settings in .lps files locally
Mantis conversion info:
- Mantis ID: 21379
- OS: Windows
- OS Build: Vista
- Build: 33549
- Platform: x64
- Version: 0.9.31 (SVN)
- Fixed in revision: 56762 (#c03b9416)