--
-- mail from:GoogleGroups "web2py-developers" mailing list
make speech: web2py-d...@googlegroups.com
unsubscribe: web2py-develop...@googlegroups.com
details : http://groups.google.com/group/web2py-developers
the project: http://code.google.com/p/web2py/
official : http://www.web2py.com/
---
You received this message because you are subscribed to the Google Groups "web2py-developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to web2py-develop...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
I propose reverting the examples app (i.e., web2py.com) to the old design. I hope I'm not being offensive, but whatever the merits of stupid.css, I'm afraid the new site does not look professionally designed (hard to put a finger on, but various subtleties regarding spacing/vertical rhythm, layout, some of the hover effects, etc.). The old site could probably use a refresh as well, but I think the new design is a step backwards. If we don't have a designer among us who can pitch in, there are plenty of free and low cost templates (yes, mostly Bootstrap) that we could adopt.
I propose reverting the examples app (i.e., web2py.com) to the old design. I hope I'm not being offensive, but whatever the merits of stupid.css, I'm afraid the new site does not look professionally designed (hard to put a finger on, but various subtleties regarding spacing/vertical rhythm, layout, some of the hover effects, etc.). The old site could probably use a refresh as well, but I think the new design is a step backwards. If we don't have a designer among us who can pitch in, there are plenty of free and low cost templates (yes, mostly Bootstrap) that we could adopt.Ahahah I think the same I tried to improve it somewhat. We could use some professional design here. The thing about using stupid.css is that if we work on the examples app we end up being forced to develop stupid.css, I want to work on improving web2py not a CSS framework of which there are plenty of good ones out there for me to use.
from pkg_resources import parse_version, SetuptoolsVersion
versions = """
2.14.4
2.14.5
2.14.6
2.14.7rc1
2.14.7rc2
2.14.7
2.14.8
2.14.9rc1.dev1
2.14.9rc1.dev2
2.14.9rc1
2.14.9
2.14.10
2.15.1
"""
list_vers = [a for a in versions.split('\n') if a]
parsed_vers = [parse_version(a) for a in list_vers]
# verify that we're using correct scheme
assert all(isinstance(a, SetuptoolsVersion) for a in parsed_vers)
# verify that the order doesn't change
parsed_vers.sort()
# print together
for i, (orig, parsed) in enumerate(zip(list_vers, parsed_vers)):
print "step %s, orig: %s, parsed %s" % (i, orig, parsed)
OK on versioning.I am committed to supporting stupid.css. I know it has problems on IE (I do not have IE and cannot test on IE) but to my eyes with Chrome, the examples app looks much more professional than it did before and the code base is much smaller.
I do not want to revert for now but I will fix specific problems if you report them. In particular if you have screenshots.
On Wed, Apr 6, 2016 at 3:56 PM, Niphlod <nip...@gmail.com> wrote:we're making different topics in one, let's keep them ordered....+1 on stupid.css not being professional. not sure about the examples app needing to be professional if shipped with web2py but for sure on webpy.com doesn't look as a good "use web2py, you'll get this stylish pages" thing. Already said stupid.css is not the answer on web2py "evading" from css-framework lock-in multiple times. Also, I'm using my own scaffolding since forever and it's filled with niceties that use bootstrap under the hood: I'm not going to leave that wealth of developed plugins by js and css developers any time soon. Not that stupid.css is a bad exercise: I just choose to give web2py the credit of being a python framework as bootstrap a css framework, each one developed by people tremendously skilled in their own "department".
On Wednesday, April 6, 2016 at 2:16:52 PM UTC-7, Massimo Di Pierro wrote:
I do not want to revert for now but I will fix specific problems if you report them. In particular if you have screenshots.I think it looks good on FF 45.0.1 on an older Fedora. Has a clean, modern look, but is very spare; could perhaps use a few softer edges.I am not a designer, though, even if I sometimes read a type design blog or browse the Hammer Museum (in person).
before make a new release I run make src so I would like anything to be done to be done in there
Found my problem. Led me to hate SQLFORM and the FORM helper, but I don't see any easy fix for that mess.
--
I am committed to supporting stupid.css.
I know it has problems on IE (I do not have IE and cannot test on IE) but to my eyes with Chrome, the examples app looks much more professional than it did before and the code base is much smaller.
I do not want to revert for now but I will fix specific problems if you report them. In particular if you have screenshots.
--
I don't think that we should use some other template as most of the observations can be fixed to me...I have a background in Pre-press infography... I can give a try...
- [...]
- On the download page, too much space between the rows of buttons, not enough space between the heading and first row. Also, the new bright primary colors are not attractive (the more muted colors of the old site were not perfect but much better). It's also not clear why particular buttons are particular colors (maybe just make them all the same color -- and please not bright red).
- The "Read More" button on the download page should have rounded corners, like all the other buttons on the site.
Anthony--
- On the download page, too much space between the rows of buttons, not enough space between the heading and first row. Also, the new bright primary colors are not attractive (the more muted colors of the old site were not perfect but much better). It's also not clear why particular buttons are particular colors (maybe just make them all the same color -- and please not bright red).
Part of that is distinguishing the columns.
I am committed to supporting stupid.css.Does that mean you are committed to using it for web2py.com?
I know it has problems on IE (I do not have IE and cannot test on IE) but to my eyes with Chrome, the examples app looks much more professional than it did before and the code base is much smaller.Looking back at the old site, indeed some elements are improved, but some are worse. Overall, both designs could use a lot of improvement.
I do not want to revert for now but I will fix specific problems if you report them. In particular if you have screenshots.My sense is that this is difficult to get right for non-designers, and we would probably be better off adapting a nice professionally designed template. But if that's off the table, here's my list of issues with the current design:
- We need a logo in the header.
- Pure white on pure black or vice versa is too much contrast (on most websites where the background or text appears black, it is not really pure black). Change the header and footer backgrounds to a very dark gray (i.e., just short of pure black). Likewise, make a similar change to the black text color.
- I don't particularly like the new green color for links, but that's a personal preference. However, it definitely does not work on the dark background of the header (i.e., when hovering over the navigation links). Instead, consider changing those links to a gray color that turns white on hover.
- The underline animation on all the links is distracting and should be removed.
- The drop shadow on the buttons on hover is distracting. Instead consider darkening the button itself upon hover.
- The font sizes all look a little too big (headings and body text).
- There is too much line spacing within paragraphs and not enough spacing between paragraphs.
- The lists on the about, docs, support, and contributors pages have too much spacing between items, too little spacing between headings/sections, and should use bullets.
- The bright red buttons on the home page do not look good in contrast to the green headings/links (the old buttons looked a little better, as they were a more muted color).
- There should be some space between the technology award image and the download button on the home page. Better yet, maybe it's time to move that four year old award to a less prominent place.
- On the download page, too much space between the rows of buttons, not enough space between the heading and first row. Also, the new bright primary colors are not attractive (the more muted colors of the old site were not perfect but much better). It's also not clear why particular buttons are particular colors (maybe just make them all the same color -- and please not bright red).
- The "Read More" button on the download page should have rounded corners, like all the other buttons on the site.
Anthony
--
On Thu, Apr 7, 2016 at 11:23 AM, Anthony <abas...@gmail.com> wrote:
I am committed to supporting stupid.css.
Does that mean you are committed to using it for web2py.com?
open for discussion. If nobody steps up to re-design it and I have to do it, than I will do it the stupid way.
--
On Thu, Apr 7, 2016 at 11:23 AM, Anthony <abas...@gmail.com> wrote:I am committed to supporting stupid.css.Does that mean you are committed to using it for web2py.com?open for discussion. If nobody steps up to re-design it and I have to do it, than I will do it the stupid way.
- Pure white on pure black or vice versa is too much contrast (on most websites where the background or text appears black, it is not really pure black). Change the header and footer backgrounds to a very dark gray (i.e., just short of pure black). Likewise, make a similar change to the black text color.
I can. I like it better black but I will try.
- I don't particularly like the new green color for links, but that's a personal preference. However, it definitely does not work on the dark background of the header (i.e., when hovering over the navigation links). Instead, consider changing those links to a gray color that turns white on hover.
Give me a color scheme. No preference.
- The drop shadow on the buttons on hover is distracting. Instead consider darkening the button itself upon hover.
How about a wave effect like materialize?
Will fix. You are right about black. Took my palette for here http://clrs.cc so should have used #111111 whish "looks black".
--
Will fix. You are right about black. Took my palette for here http://clrs.cc so should have used #111111 whish "looks black".
Anthony--
I am not a designer either but as a physicist I do not understand why the shadows should not be symmetrical. The shadow comes from raising the button and the light comes from outside the screen, not form one side.
Yep the theory is that in the real world light comes from the top, where the sun is. In my opinion, nowadays, it also makes sense to consider light coming from outside the screen (perpendicular to the screen) as people use more tablets/phones and so the position of the screen is not necessarily to be standing vertically anymore.
I agree. Shall we remove it?
I think we shouldn't be maintaining our own pg8000 driver, however, I think it's a good idea for pyDAL to support it, and if pyDAL supports it then it has to work around its bugs and limitations which it doesn't right now. I quickly stopped using pg8000 when I started using postgresql consistently because of how many problems I bumped into that simply disappeared when I used psycopg2.
Basically, we need an adapter just for pg8000 and if, for now, no one is willing to maintain it, oh well.