Re: Blue colored python file in Django Project structure.

Yup, This is pycharm IDE, and thanks for guidlines. On Friday, November 24, 2017 at 10:53:40 PM UTC+5:30, Dylan Reinhold wrote: > > This has nothing to do with django or python. This is your IDE using > colors to give you status information. Looking like you are using pycharm. > By default (whic

Re: Blue colored python file in Django Project structure.

This has nothing to do with django or python. This is your IDE using colors to give you status information. Looking like you are using pycharm. By default (which you can change) blue just means the file has been updated. https://www.jetbrains.com/help/pycharm/file-status-highlights.html Dylan On

Blue colored python file in Django Project structure.

hello, While working on Django project, suddenly one of my python file name in structure changed to blue. Till now it does not raise any error, but I am shock why it happened. Is anybody have idea regarding this change in django project directory.. -- You received this message because you ar

Re: Django project structure

You would just have one App loyalty program. You will extend UserProfile from User and the other models would be Restaurant (name,branch location etc would be the attributes). Your structure would depend on what are the various functionalities you would like to add. On Monday, October 24, 2016

Re: Django Project Structure

On 28/10/2016 5:17 PM, Deep Shah wrote: I have read this, but still confused. What would be the best practices for this? Your email doesn't say what you have read ("this" above?) so the following recommendation may be a duplication. In any case I recommend Two Scoops of Django[1] for well rea

Re: Django Project Structure

I have read this, but still confused. What would be the best practices for this? On Wednesday, October 26, 2016 at 12:05:19 PM UTC+5:30, Deep Shah wrote: > > I have a django project which is a loyalty program for restaurants. The > different database tables are- Users (and extending it with Us

Re: Django Project Structure

See this link: https://docs.djangoproject.com/en/1.10/intro/tutorial01/#creating-the-polls-app The box "Projects vs app" can help you. On 26 October 2016 at 04:35, Deep Shah wrote: > I have a django project which is a loyalty program for restaurants. The > different database tables are- Users (

Django Project Structure

I have a django project which is a loyalty program for restaurants. The different database tables are- Users (and extending it with User Profiles), Restaurant Company (the entire chain), Branches, Offers, Points (points which users get on visiting a particular restaurant) etc. How do I structur

Django project structure

I have a django project which is a loyalty program for restaurants. The different database tables are- Users (and extending it with User Profiles), Restaurant Company (the entire chain), Branches, Offers, Points (points which users get on visiting a particular restaurant) etc. How do I structur

Re: Django Project Structure for mixins - best solution?

Thank you Mike, I have a project related question also on this group, maybe you have time and take a look, please see the link below: Django Related Project Question

Re: Django Project Structure for mixins - best solution?

Thank you Mike, I have a project related question also on this group, maybe you have time and take a look, please see the link below: Django Related Project Section

Re: Django Project Structure for mixins - best solution?

Thank you Mike, I have a project related question also on this group, maybe you have time and take a look, please see the link below: Django Related Project Section

Re: Django Project Structure for mixins - best solution?

On 2/06/2016 12:54 AM, sevenrrain...@gmail.com wrote: I seen multiple project structure for Django, but they didn't discuss in detail about structuring mixins. I see that some people use mixins.py , others utils folder. Taking in consideration that I have many mixins for views(generic login,aut

Django Project Structure for mixins - best solution?

I seen multiple project structure for Django, but they didn't discuss in detail about structuring mixins. I see that some people use mixins.py , others utils folder. Taking in consideration that I have many mixins for views(generic login,authorization and more specific for the project) and

Re: Django project structure

Hi Carl That's a great idea. So, I think the idea is to make the model flexible enough that it can be used in multiple contexts. The rest follows, accordingly. I'll give it a try. Thanks a lot for the inspiration! Cheers André On Thursday, 4 February 2016 22:05:28 UTC+1, André Meyer-Vitali w

Re: Django project structure

Hi André, On 02/04/2016 02:47 PM, André Meyer-Vitali wrote: > How would I modify my contest app so that it knows about multiple > contests? Database models (and queries), templates, forms, urls need to > be adapted, I guess. Is it sufficient to add an ID to the models such > that a specific month'

Re: Django project structure

Thanks for your reply, Carl. How would I modify my contest app so that it knows about multiple contests? Database models (and queries), templates, forms, urls need to be adapted, I guess. Is it sufficient to add an ID to the models such that a specific month's data can be selected, for example?

Re: Django project structure

Hi André, On 02/04/2016 02:05 PM, André Meyer-Vitali wrote: > There's quite some confusion here about the best way to structure a > Django project. > > I'm developing a photography related web site with a news section (based > on the poll tutorial) and a contest app (among others). The contest ap

Django project structure

Dear Django Developers There's quite some confusion here about the best way to structure a Django project. I'm developing a photography related web site with a news section (based on the poll tutorial) and a contest app (among others). The contest app should be reused every month for a new con

Django project structure design

's will be captured in categories). In feature i will add my concepts in mother page up-to 10 to 20. So my question is: Which way I need to design the django project structure? I have two idea which one is best:- 1 >> Each category will be separate project, and mother page will be separate