The golden rule is "What can you get to compile on all three platforms".
If you can make the underlying libraries compile and install, everything else is largely pointless. So I'm in favour of whatever we can build an Alien:: package for. Adam K On 10 February 2010 10:51, Patrick Donelan <[email protected]> wrote: > First question I guess is.. why Gecko-based wxWebConnect instead of > Webkit-based wxWebKit? > Then we need to figure out how to create the Perl bindings. > Cheers, > Patrick > > On Tue, Feb 9, 2010 at 6:45 PM, Ahmad Zawawi <[email protected]> wrote: >> >> Hi Patrick, >> Sorry for the slow response time but I have been busy lately with >> different life ventures :) I am interested in this project especially the >> XULRunner wxWebConnect. How do we start then? >> Regards, >> Ahmad >> >> On Tue, Feb 2, 2010 at 1:57 PM, Patrick Donelan <[email protected]> wrote: >>> >>> I've been following up with Ryan Jendoubi about the Wx::Perl::WebKit >>> project he worked on for last year's GSoC as I'd really love to be able to >>> embed webkit inside of Padre. Does anyone have >>> interest/skills/tuits/suggestions to help move this along? >>> Cheers, >>> Patrick >>> On Tue, Feb 2, 2010 at 10:20 PM, Ryan Jendoubi >>> <[email protected]> wrote: >>>> >>>> Hi Patrick, >>>> >>>> Good to hear from you. >>>> >>>> The project, such as it is, is up at http://gitorious.org/wx-perl-webkit >>>> . (Sorry it's in a bit of a state - repo management, like pretty much >>>> everything else I did on the project, was completely new to me, and kinda >>>> still is). After the end of last year's GSoC I've somehow got distracted, >>>> although I've been preparing recently to try to go back to it. >>>> >>>> I'm afraid it's not really ready to ship. Last I checked there was a >>>> problem in the GNOME rendering in the wx upstream which was a bit >>>> embarrassing. Also I remember there was an issue with wxWebKit being an >>>> MSVC-only build on Windows, which I think put it in conflict with >>>> Strawberry? I can't honestly remember if that ever got straightened out. >>>> The >>>> maintainer was quite open to the idea of patches to make it mingw >>>> compatible, and that's something else I would like to look at, but honestly >>>> I wouldn't know where to start (although he said that for pretty much >>>> anyone >>>> it would be a semi-mechanical process of compile -> fail -> fix -> repeat). >>>> >>>> I never looked into it, but a possible alternative might be wxWebConnect >>>> [0], which as of five months ago at least seemed to offer several big >>>> advantages: >>>> >>>> 1) XULRunner is loaded dynamically at run time.[1] I'm not sure if this >>>> means you can use the version present on a user's machine, or if it just >>>> means you don't have to link it with your program so avoid a lot of >>>> potential grief there. Come to think of it, I'm not sure how this 'benefit' >>>> would mirrored over to Perl in practice... >>>> 2) It seems to be presented / backed by a Company, which even if they >>>> only have one go-to guy dedicated to the project, might well offer more >>>> support than the one go-to guy there is on wxWebKit, sans Company.[2] >>>> 3) Because it's XULRunner, you can embed plugins in your applications. >>>> Who knows what the tradeoffs between using an existing plugin and >>>> manipulating the DOM directly with Perl. Suppose it depends on how nice the >>>> API is to use. >>>> 4) Again since it's Moz, I'd be surprised if it was tied to MS compilers >>>> on Windows. >>>> >>>> Of course, the downside is someone would have to do the bindings from >>>> scratch. If you have a look at my project though, you might decide that you >>>> might as well start from scratch >.> Considering the potential benefits of >>>> wxWebConnect. >>>> >>>> As to skills: perl, c++, xs, xspp, perldb, gdb. But don't let any of >>>> those put anyone off, as none of these are skills I would claim to have :-p >>>> >>>> Since I can't commit to definitely doing any amount of work improving >>>> wxWebKit or starting on wxWebConnect in the coming weeks I'm not really >>>> much >>>> help to you, but I am full of Interest and Good Will, and am certainly up >>>> for answering queries about my project, if I can remember wth I was doing >>>> at >>>> any given point. At least it works better than the Wx::WebKit [3] module on >>>> CPAN from 2006, ey? >>>> >>>> All the best, >>>> >>>> -- Ryan >>>> >>>> >>>> >>>> [0] >>>> http://groups.google.com/group/wx-users/browse_thread/thread/d088dc08bb9d8f64/5c5b386f465889b4?#5c5b386f465889b4 >>>> [1] >>>> http://groups.google.com/group/wx-users/browse_thread/thread/d088dc08bb9d8f64/24be38815506ad3b?#24be38815506ad3b >>>> [2] kollivier is friendly and a great help on wxWebKit, but it could >>>> really use more contributors coming from the C++ end of things. Asking >>>> about >>>> it in either #wxwidgets or #webkit generally results in blank stares and >>>> advice that you should probably ask that kollivier guy, he's the guy that >>>> does that. Unlike some other toolkit bindings, wxWebKit tests are no longer >>>> officially part of the WebKit project, so it breaks more often than e.g. >>>> QtWebKet. As of five months ago kollivier was planning to get certain >>>> ickiness cleared up and then try to get piggybacked on Chrome development - >>>> not sure if that ever went ahead. >>>> [3] http://search.cpan.org/~dsugal/Wx-WebKit-0.02/lib/Wx/WebKit.pm >>> >>> >>> _______________________________________________ >>> Padre-dev mailing list >>> [email protected] >>> http://mail.perlide.org/mailman/listinfo/padre-dev >>> >> >> >> _______________________________________________ >> Padre-dev mailing list >> [email protected] >> http://mail.perlide.org/mailman/listinfo/padre-dev >> > > > _______________________________________________ > Padre-dev mailing list > [email protected] > http://mail.perlide.org/mailman/listinfo/padre-dev > > _______________________________________________ Padre-dev mailing list [email protected] http://mail.perlide.org/mailman/listinfo/padre-dev
