Our naming rules are Qt-style. It means:
Example:
MeshLabClassExample
{
Q_OBJECT
private:
int privateVarName;
public:
bool publicVarName;
void setValue(int &);
}
There are no strict rules on naming files, except for dialogs files.
Include files must begin with the standard legal disclamier/license intestation and report in the first line of history the $LOG$ cvs string. The following automatically generated history can be, from time to time, compressed and shortened to save space.
No absolute include path are allowed.
Each file has to include all the files that it requires. An include file should rely on the files included by its own include files.
In Class definitions place all the prototypes all together before the inline or templated implementations.
Tabs are equivalent to two spaces.
There are no strict rules placing white spaces, '{' or indenting.
A dialog tipically comes with three files: .ui, .h, .cpp. Each new .ui file must be placed in the "meshlab/ui" subfolder and its name must followed by "Dialog" suffix. Related .h and .cpp files must follow same rule but placed in the "meshlab" folder.
Example (Settings dialog):
settingsDialog.ui -> "meshlab/ui"
settingsDialog.h -> "meshlab/"
settingsDialog.cpp -> "meshlab/"
Is very simple to create a working plugin. Just read here!