nice. thanks. didnt saw prime-util while making the first project with
the "new" stuff.
btw i like it a lot :)
On 11/02/2012 08:50 PM, Arian Stolwijk wrote:
That's an interesting one indeed:
Function.prototype.bind is quite complex to "shim" correctly. For the
stuff in es5/ ... we want to shim them 100% correctly.
With .bind we think that it's too complex to shim it 100% correctly,
which is why we didn't implement it at all (in prime).
In prime-util (https://github.com/arian/prime-util) you can find
fn.bound, which is basically .bind, but smaller and faster.
Check the readme to see how you can use it.
On Fri, Nov 2, 2012 at 8:43 PM, g.schlmm <[email protected]
<mailto:[email protected]>> wrote:
a prime question:
i need for example the Function.prototype.bind function in the browser
is there already an implementation or is the es5/function a
placeholder for that ?
On 10/24/2012 06:49 PM, Arian Stolwijk wrote:
Once the documentation is ready, we like to put it somewhere on
mootools.net <http://mootools.net> <http://mootools.net> and
make a blogpost for some beta
releases.
Problems we've faced with the community is before we announce stuff,
which we can't meet, which would disappoint people.
That's why we haven't announced anything officially yet.
Anyway, if anyone feels things are moving to slow, documenting
prime,
for example, is pretty easy and by diving in the code you can
learn a lot!
Fork and edit
https://github.com/mootools/__prime/blob/master/doc/prime.md
<https://github.com/mootools/prime/blob/master/doc/prime.md>
basically.
If you want to do something serious, you could clone the repo,
and build
the html stuff:
git clone https://github.com/mootools/__prime.git
<https://github.com/mootools/prime.git>
cd prime
npm install
make docs-watch
and edit doc/prime.md <http://prime.md> <http://prime.md>.
The make docs-watch will generate the doc/prime.html (automatically
after each change in prime.md <http://prime.md>
<http://prime.md>) which you can open with
any browser.
On Wed, Oct 24, 2012 at 6:03 PM, Christoph <[email protected]
<mailto:[email protected]>
<mailto:[email protected] <mailto:[email protected]>>> wrote:
Great news and great summary, thanks Arian. I think that
would a
good thing for the MooTools Blog, there are probably many
people out
there waiting for the next major MooTools version.
I think it is also a good idea to remove the old unused
branches,
that is just confusing people - at least me until i found
this post
here.
Thanks for your awesome work. :)
Am Dienstag, 16. Oktober 2012 11:17:59 UTC+2 schrieb Arian
Stolwijk:
"MooTools 2.0" doesn't really exist in a form that it
is a 2.0,
but it are more separate packages that can be used,
more like
the "do one thing and do it right" idea, together with
commonjs/nodejs packages that are available on npm (but
can be
built for the browser as well).
Currently they are:
* https://github.com/mootools/____prime
<https://github.com/mootools/__prime>
<https://github.com/mootools/__prime
<https://github.com/mootools/prime>> (core stuff)
* https://github.com/mootools/____elements
<https://github.com/mootools/__elements>
<https://github.com/mootools/__elements
<https://github.com/mootools/elements>> (element stuff)
* https://github.com/kamicane/____moofx
<https://github.com/kamicane/__moofx>
<https://github.com/kamicane/__moofx
<https://github.com/kamicane/moofx>> (effects with css3, and
js fallback)
* https://github.com/kamicane/____agent
<https://github.com/kamicane/__agent>
<https://github.com/kamicane/__agent
<https://github.com/kamicane/agent>> (request)
* https://github.com/kamicane/____slick
<https://github.com/kamicane/__slick>
<https://github.com/kamicane/__slick
<https://github.com/kamicane/slick>> (newer selector engine)
* https://github.com/kamicane/____wrapup
<https://github.com/kamicane/__wrapup>
<https://github.com/kamicane/__wrapup
<https://github.com/kamicane/wrapup>> (nodejs tool to build
commonjs/node packages for the browser)
Besides that some utilities I created for the above
packages
* https://github.com/arian/____prime-util
<https://github.com/arian/__prime-util>
<https://github.com/arian/__prime-util
<https://github.com/arian/prime-util>>
* https://github.com/arian/____elements-util
<https://github.com/arian/__elements-util>
<https://github.com/arian/__elements-util
<https://github.com/arian/elements-util>>
Most stuff is already pretty usable if you know what you're
doing. To make it more usable I/we are currently
documenting the
packages. Docs for elements can be found (temporarily) at
http://mootools.net/test/____elements/elements.html
<http://mootools.net/test/__elements/elements.html>
<http://mootools.net/test/__elements/elements.html
<http://mootools.net/test/elements/elements.html>>. Otherwise in
a 'doc' folder or in a README in the repos.
Things aren't moving very fast, but hopefully once
everything is
documented, we can move to the next step and start
'officially'
releasing each package.
Maybe we should remove the 2.0wip and 1.5wip branches.
1.5wip is
the current master, and 2.0wip was basically MooTools
1.3 :)
On Tue, Oct 16, 2012 at 9:23 AM, Jose Achmad Palala
<[email protected] <mailto:[email protected]>> wrote:
It looks like mootools is going to use the new ECMA ES
Harmony and AMD / Require or Common JS development
systems.
On Tue, Oct 16, 2012 at 2:56 PM, dukeofgaming
<[email protected] <mailto:[email protected]>>
wrote:
Interesting. Is MooTools Core now going to be
MooTools
Prime?, or is it getting a sexy new name?
On Monday, October 15, 2012 10:40:49 PM UTC-5,
Nutron wrote:
It's just somewhere else:
https://github.com/mootools/____pr__ime
<https://github.com/mootools/__pr__ime>
<https://github.com/mootools/__prime
<https://github.com/mootools/prime>>
On Mon, Oct 15, 2012 at 6:24 PM, dukeofgaming
<[email protected]
<mailto:[email protected]>> wrote:
I had the idea that the development was
still
going but just peeked at the 2.0wip
branch and
it has been untouched for 2 years
Is MooTools still going on? :(
--
J.Palala
