1.2 Release and Important Site Notes
76 views
Skip to first unread message
Michelle Steigerwalt
Jun 10, 2008, 7:19:06 AM6/10/08
to MooTools Users
First off, welcome to the new group, MooTools Users! This is the
place for users of all skill levels to discuss the framework and their
use of it.
Frequent visitors to http://mootools.net have probably noticed a few
changes.
Among them a complete redesign, new accounts for MooTools at
Lighthouse and Github, and the 1.2 docs moved to http://docs.mootools.net.
You might also notice that the site isn't fully functional yet. It
will be soon. :)
Because of the increasing popularity of this project of ours, we have
been under an increasing amount of stress to keep the various parts of
this site running in good order. You may have experienced downtime
relative to MooTools recently. We understand that many developers
utilize MooTools in critical components of their projects, and such
downtime is completely unacceptable.
To solve these issues for the 1.2 release, we have moved our critical
components off-site to the best provider of each component, granting
the MooTools users with the highest possible uptime of all areas of
the site. A major benefit of this move is being able to completely
reinvent the way we interact with our community of users (aka you
guys!).
Many developers have also been anxiously awaiting the 1.2 release so
they could benefit from the extended features without risking their
jobs on a beta release. As such, we have decided to release 1.2 along
with the new features of our site without waiting for everything to be
100% complete. The finishing touches which remain are not related to
the critical functions of the site, including the blog and some links
on the main page.
Here are the major changes broken down by topic.
== Git ==
The most exciting change for the 1.2 release is the switch from
Subversion to Git. Git is a huge step forward to our development
model, allowing everyone who wants to contribute to MooTools the
ability to create their very own fork. Each fork can then be merged
into the main core as seen fit or used on its own as an alternate
version of MooTools. This allows us to release faster, iterate to
better versions and better handle the contributions of the community.
This allows would-be contributors to play in their own sandbox without
worrying about whether or not their suggestions are appropriate. So
get forking!
Please note that the Subversion repository will no longer keep up with
the changes to MooTools. You will have to check out the Git
repository for that.
You can see the git repository here: http://github.com/mootools/mootools-core
To keep the core clean and mean, we have created a separate repository
for plugins which don't belong in core (including some plugins which
have been part of the core distribution until now). This is a perfect
place to stash all the nifty classes you have sitting in your project
directories.
Link to the plugin hub: http://github.com/mootools/mootools-more
You'll also notice that the download page has been split into two
pages accordingly.
== Bugtracking by Lighthouse ==
We have abandoned our Trac, which has been giving us problems over the
past weeks, for Lighthouse. Lighthouse allows us to integrate our
ticketing system with our new Github account and should provide
everyone with a comparable experience to our previous system.
We would like to extend our sincere gratitude to Thomas Aylott for his
help in the switch to Github and moving the Trac tickets to
Lighthouse.
You can visit the new Lighthouse account here: http://mootools.lighthouseapp.com/
== New MooTools User Group ==
As part of our offsite initiative, we have moved the community forum
to Google, where it hopefully will not crash and die. Note that this
group is *not* a replacement for the forum, which will be back
shortly.
== Join Us on IRC ==
While we've been partying in the IRC room for quite some time, the IRC
link to #mootools on Freenode has been added to the main page of
MooTools.net. If you have not visited us there before, please feel
free to stop by to ask your questions or just hang out. We love
chatting with new users.
== Shiny New Docs ==
The 1.11 docs have been moved to http://docs111.mootools.net.
Conversely, the 1.2 docs have been moved from http://docs12b.mootools.net
to the main docs subdomain (http://docs.mootools.net).
== More to Come ==
We'll be finishing off the new site and I'll be keeping you updated
with more details once the blog gets back online. A complete
changelog and other important information is on its way. So stay
tuned!
== Thanks! ==
On behalf of the entire MooTools team, we'd like to extend special
thanks to Valerio, for working his ass off for Mootools. If you get
the chance, make sure you thank him (once he regains consciousness).
place for users of all skill levels to discuss the framework and their
use of it.
Frequent visitors to http://mootools.net have probably noticed a few
changes.
Among them a complete redesign, new accounts for MooTools at
Lighthouse and Github, and the 1.2 docs moved to http://docs.mootools.net.
You might also notice that the site isn't fully functional yet. It
will be soon. :)
Because of the increasing popularity of this project of ours, we have
been under an increasing amount of stress to keep the various parts of
this site running in good order. You may have experienced downtime
relative to MooTools recently. We understand that many developers
utilize MooTools in critical components of their projects, and such
downtime is completely unacceptable.
To solve these issues for the 1.2 release, we have moved our critical
components off-site to the best provider of each component, granting
the MooTools users with the highest possible uptime of all areas of
the site. A major benefit of this move is being able to completely
reinvent the way we interact with our community of users (aka you
guys!).
Many developers have also been anxiously awaiting the 1.2 release so
they could benefit from the extended features without risking their
jobs on a beta release. As such, we have decided to release 1.2 along
with the new features of our site without waiting for everything to be
100% complete. The finishing touches which remain are not related to
the critical functions of the site, including the blog and some links
on the main page.
Here are the major changes broken down by topic.
== Git ==
The most exciting change for the 1.2 release is the switch from
Subversion to Git. Git is a huge step forward to our development
model, allowing everyone who wants to contribute to MooTools the
ability to create their very own fork. Each fork can then be merged
into the main core as seen fit or used on its own as an alternate
version of MooTools. This allows us to release faster, iterate to
better versions and better handle the contributions of the community.
This allows would-be contributors to play in their own sandbox without
worrying about whether or not their suggestions are appropriate. So
get forking!
Please note that the Subversion repository will no longer keep up with
the changes to MooTools. You will have to check out the Git
repository for that.
You can see the git repository here: http://github.com/mootools/mootools-core
To keep the core clean and mean, we have created a separate repository
for plugins which don't belong in core (including some plugins which
have been part of the core distribution until now). This is a perfect
place to stash all the nifty classes you have sitting in your project
directories.
Link to the plugin hub: http://github.com/mootools/mootools-more
You'll also notice that the download page has been split into two
pages accordingly.
== Bugtracking by Lighthouse ==
We have abandoned our Trac, which has been giving us problems over the
past weeks, for Lighthouse. Lighthouse allows us to integrate our
ticketing system with our new Github account and should provide
everyone with a comparable experience to our previous system.
We would like to extend our sincere gratitude to Thomas Aylott for his
help in the switch to Github and moving the Trac tickets to
Lighthouse.
You can visit the new Lighthouse account here: http://mootools.lighthouseapp.com/
== New MooTools User Group ==
As part of our offsite initiative, we have moved the community forum
to Google, where it hopefully will not crash and die. Note that this
group is *not* a replacement for the forum, which will be back
shortly.
== Join Us on IRC ==
While we've been partying in the IRC room for quite some time, the IRC
link to #mootools on Freenode has been added to the main page of
MooTools.net. If you have not visited us there before, please feel
free to stop by to ask your questions or just hang out. We love
chatting with new users.
== Shiny New Docs ==
The 1.11 docs have been moved to http://docs111.mootools.net.
Conversely, the 1.2 docs have been moved from http://docs12b.mootools.net
to the main docs subdomain (http://docs.mootools.net).
== More to Come ==
We'll be finishing off the new site and I'll be keeping you updated
with more details once the blog gets back online. A complete
changelog and other important information is on its way. So stay
tuned!
== Thanks! ==
On behalf of the entire MooTools team, we'd like to extend special
thanks to Valerio, for working his ass off for Mootools. If you get
the chance, make sure you thank him (once he regains consciousness).
Message has been deleted
Harald
Jun 10, 2008, 7:42:14 AM6/10/08
to MooTools Users
Hooray for MooTools 1.2!
Great to see so many forks on github, all the contributions will back
up the coming releases. And now I'll update all the downloads and
links at digitarald.de.
On Jun 10, 1:19 pm, Michelle Steigerwalt <msteigerw...@gmail.com>
wrote:
> The 1.11 docs have been moved tohttp://docs111.mootools.net.
> Conversely, the 1.2 docs have been moved fromhttp://docs12b.mootools.net
Great to see so many forks on github, all the contributions will back
up the coming releases. And now I'll update all the downloads and
links at digitarald.de.
On Jun 10, 1:19 pm, Michelle Steigerwalt <msteigerw...@gmail.com>
wrote:
> First off, welcome to the new group, MooTools Users! This is the
> place for users of all skill levels to discuss the framework and their
> use of it.
>
> Frequent visitors tohttp://mootools.nethave probably noticed a few
> place for users of all skill levels to discuss the framework and their
> use of it.
>
> changes.
>
> Among them a complete redesign, new accounts for MooTools at
> Lighthouse and Github, and the 1.2 docs moved tohttp://docs.mootools.net.
>
> Among them a complete redesign, new accounts for MooTools at
> Conversely, the 1.2 docs have been moved fromhttp://docs12b.mootools.net
rasmusfl0e
Jun 10, 2008, 12:52:17 PM6/10/08
to MooTools Users
*Sigh of relief*
Finally I can begin doing stuff with a stable release and all the
nifty features I've been salivating over since the first betas.
Good works, guys!
;)
> The 1.11 docs have been moved tohttp://docs111.mootools.net.
> Conversely, the 1.2 docs have been moved fromhttp://docs12b.mootools.net
Finally I can begin doing stuff with a stable release and all the
nifty features I've been salivating over since the first betas.
Good works, guys!
;)
> First off, welcome to the new group, MooTools Users! This is the
> place for users of all skill levels to discuss the framework and their
> use of it.
>
> Frequent visitors tohttp://mootools.nethave probably noticed a few
> place for users of all skill levels to discuss the framework and their
> use of it.
>
> changes.
>
> Among them a complete redesign, new accounts for MooTools at
> Lighthouse and Github, and the 1.2 docs moved tohttp://docs.mootools.net.
>
> Among them a complete redesign, new accounts for MooTools at
> Conversely, the 1.2 docs have been moved fromhttp://docs12b.mootools.net
carise
Jun 10, 2008, 3:21:04 PM6/10/08
to MooTools Users
HOORAY! Congratulations, MooTools team!
Garrick
Jun 10, 2008, 5:30:16 PM6/10/08
to MooTools Users
This is very exciting news! Congratulations to everyone. A job well
done, indeed.
done, indeed.
section31
Jun 10, 2008, 6:58:11 PM6/10/08
to MooTools Users
I'm a bit disappointed that no plugin management system was added to
the new mootools site. I strongly believe in order to compete with
jquery, we need to have a plugin management system where users can
contribute and manage their own plugins.
I've mentioned this before on the forums, and I didn't get any
discussion going on. Just pure flames. Jquery has a robust user
contributed plugin system that allows users to manage their releases,
accept comments, post documentation, demos, links, bugs, and much much
more.
http://plugins.jquery.com/project/Plugins/category/48
Was this even considered? Because there is no official organizational
structure to user contributed scripts, there is no incentive to share
or contribute.
the new mootools site. I strongly believe in order to compete with
jquery, we need to have a plugin management system where users can
contribute and manage their own plugins.
I've mentioned this before on the forums, and I didn't get any
discussion going on. Just pure flames. Jquery has a robust user
contributed plugin system that allows users to manage their releases,
accept comments, post documentation, demos, links, bugs, and much much
more.
http://plugins.jquery.com/project/Plugins/category/48
Was this even considered? Because there is no official organizational
structure to user contributed scripts, there is no incentive to share
or contribute.
fabiomcosta
Jun 10, 2008, 9:10:13 PM6/10/08
to MooTools Users
this could be really nice, maybe mootools plugins third part
developers would get more excited.
A good thing too would be to let us know what each part of the more
builder needs from the core builder to work, or all of them need of
all the core to work?
Keep up the good work! It's the best javascript framework on the web!
Thanks from Brasil!
developers would get more excited.
A good thing too would be to let us know what each part of the more
builder needs from the core builder to work, or all of them need of
all the core to work?
Keep up the good work! It's the best javascript framework on the web!
Thanks from Brasil!
Guillermo Rauch
Jun 10, 2008, 9:22:15 PM6/10/08
to mootool...@googlegroups.com
On Jun 10, 2008, at 10:10 PM, fabiomcosta wrote:
>> I'm a bit disappointed that no plugin management system was added to
>> the new mootools site. I strongly believe in order to compete with
>> jquery, we need to have a plugin management system where users can
>> contribute and manage their own plugins.
>>
>> I've mentioned this before on the forums, and I didn't get any
>> discussion going on. Just pure flames. Jquery has a robust user
>> contributed plugin system that allows users to manage their releases,
>> accept comments, post documentation, demos, links, bugs, and much
>> much
>> more.
>>
>> http://plugins.jquery.com/project/Plugins/category/48
>>
>> Was this even considered? Because there is no official
>> organizational
>> structure to user contributed scripts, there is no incentive to share
>> or contribute.
This has been suggested and discussed multiple times, so I'm pretty
sure the MooTools
team is aware of the imminent need of a plugins system.
Search the forums (when they come back online), and you'll find many
interesting notes
on this matter.
Guillermo Rauch
http://devthought.com
Harald
Jun 11, 2008, 5:00:38 AM6/11/08
to MooTools Users
We focussed on releasing 1.2, the plugin forge was always in our heads
and its just a matter of investing some time to realize a rock-solid
forge app. Since everybody in the team has also real work in his life,
its always hard to find the time, but we love the idea of a forge, so
I'm sure that we tackle that missing feature soon to make the
community happy.
and its just a matter of investing some time to realize a rock-solid
forge app. Since everybody in the team has also real work in his life,
its always hard to find the time, but we love the idea of a forge, so
I'm sure that we tackle that missing feature soon to make the
community happy.
CroNiX
Jun 11, 2008, 8:21:10 PM6/11/08
to MooTools Users
I am very glad this forum is temporary and you will be putting the mt
one back up.
one back up.
Paul Redmond
Jun 11, 2008, 10:42:41 PM6/11/08
to MooTools Users
Great work! Thanks for such a great framework :)
Any idea on when 1.2 demos will be available, and if/where 1.1 demos
are for reference right now?
Thanks!
On Jun 10, 4:19 am, Michelle Steigerwalt <msteigerw...@gmail.com>
wrote:
> The 1.11 docs have been moved tohttp://docs111.mootools.net.
> Conversely, the 1.2 docs have been moved fromhttp://docs12b.mootools.net
Any idea on when 1.2 demos will be available, and if/where 1.1 demos
are for reference right now?
Thanks!
On Jun 10, 4:19 am, Michelle Steigerwalt <msteigerw...@gmail.com>
wrote:
> First off, welcome to the new group, MooTools Users! This is the
> place for users of all skill levels to discuss the framework and their
> use of it.
>
> Frequent visitors tohttp://mootools.nethave probably noticed a few
> place for users of all skill levels to discuss the framework and their
> use of it.
>
> changes.
>
> Among them a complete redesign, new accounts for MooTools at
> Lighthouse and Github, and the 1.2 docs moved tohttp://docs.mootools.net.
>
> Among them a complete redesign, new accounts for MooTools at
> Conversely, the 1.2 docs have been moved fromhttp://docs12b.mootools.net
Sietze Keuning
Jun 12, 2008, 5:44:20 AM6/12/08
to MooTools Users
Excellent work guys!
I'm just wondering one thing. On the beta site there was an option to
get backward compatability, but I can not find it anymore. Is it
coming back in the future? I thought it was really handy for all the
people who already made lots of code for the 1.1 mootools and also
want to use the new mootools...
Thanks
I'm just wondering one thing. On the beta site there was an option to
get backward compatability, but I can not find it anymore. Is it
coming back in the future? I thought it was really handy for all the
people who already made lots of code for the 1.1 mootools and also
want to use the new mootools...
Thanks
Rolf -nl
Jun 12, 2008, 4:05:02 PM6/12/08
to MooTools Users
This is all very great guys! mooorules.
Congrats, and kudos for the hard work, i can only imagine....
Congrats, and kudos for the hard work, i can only imagine....
Tobi
Nov 14, 2024, 9:15:50 PM11/14/24
to MooTools Users
Wow! MooTools 1.2 – I've been waiting for this version for so long!
When can we expect the next release? I'm really looking forward to it.
😅 Just kidding, those were good times with MooTools. All the best to the old-timers who still remember! 🍻
When can we expect the next release? I'm really looking forward to it.
😅 Just kidding, those were good times with MooTools. All the best to the old-timers who still remember! 🍻
Andrea L. Dessì
Nov 15, 2024, 3:26:12 AM11/15/24
to mootool...@googlegroups.com
MooTools! Never forget!
Mit freundlichen Grüßen,
Andrea--
---
You received this message because you are subscribed to the Google Groups "MooTools Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mootools-user...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/mootools-users/adc8a068-a274-4d3d-9af5-80a2bdb9545en%40googlegroups.com.
Zsolt Zsuffa
Nov 15, 2024, 3:27:26 AM11/15/24
to mootool...@googlegroups.com
Me too. It was a great initiative.
To view this discussion visit https://groups.google.com/d/msgid/mootools-users/CAKCaosbOk07_Y8Ju_wd-AJojL_rVH7-18N9PJS5qpACOpVX7WQ%40mail.gmail.com.
--
Thank you,
Zsolt Zsuffa
LinkedIn - Personal profile
Twitter - Professional discussions
Agile Renovation - From agony to business agility
ProcessPuzzle - Content & Workflow Management Business Platform
Open Source ProcessPuzzle - Passionate collaboration
Olivier Allouch
Nov 15, 2024, 11:12:46 AM11/15/24
to MooTools Users
Good times
No Mootools, no React (partially same team)Reply all
Reply to author
Forward
0 new messages