On Friday 16 June 2017 04:45:22 Arshpreet Singh wrote:
> So basically there will be few ML models and I will feed those some
> variables and will get some output. Before writing any kind of code I
> am interested in the architecture of the whole system. Django is the
> option to use and do things.
>
> I am bit confused and not sure where I should start to do things?
You do things in models.
You gather things in views.
You render things in templates.
You make things available through urls.
Pretty much.
--
Melvyn Sopacua
On Saturday 17 June 2017 12:17:18 A.S. Khangura wrote:
> Any way you could make me go through Architecture Design of system.
> Or any kind of open-Source project where I would be able to study
> things and look for how I can make my own?
The documentation. The tutorial takes you through all the steps I mentioned and in addition introduces the admin, forms (connecting user input with models, views and templates) and unit tests.
--
Melvyn Sopacua
On Saturday 17 June 2017 13:11:17 A.S. Khangura wrote:
> On Fri, Jun 16, 2017 at 8:39 PM, Melvyn Sopacua <m.r.s...@gmail.com> wrote:
> > You do things in models.
>
> So that means all my ML models would be Django-Models?
Yes. Models should be a representation of the data and their interaction.
> > You gather things in views.
>
> I will pass data and get results from functions to show on web-pages.
Parameters you get from requests which are passed on through URLs.
Session info can also be used to pass in data (which is tied to a cookie in the request). And finally HTTP headers may also provide information (such as the user's preferred languages).
The basic job of a view is to return a request into a response. This is by nature a functional pattern, but there are also class-based-views, which make sharing common functionality a lot easier.
--
Melvyn Sopacua