Hi,
I'm just canvassing the list to see if there are any objections /
thoughts on my registering the Wx::Perl::LogGui namespace on CPAN.
I'm currently testing wrapping Wx::PlLog::Flush and producing my own
custom Wx::LogGui class.
Why bother?
The built in Wx::LogGui class causes me problems when there is just a
single message in the buffer when flushed and therefore wxMessageDialog
/native message dialog is used. Apart from showing completely different
dialogs for essentially the same message on occasions (which looks a bit
confusing on some platforms with my particular usage), the focus /
positioning of the dialogs is different depending on which dialog class
is used to display the messages.
So, I want my own custom gui log that always uses a custom dialog and I
can control positioning and focus / modality. Seemed a candidate for CPAN.
Modules will be named
Wx::Perl::LogGui - the wxLog part
Wx::Perl::LogGui::LogWindowBase - base class for dialog implementaions
Wx::Perl::LogGui::LogWindowListCtrl - default (Perl implementation of
existing wxLogGui::Window behaviour)
Wx::Perl::LogGui::LogWindowGrid - I want to use a grid implementation
for message display so I may as well CPAN that too.
Regards
Mark
