Page 1 of 1
Differences when converting *.framework to *.exf files
Posted: Tue May 03, 2022 7:11 pm
by Johann
Hello,
I am using 24.1 Web Author version and I try to convert my *.framework files to *.exf files.
The first thing I notice is that a piece of js is no longer called.
A js file present in the "web" folder which allows to do toolbar customization is not called anymore.
It contains:
Code: Select all
goog.events.listen(workspace, sync.api.Workspace.EventType.EDITOR_LOADED, function(e) {
console.log("Editor is loaded ",$)
});
and I do no see this trace in the console.
Did I miss a change during the conversion?
Thank you,
Johann
Re: Differences when converting *.framework to *.exf files
Posted: Wed May 04, 2022 9:03 am
by cristi_talau
Hello,
When using EXF, you should explicitly specify which JS files to load using the webResource element as described here [1]. The "web/" folder is loaded only for the old ".framework" format which did not have a way to specify which JS files to load.
I will update the documentation to mention that the "web" folder does not apply when creating an EXF framework from scratch.
Best,
Cristian
[1]
https://www.oxygenxml.com/doc/versions/ ... _framework
Re: Differences when converting *.framework to *.exf files
Posted: Wed May 04, 2022 10:42 am
by Johann
Hello Cristian.
Ok that's right. It solves my issue.
On the other hand, I have another issue.
I have converted *.framework files to *.exf files but these ones were the "base" frameworks.
I already had *.exf files that override the *.framework files. It worked well.
But now that *.framework files have been replaced by *.exf files, the overridden *.exf files cannot be loaded by author web.
I have this message in Administration Page / Settings / Frameworks :
Could not load the framework descriptor: <Right-path>\description-smart.exf
This file only contains:
Code: Select all
<script xmlns="http://www.oxygenxml.com/ns/framework/extend"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.oxygenxml.com/ns/framework/extend
http://www.oxygenxml.com/ns/framework/extend/frameworkExtensionScript.xsd"
base="my framework base">
<name>my custom framework TEST</name>
<description>Test</description>
<priority>High</priority>
</script>
Thank you,
Johann
Re: Differences when converting *.framework to *.exf files
Posted: Wed May 04, 2022 7:21 pm
by Bogdan Dumitru
Hello Johann,
It seems that Web Author has a limitation and doesn't support an "*.exf" that extends another "*.exf", it just supports "*.exf" that extends a regular "*.framework". I've registered an issue in our internal issue tracker for that.
As a workaround, you can compile the base "*.exf" to a "*.framework" by opening the "*.exf" in Oxygen XML Editor and invoking the "Compile Framework Extension Script" action from the contextual menu. Then you can upload the compiled "*.framework" file in Oxygen XML Web Author instead of the "*.exf" file.
Re: Differences when converting *.framework to *.exf files
Posted: Wed May 04, 2022 7:29 pm
by Johann
Hello,
My goal was to convert base *.framework files to *.exf files.
So I will wait for the fix before pushing my work.
Can you send me a notification when the fix will be released?
Thank you,
Johann
Re: Differences when converting *.framework to *.exf files
Posted: Thu May 05, 2022 8:54 am
by mihaela
Hello,
Sure, we will update this thread when the fix will be available.
If you also want to be notified by email, please send a request to
support@oxygenxml.com .
Best Regards,
Mihaela
Re: Differences when converting *.framework to *.exf files
Posted: Tue Aug 22, 2023 3:09 pm
by Johann
Hello,
Is the fix still in your backlog?
Or has it been published in the last released versions?
Thank you,
Johann
Re: Differences when converting *.framework to *.exf files
Posted: Tue Aug 22, 2023 3:56 pm
by mihaela
Hello,
The issue is still in our backlog, the fix is not released.
Best Regards,
Mihaela
Re: Differences when converting *.framework to *.exf files
Posted: Fri Nov 29, 2024 11:25 am
by cosminef
Hello,
Starting with
version 27 of
Oxygen XML Web Author, you can disable framework validation both from the user interface [1] and from the
options.xml file [2].
This way, you will no longer receive the error "Could not load the framework descriptor..." during validation, and it should work properly.
[1]
https://www.oxygenxml.com/doc/versions/ ... _framework
[2]
https://www.oxygenxml.com/doc/versions/ ... s,-Boolean
Best,
Cosmin