What's going on with MooTools
Below is a translation of today's post one of the developers of MooTools in google groups.
I'm writing this post on the mailing list to tell the MooTools community about what the developers were doing these days and what will happen with the framework. We are all tired of answering the same questions over and over, so I hope this post will make something more clear, and we stop to see the same thing over and over again in the mailing list.
Many of you think that we have abandoned the old MooTools site in exchange for a simple boring option. The reason we have updated the website to a new, simple, absolutely no effects, that we want people to understand what is MooTools before they try to use it. We like the new site, and that's exactly what we want to see. The old site has not transferred the right of the picture framework. MooTools was never a script which can skopipastit with the code some example to get the crazy effect on the website, even if you know nothing about JavaScript. It's a framework for javascript developers. If that sounds elitist, well, so be it, but understand it is not our goal.
We also understand that regardless of what we tell everyone we can't force someone to teach something, and many people will use the tools we develop the wrong way... it's okay, because they are open source.
We like mailing lists much more, as that's what developers around the world use, and we can watch them at leisure with the help of mail clients. Please stop asking us to return the forum back, or can move on to another framework, which provides its users the official forum... (please note that all other frameworks, including jQuery use a mailing list. No one has an official forum and no user has requested it.
Moreover, there is a Nabble forum interface to the e-mail mailing lists. If you've never tried it, check out the n2.nabble.com/MooTools-Users-f660466.html
Also the guys from mooforum.net did a great job, so sign up there and use it instead of postal mailing lists if you want.
Referring to the developers and moderators mooforum.net if you need anything or you think that there is an important position that developers should watch, let me know using the email and I will answer. Thank you for all the hard work you have done.
Valerio and I have spent this week, which began with the Fronteers 2008 (let us discuss this in more detail later), working on the new MooTools blog. Mephisto gave us a lot of problems and cannot be styled in accordance with the other parts of the site, so we decided to clean it up. It was not an easy task, but as soon as that is done (later this week) I personally and other developers will write regularly useful information. Check mootools.net for updates at the end of the week.
Last week I spoke at a conference in Amsterdam called Fronteers and was dedicated to object-oriented design in JavaScript and how we use some principles in MooTools. Valerio attended the conference with me and as we were there, we talked a lot about MooTools.
I and the other speakers/developers at Fronteers conference communicated with each other, we are all on the same team! We love other frameworks, and we like the contribution that they make to the JavaScript community, and we want you all also loved them. We do not compete with any of them. If you think that jQuery is better suited for your current project, use it! It's well tested and refined framework. I also want to stop wars between frameworks. If the developers normally communicate with each other, it is supposed to do and users. Not going to blame other frameworks, okay?
We are working to release 1.2.1, which will be very soon. The biggest problem that needs to be considered is Class.js but anyone who has seen the code knows that this isn't a trivial task. I'm working on rewriting Class.js so he again worked with Safari2 and Opera, without dirty hacks. I'll tell you when we're finished and everything will be tested. 1.2.1 will also contain many other bug-fixes. There is one problem with the Request, which may require minor API changes. If that happens, I will tell a small change when it is released.
After 1.2.1, we will begin developing MooTools 1.3. If we decide that there must be other changes that should be in releases, you can release one or two intermediate release, but we will resolve it during the development process. 1.3 will contain a few new things that we are not yet fully defined. I will make several posts about it in the blog when everything is finished.
I think this small amount is officially enough information to give to understand what is happening and what will happen with MooTools. If there are other questions that I have not touched, you can ask them.
Thank you,
— Tom Occhino
PS: sorry, I don't know how to count :)
Article based on information from habrahabr.ru
I'm writing this post on the mailing list to tell the MooTools community about what the developers were doing these days and what will happen with the framework. We are all tired of answering the same questions over and over, so I hope this post will make something more clear, and we stop to see the same thing over and over again in the mailing list.
1. What's going on with the site?
Many of you think that we have abandoned the old MooTools site in exchange for a simple boring option. The reason we have updated the website to a new, simple, absolutely no effects, that we want people to understand what is MooTools before they try to use it. We like the new site, and that's exactly what we want to see. The old site has not transferred the right of the picture framework. MooTools was never a script which can skopipastit with the code some example to get the crazy effect on the website, even if you know nothing about JavaScript. It's a framework for javascript developers. If that sounds elitist, well, so be it, but understand it is not our goal.
We also understand that regardless of what we tell everyone we can't force someone to teach something, and many people will use the tools we develop the wrong way... it's okay, because they are open source.
3. What happened to the forum?
We like mailing lists much more, as that's what developers around the world use, and we can watch them at leisure with the help of mail clients. Please stop asking us to return the forum back, or can move on to another framework, which provides its users the official forum... (please note that all other frameworks, including jQuery use a mailing list. No one has an official forum and no user has requested it.
Moreover, there is a Nabble forum interface to the e-mail mailing lists. If you've never tried it, check out the n2.nabble.com/MooTools-Users-f660466.html
Also the guys from mooforum.net did a great job, so sign up there and use it instead of postal mailing lists if you want.
Referring to the developers and moderators mooforum.net if you need anything or you think that there is an important position that developers should watch, let me know using the email and I will answer. Thank you for all the hard work you have done.
2. What happened to the blog?
Valerio and I have spent this week, which began with the Fronteers 2008 (let us discuss this in more detail later), working on the new MooTools blog. Mephisto gave us a lot of problems and cannot be styled in accordance with the other parts of the site, so we decided to clean it up. It was not an easy task, but as soon as that is done (later this week) I personally and other developers will write regularly useful information. Check mootools.net for updates at the end of the week.
3. What Fronteers?
Last week I spoke at a conference in Amsterdam called Fronteers and was dedicated to object-oriented design in JavaScript and how we use some principles in MooTools. Valerio attended the conference with me and as we were there, we talked a lot about MooTools.
4. What about other frameworks?
I and the other speakers/developers at Fronteers conference communicated with each other, we are all on the same team! We love other frameworks, and we like the contribution that they make to the JavaScript community, and we want you all also loved them. We do not compete with any of them. If you think that jQuery is better suited for your current project, use it! It's well tested and refined framework. I also want to stop wars between frameworks. If the developers normally communicate with each other, it is supposed to do and users. Not going to blame other frameworks, okay?
5. What's next?
We are working to release 1.2.1, which will be very soon. The biggest problem that needs to be considered is Class.js but anyone who has seen the code knows that this isn't a trivial task. I'm working on rewriting Class.js so he again worked with Safari2 and Opera, without dirty hacks. I'll tell you when we're finished and everything will be tested. 1.2.1 will also contain many other bug-fixes. There is one problem with the Request, which may require minor API changes. If that happens, I will tell a small change when it is released.
After 1.2.1, we will begin developing MooTools 1.3. If we decide that there must be other changes that should be in releases, you can release one or two intermediate release, but we will resolve it during the development process. 1.3 will contain a few new things that we are not yet fully defined. I will make several posts about it in the blog when everything is finished.
I think this small amount is officially enough information to give to understand what is happening and what will happen with MooTools. If there are other questions that I have not touched, you can ask them.
Thank you,
— Tom Occhino
PS: sorry, I don't know how to count :)
