Re: Clarifying Project vs Apps

On Wed, 24 Aug 2016, Andromeda Yelton wrote: My feeling/practice on apps is: each app is a one-word informative noun. It contains the models that are logically grouped under that noun (and the views, urls, etc required to interact with those models on the front end). Andromeda, So are

Re: Clarifying Project vs Apps

2016-08-24 21:09 GMT+02:00 Andromeda Yelton : > My feeling/practice on apps is: each app is a one-word informative noun. > It contains the models that are logically grouped under that noun (and the > views, urls, etc required to interact with those models on the front

Re: Clarifying Project vs Apps

My feeling/practice on apps is: each app is a one-word informative noun. It contains the models that are logically grouped under that noun (and the views, urls, etc required to interact with those models on the front end). If there isn't a single word that logically represents all my models, then

Re: Clarifying Project vs Apps

On Wed, 24 Aug 2016, Andreas Kuhne wrote: If you know how your project will be used, you can usually group the models and views in logical apps. For example a customer app that has the customer (user) model, address model. Then another app for orders and invoices and so on. Andréas, Here

Re: Clarifying Project vs Apps

On Wed, 24 Aug 2016, Lee Hinde wrote: So, no one is going to grade it. You're making this for yourself, so I wouldn't over think it. I'm working on a project now that only has two apps, one with all the core models and one for utility models (like choice lists).(I'm using several packages, so

Re: Clarifying Project vs Apps

2016-08-24 19:12 GMT+02:00 Lee Hinde : > On Wed, Aug 24, 2016 at 9:23 AM, Rich Shepard > wrote: > >> On Wed, 24 Aug 2016, Lee Hinde wrote: >> >> My tuppence. >>> >> >> Lee, >> >> Before or after Brexit? The value might change. :-) >> >> No, an app

Re: Clarifying Project vs Apps

On Wed, Aug 24, 2016 at 9:23 AM, Rich Shepard wrote: > On Wed, 24 Aug 2016, Lee Hinde wrote: > > My tuppence. >> > > Lee, > > Before or after Brexit? The value might change. :-) > > No, an app is a logical grouping of objects/tables. You might, for >> instance,have an

Re: Clarifying Project vs Apps

On Wed, 24 Aug 2016, Lee Hinde wrote: My tuppence. Lee, Before or after Brexit? The value might change. :-) No, an app is a logical grouping of objects/tables. You might, for instance,have an Invoice app that would include an Invoice table (model) and a LineItems table. Products and

Re: Clarifying Project vs Apps

> On Aug 24, 2016, at 8:48 AM, Rich Shepard wrote: > > While I think that I understand the differences between a project and its > apps there remains one point of uncertainty. I've not found the answer, > although it might be in the 1.10 docs or on the Web and I've

Clarifying Project vs Apps

While I think that I understand the differences between a project and its apps there remains one point of uncertainty. I've not found the answer, although it might be in the 1.10 docs or on the Web and I've missed it. If the project represents the entire database, do the apps represent