Repository navigation
Platform build targets #6013
Replies: 2 comments 1 reply
|
Thanks! Glad the JavaScript builds are working well for you. The JavaSE menu behavior is expected. Desktop mode moves the toolbar and side-menu commands into the native menu bar, with ungrouped commands appearing under “Commands”. You can group them using codename1.arg.desktop.titleBar=toolbarThe Linux buttons not responding sounds like a bug. Does that happen with the freshly generated test app too, or only with the converted app? Do the buttons respond to keyboard activation? The libcurl message indicates a library symbol-version compatibility warning, even though the file exists. We need to investigate that separately; it isn’t yet clear whether it’s related to the buttons. Please include the complete terminal output, particularly any “required by” text following the warning, and whether you’re running X11 or Wayland. If there are other JavaSE display problems beyond the menu placement? |
|
Thanks. We have a pr that should hopefully fix this issue. It should go into the upcoming update this weekend. |

Uh oh!
There was an error while loading. Please reload this page.
I've just converted an old app to use CSS and built it using the Javascript build target. I have to say it's very impressive, and on a mobile device seems to behave very much like a native app. Kudos on making this work.
I also create a test app with the 'Create Project'. This creates a perfectly good Javascript build as well.
I also tried a JavaSE build. This didn't display too well. Like my app which has a LHS menu and a RHS menu, the commands are placed under a 'Commands' menu. Is this expected behavior ?
I also did a Cloud Linux build. The result binary loads, but the buttons don't work. Also I get an error:
/lib64/libcurl.so.4: no version information available - libcurl.so.4 exists (Alma Linux 9).
Overall, it's pretty cool that all these targets are available from the same code base.
All reactions