add events API+issues
The broadest issue is that Wagn is still an app and trying to become a platform. The events API will give the Wagn pack API a completeness analogous to an MVC framework, though, as described in Packs+API, there are significant differences.
With the views API, we are able to arrange existing data very flexibly, but we are not enabled to customize the process of generating and modifying data. This will be the role of the events API.
The new events API should unify a lot of existing functionality and make many more things possible. For example, all of the following should be implementable via events:
old (core)
- captcha
- √ notifications
- √ geocoding
- √ emailing (flexmail)
old (non-core)
- √ creating watermarked version of images
- √ special permissions warning
new (completion of these items is not hinged to this ticket)
- required "fields" (subcards) -- this is requested very often.
- customizing page to which we are directed after login (eg by role)
- integrating with remote services
- complex transactions (eg, editing one card triggers edit of another. one case might be a ticketing system where a comment on +discussion automatically reopens the ticket by changing content of