Thanksfor the info. It's looking good, I hope it gets plenty of support.
On 23/01/2013 15:52, Arian Stolwijk wrote:
Currently the MooTools Project consists mainly of MooTools-Core and
MooTools-More. Basically two projects under the MooTools umbrella by
MooTools developers. It just happens that more depends on core.
Prime and friends will be added to this, alongside mootools-core, to
the MooTools Project. It just doesn't use mootools-core.
This means that it will *not* directly replace MooTools Core or
MooTools More. To stop development of those projects would be bad
because there isn't an easy upgrade path. Prime is basically an entire
new project.
The reason we add new projects, instead of making a MooTools 2.0 that
you can upgrade from, is that there are a few key concepts different,
that wouldn't be possible using something like MooTools 1.x:
- Not extending natives (you can, if you want, with some extra code,
but prime also provides a "chain" function).
- Doesn't "polute" the global object at all
- Uses commonjs/node modules
- Does not use Element.prototype, but uses a slim element wrapper
- Moofx is CSS3 transitions based, with JS fallback. This wouldn't fit
in the Fx.* API.
Because of some of these features, like not extending natives, doesn't
put anything in the global object, it can basically work fine with
anything, and doesn't collide with other code, like jQuery, MooTools
or Prototype. For example in some project I just use MooTools Core,
which still works perfectly, together with moofx3 for animations.
On Wed, Jan 23, 2013 at 3:28 PM, Lee <lee...@gmail.com
<mailto:lee...@gmail.com>> wrote:
Is 'prime' meant to replace MooTools?
Does this mean that dedevelopment of MooTools will stop in favour
of 'prime', or will the two co-exist?
One other question: how interoperable is 'prime' intended to be
with the ubiquitous (and imo ugly) jQuery?
TIA
Lee
On 21/01/2013 19:58, Arian Stolwijk wrote:
You can read documentation here:
https://github.com/mootools/prime/blob/master/doc/prime.md
More links:
https://github.com/mootools/elements
https://github.com/mootools/wrapup
https://github.com/kamicane/moofx
https://github.com/kamicane/agent
https://github.com/kamicane/slick
https://github.com/arian/prime-util
https://github.com/arian/elements-util
https://github.com/arian/elements-ui
https://github.com/arian/wrapup-webbuilder
Basically the last step is create some kind of website, which
is still a little todo (if you think you can do something
about this, please ping us on IRC), before releasing any
"official" betas.
You can also find all those packages on npm, which are tagged
and usable.
All those packages are using commonjs modules, like node.js
does. That means you can install and require them like any
other node package on npm. Of course not all packages, like
elements, work in node.js. To get those to work in the
browser, wrapup is used to build a JS file that is usable in
the browser.
On Mon, Jan 21, 2013 at 7:40 PM, adidi <adie...@gmail.com
<mailto:adie...@gmail.com> <mailto:adie...@gmail.com
<mailto:adie...@gmail.com>>> wrote:
Can we get any news about the long awaited "prime"
(mootools 2.0) ?
As I understand it will work with conjunction to Node.js
mode of
work ?
Is there any timeframe ? something to read besides
github(which is
empty in description)
--
--
--
