Modules: use of non-module code as a dependency

[Aymeric Vitte]

I think I have already raised 10 times at least the fact that the 
current module proposal does not allow to load a non module so both are 
complementary and can interact between each others.

<script ..> is not available in non browsers environments

and 3) is unnecesary complicate

Le 30/06/2012 20:19, David Herman a écrit :
> On Jun 30, 2012, at 11:06 AM, James Burke wrote:
>
>> Possible answers:
>>
>> 1) Unsupported. Error occurs.
>>
>> 2) jQuery is suggested to provide a jquery.es.js file that uses the
>> new keywords.
>>
>> 3) Proposed: When jquery.js is compiled, and no import/module/export
>> modules are found, then the Loader will execute jquery.js to see if it
>> exports a value via a runtime API. It uses that value to then finish
>> wiring up the local jQuery reference for module foo.
> I'm curious why you didn't include what seems like the most straightforward answer to me: jQuery continues to work as it did before, and just like always, you include it via a script tag and subsequently access it as a global:
>
> <script src="jquery.js"></script>
> <script>
> ... $('#foo').blah().blah() ...
> </script>
>
> I'm wondering why you didn't include this option -- is it just because jQuery is a special case that creates globals, whereas you also want this to work for modules that don't create globals?
>
> Dave
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss

-- 
jCore
Email :  avitte at jcore.fr
Web :    www.jcore.fr
Webble : www.webble.it
Extract Widget Mobile : www.extractwidget.com
BlimpMe! : www.blimpme.com