michael-gracie / gslides

Wrapper around Google APIs to create charts in Google Slides with python
https://michael-gracie.github.io/gslides
MIT License
31 stars 6 forks source link

Feedback #6

Open jfyu opened 3 years ago

jfyu commented 3 years ago

docs

other feedback

Overall though the functionality is good and it's pretty cool. I haven't seen a similar package in pypi so this might be useful to some people (if their internal organisation opens the Google API). Advanced usage I could think of would be porting the presentation back into python and manipulate the graphs, because currently this is only going one way (data -> plot). What if I want to get the data back and do something else?

michael-gracie commented 3 years ago
  • Picky but it's very strange that the child class of something called a Series should be things like Line/Scatter/Area etc....wouldn't these come under something like Plot or Chart or something? If something inherited from a Series I'd expect series manipulation (I don't know what that would be to be honest but feels like the children classes are mostly plotting kind..)

I think that goes back to Kun's comment about aligning naming. Series is a naming that google uses but I am not consistent across the package

michael-gracie commented 3 years ago
  • I second Kun's addSlide/rmSlide idea, it feels so much more natural than calling a construction method everytime. A follow up to this is that it's actually kind of strange that everything is a class. It seems that the only method I would ever call on every class is execute, which goes back to the previous point. It definitely feels like those Line/Area/Scatter can be methods as opposed to classes

Definitely will do the full refactor to make the class into objects

michael-gracie commented 3 years ago
  • personal habit but maybe not zero logging? This is hard to debug if any bug.

Good point. The one valuable piece of information that would make sense logging is the json blob that is being passed to the Google API