Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Some thoughts on doing breakpoints persistent

<< < (3/9) > >>

MortenMacFly:

--- Quote from: oBFusCATed on June 16, 2009, 03:55:10 pm ---There should be only one file looking like:

--- End quote ---
Sure not! I don't want to share my breakpoints with other developers on the same project.

So settings like BP's cannot be in the project file. Because that's what you share with other developers. In addition it would be modified every time you change a BP. However - important settings about the setup of the debugger itself (e.g. parameters for a remote connection) belong into the project file so that's why we have that "debugger" section there.

So it would not be 100 files. It's a 1:1 relation to your project file. but it's local ("for your eyes") only because that's how the use case is in the end.

oBFusCATed:
Yes, I'm not saying to put the user settings in the project file.
I'm saying that I don't want to have 10-20 files in my project dir:
myproject.layout
myproject.bps
myproject.books
myproject.svnplg
myproject.whatnot

but just one:

myproject.user.settings (for example) that is not in svn as the other.

ollydbg:
I suggest the first step is to use separate setting files.

then after that, we can combine them together, I'm concerning mutiply-accessing to single file from different plugins will cause conflicts.

MortenMacFly:

--- Quote from: oBFusCATed on June 16, 2009, 05:06:40 pm ---myproject.user.settings (for example) that is not in svn as the other.

--- End quote ---
Agreed.

--- Quote from: ollydbg on June 16, 2009, 05:40:30 pm ---I'm concerning mutiply-accessing to single file from different plugins will cause conflicts.

--- End quote ---
Indeed. So the only solution I see is that the core provides methods to the plugin to write settings into a file handled by the core. This way all plugins have the possibility to store their (volatile) information in a file other than the project file. Still plugin may need own config files. So we cannot ensure it'll stay a single file.

oBFusCATed:

--- Quote from: MortenMacFly on June 16, 2009, 06:01:01 pm ---Indeed. So the only solution I see is that the core provides methods to the plugin to write settings into a file handled by the core. This way all plugins have the possibility to store their (volatile) information in a file other than the project file. Still plugin may need own config files. So we cannot ensure it'll stay a single file.

--- End quote ---

We talk about data per project.
If a plugin needs some global configuration, the core can(must) still provide an interface for storing settings.

Navigation

[0] Message Index

[#] Next page

[*] Previous page