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

Some thoughts on doing breakpoints persistent

<< < (8/9) > >>

MortenMacFly:

--- Quote from: oBFusCATed on December 15, 2012, 12:14:14 pm ---What about the code used to save .depend, .layout, .bmarks files?

--- End quote ---
Al-right... now I know what you mean. I thought you only think about the .layout stuff and additional stuff.


--- Quote from: oBFusCATed on December 15, 2012, 12:14:14 pm ---I was thinking of providing a function like GetUserFilePath(...)

--- End quote ---
Well what about if you return a proper file instead and simply change the the methods to create its own node in this fiel instead of creating an new one? The file would look then like:


--- Code: ---<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_meta_data_file>
  <debugger>
    <bmarks>
    </bmarks>
    <connectivity>
    </connectivity>
  </debugger>
  <core>
    <layout>
    </layout>
    <stuff_from_core_like_project_settings>
    </stuff_from_core_like_project_settings>
  </core>
</CodeBlocks_project_meta_data_file>
--- End code ---

Note that with the .depend file it is different: It comes from a 3rd party lib and we cannot change it to something else, nor integrate it,not even move it most likely without changing the depends lib.

...whatever we choose it requires some refactoring, for sure.

oBFusCATed:
This is another option, but it is more limiting, because all files should be saved in xml format.

And yes, some refactoring will be required anyway.

ollydbg:

--- Quote from: MortenMacFly on December 15, 2012, 02:39:07 pm ---Well what about if you return a proper file instead and simply change the the methods to create its own node in this fiel instead of creating an new one? The file would look then like:


--- Code: ---<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<CodeBlocks_project_meta_data_file>
  <debugger>
    <bmarks>
    </bmarks>
    <connectivity>
    </connectivity>
  </debugger>
  <core>
    <layout>
    </layout>
    <stuff_from_core_like_project_settings>
    </stuff_from_core_like_project_settings>
  </core>
</CodeBlocks_project_meta_data_file>
--- End code ---


--- End quote ---

The sdk can have a interface like:

--- Code: ---Manager::Get()->GetProjectMetaDataManager(_T("core"))         //Get the "core" Node.

--- End code ---
which return a Node pointer, then the client plugins can write and wrote on these Node/blocks.

oBFusCATed:

--- Quote from: ollydbg on December 15, 2012, 02:58:03 pm ---The sdk can have a interface like:

--- Code: ---Manager::Get()->GetProjectMetaDataManager(_T("core"))         //Get the "core" Node.

--- End code ---
which return a Node pointer, then the client plugins can write and wrote on these Node/blocks.

--- End quote ---
Doesn't like.

ollydbg:

--- Quote from: oBFusCATed on December 15, 2012, 03:25:06 pm ---
--- Quote from: ollydbg on December 15, 2012, 02:58:03 pm ---The sdk can have a interface like:

--- Code: ---Manager::Get()->GetProjectMetaDataManager(_T("core"))         //Get the "core" Node.

--- End code ---
which return a Node pointer, then the client plugins can write and wrote on these Node/blocks.

--- End quote ---
Doesn't like.

--- End quote ---
:), I'm not good at design interface, so can you give a good way? How can the interface like?

Navigation

[0] Message Index

[#] Next page

[*] Previous page