Evan Winslow

Hadn't thought about the view permissions. Seems like that complicates things and we already have acls to handle that. Is it something we really need to support in core? On...

OK agreed this seems like a good feature but do we need a unified model? I guess the current way we get what you're asking for is just admin/logged in/public...

Tl;dr: Can we return a collection of users instead of a boolean for a given user? That would make for a much more flexible system in a way that I...

Yes, I was thinking the action could be what we discussed above: 1:1 relationship with current meaning of action in elgg. Accept arbitrary params. Or we could restrict the meaning....

Alternatively, we could move the whoCan onto the action... Action { whoCan(): Set } Or if we go to restful controllers: whoCanPost, whoCanGet, whoCanDelete, whoCanPut, etc. I'm not sure what...

> Also how often does the system really have to query all users who can do something? I don't know how often this would need to happen because it isn't...

I think it's possible to create an equivalent URL, yea? Are there any cases where you can do something with ecml that you can't do with an equivalent URL? On...

Rather, where it isn't possible to have an equivalent URL On Thu, Oct 23, 2014, 11:53 AM Evan Winslow [email protected] wrote: > I think it's possible to create an equivalent...

@propertunist I would like to officially drop ECML. We are trying to weigh whether to do that. One big motivation for dropping it is there already exists open standards that...

OK so we need to make sure the implementation is performance sensitive. I think that's doable. More motivation to make loading core as cheap as possible. Can we close this...