Re: [web2py] Re: web2py 2.0 almost done
this is one of the main changes I was looking forward for 2.0, I would rather wait until the integration is complete On Thursday, August 9, 2012 9:43:28 AM UTC-7, AngeloC wrote: Hi Massimo, I think I cannot complete the bootstrap/web2py css merging in time for 2.0, it's really a lot of work and I'm a bit busy these days. Btw, i'm fixing the bug I introduced with issue 896 and I want to share a thought with you. Actually, there is no way to maintain a mobile first approach and make it working on IE other than add something like this to the scaffolding: !-- Makes bootswatch working on IE 7/8 -- !--[if (lt IE 9)] link rel=stylesheet href=/responsivekit/static/css/bootswatch_ie.css ![endif]-- This will make speedier the whole css on not IE browsers because we remove IE specific rules (smaller css), but has the downside to require an extra http get on IE. What do you think? 2012/8/9 Alec Taylor alec.t...@gmail.com javascript: It would be good to have OAuth working for web2py 2 Facebook and LinkedIn still have some issues LinkedIn: https://groups.google.com/forum/#!topic/web2py/SbnQEnXEcOg Facebook: (will add bug report once I've gotten LinkedIn login to work) On Thu, Aug 9, 2012 at 11:25 PM, Massimo Di Pierro massimo@gmail.com javascript: wrote: Can you help us fix the CSS? On Thursday, 9 August 2012 00:29:58 UTC-5, Andrew wrote: Just a note on IE7 navbar behaviour: The Menu has taken a turn for the worse: Initially the Welcome App Sub Menus dissapeared in : welcome css pathc, issue 896, thanks Angelo They then returned in fixed issue qith clicking on toplevel menus except all of the submenus are displayed when the menu first appears and they are all on top of each other. The login options are still blue, and the space between the navbar and Welcome isn't there. See screen shot. On Thursday, August 9, 2012 9:17:17 AM UTC+12, Massimo Di Pierro wrote: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- -- -- Profile: http://it.linkedin.com/in/compagnucciangelo --
Re: [web2py] Re: web2py 2.0 almost done
IE7 is looking normal ! Great work Angelo. Thanks. On Saturday, August 11, 2012 3:11:39 AM UTC+12, AngeloC wrote: Hi Massimo, I fixed compatibility with IE and reverted to a non mobile first approach. I reverted because bootstrap is not mobile first (so we add too little) and for the sake of compatibility with IE. Patch is attached to issue http://code.google.com/p/web2py/issues/detail?id=896 which I cannot reopen. Hope this helps! Angelo 2012/8/10 Angelo Compagnucci angelo.co...@gmail.com javascript: Hi Massimo, I'm writing it right now to fix ie issues! Please be patient until fixed! 2012/8/9 Massimo Di Pierro massimo@gmail.com javascript: This may be ok but where do I get bootswatch_ie.css from? On Thursday, 9 August 2012 11:43:28 UTC-5, AngeloC wrote: Hi Massimo, I think I cannot complete the bootstrap/web2py css merging in time for 2.0, it's really a lot of work and I'm a bit busy these days. Btw, i'm fixing the bug I introduced with issue 896 and I want to share a thought with you. Actually, there is no way to maintain a mobile first approach and make it working on IE other than add something like this to the scaffolding: !-- Makes bootswatch working on IE 7/8 -- !--[if (lt IE 9)] link rel=stylesheet href=/responsivekit/static/** css/bootswatch_ie.css ![endif]-- This will make speedier the whole css on not IE browsers because we remove IE specific rules (smaller css), but has the downside to require an extra http get on IE. What do you think? 2012/8/9 Alec Taylor alec.t...@gmail.com It would be good to have OAuth working for web2py 2 Facebook and LinkedIn still have some issues LinkedIn: https://groups.google.com/**forum/#!topic/web2py/** SbnQEnXEcOghttps://groups.google.com/forum/#%21topic/web2py/SbnQEnXEcOg Facebook: (will add bug report once I've gotten LinkedIn login to work) On Thu, Aug 9, 2012 at 11:25 PM, Massimo Di Pierro massimo@gmail.com wrote: Can you help us fix the CSS? On Thursday, 9 August 2012 00:29:58 UTC-5, Andrew wrote: Just a note on IE7 navbar behaviour: The Menu has taken a turn for the worse: Initially the Welcome App Sub Menus dissapeared in : welcome css pathc, issue 896, thanks Angelo They then returned in fixed issue qith clicking on toplevel menus except all of the submenus are displayed when the menu first appears and they are all on top of each other. The login options are still blue, and the space between the navbar and Welcome isn't there. See screen shot. On Thursday, August 9, 2012 9:17:17 AM UTC+12, Massimo Di Pierro wrote: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- -- -- Profile: http://it.linkedin.com/in/**compagnucciangelohttp://it.linkedin.com/in/compagnucciangelo -- -- Profile: http://it.linkedin.com/in/compagnucciangelo -- Profile: http://it.linkedin.com/in/compagnucciangelo --
Re: [web2py] Re: web2py 2.0 almost done
Hi Massimo, Mobile browser on mobile phones can work in mobile mode or in desktop mode. If you are in desktop mode, without that line, you cannot see the menu because it's faded away. And you cannot click, so the menu is faded and not clickable! In a desktop instead, when a windowed browser has a resolution less than responsive threshold, the menu is yes visible, but it's resize the page at each mouse hovering and makes the menu unusable. So, if you are in a browser with a sufficient resolution, you can see the standard dropdown, when you are on a mobile browser with a narrow resolution but in desktop mode, you can see a flat menu. This restores the default bootstrap behaviour for colllapsible dropdowns. Hope this helps! 2012/8/10 Massimo Di Pierro massimo.dipie...@gmail.com Can you explain the consequences of this line in your patch? if (jQuery(document).width() = 980) On Friday, 10 August 2012 10:11:39 UTC-5, AngeloC wrote: Hi Massimo, I fixed compatibility with IE and reverted to a non mobile first approach. I reverted because bootstrap is not mobile first (so we add too little) and for the sake of compatibility with IE. Patch is attached to issue http://code.google.com/** p/web2py/issues/detail?id=896http://code.google.com/p/web2py/issues/detail?id=896which I cannot reopen. Hope this helps! Angelo 2012/8/10 Angelo Compagnucci angelo.co...@gmail.com Hi Massimo, I'm writing it right now to fix ie issues! Please be patient until fixed! 2012/8/9 Massimo Di Pierro massimo@gmail.com This may be ok but where do I get bootswatch_ie.css from? On Thursday, 9 August 2012 11:43:28 UTC-5, AngeloC wrote: Hi Massimo, I think I cannot complete the bootstrap/web2py css merging in time for 2.0, it's really a lot of work and I'm a bit busy these days. Btw, i'm fixing the bug I introduced with issue 896 and I want to share a thought with you. Actually, there is no way to maintain a mobile first approach and make it working on IE other than add something like this to the scaffolding: !-- Makes bootswatch working on IE 7/8 -- !--[if (lt IE 9)] link rel=stylesheet href=/responsivekit/static/**cs** s/bootswatch_ie.css ![endif]-- This will make speedier the whole css on not IE browsers because we remove IE specific rules (smaller css), but has the downside to require an extra http get on IE. What do you think? 2012/8/9 Alec Taylor alec.t...@gmail.com It would be good to have OAuth working for web2py 2 Facebook and LinkedIn still have some issues LinkedIn: https://groups.google.com/**foru**m/#!topic/web2py/** SbnQEnXEcOghttps://groups.google.com/forum/#!topic/web2py/SbnQEnXEcOg Facebook: (will add bug report once I've gotten LinkedIn login to work) On Thu, Aug 9, 2012 at 11:25 PM, Massimo Di Pierro massimo@gmail.com wrote: Can you help us fix the CSS? On Thursday, 9 August 2012 00:29:58 UTC-5, Andrew wrote: Just a note on IE7 navbar behaviour: The Menu has taken a turn for the worse: Initially the Welcome App Sub Menus dissapeared in : welcome css pathc, issue 896, thanks Angelo They then returned in fixed issue qith clicking on toplevel menus except all of the submenus are displayed when the menu first appears and they are all on top of each other. The login options are still blue, and the space between the navbar and Welcome isn't there. See screen shot. On Thursday, August 9, 2012 9:17:17 AM UTC+12, Massimo Di Pierro wrote: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- -- -- Profile: http://it.linkedin.com/in/**comp**agnucciangelohttp://it.linkedin.com/in/compagnucciangelo -- -- Profile: http://it.linkedin.com/in/**compagnucciangelohttp://it.linkedin.com/in/compagnucciangelo -- Profile: http://it.linkedin.com/in/**compagnucciangelohttp://it.linkedin.com/in/compagnucciangelo -- -- Profile: http://it.linkedin.com/in/compagnucciangelo --
Re: [web2py] Re: web2py 2.0 almost done
I agree the new behavior makes much more sense. Maybe there should be a backward compatibility flag in Auth? mic 2012/8/8 Massimo Di Pierro massimo.dipie...@gmail.com: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- --
Re: [web2py] Re: web2py 2.0 almost done
Thank you AngeloC! On Friday, August 10, 2012 1:50:03 PM UTC+8, AngeloC wrote: Hi Massimo, I'm writing it right now to fix ie issues! Please be patient until fixed! 2012/8/9 Massimo Di Pierro massimo@gmail.com javascript: This may be ok but where do I get bootswatch_ie.css from? On Thursday, 9 August 2012 11:43:28 UTC-5, AngeloC wrote: Hi Massimo, I think I cannot complete the bootstrap/web2py css merging in time for 2.0, it's really a lot of work and I'm a bit busy these days. Btw, i'm fixing the bug I introduced with issue 896 and I want to share a thought with you. Actually, there is no way to maintain a mobile first approach and make it working on IE other than add something like this to the scaffolding: !-- Makes bootswatch working on IE 7/8 -- !--[if (lt IE 9)] link rel=stylesheet href=/responsivekit/static/** css/bootswatch_ie.css ![endif]-- This will make speedier the whole css on not IE browsers because we remove IE specific rules (smaller css), but has the downside to require an extra http get on IE. What do you think? 2012/8/9 Alec Taylor alec.t...@gmail.com It would be good to have OAuth working for web2py 2 Facebook and LinkedIn still have some issues LinkedIn: https://groups.google.com/**forum/#!topic/web2py/** SbnQEnXEcOghttps://groups.google.com/forum/#!topic/web2py/SbnQEnXEcOg Facebook: (will add bug report once I've gotten LinkedIn login to work) On Thu, Aug 9, 2012 at 11:25 PM, Massimo Di Pierro massimo@gmail.com wrote: Can you help us fix the CSS? On Thursday, 9 August 2012 00:29:58 UTC-5, Andrew wrote: Just a note on IE7 navbar behaviour: The Menu has taken a turn for the worse: Initially the Welcome App Sub Menus dissapeared in : welcome css pathc, issue 896, thanks Angelo They then returned in fixed issue qith clicking on toplevel menus except all of the submenus are displayed when the menu first appears and they are all on top of each other. The login options are still blue, and the space between the navbar and Welcome isn't there. See screen shot. On Thursday, August 9, 2012 9:17:17 AM UTC+12, Massimo Di Pierro wrote: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- -- -- Profile: http://it.linkedin.com/in/**compagnucciangelohttp://it.linkedin.com/in/compagnucciangelo -- -- Profile: http://it.linkedin.com/in/compagnucciangelo --
Re: [web2py] Re: web2py 2.0 almost done
Hi Massimo, I fixed compatibility with IE and reverted to a non mobile first approach. I reverted because bootstrap is not mobile first (so we add too little) and for the sake of compatibility with IE. Patch is attached to issue http://code.google.com/p/web2py/issues/detail?id=896 which I cannot reopen. Hope this helps! Angelo 2012/8/10 Angelo Compagnucci angelo.compagnu...@gmail.com Hi Massimo, I'm writing it right now to fix ie issues! Please be patient until fixed! 2012/8/9 Massimo Di Pierro massimo.dipie...@gmail.com This may be ok but where do I get bootswatch_ie.css from? On Thursday, 9 August 2012 11:43:28 UTC-5, AngeloC wrote: Hi Massimo, I think I cannot complete the bootstrap/web2py css merging in time for 2.0, it's really a lot of work and I'm a bit busy these days. Btw, i'm fixing the bug I introduced with issue 896 and I want to share a thought with you. Actually, there is no way to maintain a mobile first approach and make it working on IE other than add something like this to the scaffolding: !-- Makes bootswatch working on IE 7/8 -- !--[if (lt IE 9)] link rel=stylesheet href=/responsivekit/static/** css/bootswatch_ie.css ![endif]-- This will make speedier the whole css on not IE browsers because we remove IE specific rules (smaller css), but has the downside to require an extra http get on IE. What do you think? 2012/8/9 Alec Taylor alec.t...@gmail.com It would be good to have OAuth working for web2py 2 Facebook and LinkedIn still have some issues LinkedIn: https://groups.google.com/**forum/#!topic/web2py/** SbnQEnXEcOghttps://groups.google.com/forum/#!topic/web2py/SbnQEnXEcOg Facebook: (will add bug report once I've gotten LinkedIn login to work) On Thu, Aug 9, 2012 at 11:25 PM, Massimo Di Pierro massimo@gmail.com wrote: Can you help us fix the CSS? On Thursday, 9 August 2012 00:29:58 UTC-5, Andrew wrote: Just a note on IE7 navbar behaviour: The Menu has taken a turn for the worse: Initially the Welcome App Sub Menus dissapeared in : welcome css pathc, issue 896, thanks Angelo They then returned in fixed issue qith clicking on toplevel menus except all of the submenus are displayed when the menu first appears and they are all on top of each other. The login options are still blue, and the space between the navbar and Welcome isn't there. See screen shot. On Thursday, August 9, 2012 9:17:17 AM UTC+12, Massimo Di Pierro wrote: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- -- -- Profile: http://it.linkedin.com/in/**compagnucciangelohttp://it.linkedin.com/in/compagnucciangelo -- -- Profile: http://it.linkedin.com/in/compagnucciangelo -- Profile: http://it.linkedin.com/in/compagnucciangelo --
Re: [web2py] Re: web2py 2.0 almost done
Can you explain the consequences of this line in your patch? if (jQuery(document).width() = 980) On Friday, 10 August 2012 10:11:39 UTC-5, AngeloC wrote: Hi Massimo, I fixed compatibility with IE and reverted to a non mobile first approach. I reverted because bootstrap is not mobile first (so we add too little) and for the sake of compatibility with IE. Patch is attached to issue http://code.google.com/p/web2py/issues/detail?id=896 which I cannot reopen. Hope this helps! Angelo 2012/8/10 Angelo Compagnucci angelo.co...@gmail.com javascript: Hi Massimo, I'm writing it right now to fix ie issues! Please be patient until fixed! 2012/8/9 Massimo Di Pierro massimo@gmail.com javascript: This may be ok but where do I get bootswatch_ie.css from? On Thursday, 9 August 2012 11:43:28 UTC-5, AngeloC wrote: Hi Massimo, I think I cannot complete the bootstrap/web2py css merging in time for 2.0, it's really a lot of work and I'm a bit busy these days. Btw, i'm fixing the bug I introduced with issue 896 and I want to share a thought with you. Actually, there is no way to maintain a mobile first approach and make it working on IE other than add something like this to the scaffolding: !-- Makes bootswatch working on IE 7/8 -- !--[if (lt IE 9)] link rel=stylesheet href=/responsivekit/static/** css/bootswatch_ie.css ![endif]-- This will make speedier the whole css on not IE browsers because we remove IE specific rules (smaller css), but has the downside to require an extra http get on IE. What do you think? 2012/8/9 Alec Taylor alec.t...@gmail.com It would be good to have OAuth working for web2py 2 Facebook and LinkedIn still have some issues LinkedIn: https://groups.google.com/**forum/#!topic/web2py/** SbnQEnXEcOghttps://groups.google.com/forum/#!topic/web2py/SbnQEnXEcOg Facebook: (will add bug report once I've gotten LinkedIn login to work) On Thu, Aug 9, 2012 at 11:25 PM, Massimo Di Pierro massimo@gmail.com wrote: Can you help us fix the CSS? On Thursday, 9 August 2012 00:29:58 UTC-5, Andrew wrote: Just a note on IE7 navbar behaviour: The Menu has taken a turn for the worse: Initially the Welcome App Sub Menus dissapeared in : welcome css pathc, issue 896, thanks Angelo They then returned in fixed issue qith clicking on toplevel menus except all of the submenus are displayed when the menu first appears and they are all on top of each other. The login options are still blue, and the space between the navbar and Welcome isn't there. See screen shot. On Thursday, August 9, 2012 9:17:17 AM UTC+12, Massimo Di Pierro wrote: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- -- -- Profile: http://it.linkedin.com/in/**compagnucciangelohttp://it.linkedin.com/in/compagnucciangelo -- -- Profile: http://it.linkedin.com/in/compagnucciangelo -- Profile: http://it.linkedin.com/in/compagnucciangelo --
Re: [web2py] Re: web2py 2.0 almost done
I see. I understand it now. Thanks Anthony On Wednesday, August 8, 2012 9:37:51 PM UTC+8, Anthony wrote: On Wednesday, August 8, 2012 5:30:10 AM UTC-4, lyn2py wrote: Does this mean that if I uncomment the jquery-ui in layout.html, the autocomplete will be working even on IE? No, jQuery UI autocomplete is not implemented with web2py. Anthony --
Re: [web2py] Re: web2py 2.0 almost done
It would be good to have OAuth working for web2py 2 Facebook and LinkedIn still have some issues LinkedIn: https://groups.google.com/forum/#!topic/web2py/SbnQEnXEcOg Facebook: (will add bug report once I've gotten LinkedIn login to work) On Thu, Aug 9, 2012 at 11:25 PM, Massimo Di Pierro massimo.dipie...@gmail.com wrote: Can you help us fix the CSS? On Thursday, 9 August 2012 00:29:58 UTC-5, Andrew wrote: Just a note on IE7 navbar behaviour: The Menu has taken a turn for the worse: Initially the Welcome App Sub Menus dissapeared in : welcome css pathc, issue 896, thanks Angelo They then returned in fixed issue qith clicking on toplevel menus except all of the submenus are displayed when the menu first appears and they are all on top of each other. The login options are still blue, and the space between the navbar and Welcome isn't there. See screen shot. On Thursday, August 9, 2012 9:17:17 AM UTC+12, Massimo Di Pierro wrote: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- --
Re: [web2py] Re: web2py 2.0 almost done
Hi Massimo, I think I cannot complete the bootstrap/web2py css merging in time for 2.0, it's really a lot of work and I'm a bit busy these days. Btw, i'm fixing the bug I introduced with issue 896 and I want to share a thought with you. Actually, there is no way to maintain a mobile first approach and make it working on IE other than add something like this to the scaffolding: !-- Makes bootswatch working on IE 7/8 -- !--[if (lt IE 9)] link rel=stylesheet href=/responsivekit/static/css/bootswatch_ie.css ![endif]-- This will make speedier the whole css on not IE browsers because we remove IE specific rules (smaller css), but has the downside to require an extra http get on IE. What do you think? 2012/8/9 Alec Taylor alec.tayl...@gmail.com It would be good to have OAuth working for web2py 2 Facebook and LinkedIn still have some issues LinkedIn: https://groups.google.com/forum/#!topic/web2py/SbnQEnXEcOg Facebook: (will add bug report once I've gotten LinkedIn login to work) On Thu, Aug 9, 2012 at 11:25 PM, Massimo Di Pierro massimo.dipie...@gmail.com wrote: Can you help us fix the CSS? On Thursday, 9 August 2012 00:29:58 UTC-5, Andrew wrote: Just a note on IE7 navbar behaviour: The Menu has taken a turn for the worse: Initially the Welcome App Sub Menus dissapeared in : welcome css pathc, issue 896, thanks Angelo They then returned in fixed issue qith clicking on toplevel menus except all of the submenus are displayed when the menu first appears and they are all on top of each other. The login options are still blue, and the space between the navbar and Welcome isn't there. See screen shot. On Thursday, August 9, 2012 9:17:17 AM UTC+12, Massimo Di Pierro wrote: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- -- -- Profile: http://it.linkedin.com/in/compagnucciangelo --
Re: [web2py] Re: web2py 2.0 almost done
This may be ok but where do I get bootswatch_ie.css from? On Thursday, 9 August 2012 11:43:28 UTC-5, AngeloC wrote: Hi Massimo, I think I cannot complete the bootstrap/web2py css merging in time for 2.0, it's really a lot of work and I'm a bit busy these days. Btw, i'm fixing the bug I introduced with issue 896 and I want to share a thought with you. Actually, there is no way to maintain a mobile first approach and make it working on IE other than add something like this to the scaffolding: !-- Makes bootswatch working on IE 7/8 -- !--[if (lt IE 9)] link rel=stylesheet href=/responsivekit/static/css/bootswatch_ie.css ![endif]-- This will make speedier the whole css on not IE browsers because we remove IE specific rules (smaller css), but has the downside to require an extra http get on IE. What do you think? 2012/8/9 Alec Taylor alec.t...@gmail.com javascript: It would be good to have OAuth working for web2py 2 Facebook and LinkedIn still have some issues LinkedIn: https://groups.google.com/forum/#!topic/web2py/SbnQEnXEcOg Facebook: (will add bug report once I've gotten LinkedIn login to work) On Thu, Aug 9, 2012 at 11:25 PM, Massimo Di Pierro massimo@gmail.com javascript: wrote: Can you help us fix the CSS? On Thursday, 9 August 2012 00:29:58 UTC-5, Andrew wrote: Just a note on IE7 navbar behaviour: The Menu has taken a turn for the worse: Initially the Welcome App Sub Menus dissapeared in : welcome css pathc, issue 896, thanks Angelo They then returned in fixed issue qith clicking on toplevel menus except all of the submenus are displayed when the menu first appears and they are all on top of each other. The login options are still blue, and the space between the navbar and Welcome isn't there. See screen shot. On Thursday, August 9, 2012 9:17:17 AM UTC+12, Massimo Di Pierro wrote: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- -- -- Profile: http://it.linkedin.com/in/compagnucciangelo --
Re: [web2py] Re: web2py 2.0 almost done
Hi Massimo, I'm writing it right now to fix ie issues! Please be patient until fixed! 2012/8/9 Massimo Di Pierro massimo.dipie...@gmail.com This may be ok but where do I get bootswatch_ie.css from? On Thursday, 9 August 2012 11:43:28 UTC-5, AngeloC wrote: Hi Massimo, I think I cannot complete the bootstrap/web2py css merging in time for 2.0, it's really a lot of work and I'm a bit busy these days. Btw, i'm fixing the bug I introduced with issue 896 and I want to share a thought with you. Actually, there is no way to maintain a mobile first approach and make it working on IE other than add something like this to the scaffolding: !-- Makes bootswatch working on IE 7/8 -- !--[if (lt IE 9)] link rel=stylesheet href=/responsivekit/static/** css/bootswatch_ie.css ![endif]-- This will make speedier the whole css on not IE browsers because we remove IE specific rules (smaller css), but has the downside to require an extra http get on IE. What do you think? 2012/8/9 Alec Taylor alec.t...@gmail.com It would be good to have OAuth working for web2py 2 Facebook and LinkedIn still have some issues LinkedIn: https://groups.google.com/**forum/#!topic/web2py/**SbnQEnXEcOghttps://groups.google.com/forum/#!topic/web2py/SbnQEnXEcOg Facebook: (will add bug report once I've gotten LinkedIn login to work) On Thu, Aug 9, 2012 at 11:25 PM, Massimo Di Pierro massimo@gmail.com wrote: Can you help us fix the CSS? On Thursday, 9 August 2012 00:29:58 UTC-5, Andrew wrote: Just a note on IE7 navbar behaviour: The Menu has taken a turn for the worse: Initially the Welcome App Sub Menus dissapeared in : welcome css pathc, issue 896, thanks Angelo They then returned in fixed issue qith clicking on toplevel menus except all of the submenus are displayed when the menu first appears and they are all on top of each other. The login options are still blue, and the space between the navbar and Welcome isn't there. See screen shot. On Thursday, August 9, 2012 9:17:17 AM UTC+12, Massimo Di Pierro wrote: more issues have been addressed. In order to fix an issue I had to introduce a slight change of behavior and I am not sure what is the best way to handle it. If you login using a third party service (for example janrain using facebook) and the service sends info about you, if web2py has corresponding fields in auth_user, it stores them. If you edit your profile, logout, change your facebook profile, login again using janrain, should web2py keep the current local profile or update it? The bug report suggested that web2oy should always give preference to the local profile. I changed web2py accordingly. In practice this change will probably not affect anybody because none of the services sends any information stored by auth_user. Yet, please check it. Massimo On Monday, 6 August 2012 23:33:48 UTC-5, Massimo Di Pierro wrote: Web2py 2.0 is almost done. Please try the nightly build. Let us know if it breaks anything. massimo -- -- -- Profile: http://it.linkedin.com/in/**compagnucciangelohttp://it.linkedin.com/in/compagnucciangelo -- -- Profile: http://it.linkedin.com/in/compagnucciangelo --
Re: [web2py] Re: web2py 2.0 almost done
Does this mean that if I uncomment the jquery-ui in layout.html, the autocomplete will be working even on IE? On Tuesday, August 7, 2012 9:40:30 PM UTC+8, Anthony wrote: Maybe we should consider adopting jQuery UI autocomplete for the client-side code. Anthony On Tuesday, August 7, 2012 8:56:57 AM UTC-4, Johann Spies wrote: On 7 August 2012 06:48, lyn2py lyn...@gmail.com javascript: wrote: Question on the autocomplete widget: Previous post / discussions indicate that this widget doesn't work for IE, may I know if it has been fixed? Or what seems to be preventing IE from rendering it properly? The autocomplete widget does look good in Firefox and Chrome on Linux. See the attached screenshot. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) --
Re: [web2py] Re: web2py 2.0 almost done
As I recall, the autocomplete doesn't work at all in IE (at least not 9,
not sure about 9). That's why I was thinking we should switch to a
third-party client-side widget.
Anthony
On Wednesday, August 8, 2012 8:53:00 AM UTC-4, Johann Spies wrote:
On Tuesday, 7 August 2012 17:23:34 UTC+2, Massimo Di Pierro wrote:
Has anybody worked out a good CSS for this? I do not think web2py ever
shipped with css for the autocomplete widget.
On Tuesday, 7 August 2012 07:56:57 UTC-5, Johann Spies wrote:
The autocomplete widget does look good in Firefox and Chrome on Linux.
See the attached screenshot.
I have now determined that my screenshot does not always apply. A few
strange things happened ago.
1. Today's trunk code made all autocomplete widgets (suggest_widget
included) stop working at all. It seems that no Ajax calls were working.
So I restored a backup of yesterday's code and that restored the ajax
functionality.
2. The following form illustrates something that does not make sense at
all.
Two problems arise out of it:
* The css does not work at all on the first field (see screenshots 1 and
3).
* There are two tables (akb_journal, akb_articles) which both have a
'title' field which is a normal string. The first field's autocomplete
(and this is the case with both the suggest_widget and the autocomplete
widget) does the lookup in the wrong table. In both cases values from the
akb_journal.title field gets returned. The firstand fourth screenshots
illustrate this.
The second field was added as a debugging mechanism: From the same table
(akb_articles) I use another field (authors) and in this case both the css
and the lookup values are fine as the second screenshot shows.
The third does the lookup in the correct table, but the css is not
functioning in this when I use the Autocomplete widget. See third
screenshot.
form=SQLFORM.factory(Field('artikel', label = T('Article'),
widget = SQLFORM.widgets.autocomplete(
request,
db.
akb_articles.title,
id_field = db.akb_articles.uuid,
orderby = db.akb_articles.title,
limitby = (0, 20), min_length = 2)),
Field('x', label = T('authors'),
widget = SQLFORM.widgets.autocomplete(
request,
db.
akb_articles.authors,
id_field = db.akb_articles.uuid,
orderby = db.akb_articles.authors,
limitby = (0, 20), min_length = 2)),
Field('skrywer', label = T('author'),
widget= SQLFORM.widgets.autocomplete(
request,db.akb_authors.name,
id_field
= db.akb_authors.uuid,
orderby
= db.akb_authors.name,
limitby
= (0, 20), min_length = 2)))
I would appreciate it if someone can clear up my confusion about what is
going on here.
Regards
Johann
--
Re: [web2py] Re: web2py 2.0 almost done
On Wednesday, August 8, 2012 5:30:10 AM UTC-4, lyn2py wrote: Does this mean that if I uncomment the jquery-ui in layout.html, the autocomplete will be working even on IE? No, jQuery UI autocomplete is not implemented with web2py. Anthony --
Re: [web2py] Re: web2py 2.0 almost done
On 8 August 2012 15:36, Anthony abasta...@gmail.com wrote: As I recall, the autocomplete doesn't work at all in IE (at least not 9, not sure about 9). That's why I was thinking we should switch to a third-party client-side widget. This was on LInux and with Firefox. I would appreciate any solution what works!. The suggest_widget works in most instances for me, but in this case it also have problems. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) --
Re: [web2py] Re: web2py 2.0 almost done
On 7 August 2012 06:48, lyn2py lyn...@gmail.com wrote: Question on the autocomplete widget: Previous post / discussions indicate that this widget doesn't work for IE, may I know if it has been fixed? Or what seems to be preventing IE from rendering it properly? The autocomplete widget does look good in Firefox and Chrome on Linux. See the attached screenshot. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) -- attachment: Selection_005.png
Re: [web2py] Re: web2py 2.0 almost done
Maybe we should consider adopting jQuery UI autocomplete for the client-side code. Anthony On Tuesday, August 7, 2012 8:56:57 AM UTC-4, Johann Spies wrote: On 7 August 2012 06:48, lyn2py lyn...@gmail.com wrote: Question on the autocomplete widget: Previous post / discussions indicate that this widget doesn't work for IE, may I know if it has been fixed? Or what seems to be preventing IE from rendering it properly? The autocomplete widget does look good in Firefox and Chrome on Linux. See the attached screenshot. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) --
Re: [web2py] Re: web2py 2.0 almost done
Nah, I'm pretty sure jQuery UI is a little too heavy for our needs. Maybe just the bootstrap autocomplete plugin? On Tue, Aug 7, 2012 at 11:40 PM, Anthony abasta...@gmail.com wrote: Maybe we should consider adopting jQuery UI autocomplete for the client-side code. Anthony On Tuesday, August 7, 2012 8:56:57 AM UTC-4, Johann Spies wrote: On 7 August 2012 06:48, lyn2py lyn...@gmail.com wrote: Question on the autocomplete widget: Previous post / discussions indicate that this widget doesn't work for IE, may I know if it has been fixed? Or what seems to be preventing IE from rendering it properly? The autocomplete widget does look good in Firefox and Chrome on Linux. See the attached screenshot. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) -- --
Re: [web2py] Re: web2py 2.0 almost done
Looks like the css is missing... On Tuesday, 7 August 2012 07:56:57 UTC-5, Johann Spies wrote: On 7 August 2012 06:48, lyn2py lyn...@gmail.com wrote: Question on the autocomplete widget: Previous post / discussions indicate that this widget doesn't work for IE, may I know if it has been fixed? Or what seems to be preventing IE from rendering it properly? The autocomplete widget does look good in Firefox and Chrome on Linux. See the attached screenshot. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) --
Re: [web2py] Re: web2py 2.0 almost done
Has anybody worked out a good CSS for this? I do not think web2py ever shipped with css for the autocomplete widget. On Tuesday, 7 August 2012 07:56:57 UTC-5, Johann Spies wrote: On 7 August 2012 06:48, lyn2py lyn...@gmail.com wrote: Question on the autocomplete widget: Previous post / discussions indicate that this widget doesn't work for IE, may I know if it has been fixed? Or what seems to be preventing IE from rendering it properly? The autocomplete widget does look good in Firefox and Chrome on Linux. See the attached screenshot. Regards Johann -- Because experiencing your loyal love is better than life itself, my lips will praise you. (Psalm 63:3) --
Re: [web2py] Re: web2py 2.0 almost done
Maybe just the bootstrap autocomplete plugin? I am using the Bootstrap autocomplete (typeahead) plugin, as far as I know it styles well in IE. Annet --
Re: [web2py] Re: web2py 2.0 almost done
Nah, I'm pretty sure jQuery UI is a little too heavy for our needs. The required autocomplete code is 20KB minified (before gzipping), so not that bad, and it has a lot of functionality. Maybe just the bootstrap autocomplete plugin? Something like this may be OK too, though not quite yet, as I believe the official Bootstrap Typeahead plugin does not support Ajax (supposed to be coming in 2.1). Anthony --
