pyrosmiley/photoframe

photoframe's Issues

Standardize scripts, import as libraries as much as possible

Phase out roundabout python --> bash --> python loops, especially in button_control.py

Flickr update script hangs with no internet connection

Gonna need to figure out a way to catch a Timeout error

Flickr download script just returns corrupted and empty files

FML

RBG feedback from button controls

Mostly to show progress when user forces update from photo service. Currently, RGBLED super fucks up the update_flickr script.

Timeout for help function

So that if a user presses the button, it won't stay there forever and it'll default back to the show.

Figure out deployment strategy

update button?

Google Photos support

Give attribution for swiped code

Most notably the Big Kahuna, the pi3d show. wouldn't be anywhere without that, 100% guaranteed.

Make actual help slides instead of Iceland & duckies

you gotta actually write that stuff and make them. fr

Onboarding: let user connect to frame to set up wifi

Basically, if no known wifi network is found, launch web server to allow user to set up wifi settings a la Wemo or something like that. Ideally would scan for networks.

Migrate options to config.py

• Transition Time
• Photo Display Time
• Included Shaders
• Framerate
• Update Interval
• Filepath
• Photo Directory
• Indicator LED Brightness
• Shuffle

OAuth-based login to services

Allow users to login via the integrated webserver instead of having to get API tokens.

Start slideshow on project launch

Is video support possible?

you made that neat-o timelapse, it'd be pretty cool to be able to just dump that in there also

issue with flickr update

running the flickr update script works just fine, but removes button_control.py from receiving input from buttons. not sure if it's to do with gpiozero or not, considering all LED interaction is currently commented out.

Plex camera support

Allow enduser to specify interval to check for updates

In the future maybe we'll be able to get fancy and set separately for different sources, but first we need to have different sources. So.

Remember: No code in config, and add argument bit to Update_frame for visual feedback

[ ] global list(?) variable for photo sources
[ ] var for update interval in config
[ ] add execution to schedule.py instead of cron
[ ] multithreading in schedule.py to allow for jobs to run separately, continuously

Custom Boot Screen

it's really just an extra layer of polish, but it'd be a nice touch. Make it feel more pro

Schedule screen on/off

ALLOW for control of screen on/off from config file. Since turning the whole thing on/off automatically isn't really an option without adding some hardware, it might make sense to just hijack the 'pwr' button on the screen driver with the Rpi GPIO. That'll at least let you toggle the screen on/off, since there's no need for it to be running overnight, and the power draw from the pi itself is minimal at most.

AS far as I can tell right now, running a cron job would technically work, but doesn't allow for any user-changed settings as far as on/off times. The less an end-user has to change mess with files, the better (otherwise it won't be mom-proof, right?).

Non-public flickr albums

Probably involves major rewrite of flickr code... requires user login info also

quit launching new scripts with a system call??

import as classes and libraries instead, call from main

Allow user to select albums to display

Can't be implemented until after flickr OAuth support (probably?) but replace album ID string with user-specified albums by name

Add Dropbox Support?

not sure how it all works but it would be nice to have alternative options

Write a readme

you gotta do it dude

Instagram support(!)