From eac33736457d6bc8e26ba00283571bb8d7d1f16e Mon Sep 17 00:00:00 2001 From: rusefi Date: Tue, 17 Dec 2019 08:56:08 -0500 Subject: [PATCH] docs --- firmware/controllers/core/common_headers.h | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/firmware/controllers/core/common_headers.h b/firmware/controllers/core/common_headers.h index 189222b212..e78518d2ba 100644 --- a/firmware/controllers/core/common_headers.h +++ b/firmware/controllers/core/common_headers.h @@ -34,12 +34,21 @@ #endif /* __cplusplus */ /** - * reference to configuration parameter + * reference to configuration parameter. */ #define DISPLAY_CONFIG(x) x /** * The main annotation of live data - reference to dynamic state variable * See also 'TS_GET_STRUCT' + * The advantage of Live Data is that there is no need to copy data into tsOutputChannels structure - Live Data is reading exactly + * the same data as actual runtime logic. It's also important to have annotations of the View as close to actual implementation as possible + * to increase the changes of those being in sync. + * + * One day Live Data could be replace with a Domain Specific Language + * One day all Live Data could be provided to TS without data copy to tsOutputChannels - the idea is to have a virtual tsOutputChannels + * where rusEfi would pull data from different memory ranges depending on the requested offset, more or less virtual pages. This could depend + * on the TS bugfix described in https://github.com/rusefi/rusefi/issues/794? + * */ #define DISPLAY_FIELD(x) x /**