wxPerl has a lot of moving parts. I started thinking out loud about how to
keep these parts moving. Feel free to provide additions.

James

wxPerl Issues - January 6,2016
--------------------________----------
(Thinking out loud in outline form)

What does it take to keep the wxPerl infrastructure viable and who is
taking the lead?

wxPerl Language Support
    Bug Fixes(Mark & ?)
    wxWidgets Tracking(Mark & ?)
    Perl 5 Tracking
    Perl 6 Adaption(?)
    wxDemo(Mark & ?)
    Extensions Beyond wxWidgets(Steve's Comments)
    Documentation of the package/Software Maintenance Manual

wxPerl Website Support
    Ownership(?)
    Financial(?)
    Administration(?)

wxPerl Installation
    From CPAN
    From Source By Platform - Mac/Windows/Linux

wxPerl Deployment(Stand Alone)
    Packaging By Platform - Mac/Windows/Linux

wxPerl Documentation - The "Learning wxPerl" Book
    Introduction
    Simple Application Structure
    Windows/Frames
    Controls/Widgets
    Events
    Dialogs
    Sizers
    Drawing/Printing
    Images
    Other
    Advanced Topics
        Custom Controls
        Custom Dialogs
        SubClassing Base Widgets
        Wrapping External Libraries
        Complex Application Architecture
        Database Access
    Appendices
        Language Constants/Defines
        Simple Application Template
        Dummy C/C++ _Library and it's wxPerl Wrapper
        Examples
        User Contributed Controls/Dialogs

wxPerl Resources
    wxDemo
    Wiki - wiki.wxperl.nl
    Email List - wxperl-users@perl.org
    Email Archive -www.nntp.perl.org/group/perl.wxperl
    wxperl.it
    sourceforge.net/projects/wxperl
    The wxBook - "Cross-Platform GUI Programming with wxWidgets" Smart,
Hock, & Csomor
    wxWidgets HTML Documentation

Other

Reply via email to