sjDan2003 / Cookbook

0 stars 0 forks source link

Replace Kivy with Django #15

Closed sjDan2003 closed 4 years ago

sjDan2003 commented 4 years ago

After receiving constructive feedback about this Cookbook, I was asked why I choose Kivy over another GUI framework or a web based framework.

The original intent of this app was to have one backend and have the option for multiple front ends. I liked Kivy because it would have allowed me to have a desktop and mobile frontend. However Kivy has the feel of a mobile first design, and mouse and keyboards could get left behind.

I like the idea of using a web framework, as this would allow me to deploy this app to a Raspberry Pi for my household. This would also make it easier to share recipes since all recipes would be in the same database and no transfer of XML/JSON data would be required. I decided on Django, as I like their admin page and their focus on have a good framework. Others have pointed out that Django is better for projects that would grow and I hope this project continues to grow.

sjDan2003 commented 4 years ago

I finished the initial changes to convert the app from Kivy to Django. The user can now see a list of recipes that they imported from a website or they create themselves. While checking to see if recipe websites will still work, I noticed that some websites had changed their formatting. As a part of this check in I updated those scrappers. I also took this opportunity to handle errors better if websites update their format again.