Create “Gravity Pulls Pixel” program

[dcbriccetti]

This program uses the Circuit Playground Express’s accelerometer to position
a white pixel as if gravity were pulling it.

This may be too complicated to belong here. Please let me know if it is, and if there’s somewhere else within Adafruit where it could be useful. Otherwise I’ll just publish it within my own sphere.

Video here: https://youtu.be/sZ4tNOUKRpw

[kattni]

Thank you for submitting this! Please create a folder called Advanced Examples within the examples folder and move this file into that. There's definitely a place for it here, we simply need to create it!

As well the linting checks have failed through Travis on a couple of things. Please ping me if you need assistance with working through this.

[dcbriccetti]

Hi Kattni. How about we call the subfolder advanced, since examples is lower case, and it’s inside a folder examples we already know it’s examples?

[dcbriccetti]

The style check doesn’t like

    smaller = min(a1, a2)
    larger  = max(a1, a2)

But don’t we prefer that to:

    smaller = min(a1, a2)
    larger = max(a1, a2)

The other thing it didn’t like was a function’s formal parameters shadowing variables in the module scope. I got around it this time by renaming the module-level variables. Other solutions would be to disable the check, or move most of the top-level code into a new function so that those variables have function scope (as I did in another program, where you asked about it). For my own purposes, I would probably allow the variable shadowing, but I’m happy to fit in here with the way you like to do things.

[kattni]

I would prefer it be called advanced examples. I understand it is already in the examples folder, but I feel being more explicit is better. Lowercase is fine.

Having things lined up is a personal preference, however if you choose to do so, you must disable the pylint checks. I personally don't bother with lining things up, I go with proper spacing, but that is my preference.

[dcbriccetti]

I rebased to combine commits, and force pushed. If this passes, it’s ready as far as I’m concerned. Thanks!

[kattni]

Thank you so much!

For the record, we don't mind long commit lists. :)

[dcbriccetti]

I don’t understand the Travis error. Also, is the space in advanced examples OK?

[kattni]

Space should be ok, but we can underscore it instead for consistency. I don't think that's the issue. I think the issue is in how Travis looks to run pylint on the files. I believe we'll need to update .travis.yml. Give me a bit here to sort this out.

[kattni]

@dcbriccetti Ok I need to get some help on this one. I know what needs to happen but not entirely how to do it, and I believe that we need to update some further tools to deal with a subfolder. This is something I believe we would have eventually needed to do anyway, it happens to be that you're the first test case for it! I appreciate your patience. I'll keep you posted.

[dcbriccetti]

Sure! No rush. Glad to help you stretch things.

[kattni]

@dcbriccetti Still looking into this, haven't been able to coordinate with the person I need to yet. Wanted to give you an update.

[dcbriccetti]

Thanks. That’s thoughtful.

[kattni]

@dcbriccetti Please make the following change to .travis.yml:
Replace line 30

  - ([[ ! -d "examples" ]] || pylint --disable=missing-docstring,invalid-name examples/*.py)

with

  - ([[ ! -d "examples" ]] || pylint --disable=missing-docstring,invalid-name `find ./examples -name "*.py"`)

And let's see if that appeases Travis!

[kattni]

@dcbriccetti Thank you for making the change. I'm looking into this further.

[kattni]

Thanks for your patience! We've sorted it.

[dcbriccetti]

Hurray!

[ladyada]

yayy!

[siddacious]

🎉 🎉 HUZZAH! 🎉 🎉