@Anthony
I never said that the scaffolding can't change, I said that web2py 
currently can't apply bs3 per default without to change some core code but 
your and Niphlod solutions have cleared my doubts. In fact I have ready a 
welcome app founded on bs3 and jQuery 2.0.3.   
@Niphold
Thank you. If I had known it before I would have saved a bit of time. 
Regarding the navbar with submenus, web2py already managed it before the 
official adoption by bs2. I used it in my application.

Il giorno martedì 20 agosto 2013 23:06:34 UTC+2, Niphlod ha scritto:
>
> +1 on Anthony and on the fact that having some pretty 
> "maintained-out-of-band kickass layouts" is somewhat missing in web2py.
> I'm waiting on the final release to test bs3, but for example the 
> structure of response.menu has been definitely a PITA to work with bs2 and 
> it's going to be even more PITA on bs3. 
> It's true that welcome hasn't hard constraint, but its also true that 
> probably users will have to rethink to their menu structure before 
> switching to bs3. This is somewhat a "conflict" between what has always 
> been a nested structure in web2py (historical superfish handled it 
> perfectly) and the new "flatty" layouts that favour a streamlined-flatty 
> menu structure, mainly because responsive templates had always some issues 
> displaying them (of course, this is not strictly a bs3 issue, but more of a 
> new "design fashion").
> Again, some examples on how to maintain submenus in bs3 are yet on the 
> interwebs (http://bootply.com/71520), but lets put this in kind words.... 
> don't expect to switch the layout from bs2 to bs3 to get instant adaptation.
>
> On Tuesday, August 20, 2013 10:34:50 PM UTC+2, Anthony wrote:
>>
>> On Tuesday, August 20, 2013 1:22:19 PM UTC-7, Paolo Caruccio wrote:
>>
>>> Unfortunately bs3 has dropped some components used by web2py, for 
>>> example submenus, has changed many classes and so on. In other words it's a 
>>> different framework that requires changes in web2py code which - currently- 
>>>  infringe the backward compatibility. Moreover IE7 and FF3.6 aren't 
>>> supported anymore. Of course it's possible create customized html layouts 
>>> based on bs3 but I don't think that web2py can apply for default this new 
>>> framework.
>>>
>>
>> Backward compatibility does not apply to the scaffolding app (it has 
>> changed many times in the past) -- when you upgrade, you don't have to 
>> upgrade your app (the scaffolding is just a starting point). There is also 
>> no hard requirement that the scaffolding layout/CSS must work on all 
>> historical versions of IE and FF. Not saying we should switch immediately, 
>> but these are not necessarily hard constraints.
>>
>> Anthony 
>>
>

-- 

--- 
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/groups/opt_out.

Reply via email to