Or even, maybe a sql data file, then you can search with specific parameters (like user=x and accesslevel>y).
Or even, maybe a sql data file, then you can search with specific parameters (like user=x and accesslevel>y).
Well, that would be an option to store it and let an external system handle everything for me. The application will either define integer access levels or flags. What I'm interested in is a way to manage the config inside the program. I'd go with Q_PROPERTY's and some functions that would simply check for the USER property parameter to restrict access (using a function there that would ask an SQL db or LDAP dir), but that's insufficient as I couldn't really define limits for the settings. Basically, I'm not sure what the better approach is, but I've seen type-specific classes used to store one single setting, managed by a config class before and thought it's a nice and clear way to handle that. Do you think so too?
Bookmarks