I know it's designed that way. But it's the design I am questioning.
I think it's too confusing for everyone to have a separate COMPIZ_CONFIG_CONTEXT and COMPIZ_CONFIG_PROFILE.
Best I can tell, the context (which is what COMPIZ_CONFIG_PROFILE really is right now) is the name of the entry to look up in .config/compiz-1/compizconfig/config. It seems to be designed that way so you don't need multiple variables for COMPIZ_CONFIG_BACKEND, COMPIZ_CONFIG_INTEGRATED, COMPIZ_CONFIG_PLUGIN_LIST_AUTOSORT etc.
But it could be simpler...
What if COMPIZ_CONFIG_PROFILE actually represented the profile and we paid attention to COMPIZ_CONFIG_BACKEND? Then you would have enough information to always find the profile data. Information like integration=false could be stored in the backend as part of the profile itself. Thus if both variables are set you can ignore and live without the ini file.
I know it's designed that way. But it's the design I am questioning.
I think it's too confusing for everyone to have a separate COMPIZ_ CONFIG_ CONTEXT and COMPIZ_ CONFIG_ PROFILE.
Best I can tell, the context (which is what COMPIZ_ CONFIG_ PROFILE really is right now) is the name of the entry to look up in .config/ compiz- 1/compizconfig/ config. It seems to be designed that way so you don't need multiple variables for COMPIZ_ CONFIG_ BACKEND, COMPIZ_ CONFIG_ INTEGRATED, COMPIZ_ CONFIG_ PLUGIN_ LIST_AUTOSORT etc.
But it could be simpler...
What if COMPIZ_ CONFIG_ PROFILE actually represented the profile and we paid attention to COMPIZ_ CONFIG_ BACKEND? Then you would have enough information to always find the profile data. Information like integration=false could be stored in the backend as part of the profile itself. Thus if both variables are set you can ignore and live without the ini file.