Move device to it's own module (device.py)

[yandy-r]

What do you guys think about moving device() out of main.py and putting it in it's own module? This way we can have a true representation of the Model/View/Controller. Can also help in modularizing things a bit more.

So in this case:

Things contained under vendors are the Model for this.
Device would be the Controller
and main would be the view, the representation of the data that Device is interpreting from the model classes.

Keeping device in main, can make it cumbersome as this grows.

Just an idea. Thoughts?

[wdennis]

Is there a overall design doc available? (If not, maybe a good idea?)

On Sun, Apr 6, 2014 at 11:29 AM, Yandy Ramirez [email protected]:

What do you guys think about moving device() out of main.py and putting it
in it's own module? This way we can have a true representation of the
Model/View/Controller. Can also help in modularizing things a bit more.

So in this case:

Things contained under vendors are the Model for this.
Device would be the Controller
and main would be the view, the representation of the data that Device
is interpreting from the model classes.

Keeping device in main, can make it cumbersome as this grows.

Just an idea. Thoughts?

Reply to this email directly or view it on GitHubhttps://github.com//issues/24
.

[wdennis]

This is why I ask, by the way ;) http://t.co/9P6iNNXKU4

On Sun, Apr 6, 2014 at 1:40 PM, Willard Dennis [email protected]:

Is there a overall design doc available? (If not, maybe a good idea?)

On Sun, Apr 6, 2014 at 11:29 AM, Yandy Ramirez [email protected]:

What do you guys think about moving device() out of main.py and putting
it in it's own module? This way we can have a true representation of the
Model/View/Controller. Can also help in modularizing things a bit more.

So in this case:

Things contained under vendors are the Model for this.
Device would be the Controller
and main would be the view, the representation of the data that Device
is interpreting from the model classes.

Keeping device in main, can make it cumbersome as this grows.

Just an idea. Thoughts?

Reply to this email directly or view it on GitHubhttps://github.com//issues/24
.

[yandy-r]

ha! that was freaking funny, stealing that picture

[jedelman8]

No, there isn't. But I do want to start one, or at lease start documenting better.

Stay tuned.

On Apr 6, 2014, at 1:40 PM, Will Dennis [email protected] wrote:

Is there a overall design doc available? (If not, maybe a good idea?)

On Sun, Apr 6, 2014 at 11:29 AM, Yandy Ramirez [email protected]:

What do you guys think about moving device() out of main.py and putting it
in it's own module? This way we can have a true representation of the
Model/View/Controller. Can also help in modularizing things a bit more.

So in this case:

Things contained under vendors are the Model for this.
Device would be the Controller
and main would be the view, the representation of the data that Device
is interpreting from the model classes.

Keeping device in main, can make it cumbersome as this grows.

Just an idea. Thoughts?

Reply to this email directly or view it on GitHubhttps://github.com//issues/24
.

—
Reply to this email directly or view it on GitHub.

[sjiveson]

I'm quite happy to help with this too if need be.
Cheers
Steve Iveson

Date: Sun, 6 Apr 2014 10:47:35 -0700
From: [email protected]
To: [email protected]
Subject: Re: [cpal] Move device to it's own module (device.py) (#24)

No, there isn't. But I do want to start one, or at lease start documenting better.

Stay tuned.

On Apr 6, 2014, at 1:40 PM, Will Dennis [email protected] wrote:

Is there a overall design doc available? (If not, maybe a good idea?)

On Sun, Apr 6, 2014 at 11:29 AM, Yandy Ramirez [email protected]:

What do you guys think about moving device() out of main.py and putting it

in it's own module? This way we can have a true representation of the

Model/View/Controller. Can also help in modularizing things a bit more.

So in this case:

Things contained under vendors are the Model for this.

Device would be the Controller

and main would be the view, the representation of the data that Device

is interpreting from the model classes.

Keeping device in main, can make it cumbersome as this grows.

Just an idea. Thoughts?

Reply to this email directly or view it on GitHubhttps://github.com//issues/24

.

—

Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.

[yandy-r]

likewise

---

Yandy Ramirez

On Mon, Apr 7, 2014 at 4:42 AM, Steven Iveson [email protected]:

I'm quite happy to help with this too if need be.
Cheers
Steve Iveson

Date: Sun, 6 Apr 2014 10:47:35 -0700
From: [email protected]
To: [email protected]
Subject: Re: [cpal] Move device to it's own module (device.py) (#24)

No, there isn't. But I do want to start one, or at lease start documenting
better.

Stay tuned.

On Apr 6, 2014, at 1:40 PM, Will Dennis [email protected]
wrote:

Is there a overall design doc available? (If not, maybe a good idea?)

On Sun, Apr 6, 2014 at 11:29 AM, Yandy Ramirez <[email protected]
wrote:

What do you guys think about moving device() out of main.py and
putting it

in it's own module? This way we can have a true representation of the

Model/View/Controller. Can also help in modularizing things a bit more.

So in this case:

Things contained under vendors are the Model for this.

Device would be the Controller

and main would be the view, the representation of the data that
Device

is interpreting from the model classes.

Keeping device in main, can make it cumbersome as this grows.

Just an idea. Thoughts?

Reply to this email directly or view it on GitHub<
https://github.com/jedelman8/cpal/issues/24>

.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHubhttps://github.com//issues/24#issuecomment-39707294
.