Re: [Moo] Re: Prime and mootools 2

at, Dec 28, 2013 at 10:46 PM, utan wrote: > Hi, > > Examples? I don't get it or I have never used that, how you use in client > side? > > > On Saturday, December 28, 2013 1:42:20 PM UTC-8, Arian Stolwijk wrote: > >> Prime&friends can be used in the browse

Re: [Moo] Re: Prime and mootools 2

Prime&friends can be used in the browser through wrapup ( https://github.com/mootools/wrapup) or browserify. On Sat, Dec 28, 2013 at 8:28 PM, utan wrote: > hi, > > I am in the same position as you are, I learnt the mootools ways and never > give raw Javascript a shot till I saw Mootools slowly

Re: [Moo] 'load' fires before 'domready' on chrome!

Besides that, that old 1.11 demo uses older domready code which has been improved over the years. On Fri, Dec 20, 2013 at 7:07 AM, Sanford Whiteman wrote: > > This old 1.11 demo page handily demonstrates this: > > http://demos111.mootools.net/DomReadyVS.Load > > It does? > > I don't see it. > >

Re: [Moo] Migrate a project from mootools to prime / primish

That is actually one of the design choices of prime that it doesn't do the extra copying of property objects by default, rather it does less which is better if you consider performance when creating new objects. Probably setOptions could lookup the 'options' property of the inherited prototypes an

Re: [Moo] Migrate a project from mootools to prime / primish

Instead of --require prime ./node_modules/prime/index.js, you can simply do --require prime prime. Also if the file you're writing your JS in requires prime, the only thing you have to require with wrapup is your main file. main.js: var prime = require('prime'); // do something with prime So

Re: [Moo] Migrate a project from mootools to prime / primish

it from npm: wrup -r ./main.js -o built-file.js Finally you can On Wed, Dec 4, 2013 at 11:01 AM, Dimitar Christoff wrote: > > > On Wednesday, 4 December 2013 01:33:40 UTC, Arian Stolwijk wrote: >> >> well, use wrapup or browserify if you want to use it in the browser. >> &

Re: [Moo] Migrate a project from mootools to prime / primish

well, use wrapup or browserify if you want to use it in the browser. Then you can simply var prime = require('prime'); var A = prime({ // things }); var B = prime({ inherits: A, constructor: function() { console.log('do', this); } }); And that's it. On Tue, Dec 3, 2013 at 10:28

Re: [Moo] Mootools core dependency checker

Does that thing still exist? It doesn't work because it's 4 years old, and was for 1.2. In the latest versions of MooTools you have a URL in the comments, that link can be used to open the download page on mootools.net again. If you have a file with all dependencies, that doesn't help too much. I

Re: [Moo] Re: delay and periodical

var go; var startShow = function(){ carousel.next(); go = carousel.next.periodical(7000, carousel); } startShow.delay(3000) On Fri, Nov 8, 2013 at 5:11 PM, Chad Meyers wrote: > great thanks! I had to modify that slightly, but now it is working!!! > > startShow = function(){ > carousel.next

Re: [Moo] Restricted keywords in XHR request?

Sounds like some caching. Try to hard-refresh/disable cache. If the problem persists, we'd need some reproducible examples, otherwise we can only guess. On Tue, Oct 8, 2013 at 10:57 PM, Bryan Garaventa < bryan.garave...@whatsock.com> wrote: > ** > Hi, > I came across a weird bug I think, and was

Re: [Moo] Re: Building the new MooTools website

Correct. On Tue, Jun 18, 2013 at 1:26 PM, Tor wrote: > Yes, it works now. I did an entirely new build from scratch using the > instructions in the README and it worked flawlessly this time. > > I also agree that my path problem is in the domain of Node.js knowledge > since the error I got manif

Re: [Moo] Re: Building the new MooTools website

Okay, I've made some changes https://github.com/mootools/website/commit/2bb84ede367d4976a888fa59d3313af96dff9b31 Hope that helps. On Tue, Jun 18, 2013 at 10:35 AM, Arian Stolwijk wrote: > Also maybe when you're done could you describe the steps on the wiki, so > we can lin

Re: [Moo] Re: Building the new MooTools website

Also maybe when you're done could you describe the steps on the wiki, so we can link to it from the README. That could help other people. On Tue, Jun 18, 2013 at 10:33 AM, Arian Stolwijk wrote: > Awesome that you've come so far. This is to the point I came when trying > i

Re: [Moo] Re: Building the new MooTools website

Awesome that you've come so far. This is to the point I came when trying it out on windows. Perhaps on windows there is a `\r\n` so it never matches. Maybe you can try /^\-+(\r)?$/ Thanks and let me know if it works or not. On Tue, Jun 18, 2013 at 10:24 AM, Tor wrote: > I've now gotten so far

Re: [Moo] Re: First attempt at a MooTools website redesign. Thoughts?

#like-to-help On Wed, Apr 24, 2013 at 12:42 AM, Arian Stolwijk wrote: > Little update: https://github.com/arian/microsite#like-to-help > Let me know if you want to help out with something or if something doesn't > work. > > > On Fri, Apr 19, 2013 at 8:01 PM, Tony Brown

Re: [Moo] Re: First attempt at a MooTools website redesign. Thoughts?

om the linked prime-website repo) >> - Guides (content as routing, preferably written with markdown) >> - Section for the other projects, starting with elements, moofx, wrapup >> >> >> >> >> On Tue, Apr 16, 2013 at 12:25 PM, Arian Stolwijk < >> stolwij

Re: [Moo] Re: First attempt at a MooTools website redesign. Thoughts?

for the other projects, starting with elements, moofx, wrapup On Tue, Apr 16, 2013 at 12:25 PM, Arian Stolwijk wrote: > Just a heads up, Pietro pushed his designs and a first html / css demo to > https://github.com/mootools/website > The html / css might have to be redone, since

Re: [Moo] Re: First attempt at a MooTools website redesign. Thoughts?

Just a heads up, Pietro pushed his designs and a first html / css demo to https://github.com/mootools/website The html / css might have to be redone, since this was simply a quick prototype. So now we're at the implementation stage: https://github.com/mootools/website/wiki/Implementation The web

Re: [Moo] request problem (translating from jQuery to Mootools)

oh, you can set the "emulation" option to false. JSONP can't do any of that, because it's basically injects

Re: [Moo] request problem (translating from jQuery to Mootools)

Probably because you're doing a cross-domain request. On Fri, Apr 12, 2013 at 2:37 PM, hartum wrote: > Hi everyone > > I am translating a script from jQuery to mootools, the script in jQuery > is this: > > $.ajax({ > url:'http://10.1.1.94:8080/ui-web-logger/rest/events/load', >

Re: [Moo] Unable to get property 'apply' of undefined or null reference

The code is a bit weird, but should kind of work. Can you create a http://jsfiddle.net/ so we can actually run the *relative* code? On Thu, Apr 4, 2013 at 12:19 PM, Sitthykun LY wrote: > I'm using Joomla!, it's not standalone > it errors when I log to the site. > > Every line of my mootools co

Re: [Moo] Little bit of help with Morph

you can save the initial styles: http://jsfiddle.net/CjNyJ/1/ Also it's better to have one Fx.Morph instance for each element (rather than creating a new one each time you mouseenter). On Thu, Mar 28, 2013 at 5:13 PM, Roo wrote: > Hi all, > > Just looking for a bit of help about what to do whe

Re: [Moo] powetools swipe event

As far as I tested the swipe event works.. On Wed, Mar 27, 2013 at 3:07 PM, Tim Wienk wrote: > It might also be that it's just the demos that are outdated. > > -- > Tim Wienk, Software Developer, MooTools Developer > E. timwi...@gmail.com | W. http://tim.wienk.name > > -- > > --- > You received

Re: [Moo] Re: First attempt at a MooTools website redesign. Thoughts?

s we want. > > Anyway I think the discussion about the look must come after, mockup > discussion. > > > > El jueves, 21 de marzo de 2013 12:02:17 UTC+1, Arian Stolwijk escribió: >> >> I see no reason to use Bootstrap on MooTools.net. Bootstrap is great for >> pr

Re: [Moo] Re: First attempt at a MooTools website redesign. Thoughts?

I see no reason to use Bootstrap on MooTools.net. Bootstrap is great for prototyping a website or quickly putting something together. MooTools.net should look professional and not something that is put together in a few hours. On Thu, Mar 21, 2013 at 11:53 AM, hartum wrote: >

Re: [Moo] Re: First attempt at a MooTools website redesign. Thoughts?

We've created a central place where people can contribute ideas and designs for MooTools: https://github.com/mootools/website/wiki And for these specific ideas: https://github.com/mootools/website/wiki/MooTools.net-redesign On Thu, Mar 21, 2013 at 3:03 AM, Benjamin Kuker wrote: > Good suggestio

Re: [Moo] Re: First attempt at a MooTools website redesign. Thoughts?

like On Thu, Mar 21, 2013 at 1:41 AM, Erik Cervin Edin wrote: > This is cleaner, > nice work! > > I agree that a redesigning the site would send a strong message. Or > rather, that the site as it is doesn't look maintained. There's nothing on > the site that gives the indication that the framew

Re: [Moo] Re: Mootools Prime

;m promoting the use of your work > > > On Sun, Mar 17, 2013 at 4:29 PM, Arian Stolwijk > wrote: > >> Like I said, that is only a first test version that isn't finished yet. >> Want it to be finished, send me a pull request :P >> https://github.com/arian/prime-w

Re: [Moo] Re: Mootools Prime

0 PM, Tony Brown wrote: > >> It's the button on the left >> http://mootools.net/test/prime/ >> >> >> On Sun, Mar 17, 2013 at 3:44 PM, Arian Stolwijk > > wrote: >> >>> Which website are you referring to? >>> >>> >>>

Re: [Moo] Re: Mootools Prime

Which website are you referring to? On Sun, Mar 17, 2013 at 8:40 PM, Tony Brown wrote: > yep working now, don't know what happened but it was timing out a minute > ago? and the link is broken on the site shouldn't you fix that>? > > On Sun, Mar 17, 2013 at 3:39 PM

Re: [Moo] Re: Mootools Prime

git clone https://github.com/mootools/prime.git should work fine. On Sun, Mar 17, 2013 at 8:38 PM, Arian Stolwijk wrote: > http://mootools.net/test/prime/ is a WIP, so it's not ready yet, it needs > some design love, further content and for download we want to use > https://gi

Re: [Moo] Re: Mootools Prime

http://mootools.net/test/prime/ is a WIP, so it's not ready yet, it needs some design love, further content and for download we want to use https://github.com/arian/wrapup-webbuilder For now: "npm install prime" + wrapup (if you want to use it in a browser). Somewhere in this group I explained how

Re: [Moo] Re: Now that Joomla (3.0) has almost given up on Mootools, what will become of it ?

Working on it: http://mootools.net/test/prime/ (best design ever!) On Thu, Mar 14, 2013 at 9:57 PM, Aaron Newton wrote: > Then hurry up and release Prime before it's too late! > > > On Thu, Mar 14, 2013 at 12:43 PM, Arian Stolwijk > wrote: > >> I don't have k

Re: [Moo] Re: Now that Joomla (3.0) has almost given up on Mootools, what will become of it ?

I don't have kids yet :D On Thu, Mar 14, 2013 at 8:42 PM, Aaron Newton wrote: > > The process of development on core and more is somewhat diffuse to me. I >> thought there was an inner circle of wizards that worked on it. > > > that perhaps used to be the case, but most of them now have kids an

Re: [Moo] Re: leak , node.js and motools serverside

am effectively destroying just the > user class it started ? > > I was thinking every user is different and running his own instance of > the class.. am I right? > > > > On Mar 13, 4:00 pm, Arian Stolwijk wrote: > > Usually you don't really care, because node/V8 han

Re: [Moo] Re: leak , node.js and motools serverside

connect event listener doesn't even refer to the Server instance). Besides that it's hard to say what would be the problem without further insight. On Wed, Mar 13, 2013 at 11:40 PM, utan wrote: > So you mean, I should manually delete the instance this.server , I am > confused

Re: [Moo] Re: leak , node.js and motools serverside

No idea, generally if you want that the garbage collector picks it up, you should make sure that there are no references to it anymore. I don't really know any reason why MooTools Classes should be any different from traditional JavaScript inheritance (using var Foo = function(){ ... } Foo.prototy

Re: [Moo] Re: how to search data in an object.

Object.some / Object.every On Fri, Feb 22, 2013 at 11:06 AM, Hamburger wrote: > Hello, > thanks or all suggestions. > With Steffens solution I will get a complete object back. > What I need is only a true or false :) > > -- > > --- > You received this message because you are subscribed to the

Re: [Moo] Re: how to search data in an object.

> > Array.each(obj, function(item, index){ > if (item == '456') console.log("info22:", item.id); > }); That won't work, use Object.filter/each instead, like Steffen said. On Thu, Feb 21, 2013 at 3:24 PM, Sitthykun LY wrote: > Try this one > > Array.each(obj, function(item, index){ > if

Re: [Moo] Re: beginner question - all fade effects happening together problem

Not sure if this is what you want: http://jsfiddle.net/2bcq9/12/ Basically the element where the event was triggered on, is "this" in the event listener function. What you did is just fade all elements selected with the selector passed into $$(). Note: In your DOMReady, I introduced a "containers

Re: [Moo] Unexpected selector results with FireFox beta

Even a simpler solution, use 1.2.6 http://mootools.net/blog/2013/02/19/mootools-1-2-6-released/ On Tue, Jan 15, 2013 at 1:46 AM, Arian Stolwijk wrote: > https://github.com/mootools/mootools-core/pull/2462 > > > On Tue, Jan 15, 2013 at 1:45 AM, Arian Stolwijk > wrote: >

Re: [Moo] Firefox 18 breaks mootools 1.2.5 selector engine

You can now use MooTools 1.2.6 http://mootools.net/blog/2013/02/19/mootools-1-2-6-released/ On Fri, Jan 18, 2013 at 10:14 AM, Arian Stolwijk wrote: > Adding that line (at the top of your mootools.js file) should be enough. > If you want to rebuild, either wait until the mootools.net webs

Re: [Moo] Select an element that has two 'class' values?

The space means that the .normalise is a child of .cmd. Like a "div a" selector. When you don't use the space, you can select an element that should match all parts: div.foo.bar#hey[title="hello"] That matches a div, that has foo and bar as classes, hey as id and an attribute whose value equals h

Re: [Moo] Reverse builder

If the file was downloaded from the builder and is MooTools ≥ 1.3, it should have some link to the download page with a hash so it checks the correct dependencies. Otherwise if I ever need this by lack of a proper built script, I usually just scan through the JS, see if I can see stuff like Fx.Twe

Re: [Moo] Mootools Prime

amically ? > > And one last question, the only hold back from the beta release is the > site you mentioned in the previous post ? Do you have any dates for it ? > > > > On Wednesday, January 23, 2013 4:52:57 PM UTC+2, Arian Stolwijk wrote: > >> Currently the MooTools

Re: [Moo] Mootools Prime

23, 2013 at 3:28 PM, Lee 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 t

Re: [Moo] Mootools Prime

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/a

Re: [Moo] Set options for mBox

As you can see in the documentation, "content" isn't an option that .open accepts. "Refer to following example so see what options you can use" myMBox.open({ instant: true, target: 'myMBox9', position: { x: ['left', 'outside'] }, offset: { x: 20 }}); So,

Re: [Moo] Firefox 18 breaks mootools 1.2.5 selector engine

ntains; } catch(e) {} to my old > mootools-core.js file ? > is it enough ? > > > 2013/1/18 hx > >> howto build it ? >> >> >> 2013/1/11 Arian Stolwijk >> >>> Yeah, see https://github.com/mootools/mootools-core/issues/2402 and >>>

Re: [Moo] Create a blink effect onComplete for a ProgressBar

Anyway, something pretty quick, and perhaps chaining and stuff is better, but yeah: http://jsfiddle.net/KM8LD/ On Wed, Jan 16, 2013 at 2:59 AM, Arian Stolwijk wrote: > The '90 called, they want their tag back! > > > On Wed, Jan 16, 2013 at 2:31 AM, Mushr00m wrote: &

Re: [Moo] Create a blink effect onComplete for a ProgressBar

The '90 called, they want their tag back! On Wed, Jan 16, 2013 at 2:31 AM, Mushr00m wrote: > Don't do what ? > > Le mercredi 16 janvier 2013 02:30:18 UTC+1, Nutron a écrit : >> >> DON'T DO IT! >> >> >> On Tue, Jan 15, 2013 at 5:29 PM, Mushr00m wrote: >> >>> Hi ! >>> >>> I'm using the tutorial

Re: [Moo] Fx.Slide

First, just create *one* Fx.Slide instance. For hiding the element, just do myFxSlide.hide(); http://jsfiddle.net/EW2hp/2/ On Tue, Jan 15, 2013 at 7:51 PM, Trevor Orr wrote: > I have been playing around with Fx.Slide and having some issues getting it > to work the way I want, I am probably ju

Re: [Moo] TypeError: el.parentNode is null when I try and wrap an element

rror, have you seen: http://jsfiddle.net/m92Lu/11/ > > Hopefully that demonstrates that wraps() is more concise and easier to > read than using inject(). > > > On Tuesday, 15 January 2013 17:37:02 UTC, Arian Stolwijk wrote: > >> Why not just use .inject? wraps is more for &q

Re: [Moo] TypeError: el.parentNode is null when I try and wrap an element

Why not just use .inject? wraps is more for "in place wrap", just look at the source code: https://github.com/mootools/mootools-core/blob/master/Source/Element/Element.js#L754-L763 On Tue, Jan 15, 2013 at 6:00 PM, 4fingers wrote: > Bug has now been reported: > https://github.com/mootools/mootoo

Re: [Moo] Unexpected selector results with FireFox beta

https://github.com/mootools/mootools-core/pull/2462 On Tue, Jan 15, 2013 at 1:45 AM, Arian Stolwijk wrote: > Even a simpler solution is: > > Before you load MooTools, do: > > delete String.prototype.contains; > > > > > On Tue, Dec 11, 2012 at 1:45 AM, Ralph

Re: [Moo] Unexpected selector results with FireFox beta

before the script itself): > http://jsfiddle.net/wZsax/1/ > > Thanks again, > Ralph > > > On Tue, Dec 11, 2012 at 12:55 PM, Arian Stolwijk > wrote: > >> I think this relates to >> https://github.com/mootools/mootools-core/issues/2402 >> >> Could

Re: [Moo] Firefox 18 breaks mootools 1.2.5 selector engine

Yeah, see https://github.com/mootools/mootools-core/issues/2402 and https://groups.google.com/d/msg/mootools-users/W7MHwTFHYQ4/B4HcR951XQYJ On Thu, Jan 10, 2013 at 10:29 PM, Adriaan wrote: > Working jsfiddle example here: http://jsfiddle.net/CfJyd/ > > The problem only occurs in Firefox 18 that

Re: [Moo] Element Method: getProperty returns Array not String as documented

Because you use getElements, which returns an Elements collection. And calling Element methods on an Elements instance, returns an array. On Wed, Jan 9, 2013 at 2:51 PM, Lee wrote: > I got the same on FF 17.0.1 on OS X Snow Leopard. > > > On 09/01/2013 14:08, Johnny Fuery wrote: > >> I get "arr

Re: [Moo] passing an object to a function

One convention is to pass onThing events to the options object. However those should be handled by Events, rather than calling directly. To answer your question, when using Events (I added it to the Implements), just pass the list to the array with arguments the event is called with, like in this

Re: [Moo] Re: how to extend a class?

.parent() calls the same method, but in the parent class, so doesn't have anything to do with elements. var A = new Class({ a: function(){ console.log('A'); } }); var B = new Class({ Extends: A, a: function(){ this.parent(); console.log('B'); } }); var b = new B(); b.a(); // logs

Re: [Moo] how to extend a class?

What doesn't work, seems okay to me. exValidation has all methods of validation and extendedValidation, so including setMoreStyle. On Fri, Dec 28, 2012 at 1:29 PM, Hamburger wrote: > thx magic77, > sorry thats not what I'am looking for. > I would like to extend my functionality not only params

Re: [Moo] Unexpected selector results with FireFox beta

I think this relates to https://github.com/mootools/mootools-core/issues/2402 Could you add this somewhere, probably before adding MooTools to the page. String.prototype.contains = function(string, separator){ return (separator) ? (separator + this + separator).indexOf(separator + string

Re: [Moo] Multiple elements to collapse in Fx.Accordion

So if I understand it correctly you have 1 toggle and 2 elements, one before the the toggle, and one after? I don't think that'll work with Accordion and you'll have to write a small class or something yourself. If you wan't a quick solution you could maybe use Fx.Slide. Something like this: http

Re: [Moo] Compatibility with older versions of firefox

ential for > us, so we may be interested in building a specific test environment. > > Regards > > > Le 12/11/2012 21:05, Arian Stolwijk a écrit : > > Well, we don't test it anymore... because well, who uses firefox 1.5, > > but probably most stuff works. &g

Re: [Moo] Compatibility with older versions of firefox

Well, we don't test it anymore... because well, who uses firefox 1.5, but probably most stuff works. On Mon, Nov 12, 2012 at 5:56 PM, tonthon wrote: > Hi, > > I'm currently working on devices working on firefox 1.5, and I'd like to > use mootools as javascript library. > > Is mootools fully tes

Re: [Moo] Issue with Slider

We at least should see some code to get an idea what you're doing, jsfiddle.net is prefect for that. On Mon, Nov 12, 2012 at 5:54 PM, Kittie wrote: > I've been attempting to install more then one slider on my site (I want to > have 4) Only one slider out of the four will actually work. I've att

Re: [Moo] Equivalent of jQuery's isEmptyObject()

Or with simple JS: var empty = true; for (var k in object){ empty = false; break; } On Mon, Nov 12, 2012 at 12:09 AM, Arian Stolwijk wrote: > You could use: > > Object.every({}, function(){ return false }) // true > Object.every({a: 1}, function(){ return false }) // false > >

Re: [Moo] Equivalent of jQuery's isEmptyObject()

You could use: Object.every({}, function(){ return false }) // true Object.every({a: 1}, function(){ return false }) // false On Mon, Nov 12, 2012 at 12:01 AM, Blackbird wrote: > Hi, > > Does Mootools have an equivalent to jQuery's isEmptyObject() function? > http://api.jquery.com/jQuery.isEmp

Re: [Moo] Alternative to 'onclick' for a variable number of links?

Yes, inline event handlers are in almost all cases a bad idea. With MooTools you can use .addEvent. so you have this html: some text and this JS $('link').addEvent('click', function(event){ event.preventDefault(); // prevents the default action (which is the "return false" in your code")

Re: [Moo] Element menthods not available on IE8

object elements don't get extended with mootools methods. You could use the generic form: Element.getSize(myObjectElement). On Sun, Nov 11, 2012 at 5:11 AM, Daniel Peraza wrote: > I am aware of the document.id() stuff. > Here

Re: [Moo] IE

One word: AWESOME :P On Sat, Nov 10, 2012 at 1:13 AM, Trevor Orr wrote: > Not sure how many of you hate Internet Explorer but I sure do. So I wrote > a MooTools game so that I could kill IE whenever I wanted. > > You can too at http://fuckinie.com/ > > > > >

Re: [Moo] So, what happened with MooTools 2.0?

pe.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 <ht

Re: [Moo] Forge plug-in version?

Basically: Update the 'current' field in your package.yml Commit package.yml and tag it with the same version. Push to github. Then go to the forge, and press update button on your plugin page. On Thu, Oct 25, 2012 at 8:03 PM, Lee Goddard wrote: > How do I update a plugin on The Forge? > > Is t

Re: [Moo] Direct Link To Image in Gallery

Which gallery are you using? I guess you're using some kind of plugin. Also you're using an outdated MooTools version (1.2.1 instead of 1.4.5). Maybe you should look in the forge (http://mootools.net/forge/) for some better slideshows. On Wed, Oct 24, 2012 at 10:01 PM, jocrla wrote: > Hello, >

Re: [Moo] Re: Help with Fom.Validator

> > Great guys! It worked! I didn't know i had to include the > mootools-more.js. :) > If you would have checked your JS console, you would have noticed some stuff would be undefined, errors etc. Then usually you're missing something. On Wed, Oct 24, 2012 at 9:23 PM, mietzekotze wrote: > Great

Re: [Moo] So, what happened with MooTools 2.0?

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

Re: [Moo] Re: Geek scoping question.

Those are two separate examples, so you shouldn't execute them at the same time. >From page 29 a section about scoping starts, which explains this more. On Wed, Oct 24, 2012 at 2:27 PM, molipha wrote: > Hi, > > The example starts on the bottom of page 15. Thanks for your analysis but > actually

Re: [Moo] Re: Help with Fom.Validator

Also, did you include mootools-more with Form.Validator? On Wed, Oct 24, 2012 at 12:31 PM, ghazal wrote: > hello, > try this : > window.addEvent('domready', function(){ > // your code >}); > > > > On Wednesday, October 24, 2012 9:58:47 AM UTC+2, mietzekotze wrote: >> >> Hello guys,

Re: [Moo] Wrong $defined replacement?

(value != null) == (value !== undefined && value !== null). So != null is usually good enough. On Wed, Oct 24, 2012 at 10:33 AM, Stéphane wrote: > Hello everybody, > > I'm in the process of migrating Mootools from 1.2.5 to 1.4.5. As such, > I've been following this official upgrade > guide

Re: [Moo] Geek scoping question.

Which page? In the example you have it now (all the code together), the myFn() logs the type of the first myFn function in the global scope. If you remove the typeof operator, you should see that it logs the first global myFn. Basically what it does is: define myFn and createFn in the global scop

Re: [Moo] Re: mootools template engine

Twitter login on the forge is working again: https://github.com/mootools/mootools-forge/issues/5 On Mon, Oct 22, 2012 at 10:40 AM, Thierry Bela wrote: > Hello, > > you can find the latest version on > githubwhich is even faster than > Templayed.js :) . the

Re: [Moo] Re: Preventing Drag.Move click propagation on child element

Ooh, euh, simply preventDefault on the child? http://jsfiddle.net/2ubnr/2/ Or maybe I don't understand the problem correctly... On Fri, Oct 19, 2012 at 1:42 AM, mkljun wrote: > I know Arian ... > > How I understand it: > 1. The click event is first on the #parent and the element gets moved > aro

Re: [Moo] Re: Preventing Drag.Move click propagation on child element

Not an answer, but return false; is an old event.preventDefault(). The latter is better because it tells you what it does. On Fri, Oct 19, 2012 at 1:13 AM, mkljun wrote: > Thank Graham and Arian, > > Here's the jsFiddle http://jsfiddle.net/rand7/4/ > > If I click on the "Link" and drag the #pare

Re: [Moo] Preventing Drag.Move click propagation on child element

There are two solutions: 1. In your #parent event listener, check the event.target element. event.target is the element that was actually clicked. If that element matches your #child, then do nothing. var child = $('child'); $('parent').addEvent('click', function(event){ if (event.target == c

Re: [Moo] can't login to mootools forge

Seems you're right... :/ On Tue, Oct 16, 2012 at 3:58 PM, Thierry bela nanga wrote: > Hello, > > I used to login to the forge using the twitter login button. I have tried > different browsers it seems it is not working (at least for me). > > > Cheers, > > -- > http://tbela99.blogspot.com/ > > fax

Re: [Moo] So, what happened with MooTools 2.0?

"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:

Re: [Moo] Knob control?

What kind of knob control? On Mon, Oct 15, 2012 at 6:11 PM, Lee Goddard wrote: > Has anyone seen an MT knob control, on the Forge or elsewhere? > > I was thinking of making one outof the slider control, but if it has been > done... > > Thanks > Lee >

Re: [Moo] Click event with context != window

Can't you just do something like: $('map_bg').addEvent('mousedown', function(ev) { var pos = this.getPosition(); var rel = {x: ev.page.x - pos.x, y: ev.page.y - pos.y} }); On Mon, Oct 15, 2012 at 5:06 PM, Philip Thompson wrote: > I don't know if the event is affected by this, but it may

Re: [Moo] MooTube: Youtube Iframe API with MooTools

Good catch, after calling that method, it will replace mootube.$ready to true, and calling it a second time will fail. On Sat, Oct 6, 2012 at 12:49 AM, Philip Thompson wrote: > You're defining this property twice: $ready once as bool and once as > function > > https://github.com/Ciul/MooTube/blob

Re: [Moo] is there a moo-expression for the jquery .is()

What does it do? It looks like it's the same as .match() - http://mootools.net/docs/core/Element/Element#Element:match On Fri, Oct 5, 2012 at 3:37 PM, Hamburger wrote: > Hello, > one more beginner question please. > Is there a moo-expression for the jquery .is() > > Here the jquery code: > i

Re: [Moo] Do I have to check that an element exsist to get their properties?

$() and .getElement() can return null if the element doesn't exist. So if you're not sure the element exists, you'll have to check it indeed with an if statement. On Wed, Oct 3, 2012 at 12:36 PM, Hamburger wrote: > Hello, > please let me have one more beginner question. > With the following tes

Re: [Moo] finalText = $('').text(finalText).html();

Yes, $('') creates a new div element, same as new Element('div') in MooTools. So that code would be like: finalText = new Element('div', {text: finalText}).get('html'); On Tue, Oct 2, 2012 at 3:16 PM, Hamburger wrote: > Hello, > I need some help to translate jquery to mo. > What is the $('')

Re: [Moo] Select elements are not clickable when inside of a sortable element in Chrome

In the master branch there is an option for this now. On Tue, Sep 25, 2012 at 9:02 AM, Sanford Whiteman wrote: > > But to be honest, I don't like that!! is there any other solution? > > If you patch line #7300 of -More to include SELECT elements, you can > probably make it go away. You should fil

Re: [Moo] Unclear JavaScript error with Fx.Tween

But this jsfiddle works fine in IE8... On Sun, Aug 5, 2012 at 2:50 PM, Five wrote: > Here you go: > http://jsfiddle.net/mcwBx/8/ >

Re: [Moo] Unclear JavaScript error with Fx.Tween

Element.Events = 0; Element.NativeEvents = 0; can't do any good at least. Can you create a jsfiddle, basically paste the stuff you pasted here in a fiddle, try to make it work, and paste the link here, so we can play with it. I don't really see something which would cause those errors. On Sun, A

Re: [Moo] How can I isolate mootools code on a webpage?

Using wrapup (https://github.com/kamicane/wrapup) you can create fully encapsulated scripts with 0 globals. Using prime (http://github.com/mootools/prime) with nodes ( http://github.com/mootools/nodes) or maybe some moofx3 ( http://github.com/kamicane/moofx) It's all a bit alpha and not very docu

Re: [Moo] Re: problem loading content within same div tag.....

I don't think you should expect anyone write any code for you from scratch, so you really have to try yourself first! If I understand correctly you want to load the linked pages with ajax if you click on them. Lets reverse that sentence to understand the problem better. 1. Clicking links sho

Re: [Moo] Request.JSON

http://jsfiddle.net/Jemrp/ is doing a POST request according to the Network tab in the chrome developer console. On Tue, Jul 10, 2012 at 1:26 PM, Lee wrote: > Possibly a silly question, but I've been using Request.JSON and am getting > unexpected results, possibly due to my own tiredness and/or

Re: [Moo] moo port of real-shadow

Here you go :P https://github.com/arian/real-shadow/commit/287e3b6bac0452c9afc7247fb81ce80559c9b2d3 On Thu, Jul 5, 2012 at 5:17 PM, Philip Thompson wrote: > Why don't you create it? The code's there and appears as though it'd be a > fairly straight-forward port... =D > > ~Philip > > > On Thu, Jul

Re: [Moo] Re: XML manipulation via Javascript

That note should be added/changed in the MooTools docs probably... On Tue, Jul 3, 2012 at 11:04 PM, Arian Stolwijk wrote: > console.log only logs a representation of the nodes. > .clone() uses .cloneNode() ( > https://developer.mozilla.org/en/DOM/Node.cloneNode), so it shouldn'

  1   2   3   4   >