Just a little something for those in need of a simple to use flask project structure. Just copy the version you want from src/ and start coding = ] https://github.com/italomaia/flask-empty -- "A arrogância é a arma dos fracos." =========================== Italo Moreira Campelo Maia Bacharel em Ciência da Computação - UECE Desenvolvedor WEB e Desktop (Java, Python, Lua) Coordenador do Pug-CE ----------------------------------------------------- http://www.italomaia.com/ http://twitter.com/italomaia/ http://eusouolobomau.blogspot.com/ ----------------------------------------------------- Turtle Linux 9.10 - http://tiny.cc/blogturtle910 Turtle Linux 10.10 - http://bit.ly/cEw4ET ===========================
This is a wheel we should maybe stop reinventing! Flask-tool and 6 other packages already do this :). Finding some sensible default layouts with js/asset structures, common server conf files, tests, manage.py, requirements and like. Would be a "let's start coding" win. Gregg Sent from my iPhone On Nov 2, 2011, at 10:40 AM, Italo Maia <italo.maia@gmail.com> wrote: > Just a little something for those in need of a simple to use flask project structure. Just copy the version you want from src/ and start coding = ] > https://github.com/italomaia/flask-empty > > -- > "A arrogância é a arma dos fracos." > > =========================== > Italo Moreira Campelo Maia > Bacharel em Ciência da Computação - UECE > Desenvolvedor WEB e Desktop (Java, Python, Lua) > Coordenador do Pug-CE > ----------------------------------------------------- > http://www.italomaia.com/ > http://twitter.com/italomaia/ > http://eusouolobomau.blogspot.com/ > ----------------------------------------------------- > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > Turtle Linux 10.10 - http://bit.ly/cEw4ET > ===========================
I have one also. Very different setup with no 'src' and no blueprints (yet): http://github.com/joeyespo/flask-scaffold Here's a proposal, since lots of newcomers wonder what's a good way to get going in terms of structuring small or big apps. We end up all having slightly-to-wildly different repo structures and because of this, several scaffolds have emerged. Armin, could you start a new project on GitHub for such a best-practices starter project? Have one targeting small projects and one for large. Then we can all contribute to this project instead of via email to discuss the best practices and point newcomers to it. Does anyone else think this would be valuable? I'd also hate for something like this to become yet-another-scaffold project. 2011/11/2 Italo Maia <italo.maia@gmail.com> > Just a little something for those in need of a simple to use flask project > structure. Just copy the version you want from src/ and start coding = ] > https://github.com/italomaia/flask-empty > > -- > "A arrogância é a arma dos fracos." > > =========================== > Italo Moreira Campelo Maia > Bacharel em Ciência da Computação - UECE > Desenvolvedor WEB e Desktop (Java, Python, Lua) > Coordenador do Pug-CE > ----------------------------------------------------- > http://www.italomaia.com/ > http://twitter.com/italomaia/ > http://eusouolobomau.blogspot.com/ > ----------------------------------------------------- > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > Turtle Linux 10.10 - http://bit.ly/cEw4ET > =========================== >
In my experience it's not just the flask part that is an issue, it's all the associated configurations and such . Having a great system that incorpoorates html5boileeplate sort of ideas was a goal of Flask-tool, which has different templates for simple, heavy, etc. Armin, it seems your resisted this as shackling or restrictive in the past. I glad Flask can run in simple-api mode, but for real apps some common layouts would help ease new project startup quite well. Make it easy to setup (reuirements.txt), manage, test, deploy (stock configs), and code! Sent from my iPhone On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> wrote: > I have one also. Very different setup with no 'src' and no blueprints (yet): http://github.com/joeyespo/flask-scaffold > > Here's a proposal, since lots of newcomers wonder what's a good way to get going in terms of structuring small or big apps. We end up all having slightly-to-wildly different repo structures and because of this, several scaffolds have emerged. > > Armin, could you start a new project on GitHub for such a best-practices starter project? Have one targeting small projects and one for large. Then we can all contribute to this project instead of via email to discuss the best practices and point newcomers to it. > > Does anyone else think this would be valuable? I'd also hate for something like this to become yet-another-scaffold project. > > 2011/11/2 Italo Maia <italo.maia@gmail.com> > Just a little something for those in need of a simple to use flask project structure. Just copy the version you want from src/ and start coding = ] > https://github.com/italomaia/flask-empty > > -- > "A arrogância é a arma dos fracos." > > =========================== > Italo Moreira Campelo Maia > Bacharel em Ciência da Computação - UECE > Desenvolvedor WEB e Desktop (Java, Python, Lua) > Coordenador do Pug-CE > ----------------------------------------------------- > http://www.italomaia.com/ > http://twitter.com/italomaia/ > http://eusouolobomau.blogspot.com/ > ----------------------------------------------------- > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > Turtle Linux 10.10 - http://bit.ly/cEw4ET > =========================== >
The problem isn't that there's little info on how to structure apps, it's that there's too many of them. All different. It's overwhelming almost. Now if there's an official repo with community collaboration, you can feel much more confident that you should start out that way. The samples in the docs are nice, but having a repo with it all stitched together, and with many eyes and comments on it, that just seems a much more reliable beginning of a project than rouge skeleton projects or 3rd party commandline scaffold tools. I'm not suggesting that Armin write the repo entirely. Just start it. That alone makes it feel authentic. He can simply keep it slim by only allowing structural additions (as opposed to one with default extensions, example websites with config, etc) through community discussion. Even better, named branches can indicate the sensible variations such as "large applications." @Gregg: installation and config has been tough in my experience too. That's a whole different issue though. I think a good base project like this will help though. You can start writing about it for common cases. Something like: "for a W-like website, begin with the X branch from the skeleton repo, install Y extensions, and use configuration Z." On Wed, Nov 2, 2011 at 2:10 PM, <gregg.lind@gmail.com> wrote: > In my experience it's not just the flask part that is an issue, it's all > the associated configurations and such . Having a great system that > incorpoorates html5boileeplate sort of ideas was a goal of Flask-tool, > which has different templates for simple, heavy, etc. > > Armin, it seems your resisted this as shackling or restrictive in the > past. I glad Flask can run in simple-api mode, but for real apps some > common layouts would help ease new project startup quite well. > > Make it easy to setup (reuirements.txt), manage, test, deploy (stock > configs), and code! > > Sent from my iPhone > > On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> wrote: > > I have one also. Very different setup with no 'src' and no blueprints > (yet): http://github.com/joeyespo/flask-scaffold > > Here's a proposal, since lots of newcomers wonder what's a good way to > get going in terms of structuring small or big apps. We end up all having > slightly-to-wildly different repo structures and because of this, several > scaffolds have emerged. > > Armin, could you start a new project on GitHub for such a best-practices > starter project? Have one targeting small projects and one for large. Then > we can all contribute to this project instead of via email to discuss the > best practices and point newcomers to it. > > Does anyone else think this would be valuable? I'd also hate for something > like this to become yet-another-scaffold project. > > 2011/11/2 Italo Maia <italo.maia@gmail.com> > >> Just a little something for those in need of a simple to use flask >> project structure. Just copy the version you want from src/ and start >> coding = ] >> https://github.com/italomaia/flask-empty >> >> -- >> "A arrogância é a arma dos fracos." >> >> =========================== >> Italo Moreira Campelo Maia >> Bacharel em Ciência da Computação - UECE >> Desenvolvedor WEB e Desktop (Java, Python, Lua) >> Coordenador do Pug-CE >> ----------------------------------------------------- >> http://www.italomaia.com/ >> http://twitter.com/italomaia/ >> http://eusouolobomau.blogspot.com/ >> ----------------------------------------------------- >> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >> Turtle Linux 10.10 - http://bit.ly/cEw4ET >> =========================== >> > >
I also like the simplicity and clean of Flask at first glance. So I fall in love with it. However, when I start to use it in actual website development, I find it really hard to figure out which is the best structure it should be. I try the one Italo once leaked in the mailinglist, But it is not in python package pattern. Then I start to check the Flask-website itself and also the related Flask documentation. Until now, I still not satisfy my organization (Someone interested may check it at http://pypi.python.org/pypi/ngpy/0.1), since it seems a little messy of all .py file in the same folder as __init__.py. A common best-practice pattern should be very helpful and valuable. Eshin 2011/11/3 Joe Esposito <espo58@gmail.com> > The problem isn't that there's little info on how to structure apps, it's > that there's too many of them. All different. It's overwhelming almost. Now > if there's an official repo with community collaboration, you can feel much > more confident that you should start out that way. The samples in the docs > are nice, but having a repo with it all stitched together, and with many > eyes and comments on it, that just seems a much more reliable beginning of > a project than rouge skeleton projects or 3rd party commandline scaffold > tools. > > I'm not suggesting that Armin write the repo entirely. Just start it. That > alone makes it feel authentic. He can simply keep it slim by only allowing > structural additions (as opposed to one with default extensions, example > websites with config, etc) through community discussion. Even better, named > branches can indicate the sensible variations such as "large applications." > > @Gregg: installation and config has been tough in my experience too. > That's a whole different issue though. I think a good base project like > this will help though. You can start writing about it for common cases. > Something like: "for a W-like website, begin with the X branch from the > skeleton repo, install Y extensions, and use configuration Z." > > On Wed, Nov 2, 2011 at 2:10 PM, <gregg.lind@gmail.com> wrote: > >> In my experience it's not just the flask part that is an issue, it's all >> the associated configurations and such . Having a great system that >> incorpoorates html5boileeplate sort of ideas was a goal of Flask-tool, >> which has different templates for simple, heavy, etc. >> >> Armin, it seems your resisted this as shackling or restrictive in the >> past. I glad Flask can run in simple-api mode, but for real apps some >> common layouts would help ease new project startup quite well. >> >> Make it easy to setup (reuirements.txt), manage, test, deploy (stock >> configs), and code! >> >> Sent from my iPhone >> >> On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> wrote: >> >> I have one also. Very different setup with no 'src' and no blueprints >> (yet): http://github.com/joeyespo/flask-scaffold >> >> Here's a proposal, since lots of newcomers wonder what's a good way to >> get going in terms of structuring small or big apps. We end up all having >> slightly-to-wildly different repo structures and because of this, several >> scaffolds have emerged. >> >> Armin, could you start a new project on GitHub for such a best-practices >> starter project? Have one targeting small projects and one for large. Then >> we can all contribute to this project instead of via email to discuss the >> best practices and point newcomers to it. >> >> Does anyone else think this would be valuable? I'd also hate for >> something like this to become yet-another-scaffold project. >> >> 2011/11/2 Italo Maia <italo.maia@gmail.com> >> >>> Just a little something for those in need of a simple to use flask >>> project structure. Just copy the version you want from src/ and start >>> coding = ] >>> https://github.com/italomaia/flask-empty >>> >>> -- >>> "A arrogância é a arma dos fracos." >>> >>> =========================== >>> Italo Moreira Campelo Maia >>> Bacharel em Ciência da Computação - UECE >>> Desenvolvedor WEB e Desktop (Java, Python, Lua) >>> Coordenador do Pug-CE >>> ----------------------------------------------------- >>> http://www.italomaia.com/ >>> http://twitter.com/italomaia/ >>> http://eusouolobomau.blogspot.com/ >>> ----------------------------------------------------- >>> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >>> Turtle Linux 10.10 - http://bit.ly/cEw4ET >>> =========================== >>> >> >> > -- *Yi-Xin Liu, PHD* *Department of Macromolecular Science* *Fudan University* *Room 415, Yuejing Building * *Handan Rd. 220, **Shanghai, China* *Tel +86-021-65642863* *Mobile +86-13916819745* http://www.mendeley.com/profiles/yi-xin-liu/
Ours is at: https://github.com/imlucas/flask-tool , and incorporates html5boilerplate stuff. On Wed, Nov 2, 2011 at 6:30 PM, 刘一新 <liuyxpp@gmail.com> wrote: > I also like the simplicity and clean of Flask at first glance. So I fall in > love with it. However, when I start to use it in actual website development, > I find it really hard to figure out which is the best structure it should > be. I try the one Italo once leaked in the mailinglist, But it is not in > python package pattern. Then I start to check the Flask-website itself and > also the related Flask documentation. Until now, I still not satisfy my > organization (Someone interested may check it > at http://pypi.python.org/pypi/ngpy/0.1), since it seems a little messy of > all .py file in the same folder as __init__.py. A common best-practice > pattern should be very helpful and valuable. > Eshin > > 2011/11/3 Joe Esposito <espo58@gmail.com> >> >> The problem isn't that there's little info on how to structure apps, it's >> that there's too many of them. All different. It's overwhelming almost. Now >> if there's an official repo with community collaboration, you can feel much >> more confident that you should start out that way. The samples in the docs >> are nice, but having a repo with it all stitched together, and with many >> eyes and comments on it, that just seems a much more reliable beginning of a >> project than rouge skeleton projects or 3rd party commandline scaffold >> tools. >> I'm not suggesting that Armin write the repo entirely. Just start it. That >> alone makes it feel authentic. He can simply keep it slim by only allowing >> structural additions (as opposed to one with default extensions, example >> websites with config, etc) through community discussion. Even better, named >> branches can indicate the sensible variations such as "large applications." >> @Gregg: installation and config has been tough in my experience too. >> That's a whole different issue though. I think a good base project like this >> will help though. You can start writing about it for common cases. Something >> like: "for a W-like website, begin with the X branch from the skeleton repo, >> install Y extensions, and use configuration Z." >> On Wed, Nov 2, 2011 at 2:10 PM, <gregg.lind@gmail.com> wrote: >>> >>> In my experience it's not just the flask part that is an issue, it's all >>> the associated configurations and such . Having a great system that >>> incorpoorates html5boileeplate sort of ideas was a goal of Flask-tool, which >>> has different templates for simple, heavy, etc. >>> Armin, it seems your resisted this as shackling or restrictive in the >>> past. I glad Flask can run in simple-api mode, but for real apps some >>> common layouts would help ease new project startup quite well. >>> Make it easy to setup (reuirements.txt), manage, test, deploy (stock >>> configs), and code! >>> >>> Sent from my iPhone >>> On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> wrote: >>> >>> I have one also. Very different setup with no 'src' and no blueprints >>> (yet): http://github.com/joeyespo/flask-scaffold >>> Here's a proposal, since lots of newcomers wonder what's a good way to >>> get going in terms of structuring small or big apps. We end up all having >>> slightly-to-wildly different repo structures and because of this, several >>> scaffolds have emerged. >>> Armin, could you start a new project on GitHub for such a best-practices >>> starter project? Have one targeting small projects and one for large. Then >>> we can all contribute to this project instead of via email to discuss the >>> best practices and point newcomers to it. >>> Does anyone else think this would be valuable? I'd also hate for >>> something like this to become yet-another-scaffold project. >>> >>> 2011/11/2 Italo Maia <italo.maia@gmail.com> >>>> >>>> Just a little something for those in need of a simple to use flask >>>> project structure. Just copy the version you want from src/ and start coding >>>> = ] >>>> https://github.com/italomaia/flask-empty >>>> >>>> -- >>>> "A arrogância é a arma dos fracos." >>>> >>>> =========================== >>>> Italo Moreira Campelo Maia >>>> Bacharel em Ciência da Computação - UECE >>>> Desenvolvedor WEB e Desktop (Java, Python, Lua) >>>> Coordenador do Pug-CE >>>> ----------------------------------------------------- >>>> http://www.italomaia.com/ >>>> http://twitter.com/italomaia/ >>>> http://eusouolobomau.blogspot.com/ >>>> ----------------------------------------------------- >>>> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >>>> Turtle Linux 10.10 - http://bit.ly/cEw4ET >>>> =========================== >>> >> > > > > -- > Yi-Xin Liu, PHD > Department of Macromolecular Science > Fudan University > Room 415, Yuejing Building > Handan Rd. 220, Shanghai, China > Tel +86-021-65642863 > Mobile +86-13916819745 > http://www.mendeley.com/profiles/yi-xin-liu/ >
I think one reason why there hasn't been an official structure or "best practice" I think is because flask hasn't been around enough to really have a "best practice." I think its really up to experience and collaboration of people to come up with best practices. Like convention over configuration or where templates should be best placed, etc. Maybe someone should start pulling other people's ideas and compile it into one project? ~Jonathan C. On Wed, Nov 2, 2011 at 6:35 PM, Gregg Lind <gregg.lind@gmail.com> wrote: > Ours is at: https://github.com/imlucas/flask-tool , and incorporates > html5boilerplate stuff. > > On Wed, Nov 2, 2011 at 6:30 PM, 刘一新 <liuyxpp@gmail.com> wrote: > > I also like the simplicity and clean of Flask at first glance. So I fall > in > > love with it. However, when I start to use it in actual website > development, > > I find it really hard to figure out which is the best structure it should > > be. I try the one Italo once leaked in the mailinglist, But it is not in > > python package pattern. Then I start to check the Flask-website itself > and > > also the related Flask documentation. Until now, I still not satisfy my > > organization (Someone interested may check it > > at http://pypi.python.org/pypi/ngpy/0.1), since it seems a little messy > of > > all .py file in the same folder as __init__.py. A common best-practice > > pattern should be very helpful and valuable. > > Eshin > > > > 2011/11/3 Joe Esposito <espo58@gmail.com> > >> > >> The problem isn't that there's little info on how to structure apps, > it's > >> that there's too many of them. All different. It's overwhelming almost. > Now > >> if there's an official repo with community collaboration, you can feel > much > >> more confident that you should start out that way. The samples in the > docs > >> are nice, but having a repo with it all stitched together, and with many > >> eyes and comments on it, that just seems a much more reliable beginning > of a > >> project than rouge skeleton projects or 3rd party commandline scaffold > >> tools. > >> I'm not suggesting that Armin write the repo entirely. Just start it. > That > >> alone makes it feel authentic. He can simply keep it slim by only > allowing > >> structural additions (as opposed to one with default extensions, example > >> websites with config, etc) through community discussion. Even better, > named > >> branches can indicate the sensible variations such as "large > applications." > >> @Gregg: installation and config has been tough in my experience too. > >> That's a whole different issue though. I think a good base project like > this > >> will help though. You can start writing about it for common cases. > Something > >> like: "for a W-like website, begin with the X branch from the skeleton > repo, > >> install Y extensions, and use configuration Z." > >> On Wed, Nov 2, 2011 at 2:10 PM, <gregg.lind@gmail.com> wrote: > >>> > >>> In my experience it's not just the flask part that is an issue, it's > all > >>> the associated configurations and such . Having a great system that > >>> incorpoorates html5boileeplate sort of ideas was a goal of Flask-tool, > which > >>> has different templates for simple, heavy, etc. > >>> Armin, it seems your resisted this as shackling or restrictive in the > >>> past. I glad Flask can run in simple-api mode, but for real apps some > >>> common layouts would help ease new project startup quite well. > >>> Make it easy to setup (reuirements.txt), manage, test, deploy (stock > >>> configs), and code! > >>> > >>> Sent from my iPhone > >>> On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> wrote: > >>> > >>> I have one also. Very different setup with no 'src' and no blueprints > >>> (yet): http://github.com/joeyespo/flask-scaffold > >>> Here's a proposal, since lots of newcomers wonder what's a good way to > >>> get going in terms of structuring small or big apps. We end up all > having > >>> slightly-to-wildly different repo structures and because of this, > several > >>> scaffolds have emerged. > >>> Armin, could you start a new project on GitHub for such a > best-practices > >>> starter project? Have one targeting small projects and one for large. > Then > >>> we can all contribute to this project instead of via email to discuss > the > >>> best practices and point newcomers to it. > >>> Does anyone else think this would be valuable? I'd also hate for > >>> something like this to become yet-another-scaffold project. > >>> > >>> 2011/11/2 Italo Maia <italo.maia@gmail.com> > >>>> > >>>> Just a little something for those in need of a simple to use flask > >>>> project structure. Just copy the version you want from src/ and start > coding > >>>> = ] > >>>> https://github.com/italomaia/flask-empty > >>>> > >>>> -- > >>>> "A arrogância é a arma dos fracos." > >>>> > >>>> =========================== > >>>> Italo Moreira Campelo Maia > >>>> Bacharel em Ciência da Computação - UECE > >>>> Desenvolvedor WEB e Desktop (Java, Python, Lua) > >>>> Coordenador do Pug-CE > >>>> ----------------------------------------------------- > >>>> http://www.italomaia.com/ > >>>> http://twitter.com/italomaia/ > >>>> http://eusouolobomau.blogspot.com/ > >>>> ----------------------------------------------------- > >>>> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > >>>> Turtle Linux 10.10 - http://bit.ly/cEw4ET > >>>> =========================== > >>> > >> > > > > > > > > -- > > Yi-Xin Liu, PHD > > Department of Macromolecular Science > > Fudan University > > Room 415, Yuejing Building > > Handan Rd. 220, Shanghai, China > > Tel +86-021-65642863 > > Mobile +86-13916819745 > > http://www.mendeley.com/profiles/yi-xin-liu/ > > >
I made a list of the contenders a few months ago and posted it here. Maybe we can put a wish list or pain pint list tighter and find a consensus. I will put some paper on it tomorrow! Sent from my iPhone On Nov 2, 2011, at 7:57 PM, Jonathan Chen <tamasiaina@gmail.com> wrote: > I think one reason why there hasn't been an official structure or "best practice" I think is because flask hasn't been around enough to really have a "best practice." I think its really up to experience and collaboration of people to come up with best practices. Like convention over configuration or where templates should be best placed, etc. Maybe someone should start pulling other people's ideas and compile it into one project? > > ~Jonathan C. > > > On Wed, Nov 2, 2011 at 6:35 PM, Gregg Lind <gregg.lind@gmail.com> wrote: > Ours is at: https://github.com/imlucas/flask-tool , and incorporates > html5boilerplate stuff. > > On Wed, Nov 2, 2011 at 6:30 PM, 刘一新 <liuyxpp@gmail.com> wrote: > > I also like the simplicity and clean of Flask at first glance. So I fall in > > love with it. However, when I start to use it in actual website development, > > I find it really hard to figure out which is the best structure it should > > be. I try the one Italo once leaked in the mailinglist, But it is not in > > python package pattern. Then I start to check the Flask-website itself and > > also the related Flask documentation. Until now, I still not satisfy my > > organization (Someone interested may check it > > at http://pypi.python.org/pypi/ngpy/0.1), since it seems a little messy of > > all .py file in the same folder as __init__.py. A common best-practice > > pattern should be very helpful and valuable. > > Eshin > > > > 2011/11/3 Joe Esposito <espo58@gmail.com> > >> > >> The problem isn't that there's little info on how to structure apps, it's > >> that there's too many of them. All different. It's overwhelming almost. Now > >> if there's an official repo with community collaboration, you can feel much > >> more confident that you should start out that way. The samples in the docs > >> are nice, but having a repo with it all stitched together, and with many > >> eyes and comments on it, that just seems a much more reliable beginning of a > >> project than rouge skeleton projects or 3rd party commandline scaffold > >> tools. > >> I'm not suggesting that Armin write the repo entirely. Just start it. That > >> alone makes it feel authentic. He can simply keep it slim by only allowing > >> structural additions (as opposed to one with default extensions, example > >> websites with config, etc) through community discussion. Even better, named > >> branches can indicate the sensible variations such as "large applications." > >> @Gregg: installation and config has been tough in my experience too. > >> That's a whole different issue though. I think a good base project like this > >> will help though. You can start writing about it for common cases. Something > >> like: "for a W-like website, begin with the X branch from the skeleton repo, > >> install Y extensions, and use configuration Z." > >> On Wed, Nov 2, 2011 at 2:10 PM, <gregg.lind@gmail.com> wrote: > >>> > >>> In my experience it's not just the flask part that is an issue, it's all > >>> the associated configurations and such . Having a great system that > >>> incorpoorates html5boileeplate sort of ideas was a goal of Flask-tool, which > >>> has different templates for simple, heavy, etc. > >>> Armin, it seems your resisted this as shackling or restrictive in the > >>> past. I glad Flask can run in simple-api mode, but for real apps some > >>> common layouts would help ease new project startup quite well. > >>> Make it easy to setup (reuirements.txt), manage, test, deploy (stock > >>> configs), and code! > >>> > >>> Sent from my iPhone > >>> On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> wrote: > >>> > >>> I have one also. Very different setup with no 'src' and no blueprints > >>> (yet): http://github.com/joeyespo/flask-scaffold > >>> Here's a proposal, since lots of newcomers wonder what's a good way to > >>> get going in terms of structuring small or big apps. We end up all having > >>> slightly-to-wildly different repo structures and because of this, several > >>> scaffolds have emerged. > >>> Armin, could you start a new project on GitHub for such a best-practices > >>> starter project? Have one targeting small projects and one for large. Then > >>> we can all contribute to this project instead of via email to discuss the > >>> best practices and point newcomers to it. > >>> Does anyone else think this would be valuable? I'd also hate for > >>> something like this to become yet-another-scaffold project. > >>> > >>> 2011/11/2 Italo Maia <italo.maia@gmail.com> > >>>> > >>>> Just a little something for those in need of a simple to use flask > >>>> project structure. Just copy the version you want from src/ and start coding > >>>> = ] > >>>> https://github.com/italomaia/flask-empty > >>>> > >>>> -- > >>>> "A arrogância é a arma dos fracos." > >>>> > >>>> =========================== > >>>> Italo Moreira Campelo Maia > >>>> Bacharel em Ciência da Computação - UECE > >>>> Desenvolvedor WEB e Desktop (Java, Python, Lua) > >>>> Coordenador do Pug-CE > >>>> ----------------------------------------------------- > >>>> http://www.italomaia.com/ > >>>> http://twitter.com/italomaia/ > >>>> http://eusouolobomau.blogspot.com/ > >>>> ----------------------------------------------------- > >>>> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > >>>> Turtle Linux 10.10 - http://bit.ly/cEw4ET > >>>> =========================== > >>> > >> > > > > > > > > -- > > Yi-Xin Liu, PHD > > Department of Macromolecular Science > > Fudan University > > Room 415, Yuejing Building > > Handan Rd. 220, Shanghai, China > > Tel +86-021-65642863 > > Mobile +86-13916819745 > > http://www.mendeley.com/profiles/yi-xin-liu/ > > >
That'd be great. Perhaps get a list of existing scaffolds as a starting point. This is why I suggest Armin start the project: 1. It will be hosted by the creator of Flask. This can easily be recognized as something legit, instead of from any other GitHub user. 2. He can have the final say on community decisions/arguments that parallels the direction of Flask. If he still doesn't want to participate directly, he can add collaborators to the GitHub project with write access. It seems there's quite a few people excited about Flask standards, which is awesome, but can also lead to something best summarized by this <http://xkcd.com/927/>. @Jonathan: I completely agree. This is still a good time to begin though. Since Flask is still young and has a decent sized community, it'll evolve. However without something more central for application standards, the evolution will be quite fragmented. Thoughts? On Wed, Nov 2, 2011 at 11:04 PM, <gregg.lind@gmail.com> wrote: > I made a list of the contenders a few months ago and posted it here. > Maybe we can put a wish list or pain pint list tighter and find a > consensus. I will put some paper on it tomorrow! > > > Sent from my iPhone > > On Nov 2, 2011, at 7:57 PM, Jonathan Chen <tamasiaina@gmail.com> wrote: > > I think one reason why there hasn't been an official structure or "best > practice" I think is because flask hasn't been around enough to really have > a "best practice." I think its really up to experience and collaboration of > people to come up with best practices. Like convention over configuration > or where templates should be best placed, etc. Maybe someone should start > pulling other people's ideas and compile it into one project? > > ~Jonathan C. > > > On Wed, Nov 2, 2011 at 6:35 PM, Gregg Lind <gregg.lind@gmail.com> wrote: > >> Ours is at: https://github.com/imlucas/flask-tool , and incorporates >> html5boilerplate stuff. >> >> On Wed, Nov 2, 2011 at 6:30 PM, 刘一新 <liuyxpp@gmail.com> wrote: >> > I also like the simplicity and clean of Flask at first glance. So I >> fall in >> > love with it. However, when I start to use it in actual website >> development, >> > I find it really hard to figure out which is the best structure it >> should >> > be. I try the one Italo once leaked in the mailinglist, But it is not in >> > python package pattern. Then I start to check the Flask-website itself >> and >> > also the related Flask documentation. Until now, I still not satisfy my >> > organization (Someone interested may check it >> > at http://pypi.python.org/pypi/ngpy/0.1), since it seems a little >> messy of >> > all .py file in the same folder as __init__.py. A common best-practice >> > pattern should be very helpful and valuable. >> > Eshin >> > >> > 2011/11/3 Joe Esposito <espo58@gmail.com> >> >> >> >> The problem isn't that there's little info on how to structure apps, >> it's >> >> that there's too many of them. All different. It's overwhelming >> almost. Now >> >> if there's an official repo with community collaboration, you can feel >> much >> >> more confident that you should start out that way. The samples in the >> docs >> >> are nice, but having a repo with it all stitched together, and with >> many >> >> eyes and comments on it, that just seems a much more reliable >> beginning of a >> >> project than rouge skeleton projects or 3rd party commandline scaffold >> >> tools. >> >> I'm not suggesting that Armin write the repo entirely. Just start it. >> That >> >> alone makes it feel authentic. He can simply keep it slim by only >> allowing >> >> structural additions (as opposed to one with default extensions, >> example >> >> websites with config, etc) through community discussion. Even better, >> named >> >> branches can indicate the sensible variations such as "large >> applications." >> >> @Gregg: installation and config has been tough in my experience too. >> >> That's a whole different issue though. I think a good base project >> like this >> >> will help though. You can start writing about it for common cases. >> Something >> >> like: "for a W-like website, begin with the X branch from the skeleton >> repo, >> >> install Y extensions, and use configuration Z." >> >> On Wed, Nov 2, 2011 at 2:10 PM, <gregg.lind@gmail.com> wrote: >> >>> >> >>> In my experience it's not just the flask part that is an issue, it's >> all >> >>> the associated configurations and such . Having a great system that >> >>> incorpoorates html5boileeplate sort of ideas was a goal of >> Flask-tool, which >> >>> has different templates for simple, heavy, etc. >> >>> Armin, it seems your resisted this as shackling or restrictive in the >> >>> past. I glad Flask can run in simple-api mode, but for real apps >> some >> >>> common layouts would help ease new project startup quite well. >> >>> Make it easy to setup (reuirements.txt), manage, test, deploy (stock >> >>> configs), and code! >> >>> >> >>> Sent from my iPhone >> >>> On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> wrote: >> >>> >> >>> I have one also. Very different setup with no 'src' and no blueprints >> >>> (yet): http://github.com/joeyespo/flask-scaffold >> >>> Here's a proposal, since lots of newcomers wonder what's a good way to >> >>> get going in terms of structuring small or big apps. We end up all >> having >> >>> slightly-to-wildly different repo structures and because of this, >> several >> >>> scaffolds have emerged. >> >>> Armin, could you start a new project on GitHub for such a >> best-practices >> >>> starter project? Have one targeting small projects and one for large. >> Then >> >>> we can all contribute to this project instead of via email to discuss >> the >> >>> best practices and point newcomers to it. >> >>> Does anyone else think this would be valuable? I'd also hate for >> >>> something like this to become yet-another-scaffold project. >> >>> >> >>> 2011/11/2 Italo Maia <italo.maia@gmail.com> >> >>>> >> >>>> Just a little something for those in need of a simple to use flask >> >>>> project structure. Just copy the version you want from src/ and >> start coding >> >>>> = ] >> >>>> https://github.com/italomaia/flask-empty >> >>>> >> >>>> -- >> >>>> "A arrogância é a arma dos fracos." >> >>>> >> >>>> =========================== >> >>>> Italo Moreira Campelo Maia >> >>>> Bacharel em Ciência da Computação - UECE >> >>>> Desenvolvedor WEB e Desktop (Java, Python, Lua) >> >>>> Coordenador do Pug-CE >> >>>> ----------------------------------------------------- >> >>>> http://www.italomaia.com/ >> >>>> http://twitter.com/italomaia/ >> >>>> http://eusouolobomau.blogspot.com/ >> >>>> ----------------------------------------------------- >> >>>> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >> >>>> Turtle Linux 10.10 - http://bit.ly/cEw4ET >> >>>> =========================== >> >>> >> >> >> > >> > >> > >> > -- >> > Yi-Xin Liu, PHD >> > Department of Macromolecular Science >> > Fudan University >> > Room 415, Yuejing Building >> > Handan Rd. 220, Shanghai, China >> > Tel +86-021-65642863 >> > Mobile +86-13916819745 >> > http://www.mendeley.com/profiles/yi-xin-liu/ >> > >> > >
Well, I think flask should stay formless and third party guys, like us, show have our own recipes for how a flask project should look like. If all flasks project looks the same, people might start thinking their projects SHOULD looke the same. For a minimal framework, that doesn't sound that nice. And, besides that, there are flask docs recipes as reference. If you want to do it as suggested, you do it, if you don't, you don't. If more recipes were added to flask docs, a new repository with a "official" flask project recipe wouldn't be needed. @Jonathan maybe it was never a goal. Ain't that the django (great framework!) way? Why two django's? @Joe, flask-scaffold looks nice. Adding a html5 js fix to statics seemed like a good idea. I'll adopt that. Having a default js and css framework, not so much. It's bad for diversity. Didn't know flask-tools. Will read = ] 2011/11/3 Joe Esposito <espo58@gmail.com> > That'd be great. Perhaps get a list of existing scaffolds as a starting > point. > > This is why I suggest Armin start the project: > > 1. It will be hosted by the creator of Flask. This can easily be > recognized as something legit, instead of from any other GitHub user. > 2. He can have the final say on community decisions/arguments that > parallels the direction of Flask. > > If he still doesn't want to participate directly, he can add collaborators > to the GitHub project with write access. It seems there's quite a few > people excited about Flask standards, which is awesome, but can also lead > to something best summarized by this <http://xkcd.com/927/>. > > @Jonathan: I completely agree. This is still a good time to begin though. > Since Flask is still young and has a decent sized community, it'll evolve. > However without something more central for application standards, the > evolution will be quite fragmented. > > Thoughts? > > On Wed, Nov 2, 2011 at 11:04 PM, <gregg.lind@gmail.com> wrote: > >> I made a list of the contenders a few months ago and posted it here. >> Maybe we can put a wish list or pain pint list tighter and find a >> consensus. I will put some paper on it tomorrow! >> >> >> Sent from my iPhone >> >> On Nov 2, 2011, at 7:57 PM, Jonathan Chen <tamasiaina@gmail.com> wrote: >> >> I think one reason why there hasn't been an official structure or "best >> practice" I think is because flask hasn't been around enough to really have >> a "best practice." I think its really up to experience and collaboration of >> people to come up with best practices. Like convention over configuration >> or where templates should be best placed, etc. Maybe someone should start >> pulling other people's ideas and compile it into one project? >> >> ~Jonathan C. >> >> >> On Wed, Nov 2, 2011 at 6:35 PM, Gregg Lind <gregg.lind@gmail.com> wrote: >> >>> Ours is at: https://github.com/imlucas/flask-tool , and incorporates >>> html5boilerplate stuff. >>> >>> On Wed, Nov 2, 2011 at 6:30 PM, 刘一新 <liuyxpp@gmail.com> wrote: >>> > I also like the simplicity and clean of Flask at first glance. So I >>> fall in >>> > love with it. However, when I start to use it in actual website >>> development, >>> > I find it really hard to figure out which is the best structure it >>> should >>> > be. I try the one Italo once leaked in the mailinglist, But it is not >>> in >>> > python package pattern. Then I start to check the Flask-website itself >>> and >>> > also the related Flask documentation. Until now, I still not satisfy my >>> > organization (Someone interested may check it >>> > at http://pypi.python.org/pypi/ngpy/0.1), since it seems a little >>> messy of >>> > all .py file in the same folder as __init__.py. A common best-practice >>> > pattern should be very helpful and valuable. >>> > Eshin >>> > >>> > 2011/11/3 Joe Esposito <espo58@gmail.com> >>> >> >>> >> The problem isn't that there's little info on how to structure apps, >>> it's >>> >> that there's too many of them. All different. It's overwhelming >>> almost. Now >>> >> if there's an official repo with community collaboration, you can >>> feel much >>> >> more confident that you should start out that way. The samples in the >>> docs >>> >> are nice, but having a repo with it all stitched together, and with >>> many >>> >> eyes and comments on it, that just seems a much more reliable >>> beginning of a >>> >> project than rouge skeleton projects or 3rd party commandline scaffold >>> >> tools. >>> >> I'm not suggesting that Armin write the repo entirely. Just start it. >>> That >>> >> alone makes it feel authentic. He can simply keep it slim by only >>> allowing >>> >> structural additions (as opposed to one with default extensions, >>> example >>> >> websites with config, etc) through community discussion. Even better, >>> named >>> >> branches can indicate the sensible variations such as "large >>> applications." >>> >> @Gregg: installation and config has been tough in my experience too. >>> >> That's a whole different issue though. I think a good base project >>> like this >>> >> will help though. You can start writing about it for common cases. >>> Something >>> >> like: "for a W-like website, begin with the X branch from the >>> skeleton repo, >>> >> install Y extensions, and use configuration Z." >>> >> On Wed, Nov 2, 2011 at 2:10 PM, <gregg.lind@gmail.com> wrote: >>> >>> >>> >>> In my experience it's not just the flask part that is an issue, it's >>> all >>> >>> the associated configurations and such . Having a great system that >>> >>> incorpoorates html5boileeplate sort of ideas was a goal of >>> Flask-tool, which >>> >>> has different templates for simple, heavy, etc. >>> >>> Armin, it seems your resisted this as shackling or restrictive in the >>> >>> past. I glad Flask can run in simple-api mode, but for real apps >>> some >>> >>> common layouts would help ease new project startup quite well. >>> >>> Make it easy to setup (reuirements.txt), manage, test, deploy (stock >>> >>> configs), and code! >>> >>> >>> >>> Sent from my iPhone >>> >>> On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> wrote: >>> >>> >>> >>> I have one also. Very different setup with no 'src' and no blueprints >>> >>> (yet): http://github.com/joeyespo/flask-scaffold >>> >>> Here's a proposal, since lots of newcomers wonder what's a good way >>> to >>> >>> get going in terms of structuring small or big apps. We end up all >>> having >>> >>> slightly-to-wildly different repo structures and because of this, >>> several >>> >>> scaffolds have emerged. >>> >>> Armin, could you start a new project on GitHub for such a >>> best-practices >>> >>> starter project? Have one targeting small projects and one for >>> large. Then >>> >>> we can all contribute to this project instead of via email to >>> discuss the >>> >>> best practices and point newcomers to it. >>> >>> Does anyone else think this would be valuable? I'd also hate for >>> >>> something like this to become yet-another-scaffold project. >>> >>> >>> >>> 2011/11/2 Italo Maia <italo.maia@gmail.com> >>> >>>> >>> >>>> Just a little something for those in need of a simple to use flask >>> >>>> project structure. Just copy the version you want from src/ and >>> start coding >>> >>>> = ] >>> >>>> https://github.com/italomaia/flask-empty >>> >>>> >>> >>>> -- >>> >>>> "A arrogância é a arma dos fracos." >>> >>>> >>> >>>> =========================== >>> >>>> Italo Moreira Campelo Maia >>> >>>> Bacharel em Ciência da Computação - UECE >>> >>>> Desenvolvedor WEB e Desktop (Java, Python, Lua) >>> >>>> Coordenador do Pug-CE >>> >>>> ----------------------------------------------------- >>> >>>> http://www.italomaia.com/ >>> >>>> http://twitter.com/italomaia/ >>> >>>> http://eusouolobomau.blogspot.com/ >>> >>>> ----------------------------------------------------- >>> >>>> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >>> >>>> Turtle Linux 10.10 - http://bit.ly/cEw4ET >>> >>>> =========================== >>> >>> >>> >> >>> > >>> > >>> > >>> > -- >>> > Yi-Xin Liu, PHD >>> > Department of Macromolecular Science >>> > Fudan University >>> > Room 415, Yuejing Building >>> > Handan Rd. 220, Shanghai, China >>> > Tel +86-021-65642863 >>> > Mobile +86-13916819745 >>> > http://www.mendeley.com/profiles/yi-xin-liu/ >>> > >>> >> >> > -- "A arrogância é a arma dos fracos." =========================== Italo Moreira Campelo Maia Bacharel em Ciência da Computação - UECE Desenvolvedor WEB e Desktop (Java, Python, Lua) Coordenador do Pug-CE ----------------------------------------------------- http://www.italomaia.com/ http://twitter.com/italomaia/ http://eusouolobomau.blogspot.com/ ----------------------------------------------------- Turtle Linux 9.10 - http://tiny.cc/blogturtle910 Turtle Linux 10.10 - http://bit.ly/cEw4ET ===========================
+1 for Italo's response. This is what I wanted to say but he said it better. On Fri, Nov 4, 2011 at 8:17 AM, Italo Maia <italo.maia@gmail.com> wrote: > Well, I think flask should stay formless and third party guys, like us, show > have our own recipes for how a flask project should look like. If all flasks > project looks the same, people might start thinking their projects SHOULD > looke the same. For a minimal framework, that doesn't sound that nice. And, > besides that, there are flask docs recipes as reference. If you want to do > it as suggested, you do it, if you don't, you don't. If more recipes were > added to flask docs, a new repository with a "official" flask project recipe > wouldn't be needed. > > @Jonathan maybe it was never a goal. Ain't that the django (great > framework!) way? Why two django's? > @Joe, flask-scaffold looks nice. Adding a html5 js fix to statics seemed > like a good idea. I'll adopt that. Having a default js and css framework, > not so much. It's bad for diversity. > Didn't know flask-tools. Will read = ] > 2011/11/3 Joe Esposito <espo58@gmail.com> >> >> That'd be great. Perhaps get a list of existing scaffolds as a starting >> point. >> This is why I suggest Armin start the project: >> >> It will be hosted by the creator of Flask. This can easily be recognized >> as something legit, instead of from any other GitHub user. >> He can have the final say on community decisions/arguments that parallels >> the direction of Flask. >> >> If he still doesn't want to participate directly, he can add collaborators >> to the GitHub project with write access. It seems there's quite a few people >> excited about Flask standards, which is awesome, but can also lead to >> something best summarized by this. >> @Jonathan: I completely agree. This is still a good time to begin though. >> Since Flask is still young and has a decent sized community, it'll evolve. >> However without something more central for application standards, the >> evolution will be quite fragmented. >> Thoughts? >> On Wed, Nov 2, 2011 at 11:04 PM, <gregg.lind@gmail.com> wrote: >>> >>> I made a list of the contenders a few months ago and posted it here. >>> Maybe we can put a wish list or pain pint list tighter and find a >>> consensus. I will put some paper on it tomorrow! >>> >>> Sent from my iPhone >>> On Nov 2, 2011, at 7:57 PM, Jonathan Chen <tamasiaina@gmail.com> wrote: >>> >>> I think one reason why there hasn't been an official structure or "best >>> practice" I think is because flask hasn't been around enough to really have >>> a "best practice." I think its really up to experience and collaboration of >>> people to come up with best practices. Like convention over configuration or >>> where templates should be best placed, etc. Maybe someone should start >>> pulling other people's ideas and compile it into one project? >>> >>> ~Jonathan C. >>> >>> >>> On Wed, Nov 2, 2011 at 6:35 PM, Gregg Lind <gregg.lind@gmail.com> wrote: >>>> >>>> Ours is at: https://github.com/imlucas/flask-tool , and incorporates >>>> html5boilerplate stuff. >>>> >>>> On Wed, Nov 2, 2011 at 6:30 PM, 刘一新 <liuyxpp@gmail.com> wrote: >>>> > I also like the simplicity and clean of Flask at first glance. So I >>>> > fall in >>>> > love with it. However, when I start to use it in actual website >>>> > development, >>>> > I find it really hard to figure out which is the best structure it >>>> > should >>>> > be. I try the one Italo once leaked in the mailinglist, But it is not >>>> > in >>>> > python package pattern. Then I start to check the Flask-website itself >>>> > and >>>> > also the related Flask documentation. Until now, I still not satisfy >>>> > my >>>> > organization (Someone interested may check it >>>> > at http://pypi.python.org/pypi/ngpy/0.1), since it seems a little >>>> > messy of >>>> > all .py file in the same folder as __init__.py. A common best-practice >>>> > pattern should be very helpful and valuable. >>>> > Eshin >>>> > >>>> > 2011/11/3 Joe Esposito <espo58@gmail.com> >>>> >> >>>> >> The problem isn't that there's little info on how to structure apps, >>>> >> it's >>>> >> that there's too many of them. All different. It's overwhelming >>>> >> almost. Now >>>> >> if there's an official repo with community collaboration, you can >>>> >> feel much >>>> >> more confident that you should start out that way. The samples in the >>>> >> docs >>>> >> are nice, but having a repo with it all stitched together, and with >>>> >> many >>>> >> eyes and comments on it, that just seems a much more reliable >>>> >> beginning of a >>>> >> project than rouge skeleton projects or 3rd party commandline >>>> >> scaffold >>>> >> tools. >>>> >> I'm not suggesting that Armin write the repo entirely. Just start it. >>>> >> That >>>> >> alone makes it feel authentic. He can simply keep it slim by only >>>> >> allowing >>>> >> structural additions (as opposed to one with default extensions, >>>> >> example >>>> >> websites with config, etc) through community discussion. Even better, >>>> >> named >>>> >> branches can indicate the sensible variations such as "large >>>> >> applications." >>>> >> @Gregg: installation and config has been tough in my experience too. >>>> >> That's a whole different issue though. I think a good base project >>>> >> like this >>>> >> will help though. You can start writing about it for common cases. >>>> >> Something >>>> >> like: "for a W-like website, begin with the X branch from the >>>> >> skeleton repo, >>>> >> install Y extensions, and use configuration Z." >>>> >> On Wed, Nov 2, 2011 at 2:10 PM, <gregg.lind@gmail.com> wrote: >>>> >>> >>>> >>> In my experience it's not just the flask part that is an issue, it's >>>> >>> all >>>> >>> the associated configurations and such . Having a great system that >>>> >>> incorpoorates html5boileeplate sort of ideas was a goal of >>>> >>> Flask-tool, which >>>> >>> has different templates for simple, heavy, etc. >>>> >>> Armin, it seems your resisted this as shackling or restrictive in >>>> >>> the >>>> >>> past. I glad Flask can run in simple-api mode, but for real apps >>>> >>> some >>>> >>> common layouts would help ease new project startup quite well. >>>> >>> Make it easy to setup (reuirements.txt), manage, test, deploy (stock >>>> >>> configs), and code! >>>> >>> >>>> >>> Sent from my iPhone >>>> >>> On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> wrote: >>>> >>> >>>> >>> I have one also. Very different setup with no 'src' and no >>>> >>> blueprints >>>> >>> (yet): http://github.com/joeyespo/flask-scaffold >>>> >>> Here's a proposal, since lots of newcomers wonder what's a good way >>>> >>> to >>>> >>> get going in terms of structuring small or big apps. We end up all >>>> >>> having >>>> >>> slightly-to-wildly different repo structures and because of this, >>>> >>> several >>>> >>> scaffolds have emerged. >>>> >>> Armin, could you start a new project on GitHub for such a >>>> >>> best-practices >>>> >>> starter project? Have one targeting small projects and one for >>>> >>> large. Then >>>> >>> we can all contribute to this project instead of via email to >>>> >>> discuss the >>>> >>> best practices and point newcomers to it. >>>> >>> Does anyone else think this would be valuable? I'd also hate for >>>> >>> something like this to become yet-another-scaffold project. >>>> >>> >>>> >>> 2011/11/2 Italo Maia <italo.maia@gmail.com> >>>> >>>> >>>> >>>> Just a little something for those in need of a simple to use flask >>>> >>>> project structure. Just copy the version you want from src/ and >>>> >>>> start coding >>>> >>>> = ] >>>> >>>> https://github.com/italomaia/flask-empty >>>> >>>> >>>> >>>> -- >>>> >>>> "A arrogância é a arma dos fracos." >>>> >>>> >>>> >>>> =========================== >>>> >>>> Italo Moreira Campelo Maia >>>> >>>> Bacharel em Ciência da Computação - UECE >>>> >>>> Desenvolvedor WEB e Desktop (Java, Python, Lua) >>>> >>>> Coordenador do Pug-CE >>>> >>>> ----------------------------------------------------- >>>> >>>> http://www.italomaia.com/ >>>> >>>> http://twitter.com/italomaia/ >>>> >>>> http://eusouolobomau.blogspot.com/ >>>> >>>> ----------------------------------------------------- >>>> >>>> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >>>> >>>> Turtle Linux 10.10 - http://bit.ly/cEw4ET >>>> >>>> =========================== >>>> >>> >>>> >> >>>> > >>>> > >>>> > >>>> > -- >>>> > Yi-Xin Liu, PHD >>>> > Department of Macromolecular Science >>>> > Fudan University >>>> > Room 415, Yuejing Building >>>> > Handan Rd. 220, Shanghai, China >>>> > Tel +86-021-65642863 >>>> > Mobile +86-13916819745 >>>> > http://www.mendeley.com/profiles/yi-xin-liu/ >>>> > >>> >> > > > > -- > "A arrogância é a arma dos fracos." > > =========================== > Italo Moreira Campelo Maia > Bacharel em Ciência da Computação - UECE > Desenvolvedor WEB e Desktop (Java, Python, Lua) > Coordenador do Pug-CE > ----------------------------------------------------- > http://www.italomaia.com/ > http://twitter.com/italomaia/ > http://eusouolobomau.blogspot.com/ > ----------------------------------------------------- > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > Turtle Linux 10.10 - http://bit.ly/cEw4ET > =========================== >
Yeah, I think it'll be good to compile or make a list of people's organization together so that people can see what is good and what fits them. I like flask because it allows me to be flexible. I think it'll be good to see other people's ideas. ~Jonathan C. On Thu, Nov 3, 2011 at 9:53 PM, Adam Patterson <fakeempire@gmail.com> wrote: > +1 for Italo's response. This is what I wanted to say but he said it > better. > > On Fri, Nov 4, 2011 at 8:17 AM, Italo Maia <italo.maia@gmail.com> wrote: > > Well, I think flask should stay formless and third party guys, like us, > show > > have our own recipes for how a flask project should look like. If all > flasks > > project looks the same, people might start thinking their projects SHOULD > > looke the same. For a minimal framework, that doesn't sound that nice. > And, > > besides that, there are flask docs recipes as reference. If you want to > do > > it as suggested, you do it, if you don't, you don't. If more recipes were > > added to flask docs, a new repository with a "official" flask project > recipe > > wouldn't be needed. > > > > @Jonathan maybe it was never a goal. Ain't that the django (great > > framework!) way? Why two django's? > > @Joe, flask-scaffold looks nice. Adding a html5 js fix to statics seemed > > like a good idea. I'll adopt that. Having a default js and css framework, > > not so much. It's bad for diversity. > > Didn't know flask-tools. Will read = ] > > 2011/11/3 Joe Esposito <espo58@gmail.com> > >> > >> That'd be great. Perhaps get a list of existing scaffolds as a starting > >> point. > >> This is why I suggest Armin start the project: > >> > >> It will be hosted by the creator of Flask. This can easily be recognized > >> as something legit, instead of from any other GitHub user. > >> He can have the final say on community decisions/arguments that > parallels > >> the direction of Flask. > >> > >> If he still doesn't want to participate directly, he can add > collaborators > >> to the GitHub project with write access. It seems there's quite a few > people > >> excited about Flask standards, which is awesome, but can also lead to > >> something best summarized by this. > >> @Jonathan: I completely agree. This is still a good time to begin > though. > >> Since Flask is still young and has a decent sized community, it'll > evolve. > >> However without something more central for application standards, the > >> evolution will be quite fragmented. > >> Thoughts? > >> On Wed, Nov 2, 2011 at 11:04 PM, <gregg.lind@gmail.com> wrote: > >>> > >>> I made a list of the contenders a few months ago and posted it here. > >>> Maybe we can put a wish list or pain pint list tighter and find a > >>> consensus. I will put some paper on it tomorrow! > >>> > >>> Sent from my iPhone > >>> On Nov 2, 2011, at 7:57 PM, Jonathan Chen <tamasiaina@gmail.com> > wrote: > >>> > >>> I think one reason why there hasn't been an official structure or "best > >>> practice" I think is because flask hasn't been around enough to really > have > >>> a "best practice." I think its really up to experience and > collaboration of > >>> people to come up with best practices. Like convention over > configuration or > >>> where templates should be best placed, etc. Maybe someone should start > >>> pulling other people's ideas and compile it into one project? > >>> > >>> ~Jonathan C. > >>> > >>> > >>> On Wed, Nov 2, 2011 at 6:35 PM, Gregg Lind <gregg.lind@gmail.com> > wrote: > >>>> > >>>> Ours is at: https://github.com/imlucas/flask-tool , and incorporates > >>>> html5boilerplate stuff. > >>>> > >>>> On Wed, Nov 2, 2011 at 6:30 PM, 刘一新 <liuyxpp@gmail.com> wrote: > >>>> > I also like the simplicity and clean of Flask at first glance. So I > >>>> > fall in > >>>> > love with it. However, when I start to use it in actual website > >>>> > development, > >>>> > I find it really hard to figure out which is the best structure it > >>>> > should > >>>> > be. I try the one Italo once leaked in the mailinglist, But it is > not > >>>> > in > >>>> > python package pattern. Then I start to check the Flask-website > itself > >>>> > and > >>>> > also the related Flask documentation. Until now, I still not satisfy > >>>> > my > >>>> > organization (Someone interested may check it > >>>> > at http://pypi.python.org/pypi/ngpy/0.1), since it seems a little > >>>> > messy of > >>>> > all .py file in the same folder as __init__.py. A common > best-practice > >>>> > pattern should be very helpful and valuable. > >>>> > Eshin > >>>> > > >>>> > 2011/11/3 Joe Esposito <espo58@gmail.com> > >>>> >> > >>>> >> The problem isn't that there's little info on how to structure > apps, > >>>> >> it's > >>>> >> that there's too many of them. All different. It's overwhelming > >>>> >> almost. Now > >>>> >> if there's an official repo with community collaboration, you can > >>>> >> feel much > >>>> >> more confident that you should start out that way. The samples in > the > >>>> >> docs > >>>> >> are nice, but having a repo with it all stitched together, and with > >>>> >> many > >>>> >> eyes and comments on it, that just seems a much more reliable > >>>> >> beginning of a > >>>> >> project than rouge skeleton projects or 3rd party commandline > >>>> >> scaffold > >>>> >> tools. > >>>> >> I'm not suggesting that Armin write the repo entirely. Just start > it. > >>>> >> That > >>>> >> alone makes it feel authentic. He can simply keep it slim by only > >>>> >> allowing > >>>> >> structural additions (as opposed to one with default extensions, > >>>> >> example > >>>> >> websites with config, etc) through community discussion. Even > better, > >>>> >> named > >>>> >> branches can indicate the sensible variations such as "large > >>>> >> applications." > >>>> >> @Gregg: installation and config has been tough in my experience > too. > >>>> >> That's a whole different issue though. I think a good base project > >>>> >> like this > >>>> >> will help though. You can start writing about it for common cases. > >>>> >> Something > >>>> >> like: "for a W-like website, begin with the X branch from the > >>>> >> skeleton repo, > >>>> >> install Y extensions, and use configuration Z." > >>>> >> On Wed, Nov 2, 2011 at 2:10 PM, <gregg.lind@gmail.com> wrote: > >>>> >>> > >>>> >>> In my experience it's not just the flask part that is an issue, > it's > >>>> >>> all > >>>> >>> the associated configurations and such . Having a great system > that > >>>> >>> incorpoorates html5boileeplate sort of ideas was a goal of > >>>> >>> Flask-tool, which > >>>> >>> has different templates for simple, heavy, etc. > >>>> >>> Armin, it seems your resisted this as shackling or restrictive in > >>>> >>> the > >>>> >>> past. I glad Flask can run in simple-api mode, but for real apps > >>>> >>> some > >>>> >>> common layouts would help ease new project startup quite well. > >>>> >>> Make it easy to setup (reuirements.txt), manage, test, deploy > (stock > >>>> >>> configs), and code! > >>>> >>> > >>>> >>> Sent from my iPhone > >>>> >>> On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> > wrote: > >>>> >>> > >>>> >>> I have one also. Very different setup with no 'src' and no > >>>> >>> blueprints > >>>> >>> (yet): http://github.com/joeyespo/flask-scaffold > >>>> >>> Here's a proposal, since lots of newcomers wonder what's a good > way > >>>> >>> to > >>>> >>> get going in terms of structuring small or big apps. We end up all > >>>> >>> having > >>>> >>> slightly-to-wildly different repo structures and because of this, > >>>> >>> several > >>>> >>> scaffolds have emerged. > >>>> >>> Armin, could you start a new project on GitHub for such a > >>>> >>> best-practices > >>>> >>> starter project? Have one targeting small projects and one for > >>>> >>> large. Then > >>>> >>> we can all contribute to this project instead of via email to > >>>> >>> discuss the > >>>> >>> best practices and point newcomers to it. > >>>> >>> Does anyone else think this would be valuable? I'd also hate for > >>>> >>> something like this to become yet-another-scaffold project. > >>>> >>> > >>>> >>> 2011/11/2 Italo Maia <italo.maia@gmail.com> > >>>> >>>> > >>>> >>>> Just a little something for those in need of a simple to use > flask > >>>> >>>> project structure. Just copy the version you want from src/ and > >>>> >>>> start coding > >>>> >>>> = ] > >>>> >>>> https://github.com/italomaia/flask-empty > >>>> >>>> > >>>> >>>> -- > >>>> >>>> "A arrogância é a arma dos fracos." > >>>> >>>> > >>>> >>>> =========================== > >>>> >>>> Italo Moreira Campelo Maia > >>>> >>>> Bacharel em Ciência da Computação - UECE > >>>> >>>> Desenvolvedor WEB e Desktop (Java, Python, Lua) > >>>> >>>> Coordenador do Pug-CE > >>>> >>>> ----------------------------------------------------- > >>>> >>>> http://www.italomaia.com/ > >>>> >>>> http://twitter.com/italomaia/ > >>>> >>>> http://eusouolobomau.blogspot.com/ > >>>> >>>> ----------------------------------------------------- > >>>> >>>> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > >>>> >>>> Turtle Linux 10.10 - http://bit.ly/cEw4ET > >>>> >>>> =========================== > >>>> >>> > >>>> >> > >>>> > > >>>> > > >>>> > > >>>> > -- > >>>> > Yi-Xin Liu, PHD > >>>> > Department of Macromolecular Science > >>>> > Fudan University > >>>> > Room 415, Yuejing Building > >>>> > Handan Rd. 220, Shanghai, China > >>>> > Tel +86-021-65642863 > >>>> > Mobile +86-13916819745 > >>>> > http://www.mendeley.com/profiles/yi-xin-liu/ > >>>> > > >>> > >> > > > > > > > > -- > > "A arrogância é a arma dos fracos." > > > > =========================== > > Italo Moreira Campelo Maia > > Bacharel em Ciência da Computação - UECE > > Desenvolvedor WEB e Desktop (Java, Python, Lua) > > Coordenador do Pug-CE > > ----------------------------------------------------- > > http://www.italomaia.com/ > > http://twitter.com/italomaia/ > > http://eusouolobomau.blogspot.com/ > > ----------------------------------------------------- > > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 > > Turtle Linux 10.10 - http://bit.ly/cEw4ET > > =========================== > > >
When I need some inspiration, I always take a look at http://flask.pocoo.org/community/poweredby/ and scan the available sourcecode. Instead of making a template, maybe we should focus on this section of the website stronger. Or, if we really want blank canvases to use for our applications, maybe we can create a subsection of that website for blank template style code repositories... Josh On Fri, Nov 4, 2011 at 1:42 AM, Jonathan Chen <tamasiaina@gmail.com> wrote: > Yeah, > > I think it'll be good to compile or make a list of people's organization > together so that people can see what is good and what fits them. I like > flask because it allows me to be flexible. I think it'll be good to see > other people's ideas. > > ~Jonathan C. > > > > On Thu, Nov 3, 2011 at 9:53 PM, Adam Patterson <fakeempire@gmail.com>wrote: > >> +1 for Italo's response. This is what I wanted to say but he said it >> better. >> >> On Fri, Nov 4, 2011 at 8:17 AM, Italo Maia <italo.maia@gmail.com> wrote: >> > Well, I think flask should stay formless and third party guys, like us, >> show >> > have our own recipes for how a flask project should look like. If all >> flasks >> > project looks the same, people might start thinking their projects >> SHOULD >> > looke the same. For a minimal framework, that doesn't sound that nice. >> And, >> > besides that, there are flask docs recipes as reference. If you want to >> do >> > it as suggested, you do it, if you don't, you don't. If more recipes >> were >> > added to flask docs, a new repository with a "official" flask project >> recipe >> > wouldn't be needed. >> > >> > @Jonathan maybe it was never a goal. Ain't that the django (great >> > framework!) way? Why two django's? >> > @Joe, flask-scaffold looks nice. Adding a html5 js fix to statics seemed >> > like a good idea. I'll adopt that. Having a default js and css >> framework, >> > not so much. It's bad for diversity. >> > Didn't know flask-tools. Will read = ] >> > 2011/11/3 Joe Esposito <espo58@gmail.com> >> >> >> >> That'd be great. Perhaps get a list of existing scaffolds as a starting >> >> point. >> >> This is why I suggest Armin start the project: >> >> >> >> It will be hosted by the creator of Flask. This can easily be >> recognized >> >> as something legit, instead of from any other GitHub user. >> >> He can have the final say on community decisions/arguments that >> parallels >> >> the direction of Flask. >> >> >> >> If he still doesn't want to participate directly, he can add >> collaborators >> >> to the GitHub project with write access. It seems there's quite a few >> people >> >> excited about Flask standards, which is awesome, but can also lead to >> >> something best summarized by this. >> >> @Jonathan: I completely agree. This is still a good time to begin >> though. >> >> Since Flask is still young and has a decent sized community, it'll >> evolve. >> >> However without something more central for application standards, the >> >> evolution will be quite fragmented. >> >> Thoughts? >> >> On Wed, Nov 2, 2011 at 11:04 PM, <gregg.lind@gmail.com> wrote: >> >>> >> >>> I made a list of the contenders a few months ago and posted it here. >> >>> Maybe we can put a wish list or pain pint list tighter and find a >> >>> consensus. I will put some paper on it tomorrow! >> >>> >> >>> Sent from my iPhone >> >>> On Nov 2, 2011, at 7:57 PM, Jonathan Chen <tamasiaina@gmail.com> >> wrote: >> >>> >> >>> I think one reason why there hasn't been an official structure or >> "best >> >>> practice" I think is because flask hasn't been around enough to >> really have >> >>> a "best practice." I think its really up to experience and >> collaboration of >> >>> people to come up with best practices. Like convention over >> configuration or >> >>> where templates should be best placed, etc. Maybe someone should start >> >>> pulling other people's ideas and compile it into one project? >> >>> >> >>> ~Jonathan C. >> >>> >> >>> >> >>> On Wed, Nov 2, 2011 at 6:35 PM, Gregg Lind <gregg.lind@gmail.com> >> wrote: >> >>>> >> >>>> Ours is at: https://github.com/imlucas/flask-tool , and >> incorporates >> >>>> html5boilerplate stuff. >> >>>> >> >>>> On Wed, Nov 2, 2011 at 6:30 PM, 刘一新 <liuyxpp@gmail.com> wrote: >> >>>> > I also like the simplicity and clean of Flask at first glance. So I >> >>>> > fall in >> >>>> > love with it. However, when I start to use it in actual website >> >>>> > development, >> >>>> > I find it really hard to figure out which is the best structure it >> >>>> > should >> >>>> > be. I try the one Italo once leaked in the mailinglist, But it is >> not >> >>>> > in >> >>>> > python package pattern. Then I start to check the Flask-website >> itself >> >>>> > and >> >>>> > also the related Flask documentation. Until now, I still not >> satisfy >> >>>> > my >> >>>> > organization (Someone interested may check it >> >>>> > at http://pypi.python.org/pypi/ngpy/0.1), since it seems a little >> >>>> > messy of >> >>>> > all .py file in the same folder as __init__.py. A common >> best-practice >> >>>> > pattern should be very helpful and valuable. >> >>>> > Eshin >> >>>> > >> >>>> > 2011/11/3 Joe Esposito <espo58@gmail.com> >> >>>> >> >> >>>> >> The problem isn't that there's little info on how to structure >> apps, >> >>>> >> it's >> >>>> >> that there's too many of them. All different. It's overwhelming >> >>>> >> almost. Now >> >>>> >> if there's an official repo with community collaboration, you can >> >>>> >> feel much >> >>>> >> more confident that you should start out that way. The samples in >> the >> >>>> >> docs >> >>>> >> are nice, but having a repo with it all stitched together, and >> with >> >>>> >> many >> >>>> >> eyes and comments on it, that just seems a much more reliable >> >>>> >> beginning of a >> >>>> >> project than rouge skeleton projects or 3rd party commandline >> >>>> >> scaffold >> >>>> >> tools. >> >>>> >> I'm not suggesting that Armin write the repo entirely. Just start >> it. >> >>>> >> That >> >>>> >> alone makes it feel authentic. He can simply keep it slim by only >> >>>> >> allowing >> >>>> >> structural additions (as opposed to one with default extensions, >> >>>> >> example >> >>>> >> websites with config, etc) through community discussion. Even >> better, >> >>>> >> named >> >>>> >> branches can indicate the sensible variations such as "large >> >>>> >> applications." >> >>>> >> @Gregg: installation and config has been tough in my experience >> too. >> >>>> >> That's a whole different issue though. I think a good base project >> >>>> >> like this >> >>>> >> will help though. You can start writing about it for common cases. >> >>>> >> Something >> >>>> >> like: "for a W-like website, begin with the X branch from the >> >>>> >> skeleton repo, >> >>>> >> install Y extensions, and use configuration Z." >> >>>> >> On Wed, Nov 2, 2011 at 2:10 PM, <gregg.lind@gmail.com> wrote: >> >>>> >>> >> >>>> >>> In my experience it's not just the flask part that is an issue, >> it's >> >>>> >>> all >> >>>> >>> the associated configurations and such . Having a great system >> that >> >>>> >>> incorpoorates html5boileeplate sort of ideas was a goal of >> >>>> >>> Flask-tool, which >> >>>> >>> has different templates for simple, heavy, etc. >> >>>> >>> Armin, it seems your resisted this as shackling or restrictive in >> >>>> >>> the >> >>>> >>> past. I glad Flask can run in simple-api mode, but for real >> apps >> >>>> >>> some >> >>>> >>> common layouts would help ease new project startup quite well. >> >>>> >>> Make it easy to setup (reuirements.txt), manage, test, deploy >> (stock >> >>>> >>> configs), and code! >> >>>> >>> >> >>>> >>> Sent from my iPhone >> >>>> >>> On Nov 2, 2011, at 10:56 AM, Joe Esposito <espo58@gmail.com> >> wrote: >> >>>> >>> >> >>>> >>> I have one also. Very different setup with no 'src' and no >> >>>> >>> blueprints >> >>>> >>> (yet): http://github.com/joeyespo/flask-scaffold >> >>>> >>> Here's a proposal, since lots of newcomers wonder what's a good >> way >> >>>> >>> to >> >>>> >>> get going in terms of structuring small or big apps. We end up >> all >> >>>> >>> having >> >>>> >>> slightly-to-wildly different repo structures and because of this, >> >>>> >>> several >> >>>> >>> scaffolds have emerged. >> >>>> >>> Armin, could you start a new project on GitHub for such a >> >>>> >>> best-practices >> >>>> >>> starter project? Have one targeting small projects and one for >> >>>> >>> large. Then >> >>>> >>> we can all contribute to this project instead of via email to >> >>>> >>> discuss the >> >>>> >>> best practices and point newcomers to it. >> >>>> >>> Does anyone else think this would be valuable? I'd also hate for >> >>>> >>> something like this to become yet-another-scaffold project. >> >>>> >>> >> >>>> >>> 2011/11/2 Italo Maia <italo.maia@gmail.com> >> >>>> >>>> >> >>>> >>>> Just a little something for those in need of a simple to use >> flask >> >>>> >>>> project structure. Just copy the version you want from src/ and >> >>>> >>>> start coding >> >>>> >>>> = ] >> >>>> >>>> https://github.com/italomaia/flask-empty >> >>>> >>>> >> >>>> >>>> -- >> >>>> >>>> "A arrogância é a arma dos fracos." >> >>>> >>>> >> >>>> >>>> =========================== >> >>>> >>>> Italo Moreira Campelo Maia >> >>>> >>>> Bacharel em Ciência da Computação - UECE >> >>>> >>>> Desenvolvedor WEB e Desktop (Java, Python, Lua) >> >>>> >>>> Coordenador do Pug-CE >> >>>> >>>> ----------------------------------------------------- >> >>>> >>>> http://www.italomaia.com/ >> >>>> >>>> http://twitter.com/italomaia/ >> >>>> >>>> http://eusouolobomau.blogspot.com/ >> >>>> >>>> ----------------------------------------------------- >> >>>> >>>> Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >> >>>> >>>> Turtle Linux 10.10 - http://bit.ly/cEw4ET >> >>>> >>>> =========================== >> >>>> >>> >> >>>> >> >> >>>> > >> >>>> > >> >>>> > >> >>>> > -- >> >>>> > Yi-Xin Liu, PHD >> >>>> > Department of Macromolecular Science >> >>>> > Fudan University >> >>>> > Room 415, Yuejing Building >> >>>> > Handan Rd. 220, Shanghai, China >> >>>> > Tel +86-021-65642863 >> >>>> > Mobile +86-13916819745 >> >>>> > http://www.mendeley.com/profiles/yi-xin-liu/ >> >>>> > >> >>> >> >> >> > >> > >> > >> > -- >> > "A arrogância é a arma dos fracos." >> > >> > =========================== >> > Italo Moreira Campelo Maia >> > Bacharel em Ciência da Computação - UECE >> > Desenvolvedor WEB e Desktop (Java, Python, Lua) >> > Coordenador do Pug-CE >> > ----------------------------------------------------- >> > http://www.italomaia.com/ >> > http://twitter.com/italomaia/ >> > http://eusouolobomau.blogspot.com/ >> > ----------------------------------------------------- >> > Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >> > Turtle Linux 10.10 - http://bit.ly/cEw4ET >> > =========================== >> > >> > >
Hi,
On 11/3/11 4:42 AM, Joe Esposito wrote:
> This is why I suggest Armin start the project:
I'm obsessed with beautiful code and will become grumpy if I find old
code of mind that I wrote before I knew better. When I would make a
"How to use Flask quickly and easily" in 2011 it would be outdated in
2012 and people would still use the old code for their projects because
it ranks high on Google etc.
I could not live with myself then. I absolutely hate Boilerplate code
that goes stale. :-)
Regards,
Armin
+N On Thu, Nov 3, 2011 at 21:21, Armin Ronacher <armin.ronacher@active-4.com>wrote: > I'm obsessed with beautiful code and will become grumpy if I find old > code of mind that I wrote before I knew better. When I would make a > "How to use Flask quickly and easily" in 2011 it would be outdated in > 2012 and people would still use the old code for their projects because > it ranks high on Google etc. > > I could not live with myself then. I absolutely hate Boilerplate code > that goes stale. :-) > -- Juancarlo *Añez*
@John +1, I like that idea. @Italo Thanks! That was my first crack at it long ago to get a better understanding of what a well structured app should look like. It definitely needs updated now that I know more. This was what I was trying to get at earlier though. Newcomers won't know which 3rd-party scaffolds actually do come from experience and which are toys. Having an official place will lessen that doubt. Perhaps focusing on powered-by can help too. On Fri, Nov 4, 2011 at 11:26 AM, Juancarlo Añez <apalala@gmail.com> wrote: > +N > > > On Thu, Nov 3, 2011 at 21:21, Armin Ronacher <armin.ronacher@active-4.com>wrote: > >> I'm obsessed with beautiful code and will become grumpy if I find old >> code of mind that I wrote before I knew better. When I would make a >> "How to use Flask quickly and easily" in 2011 it would be outdated in >> 2012 and people would still use the old code for their projects because >> it ranks high on Google etc. >> >> I could not live with myself then. I absolutely hate Boilerplate code >> that goes stale. :-) >> > > > > -- > Juancarlo *Añez* >
i very much like this idea, although the flask documentation had snippets and samples of some structures, i would have liked to have seen the actual structure in its full context of the application. I had to look at different peoples projects on github(including Armin's flask site) to see the advantages/disadvantages of the different structures and how to instantiate the flask object in each case. ________________________________ From: Joe Esposito <espo58@gmail.com> To: flask@librelist.com Sent: Wednesday, November 2, 2011 1:56 PM Subject: Re: [flask] Flask-Empty I have one also. Very different setup with no 'src' and no blueprints (yet): http://github.com/joeyespo/flask-scaffold Here's a proposal, since lots of newcomers wonder what's a good way to get going in terms of structuring small or big apps. We end up all having slightly-to-wildly different repo structures and because of this, several scaffolds have emerged. Armin, could you start a new project on GitHub for such a best-practices starter project? Have one targeting small projects and one for large. Then we can all contribute to this project instead of via email to discuss the best practices and point newcomers to it. Does anyone else think this would be valuable? I'd also hate for something like this to become yet-another-scaffold project. 2011/11/2 Italo Maia <italo.maia@gmail.com> Just a little something for those in need of a simple to use flask project structure. Just copy the version you want from src/ and start coding = ] >https://github.com/italomaia/flask-empty > >-- >"A arrogância é a arma dos fracos." > >=========================== >Italo Moreira Campelo Maia >Bacharel em Ciência da Computação - UECE >Desenvolvedor WEB e Desktop (Java, Python, Lua) >Coordenador do Pug-CE >----------------------------------------------------- >http://www.italomaia.com/ >http://twitter.com/italomaia/ >http://eusouolobomau.blogspot.com/ >----------------------------------------------------- >Turtle Linux 9.10 - http://tiny.cc/blogturtle910 >Turtle Linux 10.10 - http://bit.ly/cEw4ET >=========================== >