[Moo] Re: Unexpected behaviour in URI class

2011-11-13 Thread Lennart
Fixed it by using New URI(window.location). But think it should work by using new URI( {base: true/false} ) ; On Nov 13, 10:37 pm, Lennart wrote: > That just gives me the base href. > > On Nov 13, 7:21 pm, Fli7e wrote: > > > > > > > > > Have you simly tried: > > > URI.base.toString() > > > Uri.b

[Moo] Re: Unexpected behaviour in URI class

2011-11-13 Thread Lennart
That just gives me the base href. On Nov 13, 7:21 pm, Fli7e wrote: > Have you simly tried: > > URI.base.toString() > > Uri.base is auto-created on load and the toString() will return the > full location content. > > On 13 Nov., 17:26, Lennart wrote: > > > > > > > > > I'm trying to get the window

Re: [Moo] Forcing MooTools not to extend Natives

2011-11-13 Thread André Fiedler
How about ExtJS 4? It's something like Moo but doesn't extend natives. I've used Sencha Touch some weeks now, it's build on top of ExtJS 4, and I like it. You just have to learn how the class architecture works. (implement == mixins ;o)) greetings Sunny Am 13.11.2011 um 21:12 schrieb Oskar Krawcz

Re: [Moo] Forcing MooTools not to extend Natives

2011-11-13 Thread Oskar Krawczyk
It's a very specific project. I will never have any control about the JS being injected in the application. So, I either loose my hair and go with Vanilla JS (I really don't want to go that way), or figure out a way to get Moo not extend natives. O. On Nov 13, 2011, at 9:04 PM, Sanford Whitema

Re: [Moo] Forcing MooTools not to extend Natives

2011-11-13 Thread Sanford Whiteman
> Yes, I know this is the power of MooTools, at least it was, these > days extending natives is just a pain in the neck Oskar, is it a pain in the neck because there's another framework doing the same thing in this project? Browsers have ever-growing support for extending natives, so

Re: [Moo] Forcing MooTools not to extend Natives

2011-11-13 Thread Oskar Krawczyk
Yes, I know this is the power of MooTools, at least it was, these days extending natives is just a pain in the neck - hence Milk :-) My questions stands. O. On Nov 13, 2011, at 8:24 PM, Philip Thompson wrote: > It was my understanding that this is one of the powers of Mootools - > extending n

Re: [Moo] Forcing MooTools not to extend Natives

2011-11-13 Thread Philip Thompson
It was my understanding that this is one of the powers of Mootools - extending native prototypes. Without it, you end up with something like jQuery which is function-based. I may be misunderstanding your question - if so, please set me straight! :) ~Philip On Sat, Nov 12, 2011 at 5:46 AM, Oskar

[Moo] Re: Unexpected behaviour in URI class

2011-11-13 Thread Fli7e
Have you simly tried: URI.base.toString() Uri.base is auto-created on load and the toString() will return the full location content. On 13 Nov., 17:26, Lennart wrote: > I'm trying to get the window.location, but using the URI class (i want > to set some data in the querystring later). My page h

[Moo] Unexpected behaviour in URI class

2011-11-13 Thread Lennart
I'm trying to get the window.location, but using the URI class (i want to set some data in the querystring later). My page has a base href ( https://www.domain.ext/foo/ ), the actual window.location is https://www.domain.ext/foo/bar. If I try new URI().toString(), it gives me the base href, which