Re: [Moo] Re: Problem with Form.Request and evalScripts?

var x = 'x'; var foo = function(){ var x = 'foo'; }; foo(); //x is still 'x' var bar = function(){ x = 'bar'; }; bar(); //x is now 'bar' window.addEvent('domready', bar); //changes x to 'bar' on domready window.addEvent('domready', function(){ x = 'bar'; }); //the *exact* same behavior Bes

[Moo] Re: Why don't we create a Mootools IDE

My wish for a Mootooled IDE is runtime Object property introspection just like Chrome's js console with autocompletion. On Jan 21, 9:41 am, Ryan Rampersad wrote: > Aptana uses an outdated version of Mootools and you can't force it to use > auto-completion and a newer version. I think this is beca

Re: [Moo] Re: Request.response.xml not 'mootooled' in IE.

> No, it doesn't. i.e. $(request.response.xml) returns null becaouse > request.response.xml.toElement does not exist. You might try wrapping the IE `xml` attribute using Elements.from: http://mootools.net/shell/2dupv/2/ -- S.

[Moo] Re: Problem with Form.Request and evalScripts?

Yes, sorry. I assumed this was so obvious to the rest of you that I didn't bother explaining. It would appear that declaring "var STUFF" keeps the "STUFF" object scoped (and here's where I get a little fuzzy) to the function that is fired on 'domready'. Removing "var" makes "STUFF" a global var

Re: [Moo] Why don't we create a Mootools IDE

Aptana uses an outdated version of Mootools and you can't force it to use auto-completion and a newer version. I think this is because mootools doesn't by default have a java-doc like structure for the IDE to pull from. I'd totally love some IDE. On Wed, Jan 20, 2010 at 6:56 PM, Barry van Oudtsho

Re: [Moo] Why don't we create a Mootools IDE

I use Geany with a dark Tango theme I put together (http://www.barryvan.com.au/2009/01/geany-ide-tango-dark-colour-scheme/). It works well enough, but the symbol browser doesn't understand Moo classes. It handles object literals and function()-style objects well enough, though. The main reason

Re: [Moo] Re: Problem with Form.Request and evalScripts?

Care to share your revelation with me/us? Is it because when defined with "var" no global variable is defined and so the class instance (STUFF) is not accessible in the HTML? Cheers, Daniel On 21.01.2010, at 00:21, hairbo wrote: > Hey Aaron, > > Thanks for the reply. Let me just say...OMFG.

Re: [Moo] Re: Problem with Form.Request and evalScripts?

ha. yeah. easy mistake. no worries. On Wed, Jan 20, 2010 at 3:21 PM, hairbo wrote: > Hey Aaron, > > Thanks for the reply. Let me just say...OMFG. > > I did (and usually have done) this: > > window.addEvent('domready',function(){ >var STUFF = new MyClass(); > }); > > ...instead of this:

[Moo] Re: Problem with Form.Request and evalScripts?

Hey Aaron, Thanks for the reply. Let me just say...OMFG. I did (and usually have done) this: window.addEvent('domready',function(){ var STUFF = new MyClass(); }); ...instead of this: window.addEvent('domready',function(){ STUFF = new MyClass(); }); sigh. Thanks for the help

Re: [Moo] Re: Problem with Form.Request and evalScripts?

On Wed, Jan 20, 2010 at 2:36 PM, hairbo wrote: > Okay, there may be things here that I don't understand, so > apologies... > > 1) I thought this function was supposed to be able to handle a mix of > HTML and JS, and would be smart enough to evaluate any JS it finds in > the returned data. If thi

[Moo] Re: Problem with Form.Request and evalScripts?

Okay, there may be things here that I don't understand, so apologies... 1) I thought this function was supposed to be able to handle a mix of HTML and JS, and would be smart enough to evaluate any JS it finds in the returned data. If this is the case (as it does appear to be), then removing the s

Re: [Moo] Re: Problem with Form.Request and evalScripts?

I am not sure, but you should start by removing the .. tags from the response, you can eval JS data only.. On Wed, Jan 20, 2010 at 11:58 PM, hairbo wrote: > Hmm...I *was* able to get my above example to work, but trying > different javascript fails, so something else has to b

[Moo] Re: event.stop is not working

The inspiration to learn MooTools. Though I can't still understand why this problem is happening. It works the first time you click it as the event is stop. Yet, the second time you click it, it does not stop the event. On Jan 19, 4:53 pm, Roman Land wrote: > Then where are you getting the "inspi

[Moo] Re: Problem with Form.Request and evalScripts?

Hmm...I *was* able to get my above example to work, but trying different javascript fails, so something else has to be going on. On Jan 20, 3:53 pm, hairbo wrote: > Hi all, > > I'm not sure how to set up an Ajax test in the Mooshell, so here's > hoping I can explain my issue here. > > I'm trying

[Moo] Problem with Form.Request and evalScripts?

Hi all, I'm not sure how to set up an Ajax test in the Mooshell, so here's hoping I can explain my issue here. I'm trying to submit form data using Form.Request, and then pass back some javascript with the HTML that gets returned. I'd like the Javascript to get evaluated. According to the Form.

[Moo] Re: Horizontal scrolling

Thank you so much people! I read and considered all of the posts. Your help was really appreciated, made my day better :) Works like a charm now! -Lenkey On Jan 20, 8:21 pm, holycrapperluigi wrote: > Sorry I had a is the monitor plugged in moment, should have read the > previous post before I t

[Moo] Re: Horizontal scrolling

Sorry I had a is the monitor plugged in moment, should have read the previous post before I typed. :-X Aaron saves the day. On Jan 20, 1:21 pm, Aaron Newton wrote: > 1) document.body is a pointer, not a string - just *document.body* not * > 'document.body'* > **2) Your mooshell wasn't working b

[Moo] Re: How to fire an event when a specific console.log() has been output?

have you tried onComplete: initializeTracklist instead of onComplete: function(){} yes () is taken out intentionally On Jan 20, 9:51 am, Lorenzo De Tomasi wrote: > I have added this code to MooFlow Viewer: > >                 if(cur.rel == 'html') { // if a...@rel=html], create a > div:last-c

Re: [Moo] Re: Horizontal scrolling

1) document.body is a pointer, not a string - just *document.body* not * 'document.body'* **2) Your mooshell wasn't working because you weren't including -more (where Fx.Scroll lives). http://mootools.net/shell/kEfN3/4/ << working On Wed, Jan 20, 2010 at 9:15 AM, Aske wrote: > @Florence: Great

[Moo] Re: Horizontal scrolling

I would try divs. On Jan 20, 12:55 pm, holycrapperluigi wrote: > What about a different approach? > > 1. First think how a photoshop mask works, then think how to put that > in code. > > 2. Clone the custom logic scroll event to the 'click' event of the > number element (be careful of bubbling or

[Moo] Re: Horizontal scrolling

What about a different approach? 1. First think how a photoshop mask works, then think how to put that in code. 2. Clone the custom logic scroll event to the 'click' event of the number element (be careful of bubbling or propagation stuff) 3. Check browsers IE make sure it works. I am a bit bias

Re: [Moo] Re: Horizontal scrolling

it's working now, you must include mootools more before you use Fx.Scroll http://mootools.net/shell/kEfN3/3/ On Wed, Jan 20, 2010 at 6:34 PM, Thierry bela nanga wrote: > you should not put 'document.body', > > but document.body instead (no quote) > > > > On Wed, Jan 20, 2010 at 6:15 PM, Aske

Re: [Moo] Re: Horizontal scrolling

you should not put 'document.body', but document.body instead (no quote) On Wed, Jan 20, 2010 at 6:15 PM, Aske wrote: > @Florence: Great advice! > > @cbolson & Aaron Newton, i tried both, but they do no seem to work. > > I put it in the shell: http://mootools.net/shell/kEfN3/ > > Anyone with

[Moo] Re: Horizontal scrolling

> @cbolson & Aaron Newton, i tried both, but they do no seem to work. Both of the suggested solutions do work, you just haven't implemented them fullly. Fx.Scroll is part of "more" so you need to include that (in mooshell it is an option that is defined in the "settings" panel in the left- hand s

[Moo] Re: Horizontal scrolling

@Florence: Great advice! @cbolson & Aaron Newton, i tried both, but they do no seem to work. I put it in the shell: http://mootools.net/shell/kEfN3/ Anyone with great coding skills? To repeat: Press one of the numbers in the navbar in the bottom, and the whole window (body), should scroll to th

Re: [Moo] Why don't we create a Mootools IDE

On a related note – is anyone aware of someone doing work in the MooTools-lint direction? ___ Oskar Krawczyk http://nouincolor.com On Wed, Jan 20, 2010 at 3:42 PM, Roman Land wrote: > I use Netbeans, the colors are good (and customizable), got my own dark > theme so let me know if your intere

Re: [Moo] Why don't we create a Mootools IDE

I use Netbeans, the colors are good (and customizable), got my own dark theme so let me know if your interested.. :) BTW, TextMate is MAC only, other then developing for the iPhone (no other choice really) I dont like dealing with OSX, thanks to Steve Jobs and the Apple customer base (too much bli

Re: [Moo] Why don't we create a Mootools IDE

What kind of features are you looking for? I find TextMate to be customizable enough. On Jan 20, 2010, at 8:34 AM, Roman Land wrote: Vote +1 On Wed, Jan 20, 2010 at 5:31 PM, Ren Yushiro wrote: I'm sure that with the help of an IDE, we'll be able to code a lot faster, especially in big pro

Re: [Moo] Why don't we create a Mootools IDE

Vote +1 On Wed, Jan 20, 2010 at 5:31 PM, Ren Yushiro wrote: > I'm sure that with the help of an IDE, we'll be able to code a lot > faster, especially in big project (mine has more than 100 classes > already). I've searched for an IDE that help but couldn't. Aptana said > it supported mootools bu

Re: [Moo] How to fire an event when a specific console.log() has been output?

You can add a custom event (addEvent) to the window object and then possibly trigger a fireEvent from your onComplete function. More info can be found in the docs ;) HTH, -- Roman On Wed, Jan 20, 2010 at 4:51 PM, Lorenzo De Tomasi < lorenzo.detom...@gmail.com> wrote: > I have added this code to

[Moo] Why don't we create a Mootools IDE

I'm sure that with the help of an IDE, we'll be able to code a lot faster, especially in big project (mine has more than 100 classes already). I've searched for an IDE that help but couldn't. Aptana said it supported mootools but it didn't understand mootools' great OOP. I've tried Spket and gave t

[Moo] How to fire an event when a specific console.log() has been output?

I have added this code to MooFlow Viewer: if(cur.rel == 'html') { // if a...@rel=html], create a div:last-child in div#mooflow if(!$chk(this.htmlDesc)) { this.htmlDesc = new Element('div', {'id': 'htmlDesc', 'class': 'show'}).setStyles ({'display':'none','o

Re: [Moo] getting cliche - problem adding to the forge

Yes, it wasnt. You could create a ticket at the forge repo to help the dev to remember this problem, and quickly fix this issue. http://github.com/Guille/PluginsKit/issues Thanks. -- Fábio Miranda Costa Solucione Sistemas Engenheiro de interfaces On Wed, Jan 20, 2010 at 12:17 PM, אריה גלזר w

Re: [Moo] getting cliche - problem adding to the forge

i added all the needed stuff before first committing to the forge (i have a full workflow for this by now[?]). not sure if the rest of the comment was directed to me --- אריה גלזר 052-5348-561 5561 2010/1/20 Fábio M. Costa > @dude > Hi, this seems to be a problem at the update of the re

Re: [Moo] getting cliche - problem adding to the forge

@dude Hi, this seems to be a problem at the update of the repositories on the forge. Were the tags there when you first added your repo to the forge? Or it gave you this error and then you tried to add it again? I think that there should be added the '--tags' option on the pull of the forge. This

[Moo] Re: Request.response.xml not 'mootooled' in IE.

On Jan 20, 10:11 am, Sanford Whiteman wrote: > > Unfortunately, I cannot tell my clients not to use IE, so I need an > > other solution. Any idea's? My best hope is that IE objects would be > > mootools extended. There might be other objects that are not. > > Wrapping in $() should fix up such i

Re: [Moo] Request.response.xml not 'mootooled' in IE.

> Unfortunately, I cannot tell my clients not to use IE, so I need an > other solution. Any idea's? My best hope is that IE objects would be > mootools extended. There might be other objects that are not. Wrapping in $() should fix up such irregularities, no? IE8 did add support for extendin

[Moo] Request.response.xml not 'mootooled' in IE.

Hi, Using IE8 v. FF 3.5.7, MT 1.2.3, windows XP SP 3. Request.response.xml seems not to be a mootools extended object. I.e. it doesn't have method 'get' nor does it have other mootools methods. With Request, I retrieve some xml data from a server. I want to walk through this data and retrieve so

[Moo] getting cliche - problem adding to the forge

trying to add a plugin to the forge, but getting the message GitHub repository has no tags. At least one tag is required for this repo , which has tags (even added an extra one to make sure it's not a single tag bug or something like that). this happens before