Every week the MooTools developers have an IRC office hour meeting where they work together to listen to your feedback, answer your questions, and develop on MooTools. We do this every Tuesday at 11am EST at #mootools Freenode IRC Channel. Everyone's welcome so join us tomorrow.

This recap includes:

• Compare 1.3.x and Experimental 2.y.x Code Diffs


• Things to Come (Agenda'ed Office Hour, Dedicated "Hackathon" Office Hours)

Last week we had a small conversation of the experimental branch that Valerio has for MooTools 2.0. The conversation covered most of the comments in last week's post comments. Instead of going over them again, please take a look at last week's post.

Compare 1.3.x and Experimental 2.y.x Code Diffs

Like I had promised last week, I did want to start a repository for helping you understand what are the main differences (in code) between 1.3.x and the experimental 2.y.x. Last week the mootools-1-vs-2 repository to do just that. You can use Github's awesome Compare View to view the differences between 1.3.x and 2.y.x (Valerio's experimental branch).

The files included in the repo are meant to compare Core code, Plugin code, and Application code:

Core Code

• Request.js is from the MooTools Core/Request.

Plugin Code

• Database.js (by Daniel Buchner). You can find the original Database.js in the repo as well as in his csuwldcat/mootools-htmlx.




• ScrollSpy.js (by David Walsh). You can find the original ScrollSpy.js in the MooTools Forge.

Application Code

• Examples/001.js and Examples/002.js are examples from the Request.js documentation.

Caveats

The examples are not all encompassing of user behavior and usage. I did select the scripts, but I tried to be fair. You can fork the repository and add your files to the 1.3.x branch (the base branch) and send me a pull request and I'll try to port your code. Please be considerate, and send me at most one file with recommended maximum of 500 lines.

The code will change as 2.0 is further defined. The 2.0 API is not final. Valerio is kicking butt everyday on his experimental branch. This compare 1.3.x vs. 2.y.x repo. is meant to assuage some of the concerns from the previous blog post about Valerio's experimental 2.0 branch.

This repo is not a definitive guide to 2.0. We're still working on that definitive guide for 2.0, but since the API is not strictly defined it's premature to give you this. For now, leave your comments or join us tomorrow with your questions.

The repo doesn't show Host.Install. The intention of the repo. is to show the default behavior of 2.0. I'm likely to create another branch and call it 2.y.x-installed so that you'll see the differences between 1.3.x and 2.0.x with native extensions installed.

Things to Come.

Agenda for the Office Hours

We were asked that Office Hours should have an agenda so that we can have a more directed conversation. I didn't have a chance to inquire the team for items, but we should have some items for next week.

Any suggestions? Leave a comment below.

Mini Hackathons or "Dedicated" Office Hours

Similar to the above, it's been suggested by Darren Wadell and Arian Stolwijk that we could dedicated actionable work hours. We could have demos office hour, documentation, bugfix or test office hours for example.

What do you think? Would you participate?

Next Office Hour

Remember that we're having the next office hour this:

Tuesday, July 12th at

05:01 - Honolulu (Hast UTC-10)

08:01 - San Francisco (PDT UTC-7)

10:01 - Chicago (CDT UTC-5)

11:01 - New York (EDT UTC-4)

12:01 - Rio de Janeiro (BRT UTC-3)

16:01 - London (BST UTC+1)

17:01 - Vienna (CEST UTC+2)

20:31 - Mumbai (IST UTC+5:30)

23:01 - Hong Kong (HKT UTC+8)

00:01 - Tokyo (JST UTC+9)

01:01 - Sydney (EST UTC+10)

03:01 - Auckland (NZST UTC+12)

We’ll be in the #mootools freenode.net channel.

Guidelines

We did very well last week in following the guidelines. I've included them in this post as a reminder.

1. Please use jsfiddle.net and keep your code with minimal boilerplate — get to the essence of your question


2. Stay on topic. Let’s keep the chat around MooTools and how it interacts with your code and the rest of the JavaScript ecosystem.


3. Be courteous and helpful with others. We are not guaranteeing that all of us will give you our undivided attention during the hour (we are also working!). If you can answer a question (as best as you can) it will really be helpful.


4. Sharing is caring. Share the room, but also share the event. Post to twitter, Facebook, your blog, and tell your parents. We want to foster growth in our community. This is the chance to participate and to help.

Tips

Use this button to add the open office hour to your Google Calendar. You'll need to setup the event so that it repeats weekly.




If you don't have an IRC client you can use http://webchat.freenode.net/.