On Thu, Feb 23, 2012 at 7:20 AM, Jesse Vander Does <[email protected]> wrote:
>> Go get the latest source from git and get busy! Do you have commit >> privileges? > > I don't have commit privileges, but I do have the source and have done some > of the easier changes already. Let me know how you'd like me to go about > contributing. send me an ssh public key, i'll add you to the list - in the meantime, actually go ahead and commit the changes *as if* you had commit rights (with proper commit messages and everything, and adding yourself to the pyjamas/copyright file) then use "git format-patch" command to create a set of diff patch files, attach those to a bugreport at http://code.google.com/p/pyjamas/issues. > I know this is a bit of a sore subject, but figuring that if I were to do > substantial contributions I would need to test with pyjd, not just pyjs, I > went and attempted to get pyjd running on my ubuntu image. It was too hard, > and I gave up. yyyup. perfectly understandable. there's several ways - possibly the easiest one is to set up a dchroot environment with debian/lenny and then xulrunner 1.9.1 is a dead-easy job. the only thing is you end up going back to python 2.5 for that, but hey: as it's for the front-end development *only* that's not so much of a big deal, and it's entirely in the chroot environment anyway. i'm more than happy to walk you through the process, whatever you choose. often it's something simple that was missed. you don't *have* to struggle on your own, you know - it's not a macho "rite of passage" or anything :) > I know developing pyjs without pyjd is dumb, but that's how > I've been doing it for my personal apps and unless I find a day where I feel > strangely driven to get pyjd running its probably how things will be for a > while. *lol* - well, the thing is that that's a choice you'll have to live with - feel free to see how far you get on. many people have said "my god, why did i struggle with only pyjs for so long??" after being restricted to the limited debugging capabilities inherent in web browser engines (which pyjs really, really can do absolutely nothing concrete about, short of getting people into microsoft, google, apple _and_ the mozilla foundation and banging some heads together). l.
