-
Notifications
You must be signed in to change notification settings - Fork 6
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
clean up UnderDevelopmentPlane ? #69
Comments
My thoughts were about var vBox = new VBox( {
align: 'left',
spacing: 20,
children: [
new Text( underDevelopmentLine1String, {
font: new PhetFont( 22 ),
maxWidth: maxTextWidth
} ),
new VBox( {
align: 'left',
children: [
new Text( underDevelopmentLine2String, {
font: new PhetFont( 16 ),
maxWidth: maxTextWidth
} ),
new RichText( linkText, {
links: true, // allow links in linkText
font: new PhetFont( 16 ),
maxWidth: maxTextWidth
} )
]
} )
]
} ); I too don't think it is so bad, I mentioned it because it was atypical more than it being really problematic. |
What don't you like about it? The nested structure? |
Specificity @zepumph ....Specificity :) |
Sorry folks. Yes indeed the nested structure was what I was looking at. After discussing it through, I think it is best as is. I mentioned it because I was not used to so much node creation without variable names. To me it looked sloppy. I feel good to close now without action. |
I agree, nesting like this is not desirable - difficult to read and maintain. But plan to see it in other PhET code, because it's a style preferred by some of the other PhET developers. |
In #30 (comment), @zepumph said:
What do you find messy about it? There's more "nesting" of instantiation than I typically use, but certainly not any more than some developers. The only duplication that I see is
PhetFont(16)
, and that's just coincidental - the text and link could (and did) have different font sizes.The text was updated successfully, but these errors were encountered: