JSFields in M5 Definition

[Mykola Soldatenkov]

Can you use JSFields in M5 Definition? Trying to decorate old JCR Tools app.
For regular fields only old syntax is working, but JS Field in docs has new syntax with $type property. Tried class: info.magnolia.ui.javascript.field.JavascriptFieldDefinition but no luck. Is it possible?

[Roman Kovařík]

Hi,

As far as I know, JavaScript fields heavily use the M6 API, so I don’t think it’s possible to do this without a complete rewrite of the implementation. 

Best regards

Roman

[Mykola Soldatenkov]

Hi,
thx, I see
Am I understanding it right that each module usually has its own implementation of the compatibility module? (e.g. groovy-module -> groovy-compatibility-module) and JSFields doesn't have its own yet?
Or maybe JSFields compatibility module wouldn't resolve this issue for some other reasons?

--

-- 

Powyższa wiadomość wraz z ewentualnymi załącznikami jest przeznaczona wyłącznie do wiadomości osób lub podmiotów, do których jest w sposób zamierzony zaadresowana. W przypadku otrzymania powyższej wiadomości w wyniku pomyłki, prosimy o pilne powiadomienie o tym fakcie nadawcy oraz o usunięcie wiadomości z systemu, a także o nie rozpowszechnianie treści w niej zawartych. Otrzymanie powyższej wiadomości nie może stanowić podstawy do jakichkolwiek zobowiązań nadawcy tej wiadomości wobec osób nie będących jej zamierzonymi adresatami. 

This e-mail message and any attachments is intended solely for the use of the persons or entities to whom it is intentionally addressed. If you have received this message in error, please notify the sender about this fact immediately and delete it completely from your computer system. Please do not disseminate this message unless you are the intended recipient of it. This e-mail message shall not create any legal obligation on the part of the sender to persons who are not intended recipients of it.

[Roman Kovařík]

It’s unfortunately the other way around. The M5 framework is not receiving new features; instead, the old M5 fields have been ported to the M6 framework. The M5 implementation has usually been moved to compatibility modules. These compatibility modules ensure that you can still use the M5 fields in M5 applications. ThejavascriptFieldwas introduced later in Magnolia 6.2 and won’t be ported back to the M5 framework.

On Friday, February 2, 2024 at 1:23:36 PM UTC+1 undi...@gmail.com wrote:

Hi,
thx, I see
Am I understanding it right that each module usually has its own implementation of the compatibility module? (e.g. groovy-module -> groovy-compatibility-module) and JSFields doesn't have its own yet?
Or maybe JSFields compatibility module wouldn't resolve this issue for some other reasons?

[Mykola Soldatenkov]

Ok, thanks for the reply.

On Fri, Feb 2, 2024 at 2:34 PM Roman Kovařík <roman....@magnolia-cms.com> wrote:

It’s unfortunately the other way around. The M5 framework is not receiving new features; instead, the old M5 fields have been ported to the M6 framework. The M5 implementation has usually been moved to compatibility modules. These compatibility modules ensure that you can still use the M5 fields in M5 applications. ThejavascriptFieldwas introduced later in Magnolia 6.2 and won’t be ported back to the M5 framework.

On Friday, February 2, 2024 at 1:23:36 PM UTC+1 undi...@gmail.com wrote:

Hi,
thx, I see
Am I understanding it right that each module usually has its own implementation of the compatibility module? (e.g. groovy-module -> groovy-compatibility-module) and JSFields doesn't have its own yet?
Or maybe JSFields compatibility module wouldn't resolve this issue for some other reasons?

On Fri, Feb 2, 2024 at 8:05 AM Roman Kovařík <roman....@magnolia-cms.com> wrote:

Hi,

As far as I know, JavaScript fields heavily use the M6 API, so I don’t think it’s possible to do this without a complete rewrite of the implementation. 

Best regards

Roman

On Thursday, February 1, 2024 at 9:16:09 PM UTC+1 undi...@gmail.com wrote:

Can you use JSFields in M5 Definition? Trying to decorate old JCR Tools app.
For regular fields only old syntax is working, but JS Field in docs has new syntax with $type property. Tried class: info.magnolia.ui.javascript.field.JavascriptFieldDefinition but no luck. Is it possible?

--

-- 

Powyższa wiadomość wraz z ewentualnymi załącznikami jest przeznaczona wyłącznie do wiadomości osób lub podmiotów, do których jest w sposób zamierzony zaadresowana. W przypadku otrzymania powyższej wiadomości w wyniku pomyłki, prosimy o pilne powiadomienie o tym fakcie nadawcy oraz o usunięcie wiadomości z systemu, a także o nie rozpowszechnianie treści w niej zawartych. Otrzymanie powyższej wiadomości nie może stanowić podstawy do jakichkolwiek zobowiązań nadawcy tej wiadomości wobec osób nie będących jej zamierzonymi adresatami. 

This e-mail message and any attachments is intended solely for the use of the persons or entities to whom it is intentionally addressed. If you have received this message in error, please notify the sender about this fact immediately and delete it completely from your computer system. Please do not disseminate this message unless you are the intended recipient of it. This e-mail message shall not create any legal obligation on the part of the sender to persons who are not intended recipients of it.