wxAUI class renaming proprosal

[Benjamin Williams]

Hi everyone,

A few threads ago the idea of a large wxAUI class renaming was
proposed.  As I'm not against this myself, I'd like to ask everyone
for their comments before proceeding one way or another.

The way I see it, the options are 1) go ahead with a large class
rename, 2) rename wxAuiMultiNotebook only, or 3) do nothing.  Julian
had pointed out that putting a "wxAui" prefix at the beginning of
every class would bring a certain continuity to the library and more
easily allow developers to discover less-known parts of wxAUI.

The only disadvantages that I can think of are that everybody will
have to change their code that calls wxAUI, and two, it might be a
little more verbose to code with wxAUI.

Almost all constants already have a wxAUI_ prefix.


Aggressive renaming would yield:

    wxFrameManager -> wxAuiManager
    wxFrameManagerEvent -> wxAuiManagerEvent
    wxPaneInfo -> wxAuiPaneInfo
    wxFloatingPane -> wxAuiFloatingPane
    wxDockArt -> wxAuiDockArt
    wxTabArt -> wxAuiTabArt
    wxAuiMultiNotebook -> wxAuiNotebook
    wxAuiNotebookEvent -> wxAuiNotebookEvent
    wxTabMDIParentFrame -> wxAuiMDIParentFrame
    wxTabMDIChildFrame -> wxAuiMDIChildFrame
    wxTabMDIClientWindow -> wxAuiTabMDIClientWindow

Originally my intention was to simply rename the notebook class:

    wxAuiMultiNotebook -> wxAuiNotebook (or some other name)
    wxAuiNotebookEvent -> wxAuiNotebookEvent

So what would everyone like to see?  If we do decide to undertake a
large class rename, now is the time to do it, because this is the
first time wxAUI will be included in a stable release.

All the best,
Ben