Thats fine. I was more curious on what some of the new features would be. I rather not start coding something, finish it, one week later, new version is released with exact feature I wanted. Yes, I am lazy in that regard I suppose.
On Feb 24, 10:02 am, Christoph Pojer <[email protected]> wrote: > We are trying to provide as much compatibility as possible. In cases > where it is not posible we will provide a detailed guide on how to > update your application. You can safely start with 1.2 :) > > On Feb 24, 4:56 am, ibolmo <[email protected]> wrote: > > > > > By definition I wouldn't expect 2.0 to be 100% compatible with 1.3 > > even with a compatibility layer. It's a major revision, and there > > could be breaking changes. > > > I wouldn't wait for 2.0, though. You should code for 1.2 if your > > deadline is soon, or 1.3 is you're willing to follow development -- > > but don't be surprised if there's bugs. > > > On Feb 23, 1:26 pm, Aaron Newton <[email protected]> wrote: > > > > 1.3 will be 100% backwards compatible with 1.2. So will 2.0. You can start > > > your rewrite now. > > > > 1.3 actually doesn't change a lot of the API. The changes it does make > > > are, > > > again, backwards compatible. > > > > On Tue, Feb 23, 2010 at 5:30 AM, duclet <[email protected]> wrote: > > > > So I have seen some mentioning of MooTools 1.3 and even 2.0 and just > > > > wanted to know if there is some sort of estimate on when it might be > > > > released? Currently my company is using Prototype and we are thinking > > > > about a complete rewrite using MooTools and it would be nice to know > > > > so we can plan accordingly.
