Conventions and best practices for maintaining juce modules

[yfede]

@yfede

Would you consider naming the proxy files in JuceLibraryCode with a prefix or suffix to make them easily distinguishable, like use_juce_module.cpp, link_juce_module.cpp or juce_module_usage.cpp?

In addition, prepending the same prefix to all “proxy” files would also save from making an exception for the naming of resource files (which is, append a “_r” at the end of the name before the “.r” extension) that has been recently introduced in the following commit:

Added Rez files to JuceLibraryCode so that they are compiled when not browsable

To resolve the needs described in this topic:

Xcode “build carbon resources” build phase missing

the build carbon resources build phase missing in xcode if the module juce_audio_plugin_client is not browsable in projects (projucer). without the carbon resource the audio unit won’t load in logic pro. all modules are browsable in projects by default but i still thought this issue might be worth sharing. jucer_ProjectExport_XCode.h -> addRezFile is not getting called… klaus

After having seen how easily you did introduce a change in the naming conventions of those files, I am even more persuaded that my suggestion above is feasible.