[Moo] Re: How to code entity classes

2011-11-12 Thread Fli7e
something like this ... var Stations = {}; var Vehicles = {}; var Activities = new Class({ Implements: [Options], 'options' : { 'startDate' : null, 'endDate' : null, 'station' : null, 'vehicles' : [] },

[Moo] HTML5 Form API Compatibility library

2011-11-12 Thread Daniel Antonio Peraza Cedrez
Hi guys. Looking to the Modernizr feature detection library, I wonder if there is any other moo tools -based library which nicely integrates existing widgets as the Aaron's DatePicker, and the Moo Form Validation library to work as fallback APIs for browsers that don't support the new HTML5 For

Re: [Moo] Re: JSON encoding Class instances

2011-11-12 Thread Sanford Whiteman
> Anyway, this would fit better the other thread I've opened (http:// > www.google.com/url?sa=D&q=http://groups.google.com/group/mootools-users/browse_thread/thread/7e3ce3a75a9f771&usg=AFQjCNEmzIOVds6a7bDIprS1MbSagZ_Vmg). Remember that people are accessing the groups via e-mail; you should inclu

[Moo] Re: JSON encoding Class instances

2011-11-12 Thread Blackbird
Hi Fli7e, This code looks complex to me, to provide such basic functionality. Not "KISS" IMO, I prefer my "get" methods ;) Anyway, this would fit better the other thread I've opened (http:// www.google.com/url?sa=D&q=http://groups.google.com/group/mootools-users/browse_thread/thread/7e3ce3a75a9f77

[Moo] Re: JSON encoding Class instances

2011-11-12 Thread Fli7e
I exactly did what Aaron mentioned some weeks ago (auto creating getter Functions). This is what i came up with - works very well (for me): var myNewClass = new Class({ ... options: { 'selectors' : {}, 'styles' : {}, 'states' : {}

[Moo] Forcing MooTools not to extend Natives

2011-11-12 Thread Oskar Krawczyk
Is there a semi-straightforward way into forcing MooTools (1.4+) not to extend natives, without rewriting significant chunks of core? I found myself in a situation where extending natives is not an option, and I really want to use Moo - unfortunately cannot wait for Milk. Basically, I'd need Mo

[Moo] Re: JSON encoding Class instances

2011-11-12 Thread Blackbird
Hi Aaron, I didn't experience the recursion error you're mentioning in 3). Since your comments were very interesting and wanting to investigate this further, I opened a new topic: http://groups.google.com/group/mootools-users/browse_thread/thread/7e3ce3a75a9f771 On Nov 11, 10:28 pm, Aaron Newton

[Moo] How to code entity classes

2011-11-12 Thread Blackbird
Hello, I don't really know the best way to code entity classes in Mootools. Let's consider the following entities: - Activity: Contains the following properties: ¤ startDate (of type date) ¤ endDate (of type date) ¤ station (of type Station entity) ¤ vehicles (li

[Moo] Re: getAttributeNodeNS vs. getAttributeNS

2011-11-12 Thread Fli7e
ah, ok - haven't looked into the slick issues on github ... On 12 Nov., 10:41, Arian Stolwijk wrote: > Yes, see this Slick issue:https://github.com/mootools/slick/issues/61 > > > > > > > > On Sat, Nov 12, 2011 at 9:39 AM, Fli7e wrote: > > cheers Mootoolers, > > > lately i recogniced the JS-Conso

Re: [Moo] getAttributeNodeNS vs. getAttributeNS

2011-11-12 Thread Arian Stolwijk
Yes, see this Slick issue: https://github.com/mootools/slick/issues/61 On Sat, Nov 12, 2011 at 9:39 AM, Fli7e wrote: > cheers Mootoolers, > > lately i recogniced the JS-Console in my Firefox cluttered allover > with the following statement after upgrading to 8.0 (maybe it already > was there in

[Moo] getAttributeNodeNS vs. getAttributeNS

2011-11-12 Thread Fli7e
cheers Mootoolers, lately i recogniced the JS-Console in my Firefox cluttered allover with the following statement after upgrading to 8.0 (maybe it already was there in the 7.x but i never stumbled upon): Warning: getAttributeNodeNS () should not be used anymore. Instead, use getAttribute (). I