[dev] Perms UI

[Chuck Hagenbuch]

Quoting Duck <duck at obala.net>:

> With Perms_UI version 1.35 from 3 weeks ago is presumed that there is a horde
> or application level predefine set of sub-permission values.  So when we add
> child permission we always use an populated enum values. But the problem
> comes when we would like to add an "random" child or and child permission to
> an app with no permission API call. The patch makes the Perms_UI to fallback
> to the old text input field when all the other options fails.

Apps should generally know what permissions they have though, right? So 
why not just add the permission you want to add to the app's api perms 
description?

-chuck

-- 
"But she goes not abroad in search of monsters to destroy." - John 
Quincy Adams