kube - A personal information and collaboration application

	Commit message (Collapse)	Author	Age
*	Generalize the single account concept.	Christian Mollekopf	2017-09-08
\| \| \| \| \| \| \|	* The wizard get's configured with a list of available accounts. * If only a single account type is available we skip the selection. * For the first account, account setup can not be aborted. * In single account mode the account can not be removed.
*	Some basic input field validation.	Christian Mollekopf	2017-09-08
\|
*	Single account mode	Christian Mollekopf	2017-09-07
\| \| \| \|	It's hardcoded to be enabled and set to kolabnow at the moment (TBD).
*	make more translatable	Michael Bohlender	2017-07-19
\|
*	introduce Kube.Heading	Michael Bohlender	2017-06-29
\|
*	remove kirigami dependency	Michael Bohlender	2017-06-27
\|
*	Immediately trigger a sync when creating an account	Christian Mollekopf	2017-06-21
\| \| \| \|	... and return to the mailview
*	use more kube controls in account	Michael Bohlender	2017-04-19
\|
*	make more use of Kube.Button and Popup in accounts	Michael Bohlender	2017-04-06
\|
*	A single framework plugin	Christian Mollekopf	2017-04-05
\|
*	use theme	Christian Mollekopf	2017-04-04
\|
*	port more stuff to kube theme	Michael Bohlender	2017-03-30
\|
*	Fixed kolabnow account setup page.	Christian Mollekopf	2017-02-22
	The account plugin supplies the configuration UI, the application supplies the scaffolding. That way we ensure the application doens't contain any account specific code and account configurations are free to offer specialized UI's that work best for them. We're not currently using a standardized controller, but if we did those controllers would have to live with the plugin, not the framework or the components.