Hi there, Flask is growing really fast! and I see some real nice code pattern like in this one: https://bitbucket.org/danjac/newsmeme/src Why do we make a better kitchensink program, name it maybe flask-kitchensink2? that have folder structure, modules, plugin apply, etc. I think that would really helpful. Thanks -- Jackie
I definitely agree we should have some Flask guidelines for folder structures, naming conventions, etc. I may get chewed out for saying this here, but one thing I really like about the Ruby community is that they have these. It makes browsing other people's repos and sharing code so much easier. On Wed, May 11, 2011 at 5:56 PM, Jackie Lee <jackie.space@gmail.com> wrote: > Hi there, > > Flask is growing really fast! and I see some real nice code pattern > like in this one: > https://bitbucket.org/danjac/newsmeme/src > > Why do we make a better kitchensink program, name it maybe > flask-kitchensink2? that have folder structure, modules, plugin apply, > etc. > > I think that would really helpful. > > Thanks > -- > Jackie >
On Wed, May 11, 2011 at 6:06 PM, Joe Esposito <espo58@gmail.com> wrote: > I definitely agree we should have some Flask guidelines for folder > structures, naming conventions, etc. I may get chewed out for saying this > here, but one thing I really like about the Ruby community is that they have > these. It makes browsing other people's repos and sharing code so much > easier. Let's not mix up Ruby from Rails or Python from Flask. Python has clear style guides (centered about PEP8, http://www.python.org/dev/peps/pep-0008/) and Flask has clear conventions and styles for extensions (in detail here, especially in the approval process, http://flask.pocoo.org/docs/extensiondev/). For your projects built with/using Flask, the guidelines are up to you. Patterns are provided in the documentation to help with clarity and to avoid common pitfalls. -Ron > On Wed, May 11, 2011 at 5:56 PM, Jackie Lee <jackie.space@gmail.com> wrote: >> >> Hi there, >> >> Flask is growing really fast! and I see some real nice code pattern >> like in this one: >> https://bitbucket.org/danjac/newsmeme/src >> >> Why do we make a better kitchensink program, name it maybe >> flask-kitchensink2? that have folder structure, modules, plugin apply, >> etc. >> >> I think that would really helpful. >> >> Thanks >> -- >> Jackie > >
It's that last part I'm referring to. "Those guidelines are up to you" is what makes it difficult to immediately know what someone else is trying to accomplish. Putting guidelines there would be helpful for that reason, which is what Rails does. But yes, they'd only be guidelines so you obviously don't have to follow them. It just makes it easier for the rest of the community, and sometimes even for devs since there'd be little ambiguity. The guidelines would then answer the questions of: how should I structure my project? On Wed, May 11, 2011 at 6:14 PM, Ron DuPlain <ron.duplain@gmail.com> wrote: > On Wed, May 11, 2011 at 6:06 PM, Joe Esposito <espo58@gmail.com> wrote: > > I definitely agree we should have some Flask guidelines for folder > > structures, naming conventions, etc. I may get chewed out for saying this > > here, but one thing I really like about the Ruby community is that they > have > > these. It makes browsing other people's repos and sharing code so much > > easier. > > Let's not mix up Ruby from Rails or Python from Flask. Python has > clear style guides (centered about PEP8, > http://www.python.org/dev/peps/pep-0008/) and Flask has clear > conventions and styles for extensions (in detail here, especially in > the approval process, http://flask.pocoo.org/docs/extensiondev/). > > For your projects built with/using Flask, the guidelines are up to > you. Patterns are provided in the documentation to help with clarity > and to avoid common pitfalls. > > -Ron > > > > On Wed, May 11, 2011 at 5:56 PM, Jackie Lee <jackie.space@gmail.com> > wrote: > >> > >> Hi there, > >> > >> Flask is growing really fast! and I see some real nice code pattern > >> like in this one: > >> https://bitbucket.org/danjac/newsmeme/src > >> > >> Why do we make a better kitchensink program, name it maybe > >> flask-kitchensink2? that have folder structure, modules, plugin apply, > >> etc. > >> > >> I think that would really helpful. > >> > >> Thanks > >> -- > >> Jackie > > > > >
On Wed, May 11, 2011 at 11:29 PM, Joe Esposito <espo58@gmail.com> wrote: > It's that last part I'm referring to. "Those guidelines are up to you" is > what makes it difficult to immediately know what someone else is trying to > accomplish. Putting guidelines there would be helpful for that reason, which > is what Rails does. I agree with this. And also for beginners like me, forming a better coding style sometimes does lots of good. a kitchensink program would give beginners lots of ideas of how to better accomplish something. > But yes, they'd only be guidelines so you obviously don't have to follow > them. It just makes it easier for the rest of the community, and sometimes > even for devs since there'd be little ambiguity. The guidelines would then > answer the questions of: how should I structure my project? We have docs for the structure, and we just need to put it in a kitchen sink program. Cheers, > > On Wed, May 11, 2011 at 6:14 PM, Ron DuPlain <ron.duplain@gmail.com> wrote: >> >> On Wed, May 11, 2011 at 6:06 PM, Joe Esposito <espo58@gmail.com> wrote: >> > I definitely agree we should have some Flask guidelines for folder >> > structures, naming conventions, etc. I may get chewed out for saying >> > this >> > here, but one thing I really like about the Ruby community is that they >> > have >> > these. It makes browsing other people's repos and sharing code so much >> > easier. >> >> Let's not mix up Ruby from Rails or Python from Flask. Python has >> clear style guides (centered about PEP8, >> http://www.python.org/dev/peps/pep-0008/) and Flask has clear >> conventions and styles for extensions (in detail here, especially in >> the approval process, http://flask.pocoo.org/docs/extensiondev/). >> >> For your projects built with/using Flask, the guidelines are up to >> you. Patterns are provided in the documentation to help with clarity >> and to avoid common pitfalls. >> >> -Ron >> >> >> > On Wed, May 11, 2011 at 5:56 PM, Jackie Lee <jackie.space@gmail.com> >> > wrote: >> >> >> >> Hi there, >> >> >> >> Flask is growing really fast! and I see some real nice code pattern >> >> like in this one: >> >> https://bitbucket.org/danjac/newsmeme/src >> >> >> >> Why do we make a better kitchensink program, name it maybe >> >> flask-kitchensink2? that have folder structure, modules, plugin apply, >> >> etc. >> >> >> >> I think that would really helpful. >> >> >> >> Thanks >> >> -- >> >> Jackie >> > >> > > > -- Jackie
Love that idea, I have been working with flask to make a website that is growing fast and would love to see all the options flask affords me. I would definitely be willing to help. Josh ************************************************************** Joshua Finnie Central Connecticut State University Masters of Science in Geography 24 Park Pl Apt B8H Hartford, CT 06106 (860) 716-5996 ************************************************************** On Wed, May 11, 2011 at 5:56 PM, Jackie Lee <jackie.space@gmail.com> wrote: > Hi there, > > Flask is growing really fast! and I see some real nice code pattern > like in this one: > https://bitbucket.org/danjac/newsmeme/src > > Why do we make a better kitchensink program, name it maybe > flask-kitchensink2? that have folder structure, modules, plugin apply, > etc. > > I think that would really helpful. > > Thanks > -- > Jackie >