I am not sure of the benefits of changing the brand image identity with much frequence. I think that part of the sucess of a framework like django (meaning that it is so popular) is that "graphically" it has a real fine work and It has preserved a very strong image identity (color, tipography). The brand design of web2py should be enhanced but keeping a brand style. There is a lot of experts in visual design who could help if there were some cooperation mechanism suitable for this project (is there?). Think of schools of design for example (Buenos Aires is overstocked with designers).
On Dec 1, 7:42 am, Martín Mulone <mulone.mar...@gmail.com> wrote: > Another logo contest is comming?... :) > > 2011/12/1 Massimo Di Pierro <massimo.dipie...@gmail.com> > > > > > I do not like names that have google search conflicts. Others like > > that because their search results go up. > > We had a different name and I was threatened to be sued. I spend $500 > > to trademark web2py. > > > Can anybody find a better name that has no search conflicts, is not > > trademarked, and is willing to donate $500? > > > It does take time and effort in building a brand and we are succeeded. > > We should not start again. We can give animal names to various stable > > version if you like. > > > Massimo > > > On Nov 30, 9:46 am, Omi Chiba <ochib...@gmail.com> wrote: > > > >I love the framework but hate the name Web2py > > > > Honestly, I agree. Django sounds cool but not web2py. I like gluon > > > better :) > > > > On Nov 30, 9:16 am, António Ramos <ramstei...@gmail.com> wrote: > > > > > I love the framework but hate the name Web2py > > > > Everyone uses names related to animals, objects,etc. At least it gives > > a > > > > better change for a nice logo. > > > > > Best regards > > > > > 2011/11/30 stefaan <stefaan.hi...@gmail.com> > > > > > > Web2py default layouts certainly have come a long way since the > > (IMHO, > > > > > quite awful :p ) fluorescent orange and black-green looks. > > > > > > I do seem to miss some "best-practices" documentation about how to > > > > > effectively apply themes to a web2py application. The downloadable > > > > > themes do not always properly display the newer widgets (like > > > > > sqlform.grid), leaving me (as a css nitwit) not much option but to > > use > > > > > the default layout. Unlike web2py functionality, the css classes do > > > > > not seem to be kept backward compatible (your layout won't be > > > > > overwritten if you upgrade to a newer web2py, but if you want the > > > > > newer features to render properly you may have to manually merge old > > > > > layouts with newer layouts) > > > > > > <handwaving> > > > > > I'm wondering if there aren't any WYSIWYM web layout solutions (what- > > > > > you-see-is-what-you-mean, a web equivalent to LaTeX macros for > > > > > printable documents), e.g. providing standardized css classes that > > all > > > > > scaffolding applications/widgets/user views ought to restrict > > > > > themselves to. Themes would also have to be implemented in terms of > > > > > those standardized css classes, hopefully leading to a smoother > > > > > theming experience. Approaches like the "ui" argument in sqlform.grid > > > > > do not seem ideal to me. > > > > > </handwaving> > > -- > http://martin.tecnodoc.com.ar
