I'm not confortable with having something cdn dependant. By default apps
should be available also if no internet connectivity is assured.
+1 with defaulting to local and a comment to enable the cdn version.
On Monday, February 24, 2014 1:05:13 PM UTC+1, LightDot wrote:
>
> Note to those not reading this group from a web interface: I edited my
> post to fix copy paste typos in the code. This is the correct code again:
>
> <!-- All JavaScript at the bottom, except for Modernizr and Respond
> If you need to use local copies of modernizr.min.js or respond.js
> download them in
> static/js sub-folder and replace the script links in the following
> conditional comments with
> <script src="{{=URL('static','js/modernizr.min.js')}}"></script>
> <script src="{{=URL('static','js/respond.js')}}"></script> -->
> <!-- <script src="https://cdnjs.cloudflare.com/ajax/libs/modernizr/2.7.1/
> modernizr.min.js"></script> -->
> <!--[if lt IE 9]>
> <script src="https://cdnjs.cloudflare.com/ajax/libs/respond.js/1.4.
> 2/respond.js"></script>
> <![endif]-->
>
> I apologize for the mix up.
>
> Regards
>
>
> On Monday, February 24, 2014 12:28:19 PM UTC+1, LightDot wrote:
>>
>> How about putting Paolo's bootstrap3.py into contrib an have welcome app
>> import it from there? His module provides most of the bootstrap 3 support
>> (forms, navigation, etc.). We could remove all this from core web2py.
>>
>> As for the welcome app static files, these are redundant (leftovers) now
>> and should be deleted:
>>
>> static/css/bootstrap-responsive.min.css
>> static/css/web2py_bootstrap.css
>> static/css/web2py_bootstrap_nojs.css
>> static/js/dd_belatedpng.js
>> static/js/web2py_bootstrap.js
>>
>> This one is old (v3.0.3, should be v3.1.1):
>> static/css/bootstrap-theme.min.css
>>
>> I think we should define modernizr.custom.js to use a CDN and remove it
>> from the static files too, same as respond.js is defined now. I also think
>> we should be suggesting users to use a free CDN instead of Maxcdn, so this
>> should be in layout.html instead of what is now:
>>
>> <!-- All JavaScript at the bottom, except for Modernizr and Respond
>> If you need to use local copies of modernizr.min.js or respond.js
>> download them in
>> static/js sub-folder and replace the script links in the following
>> conditional comments with
>> <script src="{{=URL('static','js/modernizr.min.js')}}"></script>
>> <script src="{{=URL('static','js/respond.js')}}"></script> -->
>> <!-- <script src="
>> https://cdnjs.cloudflare.com/ajax/libs/modernizr/2.7.1/modernizr.min.js";></script>
>>
>> -->
>> <!--[if lt IE 9]>
>> <script src="
>> https://cdnjs.cloudflare.com/ajax/libs/respond.js/1.4.2/respond.js
>> "></script>
>> <![endif]-->
>>
>> Another minor thing for the new layout.html: header section should also
>> have id="header", same as other sections have.
>>
>> I didn't have time to test the changes to gluon/tools.py yet, I'll check
>> out trunk a bit later...
>>
>> (note: edited to fix a typo in the code)
>>
>> Regards
>>
>>
>> On Monday, February 24, 2014 9:40:22 AM UTC+1, Niphlod wrote:
>>>
>>> in my POV instead of reducing all alterations of default widgets in
>>> javascript we should ship new widget sets alltogether.
>>> This was discussed long ago but nobody seemed to care .... we can't
>>> really start supporting every css framework out there unless we change the
>>> way widgets are generated.
>>> Going "bootstrap3" with this much FOUC is good for a plugin
>>> proof-of-concept but I'd not ship it as a scaffolding application...
>>>
>>> On Monday, February 24, 2014 7:12:22 AM UTC+1, Massimo Di Pierro wrote:
>>>>
>>>> Can we get rid of web2py-bootstrap3.js?
>>>>
>>>> Do we all these files?
>>>> web2py.css
>>>> bootstrap-responsive.min.css
>>>> bootstrap-theme.min.css
>>>> web2py-bootstrap3.css
>>>> web2py_bootstrap.css
>>>> web2py_bootstrap_nojs.css
>>>>
>>>> can we reduce to two:
>>>> web2py.css
>>>> web2py-bootstrap3.css
>>>>
>>>>
>>>>
>>>> On Monday, 24 February 2014 00:09:48 UTC-6, Massimo Di Pierro wrote:
>>>>>
>>>>> Added some of the missing files. They were created by Paolo but it was
>>>>> my mistake not to post them. They should address most of the issues.
>>>>>
>>>>> On Sunday, 23 February 2014 23:51:04 UTC-6, Ron McOuat wrote:
>>>>>>
>>>>>> I found this on Stack Overflow
>>>>>>
>>>>>>
>>>>>> http://stackoverflow.com/questions/16214326/bootstrap-dropdown-with-hover
>>>>>>
>>>>>> ul.nav li.dropdown:hover ul.dropdown-menu {
>>>>>> display: block;
>>>>>> }
>>>>>>
>>>>>> and I find this solution using CSS in the .css file under welcome
>>>>>> named
>>>>>>
>>>>>> static/css/web2py_bootstrap_nojs.css but not in any other css file.
>>>>>>
>>>>>> However this file is not included by another file anywhere in the
>>>>>> welcome application.
>>>>>>
>>>>>> If this is it I just got lucky is all. :-)
>>>>>>
>>>>>> The Welcome application name header is scrunched up under the menu
>>>>>> bar and partially visible lastest Firefox Ubuntu 12.04 LTS
>>>>>>
>>>>>> The web2py menu item (yellow) doesn't open like in 2.8.2
>>>>>>
>>>>>> Ron
>>>>>>
>>>>>>
>>>>>>
--
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 web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
