Sreve: I printed all/most of those references awhile back. I need to find and reread and see if they make any more sense than they did at first glance. I'm more of a C than a C++ guy, so it's more to get my arms around. I think a small, complete example would be helpful. Maybe a glossary of terms too.
James On Thu, Jan 14, 2016 at 6:18 AM, Steve Cookson - gmail < steveco.1...@gmail.com> wrote: > Hi James, > > I think you are right. > > I'm going to try to get my head around it. Mark suggested I did some > years ago, but somehow it never happened. > > There is some documentation to help us start, there is the NEWCLASS.POD, > that Mattia wrote and then Mark put some more comprehensive stuff on the > wiki. > > Basically you need to under stand what XS and XSpp do. > > It's quite easy to add most new methods to an existing class, just look at > wxPerl/XS and the class that you want. Eg look at XS/Slider.xs and you can > see a variety of methods like > > int > wxSlider::GetSelEnd() > > int > wxSlider::GetSelStart() > > int > wxSlider::GetThumbLength() > > int > wxSlider::GetTickFreq() > > You can just add one or delete one and then recompile wxPerl. > > cd ~/wxPerl > make install > > I'll send more emails as I get into it. > > Regards > > Steve. > > > > On 13/01/16 23:57, James Lynes wrote: > > I think the software maintenance and the tracking of enhancements to > wxWidgets will be the hardest of the tasks, mostly because those tasks seem > to require "internals" knowledge. I certainly don't have any current > experience in that area. A software maintenance manual maybe would open > this area up to more people. The flavors of Perl and the Win/Mac/Linux > platforms lead to a lot of combinations. > > I don't have a feel for the size of the wxPerl audience or the > distribution of experience from beginner to package maintainer. > > James > > > > > On Wed, Jan 13, 2016 at 2:31 AM, Steve Cookson - gmail < > steveco.1...@gmail.com> wrote: > >> Hi Mehmet, >> >> Thanks for your email. >> >> James' list does indeed look intimidating, but I hope once we start the >> momentum will build. >> >> Wx and Alien::Widgets are not abandoned, they are just under-resourced. >> >> Here is a list of recent updates at sourceforge: >> >> http://sourceforge.net/p/wxperl/code/HEAD/tree/ >> >> We here are all the maintainers. If we don't like something we fix it in >> our own environments and post it here. Mark will migrate it to the various >> repositories. >> >> We have had almost as much activity on the list in January 2016 than in >> the whole of 2015. Long may it continue! >> >> I don't have a Mac, but maybe I can help you with your installation >> problems. Are you still getting the same error? Ie "No wxWidgets build >> found.". >> >> Please remind us how you are installing. The purpose of Alien::wxWidgets >> is to install wxWidgets in a selected directory and then point wxPerl to >> it. There is normally a configuration file or environment variable that >> will point wxPerl (ie Wx) to the right directory. >> >> Please post your current status and I'll try to help you. >> >> Regards >> >> Steve. >> >> >> On 12/01/16 17:53, Mehmet Kayaalp wrote: >> >> On Fri, Jan 8, 2016 at 8:04 PM, James Lynes <jmlyne...@gmail.com> wrote: >> [...] >> > wxPerl Language Support >> > Bug Fixes(Mark & ?) >> >> I was looking for a proper pigeon hole to place my support request wrt >> wxPerl for Win-64 on ActivePerl >> <http://www.nntp.perl.org/group/perl.wxperl.users/2016/01/msg9577.html>. >> On the main wiki page, I found links to two support pages, Wx >> <https://rt.cpan.org/Public/Dist/Display.html?Name=Wx> and >> Alien::wxWidgets >> <https://rt.cpan.org/Public/Dist/Display.html?Name=Alien-wxWidgets>, at >> cpan, but they are not maintained. >> >> 41678 <https://rt.cpan.org/Ticket/Display.html?id=41678> *Can't build on >> OpenBSD perl 5.10 wxWidgets 2.8.7 >> <https://rt.cpan.org/Ticket/Display.html?id=41678>* open Critical 6 >> years ago 0.40 >> 0.41 >> 0.42 Maintainers of both sites are listed as MBARBON >> <https://rt.cpan.org/Public/Dist/ByMaintainer.html?Name=MBARBON>, and >> MDOOTSON >> <https://rt.cpan.org/Public/Dist/ByMaintainer.html?Name=MDOOTSON>. >> Clearly they abandoned the effort, or that is the impression I get from >> outside. >> Does anyone willing to take responsibility to maintain these pages? >> >> As I understand from you discussions, there is a new on-going reformation >> attempt. >> James' list is a good plan but it also seems overwhelming to approach, >> unless there is a prioritization in place. >> I would suggest assigning a high priority to making the existing software >> work on the current platforms with the latest versions of Perl/ActivePerl. >> >> My two cents. >> >> >> > >
