librelist archives

« back to archive

Re: Technical Help

Re: Technical Help

From:
vivek poddar
Date:
2012-05-27 @ 17:56
Hi,

I am learning flask since few days, I had an application in my mind since
many days but after reading about flask I thought that it bests suites my
needs. I have now started working on my app. But I have a small doubt, I am
not really getting the blueprint stuff. I read the docs but I really need
to understand it in the simpler language or I am missing something.

Thanks in advance!

-- 

         -*- *Vivek Poddar* -*-

 *Technical consultant (OpenERP)*

*Blog:http://vivekimsit.blogspot.in/
*

Re: [flask] Re: Technical Help

From:
Simon Sapin
Date:
2012-05-27 @ 19:23
Le 27/05/2012 19:56, vivek poddar a écrit :
> I am not really getting the blueprint stuff. I read the docs but I
> really need to understand it in the simpler language or I am missing
> something.

A blueprint is a set of views, templates and static files that can be 
later added to an app with an URL prefix. They can help to keep modular 
or reusable.

If you’re only starting don’t worry too much about blueprints. To can 
start without them, and consider them later as your application grows.

Regards,
-- 
Simon Sapin

Re: [flask] Re: Technical Help

From:
Anderson Cardoso
Date:
2012-05-27 @ 22:47
A blueprint it's like a plugable flask app. You mount it on a given prefix,
this way you can keep different features in different packages (blueprints).
I'm working on a app where every feature is a blueprint (even the root
app). This is my way of working (for now).
But you can easily come with your own way, or do everything in one app (I
mean a instance of flask.Flask) if that suits your needs.
att

Anderson Pierre Cardoso

2012/5/27 Simon Sapin <simon.sapin@exyr.org>

> Le 27/05/2012 19:56, vivek poddar a écrit :
> > I am not really getting the blueprint stuff. I read the docs but I
> > really need to understand it in the simpler language or I am missing
> > something.
>
> A blueprint is a set of views, templates and static files that can be
> later added to an app with an URL prefix. They can help to keep modular
> or reusable.
>
> If you’re only starting don’t worry too much about blueprints. To can
> start without them, and consider them later as your application grows.
>
> Regards,
> --
> Simon Sapin
>



-- 
Anderson Pierre Cardoso
Computer Engineer - University of Sao Paulo

[gtalk]: apierre.cardoso@gmail.com
[blog]:  http://anderson-hacklife.blogspot.com/

"FreeSoftware -> free as in freedom"  |  mande-me documentos em formatos
livres (ODF) -> http://www.infowester.com/odf.php

Re: [flask] Re: Technical Help

From:
vivek poddar
Date:
2012-05-28 @ 07:05
Hi,

A very thank to all of you, I just need to some practical example to get a
more grip on this concept. By the way I am making an app where there will
be users, access rights, statical graphs etc. So, any idea how I will be
using the blueprint. As for now I am dealing with users, I have created all
my models and now making UI specific to users like seeing the list of all
the users, getting the profile detail of a single user, assigning groups to
them and creating new one.

  As its my first web app ever and that too on flask. As far as I know this
approach of designing app is working for me till now. But as I told u I
don't have any past knowledge of web apps so, I am little bit confused on
how to proceed. One more thing till now I haven't used any extensions and
confused if to use them or not.

Thanks and Regards!

On Mon, May 28, 2012 at 4:17 AM, Anderson Cardoso <apierre.cardoso@gmail.com
> wrote:

> A blueprint it's like a plugable flask app. You mount it on a given
> prefix, this way you can keep different features in different packages
> (blueprints).
> I'm working on a app where every feature is a blueprint (even the root
> app). This is my way of working (for now).
> But you can easily come with your own way, or do everything in one app (I
> mean a instance of flask.Flask) if that suits your needs.
> att
>
> Anderson Pierre Cardoso
>
>
> 2012/5/27 Simon Sapin <simon.sapin@exyr.org>
>
>> Le 27/05/2012 19:56, vivek poddar a écrit :
>> > I am not really getting the blueprint stuff. I read the docs but I
>> > really need to understand it in the simpler language or I am missing
>> > something.
>>
>> A blueprint is a set of views, templates and static files that can be
>> later added to an app with an URL prefix. They can help to keep modular
>> or reusable.
>>
>> If you’re only starting don’t worry too much about blueprints. To can
>> start without them, and consider them later as your application grows.
>>
>> Regards,
>> --
>> Simon Sapin
>>
>
>
>
> --
> Anderson Pierre Cardoso
> Computer Engineer - University of Sao Paulo
>
> [gtalk]: apierre.cardoso@gmail.com
> [blog]:  http://anderson-hacklife.blogspot.com/
>
> "FreeSoftware -> free as in freedom"  |  mande-me documentos em formatos
> livres (ODF) -> http://www.infowester.com/odf.php
>
>


-- 

         -*- *Vivek Poddar* -*-

 *Technical consultant (OpenERP)*

*Blog:http://vivekimsit.blogspot.in/
*