lord2800 / deadline Goto Github PK

While I was working on the video controller, I ran into an issue where the response tried to create an AviView because the path ended with .avi. While that behavior was "correct", it was undesired. I need to decouple the view from the response, and make each controller responsible for returning the view they want (with a nice helper method in HttpResponse that automatically determines the view type unless you override it) and pass that to the response for rendering.

This will involve making PathWrapper check two locations: the directory that the phar is in first, and inside the phar second. Any and all files should be overridable by placing the file in the right directory structure.

Things to add:

• More widgets for various other controllers
  • Videos (trending, currently viewing, view count)
• User Management
  • Add a user
  • Disable a user
  • Delete a user
  • List all users
• Template management
  • Making new templates based on other templates
  • Maybe editing templates?
• Settings
  • List settings and have a way to edit settings (test type, have proper editor)
• Route editor

Issue #4 decoupled the view from the response, so /video/file should use a FileView that issue #5 is describing.

I need unit tests across everything. I'll make a list later.

They generate the wrong results. Also, make test cases for these bad results.

The cache class should favor memcache first, apc cache second, wincache third, maybe redis? fourth. Any expensive calculations should be cached.

Right now errors are statically routed to an Error class with static methods for the status number. I'm not sure of a better way to handle this yet, but it desperately needs fixing. Also, the shutdown error handler isn't finished in any way.

In 89cfcd6, I hacked the controller and view factories to scan a list inside the storage instead of looking in the Right Place (TM) for them. I need to decide how to scan for them, and the unhack that code.

Now that users can sign in and out, I need a way to protect pages by requiring authenticated users (optionally, with a specific role). I'm thinking a view descended from HtmlView for not-authed/wrong-role is going to suffice. That saves me typing as well as looks pretty.

Currently, users aren't remembered and there's no throttling for invalid attempts, not to mention no way to reset passwords. All of those things need doing.

I need a basic "page" controller for static content pages that aren't blog posts. Basically, a wiki.

That's going to be some hairy code, but it'll provide a pretty hefty win for complex/image-filled pages if I can sprite images automatically.

Issue #4 fixed views to be decoupled from the response, so now I should make a FileView that handles byte ranges and setting the right headers and putting the file to the content stream. That will slim down the bad code bloat in HttpResponse.

As mentioned in #11, there's currently no way to request a password reset. Additionally, the user profile page doesn't let you edit any fields successfully, and it lets any authed user edit any other user's fields. Plus, there's no way to add/remove users to/from roles.

Issue #4 made it possible to remove HttpResponse::setFileDownload, so I should do that.

Assuming I can sprite images into a single tile, that will be a significant http traffic win as well as a loading win up to a certain size--which is what I'll need to figure out if/when I do this.

I need to create an installer script. It needs to build the tables and insert some basic data into them (like the guest and admin users).

Currently, routing uses strpos() to determine which route has a positional parameter first. This is incorrect--it should be breaking apart the route into pieces and testing each piece to see if it's a positional parameter instead. This should be easy to fix, but low priority.