develooper Front page | perl.wxperl.users | Postings from January 2013

Re: wxPerl past, wxPerl present and wxPerl future.

Thread Previous | Thread Next
Mark Dootson
January 2, 2013 16:38
Re: wxPerl past, wxPerl present and wxPerl future.
Message ID:

On 31/12/2012 15:45, Steve Cookson wrote:

> Mark has done a heroic act of maintaining the system and I personally
> owe him a huge debt of gratitude.  Our system would not be where it is
> today without his support.  But we should have two or three
> administrators of Mark's ability and knowledge (and patience, I should
> add).  We are all a bit shy about giving Mark the credit he deserves.
> I'd like to say here and now, that Mark's professionalism and
> thoroughness is a benchmark that I should like to aspire to.

All credits happily accepted. I should point out for new list readers 
that Mattia Barbon is the creator of wxPerl and deserves 100% of the 
credit for wxPerl existing at all. The clever design of the wxPerl 
wrapper means that someone like me is able to maintain and expand the 
current code-base. I have also found that folks in the wxWidgets c++ 
community are patient and willing to help where they can to accommodate 

I think the wxPerl code-base is in good shape for a wxWidgets 3.0 
release and I look forward to supporting it through that. In the 
meantime I'm sure I'll be kept busy accommodating operating system and 
build environment changes.

 From my own point of view, the greatest obstacle to other folks 
contributing to the Wx module development is that some knowledge of c / 
c++ is required or the motivation to learn. A contributor would also 
have to become familiar with how Wx builds - I have started what I think 
is a good way of explaining this in the source code in

This wraps an entirely pointless extension called wxPerlTest - but 
provides some simple self contained C++ classes that can be extended / 
altered to demonstrate the available features of the C++ pre-processor 
(ExtUtils::XSpp) and how you may use these to wrap C++ classes. I 
thought that most people find learning by reading existing code easier 
that straight documentation so I'll be expanding this part with further 
examples and comments in the future. Whilst wxPerlTest provides no 
useful function, it does provide methods that can be used in tests - so 
can provide a complete template for wrapping new classes or extensions.

I think that making it easier to contribute to Wx development is the 
best thing I can do. Mattia made it very much easier than It might have 
been so I'll just share what I learned along the way.

With regard to wxMediaCtrl, I feel your frustration.
One way forward maybe to adopt the approach of Wx::Scintilla. You could 
develop wxMediaStreamer as a separate C++ module, building inside a 
Wx::MediaStreamer distribution. That would make wxMediaStreamer 
potentially available to the wider wxWidgets community whilst directly 
giving you what you need within a Wx::MediaStreamer module. I would be 
happy to cooperate on this if you wish to go that way. I have no clue 
what wxMediaStreamer should do, but could help in getting a module / 
build system set up.



Thread Previous | Thread Next Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at | Group listing | About