Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flesh out phet-software-design-patterns.md #88

Closed
pixelzoom opened this issue Jan 3, 2019 · 32 comments
Closed

flesh out phet-software-design-patterns.md #88

pixelzoom opened this issue Jan 3, 2019 · 32 comments

Comments

@pixelzoom
Copy link
Contributor

pixelzoom commented Jan 3, 2019

Related to phetsims/tasks#969 (comment)

At 1/3/19 dev meeting, @ariel-phet suggested that we should spend the next couple weeks of "core hours" reviewing PhET-specific design patterns. @zepumph suggested that someone should evaluate the state of phet-software-design-patterns.md, and @ariel-phet asked me to do that.

@pixelzoom
Copy link
Contributor Author

pixelzoom commented Jan 4, 2019

phet-software-design-patterns.md is currently just a sketch of what might be covered in the document. With the exception of the the "options and config parameters" section, there's no meat.

Some options:
(1) Have someone make a pass at fleshing out the document (not something that I have time for or interest in doing), then discuss/refine in discussions.
(2) Discuss patterns one at a time, and assign someone to flesh out the documentation for that pattern based on the discussion. Probably the more expensive of the 2 approaches.

@ariel-phet How do you want to proceed for next Monday's "core hours" discussion, and longterm?

@pixelzoom pixelzoom assigned ariel-phet and unassigned pixelzoom Jan 4, 2019
@ariel-phet
Copy link
Contributor

@pixelzoom Lets do a compromise.

Can you flesh out 1 pattern? and then that can be discussed at core hours. Perhaps after that, we can do a round robin. Each week a developer takes on a pattern to flesh out, and then it gets discussed at core hours. Seems like it would be a good learning experience.

@pixelzoom
Copy link
Contributor Author

That sounds OK, and I'll be happy to flesh out one of the patterns. But I won't get to it before next Monday's core hours.

@zepumph
Copy link
Member

zepumph commented Jan 4, 2019

I'll take a stab at one for Monday if you would like.

pixelzoom added a commit that referenced this issue Jan 7, 2019
pixelzoom added a commit that referenced this issue Jan 7, 2019
pixelzoom added a commit that referenced this issue Jan 7, 2019
pixelzoom added a commit that referenced this issue Jan 7, 2019
pixelzoom added a commit that referenced this issue Jan 7, 2019
pixelzoom added a commit that referenced this issue Jan 7, 2019
@pixelzoom
Copy link
Contributor Author

pixelzoom commented Jan 7, 2019

1/7/19 dev meeting on Zoom during core hours:

We put "interested developers" next to each pattern, developers self-identified who would benefit from having the pattern description fleshed out.

@pixelzoom will flesh out "Enumeration" for 1/14/19, for discussion at core hours.

@zepumph will flesh out "Dispose" for 1/14/19 (in case there's time to discuss), but we might not get to discuss until 1/28/19.

@zepumph zepumph self-assigned this Jan 8, 2019
@pixelzoom
Copy link
Contributor Author

@pixelzoom will flesh out "Enumeration" for 1/14/19, for discussion at core hours.

On hold until we resolve phetsims/phet-core#53 (Enumeration conventions).

@zepumph
Copy link
Member

zepumph commented Jan 11, 2019

Dispose design pattern added above.

@pixelzoom
Copy link
Contributor Author

Enumeration description has been fleshed out. Devs please review for Monday 1/14/19 discussion.

@pixelzoom pixelzoom removed their assignment Jan 11, 2019
zepumph added a commit that referenced this issue Jan 16, 2019
@zepumph
Copy link
Member

zepumph commented Jan 28, 2019

Discussed dispose today. I will update the docs and we will review next week. I would like to note here that we discussed the 4 implementation patterns seen in the code, but we didn't discuss the general pattern or when it is appropriate to dispose (and conversely when we shouldn't be disposing/when there is no need).

I would like to make sure we do that before moving on from this pattern.

@pixelzoom
Copy link
Contributor Author

pixelzoom commented Jun 8, 2020

All sections of phet-software-design-patterns.md have now been fleshed out. So closing this issue.

brandonLi8 added a commit that referenced this issue Jun 8, 2020
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid added a commit that referenced this issue Apr 23, 2022
samreid added a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
samreid pushed a commit that referenced this issue Apr 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants