6 Commits

Author	SHA1	Message	Date
bjoern	7f43d3bb37	let sending invalid webxdc fail (#2993) ... * let sending invalid webxdc fail invalid webxdc can still be send as Viewtype::File, however (maybe one want to discuss errors or so ;) * clarify the supported zip compression methods	2022-01-22 11:19:21 +01:00
B. Petersen	6316ee7c9b	add editable "summary" to dc_msg_get_webxdc_info() ... the summary can be modified by the apps using `sendUpdate({summary: "foo", payload: ...})` the summary is updated when there is no newer update and chat will be informed by the change as usual by `DC_EVENT_MSGS_CHANGED`.	2022-01-16 00:30:53 +01:00
B. Petersen	b6b8d11881	add option to trigger an info-message from an webxdc-update	2022-01-16 00:30:53 +01:00
B. Petersen	a043557c44	move payload to {payload:PAYLOAD} to allow additional parameters ... additional parameters will be `summary` and `msg` (for an info-message) right now, and maybe more in the future (`aggregated`, `fast`, `to` ...), so adding just more parameters easily gets wild. also, this makes adaptions easier as no ffi needs to be adapted when we add more parameters. finally, sending is in-sync with receiving, database and wire now, one receives similar objects as one sends, which also looks like the right thing :) for now, `sendUpdate()` also allows to use the old, unwrapped payload to not immediately break existing `.xdc`, however, that will be removed soon, probably before the first release.	2022-01-15 00:10:59 +01:00
B. Petersen	8c2ea0fa26	swap paramters in sendUpdate(); the 'descr' may be split up in the future, so it makes sense to have that at the end	2022-01-13 11:11:50 +01:00
B. Petersen	14e9afaf42	rename 'User Guide' to 'Developer Reference'	2022-01-13 11:11:50 +01:00