Ideas on configuration file handling for my plugin

  • Adrian

    Adrian - 2014-02-05

    I am developing a Notepad++ plugin, it needs a configuration file. At the moment I can consider any file format, including XML, INI and CSV.

    I have several related question about handling config files:
    1. How do other plugins read their config files?
    2. Does Notepad++ have any inbuilt utilities for reading config files?
    3. What other libraries are recommended for handling config files?
    4. How do plugins report errors in their config files?

  • dail8859

    dail8859 - 2014-02-05
    1. Most plugins I've seen use INI files or similar to their format. Although as you stated XML, CSV, etc are also options.
    2. No. It uses the TinyXML library for reading its own configs but if you wanted to use that you would have to link TinyXML manually while building your plugin.
    3. Various depending on your format. The Window's API has built in functions for handing INI files, which makes it convenient to work with as long as your config file doesn't need to be too complex.
    4. Normally with a MessageBox to let the user know there is a problem. Assumably this would give a message descriptive enough for the user to fix the problem.

    Hope this helps! :)

    Last edit: dail8859 2014-02-05
  • Adrian

    Adrian - 2014-02-10

    Thank you, Dial, for the information. I was hoping to get a little more in the way of recommendations on what to use for configuration file handling.

  • dail8859

    dail8859 - 2014-02-10

    This is highly dependent on what type of file you go with and what language you plan on programming in. You could read and write directly to a file with your own custom format using ordinary file IO operations.

    For INI files you can use the Windows API for WritePrivateProfileString and GetPrivateProfileString or the multiple related functions. You can see an example usage of these here. There are also other third party libraries for INI handling.

    TinyXML seems popular for XML files and I'm sure there are many others.

    Same goes for CSV and other popular formats.

    You can also look at other plugin's source code to see how they do it too.

  • Dave Brotherstone

    INI files are often used when a plugin is written in the same style as N++, ie. raw Win32 C++. If you're working in another language (for instance .NET), then you've got a lot more options. INI files have the advantage (as dail8859 mentioned) of having simple native APIs to read and write values. The disadvantage, is they only work for simple values (so nested trees of configuration isn't going to work very well), and if you're reading a lot of values they are relatively slow. Note the emphasis on relatively there, realistically, you're not going to notice reading 20-30 options in at startup. As a comparison, Python Script has it's own format for it's startup configuration file, because it wants to load all values in, and do it as quickly as possible, as it affects N++ startup time. Realisitically, it probably doesn't make any difference, but felt like the right thing to do at the time.

    What is more important, is how you handle your configuration. Definitely use NPPM_GETPLUGINSCONFIGDIR to get the directory where you should store the config. Do you really need the configuration to work, or will a default do most of the time? Message boxes are OK, but it's sometimes better not to irritate the user until they want to use your plugin. XML Tools changes it's menu items when it's not installed properly, I think it's ASpell that does this when it's not configured correctly (it needs a path setup). This is quite easy to do (just check your configuration and give back a different response in getPluginMenuItems).

    Whatever format you go with, I'd recommend adding some kind of version number to your config. That makes it easy to notice if someone had an old version, and perform an upgrade.

    There's some further notes on that may or may not be useful.



Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks