| Widgets classic are different from js [message #1839542] |
Tue, 23 March 2021 10:25  |
Eclipse User |
|
|
|
I am reviewing the new version (11) of scout, one of the advantages I see is to use its js version as frontend of an existing project in quarkus, but it strikes me that the widgets between both versions are different. If so or just that the examples contain the differences?
For example in the classic version there is the calendar widget but in js I don't see it.
I appreciate the clarification.
Regards,
Nelson F.
|
|
|
| Re: Widgets classic are different from js [message #1839576 is a reply to message #1839542] |
Wed, 24 March 2021 02:42  |
| Eclipse User |
|
|
|
Hi Nelson
You're right. The CalendarField.js seems to be missing in the JS Widgets app. I don't think that this is intentionally. Compared to the Scout Classic widgets app the Scout JS widgets app is quite new, so I guess we just didn't add the CalendarField to this app yet. However: when we add a new widget to the JS app, we take care that the JavaScript API of the widget works as intended, so if you plan to use it right now, you may stumble upon problems here and there.
In case you're not sure whether or not a widget exists in Scout JS you can simply look at the @eclipse-scout/core module. Everything that's in there can be used in a Scout JS app.
If must use the CalendarField in a Scout JS app now, I'd suggest to have a look at the Scout Classic widgets app anyway, because the widgets used in the Classic app are the same as in the JS app. Start the browser's dev tools (f12) and check the JSON response you see there, when you open the CalenderField-form and click around there. You may also set some breakpoints in Calendar.js. This way you should see, what parameters the widget expects, and which functions you should call, even though it is not yet "officially" available in the Scout JS app.
Cheers,
André
|
|
|
|
Powered by
FUDForum. Page generated in 0.03443 seconds
Home