correction. My comment was wrong. The web2py code is correct.
On Friday, 6 March 2015 11:18:24 UTC-6, Massimo Di Pierro wrote:
>
> I had no idea. I will change this immediately.
>
> On Friday, 6 March 2015 06:27:55 UTC-6, Francisco Costa wrote:
>>
>>
>>
>> On Saturday, 31 January 2015 03:24:04 UTC, Massimo Di Pierro wrote:
>>>
>>> Niphlod. Calm down. Everything is going to be fine. ;-)
>>>
>>> In fact, I almost did not know JS when I started web2py and avoided it
>>> as the plague. Today I like it a log.
>>>
>>> Back to the original question. Assuming we are diagnosing the problem
>>> correctly (and Niphlod in my experience is 100% right) there are three
>>> solutions:
>>>
>>> 1)
>>>
>>> $(document).ready(function() { ... do something after the page loads
>>> ...});
>>>
>>> 2) (new shorthand notation for the above):
>>>
>>> $(function() { ... do something after the page loads ...});
>>>
>>> 3)
>>>
>>> simply import your JS file after the rest of pages, after </body>. This
>>> is a common practice and if you look into layout.html we often import js
>>> code after </body> so it executed after everything else loads.
>>>
>>
>> Hi Massimo,
>> I must point that <script> elements should be loaded right *before* the
>> </body> for valid HTML:
>> http://stackoverflow.com/questions/3037725/is-it-wrong-to-place-the-script-tag-after-the-body-tag
>>
>>
>>>
>>> Anyway. The diagnose may still be wrong. Use the Chrome JS console and
>>> see if you get any error there.
>>>
>>> Massimo
>>>
>>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
