On Thu, Jun 18, 2015 at 10:02 AM, Stefan Adams <s1037...@gmail.com> wrote:
> It would be great to have the simple blog example be expanded to have an > Ajax interface that did not do a page refresh for each action, use > non-blocking form in the Mojo::Pg models, and have a simple authentication > system with authorization requirements for specific routes. > > Just like with the blog example, each of the additional examples wouldn't > need to be much, just enough to demonstrate best practices. > Additionally, it would be great for this enhanced example app to also have a full suite of tests. I can understand that you wouldn't want to include such an example app in Mojolicious core because of the unmet dependencies (such as Mojo::Pg). Perhaps a separate project repo whose sole purpose is to tie all these things (Mojolicious, Mojo::Pg, Minion) together and include a few additional routine bells and whistles like auth/authz, websockets, non-blocking database model, ajax user interface, etc and have a suite of tests to make the whole thing test-driven! I would buy another limited edition shirt. Probably even a couple! :D -- You received this message because you are subscribed to the Google Groups "Mojolicious" group. To unsubscribe from this group and stop receiving emails from it, send an email to mojolicious+unsubscr...@googlegroups.com. To post to this group, send email to mojolicious@googlegroups.com. Visit this group at http://groups.google.com/group/mojolicious. For more options, visit https://groups.google.com/d/optout.
