On 27.01.2012 12:34, A.L.E.C wrote:
TODO:
- create rcube_framework class as a base for rcmail, which will contain
only backend-related functionality. The idea is that in use-case where UI is not needed we'll be able to just do: class rcmail extends rcube_framework {}
- make plugins api optional, create rcmail::exec_hook() as
plugins->exec_hook() wrapper,
- don't use translation (gettext()) inside backend classes, e.g. should
rcube_addressbook return translated error messages? I think so.
- should rcube_message go to the backend group? if so, it cannot depend
on rcube_ui nor localization,
any comments on the above points?
- fix html class dependencies (rcube_ui::Q) so it can be "moved" to
Utils group,
done.
Some more ideas:
functionality,
e.g. json_serialize())
rcube_output