This is the P2PU Archive. If you want the current site, go to www.p2pu.org!
Reading Code
My recent threads
- Week 7. Sun, 2010-10-31 19:32
- Week 4: Node.js and Javascript frameworks Wed, 2010-10-13 14:49
Recently updated threads
- ANNOUNCE: New site on Stack Exchange: Code Review Fri, 2011-01-28 16:38
- Course wrap up and output: Notes on Reading Code Fri, 2010-11-05 21:48
- Week 7. Sun, 2010-10-31 19:32
- Tools for Reading Code Thu, 2010-10-28 16:52
- Week 6: Storage! MongoDB and HTML5 Web Storage Sun, 2010-10-24 20:44
Week 4: Node.js and Javascript frameworks
Go back to: General discussion
Hola a todos:
I'll begin by sharing this nice video about Jquery's source, which proved very helpful to understand this library:
http://paulirish.com/2010/10-things-i-learned-from-the-jquery-source/
This week we're covering two different languages,C with node.js and javascript with the Jquery library and other js frameworks; so even as every project is different on its own, I guess we would be studying different paradigms this time.
What do you think of this?, can we find some common ground between these projects? (from a developer's perspective, not an implementation or user's view). You're welcome to share some Node.js articles and findings as well.
Thanks,
Manuel
Hi Manuel! (and all! ) Wow , sorry I just realized I never followed up ater I missed Sunday. You guys are rockstars, thanks so much for pushing forward with the class this week! I have a very unexciting excuse unfortunately...I could not get online for the life of me on Sunday (our Internet connection at my apartment can be intermittent sometimes and especially on IRC that's a killer). This week I've been so busy with deadlines for my own classes (being a student that is, not a facilitator) that I've been completely consumed and had my head down :(.
I'm very sorry. But it seems like you're all plugging along just fine :). Did you find some good ticket trackers for node.js and Jquery, to use as starting points? I thought that was a great idea last week.
Sorry again for missing last Sunday and being completely MIA for a few days!
Jessy
I'm glad that it was nothing too serious...
Welcome back Jessy!
Jquery Bugtracker: http://dev.jqueryui.com/
Node.js has a mailing list: http://groups.google.com/group/nodejs, but I haven't seen any bugtracker.
Node's github page has a lot of articles as guidelines though.
Hey there!
I wasnt attending last week's chat because I had been sick. But I'm back and ready for this week's frameworks!
I'd love to have a look at both Node.js and JQuery, but I guess I'll start with Node.js.
Happy Code Reading!
Today's meeting transcript. http://pastebin.com/XQZx5LYy
Hi all! Last sunday I was in a bad connectivity area, and from the transcript it seems that people were finding node.js and jquery pretty dense. so let's keep going with those this week, and meet again on sunday at our regular time to discuss. How does that sound?
For bugs and tickets:
1. here you can find jquery's bug tracker with tickets sorted by priority:
http://bugs.jquery.com/query?status=!closed&report=18&desc=1&order=priority
2. and here are the node.js tickets, which are available in github:
http://github.com/ry/node/issues
About choosing bugs to track down: Having a bug, issue or feature request to track down in the code is a helpful way to focus our explorations. but some are harder than others. look for bugs that are well documented, giving clear instructions as to how to replicate. look for specific function calls being described in the ticket body. Ideally, try to focus on issues that apply to the current version of the software-- and at the very least make sure you have the same version as the one where the issue is reported. and finally, it will be difficult to track down bugs that are OS or hardware specific if you don't have matching system configuration, so keep an eye out for that as well.
As a starting point, here's a couple of tickets that look appropriate for us:
http://github.com/ry/node/issues#issue/143
http://github.com/ry/node/issues#issue/168
http://bugs.jquery.com/ticket/1118
http://bugs.jquery.com/ticket/1292
http://bugs.jquery.com/ticket/1728
Remember we're not necessarily trying to fix the bugs-- think about it this way (in increasing order of effort/difficulty!):
0. if posible, try to replicate the issue yourself
1. try to understand where it is occurring in the code
2. try to understand WHY it is happening
3. think conceptually about how you might fix it
4. if the bug tracker allows for comments, consider commenting with the results of your investigation so that others can benefit from your work!
5. feel free to muck about with our forked versions of the code of both projects, available at http://github.com/p2pu/
Regarding meetings-- if people want to have an additional meeting or if you are finding the meeting time difficult, let me know and we can try and work out an additional time!
Now that i'm back in town i'll try to be on the IRC channel more frequently again. Let us know how it's going!
Cheers,
Jessy
ps. If you still need access to the github team, let me know and i can add you.