thanks
This:
2) the code must be relatively well written (it will likely be combed over
by the development team before it goes out).

And this:
4) it should follow the general design principals that exist throughout the
-core and -more libraries.

Are the things I was aiming at.
I will wait for the more then

I M

On Thu, Feb 19, 2009 at 1:52 PM, nutron <[email protected]> wrote:

> It's the official plugin repository for the framework. By definition, the
> contributors to it *are* the MooTools team. That said, the criteria to be a
> MooTools -more developer are only that you are a) good at writing MooTools
> code and b) consistently contribute to the project. In other words, anyone
> can get involved with -more. All you have to do is fork the code in github
> and start checking in bug fixes or whatever. You can fix documentation
> errors, fix bugs, write unit tests, etc.
> You can also submit your own plugins for the repository, but it's not a
> drop-off box. We aren't interested in just taking things from people - if
> you are involved and are committed, then adding your own plugins will be
> welcome. If you just have something we think would be cool to include, we're
> not as interested.
>
> The criteria for a plugin being accepted in to -more are as follows:
>
> 1) there must be a valid use case for the code - not just something that's
> kinda cool that no one can figure out how to use.
> 2) the code must be relatively well written (it will likely be combed over
> by the development team before it goes out).
> 3) it should, when possible, build on existing plugins if possible.
> 4) it should follow the general design principals that exist throughout the
> -core and -more libraries.
>
> Additionally, a minority of -more developers must agree that it belongs
> (i.e. not just you).
>
> -Aaron
>
> On Thu, Feb 19, 2009 at 10:38 AM, Itay Moav (via Nabble) <
> ml-user%2b132720-647556...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2354771&i=0>
> > wrote:
>
>> mootools-more is developed by the Mootools team, or donations from us
>> users?
>>
>> On Thu, Feb 19, 2009 at 1:28 PM, nutron 
>> <anut...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2354694&i=0>
>> > wrote:
>>
>>> Note that MooTools -more will soon be getting a form validator of it's
>>> own. It has already been translated into 15 languages.
>>>
>>> On Thu, Feb 19, 2009 at 6:35 AM, Itay Moav (via Nabble) <
>>> ml-user%2b132720-647556...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2354634&i=0>
>>> > wrote:
>>>
>>>> thanks all
>>>>
>>>>
>>>> On Thu, Feb 19, 2009 at 7:05 AM, Thierry bela nanga 
>>>> <bna...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2353296&i=0>
>>>> > wrote:
>>>>
>>>>> I just want to add something about translation,
>>>>> I have a very simple way to handle it, I use a Hash,
>>>>>
>>>>> var Language = $H();
>>>>>
>>>>> var English = {key1: "value1", key2: "value2", ...}
>>>>> var French= {key1: "value1_fr", key2: "value2_fr", ...}
>>>>> //switch to english
>>>>> Language.extend(English);
>>>>>
>>>>> //switch to french
>>>>> Language.extend(French);
>>>>>
>>>>>
>>>>> in my classes I just use Language.get(key) to output any text
>>>>>
>>>>>
>>>>> and it works fine.
>>>>>
>>>>>
>>>>>
>>>>> in my real use, I dont use objects (English, French)  like in the
>>>>> example but I generate hash values with the cms current language (here is
>>>>> the joomla code)
>>>>>
>>>>> //php
>>>>> $lang = array()
>>>>>
>>>>> foreach(array( //list of keywords here   ) as $k)
>>>>>     //get the translation
>>>>>     $lang[$k] = JText::_($k);
>>>>>
>>>>> and then I extend the language hash on the fly
>>>>>
>>>>> Language.extend('.<?php echo getJSObject($lang);      ?>.');
>>>>>
>>>>> where getJSObject is a function that takes an array and return a
>>>>> javascript object, a king of json encoding :)
>>>>>
>>>>>
>>>>>
>>>>> - cheers
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, Feb 19, 2009 at 12:39 PM, Lennart 
>>>>> <lenn...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2353296&i=1>
>>>>> > wrote:
>>>>>
>>>>>>
>>>>>> Or you can check it out here:
>>>>>> http://pilon.nl/mootools/2008/11/28/hefvalidator-for-mootools-12/
>>>>>>
>>>>>> Updated to 1.2 and with multi-language support.
>>>>>>
>>>>>> LP
>>>>>>
>>>>>> On Feb 19, 10:25 am, ryan 
>>>>>> <rtnetwo...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2353296&i=2>>
>>>>>> wrote:
>>>>>> > Hello
>>>>>> >
>>>>>> > I have used it, and updated it for 1.2...
>>>>>> > Email me 
>>>>>> > (r...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2353296&i=3>),
>>>>>> and I'll send you the code (or you can
>>>>>> > ask me whatever problems you are having).
>>>>>> >
>>>>>> > Ryan
>>>>>> >
>>>>>> > On Feb 19, 2:30 am, Itay Moav 
>>>>>> > <itay.malimo...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2353296&i=4>>
>>>>>> wrote:
>>>>>> >
>>>>>> > > thanks,
>>>>>> >
>>>>>> > > I will certainly review this code, but for the sake of healthy
>>>>>> competition,
>>>>>> > > be happy if someone  who used FValidator with moo 1.2 with no
>>>>>> problems and
>>>>>> > > could tell about this.
>>>>>> >
>>>>>> > > I M
>>>>>> >
>>>>>> > > On Wed, Feb 18, 2009 at 9:14 PM, Frank Rossi 
>>>>>> > > <fr...@...<http://n2.nabble.com/user/SendEmail.jtp?type=node&node=2353296&i=5>>
>>>>>> wrote:
>>>>>> >
>>>>>> > > > You can use FormCheck, which is great!
>>>>>> > > >http://mootools.floor.ch/en/index.htm
>>>>>> >
>>>>>> > > > moo, too
>>>>>> > > > Frank
>>>>>> >
>>>>>> > > > On Wed, 18 Feb 2009 19:42:58 -0500, Itay Moav wrote:
>>>>>> > > > > Moo
>>>>>> >
>>>>>> > > > > Did anyone use FValidator with mootools v1.2+ (as it says in
>>>>>> the site
>>>>>> > > > > it is build on 1.1)?
>>>>>> > > > >http://zendold.lojcomm.com.br/fvalidator/
>>>>>> >
>>>>>> > > > > I M
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> fax : (+33) 08 26 51 94 51
>>>>>
>>>>
>>>>
>>> The MooTools Tutorial: www.mootorial.com Clientcide: www.clientcide.com
>>>
>>> ------------------------------
>>> View this message in context: Re: Any experience with FValidator in
>>> mootools 
>>> 1.2+<http://n2.nabble.com/Any-experience-with-FValidator-in-mootools-1.2%2B-tp2350345p2354634.html>
>>> Sent from the MooTools Users mailing list 
>>> archive<http://n2.nabble.com/MooTools-Users-f660466.html>at Nabble.com.
>>>
>>
>>
> The MooTools Tutorial: www.mootorial.com Clientcide: www.clientcide.com
>
> ------------------------------
> View this message in context: Re: Any experience with FValidator in
> mootools 
> 1.2+<http://n2.nabble.com/Any-experience-with-FValidator-in-mootools-1.2%2B-tp2350345p2354771.html>
> Sent from the MooTools Users mailing list 
> archive<http://n2.nabble.com/MooTools-Users-f660466.html>at Nabble.com.
>

Reply via email to