<commit_before>
Here are some source code maintenance tasks that need to be done, and maybe some
folks will see these items and volunteer to do them.



*** Add hierarchical menu to right mouse click in PCBNEW for the case when
multiple items are under the mouse cursor.

   
*** Set up a DOXYGEN environment starting with a configuration file that:
- understands the JavaDoc style comments that we have started using
- gives preference to comments in header files over *.cpp files
- outputs its HTML stuff relative to the base of trunk, say for example trunk/doxygen
- is then added to the svn repository (this configuration file only) 
Then add a shell script and batch file to generate the docs using the config file.
Then review the generated docs and start to go through the source and make the 
generated doxygen docs readable and clear using the JavaDoc style comments,
mostly in the header files.  The error and warning output of the doxygen
compiler can help with this too.


*** Translate comments that are in French to English so there can be a broader
understanding by new developers.
<commit_msg>added first item<commit_after>
Here are some source code maintenance tasks that need to be done, and maybe some
folks will see these items and volunteer to do them.


*** make the ADD_MENUITEM macros in include/macros.h be static inline functions instead
of macros.  e.g. w/o argument types:
static inline void ADD_MENUITEM(menu, id, text, icon)
{
    wxMenuItem * l_item;
    l_item = new wxMenuItem(menu, id, text);
    l_item->SetBitmap(icon); menu->Append(l_item);
}


*** Add hierarchical menu to right mouse click in PCBNEW for the case when
multiple items are under the mouse cursor.

   
*** Set up a DOXYGEN environment starting with a configuration file that:
- understands the JavaDoc style comments that we have started using
- gives preference to comments in header files over *.cpp files
- outputs its HTML stuff relative to the base of trunk, say for example trunk/doxygen
- is then added to the svn repository (this configuration file only) 
Then add a shell script and batch file to generate the docs using the config file.
Then review the generated docs and start to go through the source and make the 
generated doxygen docs readable and clear using the JavaDoc style comments,
mostly in the header files.  The error and warning output of the doxygen
compiler can help with this too.


*** Translate comments that are in French to English so there can be a broader
understanding by new developers.

{'fraction_non_alphanumeric': 0.0384006334125099, 'fraction_numerical': 0.0, 'mean_word_length': 4.1676891615541924, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 5, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1704831', 'n_tokens_mistral': 631, 'n_tokens_neox': 598, 'n_words': 397}